Software Development *Life-Cycle Phases*

1. Software Development*Life-Cycle Phases* Compiled by: Dharya - 1706223 Daisy - 1706240

2. Table of Contents

3. 1. Inception Phase Engineering and production Stages 4. Transition Phase 2. Elaboration Phase 3.Construction Phase

4. Software Development Process • Well defined separation between research and development activities and production activities • Overemphasis on research and development • Overemphasis on production

5. Modern Software Development Process Support : • Evolution of the Plan, requirement and architecture • Risk management and objective measures • Evolution of System capabilities

6. Life Cycle Phases : • Engineering stage - driven by less predictable but smaller teams doing design and synthesis activities • Production Stage - driven by more predictable but larger teams doing construction, test, and deployment activities.

7. LIFE CYCLE ASPECT ENGINEERING STAGE EMPHASIS PRODUCTION STAGE EMPHASIS Schedule, Technical Feasibility RISK REDUCTION Cost Product Release Baselines PRODUCTS Architecture Baseline Analysis, Design Planning ACTIVITIES Implementation, Testing Demonstration, Inspection, Analysis ASSESSMENT Testing Resolving diseconomies of scale Exploiting Economics Of scale ECONOMICS MANAGEMENT Planning Operations

8. Engineering Stage • Inception • Elaboration • Production Stage • Construction • Transition

9. Engineering Stage Production Stage Inception Elaboration Construction Transition Idea Architecture Beta Releases Products

10. Inception Phase : Primary Objectives • Establishing the project software scope and boundary conditions • Clear Understanding of what should be there or what should not? • Demonstrating at least one candidate architecture • Estimating the cost and schedule for entire project • Estimating potential risks

11. Essential Activities • Formulating Scope of the project • Synthesizing the architecture • Planning and preparing a business case

12. PrimaryEvaluation Criteria • Satisfaction of all stakeholder!! • Are requirements understood by critical use cases ?? • Are the cost and schedule estimates credible?? • Do the depth and breadth of an architecture prototype demonstrate the preceding criteria?? • Resource management is there or not??

13. ElaborationPhase • Most Critical Phase!! • Executable architecture prototype is built • Make a vision • Establishing a configuration managed snapshot • Base lining a fidelity plan for next phase • Cost Vs Time graph must work smoothly

14. Primary Objectives • Base lining the architecture as rapidly as practical. • Base lining the vision • Base lining a high-fidelity plan for the construction phase • Demonstrating that the baseline architecture will support the vision at a reasonable cost in reasonable time

15. EssentialActivities • Elaborating the vision: Understanding use cases that do planning decisions • Elaborating the process and infrastructure: evaluation of milestones is done i.e. what percent we have reached?? • Elaborating the structure and selected components

16. Primary Evaluation Criteria • Is the vision stable?? • Is the architecture stable?? • Address the major risks that can occur • Do all stakeholders agree on current vision

17. Construction Phase • During this phase, all remaining components and application features are integrated into the application and all features are thoroughly tested. • Newly developed software is integrated when required. • Managing resources and controlling operation to optimize costs, schedules and quality is the emphasis of the construction phase which represents production stage.

18. Primary Objectives • Minimizing developing cost by optimizing resources • Avoid unnecessary scraps and rework • Achieving adequate quality as rapidly as possible. • Achieving useful versions (alpha ,beta, and other tests releases).

19. Essential Activities • Resource Management, control and process optimization • Assessment of Product releases • Complete component development and testing

20. Primary Evaluation Criteria • Is this product baseline mature enough to be deployed in the user community? • Is this product baseline stable enough to be deployed in the user community? • Are the stakeholders ready for the transition to the user community?

21. Transition Phase • This phase is entered when a baseline is mature enough to be deployed in the end user domain. • This phase includes :: • Beta testing to validate the new system • Conversion of the operational databases • Training of users

22. Primary Objectives • Achieving user self-supportability. • Achieving stake holders concurrence that deployment baselines are complete and consistent with the evaluation criteria. • Achieving Final product baselines as rapidly and cost-effectively

23. Essential Activities • Synchronization and integration of current construction increment into consistent deployment baselines. • Assessment of deployment baselines against the complete vision • Acceptance criteria in the requirement set

24. Evaluation Criteria • Is the user satisfied? • Are actual resource expenditures versus Planned expenditures acceptable?

25. *Thank You*