Software/System Requirements AIM: To create a SOFTWARE/SYSTEM REQUIREMENTS SPECIFICATIONS 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 in time (usually) prior to any actual design or development work. It's a two-way insurance policy that assures that both the client and the organization understand the other's requirements from that perspective at a given point in time. The SRS document itself states in precise and explicit language those functions and capabilities a software system (i.e., a software application, an eCommerce Web site, and so on) must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blueprint for completing a project with as little cost growth as 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 It's important to note that an SRS contains functional and nonfunctional requirements only; it doesn't offer design suggestions, possible solutions to technology or business issues, or any other information other than what the development team understands the customer's system requirements to be. QUESTION: 1. List 3 software requirements of you project that will meet the different types of requirement quality. 2. Create a feasibility assessment and project scheduling of your project
Software/System Requirements
AIM: To create a SOFTWARE/SYSTEM REQUIREMENTS SPECIFICATIONS
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 in time (usually)
prior to any actual design or development work. It's a two-way insurance policy that
assures that both the client and the organization understand the other's requirements
from that perspective at a given point in time.
The SRS document itself states in precise and explicit language those functions and
capabilities a software system (i.e., a software application, an eCommerce Web site,
and so on) must provide, as well as states any required constraints by which the system
must abide. The SRS also functions as a blueprint for completing a project with as little
cost growth as 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
It's important to note that an SRS contains functional and nonfunctional requirements
only; it doesn't offer design suggestions, possible solutions to technology or business
issues, or any other information other than what the development team understands
the customer's system requirements to be.
QUESTION:
1. List 3 software requirements of you project that will meet the different types of
requirement quality.
2. Create a feasibility assessment and project scheduling of your project
Step by step
Solved in 2 steps with 1 images
