Formalization of SOA concepts with mathematical foundation

With the development of the IT industry, agility and dynamicity are the two expected characteristics from any business enterprise. Service oriented architecture (SOA) is emerging as a promising approach aiming to address the current trends/needs of enterprise business applications. The current work aims at giving an overview of the conceptual model of SOA based on set theory approach. Also, it posits mathematical definitions for service, logical service, environment service and application definition with the help of general systems theory and mathematical foundation. With the help of mathematical model, the definition and functionality of services enhances SOA principles which can be used efficiently in integrating heterogeneous components

A goal-oriented requirements modelling language for enterprise architecture

Methods for enterprise architecture, such as TOGAF, acknowledge the importance of requirements engineering in the development of enterprise architectures. Modelling support is needed to specify, document, communicate and reason about goals and requirements. Current modelling techniques for enterprise architecture focus on the products, services, processes and applications of an enterprise. In addition, techniques may be provided to describe structured requirements lists and use cases. Little support is available however for modelling the underlying motivation of enterprise architectures in terms of stakeholder concerns and the high-level goals that address these concerns. This paper describes a language that supports the modelling of this motivation. The definition of the language is based on existing work on high-level goal and requirements modelling and is aligned with an existing standard for enterprise modelling: the ArchiMate language. Furthermore, the paper illustrates how enterprise architecture can benefit from analysis techniques in the requirements domain

BPM News - Folge 3

Die BPM-Kolumne des EMISA-Forums berichtet über aktuelle Themen, Projekte und Veranstaltungen aus dem BPM-Umfeld. Schwerpunkt der vorliegenden Kolumne bildet das Thema Standardisierung von Prozessbeschreibungssprachen und -notationen im Allgemeinen und BPEL4WS (Business Process Execution Language for Web Services) im Speziellen. Hierzu liefert Jan Mendling von der Wirtschaftsuniversität Wien in aktuelles Schlagwort. Des weiteren erhalten Leser eine Zusammenfassung zweier im ersten Halbjahr 2006 veranstalteten Workshops zu den Themen „Flexibilität prozessorientierter Informationssysteme“ und „Kollaborative Prozesse“ sowie einen BPM Veranstaltungskalender für die 2. Jahreshälfte 2006

Benefits and Success Factors of Web Services Adoption: An Exploratory Action-research Project in a Brazilian Small Software House

It is usually difficult for companies to keep up with the development of new information technologies and adapt in face of the opportunities and threats those advances may represent. This is especially true for small and medium enterprises (SME) in emerging economies, where resources tend to be scarce and markets more volatile. This paper describes an action-research conducted in a small Brazilian software house that adopted an open-source Web Services development platform in order to improve its software development process. Data analysis revealed critical success factors (CSF) in the adoption process, as well as specific benefits and barriers prone to be faced by small software houses in their adoption efforts. In the process of overcoming such barriers, SME may acquire intellectual capital that represents an essential resource to ensure their competitiveness and survival in emerging economies

The Systematic Discovery of Services in Early Stages of Agile Developments: A Systematic Literature Review

In recent years, agile methodologies have been consolidated and extended in organizations that develop software in Web environments. For this reason, the development methodology of these organizations will not only be related to Services, but also to the Web Engineering paradigm. These organizations are heading for incorporating software development methodologies whose paradigm can allow integration, naturally and in the earlier stages of Web applications develop with the services of the organization that described and published in the Services Portfolio. The aim of this study will be to analyze the current state of the art in the process of discovering services in early stages of agile software development with focus on those identified requirements that could be covered with the services included in the Service Portfolio. We have identified 20 relevant papers through conducting a double systematic literature review (SLR). It is concluded that no study has been found that can solve the entire process of discovering candidate services within an organization that cover the requirements of a new application developed with agile methodologies. At the same time, guidelines have been found to formalize the solution to this problem and fill in that gap of knowledge by proposing in a single process, the formalization of a requirement based on agile techniques, which can be managed against a Services PortfolioMinisterio de Economía y Competitividad TIN2016-76956-C3-2-R (POLOLAS

Blueprint model and language for engineering cloud applications

Abstract: The research presented in this thesis is positioned within the domain of engineering CSBAs. Its contribution is twofold: (1) a uniform specification language, called the Blueprint Specification Language (BSL), for specifying cloud services across several cloud vendors and (2) a set of associated techniques, called the Blueprint Manipulation Techniques (BMTs), for publishing, querying, and composing cloud service specifications with aim to support the flexible design and configuration of an CSBA.

Knowledge-based Engineering in Product Development Processes - Process, IT and Knowledge Management perspectives

Product development as a field of practice and research has significantly changed due to the general trends of globalization changing the enterprise landscapes in which products are realized. The access to partners and suppliers with high technological specialization has also led to an increased specialization of original equipment manufacturers (OEMs). Furthermore, the products are becoming increasingly complex with a high functional and technological content and many variants. Combined with shorter lifecycles which require reuse of technologies and solutions, this has resulted in an overall increased knowledge intensity which necessitates a more explicit approach towards knowledge and knowledge management in product development. In parallel, methods and IT tools for managing knowledge have been developed and are more accessible and usable today. One such approach is knowledge-based engineering (KBE), a term that was coined in the mid-1980s as a label for applications which automate the design of rule-driven geometries. In this thesis the term KBE embraces the capture and application of engineering knowledge to automate engineering tasks, regardless of domain of application, and the thesis aims at contributing to a wider utilization of KBE in product development (PD). The thesis focuses on two perspectives of KBE; as a process improvement IT method and as a knowledge management (KM) method. In the first perspective, the lack of explicit regard for the constraints of the product lifecycle management (PLM) architecture, which governs the interaction of processes and IT in PD, has been identified to negatively affect the utilization of KBE in PD processes. In the second perspective, KM theories and models can complement existing methods for identifying potential for KBE applications.Regarding the first perspective, it is concluded that explicit regard for the PLM architecture decreases the need to develop and maintain software code related to hard coded redundant data and functions in the KBE application. The concept of service oriented architecture (SOA) has been found to enable an the explicit regard for the PLM architecture.. Regarding the second perspective, it is concluded that potential for KBE applications is indicated by: 1.) application of certain types of knowledge in PD processes 2.) high maturity and formalization of the applied knowledge 3.) a codification strategy for KM and 4.) an agreement and transparency regarding how the knowledge is applied, captured and transferred. It is also concluded that the formulation of explicit KM strategies in PD should be guided by knowledge application and its relation to strategic objectives focusing on types of knowledge, their role in the PD process and the methods and tools for their application. These, in turn, affect the methods and tools deployed for knowledge capture in order for it to integrate with the processes of knowledge origin. Finally, roles and processes for knowledge transfer have to be transparent to assure the motivation of individuals to engage in the KM strategy

