Complete reference for all NexoGraph metamodel entity types and their fields.
NexoGraph defines ten entity types. Most entities belong to exactly one root collection. Need is shared by the STAKEHOLDER_NEEDS and USER_NEEDS roots and uses a required type discriminator to identify the workspace context.
A BusinessCase is the top-level container for capturing the strategic justification of a project. It holds an ordered sequence of BusinessCaseCell nodes.
A BusinessCaseCell is a single notebook-style markdown cell inside a Business Case. Cells are ordered and can contain rich text, diagrams, or supporting data.
A Package groups related items inside package-backed roots such as stakeholder needs, stakeholder requirements, user needs, user stories, and system capabilities. It acts as a namespace that helps organise large sets of related items within a project.
A Stakeholder represents an individual or group with an interest in the system. Stakeholders are linked to stakeholder-scoped Need entities via reference relations.
A Need expresses a capability, outcome, or constraint required from the system. Needs are grouped in packages under either the stakeholder-needs workspace or the user-needs workspace. The required type property distinguishes stakeholder needs from user needs:
STAKEHOLDER - a need owned or expressed by a stakeholder and stored under STAKEHOLDER_NEEDS
USER - a need owned or expressed by a user persona and stored under USER_NEEDS
A User (also called a user persona) represents a class of end-users who interact with the system. Users are linked to user-scoped Need and UserStory entities via reference relations to build a full traceability chain.
A UserStory is an agile-style description of a feature from the perspective of a user persona. Stories are traced back to user-scoped needs and users to provide full coverage reporting.
A CustomerFeature captures customer-visible product value before it is allocated to system capabilities. Customer features are grouped in packages under CUSTOMER_FEATURES and can be traced to enabling system capabilities with the ENABLED_BY relation.
A SystemCapability captures what the system must be capable of doing in an operational scenario. Capabilities are grouped in packages under SYSTEM_CAPABILITIES and can be traced from stakeholder-scoped or user-scoped needs with the INFORMS relation.
The generated statement uses the structured capability fields:
Capability: <ability>The system shall be capable of <action> for <beneficiary> in <operationalScenario> using/with <inputsDependencies> to achieve <outcomeEffect>, with <performanceQualityLevels>, subject to <constraints>.
statementOverride replaces the generated statement for display, search, and summary text when it is set.
