What Is Requirement ?
q A capability that the system must deliver
q A capability needed by the user to solve a problem to achieve an objective
What requirement Are Not ?
q project planning information
q design or implementation details or
q testing information
Why Requirement Analysis ?
The earlier in the cycle the defect is corrected
q Cost
q Delay
q Profit
q Customer satisfaction
q Customer confidence
Type of Requirement
Business Requirement
Business requirements represent a kind of "why" information. It represent the high level of objectives of the organization or customer who requests the system. Business requirement why the organization is implementing the system. Vision and Scope statement record the business requirement.
User Requirement
requirements constitute one type of "what" information. User requirements describe what the user will be able to do with the product, such as goals or tasks that users must be able to perform. Use cases, scenarios, user stories, and event response tables are some ways to represent user requirements.
Functional Requirement
Functional requirement specify the software functionality that the developer must build into the product to enable the user to accomplish their business requirement . Functional requirements represent one kind of "what" information. The traditional "shall" statements that describe what the system "shall do" or what the system "shall let the user do.“
System Requirement
Describe the top level requirement for a product that contain multiple subsystem that is a system. A system can be all software or it can be both software and hardware.
Components of requirement Engineering
Entire Software requirement Engineering domain is split into requirements development and requirements management.
Requirement Development
The purpose of requirement development is to produce and analyze product and product component requirement. The goal of requirements development is to identify, agree and record a set of functional requirements and product characteristics that will achieve the stated business objectives.
Requirement Management
The purpose of requirement management is to manage requirments of the projects products components and to identify inconsistencies between those requirments and the project’s plan and work product.
The central purpose of requirements management is to manage changes to a set of agreed-upon requirements that have been committed to a specific product release. Requirements management also includes tracking the status of individual requirements and tracing requirements both backward to their origins and forward into design elements, code modules, and tests.
No comments:
Post a Comment