Enquiry Form

Enterprise Architecture Training Courses

Enterprise Architecture, EA, courses

Client Testimonials

UML for the IT Business Analyst

The overall training was totally relevant to my needs. The course content was excellent and the trainer (Alain) was very good in providing explanations, answering questions and really knew the subject matter from a practical point of view which I am sure will prove to be extremely useful to me.

Stephen Thompson - Babcock Airports Ltd

UML Analysis and Design

Lots of worked examples and exercises. Discussion of these really helped my understanding.

The trainer really knew his way around the course material and was able to adapt examples and exercises to suit the interests of the class. It was helpful that he was also familiar with the tool we use (Sparx EA).

Isobel Squire - ELEXON

UML Analysis and Design

I liked creating the UML diagrams and processes

Ammar Al Hadhrami- Information Technology Authority

Software Engineering

the engaging method of teaching ensured that all attending the course were involved in the learning process

Matthew Cuff - Altran UK

Software Engineering

Covered a wide range of topics - more than I would have expected in a Software Engineering lecture (such as some details on programming, safety critical systems etc.). Kristian was very friendly and easy to ask questions to. I thoroughly enjoyed the course and would recommend it to others.

Jerome Shah - Altran UK

Object-Oriented Analysis and Design using UML

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

JIMMY CHAN - THALES TRANSPORT & SECURITY (HONG-KONG) LIMITED

Subcategories

Enterprise Architecture Course Outlines

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) newest version 1.4. 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

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.

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

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

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

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.
TOGAF and Zachman are respectively trademarks of the Open Group and Zachman International

Objective:
Helping Business Analysts, architects and designers to understand how to efficiently specify and realize a Service Oriented Architecture on the basis of their business goals and align it to changing business and user requirements.
This 3 day training course aims at helping business analysts, architects and designers to learn how to specify and realize a featured Service Oriented Architecture to better deal with changes on the business and user requirements (changing objectives, strategies, tactics, rules, user interactions,...) while capitalizing on the business capabilities.
Introduction
Pros and Cons of the current development methodologies to support the Business Agility,
Objectives of the SOA,
Connections between Business Architecture, TOGAF®, BPM and SOA,
Service Definition and Categories,
Service Provider and Consumer Components,
Service Contract, Metrics
Data Transfer Objects vs. Persistence,
Service orchestration,
Role of the ESB,
Top-Down and Bottom-Up approaches,
The Layered Logical Architecture
The TOGAF® Reference Architecture for SOA,
Structure and Typology of Services,
Architecture Layers (business, functional, application, technique) in the SOA,
Presentation of the main components by layer and traceabilities,
Steps for aligning IT to changing business requirements,
Business Layer
Components of the business layer : objectives
Traceability in the Business Modeling using BMM, BPMN and UML standards,
From the business goals toward processes using Business Capabilities- the IBM's RUP for SOMA,
Alignment of business processes and entities on the changing goals,
Service Identification on the basis of Business Capabilities,
Case Study : Refinement from the Business Vision toward Processes using goal-driven business capabilities,
Language Structures of the BPMN : Good practices,
Case Study : BPMN Modeling of the previous business process,
From the Business to functional layer : Prepare the Architecture to deal with change using reusable and traceable components,
Case Study : Elaborate the business architecture backbone of the Goal-Driven SOA,
Functional Layer
The role of the functional architecture,
Service components of the functional layer : objectives
Blocks of an urbanized functional architecture : (zone, square, block)
Unit Business Services vs. Composite Services,
Service Specification using SoaML « services points » and « request points »,
Identification and specification of use cases (UC) on the basis of services,
Case Study : Complete the business architecture backbone of the Goal-Driven SOA using functional components,
Invocation of service and UC components from business process actions,
The role of the data transfer objects,
Case Study : Propagate change from Business Goals till Components of the Functional Layer,
From the functional to application layer,
Application Layer
Service components of the application layer
Building application components on the basis of functional ones,
The Business Process Execution Language,
BPMN / BPEL Mapping,
WebServices: Definition, Soap, WSDL, UDDI, standards
XSD generation on the basis of Data Models,
WSDL generation on the basis of Service Interfaces,
Module and Component Assembly,
Case Study : Design Application Use case and Service components on the basis of functional ones,
ESB features in SOA,
JBI, Services Mix and Integration Patterns,
Case Study : Integrate use case and service behaviours into the architecture backbone.
Horizontal Aspects
QoS,
Administration and Supervision,
Business Activity Monitoring (BAM),
Security and Performance,
Agility using SOA
Agility: factors and impact analysis,
Refactoring, reuse and mutualization (advantages and constraints),
Versioning,
Governance by Objectives ,
Benefices of the Goal-Driven SOA,
Agility : The Goal-Driven Structure of the SOA to support changes,
From the business to IT system capitalizing on Business Objects and Capabilities,
Impact of the Changes on Processes and Business Objects,
Projection on the IT System : Services and Use Cases to be impacted by the changes,
Description of the impact of changes on the Use case and Application Service Component behaviours,
Integration of behaviours into the backbone of the Goal-Driven SOA and tests.
Conclusion
Agility and SOA : synthesis
Overview on the steps of the Goal-Driven SOA,
Traceability from the BMM's business model structures to IT structures to better deal with changes.
Overview on the market products
Open Source Products (Service Mix, Mule, Open ESB…),
Commercial Products
Notice: The above training-mentoring sessions are conducted interactively using Business and IT 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.
Provided by GooBiz

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.

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

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

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

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

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.

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

This course gives a solid understanding across all aspects of OMG United 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
UAF History
UAF goals
Framework Documentation Structure
What is inside the UAF
How UAF works
What is an Enterprise Architecture?
How to describe the architecture?
Why Architecture Matters?
Architecture is a language
EA and decisions
Architecture Views and elements
Strategic
Operational
Services
Personnel
Resources
Security
Projects
Standards
Actual Resources
Dictionary
Requirements
Summary and Overview
Information
Parameters

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

The UK is operated by NobleProg (UK) Ltd, but a Franchise can be bought in some regions. If you are interested in opening a franchise in your country, please visit http://training-franchise.com for more information.

NobleProg® is a registered trade mark of NobleProg Limited and/or its affiliates.