File Upload (Developer Guide)
From UG
(Difference between revisions)
(→"Abnormal" Functionality (Test Cases)) |
|||
| Line 21: | Line 21: | ||
=== "Abnormal" Functionality (Test Cases) === | === "Abnormal" Functionality (Test Cases) === | ||
* '' List unusual scenarios - things that users most of the time would not do but system must handle well '' | * '' List unusual scenarios - things that users most of the time would not do but system must handle well '' | ||
| + | |||
| + | == Figures == | ||
| + | === Figure 1: === | ||
Revision as of 21:52, 5 February 2010
Contents |
Notes from Systems Architect
- This section is defined by Systems Architect. It is written after #Business Requirements are defined.
- The purpose of this section is to give direction to System Analysts who will write detailed specification.
Rapid Design
- In some cases (component is non standard) we need to do preliminary not so detailed design before detailed final. And maybe even code it to create Prototype
- This section does not have to be too detailed or too formalized. We shall not spend too much time on Prototypes - they can change many times.
Detailed Design
- This section is defined by Systems Analyst.
- It contains detailed technical design is written after #Business Requirements and #Technical Requirements are defined.
Summary
User Interface
"Normal" Functionality (Use Cases)
"Abnormal" Functionality (Test Cases)
- List unusual scenarios - things that users most of the time would not do but system must handle well
