Get in Touch
 Duration 21 hours

Course Outline

Create and configure EAP file

  • Establish and preserve an Enterprise Architect project file
  • Categories of views
  • Program interface: menus, toolbars, Toolbox, Project Browser, and associated windows
  • Docking and concealing windows

Working with a model, diagram

  • Predefined models
  • Packages (views) and diagrams
  • Incorporating elements into the model and diagram
  • Various methods for deleting items and their resulting impacts
  • Preserving diagrams

Requirements Management

  • Approaches for collecting requirements
  • FURPS requirements categories
  • Requirements Diagram
  • Interconnections between requirements
    • aggregation
    • dependency
  • Enhancing diagram presentation
    • diagram layout
    • color-coding requirement status
    • toggling package name visibility
  • Establishing and managing matrix relationships
  • Documentation of requirements
    • HTML pages
    • printable versions
  • Advanced requirement management
    • custom requirement types
    • custom requirement status
    • tracking requirements
    • requirements documentation

Business process modeling, architecture

  • Activity Diagram
  • Compound activities
  • Control flows, object flows
  • Managing exceptions, interrupt flow
  • Partitions
  • Concurrent flows and decision-making
  • Enhancing diagram presentation
    • various levels of detail
    • minimizing detail volume
    • process complexity
  • Components and Deployment diagrams
  • Initial system architecture - logical and physical
    • nested components
    • delegation and assembly
    • port
    • interface
    • communication paths
  • Non-standard implementation of stereotypes in diagrams (OPTIONAL)
    • stereotypes graphic library
    • integrating the library into the project
    • custom graphics stereotypes

Use Cases and their documentation

  • Functional requirements modeling
  • System scope
  • Actors and inter-actor relationships
    • Identifying use cases
    • Association "actor - use case" and its properties
    • Inter-use case relationships: include, extend, generalization
  • Auto numbering
  • Use Case scenarios and activity diagrams generated from them
  • Documentation generation
  • Document Templates

Analytical model

  • Class diagram at the domain model level
    • class, method, attribute, abstract class, interface
    • association and its characteristics
    • other relationships: aggregation, composition, generalization, dependency, association class
    • class identification
  • Sequence Diagram
    • message types: asynchronous, synchronous, return
    • stereotypes: Boundary, Control, and Entity

Static model

  • Class Diagram at the design level
  • Source code generation and reverse engineering (OPTIONAL)
    • generating source code from the diagram
    • generating diagrams from source code
    • synchronizing source code and diagrams
  • Object Diagrams

Dynamic Model

  • Static model verification
    • defining method signatures
    • verifying the class diagram
  • Dynamic modeling at the method call level (sequence diagram) based on use cases and the static analysis model
  • Enhancing diagram presentation
    • minimizing the number of modeled scenarios
    • reducing the number of lifelines
    • avoiding complex nested blocks
    • concealing details
  • State Machine diagram (OPTIONAL)
    • states and sub-states
    • transitions between states - trigger, condition, and action
    • internal actions (entry, do, exit)

Patterns and profiles (OPTIONAL)

  • "Gang of Four" patterns
  • Patterns defined within the project
  • User patterns
  • Importing profiles from XML files

MDA, source code (OPTIONAL)

  • Transforming Class Diagrams into database schemas
  • Generating SQL scripts based on class diagrams
  • Source code generation - available options

Group work

  • Enterprise Architect package versioning
  • Differences in project and documentation versions
  • Utilizing a repository for model storage
  • Collaboration tools

Requirements

Proficiency in UML modeling.

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories