|
Introduction and Overview
|
 |
- Overview of model-driven development
- Roles and responsibilities
- Building and maintaining an organization wide business model
- The role and importance of tools
|
| Review of UML - A short review of the UML diagrams required for requirements specification and technology neutral business process design including |
|
- Use case diagrams
- Sequence diagrams
- Activity diagrams
- Class diagrams
|
|
Review of URDAD - A short review of the URDAD analysis and design methodology based together with a case study
|
|
Working within MagicDraw - This section aims to get candidates comfortable with using a UML tool like MagicDraw |
|
-
Views (diagrams) versus the model
-
Working with UML diagrams with a particular emphasis on generating UML use case, sequence, activity and class diagrams
-
Manipulating the UML model directly
-
Setting environment and project defaults
-
Using Perspectives including Business Analyst, Architect and Developer perspectives
|
| UML profiles - UML profiles can be used to extend the UML language in order to adress some typically domain specific need |
|
|
|
| UML and BPMN - BPMN has made significant inroads into business process design |
|
- BPMN diagrams
- UML versus BPMN
- Benefits of using BPMN as a UML profile
|
|
Managing an URDAD business model within MagicDraw - This section is one of the main sections of this course. It aims to guide candidates in how to effectively manage a business model within a UML tool like MagicDraw. It shows how to generate the various URDAD model elements within a UML tool including
|
|
- Specifying the stake holder requirements
- Specifying services contracts
- Specifying user work flows for use cases
- Specifying the data structures for exchanged value objects
- How to perform the responsibility identification and allocation steps within a UML tool
- Business process specification for a specific level of granularity
The section then discusses the transition to the next level of granularity including when this is required and how this is done. Finally this section will show how to keep the business model in a manageable and navigatable state through: Effective package management, and Assigning of processes to use cases and services, and adding navigation links to the model.
|
| Model validation, metrics and refactoring - This section discusses ways in which to assess and validate a model qualities like |
|
|
|
|
Documenting the business model - This section discusses how to add metadata to models in order to improve the understandability of business models and in order to be able to use a UML tool to generate documents for various role players from the model
|
|
- Adding meta-data to models
- Generating standard reports
- Defining custom reports
- Defining URDAD report templates
|
|
Teamwork - Business analysts across the organization collaborating to build the business model. This section discusses the practicalities of doing this as well as the tools required to be able to manage an organization wide business model.
|
|
- Setting up an organization wide business model repository
- Authorization and access control
- Version control
|
| Wrap Up |
|
- Course Review
- Feedback Session
- Questions & Answers
|
back