UML Schulungen

UML Schulungen

Unified Modelling Language (UML) courses
NobleProg is a contributor to OMG UML Certification Programme (OCUP 2)


Object-Oriented Analysis and Design using UML

Learned a lot of practical material. The exercises were very practical also.


UML Schulungsübersicht

ID Name Dauer Übersicht
359678 Business Process Modeling using BPMN and UML 14 hours Objective: This training course aims at helping business analysts to learn to model efficiently their business processes using BPMN as well as resources that are handled by their activities. Being conducted by an agile enterprise framework, business analysts learn during this course how to use appropriate BPMN notations and business extensions of UML in order to deal with their "business requirements" and coherently drive underlying design level activities. Introduction Definition of BPM for an Agile Enterprise Place of the OMG's BPMN 2.0 in this context Elements of the BPMN 1.x Basic Notions Process and Collaboration Diagrams, Participants : Pool, Lane Diagram repartition on the basis of abstraction levels Process, Sub-Process, Activity, Task Events and Gateways typology, Synchronisations, Connectors, Message Flows, Data Objects, Best Practices, Case Study : Model the Business Process and establish the corresponding bridge toward an Organised Process Advanced Elements using BPMN 2.0 BPMN 2.0 advanced concepts Choreography, Collaboration and Conversation Diagrams, Detailed events and gateway typologies, Interruption Management, Incident Management, Multi-instance Elements, Transaction and Compensation, Workflow Patterns, Case Study : Update the previous diagrams considering Interruption and Compensation mechanisms Simulate and Execute BPMN Models Process Models Simulation, Correspondences BPMN and UML, BPMN tools, Business Analysis Monitoring (BAM), Case Study : Check for the previous business process correctness and adjust them Conclusion Steps of an efficient BPMN and Resource Modeling, Key Elements of the BPMN within TOGAF® and Zachman frameworks, Using BPMN for SOA Evolution Management : the Roadmap Notice : The above training-mentoring sessions are conducted interactively using Business Modeling tools in order to ensure good level of traceability between business specifications and their execution. Concepts are first explained using basic examples and are then followed by solution drafts to your own problems. After this session, we can accompany you by reviewing and validating your solutions depending on your needs.
359688 Applying SysML with MAGICDRAW 21 hours This is a 3-day training covering principles of modeling, UML, SysML and use of MagicDraw following a case study, which demonstrates a typical model-based systems engineering approach. The course: Includes lectures and hands-on practice in using MagicDraw for systems modeling using SysML; Explains major SysML concepts and diagrams; Provides hands-on experience building system model examples; Shows how to trace model elements in different views; Explains how to use MagicDraw features efficiently; Is based on a consistent modeling case study. Audience: System architects, system engineers, software architects and other stakeholders who will create and use models. Methods: Presentations, discussions, and case study-based practical assignments. Course Materials: Slides, case study model, and practical assignment descriptions. Certificates: Each participant receives No Magic and NobleProg certificates indicating that he attended the training. Introduction Trainer and Participant Introductions Introduction to modeling Introduction to SysML Introduction to MagicDraw A Case Study Definition Structural System Decomposition Package Diagram Notation Decomposing System into Packages Modeling Package Dependencies Practical Assignment: Modeling Package Structure Analyzing User Needs Use Case Diagram Notation Identifying Actors Identifying Use Cases Use Case Relationships Practical Assignment: Modeling Use Cases Defining System Requirements From Use Cases to System Requirements Requirements Diagram Notation Specifying Requirements Defining Requirements Structure Verifying Requirements with Test Cases Requirements Relationships Practical Assignment: Modeling Requirements Defining Structural Blocks (Black Box View) Block Definition Diagram Notation Structural Blocks Modeling Block Properties Defining Relationships between Blocks Defining System Data Dictionary Practical Assignment: Modeling Black Box View of a System Modeling Block Structure (White Box View) Internal Block Diagram Visualizing Block Parts Linking Parts with Connectors Defining Ports Defining Item Flows and Interface Blocks Practical Assignment: Modeling White Box View of a System Modeling System Constraints Defining Constraint Blocks Binding Constraint Properties with Value Properties Executing Parametrics Practical Assignment: Modeling Parametrics Designing State-Based System Behavior State Machine Diagram Notation Identifying States Defining State Transition Events Specifying Signals Specifying Effects Executing State Machines Practical Assignment: Modeling Statemachines Designing Control and Data Flows Activity Diagram Defining Activities Specifying Parameters Defining Actions Modeling Control Flows Modeling Data Flows Executing Activities Executing Activities in Combination with State Machines and Parametrics Practical Assignment: Modeling Activities Designing Communications Sequence Diagram Notation Modeling Lifelines Modeling Messages Decomposing Interactions Using References Applying Interaction Fragments Defining Timing Constraints Practical Assignment: Modeling Interactions Modeling Cross-Cutting Constructs Logical and Physical Architectures Allocation relationship Allocations Display Options Identifying Types of Allocations Allocation Matrix Practical Assignment: Building Allocation Matrix Wrap up Summarizing Training Discussing Remaining Questions
359683 UML OCL 7 hours UML language architecture UML 2.0 Language Architecture OCL within architecture Object Constraint Language (OCL) OCL OCL Language Description Abstract Syntax Concrete Syntax Semantics Described using UML OCL Standard Library Use of OCL Expressions in UML Models Semantics Page Other OCL concepts Example usage and Exercises Typical cases in each diagaram type Exercises
359682 System Engineering using SysML and UML 2 21 hours Objective: Helping Analysts and Designers of the System Engineering domain to understand how to efficiently gather requirements then go through the embedded software design implementation on the basis of system specifications using UML 2 and SysML. This 3 days training aims at assisting system analysts to express efficiently their needs and designers to make the appropriate architectural design of the system on the basis of these needs. The resulting system architecture provides a good level of agility to the embedded system software in face of changes as it allows a coherent traceability of the business rules encapsulated in system functions and those of the usage choices (use cases) of the end-users toward the software implementation level. Introduction The System Development Life Cycle with the Harmony Process (IBM/Telelogic) Overview of the UML/SysML diagrams used in requirements gathering, system analysis and design of the System Engineering domain A Method based Framework for requirement gathering, system analysis and design Gathering Requirements and Transforming them into System Specifications Making business and system requirements traceable using the SysML requirement diagram Define the scope of the system composed of functions and use cases that invoke these functions Model the Life Cycle of the System that orchestrates transitions between its states where functions are triggered Prepare test cases using scenarios that realize Use Cases and System Functions Case Study : Model the System Scope and the usage of the system functions on the basis of requirements Transforming System Specifications into Design Level Components Model the Block Diagram of the system and refine it using internal blocks Elaborate the Communication Architecture between Sub-System using Parts, Ports and Interfaces Case Study : Elaborate the block and Internal Block diagrams on the basis of system specifications and by considering design level choices Model the description of white box Interactions at the design level Case Study : Model interactions between blocks and Internal Blocks on the basis of design level choices Mapping of Operations on the Components (Parts) of Blocks Elaborate the Parametric Diagram of the System Functions Case Study : Update the Block and Internal Block Diagrams on the basis of design level scenarios Conclusion Steps of requirement analysis and system specifications in system engineering Traceability between requirements and the software System Integration and Acceptance Tests of the requirements Notice: The above training-mentoring sessions are conducted interactively using Requirement Engineering and Modeling tools like Enterprise Architect (EA) in order to ensure good level of traceability between requirements and underlying solutions. Concepts are explained first using basic examples and are then followed by solution drafts to your own problems. After this session, we can accompany you by reviewing and validating your solutions depending on your needs. Provided by GooBiz
359679 Efficient Requirement Management using Agile Methods and Agile UML Modeling 21 hours Objective: This training course aims at helping product managers, products owners, business analysts, system architects and developers understand how to efficiently Manage Requirements on the basis of the product vision till guiding developers accurately in implementing them. More in detail, this course aims at assisting product managers in better defining the value propositions of their products on the basis of strategies and stakeholder needs. Business Analysts and product owners understand how to describe requirements of the product backlog then discover appropriate epics and user stories of the system while contributing to the required value creation. Along interactive case study exercises, participants learn how to describe in detail such requirements in order to validate correct understanding of needs and prepare system acceptance tests. Thus, only using a very common and productive UML profile, they learn to structure requirements in order to communicate efficiently with architects and developers through an iterative requirement gathering process. Audience: Product Managers Product Owners Business Analysts Anyone interetsted in the Requirements Management Process Introduction What is the Requirement Management Process ? Why Agile ? Business agility and agile software delivery : Definitions Linking Agile to Business : Business Motivation Model vs. Business Model Canvas, How to effciently use the Value Proposition Canvas for defining the Product Vision ? Business agility vs. agile software delivery principles What is Agile Not ? Impacts of alignment with strategies and capabilities Requirement Management in an Agile Context Scrum Life Cycle : Issues about completeness of requirements and traceability How productive models enhance communication in 'Agile' ? Business Extensions of Agile : Structuring Business Value Contribution of a User Story A Panorama of UML diagrams for modeling requirements Frameworks for tracing requirements toward software implementation and tests The 5 levels planning of an agile project (from Clarifying the Vision and Product Backlog to Tasks… and the Architecture Walking Skeleton) Managing Requirements within Agile Methods (Scrum, DAD) vs. the Unified Process (RUP) Roles, teams, environments Presentation of the Case Study for Structuring requirements and managing them using an iterative process How to describe the business vision and needs via traceable models ? Qualification of the requirements : The Kano model vs. the Value Proposition Canvas Structuring the Vision of the Product on the basis of strategies, environmental forces and trends Value proposition, key activities, key resources, revenue streams and cost structures,  Discovering the business scope of the product using the customer needs, gains and pains Describing business use cases using 'value streams' and 'value stages' Bridging the business scope of the product with expected 'value contributions' Case Study : Describing the vision of the product How to describe user needs via agile use case modeling (epics and user stories) ?  Agile Estimating and Planning Building and managing the product backlog / granularity of requirements Ahead of the sprint planning Creation of the sprint backlog Agile User Story Pattern : system scope (the subject), actors, use cases, user stories, acceptance criteria, the INVEST model The Walking Skeleton using Disciplined Agile Delivery : From Processes to Technology  How to find out epics and user stories on the basis of value streams ? Value contribution of epics and user stories Writing tasks : granularity and size using the SMART model Case Study : Discovering epics and user stories on the basis of value streams Validating and testing correct understanding of detailed specifications  Using an incremental requirement gathering process and the sprint backlog Rules for efficient epic, user story and architecture descriptions Diagrams for validating epics and user story descriptions  How to choose the right diagram ?  Refining features using use cases and relationships modeling Testing correct understanding of requirements using Test-Driven Requirements Given/When/Then structures and Operation Contracts for guiding developers in implementing requirements Coverage analysis and change management Case Study : Validating, testing and communicating detailed requirements to developers Conclusion Steps of efficient requirement gathering and system analysis processes  Traceability between requirements and analysis models  Patterns for gathering and testing requirements  Notice: The above training-mentoring sessions are conducted interactively using examples from Requirement Engineering and Modeling tools in order to ensure good level of traceability between requirements and underlying solutions. Concepts are first explained using basic examples and are then followed by solution drafts to your potential case. After this session, we can also accompany you by reviewing and validating your solutions depending on your needs.
145228 Data Modelling with UML 14 hours This course has been created for Subject Matter Experts which are required to model their data with UML. It covers consistent modelling techniques without going into implementation details. Short Introduction to Data Modelling in General Languages used to describe data ERD and other pre UML notations Why data modelling is not database modelling Concepts of storing the data (Relational, Hierarchical, Object Oriented, etc...) UML and Data Modelling Class Diagram Association Aggregation Composition Inheritance (Generalization and Specialization) Attributes Attribute and attribute types Attributes and relations Data Types Constraints on data Constraints on relations Views of data models Business View Modeller View Architect View Designers View Implementers Views (just short explanation) Other useful UML diagrams Composite structure diagram Profile diagram Avoid Redundancies Stereotyping vs Inheritance Tags Design Patterns (just introduction)
25110 Objektorientierte Analyse und Design mit UML 21 hours This course is intended for analysts, designers, developers, testers and project managers. It is an introduction to system modeling using UML. Based on selected systems (case study) following phases of system modeling are presented: from modeling requirements, through business process modeling and documentation of functional and non-functional requirements, to the analytical model. The next step is the design phase - static and dynamic modeling using project classes and the interaction between the system components. Training can be the basis for a comprehensive process modeling in enterprise systems through the use of UML in all phases of software development. Application and introduction to the web application What is the servlet and JSP page, what they are and how to use them What is the difference between a typical application, a Java web application Web application architecture Discussion of the issues of architecture within the web application Introduction to the discussion of the different layers and application layers and their applications Introduction to MVC What is the model, view and controller, what are the tasks defined within each of these three components of the model. Discussion of problems solvable with the help of the design pattern Servlets Introduction to the abstraction of the servlet, HTTP request handling process Basic HTTP Why HTTP? How does a servlet can handle the request? What type of query you can handle? The life cycle of a servlet Web application What is a web application? What is the application deployment descriptor? In what way the service control flow between the client and the application? What is the client and the server application architecture? Abstract representing the query and answer application. Attributes and HTTP requests and responses  Listener interface Flow Control and conversation Introduction to the problem of conversational client application and solutions to common problems through the use of session object Association asking HTTP session and the session life cycle JSP pages What is JSP? What are the common problems solved using JSP pages in a Web application? The role of JSP pages in the application and details of JSP technology behind What are bezskryptowe JSP page? Introduction to EL Introduction to libraries and JSTL custom tag What are tags in the servlet code? How to use JSTL tag libraries and what typical problems solved using this tag? How to define my own tags? Own custom tag library (option 1 day) Issues write your own tag libraries File format descriptor tags When you write your own tag library becomes a necessity? Deployment descriptor: web.xml A thorough discussion of the process of implementing a Web application and file structure implementation Web application security issues (option 1-2) Introduction to the topic of securing web applications Using the API, container, and declarative form of defining access to resources based on roles and users Examples of applications and implementation Filters Discussion of the principles of the declaration and implementation of filters in a web application Declaration principles filters in the deployment descriptor and discuss issues within the subject filters Korporacyjne wzorce projektowe (OPCJA 1 dzień) Overview and introduction to corporate design patterns Struts (OPTIONAL - 1-2days) The introduction of a lightweight MVC web application framework Define and discuss the role of the Shares, Validator and forms within the Struts framework, discussion of control flow within the application based on Struts and write a simple application using the Struts
25056 Praxisaspekte von UML 21 hours The course extends possessed knowledge of UML. During the training, we focus on the practical use of the language of the UML object-oriented analysis. Best Practices Software crisis Best Practices in Software Development Iterative development Management requirements Component-based architecture Visual modeling Verification of quality Change management RUP Characteristics of RUP Two dimensions of RUP UML for RUP Create an object model UML 2 as a way to represent the model The object model Methods of describing the model Practical analysis of the specification of the use cases Actor A use case Association Relations inculde, extend Some object-oriented concepts in practice Abstraction Encapsulation Generalization Polymorphism The system architecture Mapping the structure and behavior of the system Two categories of UML diagrams Modeling the relationship between structure and behavior Different levels of modeling behavior Mapping class analytical design elements Relations refine Building strong relationships between the results of the analysis phase and the design phase Modeling design classes Class Association Enumeration Forward/reverse engineering Subsystem Design Component The relationship of the delegation Connector Assembly Description of the aspects of concurrency in the system architecture Examples wykorzytania in activity diagrams, sequence and state machine Description of the aspects of the architecture of the dispersion The different perspectives of architecture description
25006 UML für den IT Business-Analysten 21 hours One of the fastest growing roles in the IT industry is the IT Business Analyst. Business Analysts are found in almost organizations and are important members of any IT team whether in the private or public sector.   This course provides a clear, step-by-step guide to how the Business Analyst can perform his or her role using state-of-the-art object-oriented technology. Overview of Software Development Process and Modelling Methodologies and their impact on the work of a Business Analyst Waterfall steps Analysis, Design, Implementation, Testing, Maintenance Agile approach to business analysis Who Are Business Analysts? Perspective on the BA Role The Dynamic (Behavioral) Model The Static (Structural) Model Structured Analysis The BA’s Perspective on Object Orientation Object Oriented Programming and its impact on modelling The UML Standard Cognitive Psychology and OO? Objects Attributes and Operations Operations and Methods Encapsulation Classes Relationships Generalization Association Aggregation Composition Polymorphism Use Cases and Scenarios Business and System Use Cases An Overview of Business Object-Oriented Modeling (B.O.O.M.) B.O.O.M. and SDLCs The B.O.O.M. Steps Sequencing the Steps What Do You Define First—Attributes or Operations? Analyzing End-to-End Business Processes Interviews During the Initiation, Analysis, and Test Phases Step 1: Initiation Business Requirements Document Template Step 1a: Model Business Use Cases Step 1a i: Identify Business Use Cases (Business Use-Case Diagram) Putting Theory into Practice Note to Rational Rose Users Case Study D1: Business Use-Case Diagrams Step 1a ii: Scope Business Use Cases (Activity Diagram) Case Study D2: Business Use-Case Activity Diagram with Partitions Scoping the IT Project with System Use Cases Step 1b: Model System Use Cases Case Study E1: Role Map Step 1b ii: Identify System Use-Case Packages (System Use-Case Diagram) Case Study E2: System Use-Case Packages Step 1b iii: Identify System Use Cases (System Use-Case Diagram) Case Study E3: System Use-Case Diagrams Step 1c: Begin Static Model (Class Diagrams for Key Business Classes) Step 1d: Set Baseline for Analysis (BRD/Initiation) Storyboarding the User’s Experience Step 2: Analysis The Use-Case Description Template Documenting the Basic Flow Use-Case Writing Guidelines Basic Flow Example: CPP System Review Case Report Documenting Alternate Flows Documenting Exception Flows Guidelines for Conducting System Use-Case Interviews Activity Diagrams for System Use Cases Related Artifacts Decision Tables Case Study F1: Decision Table Decision Trees Case Study F2: Decision Tree Condition/Response Table Business Rules Advanced Use-Case Features Case Study F3: Advanced Use-Case Features Life Cycle Requirements for Key Business Objects What Is a State Machine Diagram? Step 2a ii: 1. Identify States of Critical Objects Case Study G1: States Step 2a ii: 2. Identify State Transitions Case Study G2: Transitions Step 2a ii: 3. Identify State Activities Case Study G3: State Activities Step 2a ii: 4. Identify Composite States Case Study G4: Composite States Step 2a ii: 5. Identify Concurrent States Gathering Across-the-Board Rules with Class Diagrams Step 2b: Static Analysis Step 2b i: Identify Entity Classes Case Study H1: Entity Classes Step 2b ii: Model Generalizations Case Study H2: Generalizations Step 2b iii: Model Transient Roles Case Study H3: Transient Roles Step 2b iv: Model Whole/Part Relationships The Composite Structure Diagram Case Study H4: Whole/Part Relationships Step 2b v: Analyze Associations Case Study H5: Associations Step 2b vi: Analyze Multiplicity Case Study H6: Multiplicity Optimizing Consistency and Reuse in Requirements Documentation Step 2b vii: Link System Use Cases to the Static Model Case Study I1: Link System Use Cases to the Static Model Case Study I1: Results Step 2b viii: Add Attributes Meta-Attributes Case Study I2: Add Attributes Step 2b ix: Add Look-Up Tables Case Study I5: Analyze Look-Up Tables Step 2b x: Add Operations Case Study I7: Distribute Operations Step 2b xi: Revise Class Structure Case Study I8: Revise Structure Designing Test Cases and Completing the Project Step 2c: Specify Testing Structured Walkthroughs Decision Tables for Testing Case Study J1: Deriving Test Cases from Decision Tables Boundary Value Analysis Case Study J2: Select Test Data Using Boundary Value Analysis System Tests Beyond the System Tests Step 2d: Specify Implementation Plan Step 2e: Set Baseline for Development What Developers Do with Your Requirements Object Oriented Design Patterns Visibility Control Classes Boundary Classes Sequence Diagrams Communication Diagrams Other Diagrams Layered Architecture Interfaces Mix-Ins Implementing OO Using an OO Language Implementing OOA Using Procedural Languages Implementing a Database from OOA Using a RDBMS
25004 UML in Enterprise Architect (Workshops) 21 hours 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 substates transitions between states - events, conditions and actions internal actions(entry, do, exit) Ways to improve the appearance and transparency of the diagram change the apperance 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
24984 Analyse und Design mit SoaML 14 hours This course explains the OMG SoaML standards and shows how to model the SOA landscape. It introduces the language and then shows how to discover, design and implement services and infrastructure for SOA. This course always covers the newest version of the SoaML specification. Motivation behind SoaML Standards before SoaML Vendors standards and Open Source standards The IT and the business perspective on SOA Contracts and Interfaces Top-down and bottom-up approaches Service classification Compliance Level for SoaML SoaML UML Profile Specification Agent Attachment Capability Consumer Collaboration Collaboration Use Expose MessageType Milestone Participant Port Property Provider Request ServiceChannel ServiceContract ServiceInterface Service ServiceArchitecture Categorization Catalog Categorazation Category CategoryValue RAS Placeholders BMM Integration MotivationElement MotivationRealziation SoaML Metamodel
25154 Design Patterns 14 hours Es gibt reichlich bewährte Muster, um gut strukturierte objektorientierte Programme zu entwickeln. Manchmal genügt es, den richtigen Namen für ein Konstrukt zu finden, um hunderte von Stunden für Entwicklung und Tests zu sparen. Design Patterns sind ein Satz von Bauteilen und Vokabular zugleich. Lernziele Sie können die bekannten Design Patterns verwenden Sie können eigene Design Patterns in Ihrer Organisation etablieren Sie können abschätzen, wie Design Patterns Kosten sparen und die Softwarearchitektur vereinfachen helfen. Zielgruppe Softwareentwickle und -architekten, Business Analysts, Projektmanager Aufbau des Kurses Der Kurs konzentriert sich auf Anwendungsfälle und ihren Bezug auf ein bestimmtes Entwurfsmuster (Design Pattern). Die meisten Design Patterns sind in UML und einfachen Beispielen in Java erklärt. Bei Bedarf kann der gesamte Kurs auch auf eine andere Sprache übertragen werden. Der Kurs führt Sie durch den Quelltext einzelner Patterns und erklärt wie Sie einen Musterkatalog verwenden können. Einführung Der Ursprung von Design Patterns Patterns und Architekturebenen Beschreibung von Patterns Patterns finden und auswählen Design Patterns zum Erstellen von Objekten Factory Builder Factory Method Prototype Singleton Strukturelle Design Patterns Adapter Bridge Composite Decorator Facade Flyweight Proxy Patterns mit Fokus auf dem Verhalten Chain of Responsibility Command Interpreter Iterator Mediator Memento Observer State Strategy Template Method Visitor Observer Design Patterns etablieren Wann habe ich ein Design Pattern? formelle Beschreibung von Design Patterns Organisation des Musterkatalogs Nutzen von Patterns abschätzen
25008 UML Analyse und Design 21 hours This course has been created for software architects, programmers, software developers, project managers, analysts and anyone interested in understanding analysis and designing in UML. The course shows how to analyse clients' needs, formalize them in UML diagrams, create a model and ultimately design the implementation of the software. This is a general course covering all aspects of UML. Please browse our catalogue to see more specific courses. This course uses the newest version of the standard ( and is taught by an OMG Certified UML Professional (OCUP) trainer. There are no specific tools for this course, each of the delegates can use their favourite tool. By default, Sparx Enterprise Architect is used. Introduction to Modelling Models and Modelling Idea of meta-modelling UML documentation Inheritance Analysis and Design Actors and Use Cases Class and Object Diagrams Classes, objects, types of relations Object and Class Relationships Association, Aggregation, Composition Inheritance Dependency Interaction Communication diagram Interaction overview diagram Sequence diagram Timing diagrams Activity Diagrams State Diagrams Packages Component and Deployment Workshop From Analysis to Implementation Introduction to design patterns
24111 OCUP2 UML 2.5 Certification - Foundation Exam Preparation 21 hours Audience: Developers, programmers, business analysts, project managers, software architects, testers, people responsible for documentation or anyone involved in the software development process. Objectives: Prepares you to work with the most commonly encountered UML elements Teaches you how to create simple UML models Prepares you to be a member of a UML Development Team Why we model The Class Diagram Common Structure Type Dependency Namespace VisibilityKind (public, private, protected) MultiplicityElement Constraint Comment Simple Classifiers PrimitiveType DataType Enumeration EnumerationLiteral Interface InterfaceRealization Signal Reception Structured Classifiers Association Class Classification Generalization Feature Structural Feature Behavioral Feature Property Operation Parameter AggregationKind (Composition, Aggregation) Values LiteralBoolean LiteralInteger LiteralReal LiteralUnlimitedNatural LiteralNull LiteralString Opaque Expression The Object Diagram InstanceSpecification Slot The Package Diagram Packages Package PackageImport The Use Case Diagram Use Cases UseCase Actor Include The Activity Diagram Activities Activity ActivityFinalNode ActivityParameterNode ControlFlow InitialNode DecisionNode FlowFinalNode ForkNode JoinNode MergeNode ObjectFlow ObjectNode Actions Action CallBehaviorAction CallOperationAction, SendSignalAction AcceptEventAction Pin InputPin, OutputPin OpaqueAction The Sequence Diagram Interactions Interaction OccurrenceSpecification ExecutionSpecification ExecutionOccurrenceSpecification DestructionOccurrenceSpecification Lifeline Message MessageOccurrenceSpecification MessageSort MessageEnd Common Behavior CallEvent SignalEvent Trigger OpaqueBehavior The State Machine Diagram State Machines StateMachine State Transition Pseudostate: choice, junction, initial FinalState
24109 OCUP2 UML 2.5 Certification - Intermediate Exam Preparation 14 hours Audience: Developers, programmers, business analysts, project managers, software architects, testers, people responsible for documentation or anyone involved in the software development process. Objectives: Prepares you to work with a broad range of UML elements Teaches you how to create complex UML models Prepares you to become a qualified senior member of a UML Development Team. Composite Structure Diagrams (Actions, Ports, and Structured Classes) Internal structures Structured classifier Connectors Modelling ports Port Connector End Structured Classes Invocation Actions Invocation Action Trigger Component Diagrams Basic Components Component (without Packaging) Connector Realization Other Basic Component concepts Action Models Intermediate Action Invocation Actions Apply Actions Object Actions Structured Feature Actions Link Identification Read Link Actions Write Link Actions Variable Actions Other Intermediate Action concepts Activity Diagrams Object Nodes Controls Partitions Other Activity concepts Structured Activities Structured Activity Node Conditional Node Loop Node Other Structured Activity concepts Interaction Diagrams Interaction fragments Combined Fragments Gates Interaction Occurrence Other Fragment concepts State Machine Diagrams (Behavioural) Behaviour State Machines State and Finite State Pseudo State and Final State Transition Connection Point Reference State Machine Other Behaviour State Machine concepts One-region State Machines Region Deployment Diagrams (without Components) Artifacts and Nodes Artifacts Nodes Profiles Profile Extension Stereotype and metaclass Profile Application Other Profile concepts
24113 UML 2.0 Certification - Advanced Exam Preparation 14 hours Audience: Developers, programmers, business analysts, project managers, software architects, testers, people responsible for documentation or anyone involved in the software development process. Objectives: Prepares you to work with a broad range of UML elements Teaches you how to create complex UML models Allows you become a qualified to be a senior member of a UML Development Team. Class Diagrams Association Classes Power Types Generalization set Power type Composite Structure Diagrams Collaborations Collaboration Collaboration Occurrence Component Diagrams Packaging Components Component (for Packaging Components) Actions Modelling Complete Actions Accept Event Actions Object Actions Link Identification Read Link Actions Write Link Actions Raise Exception Action Other Complete Component concepts Activity Diagrams Complete Activity Structures Elements Constraints Flows Object Nodes Data Stores Parameter Sets Control Nodes Interruptible Regions Other Complete Activity concepts Structured Nodes Structured Nodes Exceptions and Expansion Regions (Extra Structured Activities) Exceptions Expansion Regions Deployment Diagrams (with Components) Component Deployments Deployment Deployment Specification State Machine Diagrams (Protocol state machines) Protocol State Machines Protocol State Machine Constraints (In protocol state machine) Other Protocol State Machine concepts Miscellaneous Advanced Constructs Flow Diagrams Information Item Information Flow Physical System Model Templates Template Template Parameters Language Architecture UML language architecture UML 2.0 Language Architecture Infrastructure library Relationship to other MDA standards OCL within architecture Diagram interchange Object Constraint Language (OCL) OCL OCL Language Description Abstract Syntax Concrete Syntax Semantics Described using UML OCL Standard Library Use of OCL Expressions in UML Models Semantics Page Other OCL concepts
25172 Business Process Analysis mit UML und BPMN 14 hours Teilnehmer: Manager, welche BPMN Diagramme verstehen möchten, Business Consultants, Business Analysts, Business Process Engineers, System Analysts und jeder, der mit dem analysieren und planen von Business Prozessen mit standardized, unified modelling notation zu tun hat. Ziele: Erstellen von high-quality Prozessdiagrammen Modelle in BPMN process notation Erfassen der "as-is process information" Implementieren des optimierten Prozess-Flows für arbeitsintensive Prozesse Vereinfachen von komplexen Prozessdefinitionen mithilfe der Aufteilung in umgänglichere Abschnitte UML Business use case diagrams UML activity diagrams detailing the use case Business Entities definitions depicted with Class Diagrams Map the model into system use cases BPMN BPMN modelling techniques BPMN modelling shape overview Swimlane generation and viewing BPMN text objects, data objects, annotations, and attributions Basic Process optimization Process design best practices

Kommende Kurse

CourseSchulungsdatumKurspreis (Fernkurs/Schulungsraum)
Practical aspects of UML - BernMo, 2016-11-07 09:302850EUR / 3500EUR
Design Patterns - BaselSa, 2016-11-19 09:302080EUR / 2360EUR
Business Process Analysis with UML and BPMN - ZürichDi, 2016-12-20 09:301850EUR / 2350EUR
UML Schulung, UML boot camp, UML Abendkurse, UML Wochenendkurse , UML Lehrer , UML Privatkurs, UML Training, UML Seminare,UML Kurs, UML Seminar