Course Duration: 3 Days

Course Category: Business Analysis & Requirements Engineering


21 PDUs (Professional Development Units)

Essentials of Business Analysis

Course Overview
Business analysis is concerned with investigating business needs and proposing solutions to business problems. Solutions often include some form of software system, but may also include improvements to business processes, development of staff skills or changes to the organisation structure.

The people that perform business analysis have a variety of job titles.  These include business analysts, systems analyst, functional analyst, business consultant and often, simply “BA”.

No matter what your job title is, this course is designed to develop the knowledge and skills that are essential to succeed at business analysis.

The course is based on the real-world experience and lessons learnt by practicing business analysts working on actual projects.  At the same time it presents an up to date perspective on business analysis that includes use cases.

Participants leave the course with a clear understanding of what is expected from a business analyst and the skills necessary to fulfill those expectations.

Course Features
  • Adopts a “systems” perspective of business analysis.
  • Covers material required for the Information Systems Examinations Board (ISEB) and International Institute of Business Analysis (IIBA) certification exams:
  • Based on the ISEB business analysis process model.
  • Suitable for graduates, developers and others moving into a BA role for the first time as well as experienced business analysts who need to update their skills, attend a “refresher” course or simply get some new ideas.

Participant Benefits
  • Gain a better understanding of the role of a business analyst.
  • Develops the essentials knowledge and skills required to investigate business systems; identify business needs and specify the requirements of a software solution.
  • Understand how to better align IT with business needs.

Who Should Attend
  • Those acting (or planning to act) in the role of Business Analyst, Business Systems Analyst, Systems Analyst, Functional Analyst or Business Consultant.
  • Software Development Managers, Project Managers, Program Managers, Developers and Testers who need to understand what business analysts do.
  • Project Sponsors, Project Stakeholders and End-User Representatives who participate in business analysis projects.

Course Agenda Introduction to Business Analysis

  • The roles and responsibilities of a business analyst
  • Skills required by business analysts
  • Business analysis projects
    • Other roles
    • Project deliverables
  • A systems engineering perspective of business analysis
    • What is a system?
    • Types of system
    • The traditional hierarchical view of systems
    • Systems and the contemporary business environment
    • Viewing systems as independent and overlapping
  • Business analysis workflow

Business Analysis and Quality

  • Incorrect assumptions about quality
    • Quality is the same as excellence
    • Quality cannot be measured
    • Quality is expensive
    • Quality can be tested into a product
    • Quality depends on people
Business Process Modelling
  • Characteristics of Human Activity
    • Object-Oriented
    • Supported By Tools
    • Achieves Goals
    • Performed by Actors
    • Involves stakeholders
    • Conforms to Rules
    • Allocated Responsibilities
  • Naming activities
    • Verb-noun template
    • Activity Verbs
    • Goals vs. tasks
  • Developing an Activity Map
  • Identifying Activities
    • Object Life Cycles
    • Resource Life Cycle
    • Hierarchical
  • Activity diagrams
    • Representing activities
    • Showing activity sequence
    • Decomposing activities
    • Showing parallel activities
    • Modelling decisions
  • Modelling workflow
    • Using swimlanes to represent actors
    • Representing information flows
    • Representing the flow of physical objects
  • Modelling business processes
    • Modelling logical workflows
    • Modelling the current workflow
    • Modelling the future workflow
  • Publishing the Business Activity Model
Review and Conclusion
  • Concepts
    • Managing by Observing
    • Managing With Information
    • The Activity Life Cycle
    • Categories of Information
    • Information Requirements
  • Identifying Information Requirements
    • Identifying information requirements from
    • Activity Breakdowns
    • Identifying information requirements from Activity Diagrams
    • The Information Requirements Catalogue
  • Information Samples
  • Data Elements
  • Derivation Rules
    • Describing with Natural Language
    • Describing with Activity Diagram
  • Subject Areas
  • Publishing the Information Requirements Catalogue
