%in tembisa+277-882-255-28 abortion pills for sale in tembisa
Steps for System Design Realize all Use Cases Use Sequence Diagram
1. 1 / 26
System Design
with UML & Rational Rose
Robert C. Chi
cnchi@iis.sinica.edu.tw
Academia Sinica
2. 2 / 26
Agenda
What We Got Currently?
What is System Design?
Steps of System Design
Use Case Realization
Sequence Diagrams
Create User Interfaces
Create Classes
Create Database
Maintain Traceability
Re-factoring
Code Generation
Reverse Engineering
Summary
3. 3 / 26
What We Got Currently
Customer
Workers
Request Project
Create Project
Create Tasks of Project
Schedule Tasks
Assign Tasks
Report Status of Tasks
Check Status
Project Manager
Business Use Case Diagrams
Not Yet Request
Wait for
Approval
Download the
Request Form
Fill out the
Request Form
Send the
Request Form
Project Request Form
[Request Approved]
Project Request Form
[Request Disapproved]
Review the
Request
Review
Finished
Request Approved
Request Disapproved
Project Request
Form
[Not Yet Request]
Project Request Form
[Wait for Approval]
Got the
Request Form
Review the
Request Form
Approve the
Request
[ Approved ]
Disapprove the
Request
[ Disapproved ]
Project Manager
Customer
Workflow by Activity Diagrams
4. 4 / 26
What We Got Currently
Conceptual Models by Class Diagram
5. 5 / 26
What We Got Currently
Assign Tasks
Check Status
Create Project
Create Tasks of Project
Assign Tasks
(from Business Model)
Check Status
(from Business Model)
Create Project
(from Business Model)
Create Tasks of Project
(from Business Model)
Report Status of Tasks
Request Project
Schedule Tasks
Report Status of Tasks
(from Business Model)
Request Project
(from Business Model)
Schedule Tasks
(from Business Model)
Realization of Business Use Cases by Use Case Diagrams
6. 6 / 26
What We Got Currently
Apply Account
Login Account
Logout Account
User
(from 010 Actors)
Confirm Account
<<include>>
Use Case Diagrams
Not Login
Login the
System
Error
Message
Main Page
[Login]
Home Page
[Not Login]
Validate the
User
Show Error
Message
[ Invalid ]
Redirect to
Main Page
[ Valid ]
Show Main
Page
Login
System
User
System Flow by Activity Diagrams
7. 7 / 26
What We Got Currently
No Account
Wait for
Confirm
Has
Account
Account Closed
Apply Account
Confirm
Account
Login Account
Login
Logout Account
Logout
Dependency of Use Cases by Activity Diagrams
8. 8 / 26
What is System Design
Find the UI & Classes
that realize the System
Functions (Use Cases)
Find the Architecture to
Integrate all the UI and
Classes
9. 9 / 26
Steps of System Design
Realize the Use Cases
Find UI & Classes by Sequence Diagrams
Create UI & Classes
Create Database
Maintain Traceability
Re-factoring
Code Generation
Reverse Engineering
10. 10 / 26
Use Case Realization
Apply Account
(from 020 System Flow)
Confirm Account
(from 020 System Flow)
Login Account
(from 020 System Flow)
Logout Account
(from 020 System Flow)
Apply Account
Confirm Account
Login Account
Logout Account
11. 11 / 26
Use Case Realization
Why Realization Diagrams?
Modify Independently
Traceability
12. 12 / 26
Use Case Realization
Practice
Realize all the Use Cases in Logical View of
“Mr. Delay Software Company” System
Models
13. 13 / 26
Sequence Diagrams
: User : index : login : main
Visit
Fill Username & Password
Submit
'validateForm( )
Sequence Diagram:
Login Account / E1
Form Invalid
redirect
ValidateUser(String, String)
Sequence Diagram:
Login Account / E2
Login Fail
14. 14 / 26
Create User Interfaces
Before Start
Make Sure Your “Default Language” is “Web Modeler”
19. 19 / 26
Create User Interfaces
Practice
Create the Home Page and Main Page of
the “Mr. Delay Software Company” Project
Create the Sequence Diagram with the
pages you have
20. 20 / 26
Create Database
Steps of Creating Database
Create a Database in Component View
Assign Target Database (SQL92, Oracle…)
Create a Schema in Logical View
Assign the Schema to a Database
Add Tables, Views, Store Procedures
Create the Relationships between Tables
21. 21 / 26
Create Database
Practice
Create the necessary tables and
relationships of Mr. Delay Software
Company
22. 22 / 26
Maintain Traceability
Steps to Maintain the Traceability
Create Class Diagrams under Use Case
Realization
Drag & Drop the following items to
maintain the traceability
UI (Web Pages)
Classes
Schema
23. 23 / 26
Re-factoring
Definition
The activities to apply changes on previous
results
Guideline
Only create pages, classes, schema that
just realize the current use case, not going
to far.
24. 24 / 26
Code Generation
Rational Rose can generate the
following code
HTML Code
Prototype of Functions
Classes & its functions interfaces
Database schema
25. 25 / 26
Reverse Engineering
Rational Rose can do the reverse
engineering to the code it generated
26. 26 / 26
Summary
Steps for System Design
Realize all Use Cases
Use Sequence Diagrams to get the web
pages, classes, and database schema
Maintain the traceability
Synchronize the models and codes by
round-trip code generation of Rational
Rose