UML in Enterprise Architect (workshops) Training Course

Creation and Configuration of EAP Files

• Initiating and saving Enterprise Architect project files
• Exploration of view types
• Navigating the program interface: menus, toolbars, Toolbox, Project Browser, and auxiliary windows
• Customizing the workspace by docking or hiding windows

Model and Diagram Management

• Utilization of predefined models
• Structuring Packages (views) and diagrams
• Integration of elements into models and diagrams
• Techniques for removing items and understanding their implications
• Persistence strategies for saving diagrams

Requirements Management

• Strategies for effective requirements gathering
• Application of FURPS requirements categories
• Construction of Requirements Diagrams
• Defining relationships between requirements:
  • Aggregation
  • Dependency
• Enhancing diagram aesthetics and clarity:
  • Optimizing diagram layout
  • Visualizing requirement status through color coding
  • Toggling package name visibility
• Establishing and managing relationship matrices
• Documentation of requirements:
  • Generation of HTML pages
  • Creation of printable versions
• Advanced requirement management techniques:
  • Definition of custom requirement types
  • Customization of requirement statuses
  • Requirement tracking mechanisms
  • Detailed requirement documentation

Business Process Modeling and Architecture

• Development of Activity Diagrams
• Implementation of compound activities
• Management of control flows and object flows
• Handling exceptions and interrupt flows
• Use of partitions
• Modeling concurrent flows and decision logic
• Optimizing diagram readability:
  • Managing levels of detail
  • Simplifying complex details
  • Reducing process complexity visualization
• Components and Deployment diagrams
• Establishing initial system architecture (logical and physical):
  • Nested components
  • Delegation and assembly patterns
  • Port definitions
  • Interface specifications
  • Communication paths
• Custom stereotype implementations in diagrams (OPTIONAL):
  • Utilizing stereotype graphic libraries
  • Integrating libraries into projects
  • Creating custom graphic stereotypes

Use Cases and Their Documentation

• Modeling functional requirements
• Defining system scope
• Actors and inter-actor relationships:
  • Identification of relevant use cases
  • Association properties for "actor-use case" links
  • Inter-use-case relationships: include, extend, and generalization
• Automatic numbering mechanisms
• Generation of use case scenarios and activity diagrams
• Automated documentation generation
• Application of Document Templates

Analytical Model

• Class diagrams at the domain model level:
  • Classes, methods, attributes, abstract classes, and interfaces
  • Associations and their specific characteristics
  • Other relationships: aggregation, composition, generalization, dependency, and association classes
  • Class identification techniques
• Sequence Diagrams:
  • Message types: asynchronous, synchronous, and return
  • Application of 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

• Verification of the static model:
  • Clarification of method signatures
  • Validation of class diagrams
• Dynamic modeling of method calls (sequence diagrams) derived from use cases and the static analysis model
• Optimizing diagram clarity:
  • Streamlining the number of modeled scenarios
  • Reducing lifeline clutter
  • Avoiding complex nested blocks
  • Concealing unnecessary details
• State Machine diagrams (OPTIONAL):
  • States and sub-states
  • State transitions: triggers, conditions, and actions
  • Internal actions: entry, do, and exit

Patterns and Profiles (OPTIONAL)

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

MDA and Source Code (OPTIONAL)

• Transformation of Class Diagrams into database schemas
• Generation of SQL scripts from class diagrams
• Source code generation options

Collaborative Group Work

• Versioning of Enterprise Architect packages
• Analysis of differences across project and documentation versions
• Use of repositories for model storage
• Integration of collaboration tools