OS to the dis- covery OS. 5. The network entity is actually installed later. 6. The discovery os detects the installed entity and issues an "Attribute Value Change" notification on the resource state of the network entity. 7. This results in change from planning to installing. In the second method the new network entity is first announced on the CCV by the discovery os before it is given a unique name. Here we will deal with object discovery notification (ODscN) and object creation notification (OCN). The steps in the second method are: 1. A network entity that has not been announced by the inventory OS at the interface is directly detected by the discovery OS. 2. The discovery OS then sends an object discovery notification to the notifica- tion service. Fundamentals of EMS, NMS and OSS/BSS 3. The notification is received by the inventory OS. 4. The new object is given a name by the inventory OS. 5. Inventory os issues an object creation notification. 6. Other modules like discovery and activation OSs receives and processes the OCN. Service interfaces and data entities define interface implementation. The service interfaces consist of operations and notifications that have parameters. Attributes make up data entities. Additional service interfaces like operations and notifica- tions are needed as the interface is extended. Interface elements like operations will not be deleted when passing from one version to the next unless an error with an existing element is identified. Instead of "delete" term, "Deprecate" is used with respect to parameters for operations and notifications, since it may be easier to leave the operation/notification signature alone and just deprecate usage of a particular parameter. 25.4 OSS/J Overview While the NGOSS program of TMForum focuses on the business and systems aspects, essentially the problem and solution statement of OSS-solution delivery, the OSS/J program focuses on the implementation, solution realization, and deploy- ment aspects using Java technology. The OSS through the Java