ication of functionality. Flexibility The hard coding and All service components dependencies make the have a published application perform only a interface and is flexible to specific functionality and does use in multiple scenarios. not allow flexibility in using parts of the application. (Continued) Fundamentals of EMS, NMS and OSS/BSS (Continued) Attribute Legacy NMS NGNM Solution Scalability There is a separate NMS Simple customizations solution for each type of can make the solution network. work for a variety of networks. Reusability Very little reuse possible. Functionalities can be reused with minimal or no changes. Integrity Integration with a new Integration is easy with functionality requires service components in considerable rework SOA framework. Testability Addition of a new functionality Use of service will require retesting of all the components brings down modules again due to testing effort and cost interdependencies. considerably. 34.8 Conclusion It is not cost effective for NMS developers to continue using their legacy solutions and sooner or later adoption of NGNM is inevitable. The major challenge is to adopt NGNM in a manner that best addresses the business needs of the company. This report tries to come up with an NGNM framework that can be considered the best one that can be formulated from existing technology standards in the domain. The adoption methods specified in the report need to be evaluated by different compa- nies and each one should come up with the best strategy that satisfies the company goals. Suggested future work includes white papers that discuss detailed case studies on issues identified in the NGNM frame and its adoption in different companies and how these issues can be avoided. It should be understood that any development on an NGNM solution should ensure that existing scalable architecture is maintained and no new hard codings and dependencies between modules are introduced. Supporting Publications 1. Transformation of Legacy Network Management System to Service Ori