|
|
|
DMTF Tutorial
> Management Profiles
> Template
 |
Management Profile Template
|
 |
The (DSP1000) DMTF Management Profile Template is located on the DMTF website. The template sections and their intended usage and content are explained in detail in the Management Profile Specification Usage Guide (DSP1001).
The Management Profile Template captures a Profile definition in the following format:
1. Synopsis
Profile name: The name of the Profile
Version: The version number of the Profile using the formant "M.N.U" (for example, "1.0.0")
Organization: The organization publishing the Profile. (for example, "DMTF")
CIM schema version: The earliest version of the CIM Schema upon which an implementation of the Profile must be based. (for example, "2.10.0")
Central Class: The central class/focal point of the Profile. This defines the expect client entry point for discovering management information for a device that supports the Profile. (for example, CIM_ComputerSystem is the entry point for discovering management information about a Server)
Scoping Class: The scoping class for this Profile
Short Description
Table of related Profiles
NOTE: The Profile name, version and organization uniquely identify a Profile specification.
2. Description
The Description section describes the management domain implemented by a Profile and provides an overview of the model. The Description does not include any specification requirements, but rather describes how the classes of the Profile relate to the management domain. This section will typically contain class diagrams that depict the model.
3. Implementation
The Implementation section contains requirements of the model that are not covered by other sections and guidelines related to implementation. This section might include requirements that are referenced from other sections, and describe the relationship between the model and underlying instrumentation.
4. Methods
The Methods section provides a list of the Extrinsic Methods of the class in the Profile that are supported by this Profile. Profile usage of both Extrinsic Methods and Generic Operations (for example, intrinsic methods) are included, but the specification formats are different.
5. Use Cases
The Use Cases section specifies use cases that demonstrate interesting behaviors or tasks that the Profile supports.
The purpose of a use case is to illustrate the steps required to accomplish some goal and the effects on the model of accomplishing that goal. A use case defines the interaction of a client and a WBEM Server in the execution of steps that are required to realize the functionality described in the Profile. Use cases typically represent a complete task from the perspective of a client, which might involve multiple CIM operations or methods. A Profile specification can document one or more use cases, each of which has different starting conditions and ending conditions. The purpose of the use case is to illustrate the steps required to accomplish some goal and the effects on the model in the course of accomplishing that goal.
6. CIM Elements
The CIM Elements section contains the following items:
- An overview subclause that consists of a table that lists the Profile's classes, indications, and queries.
- A subclause for each class that includes a short description of the class and a table that includes the Profile's use of properties and methods.
The table (and a subclause) include all of the classes and associations that are defined in the Profile.
This section can include constraints on properties, such that a property must contain a specific value or a specific format for a value, or that a value may change based on the condition of something else.
|
|
