The Business Analyst’s Crash CourseTM: The Essential BA Toolkit [with BABOK 2]
A quick immersion course in all the key knowledge areas of Business Analysis.
Course #: BA001
Duration: 2 days (14 CDUs)
Description:
An intensive practical course covering all aspects of the Business Analyst role – from requirements gathering to testing. The emphasis of the course is on learning practical tools and techniques that can immediately be put to use. All major techniques – both Structured and Object-Oriented (OO) – are addressed. Each trainee receives a hard copy of all course material as well as a Job Aids booklet, containing useful templates, examples, guidelines and glossary for use back on the job.
NEW!! Supports the most up-to-date standards and guidelines in the industry:
BABOK 2, ITIL V3 and UML 2.2
Why:
Most large companies and organizations that rely heavily on software for business operations, employ Business Analysts to communicate business needs to software developers. When analysts do not do their job effectively, the result is incomplete or incorrect requirements - leading causes of spiraling development costs and project delays.
In the Crash Course, you’ll learn how to cut costs and delays by improving communication between business stakeholders and developers through comprehensive requirements analysis and documentation and by guaranteeing results through structured testing and quality assurance.
1. Value for money: No course on the market offers this amount of content in so little time. How can we do this? By removing all of the “fat” traditionally found in BA courses.
2. Tool-focused: This course focuses on the tools and techniques used by the BA to perform the role. Unlike in other introductory courses, you won't waste time learning generalities; you'll actually learn how to use the key BA techniques so you can hit the ground running.
3. Scenario-based training: One integrated, case study, based on real systems, is used throughout the course to provide a consistent and realistic context for learning.
4. Experience: Our course is written and delivered by professionals with extensive practical experience in business analysis.
5. BABOK 2 alignment: Our course aligned with BABOK 2 – the Business Analyst Book of Knowledge published by the IIBA. It has been developed by BABOK reviewers and is aligned with BABOK 2 knowledge areas, tools and techniques.
6. Supports ITIL V3: ITIL is the word’s most widely used set of guidelines for IT Service Management. The ACRA/Noble Crash Course is the only course to that supports and maps to ITIL V3.
7. UML 2.2: The course is compliant with the latest version of the UML (Unified Modeling Language – the state-of-the-art standard for modeling real-world and IT systems.
8. CBAP accreditation: The Crash course has been reviewed and certified by the IIBA and is eligible for 14 credits towards CBAP (Certified BA Professional) accreditation.
• Entry-level IT Business Analysts and their managers
• Self-taught IT Business Analysts requiring a course that fills in the gaps and puts all the pieces together
• Systems Analysts and programmers interested in expanding their role into the business area.
Prerequisites: none
Class Format:
The course content is presented through:
• an integrated case study based on a real-life system
• lectures
• one-on-one assistance during the workshop portion of the course
High-level objectives
· For the new BA:
o Gain hands-on experience in using essential business analysis tools
o Create requirements documentation that can be used as the basis for customized development, maintenance of existing systems or as selection criteria for off-the-shelf software
· For the experienced BA:
o Upgrade your tool usage to the latest standards and best practices: UML 2.2, BABOK 2 and ITIL V3 - the world’s most widely used set of guidelines for IT Service Management.
o Understand how all of the essential BA tools fit together in the performance of the BA role
Detailed objectives
Upon completion of this course, you will be able to:
• Conduct effective requirements-workshop sessions (facilitated meetings) for capturing and verifying requirements.
• Learn how and when to ask the right questions during requirements elicitation events.
• Create quality requirements documentation for that is comprehensive, unambiguous and promotes consistency and reuse.
• Elicit and document user requirements with use cases.
• Model business process workflow and user interactions with UML 2.2 activity diagrams.
• Capture and document complex business rules using decision tables.
• Interpret Structured Analysis Data Flow Diagram (DFD) models.
• Use Entity Relationship Diagrams (ERDs) and UML Class Diagrams during interviews as effective tools for uncovering elusive business rules - which, when not discovered during elicitation, can be extremely expensive to implement.
• Learn how to convert Class Diagrams to ERDs and stakeholder-friendly textual business rules documentation
• Support the QA process by reviewing and ensuring the quality of the test strategy, test scenarios and test data using Structured Testing, Structured Walkthroughs, decision tables, use-case scenario testing and boundary-value analysis.
• Support the PM in managing requirements and planning a requirements-elaboration approach in the context of 2 of the major approaches to IT Project Management: Waterfall and Iterative-Incremental Development (a major aspect of agile processes).
• Brainstorming
• JAD (Joint Application Design)
• Business data modeling
• Entity Relationship Diagrams
• Use cases: textual documentation and diagrams
• Work Flow Breakdown and Analysis
• Activity Diagrams
• Data Flow Diagrams and Process Decomposition
• Decision Tables for Requirements Documentation and Testing
• Structured Testing principles and methods
• Structured Walkthroughs for QA
• Black Box requirements-based testing including boundary value analysis
• Systems testing (Regression, volume, stress, usability, performance tests)
• Mapping Business Analysis tools to project development phases for:
• Waterfall methodologies
• Iterative methodologies
• Managing Requirements
• Structural Object-Oriented (OO) tools for the Business Analyst, using UML 2
• Class diagrams
• Mapping ITIL V3 to the BA role
This course addresses the following BABOK knowledge areas and tasks.
|
Knowledge Area (KA) |
KA Task |
Mapping to the course |
|
Business Analysis Planning and Monitoring |
2.1 Plan Business Analysis Approach |
|
|
2.2 Conduct Stakeholder Analysis |
· Lesson 2: guidance on modeling stakeholders (actors) who interact directly with an IT solution. | |
|
2.3 Plan Business Analysis Activities |
· Lesson 8: guidance on planning BA activities over the project lifecycle for waterfall and iterative lifecycle approaches. | |
|
2.4 Plan Business Analysis Communication |
| |
|
Elicitation |
3.1 Prepare for Elicitation |
· Lesson 1: guidance on interview formats. |
|
3.2 Conduct Elicitation Activity |
Throughout the course: Guidance and hands-on experience in structuring the interview and lists of questions for elicitation events over the lifecycle. In particular: · Lesson 1, The BA Role and Requirements Elicitation: tips on each type of elicitation activity. · Lesson 2,: questions to ask stakeholders when gathering user requirements with use cases · Lesson 3: guidance on interviewing when using decision tables · Lesson 5, Analyzing Business Rules using Data Modeling: interview questions for stakeholder when performing structural (data) analysis. | |
|
Requirements Management and Communication |
4.3 Maintain Requirements for Reuse |
· Lessons 5 and 6: guidance and hands-on experience in the use of structural (data) modeling to centralize and reuse business rules regarding business objects. |
|
4.5 Communicate Requirements |
| |
|
|
5.2 Assess Capability Gaps |
· Lesson 2:guidance and hands-on experience in workflow modeling (used to analyzed As-Is and To-Be (solution) business processes in order to identify gaps). · An important input to this task is the Enterprise Architecture – On models used in the context of the Enterprise Architecture, see: o Lesson 3: business process workflow models and Decision Tables o Lessons 5 and 6: defining business concepts and relationships with ERDs and Class Diagrams |
|
5.4 Define Solution Scope |
· Lesson 2: definition of the solution scope (for an IT solution) using System Use Cases. | |
|
Requirements Analysis |
6.2 Organize Requirements |
· Lesson 7 Workshop 7-1: mapping the dynamic and structural models to each other. |
|
6.3 Specify and Model Requirements |
· Lesson 2: definition of user classes (actors). · Lesson 5 and 6: definition of concepts and relationships. · Techniques listed in the BABOK for this task are covered in this course as follows: o Business Rules Analysis: Lesson 3 (Rules expressed as Decision Tables) o Data Modeling: Lesson 5 (structured approach using ERDs); Lesson 6 (UML approach using class diagrams0 o Process Modeling: Lesson 3 o Scenarios and Use Cases: Lesson 2. o State Diagrams: Lesson 3. | |
|
6.5 Verify Requirements |
| |
|
Solution Assessment and Validation |
7.2 Allocate Requirements |
The following techniques, listed in the BABOK for this task, are addressed in the course: · Business Rules Analysis (for rules that may be managed through the software solution): Lesson 3 (Decision Tables). · Process Modeling (for allocation of and progressive implementation of activities and subprocesses): Lesson 3. |
|
7.3 Assess organizational readiness |
Lesson 3 (on Process Models, listed in the BABOK for this task). | |
|
7.5 Validate Solution |
· Lesson 7 provides guidance on: o designing tests to assess deployed solutions and ensure adequate test coverage o testing of non-functional (service level) requirements using System Tests. |
Clients
