textual-notation-of-model/packages/methods/de4sdv/de4sdv_method_context.sysml

Source

1/*2 * DE4SDV method context and problem statement kernel.3 *4 * This package adapts only the useful SYSMOD/SysML v2 problem-statement pattern5 * for DE4SDV. It is not a full SYSMOD implementation or vendored upstream6 * library.7 *8 * A problem statement is modeled as a requirement. A system context captures9 * the system of interest, actors, and relevant context elements for an10 * increment. DE4SDV intentionally does not introduce a generic ProjectContext11 * abstraction here; feature increments can compose problem statements,12 * stakeholders, and system context directly.13 */1415package DE4SDV_MethodContext {16  private import DE4SDV_SYSMODAdapter::*;17  /* Requirement derivation discriminator: DE4SDV application connection18   * definition. A requirement usage connected as derivedRequirement19   * originates from the stakeholder need connected as need. The typed ends20   * carry the predicate's domain and range; the definition documentation21   * carries its native direction, claim strength, and claim boundary.22   * Design-input provenance only — no satisfaction, implication,23   * verification, evidence, or acceptance claim. */2425  connection def DerivesFromNeed {26    end need : StakeholderNeedCandidate;27    end derivedRequirement : RequirementCandidate;28    doc /* Design-input provenance: the derivedRequirement originates from29         * the stakeholder need. Native direction: need -> derivedRequirement.30         * Claim strength: derivation (provenance only: neither satisfaction31         * nor logical implication between the connected usages; no32         * allocation, verification, evidence, or acceptance claim). */33  }3435  /* Re-exported so feature packages can assign `attribute :>> status =36   * ReqStatus::...` (ADR 0009) without importing the adapter directly. */37  public import ReqStatus;3839  /* Re-exported so feature packages can assign `attribute :>>40   * verificationStatus = VVStatus::...` (ADR 0009 amendment) without41   * importing the adapter directly. */42  public import VVStatus;4344  part def EngineeringIncrement {45    doc /* Bounded DE4SDV work package that changes, tests, or publishes engineering knowledge. */46  }4748  part def FeatureIncrement :> EngineeringIncrement {49    doc /* Engineering increment focused on a product-line feature, common capability, or variability decision. */50  }5152  part def NeedsRequirementsIncrement :> EngineeringIncrement {53    doc /* Engineering increment focused on needs, draft requirements, traceability, and V&V planning. */54  }5556  part def SystemLayer {57    doc /* Coarse ASELCM-style system layer used to frame DE4SDV increments. */58  }5960  part def System1SDVProductLine :> SystemLayer {61    doc /* Configurable SDV product line and configured vehicle/software variants. */62  }6364  part def System2EngineeringAndAssuranceSystem :> SystemLayer {65    doc /* DE4SDV model-based life-cycle engineering, assurance, simulation, and evidence system. */66  }6768  part def System3OpenSourceGovernanceEcosystem :> SystemLayer {69    doc /* Open innovation ecosystem that governs, evolves, reviews, and improves DE4SDV. */70  }7172  part def MethodStackElement {73    doc /* Method/tooling layer participating in a DE4SDV increment. */74  }7576  part def SAFViewpointSelection :> MethodStackElement;77  part def SYSMODMethodFlow :> MethodStackElement;78  part def DE4SDVOntologyKernel :> MethodStackElement;79  part def SysMLv2ModelExpression :> MethodStackElement;80  part def VSSCandidateSignalCatalog :> MethodStackElement;8182  part def OperationalScopeBoundary {83    doc /* Boundary separating in-scope and out-of-scope content for an increment. */84  }8586  part def InScopeItem {87    doc /* Scope item included in the current increment. */88  }8990  part def OutOfScopeItem {91    doc /* Scope item explicitly deferred or excluded from the current increment. */92  }9394  requirement def ProblemStatement {95    doc /* The problem that is to be solved by the system or increment. */96  }9798  requirement def StakeholderNeedCandidate :> RequirementsManagementAttributeBase {99    doc /* Generic base for stakeholder needs before acceptance and quality gate. Inherits the NRM Chapter 15 attribute set adopted via ADR 0009. */100  }101102  requirement def ProductLineCommonCapabilityNeed :> StakeholderNeedCandidate {103    doc /* Need for a common product-line capability required across member products. */104  }105  requirement def EngineeringTraceabilityNeed :> StakeholderNeedCandidate {106    doc /* Need for engineering traceability, boundary visibility, and controlled scope. */107  }108109  requirement def ProductLineClassificationNeed :> StakeholderNeedCandidate {110    doc /* Need for explicit feature/common-capability classification and variation modeling. */111  }112113  requirement def RegulatoryVisibilityNeed :> StakeholderNeedCandidate {114    doc /* Need for visible regulatory assumptions without compliance claims. */115  }116117  requirement def VerificationPlanningNeed :> StakeholderNeedCandidate {118    doc /* Need for separate controlled V&V planning attachments. */119  }120121  requirement def ProductSafetyAvailabilityNeed :> StakeholderNeedCandidate {122    doc /* Need for bounded degradation and availability indication. */123  }124125  requirement def RequirementCandidate :> SYSMODRequirementBase, RequirementsManagementAttributeBase {126    doc /* Generic base for design-input requirement candidates before acceptance.127         * Specializes the SYSMOD requirement seam, inheriting obligation,128         * stability, and motivation metadata for requirement candidates.129         * DE4SDV candidate lifecycle semantics remain local. */130  }131132  requirement def FunctionalRequirementCandidate :> RequirementCandidate {133    doc /* Candidate requirement for functional behavior. */134  }135136  requirement def SafetyConstraintRequirementCandidate :> RequirementCandidate {137    doc /* Candidate requirement for safety constraints and non-activation. */138  }139140  requirement def SecurityConstraintRequirementCandidate :> RequirementCandidate {141    doc /* Candidate requirement for security and trust-boundary constraints. */142  }143144  requirement def ProductLineConstraintRequirementCandidate :> RequirementCandidate {145    doc /* Candidate requirement for product-line classification and variability constraints. */146  }147148  requirement def TraceabilityConstraintRequirementCandidate :> RequirementCandidate {149    doc /* Candidate requirement for traceability and V&V planning constraints. */150  }151152  requirement def EvidenceContractTraceabilityRequirementCandidate :> RequirementCandidate {153    doc /* Candidate requirement for evidence-contract traceability to controlled boundaries. */154  }155156  requirement def RegulatoryConstraintCandidate :> RequirementsManagementAttributeBase {157    doc /* Constraint or reference derived from a standard, regulation, or homologation-relevant source. Carries controlled source identity and never implies compliance. Grounds the ontology RegulatoryConstraint class and R003 derivation targets. */158  }159160  part def ArchitectureDecisionRecord {161    doc /* Reviewed architecture or method decision (recorded as an ADR in Git) that a design-input requirement can trace to as its semantic origin. Grounds the ontology ArchitectureDecisionRecord class and R003 derivation targets. */162  }163164  part def IncrementAssumption {165    doc /* Assumption recorded for an engineering increment. */166  }167168  part def IncrementGap {169    doc /* Gap or unresolved item recorded for an engineering increment. */170  }171172  part def IncrementScope {173    doc /* Scope boundary for an engineering increment. */174  }175176  part def IncrementTraceabilityShell {177    doc /* Traceability structure connecting an increment to its sources and downstream artifacts. */178  }179180  part def IncrementEngineeringQuestion {181    doc /* Engineering question that an increment answers. */182  }183184  part def IncrementLifecycleDecision {185    doc /* Lifecycle decision that an increment supports. */186  }187188  part def MissingRealizationRecord {189    doc /* Record of a missing realization allocation for a conceptual element. */190  }191192  part def BlockedRealizationBranchRecord {193    doc /* Record of a blocked realization branch due to a source defect or gap. */194  }195196  part def SourceContributionRecord {197    doc /* Record of an observable source contribution to a partial realization. */198  }199200  part def SystemContext {201    doc /* Context containing the system actors, the system of interest, and their relationships. */202    part actors[*];203    part systemOfInterest;204  }205}206