Service Modeling Language: Difference between revisions

Revision as of 21:14, 2 August 2006

Revision as of 21:15, 2 August 2006

Line 17:

'''2.''' Models are units of communication and collaboration between designers, implementers, operators, and users; and can easily be shared, tracked, and revision controlled. This is important because complex services are often built and maintained by a variety of people playing different roles.

'''3.''' Models drive [[modularity]], re[[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.

'''4.''' 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.