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 auxiliary windows
  • Customizing the workspace through docking and hiding windows

Managing Models and Diagrams

  • Utilizing predefined models
  • Organizing packages (views) and diagrams
  • Adding elements to models and diagrams
  • Techniques for removing items and understanding their implications
  • Saving and managing diagrams

Requirements Management

  • Strategies for effective requirements gathering
  • Applying FURPS requirements categories
  • Constructing Requirements Diagrams
  • Defining relationships between requirements
    • Aggregation
    • Dependency
  • Enhancing diagram aesthetics
    • Optimizing diagram layout
    • Color-coding requirement statuses
    • Toggling the visibility of package names
  • Creating and managing matrix relationships
  • Documenting requirements
    • Generating HTML pages
    • Creating printable versions
  • Advanced requirement management techniques
    • Defining custom requirement types
    • Setting custom requirement statuses
    • Tracking requirement lifecycle
    • Comprehensive requirement documentation

Business Process Modeling and Architecture

  • Developing Activity Diagrams
  • Defining compound activities
  • Mapping control and object flows
  • Handling exceptions and interrupt flows
  • Using partitions
  • Modeling concurrent flows and decision points
  • Improving diagram clarity
    • Adjusting levels of detail
    • Reducing unnecessary detail
    • Managing process complexity
  • Working with 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)
    • Utilizing stereotype graphic libraries
    • Adding libraries to the project
    • Defining custom graphic stereotypes

Use Cases and Documentation

  • Modeling functional requirements
  • Defining the system scope
  • Identifying actors and their interactions
    • Identifying use cases
    • Establishing the “actor-use case” association and its properties
    • Mapping use case relationships: include, extend, and generalization
  • Implementing auto-numbering
  • Generating use case scenarios and activity diagrams
  • Automating documentation generation
  • Managing Document Templates

Analytical Model

  • Creating domain-level Class Diagrams
    • Defining classes, methods, attributes, abstract classes, and interfaces
    • Specifying associations and their characteristics
    • Modeling other relationships: aggregation, composition, generalization, dependency, and association classes
    • Identifying key classes
  • Developing Sequence Diagrams
    • Distinguishing message types: asynchronous, synchronous, and return
    • Applying stereotypes: Boundary, Control, and Entity

Static Model

  • Creating design-level Class Diagrams
  • Source code generation and reverse engineering (OPTIONAL)
    • Generating source code from diagrams
    • Generating diagrams from source code
    • Synchronizing source code and diagrams
  • Utilizing Object Diagrams

Dynamic Model

  • Validating the static model
    • Clarifying method signatures
    • Verifying class diagrams
  • Performing dynamic modeling of method calls via sequence diagrams, based on use cases and the static analytical model
  • Enhancing diagram readability
    • Reducing the number of modeled scenarios
    • Minimizing the number of lifelines
    • Avoiding complex nested blocks
    • Hiding granular details
  • Creating State Machine diagrams (OPTIONAL)
    • Defining states and sub-states
    • Configuring transitions: triggers, conditions, and actions
    • Specifying internal actions (entry, do, exit)

Patterns and Profiles (OPTIONAL)

  • Implementing "Gang of Four" design patterns
  • Defining project-specific patterns
  • Creating 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
  • Exploring available source code generation options

Collaborative Work

  • Managing Enterprise Architect package versions
  • Analyzing differences between project and documentation versions
  • Utilizing repositories for model storage
  • Leveraging collaboration tools

Requirements

Demonstrable proficiency in UML modeling.

 21 Hours

Testimonials (1)

Related Categories