This preview shows pages 1–3. Sign up to view the full content.
This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: <Template last updated 12/21//10> Project Requirements Specification Course: ITEC 455 Business Requirements and Process Analysis Project Name: <your project title> Team Members <team member 1> <team member 2> <etc.> Client Contact Name: <contact name> Professor: J. Alberto Espinosa, Kogod School of Business, American University Last updated: <date last updated> Deliverable Number: <#> Document Revision Number: <#> NOTES: All project documents must have a cover page like this one. Every revision of this document must have all the information shown on this sample cover page. Please remove the word <Template> and all other text within brackets and template instructions (like this one) from your project document. Also, please remove all the blank forms at the end of this document. All this information is for your benefit, but should NOT appear in your own project document. I suggest that you save two copies of this document, one with the full set of instructions, and one in which you delete all the template materials and instructions, which you can use for your own project document. In other words, your final project document should look and read like a real requirements document as you would submit it to a business client. So, it must have a businesslike appearance, including: well formatted graphics and tables, clear and concise text that is readable, informational and free of typos and grammatical errors. The sections in the document must be numbered (consistent with this template) to facilitate communication with your client (and your professor) about the specifics of your document. <Your Project Title > Table of Contents 1. Introduction System Concept 2. Project Vision 3. Stakeholders System Requirements 4. System Actors 5. Scope of Work 6. Functional Requirements 7. Non-Functional Requirements 8. Mandated Constraints 9. Relevant Facts and Assumptions Database Design 10. Data Objects 11. Relationships Between Data Objects 12. Sample Queries 18. Data Model Appendices A. Glossary of Terms and Acronyms B. Actor Cards C. Scope of Work: C.1. Business Process Model C.2. Context Diagram D. Use Case Diagram E. Transitional Matrix: BPM and Use Cases F. Use Cases: Functional Requirements G. Transitional Matrix: CRUD Matrix H. Information Model <Your project specification document must contain a table of contents in the second page, right after the cover page. Your table of contents must be numbered and the numbers must match the numbers of the corresponding sections. I suggest using page numbers in the document, but not in the table of contents because they will change frequently (unless you use the outline feature that maintains the table of contents automatically). It always helps to tell the reader what they should expect to find in the document. It is very hard to read a document when there is no roadmap upfront because you dont know what to expect.> <Please note that several sections of this template have been adopted and adapted from the...
View Full Document
This note was uploaded on 12/21/2011 for the course ECON 3014 taught by Professor Michaelshaw during the Spring '11 term at HKU.
- Spring '11