textual-notation-of-model/packages/methods/saf/SAF_Viewpoints.sysml
0 view(s) · 104 declared member(s)
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 // ─── Conceptual Domain ───219 // System requirements, functional architecture, and logical architecture220 // are distinct artifact kinds in this domain. Logical architecture is the221 // technology-independent structural view. Current System* viewpoint names222 // describe the conceptual system; they do not rename the logical223 // architecture artifact or the Architecture Definition process.224225 concern def SystemContextConcern {226 require constraint {227 doc /*228 * Reviewers need the system boundary and external interfaces to229 * be defined for the increment.230 */231 }232 }233234235 concern def SystemUseCaseConcern {236 require constraint {237 doc /*238 * Reviewers need system use cases captured for the increment.239 */240 }241 }242243 viewpoint def SystemUseCaseViewpoint {244 doc /*245 * SAF Conceptual Domain: System Use Case Viewpoint.246 * Aspect: Interaction & Collaboration247 * Source: https://saf.gfse.org/userdoc/viewpoints.html248 */249 require constraint {250 doc /*251 * A system use case view shall capture system use cases with252 * actors and objectives.253 */254 }255 }256257 concern def SystemCapabilityConcern {258 require constraint {259 doc /*260 * Reviewers need system capabilities defined for the increment.261 */262 }263 }264265 viewpoint def SystemCapabilityDefinitionViewpoint {266 doc /*267 * SAF Conceptual Domain: System Capability Definition Viewpoint.268 * Aspect: Process & Behavior269 * Source: https://saf.gfse.org/userdoc/viewpoints.html270 */271 require constraint {272 doc /*273 * A system capability view shall define system capabilities274 * and their relationships.275 */276 }277 }278279 concern def FunctionalBehaviorConcern {280 require constraint {281 doc /*282 * Reviewers need the functional responsibilities, information items,283 * flows, and sequencing for the feature increment to be visible284 * with requirement trace.285 */286 }287 }288289 viewpoint def SystemFunctionalBreakdownStructureViewpoint {290 doc /*291 * SAF Conceptual Domain: System Functional Breakdown Structure Viewpoint.292 * Aspect: Process & Behavior293 * Source: https://saf.gfse.org/userdoc/viewpoints.html294 */295 require constraint {296 doc /*297 * A functional behavior view shall show functional responsibilities298 * (actions), information items, flows, and sequencing, with299 * requirement trace to functions.300 */301 }302 }303304 concern def SystemProcessConcern {305 require constraint {306 doc /*307 * Reviewers need behavior and process sequencing described for308 * the increment.309 */310 }311 }312313 viewpoint def SystemProcessViewpoint {314 doc /*315 * SAF Conceptual Domain: System Process Viewpoint.316 * Aspect: Process & Behavior317 * Source: https://saf.gfse.org/userdoc/viewpoints.html318 */319 require constraint {320 doc /*321 * A system process view shall describe behavior and process322 * sequencing for the increment, including state transitions323 * and temporal ordering.324 */325 }326 }327328 concern def FunctionalInterfaceConcern {329 require constraint {330 doc /*331 * Reviewers need the functional boundary ports, signal character,332 * direction, producer/consumer mapping, and upstreaming posture333 * for DE4SDV candidate VSS extension signals.334 */335 }336 }337338 viewpoint def SystemInterfaceDefinitionViewpoint {339 doc /*340 * SAF Conceptual Domain: System Interface Definition Viewpoint.341 * Aspect: Interaction & Collaboration342 * Source: https://saf.gfse.org/userdoc/viewpoints.html343 */344 require constraint {345 doc /*346 * A functional interface view shall show boundary port definitions,347 * their typed items, signal character, direction, and the functional348 * chain that owns the ports.349 */350 }351 }352353 concern def RequirementTraceConcern {354 require constraint {355 doc /*356 * Reviewers need requirement candidates traced to stakeholder needs,357 * with verification methods and satisfaction status, including358 * what is not yet satisfied.359 */360 }361 }362363 viewpoint def SystemRequirementDefinitionViewpoint {364 doc /*365 * SAF Conceptual Domain: System Requirement Definition Viewpoint.366 * Aspect: Traceability & Mapping367 * Source: https://saf.gfse.org/userdoc/viewpoints.html368 */369 require constraint {370 doc /*371 * A requirement definition view shall show requirement candidates372 * with their subject, stakeholder parameters, and required constraint373 * bodies.374 */375 }376 }377378 viewpoint def SystemRequirementTraceabilityViewpoint {379 doc /*380 * SAF Conceptual Domain: System Requirement Traceability Viewpoint.381 * Aspect: Traceability & Mapping382 * Source: https://saf.gfse.org/userdoc/viewpoints.html383 */384 require constraint {385 doc /*386 * A requirement traceability view shall show requirement candidates,387 * their stakeholder need sources, verification methods, and388 * satisfaction status, including explicitly unsatisfied items.389 */390 }391 }392393 // ─── Conceptual Domain (continued) ───394395 concern def ConceptualStructureConcern {396 require constraint {397 doc /*398 * Reviewers need the conceptual system decomposition, conceptual element399 * responsibilities, and ownership boundaries to be visible.400 */401 }402 }403404 viewpoint def SystemStructureDefinitionViewpoint {405 doc /*406 * SAF Conceptual Domain: System Structure Definition Viewpoint.407 * Aspect: Taxonomy & Structure408 * Source: https://saf.gfse.org/userdoc/viewpoints.html409 */410 require constraint {411 doc /*412 * A logical structure view shall show the conceptual system boundary and413 * its hierarchical decomposition into conceptual elements responsible for414 * realizing system functions.415 */416 }417 }418419 concern def ConceptualInternalExchangeConcern {420 require constraint {421 doc /*422 * Reviewers need the typed conceptual interfaces, exchanges, directions,423 * and delegation from the conceptual system boundary to internal elements.424 */425 }426 }427428 viewpoint def SystemInternalExchangeViewpoint {429 doc /*430 * SAF Conceptual Domain: System Internal Exchange Viewpoint.431 * Aspect: Interaction & Collaboration432 * Source: https://saf.gfse.org/userdoc/viewpoints.html433 */434 require constraint {435 doc /*436 * A logical internal exchange view shall show the conceptual system437 * boundary, internal conceptual elements, connected interfaces, delegated438 * boundary interfaces, and exchanged logical items.439 */440 }441 }442443 concern def ConceptualInternalInteractionConcern {444 require constraint {445 doc /*446 * Reviewers need conceptual interactions (sequences, message ordering)447 * described for the increment.448 */449 }450 }451452 viewpoint def SystemInternalInteractionViewpoint {453 doc /*454 * SAF Conceptual Domain: System Internal Interaction Viewpoint.455 * Aspect: Interaction & Collaboration456 * Source: https://saf.gfse.org/userdoc/viewpoints.html457 */458 require constraint {459 doc /*460 * A logical internal interaction view shall show interactions461 * between conceptual elements, including message sequencing and462 * temporal relationships.463 */464 }465 }466467 concern def ConceptualFunctionMappingConcern {468 require constraint {469 doc /*470 * Reviewers need every system function allocated to one or more logical471 * elements without implying a physical or software implementation.472 */473 }474 }475476 viewpoint def SystemFunctionMappingViewpoint {477 doc /*478 * SAF Conceptual Domain: System Functional Mapping Viewpoint.479 * Aspect: Process & Behavior480 * Source: https://saf.gfse.org/userdoc/viewpoints.html481 */482 require constraint {483 doc /*484 * A logical functional mapping view shall show the allocation of system485 * functions and partial functions to conceptual system elements.486 */487 }488 }489490 // ─── Physical Domain ───491492 concern def PhysicalContextConcern {493 require constraint {494 doc /*495 * Reviewer question: What is inside the candidate physical system,496 * which external physical systems interact with it, and where is the497 * physical context boundary?498 */499 }500 }501502 viewpoint def PhysicalContextDefinitionViewpoint {503 doc /*504 * SAF Physical Domain: P1_PCXD Physical Context Definition Viewpoint.505 * Aspect: Context & Exchange506 * Source: https://saf.gfse.org/userdoc/viewpoints.html507 */508 require constraint {509 doc /*510 * A physical context definition view shall show the candidate physical511 * system boundary, external physical systems, and their context roles.512 */513 }514 }515516 concern def PhysicalContextExchangeConcern {517 require constraint {518 doc /*519 * Reviewer question: What typed physical items cross the candidate520 * system boundary, and which context roles participate in each exchange?521 */522 }523 }524525 viewpoint def PhysicalContextExchangeViewpoint {526 doc /*527 * SAF Physical Domain: P1_PCXE Physical Context Exchange Viewpoint.528 * Aspect: Context & Exchange529 * Source: https://saf.gfse.org/userdoc/viewpoints.html530 */531 require constraint {532 doc /*533 * A physical context exchange view shall show boundary-crossing physical534 * exchanges, their typed items, and participating context roles. Textual535 * bindings and flows remain authoritative for exchange direction.536 */537 }538 }539540 concern def PhysicalExchangeTypeConcern {541 require constraint {542 doc /*543 * Reviewer question: Which reusable physical exchange item, endpoint,544 * and protocol definitions type the candidate realization?545 */546 }547 }548549550 concern def PhysicalStructureConcern {551 require constraint {552 doc /*553 * Reviewer question: What physical hardware, software, and mechanical554 * elements make up the candidate system, and in which internal roles555 * are they used?556 */557 }558 }559560 viewpoint def PhysicalStructureDefinitionViewpoint {561 doc /*562 * SAF Physical Domain: P2_PSTD Physical Structure Definition Viewpoint.563 * Aspect: Taxonomy & Structure564 * Source: https://saf.gfse.org/userdoc/viewpoints.html565 */566 require constraint {567 doc /*568 * A physical structure definition view shall show the physical system569 * boundary and its breakdown into physical hardware, software, and570 * mechanical elements, including the roles in which elements are used.571 */572 }573 }574575 concern def PhysicalInterfaceConcern {576 require constraint {577 doc /*578 * Reviewer question: Which reusable physical interface and protocol579 * definitions apply, and what typed ports and exchanged item directions580 * do they define?581 */582 }583 }584585 viewpoint def PhysicalInterfaceDefinitionViewpoint {586 doc /*587 * SAF Physical Domain: P5_PIFD Physical Interface Definition Viewpoint.588 * Aspect: Interaction & Collaboration589 * Source: https://saf.gfse.org/userdoc/viewpoints.html590 */591 require constraint {592 doc /*593 * A physical interface definition view shall show physical interface594 * definitions with typed ports, exchanged item directions, protocol595 * definitions, and compatibility or specialization relationships.596 */597 }598 }599600 concern def PhysicalInternalExchangeConcern {601 require constraint {602 doc /*603 * Reviewer question: Which internal physical roles exchange each typed604 * item? When an exchange crosses the subject boundary, which boundary605 * interface delegates it to an internal role?606 */607 }608 }609610 viewpoint def PhysicalInternalExchangeViewpoint {611 doc /*612 * SAF Physical Domain: P4_PIEX Physical Internal Exchange Viewpoint.613 * Aspect: Interaction & Collaboration614 * Source: https://saf.gfse.org/userdoc/viewpoints.html615 */616 require constraint {617 doc /*618 * A physical internal exchange view shall show internal physical roles619 * and typed exchanges. When an exchange crosses the subject boundary,620 * the view shall show the boundary interface and its delegation to an621 * internal role. Textual bindings and flows remain authoritative for622 * exchange direction.623 */624 }625 }626627 concern def PhysicalFunctionalMappingConcern {628 require constraint {629 doc /*630 * Reviewer question: Which physical/software elements realize which631 * system functions?632 */633 }634 }635636 viewpoint def PhysicalFunctionalMappingViewpoint {637 doc /*638 * SAF Physical Domain: P8_PFUM Physical Functional Mapping Viewpoint.639 * Aspect: Process & Behavior640 * Source: https://saf.gfse.org/userdoc/viewpoints.html641 */642 require constraint {643 doc /*644 * A physical functional mapping view shall show the allocation of645 * system functions to physical/software elements, including partial646 * and missing realizations.647 */648 }649 }650651 concern def PhysicalLogicalMappingConcern {652 require constraint {653 doc /*654 * Reviewer question: Which conceptual element roles are realized by which655 * physical element roles?656 */657 }658 }659660 viewpoint def PhysicalLogicalMappingViewpoint {661 doc /*662 * SAF Physical Domain: P8_PLOM Physical Logical Mapping Viewpoint.663 * Aspect: Traceability & Mapping664 * Source: https://saf.gfse.org/userdoc/viewpoints.html665 */666 require constraint {667 doc /*668 * A physical logical mapping view shall show logical and physical669 * element breakdowns and the realization relationships that identify670 * which physical element roles implement each conceptual element role.671 */672 }673 }674675 concern def PhysicalLogicalItemMappingConcern {676 require constraint {677 doc /*678 * Reviewer question: Which logical information items are realized by679 * which physical exchange items, and which similarly named or adjacent680 * physical items remain semantically distinct?681 */682 }683 }684685686 // ─── Safety/Security Domain ───687688 concern def AssetIdentificationConcern {689 require constraint {690 doc /*691 * Reviewers need assets affected by the feature or toolchain to be692 * identified for safety and security analysis.693 */694 }695 }696697 viewpoint def AssetIdentificationViewpoint {698 doc /*699 * SAF Safety/Security Domain: Asset Identification Viewpoint.700 * Aspect: Safety & Security701 * Source: https://saf.gfse.org/userdoc/viewpoints.html702 */703 require constraint {704 doc /*705 * An asset identification view shall identify assets affected by706 * the feature or toolchain, including safety-relevant and707 * security-relevant assets.708 */709 }710 }711712 concern def SecurityContextConcern {713 require constraint {714 doc /*715 * Reviewers need the security boundary and context identified for716 * the increment.717 */718 }719 }720721 viewpoint def SecurityContextViewpoint {722 doc /*723 * SAF Safety/Security Domain: Security Context Viewpoint.724 * Aspect: Safety & Security725 * Source: https://saf.gfse.org/userdoc/viewpoints.html726 */727 require constraint {728 doc /*729 * A security context view shall identify the security boundary,730 * trusted/untrusted domains, and security-relevant context roles.731 */732 }733 }734735 concern def SecurityRiskAnalysisConcern {736 require constraint {737 doc /*738 * Reviewers need threat and risk analysis captured for the increment.739 */740 }741 }742743 viewpoint def SecurityRiskAnalysisViewpoint {744 doc /*745 * SAF Safety/Security Domain: Security Risk Analysis Viewpoint.746 * Aspect: Safety & Security747 * Source: https://saf.gfse.org/userdoc/viewpoints.html748 */749 require constraint {750 doc /*751 * A security risk analysis view shall capture threats, risks,752 * mitigations, and residual risk for the increment.753 */754 }755 }756757 concern def ThreatSzenarioConcern {758 require constraint {759 doc /*760 * Reviewers need threat scenarios described for the increment.761 */762 }763 }764765 viewpoint def ThreatSzenarioViewpoint {766 doc /*767 * SAF Safety/Security Domain: Threat Szenario Viewpoint.768 * Aspect: Safety & Security769 * Source: https://saf.gfse.org/userdoc/viewpoints.html770 */771 require constraint {772 doc /*773 * A threat scenario view shall describe threat scenarios with774 * attack vectors, affected assets, and potential impacts.775 */776 }777 }778779 concern def ArgumentationAssuranceConcern {780 require constraint {781 doc /*782 * Reviewers need claims, arguments, evidence, and gaps linked783 * in an assurance argument for the increment.784 */785 }786 }787788 viewpoint def ArgumentationAssuranceViewpoint {789 doc /*790 * SAF Safety/Security Domain: Argumentation Assurance Viewpoint.791 * Aspect: Traceability & Mapping792 * Source: https://saf.gfse.org/userdoc/viewpoints.html793 */794 require constraint {795 doc /*796 * An argumentation assurance view shall link claims, arguments,797 * evidence, and gaps in an assurance argument structure.798 */799 }800 }801802 // ─── GfSE SAF-SysMLV2 additions ───803 concern def ImpactAnalysisConcern {804 require constraint {805 doc /*806 * Reviewers need ImpactAnalysisViewpoint captured with source-backed frame bindings for the increment.807 */808 }809 }810811 viewpoint def ImpactAnalysisViewpoint {812 doc /*813 * SAF Safety/Security Domain: ImpactAnalysis Viewpoint814 * Aspect: Safety & Security815 * Source: https://saf.gfse.org/userdoc/viewpoints.html816 * GfSE frame bindings: SeverityOfLoss.817 */818 require constraint {819 doc /*820 * A ImpactAnalysisViewpoint view shall show the source-backed SAF frame bindings for the increment.821 */822 }823 }824 concern def OperationalDomainItemKindConcern {825 require constraint {826 doc /*827 * Reviewers need OperationalDomainItemKindViewpoint captured with source-backed frame bindings for the increment.828 */829 }830 }831832 viewpoint def OperationalDomainItemKindViewpoint {833 doc /*834 * SAF Operational Domain: OperationalDomainItemKind Viewpoint835 * Aspect: Taxonomy & Structure836 * Source: https://saf.gfse.org/userdoc/viewpoints.html837 * GfSE frame bindings: OperationalExchanges.838 */839 require constraint {840 doc /*841 * A OperationalDomainItemKindViewpoint view shall show the source-backed SAF frame bindings for the increment.842 */843 }844 }845 concern def SystemContextInteractionConcern {846 require constraint {847 doc /*848 * Reviewers need SystemContextInteractionViewpoint captured with source-backed frame bindings for the increment.849 */850 }851 }852853 viewpoint def SystemContextInteractionViewpoint {854 doc /*855 * SAF Conceptual Domain: SystemContextInteraction Viewpoint856 * Aspect: Context & Exchange857 * Source: https://saf.gfse.org/userdoc/viewpoints.html858 * GfSE frame bindings: SystemUtilization, ResponseTimeRequirements, ConceptualInteractionSequence.859 */860 require constraint {861 doc /*862 * A SystemContextInteractionViewpoint view shall show the source-backed SAF frame bindings for the increment.863 */864 }865 }866 concern def OperationalContextExchangeConcern {867 require constraint {868 doc /*869 * Reviewers need OperationalContextExchangeViewpoint captured with source-backed frame bindings for the increment.870 */871 }872 }873874 viewpoint def OperationalContextExchangeViewpoint {875 doc /*876 * SAF Operational Domain: OperationalContextExchange Viewpoint877 * Aspect: Context & Exchange878 * Source: https://saf.gfse.org/userdoc/viewpoints.html879 * GfSE frame bindings: OperationalContextExchanges.880 */881 require constraint {882 doc /*883 * A OperationalContextExchangeViewpoint view shall show the source-backed SAF frame bindings for the increment.884 */885 }886 }887 concern def SystemDomainItemKindConcern {888 require constraint {889 doc /*890 * Reviewers need SystemDomainItemKindViewpoint captured with source-backed frame bindings for the increment.891 */892 }893 }894895 viewpoint def SystemDomainItemKindViewpoint {896 doc /*897 * SAF Conceptual Domain: SystemDomainItemKind Viewpoint898 * Aspect: Taxonomy & Structure899 * Source: https://saf.gfse.org/userdoc/viewpoints.html900 * GfSE frame bindings: LogicalArchitectureItems.901 */902 require constraint {903 doc /*904 * A SystemDomainItemKindViewpoint view shall show the source-backed SAF frame bindings for the increment.905 */906 }907 }908 concern def SystemFunctionalRefinementConcern {909 require constraint {910 doc /*911 * Reviewers need SystemFunctionalRefinementViewpoint captured with source-backed frame bindings for the increment.912 */913 }914 }915916 viewpoint def SystemFunctionalRefinementViewpoint {917 doc /*918 * SAF Conceptual Domain: SystemFunctionalRefinement Viewpoint919 * Aspect: Process & Behavior920 * Source: https://saf.gfse.org/userdoc/viewpoints.html921 * GfSE frame bindings: SubfunctionInteractions, SystemFunctionBreakdown, SystemFunctionDecomposition.922 */923 require constraint {924 doc /*925 * A SystemFunctionalRefinementViewpoint view shall show the source-backed SAF frame bindings for the increment.926 */927 }928 }929 concern def SystemStateConcern {930 require constraint {931 doc /*932 * Reviewers need SystemStateViewpoint captured with source-backed frame bindings for the increment.933 */934 }935 }936937 viewpoint def SystemStateViewpoint {938 doc /*939 * SAF Conceptual Domain: SystemState Viewpoint940 * Aspect: Taxonomy & Structure941 * Source: https://saf.gfse.org/userdoc/viewpoints.html942 * GfSE frame bindings: SystemModes, SystemFunctionsDependentOnModes.943 */944 require constraint {945 doc /*946 * A SystemStateViewpoint view shall show the source-backed SAF frame bindings for the increment.947 */948 }949 }950 concern def OperationalContextInteractionConcern {951 require constraint {952 doc /*953 * Reviewers need OperationalContextInteractionViewpoint captured with source-backed frame bindings for the increment.954 */955 }956 }957958 viewpoint def OperationalContextInteractionViewpoint {959 doc /*960 * SAF Operational Domain: OperationalContextInteraction Viewpoint961 * Aspect: Context & Exchange962 * Source: https://saf.gfse.org/userdoc/viewpoints.html963 * GfSE frame bindings: OperationalProcessThreads.964 */965 require constraint {966 doc /*967 * A OperationalContextInteractionViewpoint view shall show the source-backed SAF frame bindings for the increment.968 */969 }970 }971 concern def GridDefinitionConcern {972 require constraint {973 doc /*974 * Reviewers need GridDefinitionViewpoint captured with source-backed frame bindings for the increment.975 */976 }977 }978979 viewpoint def GridDefinitionViewpoint {980 doc /*981 * SAF Conceptual Domain: GridDefinition Viewpoint982 * Aspect: Traceability & Mapping983 * Source: https://saf.gfse.org/userdoc/viewpoints.html984 * GfSE frame bindings: ViewpointsUsedInSystemModel, FrameworkViewpoints.985 */986 require constraint {987 doc /*988 * A GridDefinitionViewpoint view shall show the source-backed SAF frame bindings for the increment.989 */990 }991 }992 concern def FrameworkConceptDefinitionConcern {993 require constraint {994 doc /*995 * Reviewers need FrameworkConceptDefinitionViewpoint captured with source-backed frame bindings for the increment.996 */997 }998 }9991000 viewpoint def FrameworkConceptDefinitionViewpoint {1001 doc /*1002 * SAF Framework Domain: FrameworkConceptDefinition Viewpoint1003 * Aspect: SAF Development Domain1004 * Source: https://saf.gfse.org/userdoc/viewpoints.html1005 * GfSE frame bindings: RelationsBetweenSEConcepts, ConstraintsOnSEConcepts, SEConceptsCovered.1006 */1007 require constraint {1008 doc /*1009 * A FrameworkConceptDefinitionViewpoint view shall show the source-backed SAF frame bindings for the increment.1010 */1011 }1012 }1013 concern def FrameworkConcernOverviewConcern {1014 require constraint {1015 doc /*1016 * Reviewers need FrameworkViewpointOverviewViewpoint captured with source-backed frame bindings for the increment.1017 */1018 }1019 }10201021 viewpoint def FrameworkViewpointOverviewViewpoint {1022 doc /*1023 * SAF Framework Domain: Framework ViewpointOverview Viewpoint1024 * Aspect: SAF Development Domain1025 * Source: https://saf.gfse.org/userdoc/viewpoints.html1026 * GfSE frame bindings: DefinitionOfGridRows, DefinitionOfGridColumns, FrameworkGridStructure, ViewpointLocationInGrid, MaturityOfViewpoints, AvailableViewpoints.1027 */1028 require constraint {1029 doc /*1030 * A FrameworkViewpointOverviewViewpoint view shall show the source-backed SAF frame bindings for the increment.1031 */1032 }1033 }1034 concern def FrameworkStakeholderandConcernDefinitionConcern {1035 require constraint {1036 doc /*1037 * Reviewers need FrameworkStakeholderandConcernDefinitionViewpoint captured with source-backed frame bindings for the increment.1038 */1039 }1040 }10411042 viewpoint def FrameworkStakeholderandConcernDefinitionViewpoint {1043 doc /*1044 * SAF Framework Domain: FrameworkStakeholderandConcernDefinition Viewpoint1045 * Aspect: SAF Development Domain1046 * Source: https://saf.gfse.org/userdoc/viewpoints.html1047 * GfSE frame bindings: StakeholderConcerns, FrameworkStakeholders, StakeholderConcernsReasons.1048 */1049 require constraint {1050 doc /*1051 * A FrameworkStakeholderandConcernDefinitionViewpoint view shall show the source-backed SAF frame bindings for the increment.1052 */1053 }1054 }1055 concern def FrameworkConcernDefinitionConcern {1056 require constraint {1057 doc /*1058 * Reviewers need FrameworkViewpointDefinitionViewpoint captured with source-backed frame bindings for the increment.1059 */1060 }1061 }10621063 viewpoint def FrameworkViewpointDefinitionViewpoint {1064 doc /*1065 * SAF Framework Domain: Framework ViewpointDefinition Viewpoint1066 * Aspect: SAF Development Domain1067 * Source: https://saf.gfse.org/userdoc/viewpoints.html1068 * GfSE frame bindings: ConceptsExposedInViewpoints, ConcernsFramedByViewpoints, DefinitionOfViewpoints, ViewpointLocationInGrid, ViewpointPurpose, ViewpointPresentations, ViewpointDependencies, SupportForSEStandards.1069 */1070 require constraint {1071 doc /*1072 * A FrameworkViewpointDefinitionViewpoint view shall show the source-backed SAF frame bindings for the increment.1073 */1074 }1075 }1076 concern def FrameworkConcernImplementationConcern {1077 require constraint {1078 doc /*1079 * Reviewers need FrameworkViewpointImplementationViewpoint captured with source-backed frame bindings for the increment.1080 */1081 }1082 }10831084 viewpoint def FrameworkViewpointImplementationViewpoint {1085 doc /*1086 * SAF Framework Domain: Framework ViewpointImplementation Viewpoint1087 * Aspect: SAF Development Domain1088 * Source: https://saf.gfse.org/userdoc/viewpoints.html1089 * GfSE frame bindings: ImplementationOfFrameworkConcepts, ViewpointImplementation.1090 */1091 require constraint {1092 doc /*1093 * A FrameworkViewpointImplementationViewpoint view shall show the source-backed SAF frame bindings for the increment.1094 */1095 }1096 }1097 concern def FrameworkImplementationTraceabilityConcern {1098 require constraint {1099 doc /*1100 * Reviewers need FrameworkImplementationTraceabilityViewpoint captured with source-backed frame bindings for the increment.1101 */1102 }1103 }11041105 viewpoint def FrameworkImplementationTraceabilityViewpoint {1106 doc /*1107 * SAF Framework Domain: FrameworkImplementationTraceability Viewpoint1108 * Aspect: SAF Development Domain1109 * Source: https://saf.gfse.org/userdoc/viewpoints.html1110 * GfSE frame bindings: ImplementationOfFrameworkConcepts, FrameworkModelElements.1111 */1112 require constraint {1113 doc /*1114 * A FrameworkImplementationTraceabilityViewpoint view shall show the source-backed SAF frame bindings for the increment.1115 */1116 }1117 }1118 concern def FrameworkStereotypeOverviewConcern {1119 require constraint {1120 doc /*1121 * Reviewers need FrameworkStereotypeOverviewViewpoint captured with source-backed frame bindings for the increment.1122 */1123 }1124 }11251126 viewpoint def FrameworkStereotypeOverviewViewpoint {1127 doc /*1128 * SAF Framework Domain: FrameworkStereotypeOverview Viewpoint1129 * Aspect: SAF Development Domain1130 * Source: https://saf.gfse.org/userdoc/viewpoints.html1131 * GfSE frame bindings: FrameworkModelElements.1132 */1133 require constraint {1134 doc /*1135 * A FrameworkStereotypeOverviewViewpoint view shall show the source-backed SAF frame bindings for the increment.1136 */1137 }1138 }1139 concern def OperationalPerformerConcern {1140 require constraint {1141 doc /*1142 * Reviewers need OperationalPerformerViewpoint captured with source-backed frame bindings for the increment.1143 */1144 }1145 }11461147 viewpoint def OperationalPerformerViewpoint {1148 doc /*1149 * SAF Operational Domain: OperationalPerformer Viewpoint1150 * Aspect: Taxonomy & Structure1151 * Source: https://saf.gfse.org/userdoc/viewpoints.html1152 * GfSE frame bindings: OrganizationalEntitiesForCapability, RelationshipsBetweenParties.1153 */1154 require constraint {1155 doc /*1156 * A OperationalPerformerViewpoint view shall show the source-backed SAF frame bindings for the increment.1157 */1158 }1159 }1160 concern def OperationalCapabilityMappingConcern {1161 require constraint {1162 doc /*1163 * Reviewers need OperationalCapabilityMappingViewpoint captured with source-backed frame bindings for the increment.1164 */1165 }1166 }11671168 viewpoint def OperationalCapabilityMappingViewpoint {1169 doc /*1170 * SAF Operational Domain: OperationalCapabilityMapping Viewpoint1171 * Aspect: Process & Behavior1172 * Source: https://saf.gfse.org/userdoc/viewpoints.html1173 * GfSE frame bindings: OperationalCapabilityRelationships.1174 */1175 require constraint {1176 doc /*1177 * A OperationalCapabilityMappingViewpoint view shall show the source-backed SAF frame bindings for the increment.1178 */1179 }1180 }1181 concern def OperationalProcessMappingConcern {1182 require constraint {1183 doc /*1184 * Reviewers need OperationalProcessMappingViewpoint captured with source-backed frame bindings for the increment.1185 */1186 }1187 }11881189 viewpoint def OperationalProcessMappingViewpoint {1190 doc /*1191 * SAF Operational Domain: OperationalProcessMapping Viewpoint1192 * Aspect: Process & Behavior1193 * Source: https://saf.gfse.org/userdoc/viewpoints.html1194 * GfSE frame bindings: OperationalProcessRelationships.1195 */1196 require constraint {1197 doc /*1198 * A OperationalProcessMappingViewpoint view shall show the source-backed SAF frame bindings for the increment.1199 */1200 }1201 }1202}1203