An SRS is basically an organization's understanding (in writing) of a customer or potential client's system requirements and dependencies at a particular point intime (usually) prior to any actual design or developmentwork. It's a two-way insurance policy that assures that boththe client and the organization understand the other'srequirements from that perspective at a given point intime.
The SRS document itself states in precise and explicitlanguage those functions and capabilities a software system(i.e., a software application, an eCommerce Web site, and soon) must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blue print for completing a project with as little cost growt has possible. The SRS is often referred to as the "parent" document because all subsequent project management documents, such as design specifications, statements of work, software architecture specifications, testing and validation plans, and documentation plans, are related to it.
No comments:
Post a Comment