Training Highlights
  • Focus on Hands on training with lot of assignments, practice exercises and quizzes
  • Assignments, Video recordings after each session posted on Training Blog
  • Quality Study material
  • Case Studies based on Real-time project based Scenarios
  • Certification Guidance
  • Certificate of Participation at the end.
Training Details
Course Duration: 40 hours Training + Case Studies

Training Materials: All attendees will receive,

  • Assignment after each module, Video recording of every session
  • Notes and study material for examples covered.
  • Access to the Training Blog & Repository of Materials

Training Format: This course is delivered as a highly interactive session, with extensive live examples. This course is Live Instructor led Online training delivered using Cisco Webex Meeting center Web and Audio Conferencing tool.

Timing: Weekdays and Weekends after work hours.

How are we Different from other Training Institutes?

Role-Specific Training – Traditional training focuses on an overall business process, without regard for the individual’s role. By contrast, Zaran Tech’s series of role-based courses delivers in-depth training on a specific role within the business process.

Hands-on Mentoring – Our expert trainer’s work side-by-side with each trainee and teach proven discipline and techniques for successful delivery. Mentoring is “hands-on” as part of actual projects to gain real-time experience.

Real-time Project Experience – Comprehension of practical skills is both reinforced and demonstrated in our training programs by completing Case studies of actual projects.

Certification Exams – Our trainers are all certified and provide expert industry level guidance to certification exams with tips and tricks to guarantee consistency of skills and practices for a successful completion of certification.

Ongoing Education – Zaran Tech continues to offer new courses so you can keep up-to-date on latest technologies and best practices.

After reviewing your goals, and assessing your current IT skills capability, ZaranTech will tailor an after-the-training program and placement plan that will meet your needs in successful placement. This includes Resume preparation assistance, Mock interviews (technical and project based), Soft Skills and On-the-job support.

Who Should Plan on Joining this program
  • Entry-level IT Business Analysts
  • Non IT professionals aspiring to get into Business analysis/analyst.
  • Self-taught IT Business Analysts wanting to fill in the gaps and put all the pieces together
  • Systems Analysts and programmers interested in expanding their role into the business area
About the trainer
  • 10 Years of IT Business Analysis Experience, including experience consulting for the “Big Four”
  • Domain expertise across multiple business verticals including Finance, Health Care and E Commerce
  • Accomplished trainer with experience conducting corporate workshops for audience of 30 people and more
  • Experience mentoring Junior Business Analysts for large clients. Independent consultant hired by Federal and State Government agencies to improve Business Analysis on highly visible, operation critical and time sensitive projects.
  • Member of multiple organizations including the IIBA and PMI
Modules Covered in this Training
The Business Analyst Training uses best practices and guidelines from International Institute of Business Analysis (IIBA®) in their Business Analysis Body of Knowledge® (BABOK® v2.0). The training content is customized to meet the practical needs of a Business Analyst professional.
In this training, attendees learn:
Module 1.Introduction to Business Analysis
Module 2. Understanding and Capturing business needs
Module 3. Requirement Analysis Process
Module 4.Creating Requirement gathering strategy
Module 5. Modeling Data and Processes
Module 6. UML Methodology
Module 7. Creating Effective Use Cases
Module 8.Business Analysis Tools
Module 9. Requirement Gathering, Business Modeling & Analysis Tools – MS Visio & Enterprise Architect
Module 10. Project Documentation and Management
Module 11. Software Testing
Module 12. Overview of International Institute of Business Analysis (IIBA)®, Business Analysis Body of Knowledge (BABOK), Certified Business Analysis Professional (CBAP) ®
Module 13. Requirement Gathering, Analysis and BRD creation in Real World domains, such as Financial, Health Care, Technology, Transportation and Automobile domain
Attendees also learn:
1.Resume Preparation Guidelines and Tips
2.Mock Interviews and Interview Preparation Tips
Topics Covered
 Introduction to Business Analysis
1.Introduction to Business Analysis
2.Business Composition and Architecture
3.Roles and Responsibilities of a Business Analyst
4.Need for a Business Analyst
5.Project Team
6.Importance of a Business Analyst in the Project Team
 Business Analysis Techniques
1.PESTLE – Political, Economic, Sociological, Technological, Legal, Environmental
2.MOST – Mission, Objectives, Strategies, Tactics
3.SWOT – Strengths, Weaknesses, Opportunities, Threats
4.CATWOE – Customers, Actors, Transformation Process, World View, Owner, Environmental Constraints
 System Development Life Cycle (SDLC)
1.Understanding Concept of Business Modeling
2.Requirement Gathering
 Understanding and Capturing business needs
1.Setting up priorities
2.Feasibility studies
3.Project scope
4.Business case
5.Risk assessment
6.Evaluating and selecting an initiative
7.Setting up future vision
 Software Engineering Methods
1.Waterfall Method
2.Rational Unified Process (RUP)
3.RAD Methodology
4.AGILE Methodology
5.Prototype Model
6.Comparison between Waterfall & RUP
7.Artifacts delivered in each phase of RUP
 Requirement Analysis Process
1.Creating Requirement gathering strategy
3.Requirements Activities
4.Requirement Gathering Techniques
5.Different Types of Requirements
6.Creating Business Requirement Document
7.Creating Software Requirement Specifications
8.Requirements Risk Management
9.Manage Requirements Change
 UML Methodology
