 white papers are required from a business analyst is in fraud management space. The NGN is an IP-based network and the chances of security breach and fraud that existed in the IP world is valid in the case of NGN. Fraud management is a key area of focus for NGNM and the business analyst can contribute with white papers in this space. OSS development needs input from the business analyst and SO regula- tory guidelines are required for telecom space. The changes in regulations have an impact on the business guidelines on the company and the reg- ulatory implications in an NGN environment can be identified by the business analyst. 2. System analyst/solution architect dealing with system/architecture block in System analyst/architect can look into technical marketing that involves promoting NGOSS components including eTOM, SID, TAM, and TNA as the enabler for managing heterogeneous networks with common models. Various NMS solutions are coming up in the market that have capabilities to better manage NGN and are built using NGOSS models. Legacy solution needs are best aligned with NGOSS to integrate these applications. Adoption of eTOM as a standard by ITU-T shows the wide spread use of NGOSS concepts. Legacy System owners can start by pre- paring a business map, information map, application map, and architec- ture map of their telecom system. The next step involves use of NGOSS methodology of SANRR (scope-analyze-normalize-rationalize-rectify). The end result of multiple iterations with SANRR is a set of level 4 eTOM business models, well-defined interfaces, and contracts with SID busi- nesses and system models, technology neutral architecture wherever pos- sible in implementation, and a detailed application map. Architecting based on SOA (service-oriented architecture) is another area of focus for architects. Benefits of using SOA in NMS, have driven NMS developers to come up with new SOA-based NMS suites. NGOSS does provide guidelines for developing SOA, but what is required is an archi- tecture that can convert th