Get in Touch

Course Outline

Create and Configure EAP File

  • Create and save an Enterprise Architect project file
  • Understanding 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
  • Removing items and understanding the consequences
  • Saving diagrams

Requirements Management

  • Requirements gathering methods
  • FURPS requirements categories
  • Requirements diagrams
  • Relationships between requirements
    • Aggregation
    • Dependency
  • Enhancing diagram appearance
    • Auto-layout diagrams
    • Coloring requirements by status
    • Toggling package name visibility
  • Creating and managing relationship matrices
  • Documenting requirements
    • Generating HTML pages
    • Creating printable versions
  • Advanced requirement management
    • Defining custom requirement types
    • Setting custom requirement statuses
    • Tracking requirements
    • Comprehensive 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
  • Enhancing diagram appearance
    • Adjusting levels of detail
    • Simplifying detail density
    • 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 stereotype implementation in diagrams (OPTIONAL)
    • Stereotype graphic libraries
    • Adding libraries to the project
    • Custom stereotype graphics

Use Cases and Documentation

  • Modeling functional requirements
  • Defining system scope
  • Actors and their relationships
    • Identifying use cases
    • "Actor-use case" associations and properties
    • Inter-use case relationships: include, extend, and generalization
  • Automatic numbering
  • Generating use case scenarios and corresponding activity diagrams
  • Documentation generation
  • Utilizing 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
    • Creating diagrams from source code
    • Synchronizing source code and diagrams
  • Object Diagrams

Dynamic Model

  • Static model verification
    • Refining method signatures
    • Verifying class diagrams
  • Dynamic modeling of method calls (sequence diagrams) based on use cases and static analysis
  • Enhancing diagram appearance
    • Reducing the number of modeled scenarios
    • Minimizing lifelines
    • Avoiding complex nested blocks
    • Hiding unnecessary details
  • State Machine diagrams (OPTIONAL)
    • States and sub-states
    • Transitions: 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 from class diagrams
  • Overview of source code generation options

Group Work

  • Versioning Enterprise Architect packages
  • Managing differences in project and documentation versions
  • Using repositories for model storage
  • Utilizing collaboration tools

Requirements

Proficiency in UML modeling.

 21 Hours

Testimonials (1)

Related Categories