| Date | Change |
|---|
| 2024-11-07 | set maturity of D2_VPTO Framework Viewpoint Overview Viewpointunder construction (added profile diagram, concept diagram and example) |
| 2024-11-06 | - Fuse Dev Viewpoints Stakeholder Definition, Concern Definition and Rationale Definition in one, because the Information is tightly coupled. Resulting VP is D2_STKD Framework Stakeholder and Concern Definition Viewpoint. This solves issue 79
- Change multiplicity of relationship among SE Concepts from *--* to 1--0..* Framework Concept Defintion viewpoint and also describe that relations among SE concepts may be target of relations, too. see Issue 77.
|
| 2024-11-03 | - Add an additional formal traceability documentation showing traceability from SAF Viewpoints to ISO 15288:2023 processes and SEHB V5 Information Item definitions. See Issue 75
- Remove unused concerns from documentation. See Issue 76
|
| 2024-10-28 | Add dependency relationship among Standards to C2_CSTD Common Standards Definition Viewpoint, see Issue 71 Stereotype: SAF_StandardDependingOn
|
| 2024-10-27 | Switch over to new documentation format. |
| 2024-10-19 | set maturity of D2_VPTI Framework Viewpoint Implementation Viewpoint and D2_VPTD Framework Viewpoint Definition Viewpoint to under construction. |
| 2024-10-18 | set maturity of Functional Refinement Viewpoint F3_SFRE to under construction (added profile diagram and concept diagram). |
| 2024-10-17 | set maturity of Common Terms Definition Viewpoint C2_TRMD and Common Standards Definition Viewpoint C2_CSTD to under construction, reworked example and viewpoint descriptions |
| 2024-09-27 | set maturity of Development Viewpoints Framework Stakeholder Definition Viewpoint ( D1_STKD) and Framework Rationale Definition Viewpoint (D6_RATD) to"under construction" |
| 2024-09-25 | set maturity of Development Viewpoints Framework Concept Definition Viewpoint ( D2_COTD) and Framework Concern Definition Viewpoint (D6_CCND) to"under construction" |
| 2024-09-24 | change viewpoint short code of system use case viewpoint to F1_SUCD |
| 2024-09-06 | The use case and system process used in were renamed, in the course of model cleanup of the example. |
| 2024-07-29.1 | Add example for Operational Context Interaction (OCXI), set viewpoint to released. |
| 2024-06-30.1 | add proposed viewpoints supporting SAF development into new domain "SAF Developement" |
| 2024-06-23.1 | Add concerns, stakeholders, rationale to justify framework development and specification viewpoints - SAF Developer,
- SAF MBSE approach planner,
- SAF System Model user
revisit change grid definition viewpoint, status now under development. - it has alternate table representation collecting diagrams conform to viewpoints
- added a concern
|
| 2024-06-18.1 | all Stereotypes from SCM_Profile are prefixed "SCM_", not "SAF_". |
| 2024-06-15.1 | - write down naming conventions for table and matrix representations of Viewpoints (postfixed with "_Matrix" and "_Table"
- Rename stereotypes accordingly (SAF_L8_LFUM_Matrix, SAF_O8_OPRM_Table, SAF_F8_SCYM_Table, SAF_O8_OCYM_Table, SAF_F8_SRQT_Matrix, SAF_F6_SRQD_Table, SAF_C7_PRND_Table, SAF_C2_TRMD_Table)
- new, because there is a table representation. They're currently not covered by example : SAF_F3_SSTA_Table, SAF_F3_SPRO_Table, SAF_F2_SDIK_Table, SAF_F1_SUCS_Table, SAF_F1_SCXE_Table, SAF_F1_SCXD_Table
- apply coloring legend to all viewpoint concept and profile diagrams, and redactional corrections
- In Grid Definition Viewpoint, the Implementation of Viewpoint is changed to a user usable SAF_Viewpoint defined by SAF Profile, late the SAF_Viewpoint in SCM profile will be renamed to SCM_Viewpoint, since it is used to specify SAF, and not to be intendet to be used in system models.
- Add a library of SAF_Viewpoint objects to SAF_Profile to be used to plan modeling using grid Definition VP. The viewpoint objects collect automatically all views(diagrams conform to the Viewpoint)
- SAF_LogicalContextRole did not inherit from part property
- remove exposure of elements related to domain item kinds in SDIK, since It is by no way covered by concerns of VP SDIK.
|
| 2024-06-12.1 | - make internal role stereotypes inherit from part property
- dont expose abstract general physical role, but derived non abstract concepts PFUM and PLOM, partly adressing issue #60
- rename stereotypes for PLOM and PFUM Diagrams to *_Matrix, because the Representation is a matrix.
- logical element role was'nt exposed in PLOM
|
| 2024-06-07 .1 | - Argument concept in argumentation assurance viewpoint is no longer abstract, issue #56
- Separate network PIEX view, issue #57
|
| 2024-05-27 | - shift exposure of abstract concepts (general function, general function usage) to inherited concepts
- add missing concept for usage of partial function in system function
- fix implementation spec for function usages in functions context (profile not affected)
|
| 2024-05-18 | - add own diagram icons
- add a proposed viewpoint for security classifications
|
| 2024-04-30 | fix change stereotype SAF_O1_OCYD to be SAF_O1_OCXD to be consistent with Operational-Context-Definition shortcut |
| 2024-04-26.3 | Rename some viewpoints for more consistency with other viewpoint names. - Operational Context Interaction Viewpoint
- Operational Capability Definition Viewpoint
- Logical Structure Definition Viewpoint
- Physical Structure Definition Viewpoint
- Stakeholder Requirement Definition Viewpoint
- System Capability Definition Viewpoint
- System Requirement Definition Viewpoint
|
| 2024-04-26.2 | Rename Diagram Stereotypes to use the shortcuts, e.g. SAF_SLV02a_View is renamed to SAF_L2_LSTD. This removes the redundant "View" and "V", while keeping Domain and Aspect encoding. The Numbering is replaced by the same abbreviation as in the Viewpoint. |
| 2024-04-26.1 | Introduce Viewpoint shortcuts. They are intended to used as an easy to remember abbreviation for the longer viewpoint name, e.g. O1_OCXD for Operational Context Definition Viewpoint. The Domain and aspect are also encoded in the shortcut.
|
