Policies-Characteristics-Principles-Requirements
- Klaus Vilstrup
This sections captures the Policies, Characteristics, Principles and Requrements for the Discovery part of the Peppol eDelivery Architecture.
The initial ambition is scope of relevance to a logical centralized SML vs. federated SML. The definition of a federated SML is inherent defined in the Policies.
Peppol Policies - strategic Peppol business goals that frames and are relevant to the Architecture.
Architecture relevant Policies
Architecture Characteristics - high level characteristics for the architecture. These are non-functional requirements that are often non-measureable e.g. Architecture Characteristic “Scalable”.
Architecture Principles - Guardrails that are guiding the Architeture design towards the Architecture Characteristics e.g. the Architecture principle “Scale out, not Up” supports the Architecture Characteristic “Scalable”.
Architecture Requirements - Functional requirements and Non-functional requirements that are measurable e.g. Functional Requirement “For a C4 it must be possible to change C3 because…….” or Non-Functional Requirements (measureable) like SLAs.