Get in Touch

Course Outline

Creating and Configuring EAP Files

  • Creating and saving Enterprise Architect project files
  • Overview of view types
  • Navigating the program interface: menus, toolbars, Toolbox, Project Browser, and other windows
  • Docking and hiding windows

Managing Models and Diagrams

  • Utilizing predefined models
  • Managing packages (views) and diagrams
  • Adding elements to models and diagrams
  • Methods for removing items and understanding their consequences
  • Saving diagrams

Requirements Management

  • Techniques for requirements gathering
  • FURPS requirements categories
  • Creating Requirements Diagrams
  • Defining relationships between requirements
    • Aggregation
    • Dependency
  • Enhancing diagram appearance
    • Diagram layout optimization
    • Color-coding requirement status
    • Toggling package names visibility
  • Creating and managing relationship matrices
  • Documenting requirements
    • Generating HTML pages
    • Creating printable versions
  • Advanced requirement management features
    • Defining custom requirement types
    • Configuring custom requirement statuses
    • Tracking requirements
    • Detailed requirements documentation

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 logic
  • Improving diagram presentation
    • Adjusting levels of detail
    • Reducing unnecessary detail
    • Managing process complexity
  • Components and Deployment diagrams
  • Initial system architecture (logical and physical)
    • Nested components
    • Delegation and assembly
    • Ports
    • Interfaces
    • Communication paths
  • Customizing stereotypes in diagrams (OPTIONAL)
    • Accessing the stereotypes graphic library
    • Adding libraries to the project
    • Defining custom graphic stereotypes

Use Cases and Documentation

  • Modeling functional requirements
  • Defining the system scope
  • Actors and their relationships
    • Identifying use cases
    • "Actor - Use Case" associations and properties
    • Use case relationships: include, extend, generalization
  • Auto-numbering
  • Use Case scenarios and generating activity diagrams from them
  • Generating documentation
  • Using Document Templates

Analytical Model

  • Class diagrams at the domain model level
    • Classes, methods, attributes, abstract classes, and 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
    • Validating the class diagram
  • Dynamic modeling at the method call level (sequence diagrams) based on use cases and the static analysis model
  • Improving diagram readability
    • Reducing the number of modeled scenarios
    • Minimizing the number of lifelines
    • Avoiding complex nested blocks
    • Hiding non-essential details
  • State Machine diagrams (OPTIONAL)
    • States and sub-states
    • Transitions between states (trigger, condition, action)
    • Internal actions (entry, do, exit)

Patterns and Profiles (OPTIONAL)

  • "Gang of Four" patterns
  • Patterns defined within the project
  • 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 and available options

Group Collaboration

  • Enterprise Architect package versioning
  • Reviewing differences in project and documentation versions
  • Using a repository for model storage
  • Utilizing collaboration tools

Requirements

Proficiency in UML modeling.

 21 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories