Lecture 5 software process model (3)
Download as PPT, PDF2 likes1,931 views
The document discusses the Unified Process (UP) model for software development. It describes how the UP was created by combining the best features of individual object-oriented analysis and design methods. The UP includes five phases - Inception, Elaboration, Construction, Transition, and Production. The Inception Phase involves planning and requirements activities. The Elaboration Phase refines use cases and expands the architectural design. The Construction Phase focuses on building the software. The Transition Phase involves user testing and feedback. The Production Phase involves monitoring the deployed software.
Lecture 5 software process model (3)
- 1. Introduction to Software Engineering Muhammad Nasir Software Process Model m.nasir@iiu.edu.pk
- 2. Unified Process (UP) Model ïź During the early 1990s James Rumbaugh, Grady Booch, and Ivar Jacobson began working on a âUnified Methodâ that would combine the best features of each of their individual object-oriented analysis and design methods ïź And adopted additional features proposed by other experts in object-oriented modeling. ïź The result was UMLâa Unified Modeling Language that contains a robust notation for the modeling and development of object-oriented systems. ïź UML became a de facto industry standard for object-oriented software development
- 3. Phases of the Unified Process
- 4. Inception Phase ïź Unified Process is also no exception and has the same five Process Framework activities ïź Inception Phase encompasses both customer communication and planning activities
- 5. Inception Phase ïź Architecture at this point is nothing more than a tentative outline of major subsystems and the function and features that populate them ïź Planning identifies resources, assesses major risks, defines a schedule
- 6. Elaboration Phase ïź Elaboration phase encompasses the Planning and modeling activities of the generic process model. ïź Elaboration refines and expands the preliminary use cases that were developed as part of the inception phase
- 7. Elaboration Phase ïź And expands the architectural representation to include Five different views of the software ïź Requirements Model ïź Use Case Model ïź Design Model ïź Implementation Model ïź Deployment Model
- 8. Construction Phase ïź The Construction Phase of the UP is identical to the construction activity defined for the generic software process.
- 9. Transition Phase ïź The Transition Phase of the UP encompasses the latter stages of the generic construction activity and the first part of the generic deployment (delivery and feedback) activity. ïź Software is given to end users for beta testing and user feedback reports both defects and necessary changes.
- 10. Production Phase ïź The production phase of the UP coincides with the deployment activity of the generic process. ïź During this phase, the ongoing use of the software is monitored, support for the operating environment (infrastructure) is provided, ïź And defect reports and requests for changes are submitted and evaluated.
- 11. The End ïź Thanks for listening ïź Questions would be appreciated.
Editor's Notes
- #3: [deË ËfaktoË]) is a Latin expression that means "concerning fact." In law, it often means "in practice but not necessarily ordained by law" or "in practice or actuality, but not officially established.â
- #5: Inception: The beginning of something, such as an undertaking; a commencement.
- #7: In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal. The actor can be a human or an external system.