You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: specification/10___literature.adoc
+1-2
Original file line number
Diff line number
Diff line change
@@ -15,5 +15,4 @@
15
15
16
16
- [[[MICCORE2023]]] IRT SystemX and prostep ivip MIC Core specification: https://mic-core.github.io/MIC-Core/main/
17
17
18
-
- [[[SETLEVEL]]] Credible Simulation Process Framework in GitLab: https://gitlab.setlevel.de/open/processes_and_traceability/credible_simulation_process_framework
19
-
18
+
- [[[CSP]]] Credible Simulation Process Framework in prostep Recommendation Appendix Part-H: https://www.prostep.org/shop/detail?ai%5Baction%5D=detail&ai%5Bcontroller%5D=Catalog&ai%5Bd_name%5D=psi_11_v3-0&ai%5Bd_pos%5D=20
Copy file name to clipboardexpand all lines: specification/2___framework.adoc
+3-3
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ When a __Credible Decision Process__ identifies the need for a simulation, a __S
13
13
The result of a __Credible Simulation Process__, i.e. the simulation results, is then delivered to the triggering __Credible Decision Process.__
14
14
This information transfer is referred to as __Simulation Delivery__ in <<im-crediblesimulationprocessframework>>.
15
15
16
-
For more information on the processes of the Credible Simulation Process Framework, see <<SETLEVEL>>.
16
+
For more information on the processes of the Credible Simulation Process Framework, see Appendix Part H of the prostep ivip SmartSE Recommendation v3 (<<CSP>>).
17
17
18
18
__Note: The Credible Simulation Process Framework actually includes more than just Credible Decision Process and Credible Simulation Process.
19
19
However, the SSP Traceability specification currently only supports traceability with respect to the Credible Decision Process and the Credible Simulation Process.__
@@ -46,7 +46,7 @@ Evaluation:: In this phase, the decision-relevant information returned from the
46
46
47
47
Fulfillment:: The purpose of this phase is to decide whether the results fulfill the original objectives of the decision task.
48
48
49
-
For more information on the Credible Decision Process, see <<SETLEVEL>>.
49
+
For more information on the Credible Decision Process, see <<CSP>>.
50
50
51
51
[#sec-crediblesimulationprocess]
52
52
=== Credible Simulation Process
@@ -75,4 +75,4 @@ Evaluation:: The purpose of this phase is to evaluate the simulation results, i.
75
75
76
76
Fulfillment:: The purpose of this phase is to confirm that the simulation results meet the original objectives of the simulation task.
77
77
78
-
For more information on the Credible Simulation Process, see <<SETLEVEL>>.
78
+
For more information on the Credible Simulation Process, see <<CSP>>.
Copy file name to clipboardexpand all lines: specification/6___dtmd.adoc
+4-3
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
[#sec-dtmd]
2
2
== Decision Task Meta Data File Format
3
3
4
-
The __Decision Task Meta Data__ file (short: DTMD file) is an implementation of a GlueParticle for decition tasks. It is specified to support traceability, quality assurance and re-usability for decision tasks in terms of a credible decision process as it is specified in #Document Reference#. The following sub-chapters describe the structure of an DTMD file.
4
+
The __Decision Task Meta Data__ file (short: DTMD file) is an implementation of a GlueParticle for decition tasks. It is specified to support traceability, quality assurance and re-usability for decision tasks in terms of a credible decision process as it is specified in <<CSP>>. The following sub-chapters describe the structure of an DTMD file.
5
5
6
6
[#im-credibledecisionprocess]
7
7
.Credible Decision Process
@@ -95,7 +95,8 @@ The AnalysisPhase element is associated with the following attributes.
95
95
[#sec-dtmddefinitionphase]
96
96
==== DefinitionPhase
97
97
98
-
#In the definition phase, ....#
98
+
In the definition phase, the decision task is broken down into sub-tasks, which are to be performed in the execution phase.
99
+
Additionally, the quality of the results to be achieved is defined and the overall breakdown and quality definitions are verified.
99
100
100
101
The DefinitionPhase element documents all relevant information.
101
102
@@ -198,7 +199,7 @@ The EvaluationPhase element is associated with the following attributes.
198
199
[#sec-dtmdfulfillmentphase]
199
200
==== FulfillmentPhase
200
201
201
-
#In the fulfillment phase, it is checked and decided whether the entire simulation task, including the simulation results, fulfills the requirements placed on the simulation by the commissioning higher-level engineering task and whether the simulation tasks can be completed.#
202
+
In the fulfillment phase, it is checked and decided whether the entire decision task, including all sub-tasks performed, fulfills the requirements placed on the decision task by the commissioning higher-level processes.
202
203
203
204
The FulfillmentPhasePhase element documents all relevant information.
Copy file name to clipboardexpand all lines: specification/7___stmd.adoc
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
[#sec-stmd]
2
2
== Simulation Task Meta Data File Format
3
3
4
-
The __Simulation Task Meta Data__ file (short: STMD file) is an implementation of a GlueParticle for simulation tasks. It is specified to support traceability, quality assurance and re-usability for simulation tasks in terms of a credible simulation process as it is specified in #Document Reference#. The following sub-chapters describe the structure of an STMD file.
4
+
The __Simulation Task Meta Data__ file (short: STMD file) is an implementation of a GlueParticle for simulation tasks. It is specified to support traceability, quality assurance and re-usability for simulation tasks in terms of a credible simulation process as it is specified in <<CSP>>. The following sub-chapters describe the structure of an STMD file.
0 commit comments