| < Day Day Up > |
|
The PRSpec encompasses a set of required deliverables that describe in great and exacting detail precisely what the customer will receive when the completed product is made available. Every single function, command, screen prompt, dialog, and other user-interface-related item is documented in this group of specifications. Much of the information in this document can be expanded from the High-Level Solutions Document. The four key specifications documents required at this stage include the following:
System Infrastructure Requirements
Software Requirements Specifications
Interface Requirements Specifications
Performance Requirements Specifications
The various requirements specifications documents listed are intended to ensure that a well-conceived and copiously detailed breakdown of the proposed solution is completed by the various Core Team members and other participants of the project development process.
In the course of gathering and building a requirements document, it is often necessary to review existing documentation/software. A Requirements Analysis Team may be tasked to analyze the problem domain and conduct customer interviews or even to conduct one or more user surveys. The Requirements Analysis Team must identify and evaluate reusable system components and work with the local IT or MIS organization to determine the type of host platform required. The team must also determine what platform features will be used to implement security safeguards.
Additionally, the following are some other general areas to take into consideration for analysis when deriving user requirements.
Architecture
Audience
Commands
Compatibility/migration
Competitiveness
Deviations from requirements
Ease of use
Functions
Future enhancements
Hardware supported
Information/data to be included
Internationalization requirements
Packaging
Performance
Pricing/license agreements
Publications
Reliability
Screen layout
Security
Serviceability
Software supported
Standards/ISO compliance
User interfaces
In the following paragraphs, we cover each of the four key specifications documents and discuss why each is important in the project execution process.
| < Day Day Up > |
|