This webinar has completed, the recording will be posted shortly.

Overview

Model-Based Systems Engineering has become a standard for Systems Engineers when dealing with the design and implementation of complex systems. In part one of this series we are looking at the benefits of using international modeling standards, and a centralized repository for applying these Systems Engineering standards.

Part one of the MBSE series will discuss the following questions:

REGISTER TODAY!

Don't miss this opportunity to learn more about Enterprise Architect

Session 1

Melbourne Tue 06 Dec 08:00 am
New York Mon 05 Dec 16:00 pm
Los Angeles Mon 05 Dec 13:00 pm
Singapore Tue 06 Dec 05:00 am
London Mon 05 Dec 21:00 pm

Session 2

Presenters

Dermot O'BryanSparx Systems
Scott HebbardCommunications Manager
Sparx Systems

Explore the webinar resources

High Quality MBSE Presentation For Download: ea-mbse-part-1.mp4 Download links

Questions & Answers

Part 2 will cover a key MBSE language called SysML. Enterprise Architect provides complete support of SysML 1.5 to ensure a rich, team-based modeling environment for Systems Engineers. The webinar will also examine some key practical features in Enterprise Architect for using SysML. The webinar outlines the four pillars of SysML and illustrates how they can be implemented in Enterprise Architect.

Part 3 will discuss collaboration across teams, including Chat, Model Mail, Journals and Reviews. The webinar will then look at using the computer interpretation of the model, looking at outsourcing parts of the design process to contractors when doing large systems or 'systems of systems'. Some of this process may use the Pro Cloud Server, Reusable Asset Service and industry standard exchange using technology such as XMI. The webinar also examines connectivity, traceability, code generation, DMN simulation, state machine simulation and outlines how Enterprise Architect supports math based simulation.
Part 1 provided an overview of the MBSE features and their use. The intended target audience was for executives and stakeholders overseeing designs. It is ideally suited for someone interested in understanding why MBSE is important when developing systems.

Parts 2 & 3 are oriented to the system engineers and developers using Enterprise Architect for MBSE.
A diagram tool can provide a visual representation of a system. A diagram typically does not provide information about traceability, connectivity or other system relationships and connections. A diagram is typically static, a snapshot of a moment in time and designed and built for a specific audience.

A model on the other hand, provides an abstraction that contains elements that can be used to describe every aspect of a systems, including relationships, business impacts, systems, views and much more. This includes traceability ranging from the high-end abstract models linking all the way through to more detailed specifics. It is much easier to keep a model updated and provide rich information about model elements that cater for the needs of different stakeholders. Models can be adapted to different target audiences, are constantly evolving and can help differentiate between As-Is and To-Be states.

With enterprise Architect being repository based, the MBSE tools like Enterprise Architect offer features for linking documentation and human interaction via chats and emails - which we cover in later parts of this series.
The Sparx Systems website contains a number of resources on the Model Based Systems Engineering landing page: Model Based Systems Engineering (MBSE)
There is a series of Guidebooks that Sparx Systems has created to help customers get up to speed on a variety of different topics. The following link provides a guide to MBSE with SysML: Guide to MBSE with SysML
Yes, this is advisable, beneficial and practical. It enables the project to be more tightly controlled and coordinated, as well as ensuring that for future iterations (new versions), there is a base from which the changes can be administered.

If you need assistance getting started, Sparx Systems has established a variety of service based companies around the world that provide personal localized support, installation and distribution of Enterprise Architect. Please refer to the links below to get started:

Sparx Services Partners
The simple start is to import documents and diagrams and begin to link these to any new modeling diagrams. It is easy to import high level requirements from CSV files, Documents or Spreadsheets via the MDG for MS Office. Visio diagrams can be imported as UML/BPMN and SysmL models all via the MDG for MS Office, also whole documents can be stored as Artifacts by simply dragging a file onto a diagram. These are viewable and editable within Enterprise Architect. They can be hyperlinked internally and externally.

Please refer to the Model Integration for Microsoft® Office landing page for more information: Model Integration for Microsoft® Office
A Central repository is basically a database holding all modeling content from diagrams and documents through to collaborative interactions.

Enterprise Architect's structure being 3-tiered with: UI, Business logic and Data logic, means that there is a range of repository types accessible via the data logic layer. These range from simple file based repositories for local or individual use, through to a range of eight or so DBMS that can be used as preferred by the organisation.

Please refer to the Enterprise Architect User Guide for more information on the Repository: Repository Overview
That is further augmented with the Pro Cloud Server that provides a means of hosting these, via HTTPS, off-site or on-site with external team access.

Refer to the following page to learn more about the Pro Cloud server: Pro Cloud Server
The repository being a fundamental structure is referenced in many demos, but not quite explicitly covered.

For a starter see: Creating a New Model
See the 'Pro Cloud Server' group of demos on:
Product Demonstrations
With all the languages supported by Enterprise Architect being based on a UML foundation, these are all interoperable with options to create diagrams in these languages and directly link any object on any diagram to any other object in another diagram of another language type. There can language specific validation restrictions for some types of connections, but there is the option to turn off those validation restrictions if required. However simple Trace and Note relations can always be applied regardless of any validation restrictions.
share this page share by email share on linkedin share on twitter share on facebook