Hi everyone! I’m a student currently working on a research activity for our Software Engineering class, and I’d really appreciate your insights. 😊

I’m looking to gather input from software developers, project managers, or engineers about the Software Development Life Cycle (SDLC) paradigms you’ve used in your past or current projects.

If you have a few minutes to spare, I’d love to hear your answers to these quick questions:

  1. What type of software did you develop? (e.g., mobile app, enterprise system, game, etc.)

  2. Which software development paradigm did your team follow? (eg. Prototyping Model, Spiral Model, Fourth Generation Techniques (4GT), Waterfall Model Agile Model, V-Shaped Model, Incremental Model, RAD (Rapid Application Development), Feature Driven Development (FDD), Big Bang Model, Scrum, etc)

  3. Why did you choose that particular paradigm? (e.g., client requirement, team familiarity, project scale, etc.)

Your input will be used for academic purposes only, and it would really help me complete this task with real-world insights. Thank you so much in advance!

  • Cheezyburger@programming.devOPEnglish
    4·
    2 days ago

    Hi guys thank you so much for participating in my survey! I understand that some of you may not be familiar with the specific SDLC models used in your past projects. To help clarify, here is a list of common SDLC models that may have been used in your projects:

    1. Prototyping Model: Quickly builds a basic version (prototype) of the software, gets feedback from users, and improves it through several iterations. It’s helpful when requirements are unclear.

    2. Spiral Model: Combines planning, risk analysis, and iterative development, revisiting each stage multiple times. It’s great for complex projects where risk management is key.

    3. Fourth Generation Techniques (4GT): Uses tools that automatically generate code, speeding up development but still requiring testing and design. It’s useful for small projects or prototypes.

    4. Waterfall Model: A sequential process where each step (e.g., design, coding, testing) is completed before moving to the next. It works well for projects with clear, unchanging requirements.

    5. Agile Model: Uses short development cycles (sprints) to create small, working parts of the software and allows frequent feedback from users. It’s flexible and works well when requirements change.

    6. Scrum Model: A type of Agile, Scrum breaks the project into small, manageable tasks and focuses on completing them in short, time-boxed periods called sprints. Teams hold daily meetings to discuss progress and adjust plans. It’s great for projects where the team needs flexibility and constant communication.

    7. V-Shaped Model: Like Waterfall but with a focus on testing. Each development phase is followed by a corresponding testing phase to ensure quality.

    8. Incremental Model: Breaks the system into smaller parts (increments) that are developed and tested one by one, delivering functional parts early. It allows flexibility in adding features later.

    9. RAD (Rapid Application Development): Focuses on quickly building prototypes and gathering user feedback to refine the system. It’s fast and flexible, making it great for projects with changing needs.

    10. Feature Driven Development (FDD): Develops software based on client-valued features, with each feature being developed in small cycles. It’s effective for medium-sized projects.

    11. Big Bang Model: Starts development with little planning and no defined steps, often used for smaller projects with minimal requirements. Changes are made as needed, but it’s unpredictable.