Information Technology Reference
In-Depth Information
Use case writing process:
1. Name the system scope.
2. Brainstorm and list the primary actors.
Find every human and non-human primary actor, over the life of the system.
3. Brainstorm and exhaustively list user goals for the system.
4. Select one use case to expand.
Consider writing a narrative to learn the material.
5. Write the main success scenario (MSS).
Use steps 3 to 9 to meet all interests and guarantees.
6. Brainstorm and exhaustively list the extension conditions.
Include all that the system can detect and must handle.
7. Write the extension-handling steps.
Each will end back in the MSS, at a separate success exit, or in failure.
8. Extract complex flows to sub use cases; merge trivial sub use cases.
Extracting a sub use case is easy, but it adds cost to the project.
9. Readjust the set: add, subtract, merge, as needed.
5.7 The Software Requirements Specification Document
Software Requirements Specification (SRS) consists of a complete description of
the external behavior of the software system. SRS could be written by a potential
user of a system or a developer of a system. The two scenarios create different
situations.
The following is a SRS template:
1. Introduction
This section provides an overview of the entire requirement document. This
document describes all data, functional and behavioral requirements for software.
1.1 Goals and Objectives
1.2 Statements of Scope
1.3 Software Context
1.4 Major Constraints
