SysML: Unterschied zwischen den Versionen

Aus bnw.bnwiki.de
Zur Navigation springen Zur Suche springen
 
(16 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 1: Zeile 1:
"Die Systems Modeling Language (OMG SysML) ist eine grafische, auf UML 2 basierende, standardisierte Modellierungssprache. Ihre Anwendung findet sie im Bereich Systems Engineering für die Modellierung verschiedener komplexer Systeme. Die Menge der in SysML definierten Diagramme besteht aus einer Untermenge von Diagrammen, die sich aus in UML 2 definierten Diagrammen ableiten lassen, ergänzt durch SysML-spezifische Diagramme. Es werden Struktur- und Verhaltensdiagramme unterschieden (siehe Grafik). Dem Anforderungsdiagramm als SysML-spezifischem Diagrammtyp kommt eine Einzelrolle zu."
https://de.wikipedia.org/wiki/Systems_Modeling_Language
<ref>https://de.wikipedia.org/wiki/Systems_Modeling_Language</ref>


= Dictionary =
https://help.innovator.de/Enterprise/de-de/Content/Ref.MetaM/SysML.htm
==Common==
===Note===
"A note can be attached to comment and represent its information in more details.
We advice to use Note when you want to display annotated element documentation, properties (e.g. hyperlink) on simply comment on diagram (e.g. note to yourself to clarify some details for specific element later), but you do not need this information in report and you do not need this information in other diagram. If you want to include the annotating information into report, annotate element not in browser, or reuse the information in other diagram (for example, if it is some note for all modelers working with specific element), you need to use Comment."
<ref name="a">https://community.nomagic.com/comment-vs-note-t3014.html</ref>
===Comment===
"A comment is a textual annotation that can be attached to a set of Elements. It is an UML element defined in UML specification, can exist without diagram and be created directly from model browser. One comment can be reused in several diagrams. It can be found in the model using Search even if it is not placed in diagram. As comments are elements, their text can be used in reports.===
A note is a graphical symbol containing textual information. It is not an element. It is used to add any explanatory information needed for your element or diagram, or if user needs to display element properties not displayed on element shape. A note is usually connected to the element symbol using an anchor line."
<ref name="a" />
===Problem===
The SysML Problem and Rationale extensions of the Comment are useful and pretty self-explanatory. But they are also a bit limited because they don't have any Stereotype properties for carrying "tagged values" metadata.===
So next  we'll see how we can easily extend Comment ourselves to create a custom stereotype that can carry a bit more structured information.
<ref>https://www.webel.com.au/node/1816</ref>
===Rationale===
===Element Group===
===Constraint===
===Containment===
===Abstraction===


==Block Definition Diagram==
UML; Systems Engineering; Object Management Group
===Package===
 
===Block===
= Übersicht =
===Interface Block===
{| class="wikitable"
===Flow Specification===
|+ Elemente der Systems Modeling Language (SysML)
===Constraint Block===
|-
===Domain===
! Element !! Bdeutung
===Value Type===
|-
===Enumeration===
| Modell ||
===Signal===
|-
===Instance===
| Paket||
===Interface===
|-
===Proxy Port===
| Classifier ||
===Interface Realization===
|-
===Link===
| Kommentar ||
===Association Block===
|-
===Directed Association===
| Modell ||
===Directed Aggregation===
|-
===Directed Composition===
| Ausdruck ||
==Internal Block Diagram==
|-
===Value Property===
| Randbedingung ||
===Part Property===
|-
===Reference Property===
| Datentyp, Primitiver Typ, Aufzählungstyp, Literal ||
===Constraint Property===
|-
===Flow Property===
| Schlüsselwörter ||
===Participant Property===
|}
===Bound Reference===
 
===Classifier Behaviour Property===
 
===Proy Port===
{| class="wikitable"
===Connector===
|+ Text der Überschrift
===Binding Connector===
|-
==Requriements Diagram==
! Knoten !! Bdeutung !! Grundelemente !! Anforderungsdiagramm !! Aktivitätsdiagramm !! Sequenzdiagramm !! Zustandsdiagramm !! Anwendungsfalldiagramm !! Blockdefinitionsdiagramm !! Internes Blockdiagramm !! Zusicherungsdiagramm !! Paketdiagramm !!
===Requirement===
|-
===Extended Requirement===
| Modell ||
===Satisfy===
|-
===Derive===
| Paket||
===Copy===
|-
===Trace===
| Classifier ||
===Verify===
|-
===Refine===
| Kommentar ||
===Test Case Activity===
|-
==Use Case Diagram==
| Modell ||
===Actor===
|-
===Use Case===
| Ausdruck ||
===Package===
|-
===Subsystem===
| Randbedingung ||
===Include===
|-
===Extend===
| Datentyp, Primitiver Typ, Aufzählungstyp, Literal ||
===Association===
|-
===Generalization===
| Schlüsselwörter ||
==Profiling Mechanism==
|-
===Stereotype===
| Modell ||
===Meta Class===
|-
===Extension===
| Modell ||
===Profile===
|-
===Profile Application===
| Modell ||
===Conveyed Information===
 
|}

Aktuelle Version vom 2. November 2022, 19:02 Uhr

https://de.wikipedia.org/wiki/Systems_Modeling_Language
https://help.innovator.de/Enterprise/de-de/Content/Ref.MetaM/SysML.htm

UML; Systems Engineering; Object Management Group

Übersicht

Elemente der Systems Modeling Language (SysML)
Element Bdeutung
Modell
Paket
Classifier
Kommentar
Modell
Ausdruck
Randbedingung
Datentyp, Primitiver Typ, Aufzählungstyp, Literal
Schlüsselwörter


Text der Überschrift
Knoten Bdeutung Grundelemente Anforderungsdiagramm Aktivitätsdiagramm Sequenzdiagramm Zustandsdiagramm Anwendungsfalldiagramm Blockdefinitionsdiagramm Internes Blockdiagramm Zusicherungsdiagramm Paketdiagramm
Modell
Paket
Classifier
Kommentar
Modell
Ausdruck
Randbedingung
Datentyp, Primitiver Typ, Aufzählungstyp, Literal
Schlüsselwörter
Modell
Modell
Modell