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.
Duration 21 hours
Course Outline
Create and Configure the EAP File
- Create and save an Enterprise Architect project file
- Explore various view types
- Navigate the program interface: menus, toolbars, Toolbox, Project Browser, and other windows
- Manage window docking and visibility
Working with Models and Diagrams
- Utilize predefined models
- Manage packages (views) and diagrams
- Add elements to the model and diagram
- Understand different methods for removing items and their implications
- Save diagrams effectively
Requirements Management
- Apply various requirements gathering methods
- Categorize requirements using the FURPS model
- Create and interpret Requirements Diagrams
- Define relationships between requirements
- Aggregation
- Dependency
- Enhance diagram appearance
- Apply layout settings
- Indicate requirement status via color
- Toggle package name visibility
- Create and manage relationship matrices
- Document requirements
- Generate HTML pages
- Create printable versions
- Advanced requirement management
- Define custom requirement types
- Set custom requirement statuses
- Track requirements
- Maintain requirement documentation
Business Process Modeling and Architecture
- Create Activity Diagrams
- Model compound activities
- Map control flows and object flows
- Handle exceptions and interrupt flows
- Utilize partitions
- Represent concurrent flows and decision logic
- Optimize diagram presentation
- Adjust levels of detail
- Reduce excessive detail
- Manage process complexity
- Design Components and Deployment diagrams
- Establish initial system architecture (logical and physical)
- Nested components
- Delegation and assembly
- Ports
- Interfaces
- Communication paths
- Implement non-standard stereotypes in diagrams (OPTIONAL)
- Use the stereotypes graphic library
- Add the library to the project
- Apply custom graphical stereotypes
Use Cases and Documentation
- Model functional requirements
- Define system scope
- Define actors and their relationships
- Identify use cases
- Associate "actor - use case" and define properties
- Model use case relationships: include, extend, generalization
- Apply auto-numbering
- Generate activity diagrams from use case scenarios
- Generate documentation
- Use document templates
Analytical Model
- Create Class Diagrams at the domain model level
- Define classes, methods, attributes, abstract classes, and interfaces
- Define associations and their characteristics
- Model other relationships: aggregation, composition, generalization, dependency, association classes
- Identify classes
- Create Sequence Diagrams
- Model message types: asynchronous, synchronous, return
- Apply stereotypes: Boundary, Control, and Entity
Static Model
- Design Class Diagrams at the design level
- Perform source code generation and reverse engineering (OPTIONAL)
- Generate source code from diagrams
- Generate diagrams from source code
- Synchronize source code and diagrams
- Create Object Diagrams
Dynamic Model
- Verify the static model
- Clarify method signatures
- Validate class diagrams
- Model dynamics at the method call level (sequence diagrams) based on use cases and the static analysis model
- Optimize diagram clarity
- Reduce the number of modeled scenarios
- Minimize lifelines
- Avoid complex nested blocks
- Hide unnecessary details
- Create State Machine diagrams (OPTIONAL)
- Define states and sub-states
- Model transitions: trigger, condition, and action
- Specify internal actions (entry, do, exit)
Patterns and Profiles (OPTIONAL)
- Apply "Gang of Four" patterns
- Use patterns defined within the project
- Implement user-defined patterns
- Import profiles from XML files
MDA and Source Code (OPTIONAL)
- Transform Class Diagrams into database schemas
- Generate SQL scripts from class diagrams
- Configure source code generation options
Group Work
- Version Enterprise Architect packages
- Track differences in project and documentation versions
- Use a repository for model storage
- Leverage collaboration tools
Requirements
Proficiency in UML modeling.
Testimonials (1)
Practise exercises in EA.