rocess models. Together SID and eTOM helps to ensure process to information alignment. The modeling language, UML is used for creating models in SID. The view of a business or system is created using UML class models and sequence diagrams in SID. Common definitions for terms like resource, product, customer and ser- vice, and their relationships are provided by SID. This results in a common lan- guage for information modeling with service developers, service providers, and integrators. SID is used as a reference model for data design in telecom solution development. Information Models The SID is composed of five building blocks: 1. Business entity: An item of business that follows a well-defined life cycle is represented as a business entity. It can be tangible things like a supplier, active things like inventory order, or conceptual things like customer account. 2. Aggregate business entity: A well-defined set of information and operations that helps to characterize a set of business entities is referred to as an aggregate business entity or ABE. 3. Attribute: This is a set of characteristics describing a business entity. Business entities can have relationships with other business entities and exhibit a set of characteristics. 4. Relationship: An association of business interests between two business enti- ties is called a relationship. It should be noted that a business entity can estab- lish an association with itself. 5. Domain: These are a collection of ABEs associated with a specific management area that are derived from analysis of process and information frameworks. It can be seen that domains making up the SID framework are consistent with eTOM level 0 concepts. The SID framework comprises of business entities and their attributes represented using UML models with process mapping to eTOM. The SID specifications are grouped into domains, each of which has a set of SID business entities and attri- butes collected in aggregate business entities that can be directly used for data design by the service devel