Software Requirements for project name
(NB: replace all blue in template with black) Client : Name 1 Architect: Name 2 Date
1. Introduction
Describe the purpose of the document and give a brief overview
2. Use Cases
Describe the intended uses of this system. For example, here is a template you may use for the use case:
For each intended use, at minimum you must provide:
• • • Name - This should be a short phrase expressing a user's intention The main scenario, including the behavior of all actors (users, other systems, etc.) as well as the behavior of the system. This should be specified as a numbered list of steps. Alternative scenarios, such as error cases or extensions
3. Features
Describe each of the main features of the system. For each feature include: • Name • Brief description • Expected value to user or customer For example, here are 2 features of the ATM: 3.1. Quick Picks a. Description: The user may choose one of a few frequently-used transactions, like withdrawal of $50 from their checking account, from a top-level menu. b. Expected Value: Users of the ATM will be more inclined to use the machine, with expected increased revenue of $100 in transaction fees per month. 3.2. Secure Transmission a. Description: All communication between the ATM and the host bank will be secure from eavesdropping or tampering. b. Expected Value: Customers of the ATM will be more included to buy the machine, as it will prevent potential loss from hackers (and subsequent lawsuits). Customers should be willing to pay 100% more for a secure system than an insecure system.
4. References 5. Appendices
If you have other material you want to include, place it here. For example, you might include a glossary of technical terms and abbreviations.
Include citations here. Use a standard format, such as IEEE (http://standards.ieee. g ) or /guides/style/section7.ht
6. Effort
Report the amount of time (in hours) spent on this deliverable by Client and Architect: Name 1: X hours Name 2: X hours