Get in Touch

Course Outline

Create and configure an EAP file

  • Create and save an Enterprise Architect project file
  • Understanding various view types
  • Navigating the program interface: menus, toolbars, Toolbox, Project Browser, and other windows
  • Managing window docking and visibility

Working with models and diagrams

  • Exploring predefined models
  • Using packages (views) and diagrams
  • Adding elements to models and diagrams
  • Various methods for deleting items and understanding their implications
  • Best practices for saving diagrams

Requirements Management

  • Techniques for gathering requirements
  • Understanding FURPS requirement categories
  • Utilizing Requirements Diagrams
  • Defining relationships between requirements
    • Aggregation
    • Dependency
  • Enhancing diagram appearance
    • Automating diagram layout
    • Color-coding requirement statuses
    • Toggling package name visibility
  • Creating and managing matrix relationships
  • Documenting requirements
    • Generating HTML pages
    • Creating printable versions
  • Advanced requirement management
    • Defining custom requirement types
    • Configuring custom requirement statuses
    • Tracking requirement progress
    • Comprehensive requirements documentation

Business process modeling and architecture

  • Using Activity Diagrams
  • Defining compound activities
  • Managing control flows and object flows
  • Handling exceptions and interrupt flows
  • Implementing partitions
  • Designing concurrent flows and decision logic
  • Improving diagram aesthetics
    • Adjusting levels of detail
    • Simplifying complex details
    • Managing process complexity
  • Utilizing Components and Deployment diagrams
  • Establishing initial system architecture (logical and physical)
    • Using nested components
    • Implementing delegation and assembly
    • Defining ports
    • Defining interfaces
    • Mapping communication paths
  • Implementing non-standard stereotypes in diagrams (OPTIONAL)
    • Accessing the stereotypes graphic library
    • Adding custom libraries to the project
    • Customizing stereotype graphics

Use Cases and their documentation

  • Modeling functional requirements
  • Defining system scope
  • Identifying actors and their relationships
    • Identifying use cases
    • Associations between "actor" and "use case" and their properties
    • Use case relationships: include, extend, generalization
  • Implementing automatic numbering
  • Generating Use Case scenarios and activity diagrams from 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 techniques
  • 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
  • Using Object Diagrams

Dynamic model

  • Verifying the static model
    • Clarifying method signatures
    • Verifying class diagrams
  • Dynamic modeling at the method call level (sequence diagrams) based on use cases and static analysis models
  • Enhancing 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, 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 options available

Group work

  • Versioning Enterprise Architect packages
  • Managing 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