ervices Interface Figure 44. Example of a Next-Generation Component-Based OSS Framework The Ultimate Guide to Building and Delivering OSS/BSS STANDARDS AND TRENDS 4.1 The Standards: TeleManagment Forum - NGOSS Framework The TeleManagement Forum is an international consortium of communication service providers and their suppliers whose mission is to establish operational guidance and define a systems framework for automation of business processes in a cost-effective manner. The TMF effort on next-generation OSS is called NGOSS (New Generation Operations Systems and Software). As part of this effort, TMF is developing a business case, requirements and architecture for NGOSS. The aim of the NGOSS effort is to provide the architectural framework, analytical foundation and process methodologies needed for developing, deploying and modifying OSS components. The NGOSS effort leverages previous TMF initiatives, primarily the Telecom Operations Map (TOM) that provides a high-level overview of Telecommunications OSS business processes. In concept, the NGOSS architecture is separated into a Technology Neutral Architectural Framework and a Technology Specific Architectural Framework. This separation insulates the core architectural framework from technology dependencies. The technology-neutral framework will determine how component interfaces are defined and how shared service will be used. This technology neutral framework will have to be mapped to specific technologies prior to implementation. Each technology, such as CORBA, Java and EJB, will define an execution environment in order for OSS software developers to build components guaranteed to work in any implementation of the framework. NGOSS is also defining use of technologies such as SOAP, XML and JINI for implementation of the framework. 4.2 The Web Services Revolution There are multiple definitions of Web Services. The Stencil Group defines Web services as: Loosely coupled, reusable software components that semantically encapsulate discrete functionality and are dis