teractions. The various tasks are modeled as interactions in which contracts are used to specify the behavior for how the information is exchanged between collaborating entities. The System View: In the system view, the eTOM and TNA are used to focus on the concerns of system namely managed objects, behavior and computational interactions in a technology neutral manner. The Implementation View: This view focuses on how to build hardware, software and firmware to implement the system being designed. The contracts will contain the implementation artifacts, such as code, technology specific interface definitions or APIs. The Development View: It is concerned with operating and actively monitoring the system to ensure that the observed behavior is followed through and if not then adjustments are made according to policy based management mechanisms. The deployment contracts contain statistical performance data, mechanisms for monitoring the performance, costs, and SO on. The NGOSS lifecycle and methodology approach provide traceability, from business needs to deployment options of the solution. The detailed view of the NGOSS lifecycle is shown in Figure 8.23 that shows business goals are turned into system contracts, from systems designs into implementation processes and finally into an operational (deployment) form. Core Networks and Operations Support Systems NGOSS Lifecycle Stages Business System Tailored Business Business Processes Scope, Goals, System Company Design & Mission Processes Standards Tailored & Procs. Bus, Policies Tailored System Definition System Contracts Business Process Definition Contracts Tailored Knowledge Base Process Business View Policy Model Info Model Info Model Corporate NGOSS Knowledge shared Knowledge Contract Process Impls. Instances Run-Time Implementation Process Process Processes Instances Development Environment Implementation Contract Policy Specs Environment Instances Policy Data Model Instances Deployment 4 Implementation TeleManagement FORUM TM Figure 8.23 Detailed view of NGO