Evanetics - Business System Analysis for OO Projects

Business System Analysis for Object-Oriented Projects
Description	Download Course Sample

The key to effective business analysis is to provide specification of “what” functionality a software system will provide its users, rather than “how” the software will be designed. But too often traditional business analysis produces artifacts and specifications that do not align with the concepts of object-oriented design and development.

This course focuses on how business analysts and business systems analysts can provide object-oriented developers with concise specifications of the problem domain within which a software solution will be constructed. Students will learn the power of the Unified Modeling Language version 2 (UML 2) for expressing business concepts and project goals using object-oriented models, to prepare for either in-house, or out-sourced, technical design and implementation.

Starting with basic concepts, this course challenges students with real-world examples and exercises of object-oriented thinking and UML modeling within an analysis mindset. Extensive hands-on exercises using two complete, and parallel, case studies assure that students see how a concept is modeled, and then have the opportunity to immediately apply and test their understanding.Extensive hands-on exercises using two complete, and parallel, case studies assure that students see how a concept is modeled, and then have the opportunity to immediately apply and test their understanding.

At the end of the course, the student will be able to:

Identify and conduct analysis tasks including defining the inputs, activities, and outputs of business system analysis with object-oriented modeling.
Discover and identify business abstractions from business requirements.

Translate business abstractions to object-oriented class representations in UML 2 notation.
Describe the value of responsibility-driven business analysis as a system organizing principle.

Develop both structural and behavioral UML models to specify a business domain from multiple perspectives, and know when to use each type of model.

Articulate a common analysis mindset and vocabulary to communicate effectively with other members of object-oriented projects.

Note: no computers or software modeling tools are used in this course. The emphasis is on how to analyze business needs in an object-oriented manner, not on using a CASE tool. With the concepts gained in this course, the students may then apply them using any CASE tool of their choice.

Duration

Three days.

Prerequisites

Experience in analysis is desirable, but not mandatory. This class assumes that students are new to the UML and the concepts and practices of object-oriented development, but may be either new or experienced in specifying software requirements.

Cost

$3,200 per course-day includes up to 12 students for on-site training. $300 per course-day for each additional student up to a maximum of 16 students.

Topics

Course Introduction

The Role of the IT Business Analyst

Concepts of Object-Orientation

– What it means for the IT-BA

– Student Exercise: Identify Operations & Attributes

The UML and the IT Business Analyst

Case Study Setup

Object-Oriented Analysis

Identify Analysis Classes

– Identify Candidate Entities

– Challenge the Candidate Entities

– Construct the Domain Model

– Student Exercise: Identify Analysis Classes

Responsibility-Driven Analysis

– Construct Responsibility Specifications

– Construct CRC Representations

– CRC Cards

– Example Case Study: CRC Cards

– Student Exercise: CRC Simulation

– Simulation Sequence Diagram

– Student Exercise: Identify Responsibilities

UML Overview – The 13 Diagrams

The UML Structural Model

UML Relationships

Association

– Modeling Exercise: Association

Aggregation & Composition

Association Class

– Modeling Exercise: Aggregation, Composition & Association Class

Inheritance

– Modeling Exercise: Inheritance

Developing The Analysis Class Diagram

– UML Classes, Objects & Stereotypes

– Responsibility-Driven Class Definition

– Step 1: Identify the Analysis Classes

– Step 2: Identify Classes with Relationships

– Step 3: Identify Relationship Semantics

– Step 4: Identify Relationship Multiplicity

– Example Case Study: Build the Initial Analysis Class Diagram

– Student Exercise: Build the Initial Analysis Class Diagram

Evolving the Class Diagram

– Example Case Study: Evolving the Class Diagram

– Student Exercise: Evolving the Class Diagram

The UML Behavioral Model

Developing The Sequence Diagram

– Sequence Diagram Structure

– Interaction Frames & Operators

– Special Tips for Analysis Sequence Diagrams

– Modeling Exercise: Sequence Diagram

– Example Case Study: Sequence Diagram

– Student Exercise: Build a Sequence Diagram

– Updating the Class Diagram

The Communication Diagram

Developing The State Machine Diagram

– Defining State

– State Machine Diagram Structure

– States, Events, Actions, Activities & Transitions

– Modeling Exercise: State Machine Diagram

– Example Case Study: State Machine Diagram

– Student Exercise: Build a State Machine Diagram

– Updating the Class Diagram

Developing The Activity Diagram

– Activity Diagram Structure

– Student Exercise: Build an Activity Diagram

Putting It All Together

– What Have We Accomplished?

Wrapup

References

UML 2 Notation

Appendix A: Class Diagramming Tips & Challenges

Appendix B: UML Interaction Frames

Appendix C: Advanced States

Audience

Business system analysts, business analysts, functional analysts, and project managers who need a common, practical technique for constructing business analysis specifications of object-oriented systems prior to design and architecture activities.

For more information about this course or other courses please contact Evanetics at 1-803-781-7628.