Date	Change
2026-04-11	changes according to github issue #139, rename viewpoint diagram stereotypes and viewpoint short codes according to working group decision in 2026-04-10 meeting and adapt Descriptions accordingy: all viewpoints short code C prefixes (former Common Domain ) are now A Prefixes (Architecture Management Domain) Example: C2_ARAS -> A2_ARAS all viewpoints short code L and F prefixes (former Functional and Logical Domain) are now C prefixes ) Example: F1_SUCD -> C1_SUCD LSTD->SSTD (Logical Structure Definition Viewpoint -> System Structure Definition Viewpoint) LIEX->SIEX (Logical Internal Exchange Viewpoint -> System Internal Exchange Viewpoint) LITI->SITI (Logical Internal Interaction Viewpoint ->System Internal Interaction Viewpoint) LFUM->SFUM (Logical Functional Mapping Viewpoint-> System Function Mapping Viewpoint) removed Logical and Functional Domain Pages from Documentation (has been merged into conceptual Domain Documentation)
2026-03-26	Stereotype Renames implementing the Bremen Workshop decisions : Rename Logical stereotypes to Conceptual, SOI is a matter of context, sub elements have no specific stereotypes rename SAF_LogcicalElement to SAF_ConceptualSystem rename SAF_LogcicalSOI to SAF_LogicalSOI_deprecated new stereotype on part property SAF_ConceptualContextRole_SoI rename SAF_LogicalContextRole to SAF_ConceptualContextRole rename SAF_LogicalInternalRole to SAF_ConceptualInternalRole rename SAF_LogicalExternalSystem to SAF_LogicalExternalSystem_deprecated rename SAF_PhysicalExternalSystem to SAF_PhysicalExternalSystem_deprecated rename SAF_PhysicalSystem to SAF_PhysicalSystem_deprecated new stereotype on part property SAF_PhysicalContextRole_SoI rename SAF_PhysicalSoftwareElement to SAF_PhysicalSoftware rename SAF_PhysicalElement to SAF_PhysicalSystem rename SAF_PhysicalHardwareElement to SAF_PhysicalHardware rename SAF_PhysicalSystem to SAF_PhysicalSystem_deprecated rename SAF_O2_ODIK to SAF_O2_OETD rename SAF_O2_ODIK_Table to SAF_O2_OETD_Table rename SAF_F2_SDIK to SAF_F2_SETD rename SAF_F2_SDIK_Table to SAF_F2_SETD_Table rename SAF_ContextFunction to SAF_ContextFunction_deprecated rename SAF_SystemFunction to SAF_Function new stereotype SAF_FunctionContribution rename SAF_SystemFunctionSupport to SAF_FunctionSupport rename SAF_DomainKind to SAF_ConceptualExchangeType rename SAF_DomainKindComposition to SAF_ConceptualExchangeTypeComposition rename SAF_DomainKindDerivation to SAF_ConceptualExchangeTypeDerivation rename SAF_SystemPartialFunction to SAF_SystemPartialFunction_deprecated rename SAF_LogicalContext to SAF_ConceptualContext rename SAF_LogicalEnvironment to SAF_ConceptualEnvironment rename SAF_LogicalUser to SAF_ConceptualUser rename SAF_OperationalDomainKind to SAF_OperationalExchangeType Viewpoint Renames : Exchange Types are now named consistently  across Domains, this applies also to the viewpoints. rename Operational Domain Item Kind Viewpoint to Operational Exchange Type Viewpoint rename System Domain Item Kind Viewpoint to Conceptual Exchange Type Definition Viewpoint Concept Renames following the abovementioned changes
2025-10-16	Set the C2_CSTD Common Standards Definition Viewpoint to released Set the C2_TRMD Common Terms Definition Viewpoint to released
2025-10-12	Replace Allocate for mappings between Physical Domain items and conceptual items from the Logical /Functional domain by SAF_PhysicalRealization pointing from the physical element to the conceptual element (Implementation of issue #127)
2025-10-10	Rename P2_PETD Physical Exchange Type Viewpoint to P2_PETD Physical Exchange Type Definition Viewpoint and set status to released Set status of C8_EATR EA Traceability Viewpoint to released
2025-10-09	Add Table of proposed NAF & ADMBw mappings to EA Traceability Viewpoint Provide gallery mode also for example diagrams in development section of documentation.
2025-09-26	Apply relaxed naming convention for associations in conceptual model: pre and post fixing association names is no longer necessary, making them much more readable. Changed tracing of Operational Process usages solving issue #111 Add proposed Viewpoint  for definition of Physical Types, issue #124
2025-09-09	Add Enterprise Architecture Traceability Viewpoint in status proposed.
2025-07-04	Changes according to #118 Add example for Operational State VP, setting the VP to proposed Add implementation for referencing SAF_OperationalState from SAF_OperationalProcess as pre and postcondition, as tagged values of the stereotype SAF_OperationalProcess Add implementation for referencing SAF_SystemState from SAF_SystemFunction as pre and postcondition, as tagged values of the stereotype SAF_OperationalProcess
2025-06-27	Add Operational State Viewpoint as proposed in #102 new stereotypes SAF_O3_OSTA for Diagram and SAF_OperationalState   Set System State Viewpont to under construction to review Changes triggered by #102  new stereotype SAF_SystemState
2025-06-16	Cameo implementation: move diagram stereotypes for dev viewpoints from scm profile to saf profile rename them from SCM_* to SAF_*
2025-06-11	Rename Viewpoint Operational Performer to "Operational Performer Definition", adressing #114 Allow generalizations in Viewpoint "Operational Performer Definition", adresssing #113
2025-02-21	change domain colors according to #91 Common Domain:          "808080" ->"A5A5A5" Operational Domain:      "0000FF" -> "4472C4" Functional Domain:        "6699FF" ->"00B0F0" Logical Domain:              "FFFF33" ->"FFC000" Physical Domain:             "00FF00" -> "92D050" Development Domain:    "CCCCFF" -> "C040C0" reflect grid assignment of security extension viewpoints in stereotype names, partly adressing #90 SAF_C8_ASID_Table -> SAF_F7_ASID_Table SAF_C8_ASID -> SAF_F7_ASID SAF_C9_SECT -> SAF_F7_SECT SAF_C9_SECT_Table -> SAF_F7_SECT_Table SAF_C10_IMAN -> SAF_F7_IMAN SAF_C10_IMAN_Table -> SAF_F7_IMAN_Table SAF_C11_THSC -> SAF_F7_THSC SAF_C11_THSC_Table -> SAF_F7_THSC_Table SAF_C12_RIAN -> SAF_F7_RIAN SAF_C12_RIAN_Table -> SAF_F7_RIAN_Table
2024-11-08	include proposed viewpoints of University Hamburg for security risk analysis. F7_IMAN Impact Analysis Viewpoint F7_SECT Security Context Viewpoint F7_RIAN Security Risk Analysis Viewpoint F7_ASID Asset Identification Viewpoint F7_THSC Threat Szenario Viewpoint
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.