AEC

BUSINESS ANALYST OF INFORMATION TECHNOLOGY LCA.EM

Course title:
BUSINESS ANALYSIS TECHNIQUES
420-AT4-UM















150 hours (4.67 units)
Weighting of course: 5-5-4

HOURS
Theory Practice Study at home

75 75 60




Semester: Fall 2020





COURSE OUTLINE


Theory Lab
Course code Course Title Total
hours hours
420-AT1-UM Introduction to Business Analysis 15 30 45
420-AT2-UM Data Manipulation 30 30 60
420-AT3-UM Project Management and Interpersonal Skills 30 60 90
420-AT4-UM Business Analysis Techniques 75 75 150
420-AT5-UM Supporting Tools for Business Analysis 30 30 60
420-AT7-UM Career Development 15 45 60
420-AT9-UM Project l 0 120 120
420-AT8-UM Project II – Business Analysis 0 315 315
900 195 705

COURSE DESCRIPTION

Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending
solutions that deliver value to stakeholders. It is a broad profession in which business analysts might perform work for
many different types of initiatives across an enterprise.

The primary purpose of this course is to allow students understand the Six Knowledge Areas (KA) defined in the Business
Analysis Body of Knowledge (BABOK) and apply different common used techniques and competencies to perform Business
Analysis tasks as Business Analysis professionals. There are several techniques used while analyzing a change or evaluating
the necessity for a change in an enterprise but this course targets those which have been identified by IIBA as the most
used on the market while executing BA tasks. The BABOK v3 will be explored and International Institute of Business
Analysis (IIBA) core standard will be followed in details to make sure the content is aligned.

1
AFTER SUCCESSFULLY COMPLETING THIS COURSE, THE STUDENT WILL HAVE PARTIALLY ACHIEVED THE
FOLLOWING OBJECTIVES (SKILLS) AND THEIR ELEMENTS:
Objective Objective Description Elements of the Objectives
code
ü Conduct planning activities
ü Conduct organizational activities
ü Contribute to management Activities
To use and adapt management ü Conduct monitoring activities
01HG ü Adapt methods and management tools
methods and tools
ü Contribute to the implementation of health and safety
corrective and preventive actions
ü Contribute to the implementation of the regulations and the
terms of the employment contract
ü Contribute to the planning of the quality of a product.
To contribute to an integrated
01HN ü Measuring the level of quality.
approach to quality
ü Contribute to the improvement of quality.
ü Analyze the general characteristics of the company
ü Analyze the company’s mode of operations.
Analyze the characteristics of
ü Analyze the characteristics of the flow of information within
0172 enterprise information systems
the company.
created to formulate IT solutions
ü Analyze the measures taken by the company in response to
legal requirements and internal policies regarding information

2 | P a g e
Montreal College of Information Technology

ü Model the data.
Develop conceptual models using ü Model the processes.
0173
the structured approach ü Validate the compatibility of the data models and processes

COURSE PLANNING

Class Dates Description of Theory and Practical per class Hours

Business Analysis & BA Profession

The evolution of the BA profession

BA, the foundation of Business Success

1 3.5

Underlying Competences for Business Analysis

profession
Analytical thinking and Problem Solving, Behavioral
Characteristics,

Business Knowledge, Communication Skills, Interaction
2 Skills, Tools and Technology 3.5

Business Analysis Key Concepts

Business Analysis Core Concept Model (BACCM), BABOK

Key Terms, Classification of Requirement Schema,
Requirements and Designs, Key Stakeholders

Business Analysis Planning and Monitoring KA:

Planning Business Analysis Approach (Task)

Techniques:

3 Brainstorming, Business Case, Document Analysis, 3.5

Estimation, Financial Analysis, Functional Decomposition,
Interviews, Item tracking, Lessons learned, Process

modeling, Reviews, Risk Analysis and Management, Scope
Modeling, Survey or Questionnaires, Workshops.

Inputs, Outputs & Stakeholders, Guidelines & Tools

3 | P a g e
Montreal College of Information Technology


Planning Stakeholder Engagement Approach (Task)

Techniques:

Brainstorming, Business Rules Analysis, Document Analysis,

Interviews, Lessons Learned, Mind Mapping, Organizational
Modeling, Risk Analysis and Management, Scope Modeling,

