UML in Enterprise Architect (workshops) Training Course

Creating and Configuring EAP Files

• Create and save an Enterprise Architect project file
• View types
• Program interface: menus, toolbars, Toolbox, Project Browser, and other windows
• Docking and hiding windows

Managing Models and Diagrams

• Predefined models
• Packages (views) and diagrams
• Adding elements to models and diagrams
• Various methods for removing items and their implications
• Save diagrams

Requirements Management

• Techniques for gathering requirements
• FURPS requirement categories
• Requirements Diagrams
• Relationships between requirements
  • Aggregation
  • Dependency
• Enhancing diagram appearance
  • Diagram layout
  • Coloring requirement status
  • Toggling package name visibility
• Create and manage relationship matrices
• Documentation of requirements
  • HTML pages
  • Printable versions
• Advanced requirement management
  • Custom requirement types
  • Custom requirement statuses
  • 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
  • Varying levels of detail
  • Reducing detail amount
  • Managing 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)
  • Graphic library for stereotypes
  • Adding the library 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 diagram at the domain model level
  • Classes, methods, attributes, abstract classes, interfaces
  • Associations and their characteristics
  • Other relationships: aggregation, composition, generalization, dependency, association class
  • 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 validation
  • Clarifying method signatures
  • Verifying class diagrams
• Dynamic modeling at the method call level (sequence diagram) 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 within the project
• User patterns
• Importing profiles from XML files

MDA and Source Code (OPTIONAL)

• Transformation of Class Diagrams to database schemas
• Generation of SQL scripts based on class diagrams
• Source code generation - available options

Collaborative Work

• Versioning of Enterprise Architect packages
• Differences in project and documentation versions
• Using a repository to store the model
• Collaboration tools