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 for Government
- Create and save an Enterprise Architect project file.
- Types of views.
- Program interface: menus, toolbars, Toolbox, Project Browser, and other windows.
- Docking and hiding windows.
Working with a Model, Diagram for Government
- Predefined models.
- Packages (views) and diagrams.
- Adding elements to the model and diagram.
- Different methods of removing items and their consequences.
- Saving diagrams.
Requirements Management for Government
- Methods of requirements gathering.
- FURPS requirements categories.
- Requirements Diagram.
- Relationships between requirements:
- Aggregation.
- Dependency.
- Improving the appearance of a diagram:
- Layout diagram.
- Color status requirements.
- Enable or disable package names.
- Create and manage a matrix relationship.
- Documenting requirements:
- HTML pages.
- Printable version.
- Advanced requirement management:
- Custom types of requirements.
- Custom requirements status.
- Tracking requirements.
- Documenting requirements.
Business Process Modeling, Architecture for Government
- Activity Diagram.
- Compound activities.
- Control flows, object flows.
- Handling exceptions, interrupt flow.
- Partitions.
- Concurrent flows and decision-making.
- Improving the appearance of a diagram:
- Different levels of detail.
- Reducing the amount of detail.
- Complexity of the process.
- Components and Deployment diagrams.
- The initial architecture of the system - logical and physical:
- Nested components.
- Delegation and assembly.
- Port.
- Interface.
- Communication paths.
- Non-standard implementation of stereotypes in diagrams (optional):
- Stereotypes graphic library.
- Adding the library to the project.
- Custom graphics stereotypes.
Use Cases and Their Documentation for Government
- Functional requirements modeling.
- Scope of the system.
- Actors and the relationships between them:
- Identifying use cases.
- Association "actor - use case" and its properties.
- Relationships between use cases: include, extend, generalization.
- Auto numbering.
- Use Case scenarios and activity diagrams generated based on them.
- Documentation generation.
- Document templates.
Analytical Model for Government
- 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 for Government
- Class Diagram at the design level.
- Source code generation and reverse engineering (optional):
- Source code generation from the diagram.
- Diagram generation from source code.
- Source code and diagram synchronization.
- Object Diagrams.
Dynamic Model for Government
- Static model verification:
- Clarify method signatures.
- Verification of the class diagram.
- Dynamic modeling at the level of method calls (sequence diagram) based on use cases and static analysis model.
- Improving the appearance of a diagram:
- Reducing the number of modeled scenarios.
- Reducing the number of lifelines.
- Avoiding complex nested blocks.
- Hiding 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) for Government
- "Gang of Four" patterns.
- Patterns defined in the project.
- User patterns.
- Importing profiles from XML files.
MDA, Source Code (Optional) for Government
- Class Diagram to database schema transformation.
- SQL script generation based on class diagram.
- Source code generation - available options.
Group Work for Government
- Enterprise Architect package versioning.
- Differences in the versions of the project, documentation.
- Using a repository to store the model.
- Collaboration tools.
Requirements
Developing modeling skills in UML for government projects ensures that public sector workflows and systems are accurately represented and effectively managed. These skills are essential for creating clear, standardized diagrams that enhance governance and accountability in technical documentation and project management.
21 Hours
Testimonials (1)
Practise exercises in EA.
