Table of Contents
SHOULD YOU READ THIS PAPER? WHAT IS A REQUIREMENTS DOCUMENT? WHY BOTHER WITH A REQUIREMENTS DOCUMENT? DO I HAVE TO WRITE A REQUIREMENTS DOCUMENT? WHO USES THE REQUIREMENTS DOCUMENT AND WHY? GENERAL PRINCIPLES IN WRITING A REQUIREMENTS DOCUMENT SECTIONS OF A REQUIREMENTS DOCUMENT PART I – APPLICATION OVERVIEW PART II – FUNCTIONAL REQUIREMENTS PART III – APPENDICES 3 3 4 5 5 6 9 10 12 15
WHO NEEDS WHAT? SUMMARY OF PURPOSE AND USAGE OF THE SECTIONS OF THE REQUIREMENTS DOCUMENT 17 HOW TO GET OTHERS TO READ THE REQUIREMENTS DOCUMENT? REFLECTING CHANGES IN REQUIREMENTS DOCUMENTING REQUESTS FOR ENHANCEMENTS TRACING REQUIREMENTS CONCLUSION AND FURTHER READING AUTHOR …show more content…
Requirements document states what the software will do. It does not state how the software will do it.
What the software does is directly perceived by its users – either human users or other software systems. When a user performs some action, the software responds in a particular way; when an external system submits a request of a certain form, it gets a particular response. Therefore you and the users must agree on actions they can perform and response they should expect. This common understanding is captured in the requirements document. How the software responds to the agreed upon request is not addressed in the requirements document. For example, the requirements document does not include screen layouts, database schemas, descriptions of communication layers – in short, no statements of design of any sort. For example, it is a requirement for a word processing application to be able to open an existing file. It is a design issue whether to build a customized file selection tool or use a platformstandard file selection tool. This is not to say you won’ seek users’input on some of the design, most t especially on user interface design, but it is very important to recognize and
By: Tanya Berezin Modified: June 14, 1999 Document: Writing a Requirements Document File Name: C:\My