Requirement is equal to Business analyst is a popular equation.Requirement is an integral part of business analyst’s roles and responsibilities.
There are many terminologies which describes a requirement.The BCS (British computer Society),The Chartered Institute for IT defines a Requirement as:
- A statement of need
- A condition to solve a problem or to achieve an objective
- A function that system does
- A constraint (Business, User, System, Technical, Project)
Requirements are the fundamental building blocks for every project to all organizations. Customer needs, operational needs, technology needs will get converted into Business Requirements, stakeholder Requirements, Solution Requirements, Functional and non functional Requirements.
Importance of Requirements
Requirements are considered by numerous experts to be the major non-administration, non-business reason ventures don’t accomplish the “magic triangle” of on-time, on-spending plan, and high caliber. Various studies have shown that every project succeeds or fails on the quality of its requirements. Requirements are crucial to each project as they set the scope of all subsequent work and convey project team that what is the actual need. Teams need to perform a much better job during requirement phase only if they wish to develop a quality solution on time and within budget. The cost of correction of requirements is high when system is already in operation rather than correcting it at the early stage of project.
Furthermore, the hardest part in this phase is, a business analyst does not know what questions to ask and stakeholder is unaware about what information the Business analyst needs. This phase is where business and information technology meets each other. Business team and IT team tend to speak different languages. We tend to speak and write in a format that makes English as a more ambiguous, unclear language.
A logical grouping of requirements by its common functions, features and attributes is nothing but the types of requirements. Broadly requirements are categorized into:
Business level / General Requirements – general or business requirements refer to business policies that are elaborated and expanded in the non-functional and functional requirements. These are critical activities of an organization that must be performed to meet the enterprise objectives.
User / Stakeholder Requirements – This type of requirements are gathered and written from stakeholder’s point of view. Stakeholder requirements describe the how user wants to interact with the proposed solution. These are often treated as mid level requirements between general requirements and solutions requirements
Solution Requirements – Solution Requirements are further classified into Functional and non- functional requirements.
Functional Requirements usually describes what the system must do; the capabilities, behavior and information about system or solution. Processing the inputs, data entry and retrieval type of statements classified under this group.
Non – functional Requirements are also called as quality of service requirements. Usually these requirements define the attributes of the system functions. Usually these requirements describe the conditions and constraints under which solution must operate.
Transition or implementation Requirements – These requirements define the capabilities or behavior of the solution for transitioning from current state or situation to a desired state. After implementation these requirements will no longer required.
BCS, The Chartered Institute for IT Tips for writing standard requirements:-
- Requirements should be clear
- Requirements should be concise
- Requirements should be Consistent
- Requirements should be Relevant
- Requirements should be Testable
- Requirements should be Traceable
To know more on Requirements and Requirements Engineering keep following our blogs………..