1.Use Case Diagrams
2.Activity Diagrams
3.Sequence Diagrams
4.State Chart Diagrams
 Use Cases
1.Understanding Use Cases
2.Use Case Relationships
3.Use Case Brainstorming
4.Creating Use cases from Requirements
5.Creating Use Case Narratives
6.Change Management & Version Control Concept
 Business Requirement Gathering Tools
  • Rational Requisite Pro
  • Enterprise Architect
  • MS Visio
 Business Analysis & Modeling Tools
  • Enterprise Architect
  • MS Visio
  • Rational Rose
 Business Process Improvement
1.Selection of process teams and leader
2.Process analysis training
3.Process analysis interview
4.Process documentation
5.Review cycle
6.Problem analysis
 Modeling Data and Processes
1.Data models
2.Conceptual, logical and physical schemes
3.Data modeling process
4.Modeling methodologies
5.Entity relationship diagrams
6.Generic data modeling
7.Semantic data modeling
 Software Testing
1.Introduction to QA Methodology
2.Role of BA in Testing
3.Creating Test Plans
4.Creating Test Cases
5.Different Testing Methods
6.Functional and Regression testing
7.White Box and Black Box Testing
8.Positive and Negative Testing
9.GUI and Unit Testing
10.User Acceptance Testing
 Business Analysis Governance
1.International Institute of Business Analysis (IIBA)®
2.Business Analysis Body of Knowledge (BABOK)®
3.Certified Business Analysis Professional (CBAP)®
 Resume Preparation
1.Resume Review
2.Resume Preparation Tips
3.Sample Resumes
 Interview Preparation
1.Mock Interviews
2.Interview Preparation Tips
3.Sample Interview Questions
4.How to clear an Interview
IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by InternationalInstitute of Business Analysis. These trademarks are used with the express permission of International Institute of BusinessAnalysis.
CASE STUDY # 1 – “Healthcare System”
Healthcare System Application:
As the Product Manager for Inner Expressions you are asked to provide one of your largest clients with additional features in the EMR ( Electronic Medical Records Management) System. The client has requested an integrated Referral Management System that tracks patients from Primary care into the Specialist departments. Appointments are created by either the Primary Care Physicians themselves or other clinical staff like Nurse Practitioners or Clinical Assistants. Each appointment must go through the appropriate checks including checking if the patient has an active insurance with the client, whether the insurance program covers the condition of the patient, patient’s preference for location and timings and availability of the Specialist doctor.
Some appointments may have to be reviewed by the Specialists themselves before they can be approved, the administrator of the facility (hospital) must have the ability to choose by appointment type to either make it directly bookable by the Primary Care Staff or as a type that requires review by the specialist. The system should also allow the Primary Care Staff and specialists departments to exchange notes and comments about a particular appointment. If the specialist department requests tests or reports as mandatory for the appointment, the system must ensure that the patient has these available on the date of the appointment.
The system shall also allow users to track the status of patients’ appts & must store the entire clinical history of each patient. This will be used by the hospital for two main purposes; the specialist and the primary care providers will have access to the patients complete medical history before the patient walks in for the appt and hence allowing for better patient care, the Hospital also stores this data in a general data warehouse ( without Protected Health Information) to do analytics on it and come up with local disease management programs for the area. This is aligned with the Hospitals mission of providing top quality preventive medical care.
The Hospital sets about 300 appointments per day and must support about 50 users at the same time. The existing EMR system is based on Java and an Oracle database system.
  • Identify Actors, Use Cases, Relationships,
  • Draw Use Case Diagrams
  • Identify Ideal, Alternate and Exception Flows
  • Write a Business Requirements Document
CASE STUDY # 2 – “Asset Management System”
Asset Management Application:
The asset management system keeps track of a number of assets that can be borrowed, their ownership, their availability, their current location, the current borrower and the asset history. Assets include books, software, computers, and peripherals. Assets are entered in the database when acquired, deleted from the database when disposed. The availability is updated whenever it is borrowed or returned. When a borrower fails to return an asset on time, the asset management system sends a reminder to the borrower and informs the asset owner.
The administrator enters new assets in the database, deletes obsolete ones, and updates any information related to assets. The borrower search for assets in the database to determine their availability and borrows and returns assets. The asset owner loans assets to borrowers. Each system has exactly one administrator, one or more asset owners, and one or more borrowers. When referring to any of the above actor, we use the term “user”. All users are known to the system by their name and their email address. The system may keep track of other attributes such as the owner’s telephone number, title, address, and position in the organization.
The system should support at least 200 borrowers and 2000 assets. The system should be extensible to other types of assets. The system should checkpoint the state of the database every day such that it can be recovered in case of data loss. Owners and the administrator are authenticated using a user/password combination. Actors interact with the system via a web browser capable of rendering HTML and HTTP without support for JavaScript and Java.
The persistent storage is realized using an SQL database. The business logic is realized using the WebObjects runtime system. The system includes:
  • a storage subsystem managing persistent data
  • a session subsystem controlling authentication, check out, and check in
  • a notification subsystem sending past due notices
  • an administration subsystem realizing administration requests
  • an user interface subsystem translating HTTP requests into requests to other subsystems and translating results into HTML pages.
  • Identify Actors, Use Cases, Relationships,
  • Draw Use Case Diagrams
  • Identify Ideal, Alternate and Exception Flows
  • Write a Business Requirements Document