<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://training-course-material.com/index.php?action=history&amp;feed=atom&amp;title=SysML_Intro</id>
	<title>SysML Intro - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://training-course-material.com/index.php?action=history&amp;feed=atom&amp;title=SysML_Intro"/>
	<link rel="alternate" type="text/html" href="https://training-course-material.com/index.php?title=SysML_Intro&amp;action=history"/>
	<updated>2026-04-12T23:10:54Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://training-course-material.com/index.php?title=SysML_Intro&amp;diff=59936&amp;oldid=prev</id>
		<title>Filip Stachecki: /* SysML Introduction⌘ */</title>
		<link rel="alternate" type="text/html" href="https://training-course-material.com/index.php?title=SysML_Intro&amp;diff=59936&amp;oldid=prev"/>
		<updated>2017-09-06T05:47:35Z</updated>

		<summary type="html">&lt;p&gt;&lt;span class=&quot;autocomment&quot;&gt;SysML Introduction⌘&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[Category:SysML]]&lt;br /&gt;
[[Category:private]]&lt;br /&gt;
&lt;br /&gt;
==SysML Introduction⌘==&lt;br /&gt;
=== Copyright ⌘===&lt;br /&gt;
Most of our training material is based on the OMG&amp;#039;s SysML Specification http://www.omg.org/spec/SysML&lt;br /&gt;
===SysML⌘===&lt;br /&gt;
[[File:OMG_SysML_logo.gif]]&lt;br /&gt;
* Systems Modeling Language&lt;br /&gt;
* OMG specification, current version: 1.5, release date: May 2017&lt;br /&gt;
* http://www.omg.org/spec/SysML/Current&lt;br /&gt;
* SysML is a general-purpose graphical modeling language for specifying, analyzing, designing, and verifying complex systems that may include hardware, software, information, personnel, procedures, and facilities.&lt;br /&gt;
* SysML provides semantics (meaning) and notation (representation of meaning).&lt;br /&gt;
* SysML is methodology and tool independent&lt;br /&gt;
&lt;br /&gt;
===Systems Engineering⌘===&lt;br /&gt;
[[File:SIMILAR_process.png]]&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Systems Engineering&amp;#039;&amp;#039;&amp;#039; is an engineering discipline whose responsibility is creating and executing an interdisciplinary process to ensure that the customer and stakeholder&amp;#039;s &amp;#039;&amp;#039;&amp;#039;needs are satisfied&amp;#039;&amp;#039;&amp;#039; in a high quality, trustworthy, cost efficient and schedule compliant manner throughout a system&amp;#039;s entire life cycle. &lt;br /&gt;
* This process is usually comprised of the following seven tasks: &amp;#039;&amp;#039;&amp;#039;S&amp;#039;&amp;#039;&amp;#039;tate the problem, &amp;#039;&amp;#039;&amp;#039;I&amp;#039;&amp;#039;&amp;#039;nvestigate alternatives, &amp;#039;&amp;#039;&amp;#039;M&amp;#039;&amp;#039;&amp;#039;odel the system, &amp;#039;&amp;#039;&amp;#039;I&amp;#039;&amp;#039;&amp;#039;ntegrate, &amp;#039;&amp;#039;&amp;#039;L&amp;#039;&amp;#039;&amp;#039;aunch the system, &amp;#039;&amp;#039;&amp;#039;A&amp;#039;&amp;#039;&amp;#039;ssess performance, and &amp;#039;&amp;#039;&amp;#039;R&amp;#039;&amp;#039;&amp;#039;e-evaluate. &lt;br /&gt;
source: http://www.incose.org/&lt;br /&gt;
&amp;lt;!-- http://www.incose.org/AboutSE/WhatIsSE --&amp;gt;&lt;br /&gt;
===DBSE vs. MBSE⌘===&lt;br /&gt;
[[File:ClipCapIt-160401-155945.PNG]]&lt;br /&gt;
* Document-based systems engineering approach uses textual documents that are exchanged between stakeholders&lt;br /&gt;
* Model-based systems engineering uses systems modeling as a part of the SIMILAR process.&lt;br /&gt;
* System model includes system specification, analysis, design, ... and is stored in a repository.&lt;br /&gt;
===The four pillars of system modelling⌘===&lt;br /&gt;
[[File:ClipCapIt-160726-091513.PNG]]&lt;br /&gt;
&lt;br /&gt;
===SysML/UML Interrelationship⌘===&lt;br /&gt;
[[File:SysML_and_UML.png]]&lt;br /&gt;
&lt;br /&gt;
SysML reuses a subset of UML 2 and provides additional extensions needed to address requirements of Systems Engineering.&lt;br /&gt;
&lt;br /&gt;
===SysML diagrams⌘===&lt;br /&gt;
[[File:SysML_diagrams.png]]&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
A block definition diagram is based on the UML class diagram, with restrictions and extensions as defined by SysML.&lt;br /&gt;
An internal block diagram is based on the UML composite structure diagram, with restrictions and extensions as defined by SysML.&lt;br /&gt;
A parametric diagram is a restricted form of internal block diagram that shows only the use of constraint blocks along with the properties they constrain within a context.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===SysML diagram frame⌘===&lt;br /&gt;
[[File:SysML_DiagramFrame.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source  lang=bnf&amp;gt;&lt;br /&gt;
&amp;lt;headingName&amp;gt; ::== &lt;br /&gt;
  &amp;lt;diagramKind&amp;gt; [&amp;#039;[&amp;#039;modelElementType&amp;#039;]&amp;#039;] &amp;lt;modelElementName&amp;gt; [&amp;#039;[&amp;#039;diagramName&amp;#039;]&amp;#039;]&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The frame is a rectangle that is required for SysML diagrams (Note: the frame is optional in UML).&lt;br /&gt;
====Diagram Kind⌘====&lt;br /&gt;
* SysML diagram kinds should have the following names or (abbreviations) as part of the heading:&lt;br /&gt;
** activity diagram (&amp;#039;&amp;#039;&amp;#039;act&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
** block definition diagram (&amp;#039;&amp;#039;&amp;#039;bdd&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
** internal block diagram (&amp;#039;&amp;#039;&amp;#039;ibd&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
** package diagram (&amp;#039;&amp;#039;&amp;#039;pkg&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
** parametric diagram (&amp;#039;&amp;#039;&amp;#039;par&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
** requirement diagram (&amp;#039;&amp;#039;&amp;#039;req&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
** sequence diagram (&amp;#039;&amp;#039;&amp;#039;sd&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
** state machine diagram (&amp;#039;&amp;#039;&amp;#039;stm&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
** use case diagram (&amp;#039;&amp;#039;&amp;#039;uc&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
====Diagram Frame example⌘====&lt;br /&gt;
[[File:RequirementsDeriviationDiagram.png]]&lt;br /&gt;
&amp;lt;!-- SUV requirements is a package containing &amp;#039;Requirements Deriviation&amp;#039; requirements diagram--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===The Four Pillars of SysML⌘===&lt;br /&gt;
[[File:4PillarsOfSysML.jpg]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;source: http://www.omgsysml.org/&amp;lt;/small&amp;gt;&lt;/div&gt;</summary>
		<author><name>Filip Stachecki</name></author>
	</entry>
</feed>