ther serve for real practice? How to work together with current telecom network to perform best software performance? All these questions are almost oriented to integration problems, including busi- ness integration, networks integration, and technologies integration. Before these actual implement of SDP, modeling and analyzing approaches should be taken into Service Delivery Platforms consideration first. Reference [34] proposed a model-driven approach which starts with establishing a model to describe business services from the perspective of busi- ness people. It aims to highlight the importance of modeling business specification of a service at all levels of granularity. Only in this way, business services can be designed, deployed, and delivered to maximize benefits from perspective from tele- com operators and service providers. Additionally, analysis methods are also cru- cial. Reference [35] discussed a domain requirement model and relevant analysis method in software product line engineering for solution domains. It aims to uti- lize the relationships in the domain requirement model and follow the constraints in the configuration model, which enables domain requirements that are easy to navigate, update, communicate, and configure. All in all, when it comes to software engineering, it involves with actual analy- sis, designation, modeling approaches, and technical implement. Any processes of this step will determine how the system will perform. Thus, both analysis sections and implement parts should be executed carefully and flexibly for further expand- ing and integrations. 6.2.5 Others Some other proposals and requirements also pay to notice. Reference [36] introduces the layered architecture of service delivery open platform (SDOP), and particularly describes the components and the functions of SDOP with its advantages, such as converged network, services and data resources, integration of a wide range of services ability to diverse and personal- ized business applications, service platform operation,