...
Description | A concise description of the purpose of the Capability covering the mandatory scope. |
Outcomes | The Outcomes section describes the main users of the Capability and the outcomes they want to achieve from using a Solution that meets the Capability based on the mandatory scope. |
Epics and Acceptance Criteria | Epics are individual high level business requirements and describe features relevant to the Capabilities they belong to. All Epics together define the full scope of a Capability. The Acceptance Criteria associated with an Epic define the minimum expected functions a Supplier’s Solution must deliver and are test scenarios that will be used during Capability Assessment stage of Onboarding to establish whether a Supplier’s Solution meets the Epic or not. In order to pass any Epic, all associated Acceptance Criteria for that Epic must pass the assessment. Epics are classified as either Must or May Epics and all Epics will be assessed during the Capability Assessment stage of Onboarding. It is recommended that Suppliers consider all Epics as part of User Research to understand what the Minimal Viable Product (MVP) is for their users. MustMUST EpicsMust Epics are mandatory and used to confirm during Capability Assessment stage of Onboarding that a Solution delivers the minimum required for a Capability. A Supplier Solution needs to meet all Must Epics in order to Pass Capability Assessment for a Capability. May EpicsThese Epics are not mandatory, however it is recommended a Supplier considers all MAY Epics. Which MAY Epics a Supplier chooses to implement should be determined by their User Research. All May Epics and Acceptance Criteria will be evaluated during the Capability Assessment Stage of On-boarding. Any May Epics that are assessed as met will be available to buyers to support them when comparing Solutions on the Buying Catalogue.MUST Epics describe the minimum functionality required to deliver a Capability. Solutions MUST be successfully evaluated against each Epic and Acceptance Criteria via Capability Assessment in order to be associated with this Capability MAY EpicsMAY Epics describe additional functionality associated with the Capability. Suppliers should consider all MAY Epics as part of their User Research. Suppliers can choose to map their Solutions to these Epics and they will be evaluated via Capability Assessment. Framework Authorities or purchasing organisations may require these Epics as product qualification or requirements criteria |
Additional Implementation Details | Additional Implementation Details are mandatory details related to a specific Epic and could be assessed during the Assurance stage of Onboarding. These details can include references to other Standards and Suppliers will need to complete any separate assurance activities related to those Standards. |
Supporting Information | This information may be useful to Suppliers when implementing the related Epic, but is not mandatory and is for guidance only. |
Overarching Standards | Overarching Standards apply to all Suppliers irrespective of the Capabilities their Solutions support. Suppliers will be assured against Overarching Standards during the Standards Assessment stage of Onboarding. |
Interoperability Standard | This Standard provides a single place for Suppliers to find out which interfaces they need to implement and to access the required documentation. It also contains overarching requirements that apply to all interfaces in the scope of the Interoperability Standard which are offered by a Solution. |
Roadmap | The Roadmap section summarises future changes and opportunities for Suppliers in relation to the Capability or Standard. These are linked to the individual Roadmap pages which provide further information on the Roadmap item. |
...