Requirements Engineering for Product Service Systems - A State of the Art Analysis

In recent years, manufacturing companies and service providers have moved towards offering customer-specific problem solutions. These integrated bundles usually consist of hardware, software, and service components and are called product service systems (PSS) or hybrid products. Since the success of the resulting solution depends on the understanding of all requirements, requirements engineering (RE) has become a key factor. The article analyzes the state of the art of RE for PSS based on an extensive literature review in the domains of product-, software-, and service engineering. For this, criteria are derived from the characteristics of PSS and from the task area of RE in the life cycle of PSS. Based on these criteria we analyze the most established RE approaches for their suitability for PSS. An important finding is that integrated/interdisciplinary approaches for RE are missing. Moreover, the maturity of RE approaches in the three domains varies significantly. All analyzed approaches heavily rely on concepts and solution characteristics of their own domain so that a transfer to other domains is hardly possible. This literature review lays the foundation for successful RE for PSS and especially for future research aiming at combining and integrating RE approaches and models of product-, software-, and service engineering. Such requirement models could connect concepts of single domains and enable an integrated and seamless RE for PSS

Systems Engineering and Its Application to Industrial Product Development

PREFACE : Mastering the complexity of innovative systems currently looks a challenging goal of design and product development as well as embedding a suitable degree of smartness in devices, machines and equipment to make them able of adapting their operation to variable conditions or effects of a harsh environment. This goal is achieved through a continuous monitoring of the system in service, an effec-tive control of its behavior and a wide connectivity towards many other systems. Only an effective system design and manufacture, able to cover all the required actions, can assure this kind of assessment overall the life cycle since a very ear-ly concept of the product to a full disposal and service. Complexity makes hard managing the product development, because of the number of functions, subsystems, components and related interfaces usually in-volved, like in motor vehicles, robots, railways systems, aircrafts and spacecrafts as well as in large industrial manufacturing systems or very innovative microsys-tems and bioinspired devices. A crucial issue in this activity is performing a bright and complete elicitation of requirements, which need to be fully and suit-ably allocated to the system components, through a clear traceability, especially in systems produced as a result of material processing and assembling of parts. Moreover, the product must fit the requirements associated to some customer needs, innovation targets, and technical standards and be compatible with the manufacturer’s capabilities. As it looks clear from the current state–of–art, since several years the Systems Engineering assures a suitable answer to the needs above mentioned. It provides a methodology to drive the product lifecycle assessment that is implemented through a well defined process, being based on some specific and graphical lan-guages and even formalized in several tools enabling the required analyses, tak-ing advantage of the capabilities of some dedicated commercial software. Those contents lead to create a platform, consisting of a sort of tools chain, which might be used and shared among different industrial and professional partners to digitalize both the information and even the whole industrial product develop-ment, as far as the current strategy referred to as “Industry 4.0 / The Factory of the Future” brightly suggests and supports. The so–called Model Based Systems Engineering (MBSE) is then successfully proposing an effective and modern al-ternative to the document-based approach, using data models as a main element of the design process. Some technical standards already drive the user in imple-menting the Systems Engineering, thus leading to develop a systematic approach the design aimed at satisfying the customer needs. Suitable capabilities in the manufactured system are assured by the so–called architectural frameworks, which support the system development and integration. The Model Based Systems Engineering allows proceeding with a modeling activity which investigates requirements, behavior and architecture through a combined operational, functional and logical analysis, being linked and interop-erated with a mathematical and physical modeling, which is typically more known and widely used within the industrial engineering. A full integration of all the activities of the Product Lifecycle Management (PLM) is currently going on, to include the system architecture definition and its Application Lifecycle Man-agement (ALM) as well as the Product Data Management (PDM), i.e. the design activity together with the tasks of production, testing, homologation and service. A recognized standard certification to qualify the Systems Engineer is even available as the International Council on Systems Engineering (INCOSE) pro-vides. The scenario above described is strongly integrated with the increasing devel-opment of both the network and the cyber–physical systems, for a fully distribut-ed connectivity, to be exploited in advanced smart systems and devices as well as in intelligent manufacturing, according to the most recent strategies of innova-tion as the “Industry 4.0” initiative and the “Lean manufacturing” idea. Simulta-neously, the system smartness and connectivity together increase the demand of data transmission and elaboration, thus linking this topic to the technology of big data management, whilst they benefit of the progress in information technology, through a secure cloud based on the network. The context just described motivates the fast diffusion of the Model Based Systems Engineering as a tool for innovating all the production processes. The increasing demand of specialized software and of educational activities as well as the number of workshops and conferences focused on this topic confirm this trend. However, it might be remarked that several contributions to the literature about the Systems Engineering widely grew up during the last years, thus making the Reader sometimes confused, especially when approaching this topic at first. The Systems Engineering topics are so many that it looks rather difficult mas-tering its skills, without a preliminary classification of contents. Technical do-mains involved are mainly those of engineering and computer science, although many other ones play the role of a daily user of this methodology. According to the most recent development of the Systems Engineering, whose typical applica-tion fields were the software and electronic systems even for space missions, the current focus consists of several industrial systems, being gradually innovated by introducing the tailored solutions of mechatronics. It is worthy noticing that a significant advancement was introduced between the very early implementation of the Systems Engineering and its recent evolution, since several new applica-tions are focused on the production of systems, which need to be manufactured through a material processing. Usually, they exhibit some attributes related both to their physical nature and to the functions performed, thus requiring to model both their functional and physical behaviors together. This need is changing the scenario of the typical applications of the Systems Engineering as software de-sign. This handbook expressively avoids to cover all the typical contents of the spe-cialized literature of the Model Based Systems Engineering, whilst is aimed at making easier a first approach to this topic and sharing a preliminary experience performed by the authors within some industrial domains, by proceeding in the modeling activity in a real industrial environment. The main goal is drawing a sort of simple and hopefully clear roadmap in modeling and developing the in-dustrial and material systems and in implementing the Systems Engineering, par-ticularly in the design activity. Therefore, the target audience of this handbook includes professional engineers, scientists and students dealing with the Applica-tion Lifecycle Management and the system architecture assessment, more than the Product Data Management or the whole Product Lifecycle Management. The approach followed is that of introducing some examples of implementa-tion of the Systems Engineering, by proceeding step by step from the screening of needs and the elicitation of requirements till a synthesis of the system design. Each action will be referred to the literature, related to the implementation of the Systems Modeling Language or SysML and to the use of some tools available on market, thus highlighting benefits, drawbacks and current limitations of some dedicated software or even of some proposed methodologies. Several comments will be provided to describe the troubles shared among some users of the Sys-tems Engineering as they were detected in daily practice by the authors. They wish that this handbook could briefly and gradually provide the Reader with a preliminary guideline to approach professionally the Model Based Systems En-gineering, by understanding its main contents and applying it to the industrial environment. As a desired result, this work might be considered as an integration of some textbooks of Machine Design, and it is aimed at completing the education within Engineering Design or at simply providing a friendly introduction to the Systems Engineerin

