Summary form only given. This poster presents an experience, on gathering business needs in business models adapted to the business expert language and translating these needs into a service oriented architecture (SOA) in a systematic way. The poster introduces the current situation highlighting three interoperability problems: (1) Organisations do not use a standard, unified and widely adopted business process definition language. Organisations want a common understanding of the process where they are involved from different perspectives; (2) Information systems are implemented to address specific requirements, ignoring future integration needs by using proprietary formats, and ad-hoc communication strategies and protocols; and (3) Information systems do not, clearly, support the business processes. There is a gap between business process models and their information systems implementations. The approach shown in this poster is based on the usage of the SOA paradigm from a model driven point of view: a model driven service oriented architecture (MDSOA) framework. Based on the MDA specification we have identified a metamodel for each of the three abstraction levels: (1) POP* (process, organisation, product) is selected as the metamodel to represent and exchange business processes. POP* is the unified enterprise modelling language (UEML) successor. POP* metamodel represents the starting point; (2) PIM4SOA (platform independent model for service oriented architecture) (Benguria et al., 2006) is a metamodel to represent service, process, information and quality of service elements; and (3) WSDL (Web service description language) and BPEL (business process execution language) are platform specific languages
Over the last few years, DevOps methodologies have promoted a more streamlined operationalization of software components in production environments. Infrastructure as Code (IaC) technologies play a key role in the lifecycle management of applications, as they promote the delivery of the infrastructural elements alongside the application components. This way, IaC technologies aspire to minimize the problems associated with the environment by providing a repeatable and traceable process. However, there are a large variety of IaC frameworks, each of them focusing on a different phase of the operationalization lifecycle, hence the necessity to master numerous technologies. In this research, we present the IaC Execution Manager (IEM), a tool devoted to providing a unified framework for the operationalization of software components that encompasses the various stages and technologies involved in the application lifecycle. We analyze an industrial use case to improve the current approach and conclude the IEM is a suitable tool for solving the problem as it promotes automation, while reducing the learning curve associated with the required IaC technologies.
In the last years, one of the fields of artificial intelligence that has been investigated the most is nature-inspired computing. The research done on this specific topic showcases the interest that sparks in researchers and practitioners, who put their focus on this paradigm because of the adaptability and ability of nature-inspired algorithms to reach high-quality outcomes on a wide range of problems. In fact, this kind of methods has been successfully applied to solve real-world problems in heterogeneous fields such as medicine, transportation, industry, or software engineering. Our main objective with this paper is to describe a tool based on nature-inspired computing for solving a specific software engineering problem. The problem faced consists of optimizing Infrastructure as Code deployment configurations. For this reason, the name of the system is IaC Optimizer Platform. A prototypical version of the IOP was described in previous works, in which the functionality of this platform was introduced. With this paper, we take a step forward by describing the final release of the IOP, highlighting its main contribution regarding the current state-of-the-art, and justifying the decisions made on its implementation. Also, we contextualize the IOP within the complete platform in which it is embedded, describing how a user can benefit from its use. To do that, we also present and solve a real-world use case.