Tuesday, February 15, 2011

Requirements Engineering (1)

One of the main things about delivering the product is identifying the required product. t is also quite important to identify them as soon as possible because the late correction of errors could cost upto 200 times more. Poor requirements is a major source of problems.

Before identifying the requirements, let’s see what requirements are,
• A specification of what should be implemented
• How the system should behave
• Constraint on the development process
• System properties or attributes

Requirements can be classified as the following,

• Functional Requirements- define functionality
• Implementation requirements-how to implement system
• Performance Requirements-specify minimum acceptable performance
• Usability Requirements- specify the maximum acceptable time to demonstrate the use of the system

In eliciting the above mentioned types, it is needed to identify the business / technical stakeholders. Sometimes it maybe difficult to get user input and involvement. In coming to agreements with the requirements it will be easy if the requirements have been put to understandable form. Preparing proper requirements specification with the collected requirements and sticking to them throughout reduces software defects.

The business value of requirements is huge. Unclear requirements may lead to rework and make the project cost unnecessarily large.

No comments:

Post a Comment