Faculty of Digital Transformations.

Department of Information Systems

Course: Business analysis-1

I N S T R U C TO R
M U R ATO VA K A M I L L A N U R L A N O V N A
SENIOR-LECTURER,
MASTER IN TECHNICAL SCIENCE
Content lecture 1
1. Goal and objectives
2. Course policy
3. Grading policy
4. Learning and feedback
5. Introduction to business analysis
6. Broad responsibilities of business analyst
7. Types of business analyst roles
8. Top business analyst skills
9. Software development life cycle
 Goal and objectives
Goal: to learn the core business analysis knowledge
Objectives:
Business Analysis basics – learn what a Business Analyst is, what they do, and how they do it
A breakdown of six project methodologies including traditional Waterfall and Agile frameworks
Learn how to properly initiate a project by creating a business case that aligns with the business objectives
Understand the basics of project requirements and six of the popular techniques used to elicit those details from your
stakeholders
Gain an overview of various modeling diagrams to help you recognize and understand project documentation
Conduct requirement specification - including categorizing, deriving (breaking apart), prioritizing, and validating

Basic literature:
1. Babok Guide (a guide to the business analysis body of knowledge), Version 3.0 published 2015, ISBN-13: 97978-1-
927584-03-3
2. Karl Wiegers and Joy Beatty, Software Requirements, Version 3.0 published 2013, ISBN: 978-0-7356-7966-5
What do I expect from you?

FULL ATTENDANCE; PARTICIPATION TO THE INTERESTING IDEAS; SUBMISSION OF

CLASS DISCUSSIONS; ASSIGNMENTS ON
TIME
Course policy
Students are forbidden to:
• submit any tasks after the deadline. Late
submissions are graded down (10% per day).
• cheat. Plagiarized papers shall not be graded
(ZERO);
• be late for classes. Being tardy three times
amounts to one absence; ∗ retake any tests,
unless there is a valid reason for missing them;
• use mobile phones in class;
Students should always:
• be appropriately dressed (formal/semi-formal
styles are acceptable);
• show consideration for and mutual support of
teachers and other students;
• let the teacher know of any problems arising in
connection with their studies
Grading policy
Period Assignments Score Total
1st attestation Laboratory work 1 10 100
Laboratory work 2 25
Laboratory work 3 25
Mid-term 40

2nd attestation Laboratory work 4 30 100

Laboratory work 5 30
End-of-term 40
Exam 100
Total 0,3*1stAtt+0,3*2ndAtt+0,4*Final
 Feedback for lab works will be
given during defense

Learning and
For other questions text me in
Feedback Teams(k.muratova@iitu.edu.kz)

Do not write to me in
WhatsApp/telegram/Instagram
(penalty for each message 10%)
Introduction to
business
analysis
The Business Analysis Core Concept
Model™ (BACCM™) is a conceptual
framework for business analysis. It
encompasses what business analysis is
and what it means to those
performing business analysis tasks
regardless of perspective, industry,
methodology, or level in the
organization.

The six core concepts in the BACCM

are:
What is business analysis and who is
business analyst?
Business analysis is the practice of enabling change in an
enterprise by defining needs and recommending solutions
that deliver value to stakeholders
A business analyst is any person who performs business
analysis tasks, no matter their job title or organizational role.

“THE ONLY CONSTANT IN BUSINESS IS CHANGE.”

Broad responsibilities of a business
analyst
• understanding enterprise problems and goals
• analyzing needs and solutions
• devising strategies
• driving change
• facilitating stakeholder collaboration.
Business Process Analyst

Requirements Analyst

Types of
Systems Analyst
business
Data Analyst
analyst roles
User Experience Analyst
Business Process Analyst
Models business processes
Compares “as-is” and “to-be” models
Uses workflow and process engines
 Requirements and systems analyst
Requirements analyst:
Elicits/analyzes requirements
Bridges the gap between the business and IT
Solves problems with information technology solutions
Can be involved in functional design
Systems analyst:
Received documented requirements
Creates functional specifications
Defines “how” a system will do the “what”
Works with the technical team
Data and User experience analyst
Data analyst:
Performs logical data modeling
Identifies patterns in data
Designs and creates reports
User experience analyst:
Designs the user interface look and interaction
Focuses on efficiency and ease of use
Understands the end-user’s behavior
 COMMUNICATION NEGOTIATION PROBLEM
SOLVING
Top business
analyst skills

FACILITATION ORGANIZATION CRITICAL

THINKING
 SOFTWARE
DEVELOPMENT
LIFE CYCLE
Common
Misconception
Software Development Life Cycle
(SDLC)

vs

Systems Development Life Cycle

(SDLC)
SDLC
vs
SDL
C
Software Development Life Cycle
(SDLC)

Process used to plan, create, test,

and deploy an information system.
General SDLC
Steps

1. Gather Requirements
2. Design Solution
3. Development
4. Deploy
5. Maintenance
Methodologies
• Waterfall Model
• Spiral Model
• Incremental Model
• Prototyping
• Agile
• Scrum Model
• Rapid Application Development
(RAD)
Which
methodology
is the BEST?

Unfortunately, it’s
not that easy
Next lecture:
How that methodology works
Pros and cons of the methodology
When it's best used
THANK YOU
FOR YOUR
ATTENTION!!!