It is Unified Modeling Language.

2.  Unified Modeling Language
 Family of graphical notations
 Backed by single meta-model
 Helps in describing and designing s/w system
 Particularly oo style
 Discussion abt design
 Open standard, controlled by OMG ( Object
ManagementGroup)

3.  1980s, Object Oriented languages used
widely
 Then the concept of Object oriented
graphical design languages established
 Grady Booch, Ivar Jcobson, Jim Rumbaugh
are the creators of UML

4. Web - June 1996
OOPSLA 95
Public
Feedback
OMG Acceptance, Nov 1997
Final submission to OMG, Sept 1997
First submission to OMG, Jan 1997
UML 1.0UML partners
UML 1.1
UML 1.4
UML 2.0
Planned minor revision (2000)
Planned major revision (2001)
UML 1.3Current minor revision 1999

5.  UML defines notations and meta-model
 Notation :
 Graphical stuff in models
 Graphical syntax of the modeling language
 Primarily meta-model is developed

7.  RUP is independent of UML
 Related concepts
 RUP is process framework
 It is essentially an iterative process
 Four phases of RUP projects
 Inception
 Elaboration
 Construction
 Transition

8.  Inception
 Initial evaluation of project
 You decide whether to commit enough funds to
do next phase or move forward.
 Elaboration
 Identifies primary use cases of the project in
iteration
 At the end, good sense of requirement and
skeletal working system
 Found and resolve the major risk

9.  Construction
 Actual building process
 Coding & testing
 Enough functionality for release
 Transition
 Late-stage activity
 Do not do iteratively
 Deployment of project

10.  Requirements analysis includes
 Users/customers want from system
 For that following UML techniques are used
 Use cases
▪ Describes how people interact with the system
 Class Diagram
▪ Drawn from conceptual perspective
 Activity Diagram
▪ Show the flow of the organization
▪ s/w and human activities interact
 State Diagram
▪ Life cycle of system
▪ with various states and events that change that state

11.  During Design Phase, Technical involvement of
system
 Precise notation is used
 Useful techniques for design phase
 Class Diagram
▪ s/w perspective
▪ Interrelation of the various classes
 Sequence Diagram
▪ Different kind of scenarios from system
 Package Diagram
▪ Large-scale organization of system
 State Diagram
 Deployment Diagram
▪ To show physical layout of the s/w

12.  2Types of process for project development
 Waterfall
 Iterative
 The difference in the way we break up a
project into smaller chunks

13.  Breaks down a project
based on activity
 1-year long project divide
into the parts
 Delays and aggregates
integration and testing
Code and unit test
Design
Subsystem integration
System test
Waterfall Process
Requirements
analysis

14.  Breaks down a project by subsets of functionality
 1-year project into 3-months iterations
 i.e. you take a quarter of the requirements and do
the complete SDLC for that quarter
 Analysis, design, coding, testing
 At the end of the one quarter, you have the system
that does a quarter of the functionality needed

15. Initial
Planning
Planning
Requirements
Analysis & Design
Implementation
Deployment
Test
Evaluation
Management
Environment
Each iteration
results in an
executable
release

16. • At the end of each iteration you have
production version of the s/w
• A project having multiple releases
• OO community in favor of ITERATIVE
DEVELOPMENT

17. • Used to capture the functional requirements
• Interactions between user and the system
• SCENARIO is the sequence of steps
describing an interaction