- Requirements: – Need of the client which is dynamic and eventually transform into a solution and defines how the project is supposed to be created and implemented. There are 4 types of requirements.
Business Requirements – High level document which has objectives & goals of the project & it is shared by Business owners. Eg – BRD & FRD
Stakeholder requirements – User stories requirements from Clients (Specific need of the Client) which has in depth information about the requirements. Eg – URD
Solution Requirements – These are the requirements offering the solution for business requirements and stakeholder requirements like the software /solution which we prepare & is divided into two types (Functional (Developers) & Non Functional requirements (Other actors)
- Functional Requirements: – It defines the functionality of the systems & describe external behavior of the application and expected deliverables such as functionality and capabilities of an application.
- Non Functional Requirements: -It is prepared by system analyst & defines how the application is interacted with the system hardware such as operating speed ,response time, Accessibility, Security, Reusability ,Tack time.
Transition Requirements –It defines the activities that are necessary for moving solutions out of development and into real-world business use-deployment. It is used at the time for Training, Setup, deploy & Install for end-user.
Different types of Elicitation techniques: –
Brainstorming – It is done between the groups (Clients & users) to discuss about new ideas or requirements which can be included in the system requirements.
Documentation – Reading the text of the particular product or project. Eg User manuals ,BRD,FRD,MOM,SOP and can provide details for the new system requirements.
Reverse engineering – It is trial and error base method & to understand what systems does.
There are two types of reverse engineering technique
Black box & white box reverse engineering technique
Focus groups – Generally these users are going to use our project may be aware or not aware of the projects FGD -Focus Group Discussion. There are two types of focus groups
Homogeneous & Heterogeneous focus groups.
Observation – In this technique requirements are collected by observing for users & Clients. It helps is providing information from current process. There are two types of observations active & passive
Workshop – It consists of groups of users & Clients to identify requirements. It is conducted by Client. It is one of the effective way to delivery requirements early.
Prototyping – It is Screen mockups process & helps In identifying gaps /problems in the requirements.
Interview – In this technique Structured and unstructured questions are asked by business analyst to have more clarity on the requirements. Eg Open and closed ended question.
JAD (Joint Application Development) – It is conducted between top management, authorities from different team & users who are involved in the project to gather information’s.
Questioner / Survey – It is used to collect information/requirements from large group of stake holders & it can be collected remotely. The questioner should be user friendly to answer.