|
|
|
Requirements
|
 |
Step 1 of the development process is Requirements Refinement. The purpose of Requirements
Refinement is to create consensus.
Key Points
The chief point in the Software Partners LLC approach to Requirements is to
separate Requirements from Design
This results in a Requirements Phase which passes fairly quickly. This approach gives the
greatest latitude for using design and technology to accomplish objectives in the most
creative way.
Deliverables
The Requirements Refinement process results in a Requirements Document. This is primarily
textual and "list-like" in nature. It may give:
- Background
- Primary reasons for the project
- Major and minor functions which the system must perform
- Number and type of users
- Performance and environmental constraints and factors (example: 7x24 system)
- Calendar time constraints
This document is not lengthy relative to what is produced during design. A three to six month
project may produce a document one to five pages in length.
Appropriate Methodology
Sometimes, Requirements have already been identified and documented by the customer before
project start. In this case, only review of the requirements needs to be done. In other
cases, Software Partners LLC will facilitate the development of a Requirements Document at
project outset through interviews with the appropriate individuals.
Also depending upon the project circumstances, the document may be reviewed by one or many
individuals; and a Requirements Review meeting may or may not be held.
|
|
|
