Date:
Version: V2 - description of EZWallet in FUTURE form (as proposed by the team)
| Version number | Change |
|---|---|
EZWallet (read EaSy Wallet) is a software application designed to help individuals and families keep track of their expenses. Users can enter and categorize their expenses, allowing them to quickly see where their money is going. EZWallet is a powerful tool for those looking to take control of their finances and make informed decisions about their spending.
| Stakeholder name | Description |
|---|---|
| Stakeholder x.. |
<Define here Context diagram using UML use case diagram>
<actors are a subset of stakeholders>
<describe here each interface in the context diagram>
<GUIs will be described graphically in a separate document>
| Actor | Logical Interface | Physical Interface |
|---|---|---|
| Actor x.. |
<A Persona is a realistic impersonation of an actor. Define here a few personas and describe in plain text how a persona interacts with the system>
<Persona is-an-instance-of actor>
<stories will be formalized later as scenarios in use cases>
<In the form DO SOMETHING, or VERB NOUN, describe high level capabilities of the system>
<they match to high level use cases>
| ID | Description |
|---|---|
| FR1 | |
| FR2 | |
| FRx.. |
<Describe constraints on functional requirements>
| ID | Type (efficiency, reliability, ..) | Description | Refers to |
|---|---|---|---|
| NFR1 | |||
| NFR2 | |||
| NFR3 | |||
| NFRx .. |
<define here UML Use case diagram UCD summarizing all use cases, and their relationships>
<next describe here each use case in the UCD>
| Actors Involved | |
|---|---|
| Precondition | <Boolean expression, must evaluate to true before the UC can start> |
| Post condition | <Boolean expression, must evaluate to true after UC is finished> |
| Nominal Scenario | <Textual description of actions executed by the UC> |
| Variants | <other normal executions> |
| Exceptions | <exceptions, errors > |
<describe here scenarios instances of UC1>
<a scenario is a sequence of steps that corresponds to a particular execution of one use case>
<a scenario is a more formal description of a story>
<only relevant scenarios should be described>
| Scenario 1.1 | |
|---|---|
| Precondition | <Boolean expression, must evaluate to true before the scenario can start> |
| Post condition | <Boolean expression, must evaluate to true after scenario is finished> |
| Step# | Description |
| 1 | |
| 2 | |
| ... |
..
..
<use UML class diagram to define important terms, or concepts in the domain of the application, and their relationships>
<concepts must be used consistently all over the document, ex in use cases, requirements etc>
<describe here system design>
<must be consistent with Context diagram>
<describe here deployment diagram >