Stakeholder List, Map or Personas, Survey or
Questionnaire, Workshops.

Inputs, Outputs & Stakeholders, Guidelines & Tools

Planning Business Analysis Governance Approach (Task)

Techniques:

Brainstorming, Document Analysis, Interviews, item
tracking, Lessons Learned, Organizational Modeling,
Process Modeling, Reviews, Survey or Questionnaire,
workshop.

Inputs, Outputs & Stakeholders, Guidelines & Tools

Planning Business Analysis Information Management

(Task)
Techniques:

Brainstorming, Interviews, Item tracking, Lesson Learned,
mind Mapping, Process Modelling, Process Modeling,

Survey Or Questionnaire, Workshops.

Inputs, Outputs & Stakeholders, Guidelines & Tools

4 3.5
Identify Business Analysis Performance
Improvements (Task)
Techniques:

Brainstorming, Interviews, Item tracking, Lesson Learned,

Metrics and KPI, Observation, Process Analysis, Process
Modeling, Reviews, Risk Analysis and Management, Root
Cause analysis, Survey or Questionnaire.

Inputs, Outputs & Stakeholders, Guidelines & Tools

Elicitation and Collaboration KA:
5 3.5
Preparing for Elicitation (Task)

4 | P a g e
Montreal College of Information Technology

Techniques:

Brainstorming, Data Mining, Document Analysis,
Estimation, Interviews, Mind Mapping, Risk Analysis and

Management, Stakeholder List, Map or personas.

Inputs, Outputs & Stakeholders, Guidelines & Tools

Elicitation and Collaboration KA:
Conducting Elicitation (Task)

Techniques: Benchmarking and Market Analysis,
Brainstorming, Business Rules Analysis, Collaborative

games,

Concept Modeling, Data Mining, Data Modeling, Document

Analysis, Focus Group, Interface Analysis, Interviews, mind
Mapping, Observation, Process Analysis, process Modeling

Inputs & Outputs, Guidelines & Tools

Elicitation and Collaboration KA:

Confirming Elicitation (Task)

Techniques:

6 Document Analysis, Interviews, Reviews, Workshops 3.5

Inputs & Outputs, Guidelines & Tools

Communicate Business Analysis Information (Task)

Techniques:


Interviews, Reviews, Workshops

Inputs & Outputs, Guidelines & Tools

Elicitation and Collaboration KA:

7 Managing Stakeholder Collaboration (Task) 3.5

Techniques:

5 | P a g e
Montreal College of Information Technology


Collaborative games, Lessons Learned, Risk Analysis and

Management, Stakeholder List, Map, or Personas

Inputs & Outputs, Guidelines & Tools

Requirement Life Cycle Management KA:

Tracing Requirements (Task)

Techniques:

Business Rules Analysis, Functional Decomposition, process
Modeling, Scope Modeling

Inputs & Outputs, Guidelines & Tools

Maintaining Requirements (Task)
Techniques:

Business Rules Analysis, Data Flow Diagrams, Data
Modeling, Document Analysis, Functional Decomposition,

Process Modeling, Use Case and Scenarios, User Stories.

Inputs & Outputs, Guidelines & Tools

8 Requirement Life Cycle Management KA: 3.5

Prioritizing Requirements (Task)

Techniques:

Backlog Management, Business Cases, Decision Analysis,

Estimation, Financial Analysis, Interviews, Item Tracking,

Prioritization, Risk Analysis and Management, Workshops

Inputs & Outputs, Guidelines & Tools

Requirement Life Cycle Management KA:
Assessing Requirements Changes (Task)

Techniques:

9 3.5
Business Cases, Business Analysis rules, Decision Analysis,
Document Analysis, Estimation, Financial Analysis, Interface

Analysis, Interviews, Item tracking, Risk Analysis and Design

Inputs & Outputs, Guidelines & Tools

6 | P a g e
Montreal College of Information Technology


Requirement Life Cycle Management KA:

Approving Requirements (Task)

Techniques:

Acceptance and Evaluation Criteria, Decision Analysis, Item
Tracking, Reviews, Workshops

Inputs & Outputs, Guidelines & Tools

10 Mid-term Exam: Covers Class 1 – Class 8 3.5

