- Email: [email protected]
Stages of Information System Development in the Process Approach
Available online at www.sciencedirect.com
ScienceDirect Procedia Computer Science 77 (2015) 98 – 103
ICTE in Regional Development
Stages of information system development in the process approach Vira Shendryka, Andrii Boikoa* a
Sumy State University, 2, Rymskogo-Korsakova st., 40007 Sumy ,Ukraine
Abstract The paper is dedicated to the description of problems that occur during the functional modelling of MES (manufacturing execution system) class information systems. It was determined that the most significant problem is the lack of the universality of information systems. According to preliminary studies, the universality is achieved by using a process approach during design. Thus, it requires the improvement of the design process. To solve this issue, specifics were discussed to apply different approaches to the design of information systems at the lowest level. It helped to make a conclusion about the correct choice for the design approach. During functional modelling, the emphasis was on networked information systems with complete or partial virtualization. For this task, a model of the information system was built according to features of service-oriented architecture. At the stage of selecting CASE-tools, the accent was on the use of WEB-oriented tools. These steps led to the unification of the design and implementation of MES class information systems, and it will increase the universality of the developed information systems. © Published by Elsevier B.V. B.V. This is an open access article under the CC BY-NC-ND license © 2015 2016The TheAuthors. Authors. Published by Elsevier (http://creativecommons.org/licenses/by-nc-nd/4.0/). Peer-review under responsibility of the Sociotechnical Systems Engineering of Vidzeme Applied Sciences. Peer-review under responsibility of the Sociotechnical Systems Engineering InstituteInstitute of Vidzeme UniversityUniversity of Applied of Sciences Keywords: Information system; Functional modeling; Process-oriented approach; Service-oriented architecture
1. Introduction Nowadays the vast majority of manufactures can only work effectively with “flexible” management. As the volume of processed information is growing exponentially, achieving the goal becomes more complicated. Therefore, the necessary condition to achieve “flexibility” is the use of Information Systems (ISs) and their main responsibility is to ensure the full life cycle of production. This aspect may be achieved only by using different sets
* Corresponding author. Tel.: +38-050-181-2678; E-mail address: [email protected], [email protected]
1877-0509 © 2015 The Authors. Published by Elsevier B.V. This is an open access article under the CC BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/). Peer-review under responsibility of the Sociotechnical Systems Engineering Institute of Vidzeme University of Applied Sciences doi:10.1016/j.procs.2015.12.365
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
of IS, such as Supply Chain Management (SCM), Enterprise Resource Planning (ERP), Sales and Service Management (SSM), Management of production processes and products (P/PE) and others. The modern market of information technology has a large number of information systems that belong to different classes and cover the full life cycle of industrial enterprises. However, the main difficulty arises in the process of functional modelling of ERP-systems and MESs. The class of ERP-systems is an IS of higher level that provides human resource management, financial management, asset management, etc.1, 2. They are very well represented in the world market, as they provide information support for almost all functions at the enterprise of any type. MESs are dependent on the production type of enterprises, so they are not as well represented in the IT field. MESs are considered ISs of the lowest level. They belong to the class of control systems at the plant level (the first production process in the enterprise), and they are hardly used for integrated production management in general. This class of ISs represents the automated system of management enterprise activity in real time. ISs provide planning, optimization, monitoring and documentation of production processes. Despite the wide array of functions of information systems in this class, they are not able to support the full life cycle of production, as a result, their activity is closely related to other types of ISs. Thus, it should be noted that there are no universal and commonly known investigations and recommendations about what specific method should be used for the functional modelling of MES class information systems, which can help to reduce the probability of obtaining the a result in the design process. 2. The analysis of approaches to design The majority of existing MES class information systems was designed and implemented in the maintenance of activity of a particular company. As a result, these ISs are not able to replace each other and therefore they are not universal. Each IS is not unified and cannot provide the activity of the enterprise with similar type of production. To solve this problem, firstly approaches that are used during the functional modelling of information systems should be analysed. A functional approach was one of the most popular in the functional modelling of information systems. Its essence lies in the decomposition of the total activity into automated functions: the system divides into functional subsystems, which are divided into sub-functions, and then into tasks and so on. This process continues until it receives the number of specific procedures. For this purpose such principles as “divide and conquer”, hierarchical ordering, abstraction, formalization, consistency, and data structuration are used. These principles allow getting the deterministic and verbally described model of the information system. To illustrate the functions and relations between principles different types of charts are used such as SADT (Structured Analysis and Design Technique), DFD (Data Flow Diagrams), ERD (Entity-Relationship Diagrams). The combination of these principles and diagrams allows getting a complete description of the information system during functional modelling. This approach to functional modelling was used as the core for a long time. However, during the development of IS the common error arose that resulted in the loss of system integrity. This was caused by problems in information matching of individual components. The centralized solving of this problem required changes in the design of the IS. It led to a shift from a functional approach to the methodology, which is based on the analysis and management of information flows. Then there was a transition to a process-oriented approach as a more general and informative solution. In the frame of this approach the choice of IS structure and making changes in it occur depending on the structure and features of the process, which is defined by end users. Nowadays the basis of the analysis of the information system design process is shifting even further to control work, make tools to create workflows and to manage them. It should be noted that management of business processes and workflows is not the same thing. The business process determines what should be done, including establishing a ratio between input and output. The structure of the business process may include a manual component, with the use any type of resources.3, 4 Streams of work describe how a specific result can be achieved.5 Thus it was concluded that the relationship between business process and workflow is simple enough6 and can be presented as a diagram in Figure 1.
99
100
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
Fig. 1. The relationship between business processes and workflows
Developed ISs of MES class, also do not conform to the current trend of network information systems based on virtualization, the use of which allows to maximize the use of server resources by minimizing equipment downtime (decrease IT costs), centrally manage, increase the security of IT infrastructure, etc. The fast and global development of information technology changes the direction of ISs design towards unification and universalization. This in turn led to the need to make changes in the functional modelling of MES class information systems. 3. The problem statement It was found that one of the main reasons for the transition from a functional to a process-oriented approach was a low level of the universality in the information system’s development. It, in turn, was not allowed to use the same IS in the same type of enterprise activity. The ungreediness of the functional approach should be noted: the use of networked information systems based on virtualization with complete or partial imposition of IS's infrastructure to the network. The addressing of these shortcomings should improve the functional modelling of the information system. The process of IS's designing is a multi-procedure. At the initial stage, it is primarily necessary to: x Analyse and choose a new approach to designing information systems; x Select standards that will regulate issues of standardization; x Analyse and choose the tools that will be used during the functional modelling of IS. 4. Functional design concept development During the functional modelling and implementation of IS's model, which is based on a process-oriented approach, it is appropriate to use the service-oriented architecture (SOA) of the IS. It firstly requires highlighting the functional elements of SOA services, which later will be the used for the synthesis of business processes and their modernization. According to the definition by OASIS (Organization for the Advancement of Structured Information Standards), which deals with the standardization of SOA components, SOA is a paradigm of distributed organizational and utilitarian opportunities, which works under the management of domains that belong to different owners7. In other words, SOA is an architectural style of creating IT enterprise architecture. It is based on service orientation to achieve a closer relationship between business and information systems that support business. Thus, SOA considers service orientation as an approach to the integrating of business based on interconnected services. To achieve this, software and tools need to be divided into small-unified standardized services, and in turn, the basic activity (action) corresponds to each of them. To perform this function, mechanisms of business process modelling are used. Together with the ability to quickly make changes in processes they are the basis of on SOA based IS efficiency. To solve problems that arise in this case, business tools should be provided that will be used for the creation of new business functions, making
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
101
relationships between business features that stand out from existing applications, service and the reorganization of existing business processes, the generation of a workflow to perform business processes. A common argument against transition to SOA can be a statement that the technology is associated with the complete “fracture” of the existing system, and therefore requires very high one-time costs. In fact, individual steps or applications can be gradually implemented, and the whole transition can be made in an evolutionary way. In this case are used technologies that ensure the compliance of the previously imposed standards and continuity with respect to the previously installed software and systems. A generalized SOA structure is shown in Figure 2.
Fig. 2. General service - oriented architecture
Figure 2 shows the process of information system operation, which is based on a SOA with the current proprietary software. The last are considered acting information systems, office suites, and a client software and programs that are inherited from previous stages of system development. The whole structure consists of four layers: business processes, services, applications and technological layer. At first, the concept of SOA is considered only in the frame of functional approach and then together with the CORBA concept and Java tools8. This approach is not widely used, since in the composition of the used architecture at that time there was no service layer. A large number of applications have different GUI interfaces, the incompatible logic of business processes, various storage systems (DBMS), consequently all of it complicates the system. The business process implementation was directly linked to the technological level and dependent on the speed of information exchange between components that are identical in functionality, but dissimilar in design (for example, between different database applications). The inclusion of an additional service layer in the SOA concept largely allows to independently use services below the layer of applications and technology platform. This service layer forms services that are indicated above, each of them is tied to the appropriate business logic and platform. The level of service leads to the construction of the business process layer, which ensures the next operation in information systems: x The line of business services reproduces the crude set of features for inclusion in the business process; x The description (contract) of each service in the line of services uniquely defines it, and forms the interface. The presence of the last allows to independently create business processes and without the involvement of knowledge about the technology platforms; x The tool of the registry and search of services will support the ability to change business processes through rapid access to services if the necessity arises; x The data model is implemented at the service level and is based on the structure of the business domain and does not depend on individual application data models. Further, if XML is used as a canonical data exchange format, the inclusion of services will carry out irrespective from the internal data structures in annexes.
102
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
The implementation of modern complex information systems of the MES class with the use only principle (which was explained above) is impossible without the standardization and unification of processes and elements from which systems are built. Today in the world there is no common centre, which coordinates the general policy in this area, and only several organizations are developing and supporting SOA standards. When designing ISs of the MES class, it is necessary to apply a set of standards: OASIS, W3C (World Wide Web Consortium), WS-I (Web Services Interoperability Organization), IETF (Internet Engineering Task Force), OMG (Object Management Group), the ISA-95 Standard, the ISA-88 Standard, OAG (Open Applications Group), SCOR (Supply-Chain Operations Reference). The list of standards comprehensively covers almost the entire process of IS design. Some standards are used in the design of business processes and workflow. Part of them ensure compliance with the requirements in the area of functional requirements to MES class information systems. Another part provides a regulation during the design and implementation of network components of IS. When selecting CASE-tools to the design of information systems MES class is used a number of standards. Based on current trends in the integration of Web-services and cloud technologies the necessary condition is becoming the use such complex series of standards as BPEL, WSDL, SOAP, UDDI. The composition with Web-services based on elementary works is carried out by using the language of the implementation of business processes - Business Process Execution Language (BPEL). The language appeared as a result of combining such languages as WSFL (Web Services Flow Language), developed by the corporation IBM, and XLANG created by Microsoft. Language notation is based on XML. The use of this language allows to create and execute the workflows as the logical sequence of actions that include: 1) The adoption of request for inclusion work into the process; 2) The checking of description, and in the case if options are matched, it will necessary to prepare the positive response to the request; 3) Otherwise the rejection of the request with an explanation. Typically, BPEL forms the workflow, which consists of a sequence of logic operations or activities, each of them has its own “place” in the chart of workflows or the function of programming code. It is possible to use two forms of BPEL. The first is an executable BPEL - a process that is also seen as a service, and can be an orchestration hub. The software which implements executable BPEL-processes is called BPEL-engine (the “engine” of BPEL-process). In this case, one executable process may include another which gives the effect of the inclusion of one orchestration (the service's order) to another, as shown in Figure 3.
Fig. 3. The example of related orchestrations
The second form is an abstract process that is almost identical to the executable process except for the data filing. In this case, the process is the logic of business process and can be used in defining the behaviour of organizational structure elements that support the process. Furthermore it is also a guide for programmers and developers that automate the process; and it is an input for commercial software, which will work together with the information system that is designed. 5. Conclusions In this paper studies were conducted to improve the process of functional modelling of MES class information systems. The main objective was related to the improving of the process and steps that are used in functional modelling of IS of MES class. Thus, it was considered features of the use of different approaches in the design of information systems of the lowest level. The one main problem when using a functional approach was the
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
103
combination of designed components of the IS. This led to the loss of integrity of the information system, and subsequently to the loss of universality. The unreadiness of use the functional approach during design corresponding to modern trends should also be noted t. This approach cannot properly design and implement networked information systems based on virtualization with the complete or partial imposition of IS's infrastructure to the network. This led to a conclusion about the need to move from a functional to a process-oriented approach. The use of a process-oriented methodology during the design of information systems helped to implement the serviceoriented architecture, and consider the model of IS as a set of the service level and the level of business processes that are connected with each other. The function of the last is to fulfil a whole logic of IS operation. The choice of tools was implemented according to the needs of network information system design. It allows complying with modern requirements of IS and further it will make it possible to carry out works on virtualization of IT infrastructure. The obtained results are a necessary basis for further work in the field of the functional modelling of MES class information systems.
References 1. 2. 3. 4. 5. 6. 7. 8.
Woods, D.. Enterprise Services Architecture, O’Reily Field Guide 2003. 209 p. Newcomer, E., Lomow, G.. Understanding SOA with Web Services, Addison Wesley Professional, 2005. 444p. Bass, L. Clements, P. Kazman, R. Software Architecture in Practice, 2nd Edition. Addison Wesley 2003. 560 p Kulvatunyou, B., Wysk, R. A. A functional approach to enterprise-based engineering activities. Journal of Manufacturing Systems, Vol. 19, No. 2, 2000, pp. 156 – 171. O’Brien, W. J, Joachim, H., Siddiqui, M., Topsakal O. Challenges, approaches and architecture for distributed process integration in heterogeneous environments. Advanced Engineering Informatics, Vol. 22, No. 1, 2008, pp. 28 – 44. Kishore, R., Zhang, H., Ramesh, R. Enterprise integration using the agent paradigm: foundations of multi-agent-based integrative business information systems. Decision Support Systems, Vol. 42, No. 1, 2006, pp. 48 – 78. Kettinger, W. J, Teng, J. T. C, Guha, S. Business process change: a study of methodologies, techniques, and tools. MIS quarterly, 1997, pp. 55 – 80. Ferrer, I, Rios, J, Ciurana, J. An approach to integrate manufacturing process information in part design phases. Journal of Materials Processing Technology, Vol. 209, No 4, 2009, pp.2085 – 2091.
Vira Shendryk was a visiting scholar at McMaster University, Canada in 2012 and was a visiting research fellow at the Department of Computer Science of the Faculty of Technology and Society, the Malmo University, Sweden in 2013. Her research interest is focused on the field of Information Systems and Decision Science particularly in decision making under uncertainty. She has written over 100 journal articles and conference papers and presentations.
Andrii Boiko is a Ph.D. student of computer science at the Sumy State University, Sumy, Ukraine. He had a Bachelor of Computer science at Sumy State University in 2013. He received his Master’s Degree of Information Technology of Design (Diploma with distinction) in 2014. At November 2014 till present he is a PhD student at the Sumy State University. Research direction is creation information technologies of information processing within the information systems integration of enterprise with a multiple production.
ScienceDirect Procedia Computer Science 77 (2015) 98 – 103
ICTE in Regional Development
Stages of information system development in the process approach Vira Shendryka, Andrii Boikoa* a
Sumy State University, 2, Rymskogo-Korsakova st., 40007 Sumy ,Ukraine
Abstract The paper is dedicated to the description of problems that occur during the functional modelling of MES (manufacturing execution system) class information systems. It was determined that the most significant problem is the lack of the universality of information systems. According to preliminary studies, the universality is achieved by using a process approach during design. Thus, it requires the improvement of the design process. To solve this issue, specifics were discussed to apply different approaches to the design of information systems at the lowest level. It helped to make a conclusion about the correct choice for the design approach. During functional modelling, the emphasis was on networked information systems with complete or partial virtualization. For this task, a model of the information system was built according to features of service-oriented architecture. At the stage of selecting CASE-tools, the accent was on the use of WEB-oriented tools. These steps led to the unification of the design and implementation of MES class information systems, and it will increase the universality of the developed information systems. © Published by Elsevier B.V. B.V. This is an open access article under the CC BY-NC-ND license © 2015 2016The TheAuthors. Authors. Published by Elsevier (http://creativecommons.org/licenses/by-nc-nd/4.0/). Peer-review under responsibility of the Sociotechnical Systems Engineering of Vidzeme Applied Sciences. Peer-review under responsibility of the Sociotechnical Systems Engineering InstituteInstitute of Vidzeme UniversityUniversity of Applied of Sciences Keywords: Information system; Functional modeling; Process-oriented approach; Service-oriented architecture
1. Introduction Nowadays the vast majority of manufactures can only work effectively with “flexible” management. As the volume of processed information is growing exponentially, achieving the goal becomes more complicated. Therefore, the necessary condition to achieve “flexibility” is the use of Information Systems (ISs) and their main responsibility is to ensure the full life cycle of production. This aspect may be achieved only by using different sets
* Corresponding author. Tel.: +38-050-181-2678; E-mail address: [email protected], [email protected]
1877-0509 © 2015 The Authors. Published by Elsevier B.V. This is an open access article under the CC BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/). Peer-review under responsibility of the Sociotechnical Systems Engineering Institute of Vidzeme University of Applied Sciences doi:10.1016/j.procs.2015.12.365
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
of IS, such as Supply Chain Management (SCM), Enterprise Resource Planning (ERP), Sales and Service Management (SSM), Management of production processes and products (P/PE) and others. The modern market of information technology has a large number of information systems that belong to different classes and cover the full life cycle of industrial enterprises. However, the main difficulty arises in the process of functional modelling of ERP-systems and MESs. The class of ERP-systems is an IS of higher level that provides human resource management, financial management, asset management, etc.1, 2. They are very well represented in the world market, as they provide information support for almost all functions at the enterprise of any type. MESs are dependent on the production type of enterprises, so they are not as well represented in the IT field. MESs are considered ISs of the lowest level. They belong to the class of control systems at the plant level (the first production process in the enterprise), and they are hardly used for integrated production management in general. This class of ISs represents the automated system of management enterprise activity in real time. ISs provide planning, optimization, monitoring and documentation of production processes. Despite the wide array of functions of information systems in this class, they are not able to support the full life cycle of production, as a result, their activity is closely related to other types of ISs. Thus, it should be noted that there are no universal and commonly known investigations and recommendations about what specific method should be used for the functional modelling of MES class information systems, which can help to reduce the probability of obtaining the a result in the design process. 2. The analysis of approaches to design The majority of existing MES class information systems was designed and implemented in the maintenance of activity of a particular company. As a result, these ISs are not able to replace each other and therefore they are not universal. Each IS is not unified and cannot provide the activity of the enterprise with similar type of production. To solve this problem, firstly approaches that are used during the functional modelling of information systems should be analysed. A functional approach was one of the most popular in the functional modelling of information systems. Its essence lies in the decomposition of the total activity into automated functions: the system divides into functional subsystems, which are divided into sub-functions, and then into tasks and so on. This process continues until it receives the number of specific procedures. For this purpose such principles as “divide and conquer”, hierarchical ordering, abstraction, formalization, consistency, and data structuration are used. These principles allow getting the deterministic and verbally described model of the information system. To illustrate the functions and relations between principles different types of charts are used such as SADT (Structured Analysis and Design Technique), DFD (Data Flow Diagrams), ERD (Entity-Relationship Diagrams). The combination of these principles and diagrams allows getting a complete description of the information system during functional modelling. This approach to functional modelling was used as the core for a long time. However, during the development of IS the common error arose that resulted in the loss of system integrity. This was caused by problems in information matching of individual components. The centralized solving of this problem required changes in the design of the IS. It led to a shift from a functional approach to the methodology, which is based on the analysis and management of information flows. Then there was a transition to a process-oriented approach as a more general and informative solution. In the frame of this approach the choice of IS structure and making changes in it occur depending on the structure and features of the process, which is defined by end users. Nowadays the basis of the analysis of the information system design process is shifting even further to control work, make tools to create workflows and to manage them. It should be noted that management of business processes and workflows is not the same thing. The business process determines what should be done, including establishing a ratio between input and output. The structure of the business process may include a manual component, with the use any type of resources.3, 4 Streams of work describe how a specific result can be achieved.5 Thus it was concluded that the relationship between business process and workflow is simple enough6 and can be presented as a diagram in Figure 1.
99
100
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
Fig. 1. The relationship between business processes and workflows
Developed ISs of MES class, also do not conform to the current trend of network information systems based on virtualization, the use of which allows to maximize the use of server resources by minimizing equipment downtime (decrease IT costs), centrally manage, increase the security of IT infrastructure, etc. The fast and global development of information technology changes the direction of ISs design towards unification and universalization. This in turn led to the need to make changes in the functional modelling of MES class information systems. 3. The problem statement It was found that one of the main reasons for the transition from a functional to a process-oriented approach was a low level of the universality in the information system’s development. It, in turn, was not allowed to use the same IS in the same type of enterprise activity. The ungreediness of the functional approach should be noted: the use of networked information systems based on virtualization with complete or partial imposition of IS's infrastructure to the network. The addressing of these shortcomings should improve the functional modelling of the information system. The process of IS's designing is a multi-procedure. At the initial stage, it is primarily necessary to: x Analyse and choose a new approach to designing information systems; x Select standards that will regulate issues of standardization; x Analyse and choose the tools that will be used during the functional modelling of IS. 4. Functional design concept development During the functional modelling and implementation of IS's model, which is based on a process-oriented approach, it is appropriate to use the service-oriented architecture (SOA) of the IS. It firstly requires highlighting the functional elements of SOA services, which later will be the used for the synthesis of business processes and their modernization. According to the definition by OASIS (Organization for the Advancement of Structured Information Standards), which deals with the standardization of SOA components, SOA is a paradigm of distributed organizational and utilitarian opportunities, which works under the management of domains that belong to different owners7. In other words, SOA is an architectural style of creating IT enterprise architecture. It is based on service orientation to achieve a closer relationship between business and information systems that support business. Thus, SOA considers service orientation as an approach to the integrating of business based on interconnected services. To achieve this, software and tools need to be divided into small-unified standardized services, and in turn, the basic activity (action) corresponds to each of them. To perform this function, mechanisms of business process modelling are used. Together with the ability to quickly make changes in processes they are the basis of on SOA based IS efficiency. To solve problems that arise in this case, business tools should be provided that will be used for the creation of new business functions, making
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
101
relationships between business features that stand out from existing applications, service and the reorganization of existing business processes, the generation of a workflow to perform business processes. A common argument against transition to SOA can be a statement that the technology is associated with the complete “fracture” of the existing system, and therefore requires very high one-time costs. In fact, individual steps or applications can be gradually implemented, and the whole transition can be made in an evolutionary way. In this case are used technologies that ensure the compliance of the previously imposed standards and continuity with respect to the previously installed software and systems. A generalized SOA structure is shown in Figure 2.
Fig. 2. General service - oriented architecture
Figure 2 shows the process of information system operation, which is based on a SOA with the current proprietary software. The last are considered acting information systems, office suites, and a client software and programs that are inherited from previous stages of system development. The whole structure consists of four layers: business processes, services, applications and technological layer. At first, the concept of SOA is considered only in the frame of functional approach and then together with the CORBA concept and Java tools8. This approach is not widely used, since in the composition of the used architecture at that time there was no service layer. A large number of applications have different GUI interfaces, the incompatible logic of business processes, various storage systems (DBMS), consequently all of it complicates the system. The business process implementation was directly linked to the technological level and dependent on the speed of information exchange between components that are identical in functionality, but dissimilar in design (for example, between different database applications). The inclusion of an additional service layer in the SOA concept largely allows to independently use services below the layer of applications and technology platform. This service layer forms services that are indicated above, each of them is tied to the appropriate business logic and platform. The level of service leads to the construction of the business process layer, which ensures the next operation in information systems: x The line of business services reproduces the crude set of features for inclusion in the business process; x The description (contract) of each service in the line of services uniquely defines it, and forms the interface. The presence of the last allows to independently create business processes and without the involvement of knowledge about the technology platforms; x The tool of the registry and search of services will support the ability to change business processes through rapid access to services if the necessity arises; x The data model is implemented at the service level and is based on the structure of the business domain and does not depend on individual application data models. Further, if XML is used as a canonical data exchange format, the inclusion of services will carry out irrespective from the internal data structures in annexes.
102
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
The implementation of modern complex information systems of the MES class with the use only principle (which was explained above) is impossible without the standardization and unification of processes and elements from which systems are built. Today in the world there is no common centre, which coordinates the general policy in this area, and only several organizations are developing and supporting SOA standards. When designing ISs of the MES class, it is necessary to apply a set of standards: OASIS, W3C (World Wide Web Consortium), WS-I (Web Services Interoperability Organization), IETF (Internet Engineering Task Force), OMG (Object Management Group), the ISA-95 Standard, the ISA-88 Standard, OAG (Open Applications Group), SCOR (Supply-Chain Operations Reference). The list of standards comprehensively covers almost the entire process of IS design. Some standards are used in the design of business processes and workflow. Part of them ensure compliance with the requirements in the area of functional requirements to MES class information systems. Another part provides a regulation during the design and implementation of network components of IS. When selecting CASE-tools to the design of information systems MES class is used a number of standards. Based on current trends in the integration of Web-services and cloud technologies the necessary condition is becoming the use such complex series of standards as BPEL, WSDL, SOAP, UDDI. The composition with Web-services based on elementary works is carried out by using the language of the implementation of business processes - Business Process Execution Language (BPEL). The language appeared as a result of combining such languages as WSFL (Web Services Flow Language), developed by the corporation IBM, and XLANG created by Microsoft. Language notation is based on XML. The use of this language allows to create and execute the workflows as the logical sequence of actions that include: 1) The adoption of request for inclusion work into the process; 2) The checking of description, and in the case if options are matched, it will necessary to prepare the positive response to the request; 3) Otherwise the rejection of the request with an explanation. Typically, BPEL forms the workflow, which consists of a sequence of logic operations or activities, each of them has its own “place” in the chart of workflows or the function of programming code. It is possible to use two forms of BPEL. The first is an executable BPEL - a process that is also seen as a service, and can be an orchestration hub. The software which implements executable BPEL-processes is called BPEL-engine (the “engine” of BPEL-process). In this case, one executable process may include another which gives the effect of the inclusion of one orchestration (the service's order) to another, as shown in Figure 3.
Fig. 3. The example of related orchestrations
The second form is an abstract process that is almost identical to the executable process except for the data filing. In this case, the process is the logic of business process and can be used in defining the behaviour of organizational structure elements that support the process. Furthermore it is also a guide for programmers and developers that automate the process; and it is an input for commercial software, which will work together with the information system that is designed. 5. Conclusions In this paper studies were conducted to improve the process of functional modelling of MES class information systems. The main objective was related to the improving of the process and steps that are used in functional modelling of IS of MES class. Thus, it was considered features of the use of different approaches in the design of information systems of the lowest level. The one main problem when using a functional approach was the
Vira Shendryk and Andrii Boiko / Procedia Computer Science 77 (2015) 98 – 103
103
combination of designed components of the IS. This led to the loss of integrity of the information system, and subsequently to the loss of universality. The unreadiness of use the functional approach during design corresponding to modern trends should also be noted t. This approach cannot properly design and implement networked information systems based on virtualization with the complete or partial imposition of IS's infrastructure to the network. This led to a conclusion about the need to move from a functional to a process-oriented approach. The use of a process-oriented methodology during the design of information systems helped to implement the serviceoriented architecture, and consider the model of IS as a set of the service level and the level of business processes that are connected with each other. The function of the last is to fulfil a whole logic of IS operation. The choice of tools was implemented according to the needs of network information system design. It allows complying with modern requirements of IS and further it will make it possible to carry out works on virtualization of IT infrastructure. The obtained results are a necessary basis for further work in the field of the functional modelling of MES class information systems.
References 1. 2. 3. 4. 5. 6. 7. 8.
Woods, D.. Enterprise Services Architecture, O’Reily Field Guide 2003. 209 p. Newcomer, E., Lomow, G.. Understanding SOA with Web Services, Addison Wesley Professional, 2005. 444p. Bass, L. Clements, P. Kazman, R. Software Architecture in Practice, 2nd Edition. Addison Wesley 2003. 560 p Kulvatunyou, B., Wysk, R. A. A functional approach to enterprise-based engineering activities. Journal of Manufacturing Systems, Vol. 19, No. 2, 2000, pp. 156 – 171. O’Brien, W. J, Joachim, H., Siddiqui, M., Topsakal O. Challenges, approaches and architecture for distributed process integration in heterogeneous environments. Advanced Engineering Informatics, Vol. 22, No. 1, 2008, pp. 28 – 44. Kishore, R., Zhang, H., Ramesh, R. Enterprise integration using the agent paradigm: foundations of multi-agent-based integrative business information systems. Decision Support Systems, Vol. 42, No. 1, 2006, pp. 48 – 78. Kettinger, W. J, Teng, J. T. C, Guha, S. Business process change: a study of methodologies, techniques, and tools. MIS quarterly, 1997, pp. 55 – 80. Ferrer, I, Rios, J, Ciurana, J. An approach to integrate manufacturing process information in part design phases. Journal of Materials Processing Technology, Vol. 209, No 4, 2009, pp.2085 – 2091.
Vira Shendryk was a visiting scholar at McMaster University, Canada in 2012 and was a visiting research fellow at the Department of Computer Science of the Faculty of Technology and Society, the Malmo University, Sweden in 2013. Her research interest is focused on the field of Information Systems and Decision Science particularly in decision making under uncertainty. She has written over 100 journal articles and conference papers and presentations.
Andrii Boiko is a Ph.D. student of computer science at the Sumy State University, Sumy, Ukraine. He had a Bachelor of Computer science at Sumy State University in 2013. He received his Master’s Degree of Information Technology of Design (Diploma with distinction) in 2014. At November 2014 till present he is a PhD student at the Sumy State University. Research direction is creation information technologies of information processing within the information systems integration of enterprise with a multiple production.