To be a master in Business Analysis, one should have well equipped with all the Concepts mentioned below. It is not enough to have only theoretical knowledge. Unless someone has been exposed to the practical aspects of each these concepts, then it is very difficult to implement these concepts correctly.
1. Introduction to Business Analysis
|
1.1 What is Business Analysis?
|
1.2 Who is a Business Analyst?
|
1.3 Roles and Responsibilities of a Business Analyst
|
1.4 Qualities to become a Business Analyst
|
1.5 Career as a Business Analyst
|
2. Basic Software Concepts
|
2.1 Life Cycles
|
2.1.1 Software Development Life Cycle (SDLC)
|
2.1.2 Project Life Cycle (PLC)
|
2.1.3 Test Life Cycle (TLC)
|
2.1.4 Product Development Life Cycle
2.2 Software Development Methodologies
|
2.2.1 Joint Application Development (JAD)
|
2.2.2 Rapid Application Development (RAD)
|
2.2.3 Agile Model (SCRUM)
|
2.2.4 Waterfall Model
|
2.2.5 Spiral Model
|
2.2.6 Prototype Model
2.2.7 Component Assembly Model
3. Business Analysis Planning and Monitoring
|
3.1 Define Business Need
|
3.2 Plan Business Analysis Approach
|
3.3 Conduct Stakeholder Analysis
|
3.4 Plan Business Analysis Activities
|
3.5 Plan Business Analysis
3.6 Communication
|
3.7 Plan Requirements Management Process
|
3.8 Manage Business Analysis Performance
4. Requirements Elicitation
|
4.1 Prepare for Elicitation
|
4.2 Conduct Elicitation Activity
|
4.3 Document Elicitation Results
|
4.4 Confirm Elicitation Results
5. Requirements Management and Communication
|
5.1 Manage Solution Scope & Requirements
|
5.2 Manage Requirements Traceability
|
5.3 Maintain Requirements for Re-use
|
5.4 Prepare Requirements Package
|
5.5 Communicate Requirements
6. Enterprise Analysis
|
6.1 Define Business Need
|
6.2 Assess Capability Gaps
|
6.3 Determine Solution Approach
|
6.4 Define Solution Scope
|
6.5 Define Business Case
7. Requirements Analysis and Documentation
|
7.1 Understand various Requirements Types
|
7.1.1 Business Requirement (User Requirement)
|
7.1.2 Functional Requirement
|
7.1.3 Non-Functional Requirement
|
7.1.4 User-Interface Requirements
|
7.1.5 External-Interface Requirement
7.2 Requirements Feasibility Study
|
7.2.1 Technical Feasibility
|
7.2.1 Economical Feasibility
|
7.3 Requirements Prioritization
|
7.3.1 Determine Priority of a Requirement
|
7.3.1 Determine Complexity of a Requirement
|
7.4 Requirements Documentation
|
7.4.1 Documenting various Requirements
|
7.4.1 Defining SMART Requirement
|
7.4.1 Document Risks, Issues and Constraints
7.5 Verify and Validate Requirements
|
7.6 Tracing Requirements - Requirements Traceability Matrix (RTM)
|
7.7 Define and Document Project Assumptions & Constrains
|
7.8 Create Wire-Frames (Mock UIs) with MS Visio / MS Excel
|
7.9 Manage and Document Change Requests (CR)
|
8. Project Scope Management
|
8.1 Understand Project Scope
|
8.1.1 Vision and Mission
|
8.1.2 Goals and Objectives
|
8.1.3 Strategies and Tactics
|
8.2 Document Project Scope
|
8.1.3 In-Scope
|
8.1.3 Out-Scope
|
|
9. Solution Assessment and Validation
|
9.1 Assess Proposed Solution
|
9.2 Allocate Requirements
|
9.3 Assess Organizational Readiness
|
9.4 Define Transition Requirements
|
9.5 Validate Solution
|
9.6 Evaluate Solution Performance
10. Business Process Modeling (BPM)
|
10.1 Introduction
|
10.1.1 What is Business Modeling?
|
10.1.2 What is Business Process Re-Engineering (BPR)?
|
10.1.3 Scope of Business Modeling
|
10.2 Business Modeling Types
|
10.2.1 Business Process Modeling (BPM)
|
10.2.2 Process Flow Modeling
|
10.2.3 Data Flow Modeling
|
10.3 Converting Business Requirements into Business Modeling
|
10.3.1 Technique of developing a Business Model
|
10.3.2 As-Is Process Modeling
|
10.3.3 To-Be Process Modeling
|
10.3.4 Evaluate and improve Business Processes
|
10.3.5 Write Process Descriptions
|
10.4 Drawing Modeling Diagrams through CASE Tools (MS Visio)
11. Basics of Data Modeling for a BA
|
11.1 Introduction
|
11.1.1 What is Data Modeling?
|
11.1.2 Scope of Data Modeling
|
11.2 Data Modeling Types
|
11.2.1 Conceptual Data Modeling
|
11.2.2 Logical Data Modeling
|
11.2.3 Physical Data Modeling
|
11.3 Creating Data Models
|
11.3.1 Define Entities & Relationships
|
11.3.2 Identify and Defining Attributes
|
11.3.3 Create Entity Relationship Diagrams
|
11.4 Drawing E-R Diagrams through CASE Tools (MS Visio)
12. Object Oriented Analysis & Design (OOAD) and UML
|
12.1 Introduction
|
12.1.1 Introduction to Object Oriented Analysis & Design (OOAD)
|
12.1.2 Introduction to Unified Modeling Language (UML)
|
12.1.3 Requirements Gathering & Documentation through OOAD & UML
|
12.2 UML - Structural Modeling Diagrams
|
12.2.1 Class Diagrams & Object Diagrams
|
12.2.2 Component Diagrams
|
12.2.3 Deployment Diagrams
|
12.3 UML - Behavioral Modeling Diagrams
|
12.3.1 Use Case Diagram
|
12.3.2 Activity Diagram
|
12.3.3 State Machine Diagram
|
12.3.4 Sequence Diagram & Interaction Diagram
|
12.4 Use Cases – In Detail
12.4.1 Relationships between Use Cases – E.g. Includes, Extends
|
12.4.2 Creating Use Case Diagram
|
12.4.3 Listing Use Cases
|
12.4.4 Mapping Use Cases with Requirements
|
12.4.5 Use Case Catalogue (Use Case Description)
|
12.5 Drawing UML Diagrams through CASE Tools (MS Visio)
13. Role of a Business Analyst in Testing
|
13.1 Introduction
|
13.1.1 What is Software Testing?
|
13.1.2 Testing Work Products
|
13.1.3 Testing Types
|
13.1.4 Bug Life-Cycle
|
13.1.5 Defect Prevention Techniques and Root Cause Analysis
|
13.2 User Acceptance Testing (UAT) Process
|
13.2.1 What is UAT?
|
13.2.2 UAT Process
|
13.2.3 Role of BA in UAT
|
13.2.4 Facilitate UAT
|
14. Business Analysis Techniques
|
14.1 Acceptance and Evaluation Criteria Definition
|
14.2 Benchmarking
|
14.3 Brainstorming
|
14.4 Business Rules Analysis
|
14.5 Decision Analysis
|
14.6 Document Analysis
|
14.7 Focus Groups
|
14.8 Functional Decomposition
|
14.9 Interface Analysis
|
14.10 Interviews
|
14.11 Lessons Learned Process
|
14.12 Metrics and Key Performance Indicators
|
14.13 Non-functional Requirements Analysis
|
14.14 Observation
|
14.15 Organization Modeling
|
14.16 Problem Tracking
|
14.17 Prototyping
|
14.18 Requirements Workshops
|
14.19 Risk Analysis
|
14.20 Scenarios and Use Cases
|
14.21 Survey/Questionnaire
|
14.22 SWOT Analysis
|
14.23 User Stories
|
14.24 Vendor Assessment
|
15. Business Analysis Work Products
|
15.1 Project Scope Document
|
15.2 Business Requirements Document (BRD) / User Req. Document (URD)
|
15.3 Functional Specs. Document (FSD) / Software Req. Specification (SRS)
|
15.4 System Specification Document (SSD) / Design Document
|
15.5 Requirements Traceability Matrix (RTM)
|
15.6 Use Case Template
|
15.7 Change Request Template
|
15.8 Release Notes
|
15.9 Proposal Documents (RFP Preparation)
In addition to the list of Business Analysis Concepts mentioned above, one should have been exposed to few of the below mentioned skills to make a Difference in the crowd.
Make a Difference
Professional Development
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Documentation & Presentation Skill Set
|
|
|
|
|
|
|
|
|
R & D Skills for a Business Analyst
|
|
|
|
|
|
|
|
|
Exploring a new Domain
Understanding a new Domain quickly
Exploring various modules of a new Domain
Working on a Project in a new Domain
|
contact@businessanalysis.in
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
