Content deleted Content added
m External links - remove link to common model library that no longer resolves |
m Note that ref 4 link no longer resolves |
||
Line 14:
==SML-Based Models==
One anticipated use for SML is to define a consistent way to express how computer networks, applications, servers and other IT resources are described or modeled so businesses can more easily manage the services that are built on these resources <ref>[http://www.cml-project.org/2.html Common Model Library - link no longer resolves]</ref>. This enables a hierarchy of IT resource models to be created from reusable building blocks rather than requiring custom descriptions of every service, thus reducing costs and system complexity for customers.
Models provide value in several important ways:
Line 22:
# Models drive [[modularity]], [[Re-use]], and [[standardization]]. Most real-world complex services and systems are composed of sufficiently complex parts. [[Re-use]] and [[standardization]] of services/systems and their parts is a key factor in reducing overall production and operation cost and in increasing reliability.
# Models represent a powerful mechanism for validating changes before applying the changes to a service/system. Also, when changes happen in a running service/system, they can be validated against the intended state described in the model. The actual service/system and its model together enable a self-healing service/system – the ultimate objective. Models of a service/system must necessarily stay decoupled from the live service/system to create the control loop.
# Models enable increased automation of management tasks. Automation facilities exposed by the majority of IT services/systems today could be driven by software – not people – for reliable initial realization of a service/system as well as for ongoing lifecycle management.
==References==
|