Requirements Definition
  • Why Requirements Definition?
  • Requirements Concepts
    • Types of Requirement
    • Requirements Deliverables
  • Business Rules and System Constraints
    • What are Business Rules
    • Classification of Business Rules
    • Where to Document Business Rules?
    • How to Document Business Rules?
    • Business Rules vs. Software Requirements
    • Publishing the Business Rules Catalogue
  • Vision and Scope
    • Vision
    • Features
      • Features and diagrams
      • Features and Natural Language
    • Functional Areas
    • Scope
    • Publishing the Application Vision and Scope
  • Software Requirements Specification
    • Formal Requirements
    • Requirements Characteristics
    • Interface Requirements
      • Software interfaces
      • Nwetwork interfaces
      • Hardware interfaces
    • Functional Requirements
      • Functional Requirements and diagrams
      • Functional Requirements Natural Language
      • Functional Areas
    • Storage Requirements
      • Logical Data Model
      • Data Dictionary
    • Non-Functional Requirements
      • Quality attributes (ISO9126)
      • Constraints
      • Non-Functional Requirements and diagrams
    • Publishing the Software Requirements Catalogue

Use Case Modelling

  • Why Use Case Modelling?
  • Use Case Concepts
    • Use Case and Activity Theory
    • Naming Use Cases
    • The Importance of a Glossary
  • Use Case Diagrams
  • Including Use Cases
  • Specialising Use Cases
  • Why Not to Use Extend!
    • What is "Extend"?
    • The Correct Approach to Specialisation A Better Approach to External Scenarios
  • Use Case Steps
    • The subject…verb…object template
    • Actor as the Subject
    • System as the Subject
    • Time as a Trigger
    • How to Handle "Actorless" Use Cases
    • Repetition
      • Repeating Steps
      • Concurrent Steps
  • Use Case Scenarios
    • Main Scenario
    • Alternate Scenarios
  • Handling Business Rules
  • Handing Functional and Non-Functional Requirements
  • Dealing With System Wide Functional Requirements
  • Interface Requirements
    • Handling Interface Requirements
    • Data Dictionary
    • Prototype
  • Organising Use Cases Into Functional Areas
  • Use Cases and Business Processes
    • Activity Diagrams
    • Sequence Diagrams
  • Use Case Templates
    • Use Case Templates
    • Levels of Use Case Description
    • Use Case Narrative
  • Publishing the Use Case Model

Business Analysis and Acceptance Testing

  • Why is testing necessary?
    • Software systems context
    • Causes of software defects (people)
    • Causes of software defects (environment)
    • How much testing is enough?
  • Testing principles
    • Principle 1: testing shows presence of defects
    • Principle 2: Exhaustive testing is impossible
    • Principle 3: Early testing
    • Principle 4: Defect clustering
    • Principle 5: Pesticide paradox
    • Principle 6: Testing is context dependent
    • Principle 7: Absence-of-errors fallacy
    • The software development life cycle
    • The V-model
    • Types of testing
      • Unit testing
      • Integration testing
      • System testing
      • Acceptance testing
      • Testing related to change
  • Testing and independence

Review and Conclusion

Available Funding Support
Malaysia Only

HRDF Logo_02This course is HRDF SBL & HRDF SBL Khas Approved

Leave a Reply

Your email address will not be published. Required fields are marked *

PMI, PMP, PMBOK, CAPM, PMI-ACP and the Registered Education Provider logo are registered marks of the Project Management Institute, Inc.
CMMI®, Capability Maturity Model®, Capability Maturity Modeling®, CMM®, PCMM® and Carnegie Mellon® are registered in the US Patent and Trademark Office by Carnegie Mellon University.
ISTQB® is a Registered Trade Mark of the International Software Testing Qualifications Board.
IIBA®, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis. Certified Business Analysis Professional, Certification of Competency in Business Analysis, Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
The APMG-International Agile Project Management, AgilePM and Swirl Device logos are trademarks of The APM Group Limited.
PRINCE2®, ITIL®, IT Infrastructure Library®, and MSP® are registered trademarks of AXELOS Limited. The Swirl logo™ is a trade mark of AXELOS Limited.
The ITIL Licensed Affiliate logo is a trademark of AXELOS Limited.
SCRUM Alliance REP SM is a service mark of Scrum Alliance, Inc.