SDC Models

• This Model employs rigorous phases in a linear application development process, with one phase ending and the next commencing at that point.

  Waterfall Model.
• The model's sequential steps prevent developers from going back to earlier ones if they are left unchanged, which is why the term "waterfall" refers to the fact that once water falls, it cannot rise again
• Phases of Waterfall Model

  1. Requirements
  2. Analysis
  3. Design
  4. Coding
  5. Testing
  6. Operation or Deployment
  7. Maintenance
• Given its benefits and drawbacks, this model may be...

  • a good option for projects with clearly defined requirements and an idea of the final product that needs to be produced.
  • However, projects requiring frequent iterations or those with changing needs are less suited to it due to its lack of flexibility and the possibility of late surprises.
  • Before deciding to use the this model for software development, teams should thoroughly assess the needs of the project and take into account other approaches like agile or iterative approaches.
• Advantages of Waterfall Model

  • Simple and Easy to Understand
  • Clear Requirements
  • Structured Approach
• Disadvantages of Waterfall Model

  • Inflexibility
  • Limited Client Involvement
  • Risk of Late Surprises
  • Long Delivery Time
  • Not Suitable for Complex Projects
• It is the process that runs in a V-shape, step-by-step. The verification and validation model is another name for it.

  V-Shape Model
• • Its foundation is the assignment of a testing phase to every relevant step of development.
  • Every step's development is closely related to the testing stage. There is a testing activity for every development activity, and the next step doesn't begin until the previous phase is finished.

  V-Shape Model
• • In general, projects with well stated requirements and minimal levels of uncertainty may benefit from using this model.
  • However, in more dynamic contexts where requirements are likely to change, its rigidity and limited adaptability might provide problems.
  • Before deciding on a development approach, it's critical for enterprises to thoroughly assess the unique requirements and project peculiarities.

  V-Shape Model
• Advantages of V-Shape Model

  • Highly disciplined model
  • Project requirements are clear
  • The model focuses on verification and validation activities
  • Emphasis on Testing
• Disadvantages of V-Shape Model

  • High risk and uncertainty
  • It is not good for complex and object-oriented projects.
  • Does not support iteration of phases.
  • Inflexibility
  • Time-Consuming
  • Overreliance on Documentation
• Overall, this model offers a flexible and adaptable approach to software development. However, it requires careful planning, disciplined execution, and effective project management to be successful.

  Iterative Model
• Phases of Iterative Model

  1. Requirement and Analysis
  2. Design
  3. Implementation
  4. Testing
  5. Deployment
  6. Review
  7. Maintenance
• Advantages of Iterative Model

  • Early Functionality and Feedback
  • Flexibility
  • Reduced Risk
  • Cost-Effective Changes
  • Improved Quality
• This model is a software development process that starts with implementing software requirements and gradually enhances them over time until a complete system is developed. It starts with a review of requirements and produces new versions at each iteration, with each release ending in a fixed period.

  Iterative Model
• Disadvantages of Iterative Model

  • Documentation Challenges
  • Project Management
  • Potential for Delays
  • May Not Suit Small Projects
• This is a risk-driven software development process that combines elements of the iterative and waterfall models. It emphasizes risk identification and mitigation throughout the development lifecycle.

  Spiral Model
• • Overall, this Model is a POWERFUL APPROACH for managing risk and building high-quality software in complex projects with evolving requirements.
  • This model can be tailored to the specific needs of a project.
  • Each iteration of the spiral typically involves activities like planning, risk assessment, development, testing, and customer review.

  Spiral Model
• Phases of Spiral Model

  1. Planning
  2. Risk Analysis
  3. Engineering
  4. Evaluation
• Advantages of Spiral Model

  • Risk Handling
  • Good for large projects
  • Customer Satisfaction
  • Iterative and Incremental Approach
  • Emphasis on Risk Management
  • Improved Quality
• Disadvantages of Spiral Model

  • Complex
  • Expensive
  • Too much dependability on Risk Analysis
  • Difficulty in time management
  • Time-Consuming
• This model is an iterative approach to software development that emphasizes creating functional prototypes early and often. These prototypes serve as simplified, working models of the intended software that allow for user feedback and early validation of requirements.

  Prototyping Model
• Advantages of Prototyping Model

  • Early User Feedback
  • Reduced Development Costs
  • Risk Mitigation
  • Enhanced Communication
• Disadvantages of Prototyping Model

  • Time and Resource Investment
  • Focus on Prototypes
  • "Throwaway" Prototypes
• Phases of Prototyping Model

  • Requirement Gathering and Analysis
  • Quick Design
  • Build a Prototype
  • Initial User Evaluation
  • Refining Prototype
  • Implement Product and Maintain
• This model is a valuable approach for projects where user FEEDBACK and early VALIDATION of requirements are crucial. It fosters an iterative development process that leads to a more user-centric and refined final product. The level of detail and functionality in prototypes can vary depending on the project's needs.

  Prototyping Model
• This Model is a flexible and iterative approach to software development that emphasizes collaboration, rapid prototyping, and continuous improvement. It prioritizes delivering working software in short cycles (iterations) with ongoing feedback from stakeholders.

  Agile Model
• This model offers a powerful approach for delivering high-quality software in a collaborative and adaptable manner. However, careful consideration should be given to project complexity, documentation needs, and the level of discipline required within the development team.

  Agile Model
• Phases of Agile Model

  • Requirements gathering
  • Design the requirements
  • Construction/ iteration
  • Testing/ Quality assurance
  • Deployment
  • Feedback
• Advantages of Agile Model

  • Faster Time to Market
  • Improved Quality
  • Increased Flexibility
  • Enhanced Customer Satisfaction
  • Teamwork and Morale
• Disadvantages of Agile Model

  • Project Management Complexity
  • Documentation Challenges
  • May Not Suit All Projects
  • Requires Discipline
• Verification Phases of V-Shape Model

  • Requirement Analysis
  • System Design
  • Architectural Design
  • Module Design
  • Coding Phase
• Validation Phases of V-Shape Model

  1. Unit Testing
  2. Integration testing
  3. System Testing
  4. Acceptance Testing