UML in Enterprise Architect (workshops) Training Course

Creating and Configuring EAP Files

• Creating and saving Enterprise Architect project files
• Understanding different view types
• Navigating the programme interface: menus, toolbars, Toolbox, Project Browser, and other windows
• Docking and hiding windows

Working with Models and Diagrams

• Utilising predefined models
• Managing packages (views) and diagrams
• Adding elements to the model and diagram
• Exploring different methods of removing items and understanding their consequences
• Saving diagrams

Requirements Management

• Methods for gathering requirements
• FURPS requirements categories
• Creating Requirements Diagrams
• Defining relationships between requirements
  • Aggregation
  • Dependency
• Enhancing diagram appearance
  • Layout adjustments
  • Colour-coding requirement status
  • Toggling package name visibility
• Creating and managing matrix relationships
• Documenting requirements
  • Generating HTML pages
  • Creating printable versions
• Advanced requirement management
  • Defining custom requirement types
  • Setting custom requirement statuses
  • Tracking requirements
  • Documenting requirements

Business Process Modelling and Architecture

• Creating Activity Diagrams
• Using compound activities
• Managing control flows and object flows
• Handling exceptions and interrupt flows
• Utilising partitions
• Modelling concurrent flows and decision-making
• Improving diagram readability
  • Adjusting levels of detail
  • Reducing excessive detail
  • Managing process complexity
• Creating Components and Deployment diagrams
• Establishing initial system architecture (logical and physical)
  • Nested components
  • Delegation and assembly
  • Ports
  • Interfaces
  • Communication paths
• Implementing non-standard stereotypes in diagrams (OPTIONAL)
  • Using stereotype graphic libraries
  • Adding libraries to the project
  • Creating custom graphic stereotypes

Use Cases and Documentation

• Modelling functional requirements
• Defining system scope
• Managing actors and their relationships
  • Identifying use cases
  • Associating "actor - use case" and defining properties
  • Defining use case relationships: include, extend, generalization
• Automatic numbering
• Generating Use Case scenarios and activity diagrams
• Generating documentation
• Using document templates

Analytical Model

• Creating Class Diagrams at the domain model level
  • Classes, methods, attributes, abstract classes, and interfaces
  • Associations and their characteristics
  • Other relationships: aggregation, composition, generalization, dependency, association classes
  • Class identification
• Creating Sequence Diagrams
  • Message types: asynchronous, synchronous, return
  • Applying stereotypes: Boundary, Control, and Entity

Static Model

• Creating Class Diagrams at the design level
• Source code generation and reverse engineering (OPTIONAL)
  • Generating source code from diagrams
  • Generating diagrams from source code
  • Synchronising source code and diagrams
• Creating Object Diagrams

Dynamic Model

• Verifying the static model
  • Clarifying method signatures
  • Verifying the class diagram
• Dynamic modelling of method calls (sequence diagrams) based on use cases and the static analysis model
• Enhancing diagram appearance
  • Reducing the number of modelled scenarios
  • Reducing the number of lifelines
  • Avoiding complex nested blocks
  • Hiding unnecessary details
• Creating State Machine diagrams (OPTIONAL)
  • States and sub-states
  • Transitions between states: trigger, condition, and action
  • Internal actions: entry, do, exit

Patterns and Profiles (OPTIONAL)

• "Gang of Four" patterns
• Patterns defined within the project
• User-defined patterns
• Importing profiles from XML files

MDA and Source Code (OPTIONAL)

• Transforming Class Diagrams into database schemas
• Generating SQL scripts based on class diagrams
• Source code generation: available options

Group Work

• Versioning Enterprise Architect packages
• Comparing differences in project versions and documentation
• Using repositories to store models
• Utilising collaboration tools