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
Creating and Configuring EAP Files
- Creating and saving Enterprise Architect project files
- Understanding different types of views
- Navigating the program interface, including menus, toolbars, the Toolbox, the Project Browser, and other windows
- Docking and hiding windows
Working with Models and Diagrams
- Utilizing predefined models
- Managing packages (views) and diagrams
- Adding elements to models and diagrams
- Different methods for removing items and understanding their implications
- Diagrams saving procedures
Requirements Management
- Techniques for requirements gathering
- FURPS requirements categories
- Creating Requirements Diagrams
- Defining relationships between requirements
- Aggregation
- Dependency
- Enhancing diagram aesthetics
- Layout diagram optimization
- Color-coding requirement status
- Toggling package name visibility
- Creating and managing matrix relationships
- Documenting requirements
- Generating HTML pages
- Creating printable versions
- Advanced requirement management
- Defining custom requirement types
- Customizing requirement status
- Tracking requirements
- Documenting requirements
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 logic
- Improving diagram presentation
- Adjusting levels of detail
- Reducing 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)
- Stereotypes graphic library
- Adding libraries to the project
- Custom graphics for stereotypes
Use Cases and Documentation
- Modeling functional requirements
- Defining the system scope
- Actors and their relationships
- Identifying use cases
- Association between "actor" and "use case" and associated properties
- Relationships between use cases: include, extend, and generalization
- Automatic numbering
- Generating use case scenarios and activity diagrams based on them
- Generating documentation
- Using document templates
Analytical Model
- Class diagrams at the domain model level
- Classes, methods, attributes, abstract classes, and interfaces
- Associations and their characteristics
- Other 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
- Static model verification
- Clarifying method signatures
- Verifying class diagrams
- Dynamic modeling of method calls (sequence diagrams) based on use cases and the static analysis model
- Enhancing diagram clarity
- Reducing the number of modeled scenarios
- Minimizing the number of lifelines
- Avoiding complex nested blocks
- Hiding non-essential 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
- 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 based on class diagrams
- Source code generation options
Group Collaboration
- Enterprise Architect package versioning
- Comparing differences in project and documentation versions
- Using repositories to store models
- Collaboration tools
Requirements
Proficiency in UML modeling techniques.
Testimonials (1)
Practise exercises in EA.