Quality model for semantic IS standards

Semantic IS (Information Systems) standards are essential for achieving\ud interoperability between organizations. However a recent survey suggests that\ud not the full benefits of standards are achieved, due to the quality issues. This\ud paper presents a quality model for semantic IS standards, that should support\ud standards development organizations in assessing the quality of their\ud standards. Although intended for semantic IS standards the potential use of\ud this quality model is much broader and might be applicable to all kind of\ud standards

An Analysis of Service Ontologies

Services are increasingly shaping the world’s economic activity. Service provision and consumption have been profiting from advances in ICT, but the decentralization and heterogeneity of the involved service entities still pose engineering challenges. One of these challenges is to achieve semantic interoperability among these autonomous entities. Semantic web technology aims at addressing this challenge on a large scale, and has matured over the last years. This is evident from the various efforts reported in the literature in which service knowledge is represented in terms of ontologies developed either in individual research projects or in standardization bodies. This paper aims at analyzing the most relevant service ontologies available today for their suitability to cope with the service semantic interoperability challenge. We take the vision of the Internet of Services (IoS) as our motivation to identify the requirements for service ontologies. We adopt a formal approach to ontology design and evaluation in our analysis. We start by defining informal competency questions derived from a motivating scenario, and we identify relevant concepts and properties in service ontologies that match the formal ontological representation of these questions. We analyze the service ontologies with our concepts and questions, so that each ontology is positioned and evaluated according to its utility. The gaps we identify as the result of our analysis provide an indication of open challenges and future work

Boston University Bulletin. School of Management; Graduate Programs, 1980-1981

Each year Boston University publishes a bulletin for all undergraduate programs and separate bulletins for each School and College, Summer Term, and Overseas Programs. Requests for the undergraduat e bulle tin should be addressed to the Admissions Office and those for other bulletins to the individual School or College. This bulletin contains current information regarding the calendar, admissions, degree requirements, fees, regulations, and course offerings. The policy of the University is to give advance notice of change, when ever possible, to permit adjustment. The University reserves the right in its sole judgment to make changes of any nature in its program, calendar, or academic schedule whenever it is deemed necessary or desirable, including changes in course content, the rescheduling of classes with or without extending the academic term, canceling of scheduled classes and other academic activities, and requiring or affording alternatives for schedul ed classes or other academic activities, in any such case giving such notice thereof as is reasonably practicable under the circumstances. Boston University Bulletins (USPS 061-540) are published twenty times a year: one in January, one in March, four in May, four in June, six in July, one in August, and three in September

Tracing the Scenarios in Scenario-Based Product Design: a study to support scenario generation

Scenario-based design originates from the human-computer interaction and\ud software engineering disciplines, and continues to be adapted for product development. Product development differs from software development in the former’s more varied context of use, broader characteristics of users and more tangible solutions. The possible use of scenarios in product design is therefore broader and more challenging. Existing design methods that involve scenarios can be employed in many different stages of the product design process. However, there is no proficient overview that discusses a\ud scenario-based product design process in its full extent. The purposes of creating scenarios and the evolution of scenarios from their original design data are often not obvious, although the results from using scenarios are clearly visible. Therefore, this paper proposes to classify possible scenario uses with their purpose, characteristics and supporting design methods. The classification makes explicit different types of scenarios and their relation to one another. Furthermore, novel scenario uses can be referred or added to the classification to develop it in parallel with the scenario-based design\ud practice. Eventually, a scenario-based product design process could take inspiration for creating scenarios from the classification because it provides detailed characteristics of the scenario