Strategy Analysis KA

:

Analyzing the Current State (Task)

Techniques:

Benchmarking and Market analysis, Business Capability

Analysis, Business Cases, Business Model Canvas, Concept
Modeling, Data Mining Document Analysis, Financial
Analysis, Focus Groups, Functional Decomposition,
Interviews, item Tracking, Lessons learned, Metrics and KPI,
Mind Mapping, Observation, Organization Modeling,
11 Process Analysis, Process Modeling, Risk Analysis and 3.5
Management, Root Cause Analysis, Scope Modeling,
Surveys or questionnaires, SWOT Analysis, Vendor
Assessment, Workshops, User Story.

Inputs & Outputs, Guidelines & Tools

7 | P a g e
Montreal College of Information Technology


Defining the Future State (Task)

Techniques:

Acceptance and Evaluation Criteria, Balance Score Card,

Bench Marking and Market Analysis, Brainstorming,
Business Capability Analysis, Business Cases, Business
Model Canvas, Decision Analysis, Decision Modeling,
12 Financial Analysis, Functional Decomposition, Interviews, 3.5
Lessons learned, Metrics and KPI, Mind Mapping,
Organization Modeling, Process Modeling, Prototyping,
Scope Modeling, Survey or Questionnaire, SWOT
Analysis, Vendor Assessment, Workshops, User Story.

Inputs & Outputs, Guidelines and Tools

8 | P a g e
Montreal College of Information Technology


13 3.5



Strategy Analysis KA:
Assessing Risks (Tasks)

Techniques:

9 | P a g e
Montreal College of Information Technology


Brainstorming, Business Cases, Decision Analysis,

Document Analysis, Financial Analysis, Interviews,
Lessons learned, Mind Mapping, Risk Analysis and
Management, Root Cause, Survey or Questionnaire,
Workshops.

14 3.5
Defining Change Strategy (Task)
Techniques:

Balance Scorecard, Benchmarking, and Market

Analysis, Brainstorming, Business Capability Analysis,
Business Bases, Business Model Canvas, Decision
Analysis, Estimation, Financial Analysis, Focus Groups,
Functional Decomposition, Interviews, Lessons
Learned, Mind Mapping, Organization Modeling,
Scope Modeling, SWOT Analysis, Vendor Assessment,
Workshops.

Inputs & Outputs, Guidelines and Tools

10 | P a g e
Montreal College of Information Technology


15 Requirements Analysis and Design Definition KA: 3.5

Specifying and Modeling Requirements (Tasks)

Techniques:

11 | P a g e
Montreal College of Information Technology


Acceptance and Evaluation Criteria, Business Capability

Analysis, Business Canvas Model, Business Rules Analysis,
Concept Modeling, Data Dictionary, Data Flow Diagrams,
Data Modeling, Decision Modeling, Functional
Decomposition, Glossary, Interface Analysis, Non-
Functional Requirements Analysis, Operational Modeling,
Process Modeling, Prototyping, Roles and Permissions
Matrix, Root Cause Analysis, Scope modeling, Sequence,
Diagram, Stakeholder List, Map or Personas, State
Modeling, Use Cases and Scenarios, User Stories.

Inputs & Outputs, Guidelines and Tools

16 3.5

12 | P a g e
Montreal College of Information Technology


Requirements Analysis and Design Definition KA:

Verifying Requirements Tasks)
Techniques
Acceptance and Evaluation Criteria
Item Tracking, Metrics and KPI, Reviews.
Inputs & Outputs, Guidelines and Tools

Validating Requirements (Tasks)
Techniques:

Acceptance and Evaluation Criteria, Document Analysis,

Financial Analysis, Item Tracking, Metrics and PKI,
Reviews, Risk Analysis and Management

Inputs & Outputs, Guidelines and Tools

Requirements
Analysis and
Design
Definition KA:
17 Defining 3.5
Requirements
Architecture
(Task)
Techniques:Data
Modeling,
Functional

13 | P a g e
Montreal College of Information Technology

