Get in Touch

Course Outline

Creating and Configuring the EAP File

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

Working with Models and Diagrams

  • Predefined models
  • Using Packages (views) and diagrams
  • Adding elements to models and diagrams
  • Different methods for removing items and their implications
  • Saving diagrams

Requirements Management

  • Techniques for requirements gathering
  • Understanding FURPS requirements categories
  • Utilizing the Requirements Diagram
  • Managing relationships between requirements
    • Aggregation
    • Dependency
  • Enhancing diagram aesthetics
    • Automated diagram layout
    • Color-coding requirement status
    • Enabling or disabling package names
  • Creating and managing matrix relationships
  • Documenting requirements
    • Exporting to HTML pages
    • Creating printable versions
  • Advanced requirement management
    • Defining custom requirement types
    • Setting custom requirement statuses
    • Tracking requirements
    • Comprehensive requirement documentation

Business Process Modeling and Architecture

  • Activity Diagrams
  • Compound activities
  • Managing control flows and object flows
  • Handling exceptions and interrupt flows
  • Using partitions
  • Concurrent flows and decision logic
  • Improving diagram presentation
    • Adjusting levels of detail
    • Reducing excessive detail
    • Managing process complexity
  • Components and Deployment diagrams
  • Establishing the initial system architecture - logical and physical
    • Nested components
    • Delegation and assembly
    • Ports
    • Interfaces
    • Communication paths
  • Non-standard implementation of stereotypes in diagrams (OPTIONAL)
    • Using the stereotypes graphic library
    • Adding libraries to the project
    • Creating custom stereotype graphics

Use Cases and Documentation

  • Modeling functional requirements
  • Defining system scope
  • Understanding actors and their relationships
    • Identifying use cases
    • Association between "actor - use case" and its 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 diagrams 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
    • Creating diagrams from source code
    • Synchronizing source code and diagrams
  • Object Diagrams

Dynamic Model

  • Verifying the static model
    • Clarifying method signatures
    • Verifying the class diagram
  • Dynamic modeling at the method call level (sequence diagram) based on use cases and static analysis models
  • Improving diagram presentation
    • Reducing the number of modeled scenarios
    • Minimizing the number of lifelines
    • Avoiding complex nested blocks
    • Hiding unnecessary details
  • State Machine diagrams (OPTIONAL)
    • States and sub-states
    • Transitions between states - triggers, conditions, and actions
    • 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
  • Source code generation - exploring available options

Group Work

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

Requirements

Proficiency in UML modeling.

 21 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories