Service Computing System Engineering Life Cycle

The development of service computing technology has triggered the need for organizations to build a service computing system. This system is able to deliver IT services that can meet the challenges and needs of business services. An understanding of the service computing systems engineering life cycle is necessary to model and build the systems. This paper conducts the study of the service computing systems concepts and proposes the life cycle of service computing system engineering. First, some publications relevant to the service computing systems are reviewed systematically in order to develop fundamental concepts and elements of the systems. Second, a metamodel of service computing systems is built based on those concepts. Third, the life cycle model of service computing systems engineering is proposed based on the metamodel. Finally, the verification of the life cycle is conducted by comparing the proposed life cycle to the life cycle of software engineering, service engineering, and service system engineering. The contribution of this paper is to provide a coincise understanding of the components that are needed to build such systems and show the interaction and collaboration between the components in the service computing systems

Failure Modes and Effects Analysis (FMEA) in maintenance and diagnostics

Failure Modes and Effects Analysis (FMEA) is a tool that has long been used at various stages of the product life cycle but is most commonly used in the engineering design and manufacturing planning stages. Some work has been done on conceptual design stages but very little, if any, research has been conducted to understand how FMEA might be used during the service of the product. Furthermore, the feedback of performance knowledge (in the form of FMEA data) from the in-service product use to conceptual and engineering design is a potentially valuable but un-exploited activity. This can be seen as a possible method of implementing Design for Service. Diagnostic service tools (manuals, computer diagnostics, etc) are usually created as a post-production activity, but reuse of FMEA knowledge generated during design could be used in a concurrent activity. Additional benefits are gained from improved accuracy of the FMEA and the maintenance of up-to-date product knowledge. A system for computerised interactive FMEA generation from FMEA elements has been created from the research. An object-oriented FMEA model has been adopted and expanded to generate the FMEA elements and diagnostic FMEA. The use of an object-oriented FMEA environment and FMEA object libraries promotes the reuse of existing information and has increased data availability for the diagnostic tool development. The Diagnostic Service Tool (DST) is an extended application from the automated FMEA generation. Existing failure mode data is used to determine further characteristics of parts failure. As a result, a tool in the form of diagnostic software is created which is practical for real life use. The prototype software was evaluated in a field service application using four automatic transmission problem cases. The results showed that there was significant difference in repair times between the conventional repair manuals and DST. The research has demonstrated that the prototype software is successful in providing effective field service centered tools to the Field Service and in turn a method of providing feedback to the Designer. Hence, knowledge sharing between Engineering and Field Service can be carried out continuously to provide a significant improvement in product development

Law and the software development life cycle

The increasing demand of reliable software services and the dependability that our daily personal and professional life have on them is bringing significant changes in the domain of software service engineering. One of the most revolutionary is the introduction of regulations, repeating what in the past has concerned the product market. Regulations need to find a balance between the interests of several roles and reduce the inevitable tensions that would otherwise arise among them, as well as to defend the right of the weakest parties (normally the end users). There are multiple interests to balance: the interests of end users, the protection of intellectual property, a fair competition against other enterprises, just to name a few. While some of these requirements concern the structure and organization of the enterprise, some of them are fit to penetrate into the software development life cycle. This would serve multiple purposes: allow the enterprise to design services which already take the legal requirements into account; visually represent the requirements and their interaction with the functionality of the system; develop the software components using tools and methodologies that are able to deal with those requirements; define metrics to measure the degree to which such requirements are met; measure the impact of the requirements on the functionality of the service and on other parameters of the service (such as performance or storage occupation); verify and monitor whether the legal requirements are met; and, last but not least, to have an argument to be used in case of a complaint in a court or at a competent authority. Before being considered in the software service life cycle, legal requirements must undergo a preprocessing phase in which they are translated into some form which is compatible with the tools and methodologies proper of the software engineering, for instance being modelled into a formalism that makes them processable by a machine. There is a significant amount of interdisciplinary topics that need to be combined together to reach an integration between regulation and software life cycle. In particular, at least from three complementary perspectives are needed. One perspective requires the analysis of the provisions of the law, the extraction of the legal requirements classified according to the stakeholders affected, and the translation of those requirements into some formal model that can be processed using appropriate software tools. A second perspective requires a study of the legal requirements from the point of view of requirements engineering techniques, also defining metrics to measure them. The third concerns the models used in the various stages of software engineering (design, modeling, development, validation and testing), which need to be extended to accommodate the legal requirements in their formal representation. Only by putting together these perspectives a comprehensive approach to deal with legal requirements in software engineering is possible

RANCANG BANGUN SISTEM INFORMASI PREVENTIVE MAINTENANCE BERBASIS WEB PADA PERUSAHAAN MANUFAKTUR

In order to improve the best service for its customers, PT Multi Engineering Perkasa sends a maintenance team and implements a preventive maintenance system on each machine distributed to their customers during the warranty period. Problems faced by maintenance such as delays in determining production machine repair schedules, machine repair job checklist data collection, and insufficient information facilities needed by PT Multi Engineering Perkasa regarding history of damage or checking on production machines which are still done manually, using hardcopy. This research uses the Waterfall model of Software Development Life Cycle (SDLC) development method. The waterfall model has five stages, namely analysis, design, coding, testing and maintenance. This application is created using the programming language PHP, HTML and MySQL as a database. And as a result, the web-based preventive maintenance information system can help maintenance in carrying out preventive maintenance data, especially helping in terms of information so that it can be used as a decision-making material, as well as on the part of the customer can quickly see the repair / preventive maintenance report data when needed

Automotive embedded systems software reprogramming

This thesis was submitted for the degree of Doctor of Philosophy and was awarded by Brunel UniversityThe exponential growth of computer power is no longer limited to stand alone computing systems but applies to all areas of commercial embedded computing systems. The ongoing rapid growth in intelligent embedded systems is visible in the commercial automotive area, where a modern car today implements up to 80 different electronic control units (ECUs) and their total memory size has been increased to several hundreds of megabyte. This growth in the commercial mass production world has led to new challenges, even within the automotive industry but also in other business areas where cost pressure is high. The need to drive cost down means that every cent spent on recurring engineering costs needs to be justified. A conflict between functional requirements (functionality, system reliability, production and manufacturing aspects etc.), testing and maintainability aspects is given. Software reprogramming, as a key issue within the automotive industry, solve that given conflict partly in the past. Software Reprogramming for in-field service and maintenance in the after sales markets provides a strong method to fix previously not identified software errors. But the increasing software sizes and therefore the increasing software reprogramming times will reduce the benefits. Especially if ECU’s software size growth faster than vehicle’s onboard infrastructure can be adjusted. The thesis result enables cost prediction of embedded systems’ software reprogramming by generating an effective and reliable model for reprogramming time for different existing and new technologies. This model and additional research results contribute to a timeline for short term, mid term and long term solutions which will solve the currently given problems as well as future challenges, especially for the automotive industry but also for all other business areas where cost pressure is high and software reprogramming is a key issue during products life cycle

Aligning a Service Provisioning Model of a Service-Oriented System with the ITIL v.3 Life Cycle