Decomposition,
Interviews
Techniques:
Organization
Modeling, Scope
Modeling,
Workshops,
SIPOC, Activity
Diagram
Inputs &
Outputs,
Guidelines and
Tools
Requirements
Analysis and
Design
Definition KA:
Defining Design
Options (Task)
Techniques:
Benchmarking
and Market
Analysis,
Brainstorming,
Document
analysis,
Document
Analysis,
Interviews,
Lessons
Learned, Mind
Mapping, Root
Cause Analysis,
Survey or
Questionnaire,
Vendor
Assessment,
Workshops.

Inputs &
Outputs,
Guidelines and
Tools





18
3.5

14 | P a g e
Montreal College of Information Technology

Requirements
Analysis and
Design
Definition
(KA):
Analyzing
Potential Value
and
Recommending
Solution (Task)
Techniques:

Interviews,
Metrics and PKI,
Risk Analysis and
Management,
Survey or
Questionnaire,
SWOT Analysis

Inputs &
Outputs,
Guidelines and
Tools

Solution
Evaluation
(KA):
Measuring
Solution
Performance
(Task)
Techniques:
Acceptance and
Evaluation
Criteria,
Benchmarking
and Market
Analysis,
Business Cases,
Data Mining,
Decision
Analysis, Focus
Groups, Metrics
and KPI, Non-
Functional
Requirements
Analysis,
15 | P a g e
Montreal College of Information Technology

Observation,
Prototyping,
Survey or
Questionnaire,
Use Cases and
Scenario,
Vendor
Assessment
Inputs &
Outputs,
Guidelines and
Tools



Analyzing
Performance
Measures (Task)
Techniques:
Acceptance and
Evaluation
Criteria,
Benchmarking
and Market
Analysis, Data
Mining,
Interviews,
Metrics and KPI,
Observations,
Risk Analysis and
19 Management, 3.5
Root Cause
Analysis, Survey
or
Questionnaire.
Inputs &
Outputs,
Guidelines and
Tools
Solution
Evaluation
(KA):
Assess Solution
Limitations
(Task)
Techniques

16 | P a g e
Montreal College of Information Technology

Acceptance and
Evaluation
Criteria,
Benchmarking
and Market
Analysis,
Business Rules
Analysis, Data
Mining, Decision
Analysis,
Interviews, Item
Tracking,
Lessons
Learned, Risk
Analysis and
Management,
Root Cause
Analysis, Survey
or Questionnaire
Inputs &
Outputs,
Guidelines and

Tools
Assess
Enterprise
Limitations
(Task)
Techniques:
Benchmarking
and Market
Analysis,
Brainstorming,
Data Mining,
Decision
Analysis,
Document
20 Analysis, 3.5
Interviews, Item
Tracking,
Lessons
Learned,
Observation,
Organization
Modeling, Risk
Analysis and
Management,
Roles and
Permissions
Matrix, Root
Cause Analysis,

17 | P a g e
Montreal College of Information Technology

Survey or
Questionnaire,
SWOT Analysis,
Workshops.

Inputs &
Outputs,
Guidelines and
Tools

Recommend
Actions to
increase
Solution Value
Task
Techniques:
Data Mining,
Decision
analysis,
Financial
Analysis, Focus
Groups,
Organizational
Modeling
Prioritization,
Process Analysis,
Risk Analysis and
Management,
Survey or

Questionnaire.

Business
Analysis
Perspectives
Agile: Scrum,
Kanban,
Business
21 Intelligence 3.5
perspective
Information
Technology
Perspective
Business
Architecture
perspective
18 | P a g e
Montreal College of Information Technology

Business Process
Management

perspective

22 Final Exam



Lab 01 Assignment: 5 hours
Defining interrelations between the 6 Core Concept model

Lab 02 Assignment: 4 hours
Business Scenario: Using Stakeholder List, Map, or Personas to engage stakeholders

Lab 03 Assignment: 4 hours
Business Scenario: Manage Business terms and data element using Glossary and Data Dictionary

Lab 04 Assignment: 4 hours
Business Scenario: Using Brainstorming to improve Business Analysis Performance

Lab 05 Assignment: 6 hours
Business Scenario: Using Brainstorming to Prepare for Elicitation
Business Scenario: Using Brainstorming to Conduct Elicitation

Lab 06 Assignment: 6 hours
Business Scenario:
Using Stakeholder List, Map, or Personas to engage stakeholders.
Explain Agile Mindset using Document Analysis

