Get in Touch

Course Outline

Creating and Configuring an EAP File

  • Creating and saving 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 hiding

Working with Models and Diagrams

  • Exploring predefined models
  • Utilizing packages (views) and diagrams
  • Adding elements to models and diagrams
  • Different methods for removing items and their respective consequences
  • Saving diagrams

Requirements Management

  • Methods for gathering requirements
  • FURPS requirements categories
  • Using the Requirements Diagram
  • Managing relationships between requirements
    • Aggregation
    • Dependency
  • Enhancing diagram appearance
    • Diagram layout
    • Color-coding requirement statuses
    • Enabling/disabling package names
  • Creating and managing matrix relationships
  • Documenting requirements
    • HTML pages
    • Printable versions
  • Advanced requirement management
    • Custom requirement types
    • Custom requirement statuses
    • Tracking requirements
    • 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
  • Improving diagram appearance
    • Varying levels of detail
    • Reducing detail to simplify
    • Managing process complexity
  • Components and Deployment Diagrams
  • System initial architecture: logical and physical
    • Nested components
    • Delegation and assembly
    • Ports
    • Interfaces
    • Communication paths
  • Non-standard implementation of stereotypes in diagrams (OPTIONAL)
    • Accessing stereotype graphic libraries
    • Adding libraries to the project
    • Custom graphic stereotypes

Use Cases and Their Documentation

  • Modeling functional requirements
  • Defining system scope
  • Actors and their relationships
    • Identifying use cases
    • Understanding "actor-use case" associations and their properties
    • Relationships between use cases: include, extend, generalization
  • Automatic numbering
  • Generating Use Case scenarios and associated activity diagrams
  • Documentation generation
  • 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
  • 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

  • Static model verification
    • Clarifying method signatures
    • Verifying class diagrams
  • Dynamic modeling at the method call level (sequence diagram) 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: available options

Group Work

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

Requirements

Proficiency in UML modeling.

 21 Hours

Testimonials (1)

Related Categories