Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Create and configure EAP file
- Create and save an Enterprise Architect project file
- Understanding different types of views
- Navigating the program interface: menus, toolbars, Toolbox, Project Browser, and other windows
- Docking and hiding windows
Working with a model and diagrams
- Exploring predefined models
- Utilizing packages (views) and diagrams
- Adding elements to the model and diagrams
- Various methods for removing items and their implications
- Saving diagrams
Requirements Management
- Methods for gathering requirements
- Understanding FURPS requirements categories
- Using the Requirements Diagram
- Managing relationships between requirements
- aggregation
- dependency
- Enhancing diagram aesthetics
- diagram layout
- color-coding requirement statuses
- showing or hiding package names
- Creating and managing matrix relationships
- Documenting requirements
- generating HTML pages
- creating printable versions
- Advanced requirement management
- defining custom requirement types
- setting custom requirement statuses
- tracking requirements
- documenting requirements
Business process modeling and architecture
- Activity Diagrams
- Compound activities
- Control flows and object flows
- Handling exceptions and interrupt flows
- Partitions
- Managing concurrent flows and decision-making
- Improving diagram appearance
- adjusting levels of detail
- reducing excessive detail
- managing process complexity
- Components and Deployment diagrams
- Establishing the system's initial architecture—logical and physical
- nested components
- delegation and assembly
- ports
- interfaces
- communication paths
- Custom implementation of stereotypes in diagrams (OPTIONAL)
- stereotypes graphic library
- adding libraries to the project
- custom stereotype graphics
Use Cases and their documentation
- Modeling functional requirements
- Defining the system scope
- Identifying actors and their relationships
- Identifying use cases
- Associating "actor - use case" and its properties
- Use case relationships: include, extend, generalization
- Auto-numbering techniques
- Generating Use Case scenarios and corresponding activity diagrams
- 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
- 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
- Verifying the static model
- clarifying method signatures
- verifying the class diagram
- Performing dynamic modeling at the method call level (sequence diagrams) based on use cases and static analysis models
- Improving diagram appearance
- reducing the number of modeled scenarios
- reducing the number of lifelines
- avoiding complex nested blocks
- hiding unnecessary details
- State Machine Diagrams (OPTIONAL)
- states and sub-states
- state transitions - trigger, condition, and action
- internal actions (entry, do, exit)
Patterns and profiles (OPTIONAL)
- "Gang of Four" patterns
- Patterns defined within the project
- Creating 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
- Exploring available source code generation options
Group work
- Versioning Enterprise Architect packages
- Understanding differences in project and documentation versions
- Using a repository to store the model
- Utilizing collaboration tools
Requirements
Proficiency in UML modeling.
21 Hours
Testimonials (3)
Practise exercises in EA.
Pawel - Krajowa Szkola Skarbowosci
Course - UML in Enterprise Architect (workshops)
The pace of the classes.
Ruben Redondo Correas - Isdefe
Course - UML in Enterprise Architect (workshops)
Machine Translated
Many examples.
Alberto Laguna Aceves - Isdefe
Course - UML in Enterprise Architect (workshops)
Machine Translated
