Skip to main content
If you previously published to beta.sysand.org, follow the migration guide to move your packages to sysand.com.

sysmod

published by mbse4u
4398 released
Latest Validation errors
sysand add mbse4u/sysmod
README Source Changelog Licenses 0 usages 8 versions Validation

Change Log

v5.1.7

  • MicroStory snippets the-project and problem-statement: the project now declares the views projectCoverView, projectCoverAIView, problemStatementView, and problemStatementAIView itself, as the Delivery Drone example does since 5.1.6 (they are no longer inherited from SYSMOD::Project).

  • Fixed the double bullet ("- - ") of the black box/white box entry in the 5.1.6 change log.

  • Fixed a parser error in the Percentage constraint (#39): the assert constraint now refers to the attribute value with that instead of self (that >= 0.0 and that <= 1.0).

  • Extracted the ISO/IEC/IEEE 15288 processes, the stakeholders, and the concerns into the new top-level library package ISO15288Processes in its own file SYSMOD15288.sysml:

    • The process action definitions moved from SYSMOD::ISO15288Processes; the #refinement dependencies of the SYSMOD steps refer to the new package.
    • The stakeholders and concerns moved from SYSMODViews::Stakeholders and SYSMODViews::Concerns to ISO15288Processes::Stakeholders and ISO15288Processes::Concerns. SYSMODViews imports the concerns for its viewpoints.
    • Models that use the stakeholder roles import ISO15288Processes::Stakeholders::* instead of SYSMODViews::Stakeholders::* (Delivery Drone project, MicroStory problem-statement).
    • .meta.json indexes the new package; scripts/generate_views_doc.py and the views-doc workflow read the processes, stakeholders, and concerns from SYSMOD15288.sysml. Updated README.md and the regenerated SYSMODViews.md.
  • Black box/white box separation for the solution architectures, as for the brownfield, system idea, and specification contexts:

    • functionalContext, logicalContext, and productContext are the black box contexts and specialize specificationContext; productContext no longer specializes specificationContextImpl, and productSystem now redefines the black box soi.
    • New white box contexts functionalContextImpl, logicalContextImpl (both optional), and productContextImpl, each specializing its black box context, with the systems functionalSystemImpl, logicalSystemImpl, and productSystemImpl (soiImpl).
    • productSystemImpl now satisfies the systemRequirementSpecification and is the subject of the verificationCases (productContextImpl.soiImpl).
    • logicalContextImpl and productContextImpl also specialize specificationContextImpl. functionalContextImpl does not, so the functional architecture, including its functional blocks, stays independent of the physical internal structure of the system. CreateFunctionalArchitecture therefore takes the black box specificationContext as input.
    • New allocations functionalImpl2logicalImpl and logicalImpl2productImpl between the white box contexts.
    • VerifyAndValidateRequirements takes productContextImpl as input.
    • Docs aligned in SYSMOD.sysml, the architecture and process prompts of SYSMOD4AI.sysml, the architecture view docs of SYSMODViews.sysml, and README.md.
  • Split the process step CreateSolutionArchitectures into one step per architecture kind:

    • CreateFunctionalArchitecture and CreateLogicalArchitecture (both optional) and CreateProductArchitecture, each outputting its black box and white box context; each refines the ISO 15288 System Architecture Definition process. The functional and logical steps also create the #refinement dependencies from their architecture elements to the system requirements.
    • The architecture allocations are created by the step of their target architecture: CreateLogicalArchitecture outputs functional2logical and functionalImpl2logicalImpl (new input functionalContext), and CreateProductArchitecture outputs logical2product and logicalImpl2productImpl (new input logicalContext); the allocations flow to the project. The allocation docs and the logical and product architecture prompts of SYSMOD4AI.sysml say so.
    • SYSMODDefaultProcess runs them in this order between defineSystemSpecification and verifyAndValidateRequirements. The logical step takes the white box functional context as input; the product step takes the white box functional and logical contexts.
    • The process input solutionArchitecture is replaced by functionalArchitecture, logicalArchitecture, and productArchitecture.
    • Updated the process prompts of SYSMOD4AI.sysml, the OnlyProcessStepElements constraint of SYSMODViews.sysml, and README.md.
  • Updated example model (architecture): the functional, logical, and product architectures of the Delivery Drone have a black box system (DeliveryDrone…System) and a white box system (DeliveryDrone…SystemImpl) with the building blocks, and white box contexts (DeliveryDrone…ContextImpl) that the project instantiates. MaxPayloadTest tests the DeliveryDroneProductSystemImpl. The example views of the architectures, the allocations, and V&V show the white box contexts.

  • Added verificationContext to SYSMOD::Project: it specializes productContextImpl, adds the test systems as actors (e.g., a test bench or a wind tunnel with constant wind speed), and owns the verificationCases, which moved from the project into the context.

    • VerifyAndValidateRequirements now outputs the verificationContext instead of the verificationCases, and it flows to the project.
    • Updated the process prompts of SYSMOD4AI.sysml, the viewpoint and view docs of SYSMODViews.sysml, and README.md.
  • Updated example model (verification): DD_VV::DeliveryDroneVerificationContext adds a windTunnel (#externalSystem with a constant windSpeed) to the white box product context. The project's deliveryDroneVerificationContext owns maxPayloadTest : MaxPayloadTest, the first verification case usage of the example. The example views verificationAndValidationView.svg and verificationMatrixView.svg show the usage.

  • MicroStory snippets verification, validation, and the-full-chain: the verification cases are owned by the project's verificationContext.

  • Added systemObjectives to SYSMOD::Project: the measurable goals of the system idea, an ExtendedConcern with the system idea (systemIdeaContext.soi) as subject and the projectOwner as stakeholder. It frames the stakeholderNeeds and is the basis for the system requirements and for validation.

    • PitchSystemIdea now also outputs the systemObjectives, which flow to the project; DefineSystemSpecification and its nested step elaborateSystemRequirements take them as input.
    • New AI metadata systemObjectivesAI (sysmod-system-objectives) in SYSMOD4AI.sysml. The project, process, and system requirements prompts include the system objectives.
    • The objectives direct the development. They are not framed by the system requirements and not satisfied by a system, because that would be too strong a link: an objective may not be met.
    • New view SystemObjectivesView (tree diagram of the systemObjectives with its nested objectives), satisfying ProblemSolutionViewpoint.
    • Updated the docs of ProjectViewpoint, ProblemSolutionViewpoint, and ValidationViewpoint in SYSMODViews.sysml, and README.md.
  • Updated example model (system objectives): DD_SYSTEMIDEA defines the measurable objectives FastRemoteDelivery (at most 50 % of the ground delivery time), LowCostPerDelivery (at most 70 % of the ground delivery cost), and OnTimeDelivery (at least 98 % on time). The Delivery Drone project redefines systemObjectives with these three objectives for the project owner John Finch and declares the view usage systemObjectivesView; the example view systemObjectivesView.svg shows it.

  • Spelling: "black box" and "white box" are now written as two words everywhere, also before a noun ("the black box context", "the white box view"). This replaces the hyphenated adjective form of 5.1.6 (#31) in the library, the AI prompts, the views, the examples, the example views, and README.md.

  • Updated example model (requirements traceability): elements of the functional and logical architectures refine the system requirements with #refinement dependencies.

    • Functional: batteryManagement and flightControl refine AirCharging; packageManagement refines MaxPayloadMass.
    • Logical: energyManagement, fleetCoordination, and flightControl refine AirCharging.
  • ArchitectureViewpoint: the constraint onlyArchitectureElements now also allows dependencies (SysML::Dependency), so an architecture view can show the #refinement traces to the system requirements without violating the viewpoint.

  • View dependencies: the views do not depend on each other, but the content they show does. SYSMODViews now makes this explicit as correspondences in the sense of ISO/IEC/IEEE 42010:

    • New metadata definition ViewedArtifact (#viewedArtifact) for dependencies from a view definition to the Project features it shows, e.g., #viewedArtifact dependency ProblemStatementView to Project::problemStatement;. All step-related view definitions declare them; specializations without own dependencies, e.g., ProjectAIView, inherit those of their general view.
    • SYSMODViews.md has the new chapter 6 "View Dependencies" with a Mermaid diagram and a table, and every view has a "Dependencies" block: the artifacts it shows, the SYSMOD step creating them, the views it builds on (inputs of the creating step or nested action), the information provided by a human or an AI assistant, the views it traces to (specialization of the system contexts, frame, satisfy, subject, allocate in Project), and the views it is input for.
    • The introduction of SYSMODViews.md separates the framework from the method: the framework defines what the views show and for whom; the SYSMOD process defines a default, optional, and iterative path through the steps that create the content, applied again to the subProjects.
    • scripts/generate_views_doc.py derives the dependencies from SYSMODViews.sysml and SYSMOD.sysml; nothing is maintained by hand.
  • Step status for the SYSMOD Map:

    • The Delivery Drone project redefines its defaultProcess and sets the @StepStatus of every step (all steps done, verifyAndValidateRequirements inProgress at 20 %, as verification has only started with MaxPayloadTest). It imports SYSMOD::SYSMODProcesses::* for StepStatus, StepStatusKind, and Percentage, and casts the percentage literals (1.0 as Percentage), because a real literal does not conform to Percentage.
    • New script scripts/generate_map_status.py (reuses the parser of generate_views_doc.py) reads the steps of SYSMODDefaultProcess, the StepStatusKind literals, and the StepStatus defaults from SYSMOD.sysml, and the step status of every #project in examples/. It writes the read-only examples/views/sysmodMapStatus.json and warns about unknown steps, unknown status literals, and percentages outside 0..1. Steps a project does not redefine keep the library defaults.
    • New workflow .github/workflows/map-status.yml regenerates the file on changes of the library, the examples, or the scripts.
  • New view SYSMODMapView (SYSMOD Map): the features of the exposed Project on one sheet with grid references, row A the concerns, row B the black box contexts, row C the white box contexts, and the columns 1 brownfield to 7 verification and validation. It specializes ProjectView (ProjectViewpoint, expose this, @ProjectMetadata) and replaces the tree diagram by the new rendering asSYSMODMap, whose doc lists the cells with their Project features and the steps that create them. The cell status is the @StepStatus of those steps.

    • Updated example model: the Delivery Drone project declares the view usage sysmodMapView; the example view sysmodMapView.svg shows it with the step status of sysmodMapStatus.json.

v5.1.6

  • Added examples/microstories/: the SysML v2 snippets of the SYSMOD MicroStories on the MBSE4U blog, one standalone file per story (e.g., the-project.sysml, problem-statement.sysml). Each file builds on the SYSMOD library and is the source of the snippet shown in its story; the website copies the files and checks them with the library. The files are examples and are not part of the published library package.
  • Fixed snippets that the OpenSysML checker rejected:
    • Requirements and verification usages that redefine systemRequirementSpecification or subset verificationCases now redefine the inherited subject together with the subject of their definition (subject :>> specificationSystem, deliveryDroneSystem;), so the usage has one subject, and the requirement definitions specialize ExtendedRequirement (system-requirements, requirements-traceability, the-full-chain, verification, validation).
    • logical-architecture: the nested allocations reference the named ends of functional2logical (allocate func ::> functional to logic ::> logical).
    • use-case-flows: the decision uses two guarded successions to local steps instead of else and feature chains as targets, which the checker does not parse yet.
  • Moved the view usages projectCoverView (ProjectView) and projectCoverAIView (ProjectAIView) from SYSMOD::Project to the example model (DeliveryDroneSystemProject.sysml), where they expose the Delivery Drone project.
  • StepStatus::percentage now defaults to 0.0 as Percentage (feature value with default =).
  • scripts/generate_views_doc.py now links the SYSMOD steps to the view usages of the #project occurrence definitions in examples/ as well as of SYSMOD::Project, since the library defines the views and the projects instantiate them.
  • Consistent spelling of black box and white box (#31): two words as a noun ("the system as a black box"), hyphenated as an adjective before a noun ("the black-box context", "the white-box view"). Fixed "blackbox context" and "whitebox context" in the doc comments of Project::brownfieldContext and Project::brownfieldContextImpl; all other occurrences already followed the rule.
  • Same rule for two further compounds: "elevator-pitch-style" before a noun in the problemStatementAI prompts (was "elevator-pitch style"), and "onboard" in the brownfield example (was "On-board", as everywhere else in the examples).
  • Updated example model (project): the Delivery Drone project now sets its purpose; the example views projectView.svg and projectAIView.svg show it.

v5.1.5

  • Added the SYSMODViews library package (file SYSMODViews.sysml), the SYSMOD architecture description framework according to ISO/IEC/IEEE 42010:
    • Stakeholders: 17 stakeholder roles derived from the ISO/IEC/IEEE 15288 life cycle processes, e.g., Acquirer, ProductManager, RequirementsEngineer, SystemArchitect, VerificationEngineer, and Maintainer. Each role specializes ExtendedStakeholder, so a project stakeholder can play a role by multiple typing, e.g., part johnFinch : ProductManager :>> projectOwner. The ProductManager doc states that the projectOwner typically plays this role.
    • Concerns: 17 concern definitions derived from the outcomes of the ISO/IEC/IEEE 15288 processes, e.g., ProblemSolutionPitch, MissionGoalsAndMeasures (mission, goals, objectives, and measures of success), StakeholderNeedsCoverage, ProblemSolutionIntegration, and VerificationCoverage. The Project is the entity of interest of all concerns, while the system of interest is reached through the system contexts of the Project.
    • Viewpoints: 16 viewpoint definitions that frame the concerns. Their required constraints restrict the elements a conforming view may expose to SYSMOD concepts, e.g., ExtendedConcern and SystemContext for the ProblemSolutionViewpoint, whose doc names its stakeholders (the ProductManager and the Acquirer).
    • View definitions per SYSMOD step that satisfy the viewpoints, from ProjectView (step 1) to VerificationAndValidationView and VerificationMatrixView (step 11), plus the base view SystemContextView and the abstract SolutionArchitectureView with its functional, logical, and product specializations.
    • AI renderings: the rendering definition AIRendering with a create_prompt, and the renderings asAIGenerated, as4Managers, asProjectFacts, and asMarkdown. The AI views ProjectAIView, ProblemStatementAIView, AIUseCaseView, and AIUseCase4ManagersView use them.
  • Added view usages to Project: projectCoverView and projectCoverAIView expose the project, and problemStatementView and problemStatementAIView expose the problemStatement.
  • Added the StepStatus metadata (status : StepStatusKind with open, inProgress, done, and skipped, and percentage : Percentage) to SYSMODProcesses. All steps of SYSMODDefaultProcess carry it.
  • Project::stakeholderNeeds is now typed by ExtendedConcern and Project::systemRequirementSpecification by ExtendedRequirement, so they conform to the element constraints of the requirements, verification, and agreement viewpoints.
  • IdentifyStakeholders now also refines the ISO/IEC/IEEE 15288 Business or Mission Analysis process (identification of the major stakeholders is one of its outcomes).
  • Fixed the create_questions lists in SYSMOD4AI: removed the trailing comma after the last question.
  • Added the generated, read-only documentation SYSMODViews.md, with the chapters ISO 15288 Processes, Stakeholders, Concerns, Viewpoints, and Views. It traces each view back to its SYSMOD step, viewpoints, concerns, stakeholders, and ISO/IEC/IEEE 15288 processes, and shows an example of each view. The script scripts/generate_views_doc.py generates it from the library, and the GitHub workflow views-doc.yml regenerates it whenever the library changes.
  • Updated example model: johnFinch plays the ProductManager role, logisticCompany the Acquirer role, DeliveryDroneSystemRequirements specializes ExtendedRequirement, ChargingPosition specializes Position, and the project has the views useCaseView (AIUseCaseView) and useCaseManagerView (AIUseCase4ManagersView).
  • Added example renderings of all views as SVG files to examples/views/, based on the Delivery Drone example model.
  • Removed the sysmod.org folder (the HTML documentation deck sysmodv5-reveal.html and its images) from the repository. The documentation is now maintained by the website mbse4u.com and is still available at https://sysmod.org. The README links to it.

v5.1.4

  • Added the SYSMOD use case specializations SecondaryUseCase, SystemProcess, and ContinuousUseCase (each specializing SystemUseCase, with secondaryUseCases, systemProcesses, and continuousUseCases usages) and the matching keywords #secondaryUseCase, #systemProcess, and #continuousUseCase.
  • Breaking: the actor-tagging metadata definitions are now lower camel case, so their keywords match the other SYSMOD keywords: System → system, User → user, ExternalSystem → externalSystem, EnvironmentalEffect → environmentalEffect. Replace #System, #User, #ExternalSystem, and #EnvironmentalEffect with the lower-case forms in existing models.
  • The #systemUseCase keyword (SystemUseCaseMetadata) now applies to use case definitions only, no longer to use case usages.
  • Updated example models to the new keywords. Domain library: item definitions sorted alphabetically and CustomerRequest added. Specification: added the DeliveryProcess system process, the BookDelivery use case, the MonitorDroneHealth continuous use case (with droneSTM state flying), and the createDeliveryOrder action; ChargeDrone is now a secondary use case, chargeInFlight is typed by ChargeDrone, and payloadMass is typed by ISQ::mass. Functional architecture: deliveryManagement performs createDeliveryOrder.
  • Synced the sysmod.org deck with the library and example models: new keyword spelling, the three new use case definitions and keywords in the "Full SYSMOD Library" appendix, and payloadMass :> ISQ::mass.
  • Project::subProjects is no longer a derived feature computed from all Project-typed suboccurrences. It is now a plain occurrence subProjects : Project [*], and a sub-project is added by explicitly subsetting it (occurrence myComponentProject : MyComponentProject :> subProjects). This makes membership in the sub-project list an explicit modeling decision and is consistent with the subProjectsAI prompts, which already required sub-projects to subset subProjects. Models that relied on the automatic derivation must add :> subProjects to their sub-project usages.
  • Updated example model: controlStationProject in DeliveryDroneSystemProject.sysml now explicitly subsets subProjects, and its doc comment and the README no longer describe the list as derived.
  • Updated the sysmod.org deck's "Full SYSMOD Library" appendix to show the non-derived subProjects feature.
  • Added an optional tolerance attribute (default 0.0) to the MaxValue, MinValue, RangeValue, MinAvailability, and MinReliability boilerplates in SYSMODRequirementsBoilerplates. It relaxes the bound(s) of the require constraint (currentValue <= maxValue + tolerance, currentValue >= minValue - tolerance, minValue - tolerance <= currentValue <= maxValue + tolerance, uptime / totalTime >= minAvailability - tolerance, meanTimeBetweenFailures >= minMTBF - tolerance), so specializations that do not set it get the unrelaxed bound(s). For MinReliability the tolerance is a duration (default 0.0 [SI::s]). Previously MaxValue declared a tolerance that its constraint ignored. ExactValue is unchanged; use ToleranceValue for a target value with a tolerance band.
  • Changed the MaxValue and MinValue boilerplates from strict to inclusive bounds (<= / >= instead of < / >), consistent with RangeValue, MinAvailability, and MinReliability and with the usual reading of "up to" / "at least" in requirement texts. A value exactly equal to the bound now satisfies the requirement.
  • Updated example model (specification): MaxPayloadMass now sets a tolerance of 0.1 kg on its 5 kg MaxValue limit.
  • Updated the sysmod.org deck (step 9 requirements library and model snippets and the "Full SYSMOD Library" appendix) to show the new tolerance attributes and constraints.
  • Use cases now perform the actions of their subject: each use case's subject droneSystem declares perform action uc<Name> ::> <name>; for every DeliveryDroneSystem action it orchestrates, and the successions, bindings, flows, and local flight legs reference these performed actions (droneSystem.ucPlanDelivery) instead of the system's actions directly. Updated the example model (specification) accordingly for BookDelivery, DeliverPackage, ChargeDrone, ReportFleetStatus, HandleEmergencyLanding, and MonitorDroneHealth; DeliverPackage now continues from ucPlanDelivery to the flyToPickup leg, and ChargeDrone no longer includes detectLowBattery.
  • Synced the sysmod.org deck (step 8 use cases) with the new perform action pattern in DeliverPackage.
  • Breaking: renamed the LevelKind literal medium to middle (value 0.5 unchanged). Replace LevelKind::medium with LevelKind::middle in existing models.
  • Updated example model (stakeholders): LevelKind::medium is now LevelKind::middle.
  • Updated the sysmod.org deck (step 4 stakeholder library and model snippets and the "Full SYSMOD Library" appendix) to the middle literal.
  • Added a name attribute (ScalarValues::String) to ExtendedStakeholder to hold the name of the stakeholder.
  • Updated example models (project and control station project): all stakeholders now set their name (johnFinch, tomSchilling, logisticCompany, droneOperator, recipient, regulator).
  • Updated example model (stakeholder needs): ReliableDelivery, SafeOperation, and LowDeliveryCost now declare the brownfield system as subject and their stakeholder (LogisticCompany or DroneOperator); the concern usages in the project bind them to the project's stakeholders.
  • Added the SYSMODProcesses package with SYSMODDefaultProcess, the default SYSMOD workflow, and one action definition per step: SetupProject, SpecifyBrownfieldSystem, SpecifyProblemStatement, IdentifyStakeholders, ElaborateStakeholderNeeds, PitchSystemIdea, DefineSystemSpecification (with the nested steps specifySpecificationArchitecture, identifyUseCases, and elaborateSystemRequirements), CreateSolutionArchitectures, and VerifyAndValidateRequirements. Successions define the default order (all steps after setupProject are optional), flows connect the step outputs to the project features, and bindings connect the step inputs to the project features created by earlier steps. The item definition ArchitectureDescription represents informal architecture descriptions given as input by a human or an AI assistant.
  • Added the ISO15288Processes package with an action definition and a doc comment for each of the 30 ISO/IEC/IEEE 15288 system life cycle processes (agreement, organizational project-enabling, technical management, and technical processes). #refinement dependencies in SYSMODProcesses map each SYSMOD step to the ISO 15288 process(es) it refines, e.g., DefineSystemSpecification refines SystemRequirementsDefinition.
  • Added the features defaultProcess (the SYSMODDefaultProcess performed by the project; redefine it with a specialization to tailor the process), purpose (a brief description of the project's purpose), and verificationCases (verification cases with the product system as subject) to Project.
  • Added defaultProcessAI (sysmod-default-process) to AIProject in SYSMOD4AI. It walks the user step by step through SYSMODDefaultProcess, delegates each step to the AI metadata of the artifacts it produces, and its validation prompt reports the status of every step and the next step to perform.
  • Updated the SYSMOD4AI prompts to model subjects, stakeholders, and actors as explicit, bound parameters:
    • stakeholderNeedsAI: each need definition declares the brownfield system as its first parameter (subject) and a typed stakeholder parameter per stakeholder; the need usages bind the subject to brownfieldContextImpl.soiImpl and the stakeholder parameters to the project's stakeholder part usages. The validation prompt checks the subject binding and that every need has a bound stakeholder parameter.
    • specificationContextAI: each use case definition declares the specification system as subject and a typed actor parameter per participating actor; the use case usages bind them to the context's soi and actor part usages. The validation prompt checks the actor parameter bindings.
    • systemRequirementSpecificationAI: each requirement declares the specification system as subject and a typed stakeholder parameter for the stakeholders of the framed need; the root requirement binds the subjects of its nested requirements. The validation prompt requires a frame relationship to a stakeholder need and at least one stakeholder parameter.
    • systemIdeaContextAI: removed the validation check for a satisfy relationship from the system idea to the problem statement.
  • The value attributes of the MaxValue, MinValue, RangeValue, ExactValue, and ToleranceValue boilerplates (currentValue, maxValue, minValue, targetValue, tolerance) are now untyped instead of ScalarValues::Real, so they accept plain numbers as well as quantity values with units. A specialization narrows all value attributes of a boilerplate to the same type, e.g., attribute :>> maxValue :> ISQ::mass = 5 [SI::kg];. MinAvailability keeps Real for its unitless ratio.
  • The tolerance attribute of all SYSMODRequirementsBoilerplates now has the multiplicity [0..1]. ToleranceValue::tolerance is therefore optional too and defaults to 0.0 like the others; MinReliability::tolerance (a duration) defaults to 0 [SI::s]. A specialization with units must set the tolerance with the same unit, since the default 0.0 is a plain number.
  • Updated example model (specification): MaxPayloadMass narrows currentValue, maxValue, and tolerance to ISQ::mass and sets maxValue = 5 [SI::kg] and tolerance = 0.1 [SI::kg] with units.
  • Updated example model (project): the specification context parts now redefine Project::specificationContext::soi and Project::specificationContextImpl::soiImpl instead of the system idea features.
  • Breaking: renamed the derived ExtendedStakeholder attribute priority (risk × effort) to attention. It measures how much attention a stakeholder needs and is no longer confused with the priority attribute of ExtendedConcern, which is unchanged. Replace references to a stakeholder's priority with attention in existing models.
  • Updated the sysmod.org deck (step 3 library text and snippet and the "Full SYSMOD Library" appendix) to the renamed attention attribute.
  • Updated the sysmod.org deck to the changes above: step 4 model snippet (subjects and stakeholders of the stakeholder needs), step 7 specification context snippet, step 9 MaxValue library snippet and MaxPayloadMass model snippet, the AI layers of steps 4 and 6–9, and the "Full SYSMOD Library" appendix (boilerplates and AI prompts).
  • Updated the sysmod.org deck (step 1 and step 3 library and model snippets and the "Full SYSMOD Library" appendix) to show the new name attribute of ExtendedStakeholder and the stakeholder names of the example model.

v5.1.3

  • Split the AI metadata definition and AIProject out of SYSMOD.sysml into a new top-level package, SYSMOD4AI (file SYSMOD4AI.sysml), which privately imports SYSMOD. Import it in addition to SYSMOD only where AI-assisted workflows are wanted — the core methodology library no longer carries any AI-specific content.
  • Moved and renamed the boilerplate requirements package to SYSMODRequirementsBoilerplates (file SYSMODRequirementsBoilerPlates.sysml): it is now a top-level library package alongside SYSMOD and SYSMOD4AI (previously nested inside SYSMOD), and the name's spelling is corrected. Update any qualified references from SYSMOD::RequirementBoilderplates to SYSMODRequirementsBoilerplates.
  • Updated the sysmod.org documentation deck's "Full SYSMOD Library" appendix to show SYSMOD, SYSMOD4AI, and SYSMODRequirementsBoilerplates as the three separate packages they now are, instead of one monolithic package.
  • Updated the deck's AI metadata definition and per-step AI prompts to match the library: all seven AI attributes are now shown (including perform_prompt, story_prompt, slide_prompt), the sysmod-stakeholder-priority-map skill is now documented, and the deck's own copies of the v5.1.2 MinValue/MinAvailability fixes and the boilerplates renaming — which had not been carried over from the library into the documentation — are now consistent with it.
  • Renamed the deck's "Solution System Architectures" step to "Functional, Logical, Product Architecture" and removed the last sysmod-solution-context / "solution architecture" leftovers from its text, matching the library's actual functional/logical/product structure.
  • Added a doc comment with explicit "When to use" / "When not to use" sections to all 14 AI metadata usages in SYSMOD4AI.sysml (projectAI, projectOwnerAI, brownfieldContextAI, problemStatementAI, projectStakeholdersAI, stakeholderPriorityMapAI, stakeholderNeedsAI, systemIdeaContextAI, specificationContextAI, systemRequirementSpecificationAI, functionalContextAI, logicalContextAI, productContextAI, subProjectsAI), written in the style of an AI-assistant skill's trigger/skip conditions and cross-referencing the adjacent skill to use instead where scopes could overlap. This paves the way for generating Claude Skills (or equivalent skill definitions for other LLM platforms) directly from these elements.
  • Synced the sysmod.org deck's "Full SYSMOD Library" appendix with the new "When to use" / "When not to use" doc comments on all 14 AI metadata usages, and noted the convention in the AI metadata definition's own doc and in the "About the AI Skill Layer" intro slide.
  • Fixed the "speccification" typo in the functionalContextAI validation prompt in SYSMOD4AI.sysml.
  • Updated example model (brownfield architecture): replaced packagePort (one inout parcel item) with payloadPort carrying separate pkgIn/pkgOut items, added a customer actor with a customerInterface to payloadPort, added an energyPort for the electrical energy supply, and documented all ports of DeliveryDroneSystem.
  • Updated example model (domain library): added the Energy item definition.
  • Updated example model (specification): all use case actions are now owned once by DeliveryDroneSystem and documented, including their items; use cases reference them via droneSystem.<action> instead of defining local copies. Renamed batteryLow to acceptBatteryLow (with an explicit accepted lowBattSignal), replaced flyToHomeStation by a flyToHome leg of flyToPosition targeting the new homePosition item, let detectLowBattery send its signal via a port, and added an energy input to DeliverPackage and chargeInFlight.
  • Updated example model (functional architecture): replaced the empty placeholder parts with the FAS functional blocks deliveryManagement, flightControl, packageManagement, batteryManagement, droneManagement, and fleetManagement, which perform the specification actions, are bound to the inherited system ports, and are connected via typed ports from a new Interfaces package (PositionInterface, PositionPort, EnergyPort, DeliveryPort, PayloadPort, ...). Corrected the remaining "solution" wording in its doc comments to "specification".
  • Updated the Cameo Systems Modeler file of the example model.
  • Synced the sysmod.org deck with the example model and library: Brownfield (step 5: payloadPort, energyPort, customer, port docs), Specification (step 7), Use Cases (step 8: current SystemUseCase :> ConstrainedOccurrence library snippet with startShot/endShot, and the reworked DeliverPackage), Functional Architecture (step 10), the maxPayloadMass name in steps 9 and 11, the remaining "solution" wording in the appendix's functional/logical/product context docs, and an invalid trailing comma in the appendix's projectAI create_questions.
  • Added SYSMOD4AI and SYSMODRequirementsBoilerplates to the Sysand package index (.meta.json), so both new library files are included in the published package, and added the version line to the SYSMOD4AI header.
  • Fixed the sysmod.org deck's links to the example model folder and to the SYSMOD Sysand project page.
  • The sysmod.org deck now always shows SysML v2 textual notation in full: removed all height limits and inner scroll boxes from code blocks, and the library, model, and AI slides grow with their content and scroll as a whole, so no slide is cut off.

v5.1.2

  • Fixed inconsistent "solution" terminology in SYSMOD.sysml doc comments and AI metadata prompts, correcting references to match the actual specificationContext/specificationContextImpl concepts.
  • Removed references to the non-existent solutionContext/solutionContextImpl concepts from the project AI metadata's structure and validation checks; productContext now specializes specificationContextImpl directly.
  • Fixed the RequirementBoilderplates MinValue constraint, which had its comparison operands reversed (minValue > currentValue) so it required the opposite of a lower bound; it now correctly requires currentValue > minValue.
  • Fixed the RequirementBoilderplates MinAvailability requirement's minAvailability attribute, which was typed as ISQ::duration; it is now a dimensionless ScalarValues::Real ratio, consistent with the uptime/totalTime constraint.

v5.1.1

  • Added web page https://sysmod.org to the SYSMOD repository
  • Updated example model: PRJ::stakeholderNeeds::problemStatement redefines the inherited problemStatement and subsets PRJ::problemStatement.
  • Updated example model: PRJ::deliveryDroneSystemIdeaContextImpl satisfies PRJ::problemStatement.
  • Added Cameo Systems Modeler file for the example model.
  • Added preconditions and postconditions to the SYSMOD UseCase concept.
  • Added library with RequirementBoilerplates
  • Updated example model: DeliveryDroneSystemRequirements now declares its own subject and stakeholder (projectOwner); DeliveryDroneSystemProject redefines both accordingly.
  • Updated example model: added Recipient and Regulator stakeholders to DeliveryDroneSystemStakeholders and DeliveryDroneSystemProject, so the four stakeholders match the sysmod.org story.
  • Added a "SYSMOD Steps" navigation menu to sysmod.org's header, for jumping directly to any step.
  • Added the SYSMOD products overview image to the "About SYSMOD" page on sysmod.org, with clickable step cards that jump directly to the corresponding SYSMOD step.
  • Added two validation checks to the SYSMOD library's productContextAI metadata (SYSMOD.sysml), covering MOSA-conformant port/interface-only dependencies between product components and complete interface specification.
  • Added a link to the SYSMOD Sysand project to README.md.
  • Extracted the SYSMOD UseCase's precondition/postcondition mechanism into a new, reusable ConstrainedOccurrence library concept, which SystemUseCase now specializes.