the engaging method of teaching ensured that all attending the course were involved in the learning process
Matthew Cuff - Altran UK
Unternehmensarchitektur Schulungen
Enterprise Architecture, EA, courses
Erfahrungsberichte
Unternehmensarchitektur Schulungsübersicht
| Code | Name | Dauer | Übersicht |
|---|---|---|---|
| 3166 | 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 |
| soaarch01 | SOA Architect | 35 hours | This 5 day course is designed to give an understanding of the mechanics of Service Oriented Architecture. It includes the technical design of SOA based architectures and service oriented solutions to business problems. Service Oriented Architecture and Computing Service Oriented Computing Terminology Service Oriented Analysis and Design Requirements and impact of adopting SOA Enterprise Service Bus Web Service and REST Services SOA Connection Points SOA Technology XML and XML Schema Web Services JAX-WS and WSDL REST Services JAX-RS and WADL Discovery and Service Registries Enterprise Service Bus (ESB) SOA Design and Architecture SOA Model Services and Service Capabilities WSDL first or code first design Principles of Service Orientation Service coupling Handling state Service discovery Advanced SOA Design and Architecture SOA Architecture types SOA Design Patterns Message types Data transformation SOA Workshop This hands on workshop consists of a number of individual and group exercises which allow the technologies and principles described in the previous modules to be applied. Participants can also bring real world problems to the workshop. |
| dodafint | Department of Defense Architecture Framework (DoDAF) Overview | 21 hours | The Department of Defense Architecture Framework (DoDAF) is an architecture framework for the United States Department of Defense, that provides structure for a specific stakeholder concern through viewpoints organized by various views. DoDAF defines a set of views that act as mechanisms for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal or graphical means. It is especially suited to large systems with complex integration and interoperability challenges, and is apparently unique in its use of operational views detailing the external customer's operating domain in which the developing system will operate. DoDAF Architecture Framework Introduction DoDAF Architecture Vision DoDAF Architecture Resources Relationships to Other Architecture Frameworks DoDAF Architecture Background Architecture Development Methodologies DoDAF View points and Models DM2 - DoDAF Meta-Model DoDAF Roles - Manager, Architect, Developer |
| softeng | Software Engineering | 35 hours | Software Engineering starts where programming stops. In this course you will learn a solid foundation in Software Engineering. It builds a bridge from programming to solid engineering practices. The course gives you an overview of basic concepts and vocabulary typically used in the field. During the course, you will learn to use many techniques to plan, implement and validate software projects and to evaluate and improve development processes. Audience: This course is intended for software developers with various backgrounds who know at least one programming language. Day 1: Process Introduction What is Systems Engineering? What is Software Engineering? Why is Software Engineering difficult? System requirements System modeling Software Engineering Processes What is a Software Development Process? Traditional Processes Agile Processes Processes for building High-Integrity Systems Standards & certification systems High-Integrity Systems What are High-Integrity Systems? The role of QM culture Reasons for errors Critical systems standard Reliability engineering Software Maintenance Day 2: Planning Requirements User requirements Elicitation/analysis of user requirements System requirements Software requirements Specification of software Requirements process Tools to manage requirements Software Design Conways Law Design patterns Textual modeling tools Principles of OO design Design tools Common architectures Modeling Planning an architecture UML graphical representations Non-UML graphical representations Day 3: Code Software Construction How to take a design into code Programming best practices Abstraction of code Programming workflow Configuration Management What is Configuration Management? Configuration Management in ISO9000 and CMMI CASE tools for planning, design & QA CASE tools for writing software Version control with SVN System Integration Code for High-Integrity Systems Preventing errors Catching errors Reducing the impact of errors Typical problems with code for High-Integrity Systems Code quality metrics Code size metrics Code complexity metrics Non-code metrics Static analysis Day 4: Verification & Validation Reviews Fundamentals of VV Independent Verification & Validation Design and requirement reviews Code inspections Software Walkthroughs Audits Other V & V methods Testing High-Integrity Systems Documents regarding safety Scenarios Argumentation for safety Reviews of High-Integrity Systems Predicting reliability Formal methods Costs of V + V Automated Testing Why test? Automatic vs manual tests Incremental testing Types of tests Testing tools Test Harnesses Day 5: Management Project Management What is Project Management? Customer handover Standards (PMP, PRINCE2) Time management Cost management Risk management Project documentation Process Evaluation The function of process evaluation Acting on the metric Process metrics Process evaluation standards & frameworks (CMMI, ISO 9001, TickIt+) Process evaluation meetings Summary and Conclusions |
| softengret | Software Engineering, Requirements Engineering and Testing | 63 hours | Software Engineering 5 days Day 1: Project Management Project versus line management and maintenance and support Project definition and project forms Management – general rules and project management Management styles What is special for IT projects? Basic project process Iterative, incremental, waterfall, agile and lean project process Project phases Project roles Project documentation and other artefacts Soft factors and peopleware PRINCE 2, PMBOK, PMI, IPMA and other project standards Day 2: Business Analysis and Requirements Engineering Fundamentals Defining business goals Business analysis, business process management, business process improvement The boundary between business and system analysis System stakeholders, system users, system context and system boudaries Why are requirements necessary? What us requirements engineering The boundary between requirements engineering and architectural design Where is requirements engineering often hidden? Requirements engineering in iterative, lean, and agile development and in continuous integration – FDD, DDD, BDD, TDD Basic requirements engineering process, roles and artefacts Standards and certifications: BABOK, ISO/IEEE 29148, IREB, BCS, IIBA Day 3: Architecture and Development Fundamentals Programming languages – structural and object-oriented paradigms Object-oriented development – how much is history, how much is the future Modularity, portability, maintainability and scalability of architectures Definition and type of software architectures Enterprise architecture and system architecture Programming styles Programming environments Programming mistakes and how to avoid and prevent them Modelling architecture and components SOA, Web Services and micro-services Automatic build and continuous integration How much architecture design is there on a project? Extreme programming, TDD and re-factoring Day 4: Quality Assurance and Testing Fundamentals Product quality: what is it? ISO 25010, FURPS etc. Product quality, user experience, Kano Model, customer experience management and integral quality User-centred design, personas and other ways to make quality individual Just-enough quality Quality Assurance and Quality Control Risk strategies in quality control The components of quality assurance: requirements, process control, configuration and change management, verification, validation, testing, static testing and static analysis Risk-based quality assurance Risk-based testing Risk-driven development Boehm’s curve in quality assurance and in testing The four testing schools – which suits your need? Day 5: Process Types, Maturity and Process Improvement The evolution of IT process: from Alan Turing through Big Blue to lean startup Process and process-oriented organization The history of processes in crafts and industries Process modelling: UML, BPMN and more Process management, process optimization, process re-engineering and process management systems Innovative process approaches: Deming, Juran, TPS, Kaizen Is (process) quality free? (Philip Crosby) The need and history of maturity improvement: CMMI, SPICE and other maturity scales Special types of maturity: TMM, TPI (for testing), Requirements Engineering Maturity (Gorschek) Process maturity versus product maturity: any correlation? any causal relationship? Process maturity versus business success: any correlation? any causal relationship? A forsaken lesson: Automated Defect Prevention and The Next Leap in Productivity Attempts: TQM, SixSigma, agile retrospectives, process frameworks Requirements Engineering - 2 days Day 1: Requirements Elicitation, Negotiation, Consolidation and Management Finding requirements: what, when and by whom Stakeholder classification Forgotten stakeholders Defining system context – defining requirements sources Elicitation methods and techniques Prototyping, personas, and requirements elicitation through testing (exploratory and otherwise) Marketing and requirements elicitation – MDRA (“Market-Driven Requirements Engineering”) Prioritising requirements: MoSCoW, Karl Wiegers and other techniques (including agile MMF) Refining requirements – agile “specification by example” Requirements negotiation: types of conflicts, conflict-solving methods Solving internal incongruence between some types of requirements (e.g. security versus ease of use) Requirements traceability – why and how Requirements status changes Requirements CCM, versioning and baselines Product view and project view on requirements Product management and requirements management in projects Day 2: Requirements Analysis, Modelling, Specification, Verification and Validation Analysis is the thinking and re-thinking you do between elicitation and specification Requirements process is always iterative, even in sequential projects Describing requirements in natural language: risks and benefits Requirements modelling: benefits and costs The rules for using natural language for requirements specification Defining and managing requirements glossary UML, BPMN and other formal and semi-formal modelling notations for requirements Using document and sentence templates for requirements description Verification of requirements – goals, levels and methods Validation – with prototyping, reviews and inspections, and testing Requirements validation and system validation Testing - 2 days Day 1: Test Design, Test Execution and Exploratory Testing Test design: after risk-based testing, choosing the optimum way to use the time and resources available Test design “from infinity to here” – exhaustive testing is not possible Test cases and test scenarios Test design on various test levels (from unit to system test level) Test design for static and for dynamic testing Business-oriented and technique-oriented test design (“black-box” and “white-box”) Attempting to break the system (“negative testing”) and supporting the developers (acceptance testing) Test design to achieve test coverage – various test coverage measures Experience-based test design Designing test cases from requirements and system models Test design heuristics and exploratory testing When to design test cases? – traditional and exploratory approach Describing test cases – how much detail? Test execution – psychological aspects Test execution – logging and reporting Designing tests for “non-functional” testing Automatic test design and MBT (Model-Based Testing) Day 2: Test Organization, Management and Automation Test levels (or phases) Who does the testing, and when? – various solutions Test environments: cost, administration, access, responsibility Simulators, emulators and virtual test environment Testing in agile scrum Test team organization and role Test process Test automation – what can be automated? Test execution automation – approaches and tools |
| updmint | Überblick über Unified Profile for DoDAF/MODAF (UPDM) | 21 hours | UPDM is an Object Management Group (OMG) initiative to develop a modeling standard that supports both the USA Department of Defense Architecture Framework (DoDAF) and the UK Ministry of Defence Architecture Framework (MODAF). The modeling standard is called the Unified Profile for DoDAF and MODAF (UPDM). Introduction to UPDM Compliance Normative References Terms and Definitions Symbols and Acronyms Additional Information Additional Materials Overview of this Specification Acknowledgements Language Architecture Introduction Philosophy Core Principles Profile Structure Representing Stereotype Constraints UML Constraint Representation Important Areas of the Architecture UPDM Profile DoDAF Class Library UPDM L1 ActualProject |
| sysengsysmluml2 | 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. |
| modafint | MOD Architecture Framework (MODAF) Überblick | 21 hours | MODAF is an internationally recognised enterprise architecture framework developed by the MOD to support Defence planning and change management activities. It does this by enabling the capture and presentation of information in a rigorous, coherent and comprehensive way that aids the understanding of complex issues. The audience: Enterprise Architects, the principal customers for MODAF views, who need to both correctly interpret standard MODAF views provided to them and to specify and control the tasks required to create new views Architectural modellers who need guidance on the creation and interchange of MODAF views (including for example: architecting principles, view coherence rules and tool selection criteria) Tool developers and engineers who are implementing architectural data repositories for storing and manipulating MODAF Architecture data elements Trainers and educators who require reference material in order to appropriately train and support the previous types of MODAF users MODAF users who wish to contribute to the development of MODAF Managers who need to understand what views are required to answer their particular questions Introduction Purpose Background Overview of MODAF MODAF Framework MODAF Viewpoints Relationship Between MODAF Viewpoints Key Supporting Elements to MODAF Ensuring Architectures are MODAF compliant MODAF Documentation Suite Benefits of Developing MODAF Architectures Quantifying MODAF Benefits Benefits to MOD communities of Interest Approach to developing MODAF Architectures General Approach to Developing MODAF Architectures Practical Applications of General Approach to MODAF Architectures COI-Specific Architecture Processes |
| sysmlmd | 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 |
| technicalarc | Technical Architecture and Patterns | 21 hours | With the emergence of very complex distributed systems, complexity of a single system moved to the complexity of the architecture of the group of systems. This course covers the relationship of Software Architecture with Technical Enterprise Architecture. These two areas are interrelated in a way which currently is not well described. For example, splitting complex monolithic system into two systems communicating via web services will trigger substantial changes to both the new systems, and the architecture between them. This course will cover trade-offs, currently common patterns and solutions for managing complex systems and communication within and between them. Overview System and Component Cohesion System/component Dependencies Software Architecture Technical Architecture Enterprise Architecture SOA and Micro services architecture Relationships between above concepts Logic redudancy vs dependency Data reduancy vs dependency Software Architecture Fundamentals clarification of terms: architecture, design, modeling orthogonality conways Law Common Architectures modular decomposition hierarchical architecture centralised (Mediator Pattern) event-based architecture interrupt-based OSI client/server layer model Principles of OO Design DRY, SRP encapsulation program against an interface Liskovs principle Law of Demeter Design Patterns what are Design Patterns Creational Patterns Structural Patterns Behavioural Patterns Model-Controller-View (MCV) Design Tools Domain specific language Lexical Analysis CRC cards scenarios Use Case descriptions UML Graphical Representations Class Diagram Sequence Diagram aggregation diagram UML tools Non-UML Graphical Representations ER-modeling State Machine data flow architectural model Design and Maintenance Lehmanns Laws Architectural Antipatterns Refactoring Strategies SOA and Integration Patterns Integration technologies and methods Synchronous/Asynchronous More details direct communication patterns Direct and brokered communication Message Queuing ESB Deployment Patterns Code Deployment Immutable deployment Availability, Scaleability, High Performance, Fault tolerance patterns Data and messages replication and clustering (CAP theorem) |
| anafmd | Applying NAF with MAGICDRAW | 21 hours | This is a 3-day training covering principles of modeling, NAF, UPDM and use of MagicDraw following a case study, which demonstrates a typical defense architecture approach. The course: Includes lectures and hands-on practice in using MagicDraw for NAF modeling using UPDM; Explains NAF views, sub-views and concepts; Explains UPDM concepts and diagrams; Provides hands-on experience building models; 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: Enterprise architects, 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 certificate indicating that he attended the training. Introduction Trainer and Participant Introductions Introduction to NAF Introduction to UPDM Introduction to MagicDraw A Case Study Definition Managing Capability Portfolio Capability View Sub-views for Capability View Practical Assignment Defining Operational Scenarios Operational View Sub-views for Operational View Practical Assignment Defining Capability Configurations Systems View Sub-views for Systems View Practical Assignment SOA Service-Oriented View Sub-views for Service-Oriented View Incorporating Services into Operational and Systems Views Managing Project Portfolio Programme View Sub-views for Programme View Practical Assignment Applying Standards Technical View Sub-views for Technical View Describing Architecture All View Sub-views for All View Practical Assignment Establishing Traceability Specifying and analyzing traces between different architecture Views Wrap up Summarizing Training Discussing Remaining Questions Identifying Further Action Points |
| OMGUAF1 | Nato Architecture Framework (NAF) | 35 hours | This course gives a solid understanding across all aspects of Nato Architecture Framework. It does not focus on a specific view or function, but allows the delegates to easily find more information in the documentation and easily understand it. During the course the delegates will do simple exercises, answer questions, etc... Sparx Enterprise Architect is usually used during the course, but any other tools can be used instead. Background NATO C3 NATO C3 Organisation Mission NAF goals Framework Documentation Structure What is inside the NAF How NAF works NATO Network Enabled Capability What is an Enterprise Architecture? How to describe the architecture? Why Architecture Matters? Architecture is a language EA and decisions Types of NATO Architectures Quiz: Which architecture is described by the sentences below? Overarching Architecture (OA) Reference Architectures (RA) Target Architectures (TA) Baseline Architecture NATO Architecture Views NATO All View (NAV) NATO Capability View (NCV) NATO Operational View (NOV) NATO Service-Oriented View (NSOV) NATO Systems View (NSV) NATO Technical View (NTV) NATO Programme View (NPV) Stakeholders Communities of Interest Life-cycle management in NAF How NAF align stakeholders interest with the architecture? Identification of Stakeholders Identification of Communities of Interest (CoIs) Example CoIs Relation between Stakeholders and CoI’s Requirements Analysis of CoIs Description of CoI Interests CoI’s Architecture Interests and Impacts Requirements of Architecture Views |
| modafome | MODAF Overview and Modelling the Enterprise | 21 hours | This course is delivered in 2 modules: First module enables students to gain an overview of the use of MODAF to support acquisition. Secong module provides an in-depth description of the MODAF views and how they are used in the development of an architecture. It describes how the 6-step process is applied and how information gathered from stakeholders is interpreted within the MODAF model and represented in user-focussed views. Module 1 – Introduction to MODAF (½Day) Explain the benefits of a model-based approach Describe how MODAF provides graphical and textual visualisations of the enterprise (Viewpoints) Describe how MODAF ensures coherence between views (M3 metamodel) Describe the MODAF Viewpoints Describe how MODAF Views combine to describe enterprise change requirements Describe the MODAF 6-step approach Module 2 – MODAF, Modelling the Enterprise (2 ½ Days) Describe how to scope an EA problem and develop an initial AV-1 Describe the purpose and structure of each of the MODAF Views Explain how a MODAF-based architecture can: Describe the context of an enterprise Express operational capabilities and their metrics and map these to solution elements Express capability within an operational context and the processes that achieve the business or mission goal Describe elements of an enterprise from an SOA Viewpoint Describe how solution resources can be composed to realise capabilities or deliver services Describe the functional behaviour of solution resources Model system data and express how system level data exchange requirements can be mapped to operational information exchange requirements Specify system ports, the routing of port connections, protocols and hardware specifications Describe how architecture models can be enhanced using navigation views and dashboards |
| eaint | Überblick über Enterprise Architecture | 14 hours | This course is for everyone involved in planning, analysing, implementing, executing, maintaining or improving Enterprise Architectures. It shows comprehensive perspective of tools used to describe and implement the EA. Introduction to Enterprise Architecture What is architecture Enterprise Architecture (EA) Why do we need EA IT Enterprise Architecture Business Enterprise Architecture Enterprise Architecture Description vs EA Implementation Enterprise Architecture Methods, Frameworks, Concepts and Paradigms EA, Governance and Strategic Planning Strategic Management, Strategic Planning OMG Business Motivation Model Strategy Execution (EFQM) Quality Management(Six Sigma, TQM, ISO 9001) IT Governance IT Service Delivery and Support (ITIL) IT Implementation (CMM and CMMI) Methods and Frameworks IEEE Standards Zachman Framework OMG UAF (Unifed Architecture Framework) MDA SOA Nato Architecture Framework, MoDAF, DoDAF, UPDM Description Languages IDEF BPMN Testbed SoaML UML Architecture Description Languages Suitability for EA Enterprise Architecture Modelling Modelling Process Readability and Usability of Models Viewpoints and Visualisation Architecture Analysis Analysis Techniques Quantitative Analysis Functional Analysis Other Architecture Alignment Tool Support |
| sysml | System Modeling with SysML | 21 hours | This course is offered in two variants to provide a practical understanding of how systems can be modelling using the newest version of OMG's Systems Modelling Language (SysML) specification. The notation and underlying semantics of SysML are explained in a way that allows students to apply what they learn to any suitable system modelling method or tool. Introduction to System Modelling What is a system model? The four pillars of system modelling Model centric vs document centric What is SysML? Relationship between SysML and UML The four pillars of SysML Common and Crosscutting Constructs Profiles, stereotypes and tags Diagram frames Comments Allocations Requirement Diagrams What is a requirement? Modelling atomic requirements Requirement traceability Activity Diagrams Modelling flow-based logic Actions vs activities Understanding token flow Control flow vs object flow Modelling decisions · Modelling concurrency Swimlanes and responsibility Use Case Diagrams The system as a black box Identifying the system boundary with actors Use cases as system services Behind the use case diagram Use case structure · Nominal and alternative scenarios Handling common behaviour Extended and specialised behaviour Block Definition Diagrams What is a block? Block features Modelling types Modelling system hierarchy Generalising system elements Internal Block Diagrams Parts revisited Ports with Flow Properties Standard ports and interfaces Proxy ports and interface blocks Full ports Parametric Diagrams What is a constraint block? Constraining system properties Package Diagrams What is a package? Structuring the model with packages Package containment Package dependencies Representing the model structure Views and viewpoints Sequence Diagrams Interaction-based behaviour Simple sequences Synchronous vs asynchronous Fragment nodes Interaction use nodes State Machine Diagrams States and their syntax Transitions between states Pseudo state notation (initial, decision, history, end) Decomposing states Modelling concurrent states System Modelling Resources and Further Reading Suggested web resources Recommended literature |
| eaintro1 | Introduction to Enterprise Architectures | 14 hours | Objective This training course aims at helping attendees to understand the most used Enterprise Architectures and rules to follow up in their construction to succeed with an appropriate architecture scenario for their organisation. Thanks to the selection of appropriate architecture layers, components and traceability links that are to be established from the business layer to the technical layer, the resulting enterprise architecture framework allows you a good impact analysis in the face of evolutions of the business decisions and anticipates mutations of the corresponding information system components. Why Architecting the Enterprise? Introduction : Current issues in the Enterprise and IT governance Legacy Systems and evolution needs Business Architecture and Enterprise Architecture : similarities and differences The fundamentals Architecting the Enterprise : the principles Strategic Alignment Business and IT Repository Logical Architectures n-tiers Application technologies : ERP, SCM, webportail, Integration architectures and Services Architectures : EAI and ESB Service Oriented Architectures : Roles of the BPM and BAM Enterprise Architecture Strategies and Methodologies "As is" and "To be" system cartographies : How to determine the roadmap ? Structures to better align IT with the Strategies ? What is the approach ? What are links with the development processes ? Enterprise Architecture Content Framework Identifying the business functions of the enterprise Cartography of the actors and business functions Aligning business strategies Patterns to architecting the IT system Zones, squares and blocks Identifying Exchanges using services and events Modeling inter-block exchanges and data objects to support business process realizations Building the repository and data architectures The Master Data Management (MDM) Granularity Management Modeling Languages Definition of the meta-model and architecture rules Elaborate the Enterprise Architecture Repository Architecture Cartography Reference Layers Business, Functional, Application and Technical Layers Links between the Strategic and Business Views Traceability between the Business and Functional Views Traceability between the Functional and Application Views Bridges with the Technical View Contribution of an 'Enterprise Architecture' to create value Contribution to the business value Best Practices The Enterprise Architecture Roadmap Perspectives Tools Business Process and Cartography Management tools Presentation on a case study 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. The logos BMM, BPMN and UML referenced on this site are trademarks of the Object Management Group (OMG). The RUP and SOMA are rademarks of the IBM / Rational Software. |
| eaintro | Einführung in Enterprise Architect | 7 hours | This Introduction to Enterprise Architect training course is designed for all persons who wish to use Sparx Systems’ UML modelling tool, Enterprise Architect, for their modelling activities yet are unfamiliar with the features, functions and use of Enterprise Architect. High Level Principles of UML Business Use Case modelling Process Business Modelling (Activity Diagrams) Sparx EA 9.3 (professional) Printing Publishing models on the Server - HTML |
| UML | 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 |
| soa2eda | SOA 2.0 und EDA | 14 hours | Our ED-SOA training focuses on building and analysing an architecture framework that builds upon the SOA reference architecture. Services are used as event generators, signifying a problem or impending problem, an opportunity, a threshold, or a deviation. SOA and EDA The fusion of SOA and EDA into ED-SOA Combining events and services Business rule processing Transforming messages Solicit-Response Different ways of thinking about problem solving WS-Eventing Potential overlap between SOA and EDA Standardizing event processing rules Fundamental EDA Characteristics Decoupled interactions Publish/Subscribe messaging Many-to-many communications Event-based triggers Asynchronous interactions How does ED-SOA support faster responses? Event-driven Architecture Event processors Using a dashboard Event monitoring Event infrastructure Propagation of events Kicking off a business process SOA Action Framework Triggering actions Subscribing to an event The ESB and event propagation Complex event processing Event consumers Event producers Storing and forwarding events Facilitating system responsiveness Event processing Styles Simple processing Handling real-time flow of work Reducing lag time and cost Stream processing Real time flow of information Enabling in-time decision making Complex processing Inferring event occurrence Event correlation Sophisticated event interpreters Responding to business anomalies Enterprise Service Bus (ESB) Standard-based connectivity Transport services Message routing capabilities Message transformation features Event services Mediation capabilities Protocol mediation Content mediation Configuring a simple ESB solution Pervasive integration Reliable integration WS-Eventing Delivery modes Subscription managers Notations and terminology Subscription messages Notifications Faults Security considerations Message security Access control Complex Event Processing (CEP) CQL - Complex Query Language Event Attributes or properties Granularity of events Using timestamps Creation time and arrival time Event processing language (EPL) Event processing agents (EPA) Composite events Derived events Event source and event channel SOA event Patterns Discovering event patterns Commands Queries Event pattern monitoring Monitoring for control of process execution Event cascade When to use event patterns Event sourcing Structuring the event handler logic Reversing events SOA events and the SLA Importance of a Service level agreement Keeping services within the agreement Instances violating the SLA Priority for executing risk assessment steps Building autonomous processes Monitoring and event pattern triggering Dependence between events Software Platform for ED-SOA Software Tools for ED-SOA Event-optimized runtimes Supporting bulk application of rules Dynamic data-driven event definition Agents and streams Guaranteed pause times Sensors and event-processing agents Responders Conclusions Building of processes facilitated by ED-SOA ED-SOA constructed using BPM CEP principles as component of ED-SOA The increasing quest for control of BP Real time autonomous operation Gathering business intelligence from events |
| umlea | 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 |
| naf | Nato Architecture Framework (NAF) | 35 hours | This course gives a solid understanding across all aspects of Nato Architecture Framework. It does not focus on a specific view or function, but allows the delegates to easily find more information in the documentation and easily understand it. During the course the delegates will do simple exercises, answer questions, etc... Sparx Enterprise Architect is usually used during the course, but any other tools can be used instead. Background NATO C3 NATO C3 Organisation Mission NAF goals Framework Documentation Structure What is inside the NAF How NAF works NATO Network Enabled Capability What is an Enterprise Architecture? How to describe the architecture? Why Architecture Matters? Architecture is a language EA and decisions Types of NATO Architectures Quiz: Which architecture is described by the sentences below? Overarching Architecture (OA) Reference Architectures (RA) Target Architectures (TA) Baseline Architecture NATO Architecture Views NATO All View (NAV) NATO Capability View (NCV) NATO Operational View (NOV) NATO Service-Oriented View (NSOV) NATO Systems View (NSV) NATO Technical View (NTV) NATO Programme View (NPV) Stakeholders Communities of Interest Life-cycle management in NAF How NAF align stakeholders interest with the architecture? Identification of Stakeholders Identification of Communities of Interest (CoIs) Example CoIs Relation between Stakeholders and CoI’s Requirements Analysis of CoIs Description of CoI Interests CoI’s Architecture Interests and Impacts Requirements of Architecture Views |
| restapi | REST API - ein Schema für den Informationsaustausch zwischen Sites | 14 hours | The course is designed for developers, web applications, aims to provide opportunities offered by the REST architectural pattern by which you can communicate between sites. REST - base The need for the exchange of information between sites HTTP POST / GET / PUT / DELETE Services such MushUp and popular applications Services using REST Conventions Rest Mapping CRUD operations on HTTP calls Conventions API URL structure Passing Parameters Return Values HTTP statuses JSON - a universal format for the exchange of information Using the API services - customer Examples of the popular API Create a REST API - Server Gathering requirements and identify functionality Design and API documentation Installing the required libraries Business Object - mapping the class Controller methods Representation of a business object as JSON HTTP Headers - as metadata Testing the API using cURL Authentication mechanisms |
| soamlad | 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 |
| opstcloud | Create OpenStack cloud infrastructure | 14 hours | The course helps to understand and implement cloud infrastructure based on OpenStack. The participant learns the architecture and capabilities of OpenStack and a variety of installation scenarios. Introduction OpenStack Architecture Core services Additional services Environment Planning implementation Preparing the environment Identity service Installing Keystone Architecture Authentication Image service Installing Glance Architecture Adding images Compute service Installing Nova Architecture Adding compute nodes Network service Installing Neutron Architecture Creating a simple network Block storage service Installing Cinder Architecture Administration Creating users and projects Creating and destroying instances Creating and attaching volumes Configuration tools |
| umlitba | 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 |
| soastm | Service-Oriented Architecture: Strategy, Technology and Methodology | 35 hours | This course is intended for Post Graduate (or equivalent) level students and will be a combination of lectures and lab sessions (theory and practice). At the end of the course the student should be able to: Knowledge and Understanding. Understand the principles and business advantage of systems developed around services. Become fully aware of the major protocols and technologies involved in the web services standard, and understand how these technologies fit together. Your knowledge will extend to leading-edge and emerging aspects of web services as well as the more established elements of the standard. Understand in depth the technology used to enable systems based on a widely used programming language to both use and provide Web Services. Intellectual Skills: Identify where the service oriented approach and in particular web services are appropriate for particular business scenarios. Consider the most effective design for a web services solution Acquire, in the future, knowledge and understanding of emerging aspects of the rapidly evolving web services standard Practical Skills: Operate with current technologies associated with Web Services that are platform neutral – XML, SOAP, WSDL Write and expose web services in a widely used programming language and write client code in that language to invoke web services. The overall approach to design of systems based on services XML The RESTful approach to web services and the SOAP standard The Web Services Definition Language (WSDL) and other standards for the specification of services. Advanced web service standards to ensure such features as security and reliability BPEL, the Business Process Execution Language Web services in the cloud and the use of web services by mobile devices. |
| modafnafint | MoDAF/NAF Introduction | 7 hours | The course is aimed at business analysts, architects and systems engineers who want to understand how MODAF can be used in their organisation. Introduction to Enterprise Architecture in Defence EA Enablers: Frameworks, Tools, Meta-Models & Repositories Overview of MoDAF: what is it for, and how does it fit together Key MoDAF Views: Strategic, Operational, System Detail of MoDAF Views: The key views and how they're structured Developing Capability Models: Strategic Architectures The MoDAF System Views: Structure, Behaviour, Configuration Management Programmatic Views: Project Plans (AcV-2), Capability Planning (StV-3) Service Views: MoDAF interpretation of Services and SOA |
| umlad | 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 (http://www.omg.org/spec/UML) 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 |
| bpaumlbpmn | 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
| Course | Schulungsdatum | Kurspreis (Fernkurs / Schulungsraum) |
|---|---|---|
| Service-Oriented Architecture: Strategy, Technology and Methodology - Basel | Mo, 2017-10-09 09:30 | 6310EUR / 7260EUR |
| MOD Architecture Framework (MODAF) Überblick - Bern | Mo, 2017-10-09 09:30 | 2780EUR / 3430EUR |
| Overview of Unified Profile for DoDAF/MODAF (UPDM) - Zürich | Mo, 2017-10-09 09:30 | 4480EUR / 5130EUR |
Unternehmensarchitektur Schulung, Unternehmensarchitektur boot camp, Unternehmensarchitektur Abendkurse, Unternehmensarchitektur Wochenendkurse
, Unternehmensarchitektur Privatkurs, Unternehmensarchitektur Lehrer
, Unternehmensarchitektur Seminare, Unternehmensarchitektur Training, Unternehmensarchitektur Coaching,Unternehmensarchitektur Kurs
