. A set of meta models are used for developing business and technology artifacts. This way changes can be tracked and easily updated. Separate emphasis to enterprise as business, such as in Zachman framework. Support for distributed framework as in RM-ODP. Use case based iterative approach used in USDP. Some of the goals of having an NGOSS lifecycle were to: Identify different levels of process and information decomposition. Define specifications for business model and solution. Provide traceability between the different stages in the life cycle. Have a formalized way for NGOSS solution development. NGOSS lifecycle is built on two sets of views. In the first set there is a physical or technology specific and a logical or technology neutral view. The technology spe- cific view handles implementation and deployment and the technology neutral view handles requirements and design. When a problem is identified, the requirements that are captured are not specific to a technology. NGOSS suggests the design definition also to be independent of the technology to facilitate multiple equivalent instantiations from a single solution definition. In the implementation and deploy- ment phase a specific technology is adopted and used. The second set consists of a service developer view and a service provider view. While the service provider identifies the business issues and finally deploys the solution, the design and implementation of the solution is handled by the service developer. It can be seen that both service provider and service developer has inter- actions with the logical and physical views of the NGOSS lifecycle. The overlap of service provider view with the logical view happens in the busi- ness block where the business problems are identified. All the activities of the ser- vice provider, for business definition including process and preparation of artifacts for service developer to start work on the design, happens in the business block. The overlap of service developer with the logical view happens in the system