Get in Touch

Course Outline

Create and configure EAP file

  • Initialize and save an Enterprise Architect project file
  • Explore view types
  • Navigate the program interface, including menus, toolbars, Toolbox, Project Browser, and auxiliary windows
  • Customize the workspace by docking and hiding windows

Working with a model, diagram

  • Utilize predefined models
  • Manage packages (views) and diagrams
  • Insert elements into models and diagrams
  • Understand the various methods for removing items and their implications
  • Persist diagram changes

Requirements Management

  • Techniques for requirements gathering
  • Classify requirements using FURPS categories
  • Create Requirements Diagrams
  • Define relationships between requirements
    • Aggregation
    • Dependency
  • Enhance diagram aesthetics
    • Apply diagram layout rules
    • Color-code requirement status
    • Toggle package name visibility
  • Establish and manage relationship matrices
  • Document requirements
    • Generate HTML pages
    • Create printable versions
  • Advanced requirements management
    • Define custom requirement types
    • Set custom requirement statuses
    • Track requirement progress
    • Document requirement details

Business process modeling, architecture

  • Activity Diagrams
  • Compound activities
  • Manage control and object flows
  • Handle exceptions and interrupt flows
  • Use partitions
  • Model concurrent flows and decision points
  • Improve diagram presentation
    • Adjust detail levels
    • Simplify visual complexity
    • Manage process complexity
  • Components and Deployment diagrams
  • Establish initial system architecture (logical and physical)
    • Nested components
    • Delegation and assembly
    • Ports
    • Interfaces
    • Communication paths
  • Implement non-standard stereotypes in diagrams (OPTIONAL)
    • Use the stereotypes graphic library
    • Add the library to your project
    • Create custom graphics stereotypes

Use Cases and their documentation

  • Model functional requirements
  • Define system scope
  • Identify actors and their relationships
    • Identify use cases
    • Configure the "actor - use case" association and its properties
    • Map use case relationships: include, extend, generalization
  • Automate numbering
  • Generate use case scenarios and corresponding activity diagrams
  • Generate documentation
  • Utilize document templates

Analytical model

  • Domain-level Class Diagrams
    • Model classes, methods, attributes, abstract classes, and interfaces
    • Define associations and their characteristics
    • Map other relationships: aggregation, composition, generalization, dependency, association classes
    • Identify key classes
  • Sequence Diagrams
    • Handle message types: asynchronous, synchronous, return
    • Apply stereotypes: Boundary, Control, and Entity

Static model

  • Design-level Class Diagrams
  • Source code generation and reverse engineering (OPTIONAL)
    • Generate source code from diagrams
    • Generate diagrams from source code
    • Synchronize source code with diagrams
  • Object Diagrams

Dynamic Model

  • Validate static models
    • Clarify method signatures
    • Verify class diagrams
  • Perform dynamic modeling at the method call level (sequence diagrams) based on use cases and static analysis models
  • Enhance diagram readability
    • Reduce modeled scenarios
    • Minimize lifelines
    • Avoid complex nested blocks
    • Hide unnecessary details
  • State Machine diagrams (OPTIONAL)
    • Model states and sub-states
    • Define state transitions: trigger, condition, and action
    • Specify internal actions (entry, do, exit)

Patterns and profiles (OPTIONAL)

  • Apply "Gang of Four" patterns
  • Utilize patterns defined within the project
  • Implement user-defined patterns
  • Import profiles from XML files

MDA, source code (OPTIONAL)

  • Transform Class Diagrams into database schemas
  • Generate SQL scripts from class diagrams
  • Generate source code using available options

Group work

  • Version control for Enterprise Architect packages
  • Analyze differences between project and documentation versions
  • Use repositories for model storage
  • Leverage collaboration tools

Requirements

Proficiency in UML modeling.

 21 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories