Requirement is nothing but a need of the client for this need we will gather all the requirements and transform in to solution. Requirement is the foundation of systems or system components. There are four types of requirements
- Business requirements.
- Stakeholder Analysis.
- Solution requirements
- Functional Requirements
- Non-Functional requirements
- Transition requirements
Business requirement is the goal, objective need of the enterprise. It mainly defines why the project is initiated. These are developed and defined through enterprise analysis.
Stakeholder requirement is the need of the particular stakeholders or department. They provide what exactly they need. It serves as bridge between business requirements and solution requirements. These are developed and defined through requirement analysis.
Solution Requirements defines the solution that meets all the business requirement and also stakeholder requirements. These are categorised as Functional requirements and Non-functional requirements.
Functional requirements define the nature and information that the solution will manage. What should be the information application actions or responses to be provided
Non-functional requirements does not directly depend on the functionality of the solution it depends on which environment it should work, which quality to be provided by the systems. They are also known as quality or supplementary requirements. For example requirements related to capacity, speed, security, availability and the information architecture and presentation of user interface.
Transition Requirements defines the capabilities that the solution must have from transition from current state to future state which is desired, further which is not required once transition is completed. These are different from other requirements as these are temporary in nature which will not be set up until the solution is defined. Single time installation of systems, LAN Connections counters both physically and application and on which website to be used.
As a Business Analyst one should be facilitator between technical team and client not only client with all the stakeholders whomsoever involved in the project. He should be gathering all the requirements from the stakeholders he should do the following in a project
- Gather all the requirements using elicitation techniques
- Document the requirement using industry standards
- Models the requirement using UML
- Communicate the requirements to the technical team
- Tracks the requirement during development stage
- Handle change requests
- Facilitates during UAT(user acceptance testing)
One should always follow 3C-correct, Complete and Consistent though out the project.
As a Business Analyst one should do requirement analysis though elicitation techniques those are
- Document analysis
- Reverse Engineering
- Focus Groups
- JAD(joint application development)
Sorting all the requirements and defining them, prioritizing those requirements through one of the methods:
- 100 dollars test
- Top 10 requirements
- Numerical assignment
- Moscow-Must Should Could Would
Validating all the requirements which ever gathered from the client
- FURPS-Functionality, Usability, Reliability, performance, Supportability
- CUCV-Clarity, understandable, Consistent and verifiable
- CAE- Complete accurate and executable
- APVU-authorised prioritized verifiable and unique
- SMART-Specific, measurable attainable realistic and traceable.