may start with a business requirement and finish with a deployed solution to support and automate the stated requirement. It is also important to note that an organization may move through the lifecycle in other ways to deploy a solution. The important note is that for all solutions, the business and technology processes will make up a lifecycle which will pass through various views with clearly identifiable entry and exit criteria. 8 Simple Object Access Protocol (SOAP) is a protocol specification for exchanging structured information in the implementation of web services in computer networks. Java Platform, Enterprise Edition or Java EE is a widely used platform for server programming in the Java programming language. The Extensible Markup Language (XML) is a general-purpose specification for creating custom markup languages. The Java Message Service (JMS) API is a Java Message Oriented Middleware (MOM) API for sending messages between two or more clients. JMS is a part of the Java Platform, Enterprise Edition. Next Generation Mobile Communications Ecosystem NGOSS Lifecycle Logical Technology Business Neutral System Business Capabilities, Knowledge Base System Capabilities, Constraints & Context Constraints & Context Corporate NGOSS Knowledge Shared Knowledge Deployment Implementation Physical Technology Specific Deployment Capabilities, Implementation Capabilities, Constraints & Context Constraints & Context Service Providers Service Developers Figure 8.22 NGOSS lifecycle and methodology. Reproduced from 2004 TM Forum [33] The NGOSS lifecycle as shown in Figure 8.22 consists of two planes of interest, the Logical or Technology Neutral plane and the Physical or Technology Specific plane. These planes intersect with two perspectives of influence namely service provider perspective and the service developers' perspective to produce the four NGOSS lifecycle views [33]: The Business View: In the business view, the eTOM and SID are used to focus on the concerns of business namely processes, policies, entities and in