Data and Object Modeling Workshop for the BA: Analyzing Business Rules with Class Diagrams and ERDs (with UML 2)
-
I had some basic cloud experience only so it was advanced for me though after a lot of questions I decided to go sit on the course and got a lot of help to understand the concept.
← | →
-
Relevant course material to my current project.
← | →
Course
Inhouse
Description
-
Type
Course
-
Methodology
Inhouse
-
Start date
Different dates available
Learn how to use static, structural analysis techniques to model a business domain. This is a hands-on practical workshop in the use of class diagrams, data models and other structural modeling diagrams to describe business requirements for an IT system. You will step through a complex real-life case study, learning at what points to develop and verify portions of the model. You will learn how to use structural analysis ‘live’ during interviews to define business concepts and objects and capture business rules and, later, how to use the structural model to verify use-cases from the behavioural model. You will also learn how to convert UML class diagrams to ERDs (Entity Relationship Diagrams), so that you can adapt to any analysis environment – OOA (Object-Oriented Analysis), structured analysis or mixed. Please note that this course is available on request with workshops in IBM Rational ROSE.
Facilities
Location
Start date
Start date
About this course
Upon completion of this course, you will be able to:Use object modeling to help guide questions during interviews.Integrate object modeling with use-case analysis.Create UML class diagrams that centralize business rules that apply across multiple use-cases and business contexts.Create links from structural modeling diagrams to the use-case model, and vice-versa: from use-cases to the diagrams.Judge how much modeling to do (and why) for different types of projects.Convert class diagrams to entity relationship diagrams (ERD) for use with Relational Data Base Management Systems (RDBMS).Understand the BA role on a Data Warehousing project and how to transition from relational transaction databases to a data warehouse.Upon request: Use a modeling tool (IBM Rational Rose, etc.) to model business requirements.
Business AnalystsData Base Administrators, Systems Analysts, Data Modelers expanding their role into the Business Analysis area
There are no formal prerequisites for this course.
Project failures or cost overruns can often be traced to Business Requirements documentation that is incomplete, inconsistent or ambiguous.Object and data modeling address all three issues:Complete documentation is ensured through model-driven interview techniques that ensure that all the right questions get asked.Consistent documentation is obtained through techniques that centralize common business rules within the structural model.Unambiguous documentation is produced by conforming to the UML – a standard widely accepted and wellunderstood by developers.
Reviews
-
I had some basic cloud experience only so it was advanced for me though after a lot of questions I decided to go sit on the course and got a lot of help to understand the concept.
← | →
-
Relevant course material to my current project.
← | →
Course rating
Recommended
Centre rating
Michael Linda
Lee Page
This centre's achievements
All courses are up to date
The average rating is higher than 3.7
More than 50 reviews in the last 12 months
This centre has featured on Emagister for 6 years
Subjects
- Inheritance
- Object oriented training
- UML training
- UML
- Object-oriented training
Course programme
#text-block-10 { margin-bottom:0px; text-align:left; }
1. Principles of Object Oriented Analysis
Benefit of Object Oriented Analysis
Determining how much modeling to do when the project is for a front-end to an existing legacy system
Objects, classes, inheritance, aggregation, polymorphism
2. Creating the essential business class model
Creating a common frame of reference of business concepts (classes) at the start of a project
Defining key entity (business) classes
Defining key associations during interviews with the client
Defining multiplicity during interviews with the client
Documenting entity classes with UML and Rational ROSE
Modeling roles in the class diagram: How to model people who interact in numerous ways with the business (e.g., a beneficiary who is also a policy owner)
3. Creating the detailed business structural model
Converting the essential business model into a detailed model by adding attributes and operations
Defining business data rules in the “Attributes” documentation of a class
Defining business procedural rules in the “Operations” documentation of a class
Distributing attributes and operations amongst classes when inheritance and aggregation are present in the model
4. Developing the structural model during use-case iterations
Identifying business classes referred to by a use-case
Verifying the use-case against the existing class model
Updating the class model based on the use-case
Linking the use-case to the structural model
#text-block-11 { margin-bottom:0px; text-align:left; }
5. Developing the data model
Reasons for converting the structural OO model (class diagrams) into a data model
Creating Entity Relationship Diagrams (ERDs) from class diagrams
Drawing Entities, Entity Relationships, Cardinalities
Converting inheritance and aggregation relationships to data modeling elements
How inheritance is implemented in a Relational Data Base Management System (RDBMS) such as ORACLE or DB2
6. Introduction to Data Warehouses
Mapping the Object Model to the Data Warehouse
7. Advanced topics
How the developer uses the business structural model to design the software
Interfaces, Patterns
Introduction to IDEF1
Introduction to new technologies: DSLs (Domain Specific Languages), MDA (Model Driven Architecture), the metapattern
Data and Object Modeling Workshop for the BA: Analyzing Business Rules with Class Diagrams and ERDs (with UML 2)