Академический Документы
Профессиональный Документы
Культура Документы
1. Identify the users/actors (Chapter 6): 6. Apply design axioms to design classes, BankC lien t
#firstName : Strin g
#las tName :S trin g
ATMMac hin e
#a ddre s : Strin g
#sta te : Strin g
+v er ifyPassword()
Account
+withdra w()
#retrie veAccount()
#updateA ccount()
No
Si t
Read som ew here
user requirements
representation of methods
insuf icient f unds
ac count
algorithm
su f icie nt fun ds ac o unt
SavingsAccount.withdraw
withdraw using SavingsAccount.balance -
SavingsAccount (anAmount -
method CheckAc ount.balance))
3. Develop the use case (Chapter 6): associations between classes returnCode=
"OK"
returnC ode
="Insufficient
funds"
What are (or wil be) the users are 6.1.4 Refine (if required) class
doing with the system? hierarchy and design with
inheritance Design methods by
Use cases provide comprehensive
util zing UML Activity
documentation of the system under 6.2 Iterate and refine (reapply Design
Diagram
study axioms).
Use case diagrams
Use cases capture the goal of the
Business Cla sses
1
Has
Cancel OK
1.
Transaction
*
Access Class(es)
Account #transID :String
Create the forms and controls
4. Interaction diagrams
BankDB
#transaction: Transaction 1 #amount:f loat
#postBalance: float
Enter title here
#bankDB: BankDB
#account : Account
+deposit()
+re trie ve Client() +with draw() As sociat e act ions
(Chapter 7)
Bank Cli ent AT M Mach in e Acco unt Checki ng Acc ount
+updateSavin gsAccount() #updateAccountt () Interface cont rols
+retr ieveCheckingAccount() an dth eirevent s
+updateCheckingAccount()
diagrams
-updateAccountt () -updateAccountt()
4.2 Develop
En te rKin d
Reque stAmount
collaboration diagrams.
Trans actio n suc e d Withdra wSu c es sfu l
Dis pens e Ca sh
col aboration diagram Sequence diagram 8. Designing view layer classes (Chapter 12)
Prototype user interface
8.1 Macro-level UI design Process- Identifying View layer Objects
8.2 Micro-level UI design activities:
5. Classification (Chapter 8) 8.2.1 Designing the view layer objects by applying design Is easy to operate:
How do yo u ra te the ViaNet Bank ATM Kiosk Interface?
Class diagram
Very ea sy
reco very Not at al
Comments:
The process of creating sequence or collaboration diagrams is a Iha ve mo re to sa y,Iwoul d li ke to see you.
systematic way to think about how a use case can take place, and by 9. Iterate and refine the design/analysis: If needed repeat the preceding Usability and user
doing so, it forces you to think about objects involves in your steps
application satisfaction testing
Analysis Design
ViaNet Bank ATM
1. Identify the users/actors (Chapter 6): 6. Apply design axioms to design classes,
Who is (or will be) using the system? their attributes, methods, associations,
structures, and protocols (Chapter 9)
6.1. Refine and complete the static
UML class diagram (object model)
2. Develop a simple business by adding details to the UML class
Chec
Member #saving
comes in Retu rn
Go to counter
Checkin g
Go to counte r
Yes and return th e Done? Yes and check out
Book? out Books?
book the book
No
Sit
Read somewhere
user requirements
representation of methods
using activity diagram
algorithm
suffi
What are (or will be) the users are 6.1.4 Refine (if required) class
doing with the system? hierarchy and design with
inheritance Design
Use cases provide comprehensive
utilizing
documentation of the system under 6.2 Iterate and refine (reapply Design
study axioms).
Use case diagrams
Use cases capture the goal of the
users and the responsibility of the 7.0 Design the access ayer (Chapter 11)
system to its users 7.1. Create maccess layer classes by
mirroring the business classes Access Class(es)
+ret rieveClient()
(Chapter 7)
Bank Cli ent ATM Machine Account Checking Account
+updateSavin gs Acco unt()
+retrieveCheckingAccou nt()
+updateCheckingAccount()
Request Amount
Enter Amount
7.4 Iterate and refine UML
Process Transacti on
with
Wit hdrawChecking Account
collaboration diagrams.
Transaction succeed WithdrawSuccessful
Dispense Cash
collaboration diagram Sequence diagram 8. Designing view layer classes (Chapter 12)
8.1 Macro-level UI design Process- Identifying View layer Objects
8.2 Micro-level UI design activities:
5. Classification (Chapter 8) 8.2.1 Designing the view layer objects by applying design
5.1 Identify Classes axioms and corollaries
8.2.2 Prototyping the view layer interface.
1
Class diagram
The process of creating sequence or collaboration diagrams is a
systematic way to think about how a use case can take place, and by 9. Iterate and refine the design/analysis: If needed repeat the preceding
doing so, it forces you to think about objects involves in your steps
application