Bringing together the ICT and the business layer of a service-oriented system (SoS) remains a great challenge. Few papers tackle the management of SoS from the business and organizational point of view. One solution is to use the well-known ITIL v.3 framework. The latter enables to transform the organization into a service-oriented organizational which focuses on the value provided to the service customers. In this paper, we align the steps of the service provisioning model with the ITIL v.3 processes. The alignment proposed should help organizations and IT teams to integrate their ICT layer, represented by the SoS, and their business layer, represented by ITIL v.3. One main advantage of this combined use of ITIL and a SoS is the full service orientation of the company.Comment: This document is the technical work of a conference paper submitted to the International Conference on Exploring Service Science 1.5 (IESS 2015

A quality management based on the Quality Model life cycle

Managing quality is a hard and expensive task that involves the execution and control of processes and techniques. For a good quality management, it is important to know the current state and the objective to be achieved. It is essential to take into account with a Quality Model that specifies the purposes of managing quality. QuEF (Quality Evaluation Framework) is a framework to manage quality in MDWE (Model-driven Web Engineering). This paper suggests managing quality but pointing out the Quality Model life cycle. The purpose is to converge toward a quality continuous improvement by means of reducing effort and time.Ministerio de Ciencia e Innovación TIN2010-20057-C03-02Ministerio de Ciencia e Innovación TIN 2010-12312-EJunta de Andalucía TIC-578

A taxonomy of asymmetric requirements aspects

The early aspects community has received increasing attention among researchers and practitioners, and has grown a set of meaningful terminology and concepts in recent years, including the notion of requirements aspects. Aspects at the requirements level present stakeholder concerns that crosscut the problem domain, with the potential for a broad impact on questions of scoping, prioritization, and architectural design. Although many existing requirements engineering approaches advocate and advertise an integral support of early aspects analysis, one challenge is that the notion of a requirements aspect is not yet well established to efficaciously serve the community. Instead of defining the term once and for all in a normally arduous and unproductive conceptual unification stage, we present a preliminary taxonomy based on the literature survey to show the different features of an asymmetric requirements aspect. Existing approaches that handle requirements aspects are compared and classified according to the proposed taxonomy. In addition,we study crosscutting security requirements to exemplify the taxonomy's use, substantiate its value, and explore its future directions

Value-Based Business-IT Alignment in Networked Constellations of Enterprises

Business-ICT alignment is the problem of matching ICTservices with the requirements of the business. In businesses of any significant size, business-ICT alignment is a hard problem, which is currently not solved completely. With the advent of networked constellations of enterprises, the problem gets a new dimension, because in such a network, there is not a single point of authority for making decisions about ICT support to solve conflicts in requirements these various enterprises may have. Network constellations exist when different businesses decide to cooperate by means of ICT networks, but they also exist in large corporations, which often consist of nearly independent business units, and thus have no single point of authority anymore. In this position paper we discuss the need for several solution techniques to address the problem of business-ICT alignment in networked constellations. Such techniques include: -RE techniques to describe networked value constellations requesting and offering ICT services as economic value. These techniques should allow reasoning about the matching of business needs with available ICT services in the constellation. - RE techniques to design a networked ICT architecture that supports ICT services required by the business, taking the value offered by those services, and the costs incurred by the architecture, into account. - Models of decision processes about ICT services and their architecture, and maturity models of those processes.The techniques and methods will be developed and validated using case studies and action research

Performance Feedback A Common Thread in the Process to Provide Optimal Heart Failure Care⁎⁎Editorials published in the Journal of the American College of Cardiology reflect the views of the authors and do not necessarily represent the views of JACC or the American College of Cardiology.

Current software community players like academy and industry have been changing the traditional paradigms of software engineering towards context-awareness and distributed computing. Nowadays, service-oriented computing and context-aware computing are two emerging paradigms that are changing the way of designing, developing, providing and consuming software services. Whilst service-oriented computing is based on service-oriented architectures and it is focused on modelling functionality and providing flexible software services, context-aware computing is based on the context life cycle and it allows processing and changing the behaviour of such services given certain context information. The synergy between both paradigms is a core research topic in ubiquitous and pervasive computing widely applied to the Internet of Things and Smart Cities.In the present PhD thesis, we exploit this synergy by focusing on context-aware computing from the perspective of service-oriented computing, which is also known as context-aware service-oriented computing. Such research topic involves the management of context within different essential phases of the context life cycle that show how the context data moves from phase to phase in software services within the paradigm of the service-oriented computing. Hence, the work done in this thesis involves different components and processes that have the aim to accomplish the context life cycle, namely the acquisition, modelling, reasoning and dissemination of the context in service-oriented computing. Particularly, we make an effort to provide both a context ontology for context modelling, context reasoning and high-level context dissemination, and a context-aware monitoring architecture for context acquisition and low-level context dissemination.Such work of the thesis has been motivated for contributing in the solution of different issues mainly identified in the phases of context modelling and context acquisition that are a strong basis of the context life cycle. Firstly, in the context modelling we mainly identified the proliferation of several context models presenting some problems about: reusability, extensibility and adaptation. Secondly, in the context acquisition we mainly identified that existing monitoring infrastructures are not prepared to support the constant changes in their context and the context of other entities, including the services that they are supervising which provoke the provisioning of context data that is not reliable. In summary, this thesis explores three big research questions: 1) What context data to acquire and to model? This involves the study of the current state of the art of context models, specifically: which are these proposals and how are they related, what are their structural characteristics, what context information is the most addressed, and what are their most consolidated definitions. 2) How to model context data? This involves the development of a three-level context ontology with the aim of improving the reusability, extensibility and adaptation capabilities of existing context models. 3) How to acquire context data? This involves the development of a context-aware monitoring architecture that can be easily configured, adapted or evolved according to the constant changes of the context.The context model and the architecture proposed in this PhD thesis are validated through different scenarios and use cases, highlighting their integration in SUPERSEDE (www.supersede.eu), a European project in the H2020 program for fulfilling some requirements of data acquisition and management demonstrating that the context life cycle is supported.Els actors actuals de la comunitat de software, com l'acadèmia o la indústria, han anat canviant els paradigmes tradicionals de l'enginyeria de software cap a la sensibilitat al context i la computació distribuïda. Avui dia, la computació orientada a serveis i la computació conscient del context són dos paradigmes emergents que estan canviant la forma de dissenyar, desenvolupar, proporcionar i consumir serveis de software. Mentre que la computació orientada a serveis es basa en arquitectures orientades a serveis i se centra en el modelatge de la funcionalitat i la prestació de serveis de software flexibles, la computació sensible al context es basa en el cicle de vida del context i permet el processament i canviar el comportament d'aquest tipus de serveis donada una determinada informació del context. La sinergia entre els dos paradigmes és un tema central de recerca a la computació ubiqua i omnipresent, àmpliament aplicada a la Internet de les coses i les ciutats intel·ligents. En la present tesi doctoral explotem aquesta sinèrgia, centrant-se en la computació sensible al context des de la perspectiva de la computació orientada a serveis, que també es coneix com computació orientada a serveis sensibles al context. Tal tema de recerca implica la gestió de contexts en diferents fases essencials del cicle de vida del context que mostren com les dades de context es mouen d'una fase a l’altra en serveis de software dins del paradigma de la computació orientada a serveis. Per tant, el treball realitzat en aquesta tesi consisteix en diferents components i processos que tenen l'objectiu d'aconseguir el cicle de vida del context, és a dir, l'adquisició, el modelatge, el raonament i la difusió del context en computació orientada a serveis. En particular, fem un esforç per proporcionar tant una ontologia de context per a la modelització, raonament i difusió del context d'alt nivell, i una arquitectura de monitorització sensible al context per a l'adquisició i difusió del context de baix nivell. Aquest treball de tesi ha estat motivat per contribuir a la solució dels diferents problemes identificats principalment en les fases de modelatge de context i adquisició de context que són una base sòlida del cicle de vida del context. En primer lloc, en el modelatge de context es van identificar principalment la proliferació de diversos models de context que presenten alguns problemes sobre: reutilització, l'extensibilitat i l'adaptació. En segon lloc, en l'adquisició del context identifiquem principalment que les infraestructures de monitorització existents no estan preparats per suportar els canvis constants en el seu context i el context d'altres entitats, incloent-hi els serveis que s'estan supervisant, que provoquen un aprovisionament de dades de context que no és fiable. En resum, aquesta tesi explora tres grans preguntes de recerca: 1) Quines dades de context cal adquirir i modelar? Això implica l'estudi de l'estat actual de la tècnica dels models de context, en concret: ¿quines són aquestes propostes i com es relacionen, quines són les seves característiques estructurals, quina informació de context és la més adreçada, i quines són les seves definicions més consolidades. 2) Com modelar les dades de context? Això implica el desenvolupament d'una ontologia de context de tres nivells amb l'objectiu de millorar les capacitats de reutilització, extensibilitat i adaptació dels models de context existents. 3) Com adquirir dades de context? Això implica el desenvolupament d'una arquitectura de monitorització sensible al context que pot ser fàcilment configurat o adaptat d'acord amb els canvis del context. El model de context i l'arquitectura proposada en aquesta tesi doctoral es validen a través de diferents escenaris i casos d'ús, destacant la seva integració en SUPERSEDE, un projecte europeu en el programa H2020 per al compliment d'alguns requisits d'adquisició i gestió de dades que demostra que es dóna suport al cicle de vida del context