Module 2 Unified - Process PDF
Module 2 Unified - Process PDF
and Design
1
MODULE TWO
UNIFIED PROCESS
System development Process models
in object technology (with UML)
2
Assignment-1
3
Advantages:
Users are involved in the A&D process
Captures requirements in concrete form, rather than
verbal/abstract form
Disadvantages
Insufficient analysis
User confusion of prototype and finished system
Developer misunderstanding of user objectives
Developer attachment to prototype
Excessive development time of the prototype
Relatively costly development as developers produce different
versions before final delivery
Iterative and Incremental (Evolutionary)
development
15
Problems
• Lack of process visibility
• Systems are often poorly structured due to lack of proper
planning
• Special skills (e.g. in languages for rapid prototyping) may be
required
Applicability
•For small or medium-size interactive systems
•For parts of large systems (e.g. the user interface)
•For short-lifetime systems
Iteration Across Life Cycle Phases
Iterative Refinement
Evaluation Requirements
Implementation
(prototype) Design
Spiral model- as part of evolutionary process
20
Phase iteration
Inception
Establish the business case for the system.
Elaboration
Develop an understanding of the problem domain and the
system architecture.
Construction
System design, programming and testing.
Transition
Deploy the system in its operating environment.
The Unified Process Life Cycle
Model
Benefits of RUP
Requirement definition
captures the functional and non functional
requirements of the new system
Tries to understand what users need
aims at building mainly the essential use case
model and CRC
Outcome: Understanding users through Use-case
Diagram, CRC, Essential UI prototyping ,
Supplementary specification
Cont…
32
Analysis
Structuring, analyzing and modeling requirements
aims at understanding the system and building the
analysis model
helps the developer refine and structure the functional
requirements captured through essential use-case
model
Outcome: Determining what the system should do
and look like through System Use case, Class/Object
Diagram, Sequence Diagram, Activity diagram and UI
prototyping.
Design
Focus on how to make the analysis a reality
defines how things will be built
aims at building the design model
describes the physical realisations of the use cases
from the use-case models and the contents of the
analysis model
Outcome: Design level class diagram, Collaboration
Diagram, sate chart diagram, component diagram,
deployment diagram, persistent model; extending the
UML
Cont…
34
Structured vs OO technologies
Structured (process oriented) Vs OOT (object oriented)
End of Module 2