Power Electronics


Course Overview

  1. Why This Course?

    This course will help students to gain the foundational skills to perform the role of a business analyst (BA) in both waterfall and agile environments. They will learn how to plan business analysis activities; as well as the basics of eliciting, analysing, modelling, and writing requirements. Learn how to verify and validate product requirements, gain approval, and manage the requirements through the life cycle of the project. Understand the BA role in the design, development, and testing phases of a project. Gain new perspectives through hands-on, interactive group activities.
  2. What you will learn?

    1. Introduction to Business Analysis 1.1. Importance of Effective Business Analysis 1.2. Business Composition and Architecture 1.3. Roles and Responsibilities of a Business 2. Analyst 2.1. Need for a Business Analyst 2.2. Standardization and Adaptability 2.3. Importance of Communication/Collaboration Project Team 2.4. Importance of Business Analyst in the Project 2.5. Team 2.6. Business Analyst Career Path 2.7. Essential Skills of BA-Underlying 3. Competencies 3.1. SDLC Methodologies and Models 3.2. Waterfall Model 3.3. Rational Unified Process (RUP) 3.4. RAD Methodology 3.5. AGILE SCRUM Methodology 3.6. Prototype Model 3.7. Comparison between Waterfall and Agile Model 3.8. Artifacts delivered in each phase 3.9. Role of BA in Agile Scrum 4. Enterprise Analysis 4.1. SWOT Analysis 4.2. GAP Analysis 4.3. Feasibility Study 4.5. Root Cause Analysis 4.6. Strategy Analysis o External Environment 5. Analysis 5.1. Technique 5.2. Enterprise Architecture Frameworks 5.3. Scope 5.4. Business Case 5.5. Risk Assessment 6. OOA and Unified Modeling Language (UML) 6.1. Why Models are created? 6.2. Objectives of Modeling 6.3. What is Process Management 6.4. Understanding Process Modeling 6.5. Prototype 6.6. Analyzing and Managing Your Stakeholders 6.7. Identifying your stakeholders 7. Analyzing your stakeholders 7.1. Managing your stakeholders o Interacting 7.2. with your stakeholders 7.3. Requirements Elicitation 7.4. Define the term Requirement 8.Types of Requirements 8.1. Identifying good questions for elicitation 8.2. Roles of BA in Requirements Planning 9. Requirements Planning and monitoring 9.1. Business Analysis Planning Approach 9.2. Plan Business Analysis 9.3. Plan BA communication 9.4. Plan requirement management 9.5. Identify BA performance Improvement 10. Requirement Management 10.1. Prioritizing Requirements 10.2. Requirement traceability 10.3. Creating requirement package 10.4. Maintain requirement for reuse 10.5. Role of BA in Change Management 11. Verifying and Validating Requirements 11.1. Difference between Validation and Verification 11.2. Characteristics of Good Requirements 11.3. Risks associated with Requirements 11.4. Types of Testing Approaches 11.5. Creating a Test Plan 11.6. Requirements Traceability Matrix 11.7. Verified and Validated Requirements 12. Requirement Documentation 12.1. Formal and Informal Documentation and the Level of Detail Required 12.2. Writing for Usability and Comprehension 12.3. Common Requirements Document Defects 12.4. Components of a Formal Requirements Document 12.5. Requirements Verification and Validation 12.6. Requirements Sign-Off
  3. Venue and Schedule

    Schedule : To be notified