Knowledge-based Engineering in Product Development Processes - Process, IT and Knowledge Management perspectives

Product development as a field of practice and research has significantly changed due to the general trends of globalization changing the enterprise landscapes in which products are realized. The access to partners and suppliers with high technological specialization has also led to an increased specialization of original equipment manufacturers (OEMs). Furthermore, the products are becoming increasingly complex with a high functional and technological content and many variants. Combined with shorter lifecycles which require reuse of technologies and solutions, this has resulted in an overall increased knowledge intensity which necessitates a more explicit approach towards knowledge and knowledge management in product development. In parallel, methods and IT tools for managing knowledge have been developed and are more accessible and usable today. One such approach is knowledge-based engineering (KBE), a term that was coined in the mid-1980s as a label for applications which automate the design of rule-driven geometries. In this thesis the term KBE embraces the capture and application of engineering knowledge to automate engineering tasks, regardless of domain of application, and the thesis aims at contributing to a wider utilization of KBE in product development (PD). The thesis focuses on two perspectives of KBE; as a process improvement IT method and as a knowledge management (KM) method. In the first perspective, the lack of explicit regard for the constraints of the product lifecycle management (PLM) architecture, which governs the interaction of processes and IT in PD, has been identified to negatively affect the utilization of KBE in PD processes. In the second perspective, KM theories and models can complement existing methods for identifying potential for KBE applications.Regarding the first perspective, it is concluded that explicit regard for the PLM architecture decreases the need to develop and maintain software code related to hard coded redundant data and functions in the KBE application. The concept of service oriented architecture (SOA) has been found to enable an the explicit regard for the PLM architecture.. Regarding the second perspective, it is concluded that potential for KBE applications is indicated by: 1.) application of certain types of knowledge in PD processes 2.) high maturity and formalization of the applied knowledge 3.) a codification strategy for KM and 4.) an agreement and transparency regarding how the knowledge is applied, captured and transferred. It is also concluded that the formulation of explicit KM strategies in PD should be guided by knowledge application and its relation to strategic objectives focusing on types of knowledge, their role in the PD process and the methods and tools for their application. These, in turn, affect the methods and tools deployed for knowledge capture in order for it to integrate with the processes of knowledge origin. Finally, roles and processes for knowledge transfer have to be transparent to assure the motivation of individuals to engage in the KM strategy

INDUSTRY 4.0 TECHNOLOGIES AND ORGANIZATIONAL DESIGN–EVIDENCE FROM 15 ITALIAN CASES

Current literature on Industry 4.0 technologies has mainly explored their relationship to the employment dynamics, or to the required competencies and emerging roles. This paper is complementing current literature with a perspective focused on organizational design. The aim of the paper is to explore how organizations are re-designed when Industry 4.0 technologies are implemented. The paper is based on 15 case studies carried out in Italian manufacturing companies and data was collected from 70 semi-structured interviews to relevant roles involved in the implementation of digital technologies. Results show that, when Industry 4.0 technologies are implemented, organizations are redesigned following an employee control-oriented or following an employee commitment-oriented organizational design. These results show that organizational design is the result of decisions, and is not determined by technology. The implications of our findings are presented and discussed