Produce the following for the Withdraw Money expanded use case given below: scenario,
scenario table, informal/analysis sequence diagrams, and design sequence diagrams.
Do all the parts in bold.
Here is the use case:
Here is an example of how scenario part should look like:
Here is an example of how the scenario table should look like(Note: make sure in the withdraw
money scenario table you have all the column headers that the example has-so step #, subject,
subject action, other data/objects, and object acted upon):
Example of how informal/analysis sequence diagrams should look like: UC 2. Withdraw Money
\begin{tabular}{|l|l|} \hline
\multicolumn{1}{|l|}{Precondition::ThisusecaseassumesthatthecustomerhasloggedintotheATM.}
\\ \hline \multicolumn{1}{|c|}{ Actor: ATM Customer } & \multicolumn{1}{|c|}{ System: ATM
} \\ \hline & 0)ATMdisplaystheTransactionSelectionscreen \\ \hline
1)TUCBWcustomerpressestheWithdrawbuttonontheTransactionSelectionscreen. &
2)ATMasksthecustomertoentertheamounttobewithdrawn. \\ \hline
3)CustomerenterstheamountandpressestheSubmitbutton. &
4)ATMdisplaysaconfirmationoftheamountofcashdispensed,anddispensesthecash. \\ \hline
5)TUCEWcustomerpressestheOKbuttonontheconfirmationdialogandgetsthecorrectamountofcash
dispensed. & \\ \hline \end{tabular}
Legend: Subject Spbiect.Action Obiect.ActedUpon Other Required Data or Objects Composition
operator FIGURE 9.10 Marked scenario for a nontrivial step
FIGURE 9.11 Scenario table for the Checkout Document use case
FIGURE 9.18 An informal sequence diagram with a loop
FIGURE 9.22 Checkout Document sequence diagram with formally specified messages.
Produce the following for the Withdraw Money expanded use case given.pdf
1. Produce the following for the Withdraw Money expanded use case given below: scenario,
scenario table, informal/analysis sequence diagrams, and design sequence diagrams.
Do all the parts in bold.
Here is the use case:
Here is an example of how scenario part should look like:
Here is an example of how the scenario table should look like(Note: make sure in the withdraw
money scenario table you have all the column headers that the example has-so step #, subject,
subject action, other data/objects, and object acted upon):
Example of how informal/analysis sequence diagrams should look like: UC 2. Withdraw Money
begin{tabular}{|l|l|} hline
multicolumn{1}{|l|}{Precondition::ThisusecaseassumesthatthecustomerhasloggedintotheATM.}
hline multicolumn{1}{|c|}{ Actor: ATM Customer } & multicolumn{1}{|c|}{ System: ATM
} hline & 0)ATMdisplaystheTransactionSelectionscreen hline
1)TUCBWcustomerpressestheWithdrawbuttonontheTransactionSelectionscreen. &
2)ATMasksthecustomertoentertheamounttobewithdrawn. hline
3)CustomerenterstheamountandpressestheSubmitbutton. &
4)ATMdisplaysaconfirmationoftheamountofcashdispensed,anddispensesthecash. hline
5)TUCEWcustomerpressestheOKbuttonontheconfirmationdialogandgetsthecorrectamountofcash
dispensed. & hline end{tabular}
Legend: Subject Spbiect.Action Obiect.ActedUpon Other Required Data or Objects Composition
operator FIGURE 9.10 Marked scenario for a nontrivial step
FIGURE 9.11 Scenario table for the Checkout Document use case
FIGURE 9.18 An informal sequence diagram with a loop
FIGURE 9.22 Checkout Document sequence diagram with formally specified messages
