ends 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 (OSS/J) initiative defines a technology specific set of API specifications. In addition to API specifi- cations, OSS/J also includes reference implementations, technology compatibility kits, and multitechnology profiles for OSS integration and deployment. The core business entities (CBE) model of shared information/data (SID) model that helps to provide a technology neutral implementations view of the NGOSS architecture is used by the OSS/J API specifications. The Java 2 Platform Enterprise Edition and EJB-based Application Architecture are the enabling technologies in OSS/J, used as tools for developers to easily develop applications. The J2EE plat- form offers faster solution delivery