 block where the technology neutral design is defined. All the activities of the service developer for system design including preparation of artifacts to start work on the imple- mentation happens in the system block. The overlap of service developer with the physical view happens in the implementation block where the technology specific implementation occurs. All the activities of the service developer for implementing NGOSS Service providers view Service developers view Logical view Business System (Technology neutral) Knowledge Physical view Deployment Implementation (Technology specific) Figure 21.2 NGOSS lifecycle. the solution as per the definitions in system design happen in the implementation block. The overlap of service provider with the physical view happens in the deploy- ment or run time block where the technology specific deployment is performed. This block is expected to capture all the activities of the service provider for deploy- ing the solution as per the definitions in business, system, and implementation block. Though the model appears to be hierarchical in passing through the stages of defining, designing, implementing, and deploying one after the other, it is possible to move into any one of the intermediate stages and then work on the other stages. This means that there is traceability between blocks and at any stage a telecom player can start aligning with NGOSS. The overlap of views then creates four quad- rants each corresponding to a block in the telecom life cycle (see Figure 21.2). There are many artifacts that are generated as part of the activities in the various blocks (the blocks are also referred to as views). The business view will have artifacts on business requirements, process definition, and policies. In the system view as part of modeling, the solution there will be artifacts on the system design, system contracts, system capabilities, and process flow represented as information mod- els. In the implementation view the system design is validated and implemented on specif