Hathaway & Associates, Inc. is a Florida-based training and consulting firm

To better serve you,
we have more offerings in

Training, Products, Services, SDLC


	Business Analysis Using the Unified Modeling Language
	Business Analysis Using the Unified Modeling Language

Course Outline and Objectives
Course Philosophy and Approach
Public Class Schedule

printer friendly syllabus

No time for formal training?
try it with e-mentoring


	3 days

The target audience includes project leaders, business analysts, systems analysts, managers and end-users who may not be information system experts but are interested in using information technology to create a competitive advantage.

Business Analysis, Requirements Definition, and Testing Techniques or equivalent

Business Analysis and Requirements Gathering or equivalent

Our instructors have extensive experience in applying these techniques on projects with business experts from a wide variety of fields.

OI Business Analysis Revisited
OU Use Cases from a Business Perspective
OC Classifying and Analyzing Business Objects
OR Modeling Business Requirements with the UML
OA Business Architecture Analysis
OS Analysis and the UML: A Summary

Business analysts need more and better ways to effectively communicate business needs to IT professionals. For modern business analysts who are comfortable using process and data models, the next level of communication is the Unified Modeling Language (UML). This class uses non-technical terminology to introduce use case, class, object, activity, sequence, and state diagrams. Practical exercises will help you add these powerful new weapons to your communications arsenal.

You Need to Speak the Unified Modeling Language (UML) to:

	keep up with emerging forms of knowledge representation in the IT world
	evaluate whether or not the UML can be used on your project
	participate in an independent discussion of the merits of object versus structured approaches
	maintain or improve your communication skills
	create a consistent set of business and technical models from the beginning of the project


	Models of the Future

	This interactive training session introduces business and system experts to a new diagramming paradigm. Class, object, use case, activity, sequence, and state diagrams are explained in non-technical language, demonstrated using a simple model, and used by the participants in an extensive case study. If a picture is worth a thousand words, good models can decrease the project effort by an order of magnitude.

printer friendly syllabus

Course Outline and Objectives

Business Analysis Revisited
Module OI : Duration ~ 2 hours


	The process of figuring out how the business community can take advantage of information technology is evolving. For years, developers, system analysts and business analysts have struggled to find better and faster ways to gather, evaluate, and comprehend business requirements. Use cases, object models and a new language called the UML (Unified Modeling Language) promise to improve the way we do business analysis.

		What Do Business Analysts Analyze?
		Who Are the Stakeholders in an Information Project?
		What Is Requirements Engineering?
		Why Do You Need Models?
		What Is Different About Analysis For New Development and Maintenance Projects?

		Define the Evolving Role of Today's Business Analyst
		Recognize 7 Major Dimensions of Business Systems
		Differentiate Between Structured and Object-Oriented Analysis

Use Cases from a Business Perspective
Module OU : Duration ~ 5 hours


	A use case depicts how end-users and other actors will interact with the delivered information technology solution. A Use Case Diagram shows the interaction at a high level. The Basic Course of Events of a use case defines the specific and detailed steps that are part of that interaction.

		Who Or What Can Be an Actor?
		Where Do You Find Uses Cases?
		What Is in a Basic Course of Events?
		Where Do Happy, Alternate, and Exception Paths Lead?

		Document User Interaction in Use Cases
		Depict Your Scope with Use Case Diagrams
		Create Scenarios To Flush Out Details

Classifying and Analyzing Business Objects
Module OC : Duration ~ 5 hours


	As a business analyst, you have to understand what role information plays in the end-users' universe. Information systems represent the real world. It can be challenging to recognize what impact changes in reality have on the technology. Creating an object or class model will help you recognize and track how the various kinds of relationships that exist in the business system are or will be represented in the information system.

		When Do You Need To Model What?
		How Is Data Represented in the Unified Modeling Language (UML)?
		How Do You Create Class and Object Models That Normal Mortals Can Use?
		What Role Do These Static Models Play in Requirements Engineering?

		Create Class and Object Diagrams of the Business System
		Represent How Various Business Components Are Related
		Capture Implicit and Explicit Services That Objects Provide

Modeling Business Requirements with the UML
Module OR : Duration ~ 3 hours


	Business requirements are the subject matter expert's primary mechanism for communicating with information technology professionals. Written (textual) requirements are an essential component, but effective communication requires pictures. Activity, Sequence, and State Diagrams can flush out details that the text does not cover.

		What Do Business Requirements Define?
		Which UML Models Show Business Requirements?
		How Do You Create Activity, State, and Sequence Diagrams?
		When Do You Need Swimlanes?

		Analyze UML Diagrams To Identify Business Needs
		Identify State Transition Rules
		Document Communication Between Business Objects

Business Architecture Analysis
Module OA : Duration ~ 3 hours


	Whether new development or maintenance, the start of a project is an exciting and frustrating phase. At this point, you probably don't even know what you don't know about the project, and you have to get a handle on things quickly. Business analysis is all about finding the right questions to ask, asking the right people, and recognizing valid answers. If you could draw a picture of all of this, you would be well on your way to finding the right solutions.

		What's the Problem?
		How Can You Diagram a Business System?
		Where Do You Start?
		What Are Objects and Classes and Why Should You Care?

		Identify Critical Project Stakeholders
		Model the Business System Components
		Use Business Problems To Determine the Scope of a Project

Analysis and the UML: A Summary
Module OS : Duration ~ .5 hours


	Ultimately, the success of training lies not in the seminar itself but in the effect it has on your life. Given the time pressures of business life in the 21st century, you need to find new and creative ways of incorporating the presented techniques into your day-to-day work. To understand the importance of doing that, it might help to see the whole picture and review what was presented.

		What Are Other Standard Diagrams of the UML?
		Where Do We Go From Here?

		Discuss Additional Diagrams of the UML
		Evaluate the Topics Presented and Create a Personal Action List

Visit our Business System Analyst Bookstore
for books on the topics covered in this seminar.

	Object Oriented ( Business Objects , Object Oriented Analysis , Object Oriented Design , Object Oriented Modeling , Object Oriented Testing , State Transition Diagrams , Unified Modeling Language (UML) , Use Cases )
	Requirements ( Business Rules , Prototyping , Miscellaneous , Requirements Analysis , Requirements Definition , Requirements Documentation , Requirements Elicitation , Requirements Engineering , Requirements Management , Requirements Traceability , System Specifications , User Interfaces )
	Problem Analysis
	Workflow Analysis

Home In-House Training Public Seminars e-Mentoring Consulting FAQ Books

info@theHathaway.com