Mastering Object-Oriented Analysis and Design With UML
Mastering Object-Oriented Analysis and Design With UML
Best Practices
Process Made Practical
Develop Iteratively
Manage Requirements
Use Component
Architectures
Model Visually (UML)
Continuously Verify Quality
Manage Change
Evaluation
Waterfall Risk
Risk
Risk Reduction
Iterative Risk
Time
Best Practices
Process Made Practical
Develop Iteratively
Manage Requirements
Use Component
Architectures
Model Visually (UML)
Continuously Verify Quality
Manage Change
Problem Problem
Space
Needs
Solution
Tr
Space
a
Features
ce
a bil
The
ity
Product
Software to Be
Requirements Built
Best Practices
Process Made Practical
Develop Iteratively
Manage Requirements
Use Component
Architectures
Model Visually (UML)
Continuously Verify Quality
Manage Change
Best Practices
Process Made Practical
Develop Iteratively
Manage Requirements
Use Component
Architectures
Model Visually (UML)
Continuously Verify Quality
Manage Change
Collaboration Component
Models
Diagrams Diagrams
DocumentList
add( )
name : int
Actor A Actor B fetchDoc( ) delete( )
docid : int
sortByName( ) numField : int Writing
add file [ numberOffile==MAX ] /
flag OFF
get( )
open( ) read() fill the
Use Case 2 close( ) code..
Openning
FileList read( )
sortFileList( )
fList create( )
fillDocument( ) close file
add( )
delete( )
1
rep
File
Repository
(from Persistence)
name : char * = 0
readDoc( )
readFile( )
read( )
GrpFile
read( )
open( )
create( )
Deployment
Diagram
fillFile( )
Collaboration 9: sortByName ( )
Repository DocumentList
2: fetchDoc( )
FileManager
Window95
¹®¼°ü¸®
Ŭ¶óÀ̾ðÆ®.EXE
Windows95
Windows95
8: fillFile ( ) Windows
NT
IBM
7: readFile ( ) Mainframe
5: readDoc ( )
document : Document
repository : Repository µ¥ÀÌŸº£À̽º¼¹ ö
user
mainWnd fileMgr :
FileMgr
document :
Document
gFile repository
Component
Diagram
Target
ƯÁ¤¹®¼ ¿¡ ´ëÇÑ º¸±â¸¦ 1: Doc view request ( )
»ç¿ëÀÚ°¡ ¿äûÇÑ´Ù.
2: fetchDoc( )
3: create ( )
4: create ( )
System
5: readDoc ( )
7: readFile ( )
8: fillFile ( )
Forward and
ȸ é °´Ã¼´Â ÀÐ¾îµ éÀÎ 9: sortByName ( )
°´Ã¼µé¿¡ ´ëÇØ À̸§º°·Î
Á¤·ÄÀ» ½ÃÄÑ È¸ é¿¡
º¸¿©ÁØ´Ù.
Sequence Reverse
Diagram Engineering
Mastering Object Oriented Analysis and Design with UML
Copyright © 2003 Rational Software, all rights reserved 21
Practice 5: Continuously Verify Quality
Best Practices
Process Made Practical
Develop Iteratively
Manage Requirements
Use Component
Architectures
Model Visually (UML)
Continuously
Verify Quality
Manage Change
Mastering Object Oriented Analysis and Design with UML
Copyright © 2003 Rational Software, all rights reserved 22
Continuously Verify Your Software’s Quality
Software problems are
100 to 1000 times more costly
to find and repair after deployment
Functionality Reliability
Test the accurate Test that the application
workings of each behaves consistently
usage scenario. and predictably.
Supportability Performance
Test the ability to Test the online response
maintain and support under average and
application under peak loading.
production use.
Mastering Object Oriented Analysis and Design with UML
Copyright © 2003 Rational Software, all rights reserved 24
Test Each Iteration
Iteration 1 Iteration 2 Iteration 3 Iteration 4
UML Model
and
Implementation
Tests
Requirements Capture
Verify Approach
Time
Best Practices
Process Made Practical
Develop Iteratively
Manage Requirements
Use Component
Architectures
Model Visually (UML)
Continuously Verify Quality
Manage Change
Configuration
Management is
more than just
check-in and check- REPORT ALERT
out Process Build
Integration Management
Validates architectural
Use Component Architectures
decisions early on
Addresses complexity of
Model Visually (UML) design/implementation incrementally
Best Practices
Process Made Practical
Develop Iteratively
Manage Requirements
Use Component Architectures
Model Visually (UML)
Continuously Verify Quality
Manage Change
Iterative approach
Guidance for activities
and artifacts
Process focus on
architecture
Use cases that drive
design and
implementation
Models that abstract
the system
time
time
Disciplines
group
activities
logically.
Models
Implemented
Realized By By
Realized Business Use- Use-Case
By Case Model Model
B
B B B
Automated
Business By Design Model Implementation
Object Model Model
Requirements:
Workflow
Mastering Object Oriented Analysis and Design with UML
Copyright © 2003 Rational Software, all rights reserved 41
Overview of Rational Unified Process Concepts
Divided into Considers Described by
Workflow
Phase Iteration Discipline Detail
Participates in References
Role Activity
Responsible for Modifies
Model
Document Model
Element
Artifact
Mastering Object Oriented Analysis and Design with UML
Copyright © 2003 Rational Software, all rights reserved 42
Review
Best Practices guide software engineering
by addressing root causes.
Best Practices reinforce each other.
Process guides a team on who does what,
when, and how.
The Rational Unified Process is a means of
achieving Best Practices.