UML in Enterprise Architect (workshops) Training Course

Create and configure EAP file

• Creating and saving Enterprise Architect project files
• Types of views
• Program interface: menus, toolbars, Toolbox, Project Browser, and other windows
• Docking and hiding windows

Working with models and diagrams

• Predefined models
• Packages (views) and diagrams
• Adding elements to models and diagrams
• Methods for removing items and their implications
• Saving diagrams

Requirements Management

• Methods for requirements gathering
• FURPS requirements categories
• Requirements Diagrams
• Relationships between requirements
  • Aggregation
  • Dependency
• Enhancing diagram appearance
  • Diagram layout
  • Color-coding requirement status
  • Enabling or disabling package names
• Creating and managing relationship matrices
• Documenting requirements
  • HTML pages
  • Printable versions
• Advanced requirement management
  • Custom requirement types
  • Custom requirement status
  • Requirement tracking
  • Requirement documentation

Business process modeling and architecture

• Activity Diagrams
• Compound activities
• Control flows and object flows
• Handling exceptions and interrupt flows
• Partitions
• Concurrent flows and decision-making
• Enhancing diagram appearance
  • Various levels of detail
  • Reducing the amount of detail
  • Process complexity
• Component and Deployment diagrams
• Initial system architecture—logical and physical
  • Nested components
  • Delegation and assembly
  • Ports
  • Interfaces
  • Communication paths
• Non-standard implementation of stereotypes in diagrams (OPTIONAL)
  • Stereotype graphic libraries
  • Adding libraries to the project
  • Custom graphic stereotypes

Use cases and their documentation

• Modeling functional requirements
• System scope
• Actors and their relationships
  • Identifying use cases
  • "Actor-Use Case" associations and their properties
  • Relationships between use cases: include, extend, generalization
• Automatic numbering
• Use case scenarios and activity diagrams generated from them
• Documentation generation
• Document templates

Analytical model

• 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
• Sequence Diagrams
  • Message types: asynchronous, synchronous, return
  • Stereotypes: Boundary, Control, and Entity

Static model

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

Dynamic Model

• Static model verification
  • Clarifying method signatures
  • Verifying class diagrams
• Dynamic modeling at the method call level (sequence diagrams) based on use cases and the static analysis model
• Enhancing diagram appearance
  • Reducing the number of modeled scenarios
  • Reducing the number of lifelines
  • Avoiding complex nested blocks
  • Hiding details
• 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 in the project
• User patterns
• Importing profiles from XML files

MDA, source code (OPTIONAL)

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

Group work

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