- Click here to view the complete Table of Contents. This gives you an indication of the scope and level of detail of this document.
Note formatting may be affected in conversion from Word to HTML.
How to Capture IS User Requirements
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 Obtaining Sign-offHow 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.
A B O U T T H E A U T H O R
How to Capture IS User Requirements was written by David Tuffley, who combines a successful career as a technical communication and quality management consultant with academic involvement at the School of ICT, at Griffith University, Australia, where he is doing postgraduate research in IS Quality.
See Client list.
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.
V I E W T A B L E O F C O N T E N T S
D O W N L O A D - F R E E - U S E F U L - S A M P L E S
Two brief (~10 pages each) how to guides can be downloaded for free. They are zip files containing rtf & pdf copies of the documents.
They are useful and relevant to any software development project and are intended to give prospective buyers of the full featured range of TCS how to guides an indication of their quality and usefulness.
Click here to download How to Perform Risk Management (.docx format).
Click here to download How to Perform Project Estimates (.docx format).
O R D E R Y O U R C O P Y N O W
This guide, proven over the past fifteen years at large commercial and public sector sites, could save you thousands of dollars in consultancy fees. Or put it another way, you could not buy even an hour of a good consultant's time for the price of this valuable How To guide. Yet consultants routinely spend weeks or months implementing procedures similar to those contained in this guide.
Ordering your copy of this excellent How To guide for only US$24.95 is easy. Buy It
Transaction Record. Your credit card transaction will be processed using the latest secure processes by CCNow (TCS's authorized online retailer). Your credit card transaction statement will show CCNow.
Delivery Information. You will receive a download link by email soon after you place the order. The download contains the deliverables in MS Word (.docx) and PDF. The documents are your master copy.
How to Use the Documents. Save the master as a working document. Read the reference text that details what needs to be written, and to what level of detail. Then write what needs to be written, and delete the reference text, leaving the completed document. The structure is embodied in the template. Documents can be converted to HTML for intranet/internet delivery if desired, using your wordprocessor's inherent HTML conversion capabilities, or by using proprietary conversion software that builds contents hierarchies that greatly facilitates navigation. Contact TCS for more information.
Transaction Record. Your credit card transaction will be processed using the latest secure processes by CCNow (TCS's authorized online retailer). Your credit card transaction statement will show CCNow.
O T H E R T C S P U B L I C A T I O N S
Client list Complete Library (all of the below + 19 extra) 
User Manuals Software Requirements Specifications Capture IS User Requirements Software Test Documentation Software Design Descriptions Configuration Management Plans Version & File Software Development Documentation Software Project Agreements Software Project Plans Software Quality Management Plans Software Project Review & Audits Software Project Terms of Reference Perform Software Project Metrics Initiate Software Projects Software project procurement & handling client supplied materials
R E T U R N T O T C S H O M E P A G E
Site design by David Tuffley.