Lab 07 Assignment: 6 hours
Business Scenario: Using User Stories to analyze the current State and Define the Future State

Lab 08 Assignment: 4 hours
Business Scenario: Using interviews to define the change strategy

Lab 09 Assignment: 6 hours
Business Scenarios:
1. Explain Supply-chain relationship using Process Analysis and modeling (SIPOC/Activity Diagram)
2. Outline User interaction using Use Cases and Scenarios

Lab 10 Assignment: 6 hours
Business Scenario:
1. Clarify Business operations using Business Rule Analysis
2. Aligning solution components with Desired outcomes using Reviews

Lab 11 Assignment: 4 hours
Business Scenario: Outline user interaction using Interviews

Lab 12 Assignment: 6 hours
Business Scenario: Assess Solution limitation, enterprise limitations using Observation

Lab 13 Assignment: 4 hours
Develop Agile mindset

19 | P a g e
Montreal College of Information Technology

Notes regarding online classes as per Article 1 and Article 20 of the College Education Regulations of Québec (RREC):

- The number of classes and hours per each class described in the above plan may vary for courses delivered temporarily
online. Online courses are consisted of live sessions delivered by instructors, as well as extra activities through the
Learning Management System under the instructor guidance/supervision.

- Instructors will be providing students with more details regarding learning activities as classes resume.

- The duration of your program and respective courses is still the same.

- Students are encouraged to interact with instructors through Omnivox, as it will continue to be the main platform for
sharing content and providing assignments, among other activities.

- Examinations will be held in an online format. Instructors will be providing more details as classes start.


LAB SESSIONS

Please be advised that your program is composed of theory and labs. Similar to the theory portion of your program,
the student must also complete the lab portion in order to successfully complete the program leading to the diploma.

Students are encouraged to attend the lab sessions where they will receive additional assistance to complete their
labs, review the content delivered in class or address any questions they may have regarding the course content.

Please check the lab sessions schedule available for your course on Omnivox under “Documents and Messages”.
Additional sessions can also be requested by following the instructions available in the document.

Further instructions on completing the labs will be provided by your teachers.

If you have any questions or would like further information, please contact the Academics Department using the
email below:
academics@montrealcollege.ca


WEIGHTING OF THE SUMMATIVE EVALUATIONS

Labs 10%

Mid-Term Exam 40%

Final Exam 50%

ACADEMIC INTEGRITY: PLAGIARISM AND CHEATING

As stated in clause 4.10 of the IPESA:

MCIT defines plagiarism as: The use by a student of someone else’s language, ideas, images, work, information or any
other original material without acknowledging and/or documenting its source. This applies to any work presented or
submitted by the student such as, but not limited to: text, media, print or online document. To avoid plagiarism, all work
material must be in a student’s own words or, if using other resources – they must be appropriately quoted and
referenced.

Cheating means any dishonest or deceptive practices in relation to information, academic coursework and evaluation.

20 | P a g e
Montreal College of Information Technology

All incidents of plagiarism or cheating will be reported to the Pedagogical Committee and the Academic Dean will be
informed.

The above incidents may result in disciplinary action such as:
- Failing grade of zero on the assignment, work or course.
- Suspension/expulsion from the course and/or the program and/or the college.

For further information, please refer to the IPESA, found on Omnivox under “Documents and Messages”.

RECOMMENDED READINGS AND MEDIA

• IIBA Core Standard

• BABOK v3
• UML for the IT Business Analyst - A practical Guide to Requirements Gathering Using the Unified Modeling
Language,
Nd
2 Edition by Howard Podeswa
• http://www.mountaingoatsoftware.com/

TEACHING METHODOLOGY

This course has a total of 150 hours of theoretical and practical training. The training consists of different components:
lecture, practice, formative assessment, demonstrative, etc. The material is seen in class. The student is expected to do
homework at home. The nature and content of the Project will be explained during the semester at the Teacher’s
discretion.

The Student is responsible for reading the Institutional Policy on the Evaluation of Student Achievement (IPESA).

TEACHER’S COORDINATES

Name:

To e-mail the Instructor, please use MIO, which is found on Omnivox.

21 | P a g e
Montreal College of Information Technology