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
Creating and Configuring EAP Files
- Creating and saving Enterprise Architect project files
- Understanding various view types
- Exploring the program interface: menus, toolbars, Toolbox, Project Browser, and other windows
- Managing window docking and visibility
Working with Models and Diagrams
- Utilizing predefined models
- Managing packages (views) and diagrams
- Adding elements to models and diagrams
- Understanding different methods for removing items and their implications
- Save diagrams effectively
Requirements Management
- Techniques for gathering requirements
- FURPS requirement categories
- Creating Requirements Diagrams
- Defining relationships between requirements
- Aggregation
- Dependency
- Enhancing diagram aesthetics
- Diagram layout optimization
- Color-coding requirement statuses
- 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 statuses
- Tracking requirement changes
- Documenting requirements comprehensively
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 appearance
- Adjusting levels of detail
- Minimizing unnecessary details
- Managing process complexity
- Component and Deployment diagrams
- Establishing the initial system architecture - logical and physical
- Nested components
- Delegation and assembly
- Ports
- Interfaces
- Communication paths
- Implementing non-standard stereotypes in diagrams (OPTIONAL)
- Using stereotype graphic libraries
- Adding libraries to the project
- Creating custom graphical stereotypes
Use Cases and Documentation
- Modeling functional requirements
- Defining the system scope
- Actors and their relationships
- Identifying use cases
- Association between actors and use cases, including properties
- Relationships between use cases: include, extend, generalization
- Automatic numbering
- Use Case scenarios and generating activity diagrams based on them
- Generating documentation
- Utilizing 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
- Verifying the static model
- Clarifying method signatures
- Validating class diagrams
- Dynamic modeling at the method call level (sequence diagrams) based on use cases and the static analysis model
- Enhancing diagram appearance
- Reducing the number of modeled scenarios
- Minimizing lifelines
- Avoiding complex nested blocks
- Hiding unnecessary details
- State Machine diagrams (OPTIONAL)
- States and sub-states
- Transitions between states: triggers, conditions, and actions
- Internal actions: entry, do, and exit
Patterns and Profiles (OPTIONAL)
- 'Gang of Four' patterns
- Project-defined patterns
- 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: exploring available options
Collaborative Work
- Versioning Enterprise Architect packages
- Reviewing differences across project and documentation versions
- Using repositories for model storage
- Utilizing collaboration tools
Requirements
Proficiency in UML modeling is required.
21 Hours
Testimonials (1)
Practise exercises in EA.