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
  • Managing window docking and visibility

Working with Models and Diagrams

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

Requirements Management

  • Techniques for gathering requirements
  • FURPS requirements categories
  • Using the Requirements Diagram
  • Relationships between requirements
    • Aggregation
    • Dependency
  • Enhancing diagram appearance
    • Automated layout
    • Color-coding requirement statuses
    • Toggling package names visibility
  • Creating and managing requirement matrices
  • Documentation of requirements
    • Generating HTML pages
    • Creating printable versions
  • Advanced requirement management
    • Defining custom requirement types
    • Customizing requirement statuses
    • Tracking requirements
    • Managing requirement documentation

Business Process Modeling and Architecture

  • Activity Diagrams
  • Compound activities
  • Control flows and object flows
  • Handling exceptions and interrupt flows
  • Partitions
  • Managing concurrent flows and decision points
  • Enhancing diagram appearance
    • Adjusting levels of detail
    • Simplifying complex details
    • Managing process complexity
  • Components and Deployment Diagrams
  • Defining the initial system architecture (logical and physical)
    • Nested components
    • Delegation and assembly
    • Ports
    • Interfaces
    • Communication paths
  • Non-standard implementation of stereotypes in diagrams (OPTIONAL)
    • Accessing the stereotypes graphic library
    • Adding libraries to the project
    • Creating custom graphic stereotypes

Use Cases and Documentation

  • Modeling functional requirements
  • Defining system scope
  • Actors and their relationships
    • Identifying use cases
    • Associations between "actor" and "use case" and their properties
    • Inter-use case relationships: include, extend, generalization
  • Automatic numbering
  • Generating Use Case scenarios and activity diagrams based on them
  • Generating documentation
  • Utilizing 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 Diagram
    • Message types: asynchronous, synchronous, return
    • Stereotypes: Boundary, Control, Entity

Static Model

  • Class Diagram 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
    • Refining method signatures
    • Validating the class diagram
  • 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 unnecessary details
  • State Machine Diagram (OPTIONAL)
    • States and sub-states
    • Transitions between states: trigger, condition, 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 into database schemas
  • Generating SQL scripts based on Class Diagrams
  • Exploring source code generation options

Group Work

  • Versioning Enterprise Architect packages
  • Managing differences in project versions and documentation
  • Using a repository to store the model
  • Utilizing collaboration tools

Requirements

Proficiency in UML modeling.

 21 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories