Get in Touch
 Duration 21 hours

Course Outline

Creating and Configuring EAP Files

  • Initiating and saving Enterprise Architect project files
  • Understanding different types of views
  • Navigating the program interface: menus, toolbars, Toolbox, Project Browser, and additional windows
  • Managing window docking and visibility

Model and Diagram Management

  • Utilizing predefined models
  • Organizing packages (views) and diagrams
  • Inserting elements into models and diagrams
  • Exploring various deletion methods and their impacts
  • Strategies for saving diagrams

Requirements Management

  • Techniques for gathering requirements
  • Understanding FURPS requirement categories
  • Constructing Requirements Diagrams
  • Defining relationships between requirements
    • Aggregation
    • Dependencies
  • Enhancing diagram aesthetics
    • Adjusting diagram layout
    • Color-coding requirement statuses
    • 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
    • Documentation practices

Business Process Modeling and Architecture

  • Activity Diagrams
  • Compound activities
  • Control and object flows
  • Managing exceptions and interrupt flows
  • Partitions
  • Concurrent flows and decision logic
  • Improving diagram clarity
    • Varying levels of detail
    • Minimizing unnecessary detail
    • Managing process complexity
  • Component and Deployment Diagrams
  • Initial system architecture (logical and physical)
    • Nested components
    • Delegation and assembly
    • Ports
    • Interfaces
    • Communication paths
  • Non-standard implementation of stereotypes in diagrams (OPTIONAL)
    • Utilizing the stereotypes graphic library
    • Adding libraries to the project
    • Custom graphic stereotypes

Use Cases and Documentation

  • Modeling functional requirements
  • Defining the system scope
  • Actors and their interrelationships
    • Identifying use cases
    • Associations between "actor" and "use case" and their properties
    • Use case relationships: include, extend, and generalization
  • Automatic numbering
  • Use Case scenarios and the generation of activity diagrams from them
  • Documentation generation
  • Document Templates

Analytical Model

  • Class Diagrams at the domain model level
    • Classes, methods, attributes, abstract classes, and interfaces
    • Associations and their characteristics
    • Additional relationships: aggregation, composition, generalization, dependency, and association classes
    • Class identification
  • 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
    • Validating class diagrams
  • Dynamic modeling of method calls (sequence diagrams) based on use cases and static analysis models
  • Enhancing diagram readability
    • Reducing the number of modeled scenarios
    • Limiting the number of lifelines
    • Avoiding complex nested blocks
    • Concealing unnecessary details
  • State Machine Diagrams (OPTIONAL)
    • States and sub-states
    • State transitions: triggers, conditions, and actions
    • Internal actions (entry, do, exit)

Patterns and Profiles (OPTIONAL)

  • "Gang of Four" design patterns
  • Patterns defined within the project
  • 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
  • Source code generation options

Collaborative Work

  • Versioning Enterprise Architect packages
  • Reviewing differences in project and documentation versions
  • Using repositories for model storage
  • Collaboration tools

Requirements

Prior proficiency in UML modeling.

Testimonials (1)

Related Categories