Download ArgoUML User Manual - The GNU

Transcript
Requirements Capture
The project must be completed within nine months. It must cost no more than 1,750,000 USD excluding
production costs. Components may be contracted out, but the basic architecture as well as the infrastructure will be designed in house. Close liaison must be maintained between the software development and
the design, development and production of the hardware. Neither the hardware nor the software shall be
considered the independent variable, but rather they shall be considered equal.
4.5.1.7. Appendix
The following are the actors that directly support this vision. Additional actors may be identified later
that are needed to support this or that technology. They should not be added to this list unless they are
deemed to directly support the vision as described in this document.
•
Central Computer
•
Customer
•
Local Branch Official
•
Maintenance Engineer
The following are the use cases that directly support this vision. Additional use cases may be identified
later that are needed to support this or that technology or to support the use cases listed here. They
should not be added to this list unless they are deemed to directly support the vision as described in this
document.
•
Audit
•
Customer Uses Machine
•
Maintain Machine
4.5.2. Identifying Actors and Use Cases
For the ATM case study, we will elaborate on the examples in Section 4.3, “Output of the Requirements
Capture Process”, Figure 4.4, “Use case diagram for an ATM system showing include relationships.”
and Figure 4.5, “Use case diagram for an ATM system showing an extend relationship.”, and progress to
identify additional actors and use cases that comprise our model of the ATM system. Figure 4.4, “Use
case diagram for an ATM system showing include relationships.” and Figure 4.5, “Use case diagram for
an ATM system showing an extend relationship.” exemplified the essential concepts and components of
a use case diagram such as, use cases, actors, multiplicity, and include / extend relationships. They
showed the relationships between the actors and use cases, and demonstrated how these actors and use
cases interact.
In Figure 4.4, “Use case diagram for an ATM system showing include relationships.” we see a use case
diagram for an ATM system consisting of «include» relationships for the use cases, Maintain ATM and
Use ATM. Maintain ATM was further defined by two use cases, "Maintain Equipment" and "Reload
ATM". Use ATM was further defined in terms of the behavior of three simpler use cases: "Deposit
Cash", "Withdraw Cash" and "Query Account".
More to be written...
4.5.3. Associations (To be written)
To be written...
51