(Software Engineering )Unified Process Model

 Unified Process Model :

1. It is a use-case driven, architecture-centric, iterative and incremental software process 
2. UP is an attempt to draw on the best features and characteristics of conventional s/w process models 
3. Also implements many of the best principles of agile software development 
4. UP is a framework for object-oriented software engineering using UML (Unified Modelling Language) 
5. UML—a unified modelling language that contains a robust notation for the modelling and development of object-oriented systems. 

 

PHASES OF UP 

1) Inception 

• Encompasses both customer communication and planning activities 

• Fundamental business requirements are described through a set of preliminary use-cases 
  

• A use-case describes a sequence of actions that are performed by an actor (e.g., a person, a machine, another system) as the actor interacts with the software  
• A rough architecture for the system is also proposed 

2) Elaboration 

• Encompasses customer communication and modelling activities 
• Refines and expands the preliminary use-cases 

• Expands the architectural representation to include five different views of the software 

•      1) The use-case model 

•      2) The analysis model 

•      3) The design model 

•      4) The implementation model 

•      5) The deployment model 

• In some cases, elaboration creates an “executable architectural baseline” that represents a “first cut” executable system 

 

3) Construction 

• Makes each use-case operational for end-users 
• Unit tests are designed and executed for each component as they get implemented 
• Integration activities (component assembly and integration testing) are conducted 
• Use-cases are used to derive a suite of acceptance tests 

 

4) Transition 

• Software is given to end-users for beta testing 

• The software team creates the necessary support information – 

  User manuals 
• Trouble-shooting guides 
• Installation procedures 
• At the conclusion of the transition phase, the software increment becomes a usable software release 

5) Production 

• Coincides with the deployment activity of the generic process 
• The on-going use of the software is monitored 
• Support for the operating environment (infrastructure) is provided 
• Defect reports and requests for changes are submitted and evaluated 

 

UNIFIED PROCESS WORK PRODUCTS 

Inception 
        Vision document 
         Initial use-case model 
Elaboration 
        Analysis model, design model 
Construction 
        Implementation model, deployment model, test model 
Transition 
        Delivered software, beta test reports, general user feedback