IT BUSINESS ANALYST : IT BUSINESS ANALYST CAREER TRAINING
WELCOME : WELCOME
AGENDA : INTRODUCTIONS
COURSE DETAILS
IT BUSINESS ANALYST ROLE
REQUIREMENTS MANAGEMENT (USE CASE)
USE CASE EXCERCISE
INTRODUCTION TO UML
Q & A AGENDA
INTRODUCTIONS : NAME
WHAT DO YOU DO
A BRIEF SUMMARY OF YOUR CAREER
WHY YOU WANT THIS TRAINING INTRODUCTIONS
COURSE OUTLINE : Module 1: Business Analyst Roles, Object Oriented Analysis and Design (OOAD) and Rational Unified Process (RUP) Overview
Module 2: Unified Modeling Language (UML) Deep Dive Hands-on training with Rational Rose
Module 3: Documenting Functional Requirements creating Use Cases and Hands-on training with Rational Requisite Pro
Module 4: Data modeling and Data Analysis using Microsoft Visio, Excel & Access
Module 5: Software Quality Assurance using Mercury Quick Test professional and Mercury Quality center
Module 6: Ad-Hoc reporting with SQL Server Reporting services
Module 7: Client and meeting management skills
Module 8: Resume preparation and mock interviews COURSE OUTLINE
DAY 1 : Business Analyst Roles
Rational Unified Process (RUP) Overview
Requirements Management
Training with Rational Requisite Pro
Documenting Functional Requirements
Use Case Design
Brainstorming & JAD Sessions DAY 1
DAY 2 : Hands-on training with Rational ROSE
Creating UML Diagrams
Creating Story-Boards with Visio DAY 2
DAY 3 : SQL Server Reporting Services
Principals of Software Quality Assurance
Using Mercury Quick Test professional and Mercury Quality center DAY 3
DAY 4 : Resume preparation and interviews tips & techniques
Review of Topics
Q&A DAY 4
What You Can Expect to Learn? : Conduct Brainstorming & JAD Sessions
Facilitate Client Meetings & manage projects
Capture requirements, develop use case specifications and other project documentation
Change Management (Requirements)
Object oriented Analysis & Design (UML Models)
Create DataFlow diagrams and Storyboards in Visio
Software Quality Assurance
Database Reporting What You Can Expect to Learn?
DURATION : 1 MONTH
4 SATURDAYS
3 HOURS EACH SESSION
CLASSES HELD 10AM-1PM
AVAILABLE IN CLASSROOM & ONLINE FORMAT DURATION
WHY MCOM? : COURSES DESIGNED WITH END GOAL IN MIND
REAL LIFE PROJECT EXAMPLES
EMPHASIS ON PRACTICAL TRAINING
FREE PLACEMENT ASSISTANCE
ON THE JOB LIFE-LINE SUPPORT WHY MCOM?
IT BUSINESS ANALYST : A Business Analyst is involved in:
A. Gathering Requirements
B. Managing Requirements
C. Managing Projects
D. Writing code
E. All of the above
F. None of the above
G. All except D IT BUSINESS ANALYST
IT BUSINESS ANALYST : A Business Analyst is involved in:
A. Gathering Requirements
B. Managing Requirements
C. Managing Projects
D. Writing code
E. All of the above
F. None of the above
G. All except D IT BUSINESS ANALYST
OBJECT ORIENTED DESIGN : OBJECT ORIENTED DESIGN
IT BUSINESS ANALYST : IT BUSINESS ANALYST The IT Business Analyst is the professional who is generally associated
with requirements elicitation/analysis and solving problems using
information technology solutions. This role is the bridge between
business & IT.
The analysts in this role generally begin their work once a given IT
project has been initiated. They are the ones eliciting requirements
from stakeholders, analyze the requirements, document them in BRDs
(business requirements documents), and create functional
specifications. In this role the analyst may also interacts
with the development and quality assurance teams.
Other common titles for this role are: Requirements Engineer,
Requirements Analyst, Application Consultant, Application Analyst,
Business Analyst (generic term), etc. IT Business Analyst
» Focused on requirements
» Solves problems with IT solutions
» Bridge between business and IT
» Performs functional design THE WHAT #1
IT BUSINESS ANALYST : IT BUSINESS ANALYST
IT BUSINESS ANALYST : IT BUSINESS ANALYST
IT BUSINESS ANALYST : IT BUSINESS ANALYST
REQUIREMENTS MANAGEMENT : REQUIREMENTS MANAGEMENT Use cases describe the system from the user's point of view.
Use cases describe the interaction between a primary actor (the initiator of the interaction) and the system itself, represented as a sequence of simple steps. Actors are something or someone which exists outside the system under study, and that take part in a sequence of activities in a dialogue with the system to achieve some goal.
Actors may be end users, other systems, or hardware devices. Each use case is a complete series of events, described from the point of view of the actor. USE CASE
REQUIREMENTS MANAGEMENT : REQUIREMENTS MANAGEMENT REQUIREMENTS FLOW
CLASS PROJECT : Create a use case specification for the following product feature:
User Login CLASS PROJECT
RECAP : Intro to Business Analyst Role
Some Common challenges
Use Case
How to create a use case specification RECAP
INTRO TO UML : INTRO TO UML A Picture is worthier than a thousand words
INTRO TO UML : INTRO TO UML Project Summary
The CRM system consists of three major components. A contact manager, a data
merge/purge component and a backend Database. A user can access the CRM system
using a standard internet explorer webpage over the internet
INTRO TO UML : INTRO TO UML Project Summary
INTRO TO UML : INTRO TO UML UML DIAGRAMS Use case Diagrams
Activity Diagrams
Sequence Diagrams
Collaboration Diagrams
Class Diagrams
Deployment Diagrams
INTRO TO UML : INTRO TO UML Use case Diagrams
INTRO TO UML : INTRO TO UML Use case Diagrams
INTRO TO UML : INTRO TO UML Use case Diagrams ACTOR USE CASE Generalization DEPENDENCY
Q&A : Q&A