textual-notation-of-model/packages/methods/saf/SAF_Viewpoints.sysml
0 view(s) · 104 declared member(s) view source on GitHub
Source
1/*2 * GfSE SAF viewpoint and concern definitions used by DE4SDV.3 *4 * Source: https://saf.gfse.org/userdoc/viewpoints.html5 * Repository: https://github.com/GfSE/SAF-SysMLV26 * License: Apache-2.07 *8 * This package is a source-backed reference catalogue, not a vendored copy.9 * DE4SDV-specific method-governance viewpoints remain in10 * DE4SDV_MethodViewpoints, not here.11 */1213package SAF_Viewpoints {14 private import Views::*;1516 // ─── Common Domain ───1718 concern def CommonTermsConcern {19 require constraint {20 doc /*21 * Reviewers need terms introduced by an increment to be defined22 * in a glossary or terminology section.23 */24 }25 }2627 viewpoint def CommonTermsDefinitionViewpoint {28 doc /*29 * SAF Common Domain: Common Terms Definition Viewpoint.30 * Aspect: Traceability & Mapping31 * Source: https://saf.gfse.org/userdoc/viewpoints.html32 */33 require constraint {34 doc /*35 * A common terms view shall define terms introduced by the36 * increment in a glossary or terminology section.37 */38 }39 }4041 concern def CommonStandardsConcern {42 require constraint {43 doc /*44 * Reviewers need standards and regulations used as constraints45 * or references to be registered with source attribution.46 */47 }48 }4950 viewpoint def CommonStandardsDefinitionViewpoint {51 doc /*52 * SAF Common Domain: Common Standards Definition Viewpoint.53 * Aspect: Traceability & Mapping54 * Source: https://saf.gfse.org/userdoc/viewpoints.html55 */56 require constraint {57 doc /*58 * A common standards view shall register standards, regulations,59 * and external references used as constraints with source60 * attribution and scope notes.61 */62 }63 }6465 concern def EATraceabilityConcern {66 require constraint {67 doc /*68 * Reviewers need increment artifacts linked together in a69 * traceability chain from needs to evidence.70 */71 }72 }737475 concern def StakeholderIdentificationConcern {76 require constraint {77 doc /*78 * Reviewers need roles affected by the increment to be79 * identified with their concerns.80 */81 }82 }8384 viewpoint def StakeholderIdentificationViewpoint {85 doc /*86 * SAF Common Domain: Stakeholder Identification Viewpoint.87 * Aspect: Context & Exchange88 * Source: https://saf.gfse.org/userdoc/viewpoints.html89 */90 require constraint {91 doc /*92 * A stakeholder identification view shall identify roles93 * affected by the increment and their concerns.94 */95 }96 }9798 // ─── Operational Domain ───99100 concern def OperationalContextConcern {101 require constraint {102 doc /*103 * Reviewers need to see the operational actors, context boundary,104 * and operational story for the feature increment.105 */106 }107 }108109 viewpoint def OperationalContextDefinitionViewpoint {110 doc /*111 * SAF Operational Domain: Operational Context Definition Viewpoint.112 * Aspect: Context & Exchange113 * Source: https://saf.gfse.org/userdoc/viewpoints.html114 */115 require constraint {116 doc /*117 * An operational context view shall show external actors, context118 * boundary, use case/actor framing, and operational behavior119 * (actions, items, flows, sequencing) for the increment.120 */121 }122 }123124 concern def OperationalStoryConcern {125 require constraint {126 doc /*127 * Reviewers need the operational scenario told in stakeholder128 * language to validate fitness-for-use intent.129 */130 }131 }132133 viewpoint def OperationalStoryViewpoint {134 doc /*135 * SAF Operational Domain: Operational Story Viewpoint.136 * Aspect: Interaction & Collaboration137 * Source: https://saf.gfse.org/userdoc/viewpoints.html138 */139 require constraint {140 doc /*141 * An operational story view shall tell the scenario in142 * stakeholder language, connecting operational context to143 * validation intent.144 */145 }146 }147148 concern def OperationalCapabilityConcern {149 require constraint {150 doc /*151 * Reviewers need the operational capability expected from the152 * product line to be described for the increment.153 */154 }155 }156157 viewpoint def OperationalCapabilityDefinitionViewpoint {158 doc /*159 * SAF Operational Domain: Operational Capability Definition Viewpoint.160 * Aspect: Process & Behavior161 * Source: https://saf.gfse.org/userdoc/viewpoints.html162 */163 require constraint {164 doc /*165 * An operational capability view shall describe the operational166 * capability expected from the product line for the increment.167 */168 }169 }170171 concern def OperationalProcessConcern {172 require constraint {173 doc /*174 * Reviewers need the operational flow or lifecycle process to be175 * described for the increment.176 */177 }178 }179180 viewpoint def OperationalProcessViewpoint {181 doc /*182 * SAF Operational Domain: Operational Process Viewpoint.183 * Aspect: Process & Behavior184 * Source: https://saf.gfse.org/userdoc/viewpoints.html185 */186 require constraint {187 doc /*188 * An operational process view shall describe the operational189 * flow or lifecycle process for the increment.190 */191 }192 }193194 concern def StakeholderNeedsConcern {195 require constraint {196 doc /*197 * Reviewers need stakeholder needs and validation intent to be198 * visible as requirement-like usages, not generic prose.199 */200 }201 }202203 viewpoint def StakeholderRequirementDefinitionViewpoint {204 doc /*205 * SAF Operational Domain: Stakeholder Requirement Definition Viewpoint.206 * Aspect: Traceability & Mapping207 * Source: https://saf.gfse.org/userdoc/viewpoints.html208 */209 require constraint {210 doc /*211 * A stakeholder needs view shall show stakeholder needs as native212 * requirement usages, stakeholder roles, and validation intent213 * for the increment.214 */215 }216 }217218 // ─── Functional Domain ───219220 concern def SystemContextConcern {221 require constraint {222 doc /*223 * Reviewers need the system boundary and external interfaces to224 * be defined for the increment.225 */226 }227 }228229230 concern def SystemUseCaseConcern {231 require constraint {232 doc /*233 * Reviewers need system use cases captured for the increment.234 */235 }236 }237238 viewpoint def SystemUseCaseViewpoint {239 doc /*240 * SAF Functional Domain: System Use Case Viewpoint.241 * Aspect: Interaction & Collaboration242 * Source: https://saf.gfse.org/userdoc/viewpoints.html243 */244 require constraint {245 doc /*246 * A system use case view shall capture system use cases with247 * actors and objectives.248 */249 }250 }251252 concern def SystemCapabilityConcern {253 require constraint {254 doc /*255 * Reviewers need system capabilities defined for the increment.256 */257 }258 }259260 viewpoint def SystemCapabilityDefinitionViewpoint {261 doc /*262 * SAF Functional Domain: System Capability Definition Viewpoint.263 * Aspect: Process & Behavior264 * Source: https://saf.gfse.org/userdoc/viewpoints.html265 */266 require constraint {267 doc /*268 * A system capability view shall define system capabilities269 * and their relationships.270 */271 }272 }273274 concern def FunctionalBehaviorConcern {275 require constraint {276 doc /*277 * Reviewers need the functional responsibilities, information items,278 * flows, and sequencing for the feature increment to be visible279 * with requirement trace.280 */281 }282 }283284 viewpoint def SystemFunctionalBreakdownStructureViewpoint {285 doc /*286 * SAF Functional Domain: System Functional Breakdown Structure Viewpoint.287 * Aspect: Process & Behavior288 * Source: https://saf.gfse.org/userdoc/viewpoints.html289 */290 require constraint {291 doc /*292 * A functional behavior view shall show functional responsibilities293 * (actions), information items, flows, and sequencing, with294 * requirement trace to functions.295 */296 }297 }298299 concern def SystemProcessConcern {300 require constraint {301 doc /*302 * Reviewers need behavior and process sequencing described for303 * the increment.304 */305 }306 }307308 viewpoint def SystemProcessViewpoint {309 doc /*310 * SAF Functional Domain: System Process Viewpoint.311 * Aspect: Process & Behavior312 * Source: https://saf.gfse.org/userdoc/viewpoints.html313 */314 require constraint {315 doc /*316 * A system process view shall describe behavior and process317 * sequencing for the increment, including state transitions318 * and temporal ordering.319 */320 }321 }322323 concern def FunctionalInterfaceConcern {324 require constraint {325 doc /*326 * Reviewers need the functional boundary ports, signal character,327 * direction, producer/consumer mapping, and upstreaming posture328 * for DE4SDV candidate VSS extension signals.329 */330 }331 }332333 viewpoint def SystemInterfaceDefinitionViewpoint {334 doc /*335 * SAF Functional Domain: System Interface Definition Viewpoint.336 * Aspect: Interaction & Collaboration337 * Source: https://saf.gfse.org/userdoc/viewpoints.html338 */339 require constraint {340 doc /*341 * A functional interface view shall show boundary port definitions,342 * their typed items, signal character, direction, and the functional343 * chain that owns the ports.344 */345 }346 }347348 concern def RequirementTraceConcern {349 require constraint {350 doc /*351 * Reviewers need requirement candidates traced to stakeholder needs,352 * with verification methods and satisfaction status, including353 * what is not yet satisfied.354 */355 }356 }357358 viewpoint def SystemRequirementDefinitionViewpoint {359 doc /*360 * SAF Functional Domain: System Requirement Definition Viewpoint.361 * Aspect: Traceability & Mapping362 * Source: https://saf.gfse.org/userdoc/viewpoints.html363 */364 require constraint {365 doc /*366 * A requirement definition view shall show requirement candidates367 * with their subject, stakeholder parameters, and required constraint368 * bodies.369 */370 }371 }372373 viewpoint def SystemRequirementTraceabilityViewpoint {374 doc /*375 * SAF Functional Domain: System Requirement Traceability Viewpoint.376 * Aspect: Traceability & Mapping377 * Source: https://saf.gfse.org/userdoc/viewpoints.html378 */379 require constraint {380 doc /*381 * A requirement traceability view shall show requirement candidates,382 * their stakeholder need sources, verification methods, and383 * satisfaction status, including explicitly unsatisfied items.384 */385 }386 }387388 // ─── Conceptual Domain ───389390 concern def ConceptualStructureConcern {391 require constraint {392 doc /*393 * Reviewers need the conceptual system decomposition, conceptual element394 * responsibilities, and ownership boundaries to be visible.395 */396 }397 }398399 viewpoint def SystemStructureDefinitionViewpoint {400 doc /*401 * SAF Conceptual Domain: System Structure Definition Viewpoint.402 * Aspect: Taxonomy & Structure403 * Source: https://saf.gfse.org/userdoc/viewpoints.html404 */405 require constraint {406 doc /*407 * A logical structure view shall show the conceptual system boundary and408 * its hierarchical decomposition into conceptual elements responsible for409 * realizing system functions.410 */411 }412 }413414 concern def ConceptualInternalExchangeConcern {415 require constraint {416 doc /*417 * Reviewers need the typed conceptual interfaces, exchanges, directions,418 * and delegation from the conceptual system boundary to internal elements.419 */420 }421 }422423 viewpoint def SystemInternalExchangeViewpoint {424 doc /*425 * SAF Conceptual Domain: System Internal Exchange Viewpoint.426 * Aspect: Interaction & Collaboration427 * Source: https://saf.gfse.org/userdoc/viewpoints.html428 */429 require constraint {430 doc /*431 * A logical internal exchange view shall show the conceptual system432 * boundary, internal conceptual elements, connected interfaces, delegated433 * boundary interfaces, and exchanged logical items.434 */435 }436 }437438 concern def ConceptualInternalInteractionConcern {439 require constraint {440 doc /*441 * Reviewers need conceptual interactions (sequences, message ordering)442 * described for the increment.443 */444 }445 }446447 viewpoint def SystemInternalInteractionViewpoint {448 doc /*449 * SAF Conceptual Domain: System Internal Interaction Viewpoint.450 * Aspect: Interaction & Collaboration451 * Source: https://saf.gfse.org/userdoc/viewpoints.html452 */453 require constraint {454 doc /*455 * A logical internal interaction view shall show interactions456 * between conceptual elements, including message sequencing and457 * temporal relationships.458 */459 }460 }461462 concern def ConceptualFunctionMappingConcern {463 require constraint {464 doc /*465 * Reviewers need every system function allocated to one or more logical466 * elements without implying a physical or software implementation.467 */468 }469 }470471 viewpoint def SystemFunctionMappingViewpoint {472 doc /*473 * SAF Conceptual Domain: System Functional Mapping Viewpoint.474 * Aspect: Process & Behavior475 * Source: https://saf.gfse.org/userdoc/viewpoints.html476 */477 require constraint {478 doc /*479 * A logical functional mapping view shall show the allocation of system480 * functions and partial functions to conceptual system elements.481 */482 }483 }484485 // ─── Physical Domain ───486487 concern def PhysicalContextConcern {488 require constraint {489 doc /*490 * Reviewer question: What is inside the candidate physical system,491 * which external physical systems interact with it, and where is the492 * physical context boundary?493 */494 }495 }496497 viewpoint def PhysicalContextDefinitionViewpoint {498 doc /*499 * SAF Physical Domain: P1_PCXD Physical Context Definition Viewpoint.500 * Aspect: Context & Exchange501 * Source: https://saf.gfse.org/userdoc/viewpoints.html502 */503 require constraint {504 doc /*505 * A physical context definition view shall show the candidate physical506 * system boundary, external physical systems, and their context roles.507 */508 }509 }510511 concern def PhysicalContextExchangeConcern {512 require constraint {513 doc /*514 * Reviewer question: What typed physical items cross the candidate515 * system boundary, and which context roles participate in each exchange?516 */517 }518 }519520 viewpoint def PhysicalContextExchangeViewpoint {521 doc /*522 * SAF Physical Domain: P1_PCXE Physical Context Exchange Viewpoint.523 * Aspect: Context & Exchange524 * Source: https://saf.gfse.org/userdoc/viewpoints.html525 */526 require constraint {527 doc /*528 * A physical context exchange view shall show boundary-crossing physical529 * exchanges, their typed items, and participating context roles. Textual530 * bindings and flows remain authoritative for exchange direction.531 */532 }533 }534535 concern def PhysicalExchangeTypeConcern {536 require constraint {537 doc /*538 * Reviewer question: Which reusable physical exchange item, endpoint,539 * and protocol definitions type the candidate realization?540 */541 }542 }543544545 concern def PhysicalStructureConcern {546 require constraint {547 doc /*548 * Reviewer question: What physical hardware, software, and mechanical549 * elements make up the candidate system, and in which internal roles550 * are they used?551 */552 }553 }554555 viewpoint def PhysicalStructureDefinitionViewpoint {556 doc /*557 * SAF Physical Domain: P2_PSTD Physical Structure Definition Viewpoint.558 * Aspect: Taxonomy & Structure559 * Source: https://saf.gfse.org/userdoc/viewpoints.html560 */561 require constraint {562 doc /*563 * A physical structure definition view shall show the physical system564 * boundary and its breakdown into physical hardware, software, and565 * mechanical elements, including the roles in which elements are used.566 */567 }568 }569570 concern def PhysicalInterfaceConcern {571 require constraint {572 doc /*573 * Reviewer question: Which reusable physical interface and protocol574 * definitions apply, and what typed ports and exchanged item directions575 * do they define?576 */577 }578 }579580 viewpoint def PhysicalInterfaceDefinitionViewpoint {581 doc /*582 * SAF Physical Domain: P5_PIFD Physical Interface Definition Viewpoint.583 * Aspect: Interaction & Collaboration584 * Source: https://saf.gfse.org/userdoc/viewpoints.html585 */586 require constraint {587 doc /*588 * A physical interface definition view shall show physical interface589 * definitions with typed ports, exchanged item directions, protocol590 * definitions, and compatibility or specialization relationships.591 */592 }593 }594595 concern def PhysicalInternalExchangeConcern {596 require constraint {597 doc /*598 * Reviewer question: Which internal physical roles exchange each typed599 * item? When an exchange crosses the subject boundary, which boundary600 * interface delegates it to an internal role?601 */602 }603 }604605 viewpoint def PhysicalInternalExchangeViewpoint {606 doc /*607 * SAF Physical Domain: P4_PIEX Physical Internal Exchange Viewpoint.608 * Aspect: Interaction & Collaboration609 * Source: https://saf.gfse.org/userdoc/viewpoints.html610 */611 require constraint {612 doc /*613 * A physical internal exchange view shall show internal physical roles614 * and typed exchanges. When an exchange crosses the subject boundary,615 * the view shall show the boundary interface and its delegation to an616 * internal role. Textual bindings and flows remain authoritative for617 * exchange direction.618 */619 }620 }621622 concern def PhysicalFunctionalMappingConcern {623 require constraint {624 doc /*625 * Reviewer question: Which physical/software elements realize which626 * system functions?627 */628 }629 }630631 viewpoint def PhysicalFunctionalMappingViewpoint {632 doc /*633 * SAF Physical Domain: P8_PFUM Physical Functional Mapping Viewpoint.634 * Aspect: Process & Behavior635 * Source: https://saf.gfse.org/userdoc/viewpoints.html636 */637 require constraint {638 doc /*639 * A physical functional mapping view shall show the allocation of640 * system functions to physical/software elements, including partial641 * and missing realizations.642 */643 }644 }645646 concern def PhysicalLogicalMappingConcern {647 require constraint {648 doc /*649 * Reviewer question: Which conceptual element roles are realized by which650 * physical element roles?651 */652 }653 }654655 viewpoint def PhysicalLogicalMappingViewpoint {656 doc /*657 * SAF Physical Domain: P8_PLOM Physical Logical Mapping Viewpoint.658 * Aspect: Traceability & Mapping659 * Source: https://saf.gfse.org/userdoc/viewpoints.html660 */661 require constraint {662 doc /*663 * A physical logical mapping view shall show logical and physical664 * element breakdowns and the realization relationships that identify665 * which physical element roles implement each conceptual element role.666 */667 }668 }669670 concern def PhysicalLogicalItemMappingConcern {671 require constraint {672 doc /*673 * Reviewer question: Which logical information items are realized by674 * which physical exchange items, and which similarly named or adjacent675 * physical items remain semantically distinct?676 */677 }678 }679680681 // ─── Safety/Security Domain ───682683 concern def AssetIdentificationConcern {684 require constraint {685 doc /*686 * Reviewers need assets affected by the feature or toolchain to be687 * identified for safety and security analysis.688 */689 }690 }691692 viewpoint def AssetIdentificationViewpoint {693 doc /*694 * SAF Safety/Security Domain: Asset Identification Viewpoint.695 * Aspect: Safety & Security696 * Source: https://saf.gfse.org/userdoc/viewpoints.html697 */698 require constraint {699 doc /*700 * An asset identification view shall identify assets affected by701 * the feature or toolchain, including safety-relevant and702 * security-relevant assets.703 */704 }705 }706707 concern def SecurityContextConcern {708 require constraint {709 doc /*710 * Reviewers need the security boundary and context identified for711 * the increment.712 */713 }714 }715716 viewpoint def SecurityContextViewpoint {717 doc /*718 * SAF Safety/Security Domain: Security Context Viewpoint.719 * Aspect: Safety & Security720 * Source: https://saf.gfse.org/userdoc/viewpoints.html721 */722 require constraint {723 doc /*724 * A security context view shall identify the security boundary,725 * trusted/untrusted domains, and security-relevant context roles.726 */727 }728 }729730 concern def SecurityRiskAnalysisConcern {731 require constraint {732 doc /*733 * Reviewers need threat and risk analysis captured for the increment.734 */735 }736 }737738 viewpoint def SecurityRiskAnalysisViewpoint {739 doc /*740 * SAF Safety/Security Domain: Security Risk Analysis Viewpoint.741 * Aspect: Safety & Security742 * Source: https://saf.gfse.org/userdoc/viewpoints.html743 */744 require constraint {745 doc /*746 * A security risk analysis view shall capture threats, risks,747 * mitigations, and residual risk for the increment.748 */749 }750 }751752 concern def ThreatSzenarioConcern {753 require constraint {754 doc /*755 * Reviewers need threat scenarios described for the increment.756 */757 }758 }759760 viewpoint def ThreatSzenarioViewpoint {761 doc /*762 * SAF Safety/Security Domain: Threat Szenario Viewpoint.763 * Aspect: Safety & Security764 * Source: https://saf.gfse.org/userdoc/viewpoints.html765 */766 require constraint {767 doc /*768 * A threat scenario view shall describe threat scenarios with769 * attack vectors, affected assets, and potential impacts.770 */771 }772 }773774 concern def ArgumentationAssuranceConcern {775 require constraint {776 doc /*777 * Reviewers need claims, arguments, evidence, and gaps linked778 * in an assurance argument for the increment.779 */780 }781 }782783 viewpoint def ArgumentationAssuranceViewpoint {784 doc /*785 * SAF Safety/Security Domain: Argumentation Assurance Viewpoint.786 * Aspect: Traceability & Mapping787 * Source: https://saf.gfse.org/userdoc/viewpoints.html788 */789 require constraint {790 doc /*791 * An argumentation assurance view shall link claims, arguments,792 * evidence, and gaps in an assurance argument structure.793 */794 }795 }796797 // ─── GfSE SAF-SysMLV2 additions ───798 concern def ImpactAnalysisConcern {799 require constraint {800 doc /*801 * Reviewers need ImpactAnalysisViewpoint captured with source-backed frame bindings for the increment.802 */803 }804 }805806 viewpoint def ImpactAnalysisViewpoint {807 doc /*808 * SAF Safety/Security Domain: ImpactAnalysis Viewpoint809 * Aspect: Safety & Security810 * Source: https://saf.gfse.org/userdoc/viewpoints.html811 * GfSE frame bindings: SeverityOfLoss.812 */813 require constraint {814 doc /*815 * A ImpactAnalysisViewpoint view shall show the source-backed SAF frame bindings for the increment.816 */817 }818 }819 concern def OperationalDomainItemKindConcern {820 require constraint {821 doc /*822 * Reviewers need OperationalDomainItemKindViewpoint captured with source-backed frame bindings for the increment.823 */824 }825 }826827 viewpoint def OperationalDomainItemKindViewpoint {828 doc /*829 * SAF Operational Domain: OperationalDomainItemKind Viewpoint830 * Aspect: Taxonomy & Structure831 * Source: https://saf.gfse.org/userdoc/viewpoints.html832 * GfSE frame bindings: OperationalExchanges.833 */834 require constraint {835 doc /*836 * A OperationalDomainItemKindViewpoint view shall show the source-backed SAF frame bindings for the increment.837 */838 }839 }840 concern def SystemContextInteractionConcern {841 require constraint {842 doc /*843 * Reviewers need SystemContextInteractionViewpoint captured with source-backed frame bindings for the increment.844 */845 }846 }847848 viewpoint def SystemContextInteractionViewpoint {849 doc /*850 * SAF Functional Domain: SystemContextInteraction Viewpoint851 * Aspect: Context & Exchange852 * Source: https://saf.gfse.org/userdoc/viewpoints.html853 * GfSE frame bindings: SystemUtilization, ResponseTimeRequirements, ConceptualInteractionSequence.854 */855 require constraint {856 doc /*857 * A SystemContextInteractionViewpoint view shall show the source-backed SAF frame bindings for the increment.858 */859 }860 }861 concern def OperationalContextExchangeConcern {862 require constraint {863 doc /*864 * Reviewers need OperationalContextExchangeViewpoint captured with source-backed frame bindings for the increment.865 */866 }867 }868869 viewpoint def OperationalContextExchangeViewpoint {870 doc /*871 * SAF Operational Domain: OperationalContextExchange Viewpoint872 * Aspect: Context & Exchange873 * Source: https://saf.gfse.org/userdoc/viewpoints.html874 * GfSE frame bindings: OperationalContextExchanges.875 */876 require constraint {877 doc /*878 * A OperationalContextExchangeViewpoint view shall show the source-backed SAF frame bindings for the increment.879 */880 }881 }882 concern def SystemDomainItemKindConcern {883 require constraint {884 doc /*885 * Reviewers need SystemDomainItemKindViewpoint captured with source-backed frame bindings for the increment.886 */887 }888 }889890 viewpoint def SystemDomainItemKindViewpoint {891 doc /*892 * SAF Functional Domain: SystemDomainItemKind Viewpoint893 * Aspect: Taxonomy & Structure894 * Source: https://saf.gfse.org/userdoc/viewpoints.html895 * GfSE frame bindings: LogicalArchitectureItems.896 */897 require constraint {898 doc /*899 * A SystemDomainItemKindViewpoint view shall show the source-backed SAF frame bindings for the increment.900 */901 }902 }903 concern def SystemFunctionalRefinementConcern {904 require constraint {905 doc /*906 * Reviewers need SystemFunctionalRefinementViewpoint captured with source-backed frame bindings for the increment.907 */908 }909 }910911 viewpoint def SystemFunctionalRefinementViewpoint {912 doc /*913 * SAF Functional Domain: SystemFunctionalRefinement Viewpoint914 * Aspect: Process & Behavior915 * Source: https://saf.gfse.org/userdoc/viewpoints.html916 * GfSE frame bindings: SubfunctionInteractions, SystemFunctionBreakdown, SystemFunctionDecomposition.917 */918 require constraint {919 doc /*920 * A SystemFunctionalRefinementViewpoint view shall show the source-backed SAF frame bindings for the increment.921 */922 }923 }924 concern def SystemStateConcern {925 require constraint {926 doc /*927 * Reviewers need SystemStateViewpoint captured with source-backed frame bindings for the increment.928 */929 }930 }931932 viewpoint def SystemStateViewpoint {933 doc /*934 * SAF Functional Domain: SystemState Viewpoint935 * Aspect: Taxonomy & Structure936 * Source: https://saf.gfse.org/userdoc/viewpoints.html937 * GfSE frame bindings: SystemModes, SystemFunctionsDependentOnModes.938 */939 require constraint {940 doc /*941 * A SystemStateViewpoint view shall show the source-backed SAF frame bindings for the increment.942 */943 }944 }945 concern def OperationalContextInteractionConcern {946 require constraint {947 doc /*948 * Reviewers need OperationalContextInteractionViewpoint captured with source-backed frame bindings for the increment.949 */950 }951 }952953 viewpoint def OperationalContextInteractionViewpoint {954 doc /*955 * SAF Operational Domain: OperationalContextInteraction Viewpoint956 * Aspect: Context & Exchange957 * Source: https://saf.gfse.org/userdoc/viewpoints.html958 * GfSE frame bindings: OperationalProcessThreads.959 */960 require constraint {961 doc /*962 * A OperationalContextInteractionViewpoint view shall show the source-backed SAF frame bindings for the increment.963 */964 }965 }966 concern def GridDefinitionConcern {967 require constraint {968 doc /*969 * Reviewers need GridDefinitionViewpoint captured with source-backed frame bindings for the increment.970 */971 }972 }973974 viewpoint def GridDefinitionViewpoint {975 doc /*976 * SAF Functional Domain: GridDefinition Viewpoint977 * Aspect: Traceability & Mapping978 * Source: https://saf.gfse.org/userdoc/viewpoints.html979 * GfSE frame bindings: ViewpointsUsedInSystemModel, FrameworkViewpoints.980 */981 require constraint {982 doc /*983 * A GridDefinitionViewpoint view shall show the source-backed SAF frame bindings for the increment.984 */985 }986 }987 concern def FrameworkConceptDefinitionConcern {988 require constraint {989 doc /*990 * Reviewers need FrameworkConceptDefinitionViewpoint captured with source-backed frame bindings for the increment.991 */992 }993 }994995 viewpoint def FrameworkConceptDefinitionViewpoint {996 doc /*997 * SAF Framework Domain: FrameworkConceptDefinition Viewpoint998 * Aspect: SAF Development Domain999 * Source: https://saf.gfse.org/userdoc/viewpoints.html1000 * GfSE frame bindings: RelationsBetweenSEConcepts, ConstraintsOnSEConcepts, SEConceptsCovered.1001 */1002 require constraint {1003 doc /*1004 * A FrameworkConceptDefinitionViewpoint view shall show the source-backed SAF frame bindings for the increment.1005 */1006 }1007 }1008 concern def FrameworkConcernOverviewConcern {1009 require constraint {1010 doc /*1011 * Reviewers need FrameworkViewpointOverviewViewpoint captured with source-backed frame bindings for the increment.1012 */1013 }1014 }10151016 viewpoint def FrameworkViewpointOverviewViewpoint {1017 doc /*1018 * SAF Framework Domain: Framework ViewpointOverview Viewpoint1019 * Aspect: SAF Development Domain1020 * Source: https://saf.gfse.org/userdoc/viewpoints.html1021 * GfSE frame bindings: DefinitionOfGridRows, DefinitionOfGridColumns, FrameworkGridStructure, ViewpointLocationInGrid, MaturityOfViewpoints, AvailableViewpoints.1022 */1023 require constraint {1024 doc /*1025 * A FrameworkViewpointOverviewViewpoint view shall show the source-backed SAF frame bindings for the increment.1026 */1027 }1028 }1029 concern def FrameworkStakeholderandConcernDefinitionConcern {1030 require constraint {1031 doc /*1032 * Reviewers need FrameworkStakeholderandConcernDefinitionViewpoint captured with source-backed frame bindings for the increment.1033 */1034 }1035 }10361037 viewpoint def FrameworkStakeholderandConcernDefinitionViewpoint {1038 doc /*1039 * SAF Framework Domain: FrameworkStakeholderandConcernDefinition Viewpoint1040 * Aspect: SAF Development Domain1041 * Source: https://saf.gfse.org/userdoc/viewpoints.html1042 * GfSE frame bindings: StakeholderConcerns, FrameworkStakeholders, StakeholderConcernsReasons.1043 */1044 require constraint {1045 doc /*1046 * A FrameworkStakeholderandConcernDefinitionViewpoint view shall show the source-backed SAF frame bindings for the increment.1047 */1048 }1049 }1050 concern def FrameworkConcernDefinitionConcern {1051 require constraint {1052 doc /*1053 * Reviewers need FrameworkViewpointDefinitionViewpoint captured with source-backed frame bindings for the increment.1054 */1055 }1056 }10571058 viewpoint def FrameworkViewpointDefinitionViewpoint {1059 doc /*1060 * SAF Framework Domain: Framework ViewpointDefinition Viewpoint1061 * Aspect: SAF Development Domain1062 * Source: https://saf.gfse.org/userdoc/viewpoints.html1063 * GfSE frame bindings: ConceptsExposedInViewpoints, ConcernsFramedByViewpoints, DefinitionOfViewpoints, ViewpointLocationInGrid, ViewpointPurpose, ViewpointPresentations, ViewpointDependencies, SupportForSEStandards.1064 */1065 require constraint {1066 doc /*1067 * A FrameworkViewpointDefinitionViewpoint view shall show the source-backed SAF frame bindings for the increment.1068 */1069 }1070 }1071 concern def FrameworkConcernImplementationConcern {1072 require constraint {1073 doc /*1074 * Reviewers need FrameworkViewpointImplementationViewpoint captured with source-backed frame bindings for the increment.1075 */1076 }1077 }10781079 viewpoint def FrameworkViewpointImplementationViewpoint {1080 doc /*1081 * SAF Framework Domain: Framework ViewpointImplementation Viewpoint1082 * Aspect: SAF Development Domain1083 * Source: https://saf.gfse.org/userdoc/viewpoints.html1084 * GfSE frame bindings: ImplementationOfFrameworkConcepts, ViewpointImplementation.1085 */1086 require constraint {1087 doc /*1088 * A FrameworkViewpointImplementationViewpoint view shall show the source-backed SAF frame bindings for the increment.1089 */1090 }1091 }1092 concern def FrameworkImplementationTraceabilityConcern {1093 require constraint {1094 doc /*1095 * Reviewers need FrameworkImplementationTraceabilityViewpoint captured with source-backed frame bindings for the increment.1096 */1097 }1098 }10991100 viewpoint def FrameworkImplementationTraceabilityViewpoint {1101 doc /*1102 * SAF Framework Domain: FrameworkImplementationTraceability Viewpoint1103 * Aspect: SAF Development Domain1104 * Source: https://saf.gfse.org/userdoc/viewpoints.html1105 * GfSE frame bindings: ImplementationOfFrameworkConcepts, FrameworkModelElements.1106 */1107 require constraint {1108 doc /*1109 * A FrameworkImplementationTraceabilityViewpoint view shall show the source-backed SAF frame bindings for the increment.1110 */1111 }1112 }1113 concern def FrameworkStereotypeOverviewConcern {1114 require constraint {1115 doc /*1116 * Reviewers need FrameworkStereotypeOverviewViewpoint captured with source-backed frame bindings for the increment.1117 */1118 }1119 }11201121 viewpoint def FrameworkStereotypeOverviewViewpoint {1122 doc /*1123 * SAF Framework Domain: FrameworkStereotypeOverview Viewpoint1124 * Aspect: SAF Development Domain1125 * Source: https://saf.gfse.org/userdoc/viewpoints.html1126 * GfSE frame bindings: FrameworkModelElements.1127 */1128 require constraint {1129 doc /*1130 * A FrameworkStereotypeOverviewViewpoint view shall show the source-backed SAF frame bindings for the increment.1131 */1132 }1133 }1134 concern def OperationalPerformerConcern {1135 require constraint {1136 doc /*1137 * Reviewers need OperationalPerformerViewpoint captured with source-backed frame bindings for the increment.1138 */1139 }1140 }11411142 viewpoint def OperationalPerformerViewpoint {1143 doc /*1144 * SAF Operational Domain: OperationalPerformer Viewpoint1145 * Aspect: Taxonomy & Structure1146 * Source: https://saf.gfse.org/userdoc/viewpoints.html1147 * GfSE frame bindings: OrganizationalEntitiesForCapability, RelationshipsBetweenParties.1148 */1149 require constraint {1150 doc /*1151 * A OperationalPerformerViewpoint view shall show the source-backed SAF frame bindings for the increment.1152 */1153 }1154 }1155 concern def OperationalCapabilityMappingConcern {1156 require constraint {1157 doc /*1158 * Reviewers need OperationalCapabilityMappingViewpoint captured with source-backed frame bindings for the increment.1159 */1160 }1161 }11621163 viewpoint def OperationalCapabilityMappingViewpoint {1164 doc /*1165 * SAF Operational Domain: OperationalCapabilityMapping Viewpoint1166 * Aspect: Process & Behavior1167 * Source: https://saf.gfse.org/userdoc/viewpoints.html1168 * GfSE frame bindings: OperationalCapabilityRelationships.1169 */1170 require constraint {1171 doc /*1172 * A OperationalCapabilityMappingViewpoint view shall show the source-backed SAF frame bindings for the increment.1173 */1174 }1175 }1176 concern def OperationalProcessMappingConcern {1177 require constraint {1178 doc /*1179 * Reviewers need OperationalProcessMappingViewpoint captured with source-backed frame bindings for the increment.1180 */1181 }1182 }11831184 viewpoint def OperationalProcessMappingViewpoint {1185 doc /*1186 * SAF Operational Domain: OperationalProcessMapping Viewpoint1187 * Aspect: Process & Behavior1188 * Source: https://saf.gfse.org/userdoc/viewpoints.html1189 * GfSE frame bindings: OperationalProcessRelationships.1190 */1191 require constraint {1192 doc /*1193 * A OperationalProcessMappingViewpoint view shall show the source-backed SAF frame bindings for the increment.1194 */1195 }1196 }1197}1198