{'fraction_non_alphanumeric': 0.034458579585295, 'fraction_numerical': 0.01041771010718221, 'mean_word_length': 5.151571164510166, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Analysis Service Engineering Development Lifecycle: an Object-Oriented Approach

Service Engineering (SE) is defined as a set of activities introducing a new business service. An object-oriented methodology is defined as principles and procedures to develop object-oriented software. This paper proposes an object-oriented methodology embedded SE framework in re-defining business service as a service-oriented application with detail implementation by using Activities and Artifacts. The proposed model for SE lifecycle consists of Process, Notation, and Tools modeled by utilizing Unified Process (UP), Business Process Model and Notation (BPMN), a programming language that supports the Business Process Management System (BPMS). In this research, the explanation is organized into three parts: (1) the brief review of the existing SE framework, (2) the elaboration of the proposed model, and (3) the detail of the SE lifecycle model with survey results from case studies. The framework is proposed to help practitioners and researchers to conduct service-oriented application by employing principles and methodology offered by the object-oriented approach.


Introduction
SE represents software engineering process at a higher level of abstraction. If the main purpose of software engineering is a software system, the main purpose of SE is business service system [1]. Business service in this research refers to a common definition of a service as business activity provided by a service provider to service consumer in order to create value for the customer [2]. There are three main factors to make an organization get more value than other competitors, which are a business organization, product or services produced, and ongoing business process organization [3].
There is a method to evaluate and improve business process, called Business Process Management (BPM) [3]. The use of BPM method in this research defines an SE framework into two workflows process of UP disciplines. Those workflows are Business Modeling of a current business process (As-Is) and implemented business process (To-Be). Based on the result of Requirement analysis for a solution of information system or application. BPM is applied on the stage of the SE framework.
The purpose of the SE framework is to provide service in a layer of information and technology. Particularly, in the form of web services can automate the interaction between services. Hence, the enterprise architecture has to be redefined using the approach of Service Oriented Architecture (SOA). The SOA approach can integrate business process and information technology infrastructure. Analysis and design of service are derived from the organization's business process [4].
In SOA development requires a methodology, such as Service Oriented Unified Process (SOUP) from [5]. SOUP includes the complete stage of software engineering lifecycle for SOA development side (SOUP for Initial SOA Deployment) until the maintenance side (SOUP for Ongoing SOA Management). However, SOUP already explained the documentation, but it still leaves room for adaptation. Hence, this research gives a practical approach for SOA development by using a framework of SE [1].
A comprehensive SE framework for delivering business service as service-oriented application based on SOA methodology has been proposed by Suhardi et al. [6]. The SE framework consists of 8 activities grouped into three stages: (1) identification, (2) design, and (3) prototyping. The main analysis tool proposed in Identification stage that is the Business Model Canvas (BMC), then in Design stage uses Service Blueprinting. The use of BMC and Service Blueprinting aim to replace the process of service analysis and service design from SOA methodologies.
There are several technical platforms introduced in Prototyping stage along with proposed technology that is Microsoft's Windows Communication Foundation (WCF) [6]. To achieve the goal within the proposed lifecycle model in detailing Activities and Artifacts, Bizagi technology is recommended due to its rapid process automation. Bizagi support BPM and SOA with real-time analytics [7]. The BPM component consists of process modeling, process execution, and process monitoring [8]. Specifically, the SOA component is in the form of web service technology [1].

The Proposed Model
The idea of this research is to use True Requirement Investigation from Identification phase of SE framework [1] by using Business Modeling and Requirements phase of UP [9] as a prior workflows process for the design process. The Business Modeling tool uses flowchart as business process of As-Is. The Requirements uses basic analysis activities [10] to analyze the priority components which consists of: (1) list of problems, (2) list of directives, and (3) list of opportunity. Furthermore, BPM is used in Identification Analysis by applying analysis value added to business service as service-oriented Idea [3].
International Conference on Computation in Science and Engineering IOP Publishing IOP Conf. Series: Journal of Physics: Conf. Series 1090 (2018) 012020 doi :10.1088/1742-6596/1090/1/012020 Figure 3. Identification stage: apply analysis value added to get service-oriented Idea (adapted from [1], [3]) Service Blueprinting can be used to describe service-oriented as business process of To-Be designed in SOA approached by using BPM notation (BPMN) model [8]. Bizagi as BPM system (BPMS) makes the implementation of immediate business requirements by providing monitor and continuously improve the business process [7]. In this research, for the Prototyping stage is only a Develop process which is performed. Finally, an object-oriented methodology from UP [9] is used in detailing Activities and Artifacts with BPMN as a modeling language.

Results and Discussion
There are three phases of UP that are used in this research which are (1) inception, (2) elaboration, and (3) construction. Each phase consists of five workflows process: (1) business modeling, (2) requirements, (3) analysis & design, (4) implementation, (5) test.  [6]. The software based on SOA consists of two parts: (1) a set of services as service provider and (2) client applications as service consumer [12]. Hence, the additional activities required for defining the service that is service analysis and service design with reference to SOA lifecycle [4]. In this research, the SOA lifecycle consists of: (1) serviceoriented analysis, (2) service-oriented design, (3) service development, (4) service testing.  [7]. Technically, BPEL as a language that can be compiled by an application supporting orchestration of SOA layer [4]. BPMS role in this research is to support the technology needs of BPMN and BPEL. The following figure is the proposed lifecycle model for SE based on UP methodology.   From table 3, the proposed lifecycle model is below (I-Inception; E-Elaboration; C-Construction; sstart; r-refine): Test plan: unit, system s r

Case Studies
The first case study was performed before a definitive formal framework was devised. The goal was to provide an integrated e-government implementation [13]. The case study was started with a strategic analysis of the EKPPD (Evaluasi Kinerja Penyelenggaraan Pemerintahan Daerah) with BMC. Service blueprinting tool was only used lightly to specify the data dissemination service based on a request from SKPD (Satuan Kinerja Penyelenggaraan Pemerintahan Daerah). SOA method was employed to produce three layers of service: task-centric, entity-centric, and application utility. The service interface is described by using WSDL. The second case study was done after the first draft of the framework was formalized. The case study employed SE based on an object-oriented methodology of room usage permit in POLBAN [14]. The work produced two BPM diagrams: as-is business process to describe existing situation and to-be business process to propose the new service based on Porter's value chain analysis in performing true requirement investigation. Modeling notation was complemented with basic UML diagrams: Use Case, Class Diagram, and Sequence Diagram.
The third case study also select the process of room usage permit in POLBAN, but focusing on the design of proposed external data service for the agency as an external user. The work was also done by following the completed and formalized framework. BPMN diagram and Bizagi were used as BPMS in supporting the simplicity of service analysis as SE Identification, service design as SE Design, and service implementation as Prototyping of SE.
The results from the proposed framework utilization in the third case study were taught in a Proyek 3 Diploma degree class for a semester. At the end of the semester, there are three questions of a survey that was conducted to 32 students of the class to assess the simplicity of using the proposed framework. The response are given under 5-scale likert respond, from "strongly agree" to "strongly disagree". The questions and their results are presented in the following charts. The results from figure 6 show that more than 83% of the respondents agree that they able to adopt the proposed framework regarding the explicitness of activities and artifacts in implementing serviceorientation application.

Conclusion
Alternative software development for adopting SOA lifecycle within SE framework is proposed here along with several trial case studies. The proposed framework is emphasized on the simplicity of the object-oriented approach by using specific tools, notation, and process for each activity and artifact of introducing a new business service.
There is technology to support business service as a service-oriented application, Bizagi as Tools. The technology is used to ensure the proposed service analysis is implementable by using BPMN as Notation for service design process. The analysis and design of service will continue to be improved implementation in each UP phase as Process.