I N T R O D U C T I O N
Understanding the user's real requirements, rather than their requirements as perceived by the IS developer, is absolutely critical to the development of successful information systems.
To achieve a high level of IS quality (user-friendliness), it is essential that the statement of user requirements be developed in the correct way. If this is done, the software that is produced will meet the user's needs, and will lead to user satisfaction. If it is not done, the software is likely to not meet the user's requirements, even if the software conforms with the specification and has few defects.
How to Capture IS User Requirements is an easy to use, step-by-step procedural guide to developing high quality, effective statement of user requirements for information systems. It contains the following topics:
An outline of the requirements capture process
Developing the Requirements List (RL)
Developing the Statement of User Requirements
Developing the Interface Control Document (ICD)
Developing the Software Requirements Specification
How to Capture IS User Requirements relies on the proven methods outlined in IEEE Std 830-1984 Guide to Software Requirements Specifications and IEEE Std P1233 - 1992 Guide for Developing System Requirements Specification. It is written in 'plain English' and contains added features to enable project staff with average literacy skills to effectively develop a comprehensive statement of user requirements.
W H A T C A N Y O U A C H I E V E ?
With this comprehensive guide to the preparation of the requirements capture documents, you will learn how:
the Requirements List is produced by the customer to effectively describe the features and capabilities required by a proposed system.
the Statement of User Requirements document is developed, based on the Requirements List.
content is developed.
the Requirements List and Statement of User Requirements are formatted.
the Review/Approval process is performed.
By using How to Capture IS User Requirements you can achieve the following.
to achieve consistency across Requirements Lists which are derived from different sources. The resulting consistency allows for a more objective assessment of the requirements.
a statement of user requirements which can be effectively used as the basis for the development of a detailed user requirement specification.
project staff have the means to identify and follow the processes involved with the Requirements Capture Process.
to furnish a guide to the format and contents of the Requirements List.
How to Capture Software User Requirements
Plain English guide based on IEEE Std 830
Publication date: 22/04/2011
Practical guide for software development project managers and staff
El vendedor asume toda la responsabilidad de esta entrada.