Description

Type

Course

Methodology

Online

The course is designed for analysts, designers, developers, testers and project managers.
The workshop presents a problem analysis, design and documentation systems using UML and Enterprise Architect of Sparx Systems. During the training will be presented to the advanced capabilities of the program (such as MDA, profiles, XMI), and best practices that can greatly simplify and accelerate modeling.
The training method:
Lecture 10%, 90% workshop

About this course

Requirements

Basic knowledge of the concepts of object-oriented programming and UML.

Questions & Answers

Add your question

Our advisors and other users will be able to reply to you

Reviews

Subjects

UML training
UML
Windows
Design
XMI
Project
Systems
Engineering
Communication Training
Architect

Course programme

Create and configure EAP file

Create and save a Enterprise Architect project file
File structure of the project
Types of views
Program interface: menus, toolbars, Toolbox, Project Browser and other windows
Docking and hiding windows

Working with a model, diagram

Predefined models
Packages (views) and diagrams
Adding elements to the model and diagram
Different ways of removing the items and their consequences
Saving diagrams

Requirements Management

Methods of requirements gathering
FURPS requirements categories
Requirements Diagram
Relationships between requirements
- aggregation
- dependency
- realization
How to improve the appearance of a diagram?
- layout diagram
- colour status requirements
- enable / disable the package names
Create and manage a matrix relationship
Documenting requirements
- HTML pages
- printable version
Advanced requirement management
- custom types of requirements
- custom requirements status
- tracking requirements
- requirements documenting

Business process modeling, architecture

Activity Diagram
Compound activities
Control flows, object flows
Handling exceptions, interrupt flow
Partitions
Concurrent flows and decision-making
How to improve the appearance of a diagram?
- different levels of detail
- reducing the amount of detail
- complexity of the process
Components and Deployment diagrams
The initial architecture of the system - logical and physical
- nested components
- delegation and assembly
- port, part
- interface
- communication paths
Security, performance, reliability of the system requirements modelling
Non-standard implementation of stereotypes in diagrams
- stereotypes graphic library
- adding the library to the project
- custom graphics stereotypes

Use Cases and their documentation

Functional requirements modeling
Scope of the system
Actors and the relationships between them
- Identifying use cases
- Association "actor - use case" and its properties
- Relationship between use cases: include, extend, generalization
Auto names
Use Case scenarios and diagrams generated based on them them (activity, state machine, sequence)
Use Case scenarios from external files
Documentation generation
Document Templates

Domain model

Main classes/objects of a system
Communication Diagram
- message types: asynchronous, synchronous, return
- messages numbering
- stereotypes: Boundary, Control and Entity
System design introduction

Static model

Class Diagram
Class diagram and source code generation
- association and its characteristics
- other relationships: aggregation, composition, generalization, dependency, association class
- naming convention for classes and their elements
- show/hide classes
Forward/Reverse engineering
- source code generating from the diagram
- diagram generation from source code
- source code and diagram synchronization
Object Diagrams

Dynamic Model

Static model verification
- clarify the method signatures
- verification of the class diagram
Dynamic modeling at the level of method calls (sequence diagram) based on use cases and static analysis model
How to improve the appearance of a diagram?
- reducing the number of modeled scenarios
- reducing the number of lifelines
- avoiding complex nested blocks
- hiding details
State Machine diagram
- states and sub-states
- transitions between states - trigger, condition and action
- internal actions (entry, do, exit)
How to improve the appearance of a diagram?
- line style
- state decomposition

Patterns and profiles

"Gang of Four" patterns
Patterns defined in the project
Collaboration
User patterns
Importing profiles from XML files

MDA, source code

Class Diagram to database schema transformation
SQL script generation based on class diagram
Source code generation - available options

Group work

Enterprise Architect package versioning
Differences in the versions of the project, documentation
Using a repository to store the model
Collaboration tools

Additional information

21 hours (usually 3 days including breaks)

See related categories

Contact us

UML in Enterprise Architect (workshops) Training Course

Questions & Answers

Reviews

Subjects

Course programme

Add similar courses
and compare them to help you choose.

UML in Enterprise Architect (workshops) Training Course

Questions & Answers

Reviews

Subjects

Course programme

Add similar coursesand compare them to help you choose.

Add similar courses
and compare them to help you choose.