Requirements Engineering
Bread Crumbs: Home - SW_Dev_Proc
- Req Engr
Requirements
engineering assesses the feasibility of a project and if deemed
feasible, gleans precise and accurate requirements which, when
fulfilled, culminate in the correct system for the customer.
It is important to build the correct system correctly and that cannot happen without defining accurate, precise, and valid requirements. Requirements must be accurate in that they must capture the actual meaning of customer inputs and not attempt to interpret or embellish those inputs. Requirements must be precise in that if a customer says they want a certain detail, say temperature displayed in degrees Fahrenheit, it is important to deliver that detail. Don't assume that degrees in Celsius should be just as good. That is not precisely what the customer wanted. Requirements must be valid. If the customer wants a microwave oven controller system that is cost-effective but adequate, do not provide a controller system that is leading edge with functionality beyond what was desired and then expect to charge the customer for budget overruns. All of the requirements that led to the "gold-plating" were invalid. Building an incorrect system correctly is still total failure.
The end result of the requirements engineering activities is a populated System Requirements Specification (or SRS) and a completed System Specification.
It is important to build the correct system correctly and that cannot happen without defining accurate, precise, and valid requirements. Requirements must be accurate in that they must capture the actual meaning of customer inputs and not attempt to interpret or embellish those inputs. Requirements must be precise in that if a customer says they want a certain detail, say temperature displayed in degrees Fahrenheit, it is important to deliver that detail. Don't assume that degrees in Celsius should be just as good. That is not precisely what the customer wanted. Requirements must be valid. If the customer wants a microwave oven controller system that is cost-effective but adequate, do not provide a controller system that is leading edge with functionality beyond what was desired and then expect to charge the customer for budget overruns. All of the requirements that led to the "gold-plating" were invalid. Building an incorrect system correctly is still total failure.
The end result of the requirements engineering activities is a populated System Requirements Specification (or SRS) and a completed System Specification.
