Service Usage Model Classification Scheme
The e-Framework uses several classification categories to tag Service Usage Models (SUMs) for cataloguing and discovery purposes. These classifiers will be used for all SUMs published by the e-Framework; however, submitters and other communities may add their own additional classifiers.
Complete and accurate classification of the SUMs will enable all parties to obtain a sense of a SUM’s characteristics and status, thereby helping them to assess the uniqueness of the SUM as well as its potential for application by other organizations or in other scenarios.
Major groups of classifiers
The classification scheme for SUMs includes several Status Classifiers as well as Technical Classifiers. Within each of these major groups, some classifiers are required while others are optional but highly desirable. Click on the links to view the permitted choices you can select for required status classifiers, optional status classifiers, and optional technical classifiers.
Status classifiers
These classifiers describe a SUM’s general status and state of the component.
Required Status Classifiers:
- SUM Type – The kinds of domains in which SUM is used.
- Domain - Focus, or area, of activity in which the SUM is principally used within an IT system. Areas of activity are generalised from the context of higher education.
- Maturity - The measure of maturity of the SUM.
- Purpose – The purpose of documenting this SUM and describing its intent and use by the submitter or the e-Framework.
- XOR – whether the SUM defined exclusively in terms of Service Genres or Service Expressions.
Optional Status Classifiers:
- Development status - Status of the development of the SUM.
- Deployment scale - The level of deployment or use within the community.
Technical classifiers
These classifiers denote the technical and behavioural characteristics of the SUM. Technical classifiers are primarily applicable to Service Expressions.
Required Technical Classifiers:
Optional Technical Classifiers:
- State behaviour - How a service implementation invocation is related to any other service implementation invocation.
- Transactional behaviour – How a service implementation processes data as transactions.
- Batch behaviour - The type of processing of data or document sets by the service implementation.
- Time-constraint behaviour - How the service implementation deals with time constraints.
- Service End point – A description of the role of the SUM's data/resource processing relationship with other technical components.
- Authentication or authorization dependency - A description of how the service implementation incorporates internal authentication or authorization controls.
- Protocol binding – The type of communications protocol binding for service implementation.
Permitted choices for SUM classifier values
The e-Framework has specified a vocabulary from which you can choose the values to assign to each of the classifiers. Simply check the box next to the chosen word or phrase in the template document when you are preparing your Service Usage Model (SUM) description for submission to the e-Framework.
For most classifiers, only one choice can be selected. For some classifiers, selecting multiple values is allowed; these classifiers will be listed as the plural form (with an 's') in the template used to submit a Service Usage Model.
Click on the classifier links above to review the definitions of the available choices. Providing a value or values for each required classifier and for as many optional classifiers as you can will benefit the entire community. (Required classifiers are in BOLD type in the templates.)
Note: The e-Framework Editorial Team will assign the appropriate Status and Confidence level, and reserves the right to modify other classifier values prior to publication to ensure consistency across all components.
Last updated 14 October 2008