e based on loosely coupled, service discovery architecture. COTS-based implemen- tation also leads to reuse when the product is developed for integration with a wide variety of components. The main intent of splitting to components is to achieve better management at the component level and at the same time having the entire system controlled by managing specific components, thus reducing the complexity. 5. Other requirements associated with NGNM: Compliance to standards is a key requirement for NGNM. This includes standards given by telecom and enterprise standardizing organizations, compliance specified by regu- latory bodies and legal obligations. Regulatory requirements include emer- gency services and legal obligations can include security features like lawful interception. With multiple NGNM requirements from different standardizing bodies, ser- vice providers and developers have difficulty in determining what standards to use. So liaison of standardizing bodies to do collaborative work and combining standards and refining them to suit business needs is also being looked into as an outcome of NGNM initiatives. 17.3 TR133 TeleManagement Forum (TMF) has published a member evaluation version of NGNM strategies (TR133), which suggests a lifecycle approach to give holistic view to NGNM. The lifecycle model has four blocks (see Figure 17.1) that correspond to intersection of stake holder and technology parts. Stake holder part has the service provider and service developer space. Technology part has the technology neutral and technology specific space. The four blocks are: Business: This block is the intersection of technology neutral space and ser- vice provider space. The service provider defines requirements in a technology agnostic manner, which is the business block. System/architecture: This block is the intersection of technology neutral space and service developer space. Based on the requirements defined in a business Next Generation Network Management (NGNM) Business TR133 Deployment System/ architecture 