(4.5) Using the technique suggested here, where natural language descriptions are presented in a standard format, write plausible user requirements for the following functions:
• The gas pump system shall be unattended.
• The gas pump system shall have a credit card reader (The pump system must have a card reader to ensure the system is functional when unattended),
• The gas pump system shall ask for a specified amount of fuel after customer swipes their card.
• The gas pump shall debit the customer account after fuel is delivered (Customers account should be charged after the system verifies the fuel has been delivered to avoid a scenario where the system charges the customers account, but has less fuel available to deliver than the customers specified amount).
• The cash-dispensing machine shall be a bank ATM.
• The internet banking system should allow customers to transfer funds between accounts hosted by the bank.
(4.6) Suggest how an engineer responsible for drawing up a system requirements specification might keep track of the relationships between functional and non-functional requirements.
Requirement specification is defined as the process of formally documenting the requirements of the software, user and system. An engineer can track of their functional and non-functional requirement relationships by using an appropriate Unified Modeling Language such as use cases.
(4.7) Using your knowledge of how an ATM is used, develop a set of use cases that could serve as a basis for understanding the requirements for an ATM system
ACTOR: USER
ACTOR: BANK_SYS.
- USER (inserts card) —> enter pin —> enter withdraw amount
- USER (inserts card) —> enter pin —> choose deposit account
- BANK_SYS —> validate pin
- BANK_SYS—> validate withdraw/deposit specified amount
- BANK_SYS —> verify pin —> dispense/retrieve specified amount
No comments:
Post a Comment