Get in Touch

Course Outline

Create and Configure EAP File

  • Creating and saving an Enterprise Architect project file
  • Understanding different types of views
  • Navigating the program interface: menus, toolbars, Toolbox, Project Browser, and other windows
  • Docking and hiding windows

Working with Models and Diagrams

  • Utilizing predefined models
  • Managing packages (views) and diagrams
  • Adding elements to the model and diagrams
  • Various methods for removing items and their implications
  • Saving diagrams

Requirements Management

  • Methods for gathering requirements
  • FURPS requirements categories
  • Using the Requirements Diagram
  • Understanding relationships between requirements
    • aggregation
    • dependency
  • Enhancing diagram appearance
    • diagram layout
    • color-coding requirements by status
    • toggling package names visibility
  • Creating and managing matrix relationships
  • Documenting requirements
    • HTML pages
    • printable versions
  • Advanced requirement management
    • custom requirement types
    • custom requirement statuses
    • tracking requirements
    • documenting requirements

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
  • Improving diagram appearance
    • adjusting levels of detail
    • reducing the amount of detail
    • managing process complexity
  • Components and Deployment diagrams
  • Establishing initial system architecture - logical and physical
    • nested components
    • delegation and assembly
    • ports
    • interfaces
    • communication paths
  • Non-standard stereotype implementation in diagrams (OPTIONAL)
    • stereotype graphic library
    • adding the library to the project
    • custom graphics for stereotypes

Use Cases and Documentation

  • Modeling functional requirements
  • Defining system scope
  • Actors and their relationships
    • Identifying use cases
    • Association "actor - use case" and its properties
    • Use case relationships: include, extend, generalization
  • Auto-numbering
  • Generating Use Case scenarios and activity diagrams based on them
  • Documentation generation
  • Document Templates

Analytical Model

  • Class Diagrams at the domain model level
    • classes, methods, attributes, abstract classes, interfaces
    • associations and their characteristics
    • other relationships: aggregation, composition, generalization, dependency, association class
    • identifying classes
  • 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

  • Verifying the static model
    • 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
  • Project-defined patterns
  • User-defined patterns
  • Importing profiles from XML files

MDA and 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

Requirements

Proficiency in UML modeling.

 21 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories