Elicitation Techniques: Elicitation include -Document Analysis – Reverse Engineering – Focus Groups- Observations –Workshops – JAD (Joint Application Development) – Interview – Prototyping – Survey/ Questionnaire – Brainstorming – Use Case Spec
Document Analysis : Document analysis is done through reading a document and understanding the project requirements , as well as the process implemented. When the project is started the stake holder will share the functionality, process documents, some this it can be series of mail exchange, minute of meetings , When you read any text you understand about the process product or project then it called as a Document Analysis.
Reverse Engineering: In situations where software for an existing system is outdated and its necessary to understand that what the system actually does.
Reverse engineering, also called back engineering
Reverse-engineering is generally done for migration projects. For ex. – from. Net to Oracle
There are two general categories of reverse engineering
1. Black Box Reverse engineering – the product is studied without examining its internal structure.
2. White Box Reverse engineering – The inner working of the system / product are studied
Focus Groups: A need to study an existing idea, solution or process. Purpose of this technique is Improve existing ideas.
Observations – Observing that what is users doing a part of their job, can provide information of existing processes, inputs and outputs.
Passive observation: In this approach a business Analyst observe the stake holder / SME throughout the business routine but does not ask the question. BA will wait till the entire process is completed before asking the questions.
Active observation: In this approach business Analyst observe the current process and take the notes , he/ she may dialog with the stakeholder, once the stake holder is allowing to ask the question BA will ask the questions to his it’s called as active Observation
JAD (Joint Application Development) – JAD (Joint Application Development) is a methodology that involves the client or end user in the design and development of an application.
We can use this technic for Technical Project. ex. Networking project , DP Project , Testing Project. We can use this technic for Technical Project. ex. Networking project , DP Project , Testing Project
Interview – Interview of a user and stakeholders are important in creating software. An interview is a systematic approach where interviewee is going to ask relevant questions related to software and documenting the responses.
As a Business Analyst after gathering the requirement the next step to sort the requirements, while sorting the requirement we realized that there is some conflicts in the requirements and few requirements are contradict with other requirements, in such a case we can take appointment with the respective stake holders and then we will ask questions on our observed conflicts and they clarified that.
To conduct an interview there is 2 approaches
Structured Approach means whatever question we want to ask will asked one after other and note down the answers that called structured Approach. (Based on Predefined Questions)
Unstructured Approach means we know what the problem is? , what the concept is?, once we meet the stakeholder we ask them the question on it and they answer on it , On based on the answer we will ask the next questions that approach we called as Unstructured Approach. (Bases on the Respond of Stake holder)
Survey/ Questionnaire – In case the more no of stake holders and we can’t get the opinion of every one in that case we chose these Questionnaires / Survey forms. It’s just like a feedback form, is have multiple chose answers, its mostly like rating or predefined values (poor/ fair / good). Once will get the feedback we can use statistical tool to measure it.
A questionnaire is a list of questions or items used to gather data from respondents about their attitudes, experiences, or opinions. Questionnaires can be used to collect quantitative and/or qualitative information.
Questionnaires are commonly used in market research as well as in the social and health sciences.
Brainstorming – Brainstorming can be done either individually or in groups. The ideas collected during the brainstorming session are reviewed or analyzed and where relevant included within the system requirements. In case we are find challenges to find out the functional requirement from business requirement in that case we can conduct brainstorming.
Domain Experts and SME (Subject Matter Experts) are involved in this activity. It needs to take approval from Project manager to conduct it. Brainstorming is an effective way to generate lots of ideas on a specific issue and then determine which idea is the best solution.
Brainstorming is a method of generating ideas and sharing knowledge to solve a particular commercial or technical problem, in which participants are encouraged to think without interruption. Brainstorming is a group activity, it’s a group of 8-12 people where each participant shares their ideas as soon as they come to mind.
What requirements questions to be asked
Share the Features of the Product?
What is the assumption you have that who the project works?
Which thinks we have to need to update or implement in project?
What is the impact of the new features?
What is the end result of this implementation?
How could these requirements will justify the business needs?
What is the current features of the project?