(BA004) Data and Object Modeling Workshop
for the BA
Analyzing Business Rules with Class Diagrams and ERDs (with UML 2)
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.
Available on demand
Location: Live Online Event or In-Person at your Location
Duration: 2 days
Presented in English by Howard Podeswa
This course is IIBA-approved and qualifies for 14 CDUs (Career Development Units) towards CBAP accreditation.
Learning Objectives
What is this training about and why is it important?
Project failures or cost overruns can often be traced to Business Requirements documentation that is incomplete, inconsistent or ambiguous. By applying the data/object modeling techniques in the course, you will be able to successfully 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.
What you will learn and how you can apply it
Use object modeling techniques to help guide questions during business-rules 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.
Link the use-case model to the structural model (ERDs, class diagrams)
Determine 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.
Course Topics Include:
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
• 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)
• 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
• 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
• 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
• Introduction to Data Warehouses
> Mapping the Object Model to the Data Warehouse
• 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
Audience
Business Analysts
Data Base Administrators, Systems Analysts, Data Modelers expanding their role into the Business Analysis area