Get in Touch

Course Outline

Creating and Configuring an EAP File

  • Creating and saving Enterprise Architect project files
  • Understanding types of views
  • Navigating the program interface: menus, toolbars, Toolbox, Project Browser, and additional 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
  • Removing items and understanding the consequences of deletion
  • Saving diagrams

Requirements Management

  • Methods for gathering requirements
  • FURPS requirements categories
  • Creating Requirements Diagrams
  • Understanding relationships between requirements
    • Aggregation
    • Dependency
  • Enhancing diagram appearance
    • Layout adjustments
    • Color-coding requirements by status
    • Toggling package name visibility
  • Creating and managing matrix relationships
  • Documenting requirements
    • Generating HTML pages
    • Creating printable versions
  • Advanced requirement management
    • Defining custom requirement types
    • Setting 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
  • Managing concurrent flows and decision-making
  • Improving diagram appearance
    • Adjusting levels of detail
    • Reducing visual complexity
    • Managing process complexity
  • Components and Deployment diagrams
  • Establishing the initial system architecture - logical and physical
    • Nested components
    • Delegation and assembly
    • Ports
    • Interfaces
    • Communication paths
  • Implementing non-standard 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 the system scope
  • Actors and their relationships
    • Identifying use cases
    • Associating "actors" with "use cases" and understanding their properties
    • Relationships between use cases: include, extend, and generalization
  • Automatic numbering
  • Generating Use Case scenarios and corresponding activity diagrams
  • 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, and association classes
    • Class identification techniques
  • Sequence Diagrams
    • Message types: asynchronous, synchronous, and 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 diagram accuracy
  • Dynamic modeling at the method call level (sequence diagrams) based on use cases and static analysis models
  • Improving diagram appearance
    • 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, and exit

Patterns and Profiles (OPTIONAL)

  • "Gang of Four" design 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 options

Group Work

  • Versioning Enterprise Architect packages
  • Managing differences in project versions and documentation
  • Using a repository for model storage
  • Leveraging collaboration tools

Requirements

Proficiency in UML modeling.

 21 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories