Enterprise Architecture Training Courses

Enterprise Architecture Training

Enterprise Architecture, EA, courses

Client Testimonials

Software Engineering

Kristian (the trainer) was very well prepared and anticipated potential changes in the course content ( we had varying levels of experience). He also integrated information specific to our company in a professional and dynamic way.

Maell Cullen - Altran UK

Software Engineering

Kristian (the trainer) was very well prepared and anticipated potential changes in the course content ( we had varying levels of experience). He also integrated information specific to our company in a professional and dynamic way.

Maell Cullen - Altran UK

Software Engineering

Kristian (the trainer) was very well prepared and anticipated potential changes in the course content ( we had varying levels of experience). He also integrated information specific to our company in a professional and dynamic way.

Maell Cullen - Altran UK

Software Engineering

Kristian (the trainer) was very well prepared and anticipated potential changes in the course content ( we had varying levels of experience). He also integrated information specific to our company in a professional and dynamic way.

Maell Cullen - Altran UK

Software Engineering

Kristian (the trainer) was very well prepared and anticipated potential changes in the course content ( we had varying levels of experience). He also integrated information specific to our company in a professional and dynamic way.

Maell Cullen - Altran UK

Software Engineering

The trainer was excellent, the only reason I have not indicated all sixes was that there were some subjects that I was less interested in but this is just due to personal taste and career path.

There were computer based activities e.g writing code and using existing programs.

Mel Irfan - Altran UK

Software Engineering

The trainer was excellent, the only reason I have not indicated all sixes was that there were some subjects that I was less interested in but this is just due to personal taste and career path.

There were computer based activities e.g writing code and using existing programs.

Mel Irfan - Altran UK

Software Engineering

The trainer was excellent, the only reason I have not indicated all sixes was that there were some subjects that I was less interested in but this is just due to personal taste and career path.

There were computer based activities e.g writing code and using existing programs.

Mel Irfan - Altran UK

Software Engineering

The trainer was excellent, the only reason I have not indicated all sixes was that there were some subjects that I was less interested in but this is just due to personal taste and career path.

There were computer based activities e.g writing code and using existing programs.

Mel Irfan - Altran UK

Software Engineering

The trainer was excellent, the only reason I have not indicated all sixes was that there were some subjects that I was less interested in but this is just due to personal taste and career path.

There were computer based activities e.g writing code and using existing programs.

Mel Irfan - Altran UK

Software Engineering

Enthusiastic and interesting trainer.

Adrian Turner - Altran UK

Software Engineering

Enthusiastic and interesting trainer.

Adrian Turner - Altran UK

Software Engineering

Enthusiastic and interesting trainer.

Adrian Turner - Altran UK

Software Engineering

Enthusiastic and interesting trainer.

Adrian Turner - Altran UK

Software Engineering

Enthusiastic and interesting trainer.

Adrian Turner - Altran UK

Software Engineering

I liked the refresher of what we had learnt at the end of each day and at other regular intervals. Kristian (the trainer) seemed to have anticipated questions that we asked and had presentations and knowledge to help answer these questions.

Ashley Day - Altran UK

Software Engineering

I liked the refresher of what we had learnt at the end of each day and at other regular intervals. Kristian (the trainer) seemed to have anticipated questions that we asked and had presentations and knowledge to help answer these questions.

Ashley Day - Altran UK

Software Engineering

I liked the refresher of what we had learnt at the end of each day and at other regular intervals. Kristian (the trainer) seemed to have anticipated questions that we asked and had presentations and knowledge to help answer these questions.

Ashley Day - Altran UK

Software Engineering

I liked the refresher of what we had learnt at the end of each day and at other regular intervals. Kristian (the trainer) seemed to have anticipated questions that we asked and had presentations and knowledge to help answer these questions.

Ashley Day - Altran UK

Software Engineering

I liked the refresher of what we had learnt at the end of each day and at other regular intervals. Kristian (the trainer) seemed to have anticipated questions that we asked and had presentations and knowledge to help answer these questions.

Ashley Day - Altran UK

Subcategories

Enterprise Architecture Course Outlines

ID Name Duration Overview
2145 Overview of 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
2140 Enterprise Architecture Overview 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 TOGAF MDA SOA Nato Architecture Framework, MoDAF, DoDAF, UPDM Description Languages IDEF BPMN Testbed SoaML UML ArchiMate 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
2121 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
287852 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
2062 Introduction to Domain Driven Design 14 hours What Is Domain-Driven Design (DDD) Building Domain Knowledge The Ubiquitous Language The Need for a Common Language Creating the Ubiquitous Language The Building Blocks Of A Model-Driven Design Layered Architecture Entities Value Objects Services Modules Aggregates Factories Repositories Refactoring Toward Deeper Insight Continuous Refactoring Bring Key Concepts Into Light Preserving Model Integrity Bounded Context Continuous Integration Context Map Shared Kernel Customer-Supplier Conformist Anticorruption Layer Separate Ways Open Host Service Distillation
287820 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.
1939 UML for the IT Business Analyst 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
287762 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
2634 Introduction to 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
1937 Analysis and Design with 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 Categorization Category CategoryValue RAS Placeholders BMM Integration MotivationElement MotivationRealziation SoaML Metamodel
2569 Object-Oriented Analysis and Design using 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. Introduction to UML A brief History of UML Overview of issues in the field of object-oriented modeling UML Specification (OMG) UML diagrams overview Requirements management Requirements Types Requirements Categories (FURPS) Methods for gathering requirements Modeling requirements using UML The relationship matrix for the requirements Creating a requirements specification Modeling business processes Activity Diagram Business process modeling in UML The definition of a business process Concurrent flows and decisions Exceptions and Exception Handling Partitions, path Modeling non-functional requirements Components and Deployment diagrams The initial architecture of the system - logical and physical Modeling requirements for security, performance, reliability, ... Modeling functional requirements Modeling functionality with the Use Case diagram Determining the scope of the system Actors and the relationships between them Identifying use cases Association "actor - use case" and its properties The relationship between use cases: include, extend, generalization Creating a use case scenarios and generate diagrams from them (activity, state machine) Analytical model of the system Using communication diagram to identify the main system objects The types of messages: asynchronous, synchronous, reply Specify the numbering sequence of messages Categories of objects: Boundary, Control and Entity Introduction to the project system Modeling the interaction Static Modeling Class Diagram and source code generation Association relationship and its characteristics. Other relationships: aggregation, composition, generalization, dependency, association class Forward/Reverse engineering Generating source code from the model Generating diagram based on the source code Synchronizing code and diagram Object Diagrams, Composite Structure Diagrams, and Package Diagrams Dynamic Modeling Verification of the static model Clarification of method signatures Verification of the class diagram The dynamic modeling at the level of method calls Diagrams: Sequence, State Machine, Timing, and Interaction
2494 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 configure EAP file Create and save a Enterprise Architect project file File structure of the project Types of views Program interface: menus, toolbars, Toolbox, Project Browser and other windows Docking and hiding windows Working with a model, diagram Predefined models Packages (views) and diagrams Adding elements to the model and diagram Different ways of removing the items and their consequences Saving diagrams Requirements Management Methods of requirements gathering FURPS requirements categories Requirements Diagram Relationships between requirements aggregation dependency realization How to improve the appearance of a diagram? layout diagram colour status requirements enable / disable the package names Create and manage a matrix relationship Documenting requirements HTML pages printable version Advanced requirement management  custom types of requirements custom requirements status tracking requirements requirements documenting Business process modeling, architecture Activity Diagram Compound activities Control flows, object flows Handling exceptions, interrupt flow Partitions Concurrent flows and decision-making How to improve the appearance of a diagram? different levels of detail reducing the amount of detail complexity of the process Components and Deployment diagrams The initial architecture of the system - logical and physical nested components delegation and assembly port, part interface communication paths Security, performance, reliability of the system requirements modelling Non-standard implementation of stereotypes in diagrams stereotypes graphic library adding the library to the project custom graphics stereotypes Use Cases and their documentation Functional requirements modeling  Scope of the system Actors and the relationships between them Identifying use cases Association "actor - use case" and its properties Relationship between use cases: include, extend, generalization Auto names Use Case scenarios and diagrams generated based on them them (activity, state machine, sequence) Use Case scenarios from external files Documentation generation Document Templates Domain model Main classes/objects of a system Communication Diagram message types: asynchronous, synchronous, return messages numbering stereotypes: Boundary, Control and Entity System design introduction  Static model Class Diagram Class diagram and source code generation association and its characteristics other relationships: aggregation, composition, generalization, dependency, association class naming  convention for classes and their elements show/hide classes Forward/Reverse engineering source code generating from the diagram diagram generation from source code source code and diagram synchronization Object Diagrams Dynamic Model Static model verification clarify the method signatures verification of the class diagram Dynamic modeling at the level of method calls (sequence diagram) based on use cases and static analysis model How to improve the appearance of a diagram? reducing the number of modeled scenarios reducing the number of lifelines avoiding complex nested blocks hiding details State Machine diagram states and sub-states transitions between states - trigger, condition and action internal actions (entry, do, exit) How to improve the appearance of a diagram? line style state decomposition Patterns and profiles "Gang of Four" patterns Patterns defined in the project Collaboration User patterns Importing profiles from XML files MDA, source code Class Diagram to database schema transformation SQL script generation based on class diagram Source code generation - available options Group work Enterprise Architect package versioning Differences in the versions of the project, documentation Using a repository to store the model Collaboration tools
1319 SOA 2.0 and 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
2471 Quality Assurance and Continuous Integration 14 hours Training is open to both developers, Scrum Masters, Product Owner and also some aspects of the business department. The purpose of training is to introduce topics Quality Assurance and Continuous Integration and their place in projects conducted agile methodologies. Participants will gain a broad perspective on the issues discussed as well as practical knowledge of the tools and processes of software development in line with the QA / CI. Representatives of business, will be able to know the benefits of implementing those tools and processes and translate into both the time and cost of software development. The issues presented are based on PHP or Java, depending on customer requirements. QA/CI What is QA? What is CI? The costs of software development, refactoring and fix errors Identifying and understanding the project Profit for the organization DDD Software development based on business requirements, assumptions DDD Problems in communication IT-Business Domain Model Best Practices KISS principle and DRY Coding standards Creating reusable code through OOP and design patterns Identifying and reducing cyclomatic complexity Software Metrics Weight Method per Class Response For a Class Depth of Inheritance Tree Coupling Between Objects Lack of Cohesion of Methods Number of Children Cyclomatic complexity Metrics class Model Metrics Metrics for use Software Testing What, when and how to test? The method of "white-box" and "black box" The role of testing in agile methodologies TDD only a potential increase in the cost of the project Unit testing with JUnit (Java), PHPUnit (PHP) Behavioral tests of JBehave (Java), Behat and Mink (PHP) Functional tests Refactoring What is refactoring? Debt technology Code smell Refactoring patterns Documentation The role of documentation in agile methodologies What to document? Types of documentation Documentation and agile methodologies, or you can call (Working software over comprehensive documentation)? Standard XMI Automatic generation of documentation from the Javadoc (Java), ApiGen (PHP) Tools and Environment CI Tools and Environment CI PMD (Java), phpmd (PHP) CPD (Java), phpcpd (PHP) Lines Of Code Counter (Java), phploc (PHP) UCDetector (Java), phpdcd (PHP) Jdepend (Java), phpdepend (PHP) Jenkins Continuous Integration Server Agile and CI/QA Planning and incremental development Embracing Change Short stages Interdisciplinary team Extreme Programming, Code Review Individuals and interactions over processes and tools Summation Discussion Questions How do you begin the process of implementation?
2490 Practical aspects of 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 include, 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 of activity diagrams, sequence and state machine Description of the aspects of the architecture of the dispersion The different perspectives of architecture description
2464 REST API - a pattern of exchange of information between 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
2458 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
2435 System Modelling with SysML 21 hours This course is offered in two variants to provide a practical understanding of how systems can be modelling using the OMG's Systems Modelling Language (SysML) version 1.2 or 1.3. 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 five pillars of SysML Common and Crosscutting Constructs Profiles, stereotypes and tags Diagram frames Comments Allocations Package Diagrams What is a package? Structuring the model with packages Package containment Package dependencies Representing the model structure Views and viewpoints 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 Sequence Diagrams Interaction-based behaviour Simple sequences Synchronous vs asynchronous Fragment nodes Interaction use nodes System Modelling with SysML Activity Diagrams Modelling flow-based logic Actions vs activities Understanding token flow Control flow vs object flow Modelling decisions · Modelling concurrency Swimlanes and responsibility State Machine Diagrams States and their syntax Transitions between states Pseudo state notation (initial, decision, history, end) Decomposing states Modelling concurrent states Block Definition Diagrams What is a block? Block features Modelling types Modelling system hierarchy Generalising system elements Internal Block Diagrams Parts revisited Flow ports, flow specifications and item flow (SysML 1.2 only) Standard ports and interfaces (SysML 1.2 only) Proxy ports and interface blocks (SysML 1.3 only) Full ports (SysML 1.3 only) Parametric Diagrams What is a constraint block? Constraining system properties Requirement Diagrams What is a requirement? Modelling atomic requirements Requirement traceability System Modelling Resources and Further Reading Suggested web resources Recommended literature
2434 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.
2147 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
2146 MOD Architecture Framework (MODAF) Overview 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
1938 UML Analysis and 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
1476 Business Process Analysis with UML and BPMN 14 hours Course Audience: Managers who want to understand BPMN diagrams, Business Consultants, Business Analysts, Business Process Engineers, System Analysts and anyone who is involved in analyzing and planning Business Processes using standardized, unified modelling notation. Course Goals: Produce high-quality process diagrams Model in the BPMN process notation Capture as-is process information Implement optimized process flows for people-intensive processes Simplify complex process definitions and break them into more manageable pieces 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
Weekend Enterprise Architecture courses, Evening Enterprise Architecture training, Enterprise Architecture boot camp, Enterprise Architecture instructor-led , Enterprise Architecture private courses, Enterprise Architecture classes, Enterprise Architecture coaching, Evening Enterprise Architecture courses, Enterprise Architecture training courses, Enterprise Architecture one on one training , Enterprise Architecture instructor, Enterprise Architecture trainer , Enterprise Architecture on-site

Some of our clients