IT / Modelling / OMG / UML / Notation and Concepts
| ID | 2757716 |
|---|---|
| Classroom | 3 days 9:00-16:30 |
| Webinar | 5 days 9:00-12:30 |
| Method | Lecture with examples and exercises. |
| Prequisite | Knowledge in software development, project experience |
| Audience | Programmers, software architects, managers, |
Unified Modeling Language (UML) is a standardized, general-purpose modeling language for software engineering and modeling. The Unified Modeling Language includes a set of graphic notation techniques to create visual models of object-oriented software-intensive systems. The Unified Modeling Language (UML) offers a standard way to visualize a system's architectural blueprints, including elements such as: activities
actors, business processes, database schemas, (logical) components, programming language statements, and reusable software components. UML has 14 types of diagrams divided into two categories. Seven diagram types represent structural information, and the other seven represent general types of behavior, including four that represent different aspects of interactions. This training covers these diagrams and their elements, as well as their relationships and their usage scenarios in the software design life cycle.
Diagrams: Class Diagram, Package Diagram, Object Diagram - Node Types: Class, Interface, InstanceSpecification, Package - Path Types: Aggregation, Association, Composition, Dependency, Generalization, InterfaceRealization, Realization, Usage, Package Merge, PackageImport
Component Diagram: Component, Interface, ComponentRealization, Interface Realization, Usage Dependencies, Class, Artifact, Port - Composite Structure Diagram: Part, Port, Collaboration, CollaborationUse, Connector, Role Binding - Deployment Diagram: Artifact, Node, Deployment Specification, Association, Dependency, Generalization, Deployment, Manifestation
Activity Diagram: Action, Activity and ActivityPartition, Modeling the Logical Flow (ControlFlow and ObjectFlow, Nodes: ActivityFinal, ActivityNode, ControlNode, DecisionNode, FinalNode, FlowFinal, ForkNode, InitialNode, JoinNode, MergeNode), Modeling Data (DataStore, ObjectNode), Modeling Containment (InterruptibleActivityRegion, ExceptionHandler, ExpansionRegion) - Use Case Diagram: Actor, Extend/Include Relationship, UseCase
State Machine, Typology of States (Choice / History / Initial/ Junction Pseudostate, Composite State, Final State), Transition between States, Actions (Receive / Send Signal Action)
Sequence Diagram: Frame, Lifeline, Execution Specification, InteractionUse, CombinedFragment, Continuations, Coregion, Modeling Constraints (TimeConstraint, DurationConstraint, StateInvariant), Modelling Messags (Message, Found / Lost Message) - Communication Diagram: Frame, Lifeline, Message Interchange
Interaction Overview Diagram: Frame, Interaction and InteractionUse - Timing Diagram: Frame, Message, Lifeline, Modeling Time
Das Dozenten- und Autoren-Team Marco Skulschus (Studium der Ökonomie in Wuppertal und Paris) und Marcus Wiederstein (Studium der Elektrotechnik in Bochum und Dortmund) haben schon viele Seminare im Software-, Daten- und Prozess-Modellierung mit den Techniken der OMG (UML und BPMN) und des W3C (XML Schema, RDF/OWL) konzipiert und führen sie in der DACH-Region durch. Dazu veröffentlichen sie seit 2002 immer wieder Fachbücher zu Softwareentwicklung und Datenbanken.
In ihren Projekten entstanden verschiedene betriebliche Anwendungen und seit mehreren Jahren hauptsächlich Berichtssysteme und Data Warehouse-/OLAP-Lösungen. Sie sind für Kunden in DACH tätig und leiten dabei indische Entwicklerteams.
