Practical aspects of UML
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 in Software Development
Verification of quality
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
A use case
Relations include, extend
Some object-oriented concepts in practice
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
Building strong relationships between the results of the analysis phase and the design phase
Modeling design classes
The relationship of the delegation
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
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.
This course is intended for software developers with various backgrounds who know at least one programming language.
Day 1: Process
What is Systems Engineering?
What is Software Engineering?
Why is Software Engineering difficult?
Software Engineering Processes
What is a Software Development Process?
Processes for building High-Integrity Systems
Standards & certification systems
What are High-Integrity Systems?
The role of QM culture
Reasons for errors
Critical systems standard
Day 2: Planning
Elicitation/analysis of user requirements
Specification of software
Tools to manage requirements
Textual modeling tools
Principles of OO design
Planning an architecture
UML graphical representations
Non-UML graphical representations
Day 3: Code
How to take a design into code
Programming best practices
Abstraction of code
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
Code for High-Integrity Systems
Reducing the impact of errors
Typical problems with code for High-Integrity Systems
Code quality metrics
Code size metrics
Code complexity metrics
Day 4: Verification & Validation
Fundamentals of VV
Independent Verification & Validation
Design and requirement reviews
Other V & V methods
Testing High-Integrity Systems
Documents regarding safety
Argumentation for safety
Reviews of High-Integrity Systems
Costs of V + V
Automatic vs manual tests
Types of tests
Day 5: Management
What is Project Management?
Standards (PMP, PRINCE2)
The function of process evaluation
Acting on the metric
Process evaluation standards & frameworks (CMMI, ISO 9001, TickIt+)
Process evaluation meetings
Summary and Conclusions
Introduction to Enterprise Architectures
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
Architecting the Enterprise : the principles
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)
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
The Enterprise Architecture Roadmap
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.
SOA 2.0 and EDA
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
Different ways of thinking about problem solving
Potential overlap between SOA and EDA
Standardizing event processing rules
Fundamental EDA Characteristics
How does ED-SOA support faster responses?
Using a dashboard
Propagation of events
Kicking off a business process
SOA Action Framework
Subscribing to an event
The ESB and event propagation
Complex event processing
Storing and forwarding events
Facilitating system responsiveness
Event processing Styles
Handling real-time flow of work
Reducing lag time and cost
Real time flow of information
Enabling in-time decision making
Inferring event occurrence
Sophisticated event interpreters
Responding to business anomalies
Enterprise Service Bus (ESB)
Message routing capabilities
Message transformation features
Configuring a simple ESB solution
Notations and terminology
Complex Event Processing (CEP)
CQL - Complex Query Language
Event Attributes or properties
Granularity of events
Creation time and arrival time
Event processing language (EPL)
Event processing agents (EPA)
Event source and event channel
SOA event Patterns
Discovering event patterns
Event pattern monitoring
Monitoring for control of process execution
When to use event patterns
Structuring the event handler logic
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
Supporting bulk application of rules
Dynamic data-driven event definition
Agents and streams
Guaranteed pause times
Sensors and event-processing agents
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
System Engineering using SysML and UML 2
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.
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
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.
Analysis and Design with SoaML
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
Compliance Level for SoaML
SoaML UML Profile Specification
Applying NAF with MAGICDRAW
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.
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.
software architects and other stakeholders who will create and use models
Presentations, discussions, and case study-based practical assignments.
Slides, case study model, and practical assignment descriptions.
Each participant receives No Magic and NobleProg certificate indicating that he attended the training.
Trainer and Participant Introductions
Introduction to NAF
Introduction to UPDM
Introduction to MagicDraw
A Case Study Definition
Managing Capability Portfolio
Sub-views for Capability View
Defining Operational Scenarios
Sub-views for Operational View
Defining Capability Configurations
Sub-views for Systems View
Sub-views for Service-Oriented View
Incorporating Services into Operational and Systems Views
Managing Project Portfolio
Sub-views for Programme View
Sub-views for Technical View
Sub-views for All View
Specifying and analyzing traces between different architecture Views
Discussing Remaining Questions
Identifying Further Action Points
UML for the IT Business Analyst
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
The BA’s Perspective on Object Orientation
Object Oriented Programming and its impact on modelling
The UML Standard
Cognitive Psychology and OO?
Attributes and Operations
Operations and Methods
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
Case Study F1: Decision Table
Case Study F2: Decision Tree
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
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
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
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
Implementing OO Using an OO Language
Implementing OOA Using Procedural Languages
Implementing a Database from OOA Using a RDBMS
Object-Oriented Analysis and Design using UML
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 Categories (FURPS)
Methods for gathering requirements
Modeling requirements using UML
The relationship matrix for the requirements
Creating a requirements specification
Modeling business processes
Business process modeling in UML
The definition of a business process
Concurrent flows and decisions
Exceptions and Exception Handling
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
Class Diagram and source code generation
Association relationship and its characteristics.
Other relationships: aggregation, composition, generalization, dependency, association class
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
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
Nato Architecture Framework (NAF)
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.
NATO C3 Organisation Mission
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)
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)
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)
Relation between Stakeholders and CoI’s
Requirements Analysis of CoIs
Description of CoI Interests
CoI’s Architecture Interests and Impacts
Requirements of Architecture Views
MODAF Overview and Modelling the Enterprise
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
Enterprise Architecture Overview
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 Service Delivery and Support (ITIL)
IT Implementation (CMM and CMMI)
Methods and Frameworks
OMG UAF (Unifed Architecture Framework)
Nato Architecture Framework, MoDAF, DoDAF, UPDM
Architecture Description Languages
Suitability for EA
Enterprise Architecture Modelling
Readability and Usability of Models
Viewpoints and Visualisation
Technical Architecture and Patterns
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.
System and Component Cohesion
SOA and Micro services architecture
Relationships between above concepts
Logic redudancy vs dependency
Data reduancy vs dependency
clarification of terms: architecture, design, modeling
centralised (Mediator Pattern)
Principles of OO Design
program against an interface
Law of Demeter
what are Design Patterns
Domain specific language
Use Case descriptions
UML Graphical Representations
Non-UML Graphical Representations
Design and Maintenance
SOA and Integration Patterns
Integration technologies and methods
More details direct communication patterns
Direct and brokered communication
Availability, Scaleability, High Performance, Fault tolerance patterns
Data and messages replication and clustering (CAP theorem)
Overview of Unified Profile for DoDAF/MODAF (UPDM)
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
Terms and Definitions
Symbols and Acronyms
Overview of this Specification
Representing Stereotype Constraints
UML Constraint Representation
Important Areas of the Architecture
DoDAF Class Library
OMG Unified Architecture Framework (UAF)
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.
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
Summary and Overview
MOD Architecture Framework (MODAF) Overview
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.
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
Overview of MODAF
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
Department of Defense Architecture Framework (DoDAF) Overview
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
Introduction to Enterprise Architect
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
Process Business Modelling (Activity Diagrams)
Use Case modelling
Static modelling (Class Diagrams)
Dynamic modelling (Sequence Diagrams)
Sparx EA (professional)
Publishing models on the Server - HTML documentation
Tips & Tricks
Service-Oriented Architecture: Strategy, Technology and Methodology
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.
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
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
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.
Systems Modelling with SysML
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
What is a requirement?
Modelling atomic requirements
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?
Modelling system hierarchy
Generalising system elements
Internal Block Diagrams
Ports with Flow Properties
Standard ports and interfaces
Proxy ports and interface blocks
What is a constraint block?
Constraining system properties
What is a package?
Structuring the model with packages
Representing the model structure
Views and viewpoints
Synchronous vs asynchronous
Interaction use nodes
State Machine Diagrams
States and their syntax
Transitions between states
Pseudo state notation (initial, decision, history, end)
Modelling concurrent states
System Modelling Resources and Further Reading
Suggested web resources
Create OpenStack cloud infrastructure
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.
Preparing the environment
Adding compute nodes
Creating a simple network
Block storage service
Creating users and projects
Creating and destroying instances
Creating and attaching volumes
REST API - a pattern of exchange of information between sites
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
Mapping CRUD operations on HTTP calls
Conventions API URL structure
JSON - a universal format for the exchange of information
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
Representation of a business object as JSON
HTTP Headers - as metadata
Testing the API using cURL
UML Analysis and Design
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
Analysis and Design
Actors and Use Cases
Class and Object Diagrams
Classes, objects, types of relations
Object and Class Relationships
Association, Aggregation, Composition
Interaction overview diagram
Component and Deployment
From Analysis to Implementation
Introduction to design patterns
Business Process Analysis with UML and BPMN
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.
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
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 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