2d8d1de3__Courses___NobleProg_Worldwide__Overview
[ID] 2494 [Name] UML in Enterprise Architect (workshops) [Duration] 21 hours [Overview] 
The course is designed for analysts, designers, developers, testers and project managers. The workshop presents a problem analysis, design and documentation systems using UML and Enterprise Architect of Sparx Systems. During the training will be presented to the advanced capabilities of the program (such as MDA, profiles, XMI), and best practices that can greatly simplify and accelerate modeling. The training method: Lecture 10%, 90% workshop Create and configurable have a draft EAP Create and save a project file of Enterprise Architect Discussion of the file structure of the project Types of views available in the project The program's interface: menus, toolbars, Toolbox, Project Browser and other windows Docking and hiding windows Working with a model, diagram Predefined patterns model Creating packages (views) and add diagrams Adding elements to the model and diagram Different ways of removing the items and their consequences Saving diagrams Collecting requirements Methods for requirements gathering Categories requirements by FURPS Diagram requirements (Requirements Diagram) Ways of presenting the requirements and the relationships between requirements aggregation dependency realization Ways to improve the appearance and transparency of the diagram correction layout diagram use color to distinguish between status requirements enable / disable the package names Create and manage a matrix relationship Documentation requirements in the form of HTML pages and printable version Advanced management requirements create your own types of requirements create your own status requirements the relationship between the tracking requirements documenting the ways to implement the requirements Business process modeling, architecture Handling exceptions, interrupting the flow Partitions track Concurrent flows and decision-making Control and cash flow objects, pins Creating a complex process, abstracting The use of stereotypes, the process for doing Working with activity diagram Ways to improve the appearance and transparency of the diagram diagrams at different levels of detail reducing the amount of detail different ways to show the complexity of the process The use of components and deployment diagrams The initial architecture of the system - logical and physical nested components relationship delegation port, part interface communication paths extracting parts of the diagram Modeling requirements for security, performance, reliability of the system The use of non-standard implementation of stereotypes in diagrams the use of stereotypes graphics library connect the library to the project use your own graphics stereotypes and their high-speed connectivity to the diagram elements Use cases and their documentation Modeling functionality with the use case diagram Determining the scope of the system Identify the actors and the relationships between them Identifying use cases Association "actor - use case" and its properties The relationship between use cases: include, extend, generalization Automatically number of use cases Creating a use case scenarios and generate diagrams from them (activity, state machine, sequence) Connecting a use case scenarios from external files Generating the documentation Create templates Analysis field Require the use of tabs to determine the liability classes Identification of the major classes / objects of the system. Use the diagram of communication types of statements: asynchronous, synchronous, return define and modify the numbering sequence of messages the use of stereotypes analysis: Boundary, Control and Entity Introduction to the design of the system Static model Create a class diagram based on the analytical model and use cases Class diagram and source code generation association relationship and its characteristics other relationships: aggregation, composition, generalization, dependency, class associative use appropriate conventions for naming classes and their components show and hide the classes Forward/Reverse engineering generating source code from the diagram generate flow chart from source code synchronization code and diagram object diagrams Dynamic Model Verification of the static model clarify the method signatures verification of the class diagram The dynamic modeling at the level of method calls (sequence diagram) based on use cases and static analysis model Ways to improve the appearance and transparency of the diagram reducing the number of modeled scenarios reducing the number of lines of life avoiding complex nested blocks hiding the details and references to the block-by-reference State machine diagram determination of states and sub-states transitions between states - events, conditions and actions internal actions(entry, do, exit) Ways to improve the appearance and transparency of the diagram change the appearance of lines decomposition states Creating and using patterns and profiles The use of design patterns "Gang of Four" The use of patterns defined in the project Identifying the mobilization patterns by a component of cooperation (collaboration) Create your own patterns Importing profiles from XML files MDA, support for technology and work with source code Transformation of the class diagram for the database schema using MDA Generate SQL script that creates the database Generating source code - available options Groupware Use tools Enterprise Architect package versioning Determining the differences in the versions of the project, the creation of documentation Using a repository to store the model Tools to support collaboration
UML Training Courses | NobleProg Worldwide
Overview