Requirements-Data Types

V3 Data Types: Methodology Requirements

Preliminary Requirements

Requirement	Must be able to define Data Types for all RIM Attributes
Rationale	As presented here, the requirement for data types is secondary to the use of the RIM to solve other requirements, though it is likely that any other approach to solving the requirements that the RIM fulfills would lead to the creation of data types.
Methodology	Existence of data types; controls the scope of the data types

Requirement	Must provide consistent design approach for all data types with clear semantic definitions
Rationale	Previous experience, involving mixing and matching data types and definition approaches, has lead to much confusion and overhead when using them in standards development or implementatation.
Methodology	Develop common architecture, strictly controled definition templates, formal definition language

Requirement	Definitions must be technology neutral
Rationale	The development and maintenance of the data types (along with the RIM) is expected to be on a slower cycle than the definition of technologies such as XML and UML, and we need to able deliver standards based on future technologies in a more timely fashion
Methodology	Split between Abstract Data types - no technology dependence in the definitions, and the implementations, which are technology specific (and optimised)

Requirement	Must be possible to implement the data types using common implementation technologies at this time.
Rationale	People do actually have to use them.
Methodology	Provision of XML and UML implementation specifications

These preliminary requirements suggests a number of semantic requirements for the datatypes themselves, but this document focuses on the definitional mechanisms rather than the semantic ones, the requirements for the solution that defines the data types.