Scribd
Upload
24 views

Business/ Systems Analysis Programe: Course Contents

This program provides knowledge, skills, and training for business analysts. [1] It covers topics like requirements elicitation, documentation, UML, use cases, stakeholder management, and systems analysis. [2] Upon completing the course, students will be able to describe a business analyst's responsibilities, distinguish their role from other roles, develop requirements, and assist with prioritizing business needs. [3] The program uses modeling, interviews, and case studies to teach students how to diagnose business problems, develop requirements, and manage projects.

Uploaded by

Vighneswar Mulaga
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
24 views

Business/ Systems Analysis Programe: Course Contents

This program provides knowledge, skills, and training for business analysts. [1] It covers topics like requirements elicitation, documentation, UML, use cases, stakeholder management, and systems analysis. [2] Upon completing the course, students will be able to describe a business analyst's responsibilities, distinguish their role from other roles, develop requirements, and assist with prioritizing business needs. [3] The program uses modeling, interviews, and case studies to teach students how to diagnose business problems, develop requirements, and manage projects.

Uploaded by

Vighneswar Mulaga
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

BUSINESS/ SYSTEMS ANALYSIS PROGRAME

Course Contents
Audience: Business Analystes, Tester, Developers, Domain/ Functional consultants

Objective
A branded program suite which provides knowledge, skill and attitude required for Business Analysts.
This suite of program covers all aspects of Business engineering, Requirements elicitation, Requirements
verification, Requirements documentation and Requirements tracing.

Business Analyst’s need (Knowledge + Skill + Attitude)


UML
Rational Unified Process
Business model
Use case model
Storyboarding
User Interviews
Requirements documentation
Requirements verification
Systems thinking – Big picture view
Negotiation skills
Team concepts
Translation of requirements to design

Upon completion of the course, you will be able to (Learning Objective):

Describe the responsibilities of the business analyst and the major deliverables for each major step in the
business solutions life cycle

 Distinguish between the role of the business analyst and the project manager

 Distinguish between the role of the business analyst and the systems analyst

 List the critical skills needed to be a successful BA

 Define measurable project objectives

 Define business problems and find their true cause

 Develop tactics for diffusing resistance to change

 Prepare a stakeholder analysis to identify and classify those who will influence and be affected by

the solution
 Create and execute a Requirements Development plan

 Use modeling tools and techniques to elicit, document and validate a project’s scope and

requirements
 Use business analysis & project management tools

 Assist decision-makers in analyzing and prioritizing business needs

 Create a business case

 Communicate the results of a business case to stakeholders


Course Topics

 Introduction - What is Business Analysis?


o A look at different viewpoints
o What is being analyzed?
o What’s the goal?
o Current trends in business analysis
o Key concepts
o Definition
o Reconciled to common understanding within the organization
 The Role of the BA
o The relationship of business analysis to project management
o Differentiating between business analysis and other “analyst” roles
o Customer Needs & IT Needs
o The Skill Set Of A BA
o The BA’s Core Knowledge Set
 The Practice of Business Analysis
o BA Responsibilities
o Requirements Shepherding
 Software Engineering Process Models    

o SDLC
o Water Fall Model
o Spiral Methodology
o Agile (more evolved, RAD session: reverse-engineer session)
o RUP (Rational Unified Process)
o Example Case Study

 Modeling using UML


o UML
o Uml Defined
o UML History
o UML diagrams
o UML modeling mechanisms
o Reviews

 Diagnosing the Business Environment (Enterprise analysis)


o Business problem solving
o Understanding the business environment

o Capturing business initiatives across the enterprise

o Diagnosing a business problem or opportunity (i.e.; business initiative)

 Definition of a problem

 Finding and verifying true causes

 The use of the problem statement


o Techniques to identify business problems and causes

 Workflow modeling

 Fishbone Diagrams
o Gap Analysis

 Requirements Definition and Documentation


o Assessing stakeholder roles and responsibilities
o Identifying internal and external stakeholders
o Conducting stakeholder analysis
o Selecting requirements development templates
o Stake Holder Request Template
 Analysis of Requirements
o Fact gathering methods
o Interviewing
o Observation
o Questionnaires
o Research
o Organizing the facts
o Determining requirements
o Managing requirements
o Building a model of the solution
o Intro to Process modeling using DFDs
o Intro to data modeling –Information modeling
o
 Requirements Management with Use Cases 

o Key Concepts, Use case Model  


o Essentials elements of Use Cases:
o The writing process . . . (Dos and Don'ts)
o Linking Use Cases
o Analyzing Use Case text to uncover specific system requirements
o Converting Use Case description sentences into well-formed requirement
o A style guide with suggested formats for different levels of Use Case
o List of time-saving Use Case writing tips
o A proven methodology for taking advantage of Use Cases
o Business modeling i.e. techniques of identifying business concepts and tasks, and
introducing relevant parts of UML along the way/during Analysis phase.
o Activity Diagram

 Use Case Analysis Overview   

o Use Case Analysis Overview              


o Supplement Use case Description        
o Find Classes from Use Case behavior  
o Distribute Use case behavior to Classes
o Responsibilities of classes    
o Describe attributes and associations  
o Class Diagrams
o Sequence Diagram
o Collaboration Diagram

 Change Configuration Mgt and QA Concepts

o The business analysts role in testing


o Objectives
o Requirements
o Types of tests
o Use Case vs. Test Case
o Key to successful tests - anticipation and reconciliation
 Zach man Architecture (Reference )
 Project
For Student Assignment & Evaluation

          
                               

You might also like