Requirements Specification is a description of what you want the system to do. This document may also be called a Business Needs Specification. The Requirements Specification should generally not be written in computer terms or contain assumptions about how the system should be written (unless these are part of the requirements). Requirements Specification should cover topics like:
1.Introduction: Your introduction, location, your market and target customers, contact details and the service your offer.
2.System Overview: Potential users of the system, number of users, kind of users according to their work, the problems they face, hardware and environmental constraints etc. This also includes the deliverables, business rules that needs to be included in the system, back up for the system, security needed for the system, technical support required.
3.Functional Requirement: This includes your requirements, importance of the requirements, design or implementation issues.
4.Data to be held: The kind of data that the system should held
5.Operational Scenario: The kind of scenarios that an user might face while using the system.
6.Budget and Schedule: Timescale required, management constraints, critical deadlines and the budget.
7.Appendices and Contact Number: Any acronyms or abbreviations.
Friday, May 11, 2007
Subscribe to:
Posts (Atom)
