Chapter 2: The Requirement Process ( Duy Anh Tran )
The Volere Requirements Process is the way to get you from the business problem all the way to atomic functional and non-functional requirements.
Business Requirements are an essential part of project success and a key responsibility for the Business Analyst. A requirements something the product must do to support its owner's business, or a quality it must have to make it acceptable and attractive to the owner. A requirement exists because the type of product demands certain functions and qualities, or because the client asks for that requirement to be part of the delivered product.
The most common objectives of the Business Requirements are:
- To gain agreement with stakeholders
- To provide a foundation to communicate to a technology service provider what the solution needs to do to satisfy the customer’s and business’ needs
- To describe what not how the customer/business needs will be met by the solution
Functional Requirements: Its definition is that it essentially specifies something the system should do.
Some typical functional requirements: Business rules, legal or regulatory requirements, administrative functions.
Non-functional Requirements: It covers all other remaining requirements. They specify the operation of a system, rather than their specific behaviors. For example: performance, security and usability can be some of the typical non-functional requirements.
Formality guide: Rabbit, Horse and Elephant.
Comments
Post a Comment