Download Software Development Model and more Slides Software Engineering in PDF only on Docsity! Waterfall Model • Linear sequential model • each phase must be completed before the next phase can begin and there is no overlapping in the phases. • outcome of one phase acts as the input for the next phase sequentially
Requirement
Analysis
Waterfall Model
Maintenance
Disadvantages • Not a good model for complex and object- oriented projects. • It is difficult to measure progress within stages. • Cannot accommodate changing requirements. RAD Model • based on prototyping and iterative development • focuses on gathering customer requirements through workshops or focus groups • uses minimal planning in favor of rapid prototyping • model the functional modules are developed in parallel as prototypes and are integrated to make the complete product for faster product delivery RAD Model • there is no detailed preplanning, it makes it easier to incorporate the changes within the development process Advantages • Changing requirements can be accommodated. • Reduced development time. • Progress can be measured. • Quick initial reviews occur • Encourages customer feedback • Integration from very beginning solves a lot of integration issues. Disadvantages • Requires highly skilled developers/designers. • High dependency on modeling skills • Management complexity is more. • Dependency on technically strong team members for identifying business requirements. Iterative Model • iterative process starts with a simple implementation of a small set of the software requirements and iteratively enhances the evolving versions • Iterative process starts with a simple implementation of a subset of the software requirements and iteratively enhances the evolving versions until the full system is implemented. • At each iteration, design modifications are made and new functional capabilities are added. V - Model Detailed Design Unit Testing High-level Design Integration Testing Software Requirements Specification System Testing Acceptance Testing Contract Warranty Coding User’s Software Requirements Review/Test So ft w ar e D ev e lo p m e n t V e ri fi ca ti o n a n d T e st in g “V” Model Each phase has corresponding test or validation counterpart Requirements Analysis System Design Program Design Implementation Unit Test Integration Test Acceptance Test SDLC STLC Requirements Gathering Requirement Analysis - The requirements documents are analyzed and validated and scope of testing is defined. Designing Test Planning, Analysis and Design - Defining test specifications, analyses and reviewing of requirement documents, risk analysis reports and other design specifications. Coding Test Case Development, Test Environment Setup - Involves the test case creation, test data and environment setup. Testing Test Execution - Involves manual and automated test case execution and result logging. Deployment Exit Criteria Evaluation, Resporting and Test CLosure - Involves checking if all the project deliverables are delivered, archiving the testware, test environment and documenting the learnings. Maintenance Maintenance testing - Testing required after an upgrade, correction or any change in the software under maintenance.
