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

Participants will:

• Gain a better understanding of the role of a business analyst
• Develop 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

Introduction to Business Analysis

• Business Analyst Roles and Responsibilities

•  Understanding the Business Analyst Role

• Skills Required By Business Analysts

• Business Analysis Projects

• Projects Roles

• Projects Deliverables

• A Systems Engineering Perspective of Business Analysis

• What is a System?

• Types of System

• Introduction to Soft Systems

Business Analysis Process Model

• Understand Business Strategy

• Investigate the Situation

• Consider Perspectives

• Analyse Needs

• Evaluate Options

• Define Requirements

Understanding Business Strategy

• Internal Strategy

• MOST Analysis

• Resource Analysis

• Portfolio Analysis Products and Services

• External Strategy

• PESTEL Analysis

• Competitive Analysis

• SWOT Analysis

Investigating the Situation

• Using Rich Pictures to Explore Scope

• Mind Maps as an Alternative to Rich Pictures

• Radiant Thinking

• Pattern Recognition

• PROMPT Analysis

Considering Perspectives

• Investigating Soft Systems

• Stakeholder Analysis

• Identifying Stakeholders

• Understanding Stakeholder Perspectives

• Stakeholder Profiles

• Classifying Stakeholders

• Managing Stakeholders

• Understanding the System Environment

• Introduction to Activity Theory

• Characteristics of Human Activity

• Object-Oriented

• Supported by Tools

• Achieve Goals

• Performed by Actors

• Hierarchical

• Developing Activity Breakdowns

• Synthesising Stakeholder Perspectives

• Decomposing Activities

• Mission

• Functions

• Tasks and Steps

• Arranging Activities Into an Approximate Time Line

• Showing Alternative Activities

Modelling Business Processes

• Introduction to Activity Diagrams

• Representing Activities

• Structuring Activities

• Showing a Sequence of Activities

• Representing Parallel Activities

• Modelling Decisions

• Modelling Actors

• Decomposing Activities

• Modelling Events

• Business Processes Models

• Modelling Physical Workflows

• Information Flows

• Flow of Physical Things

• Modelling Logical Workflows

• Modelling “As Is” Processes

• Modelling “To Be” Processes

Analysing Needs

• Requirements Hierarchy

• Business Needs

• Solution Features

• Software Requirements

• Identifying Business Needs

• Support for Business Activities

• Retrieving Information

• Enforcing Business Rules

• Solving Business Problems

• SWOT Analysis

• Root Cause Analysis

• Exploiting Opportunities

• Avoiding Threats

Evaluating Options

• Identifying Potential Solutions

• Categories of Solution

• Outlining

• Describing the Solution features

• Developing the "To Be" Business Process

• Investigating Feasibility

• Economic Feasibility

• Identifying Costs

• Hardware

• Network

• Software

• Staff

• Other

• Identifying Benefits

• Strengthening a Position

• Increasing Revenue

• Avoiding Costs

• Improving Value

• Analysing Benefits With a Results Chain

• Understanding the Time Value of Money

Defining Requirements

• An Overview of Formal Software Requirements

• Functional Requirements

• Interface Requirements

• Storage Requirements

• Non-Functional Requirements

• Usage Scenarios as an Alternative to Formal Requirements

• Documenting requirements With Use Cases

• Developing Use Case Diagrams

• Choosing Use Case Names

• The Importance of a Glossary
• Use Case Steps

• Use Case Scenarios

• Capturing Interface Requirements

• Data Dictionary

• End User Prototypes

• Use Case Templates

• Levels of Use Case Description

• Use Case Narrative

• Use Cases and Business Processes

• Using an Activity Diagram to Show the Sequence of Use Cases

• Using a Sequence Diagram to Show Interactions Between Actors

Review and Conclusion

Payment can be made by:

1. Cash or Credit Card or Bank Cheque payable to "สำนักงานพัฒนาวิทยาศาสตร์และเทคโนโลยีแห่งชาติ" (a post-dated cheque is not accepted) on the first day of the service or within the last day of the service.
2. Account transfer and send the proof of the payment (the deposit slip) via email [email protected]
   • ธนาคารกรุงเทพ สาขาอุทยานวิทยาศาสตร์
     Saving Account Number: 080-0-00001-0
     Account Name: สำนักงานพัฒนาวิทยาศาสตร์และเทคโนโลยีแห่งชาติ
   • ธนาคารกรุงไทย สาขาตลาดไท
     Saving Account Number: 152-1-32668-1
     Account Name: สำนักงานพัฒนาวิทยาศาสตร์และเทคโนโลยีแห่งชาติ