Requirement Elicitation Techniques for IT Business Analysts

Understand what exactly is a Requirement for any IT system (software application) with real-world examples.

Understand the Requirement Classification Scheme i.e. Types of Requirements with real-world examples. It includes 4 types of Requirements: Business Requirements, Stakeholder Requirements, Solution Requirements (Functional and Non-functional Requirements) and Transition Requirements.

Understand the general Software Aspects (Cross-cutting concerns) and Quality Attributes that should be available in any Software System to function correctly. This chapter explains all the Software Aspects (such as Data Validation, Security, Error Handling) and Quality Attributes (such as Usability, Reliability) with real-world examples. This knowledge is useful while eliciting requirements for any Software System to make sure that the elicited requirements cover the important software aspects and quality attributes.

Be able to understand and apply the SMART technique while Eliciting and Defining requirements. SMART stands for Specific, Measurable, Achievable, Relevant, Time-bounded.

Understand what is a Business Rule, Types of Business Rules (Structural, Behavioral), Basic Principles of Business Rules and the Analysis of Business Rules with real-world examples.

Understand the Lifecyle of a Requirement and the tasks that need to be performed during the lifecycle to manage and maintain requirements and design information: Trace Requirements, Maintain Requirements, Prioritize Requirements, Assess Requirement Changes and Approve Requirements.

Revision of important concepts learned in this chapter.

Understand how the requirements are provided to an IT Business Analyst through these sources: Official Email, CRM Tickets and Business Case or Project Charter with real-world examples. Be able to interpret requirements from these sources and prepare for eliciting requirements.

Understand how the requirements are provided to an IT Business Analyst through the Business Requirement Document (BRD) with a real-world example of a BRD. Be able to interpret requirements from the BRD and prepare for eliciting the requirements.

Understand the definition of Requirement Elicitation for IT Requirements with real-world examples.

Get an overview of 8 Requirement Elicitation Techniques, their types (Event Based or Activity Based) and usage of each technique.

Understand the overall process steps to Elicit any kind of Requirement. These steps include: (1) Prepare for Elicitation (2) Conduct Elicitation and (3) Confirm Results & Collaborate.

Revision of important concepts learned in this chapter.

It explains the Brainstorming Technique to elicit requirements with it's use cases, process to conduct a brainstorming session, Tools & Techniques (Mind Mapping, Round Robin, Reverse Brainstorming, Starbursting, FigJam Board) and a Real-world example to help you relate and apply your learning to your work practise.

It explains the Workshop Technique to elicit requirements with it's use cases, process to conduct a Workshop session, Workshop Roles, Tools & Techniques (FigJam Board) and a Real-world example to help you relate and apply your learning to your work practise.

It explains the Interview Technique to elicit requirements with it's use cases, different types of Interviews, process to conduct an Interview session and a Real-world example to help you relate and apply your learning to your work practise.

It explains the Observation Technique to elicit requirements with it's use cases, different types of Observations, process to conduct Observation and a Real-world example to help you relate and apply your learning to your work practise.

It explains the Survey Technique to elicit requirements with it's use cases, different types of Surveys, process to conduct a Survey, Tools (Google Forms / Type Form) and a Real-world example to help you relate and apply your learning to your work practise.

It explains the Prototyping Technique to elicit requirements with it's use cases, different types of Prototypes, process to do prototyping, Tools (Figma) and a Real-world example to help you relate and apply your learning to your work practise.

It explains the Document Review/Analysis Technique to elicit requirements with it's use cases, process to do Document Analysis and a Real-world example to help you relate and apply your learning to your work practise.

It explains the Interface Analysis Technique to elicit requirements with it's use cases, different types of interfaces, process to do Interface Analysis and a Real-world example to help you relate and apply your learning to your work practise.