Structuring requirements as necessary premise for customer-oriented development of complex products: a generic approach

Purpose: Complex products like for example intra-logistical facilities make high demands on developers and producers and involve high investment and operating costs. When planning and developing and also making buying decisions the facility utilization and the thus ensuing requirements on the facility and its components are inadequately considered to date. Nevertheless, with regard to customer-directed product design, these requirements must all be taken into account – especially as they can contribute to possible savings. In this context, it is necessary to survey and systematically regard requirements from a large number of areas like for example the operator, the facility producer and also requirements of external parties such as the law and to implement into adequate product characteristics to produce customer-oriented products. This is, however, a difficult task because of the diversity of stakeholders involved and their numerous and often divergent requirements. Therefore, it is essential to structure the requirements, so that planners and developers are able to manage the large amount of information. Structure models can be used in this context to cluster requirements. Within the German Collaborative Research Centre 696 a 10-dimensional model has been developed. This model allows structuring of all requirements on intra-logistical facilities or respectively complex products in general. In the context of dealing with hundreds of data records, structuring requirements is mandatory to achieve accuracy, clarity and consequently satisfactory results when transforming requirements into product characteristics which fit customer needs. In the paper an excerpt of this model is presented. Design/methodology/approach: In literature a multitude of methods which deal with the topic of structuring exist. The methods have been analysed regarding their purpose and their level of specification, i.e. the number of differentiated categories, to check if they could be applied in the regarded area of intra-logistics. Also potential stakeholders have been identified to ensure that the surveying of requirements is not incomplete. Based on these analyses an own model has been developed which combines, adepts and enlarges the existing methods. Findings: A 10-dimensional model has been developed for structuring requirements on intra-logistical facilities. This model is holistic, because additionally it allows capturing the stakeholders’ feedback to the requirements’ fulfilment. The dimensions of the model can be divided into four groups. The first one serves to structure the requirements regarding their content. These are the dimensions obligations, surroundings, information, qualification, technical-functional requirements and qualification. The second group serves to structure the reference object to which the requirements refer and includes the dimension product. Weighted level of performance and customer satisfaction are part of the third group, which encompasses the evaluation of the requirements’ fulfilment. The fourth group is for the temporal structuring of requirements and includes the dimension time. For applying the model it has been implemented for data processing as component of a large data processing system. The developed model is presented in this paper. Research limitations/implications: A 10-idimensional model for structuring requirements is presented in this paper. Thereby, a sub-division of the dimensions into categories and sub-categories has been made to ensure a topical classification of the requirements and additionally a structuring according to their level of specification. Considering individual dimensions and/or selected categories of dimensions allow a thematic focus to be placed on certain groups of requirements. This is particularly important, not only for the implementation of requirements into solutions but also for focusing on the needs of individual stakeholders, if e.g. requirements on maintenance have to be observed. Using the model, working with lots of requirements should be facilitated. Thereby, clustering and weighting of requirement should be advanced. Practical implications: For applying the model and handling the great amount of requirements, the model has been implemented for data processing. This allows the stakeholder to easily sort the requirements into the model. Thereby, the system offers many assistance functions which should facilitate the matching for example matching of the same requirement by other stakeholders can be shown or matching of similar requirements. Originality/value: In contrast to the existing structuring methods the developed model is holistic and generic. It allows to capture the stakeholders’ feedback to the requirements fulfilment and hence a comparison between nominal and actual condition. Moreover, it can be applied not only the area of intra-logistics, for which it has been originally developed, but to complex products in general. Even if an adaption of the dimensions’ categories might be necessary.Peer Reviewe

Developing Design Methods - A Conceptual Requirement Framework

Design methods can provide valuable support in structuring and solving complex product design problems. However, the application and the transfer of methods from academia to industry is limited. To date, research has tended to focus on solving this through improved method selection, method adaptation and training. The development of design methods itself has attracted surprisingly low attention. This paper closes this gap and adds a quite new perspective of systematic requirement management of method development. However, the variety of methods, method users and application contexts is a key challenge and does not allow for a universal set of requirements. Thus, this paper transfers the concept of solution-neutral requirements frameworks, which are established in product design, to method development. The framework is derived from analysing and structuring different requirements found in literature. Different requirement sub-/categories allow for accommodating the varying levels of detail of requirements. The framework works like a checklist and helps design researchers to consider the most important requirement categories, which subsequently can be detailed project-specifically

Cent CORE: Centralized Cloud Oriented Requirement Engineering Strategy for Tracking and Elicitation of Dynamic Requirements

Requirement Engineering is one of the most important stages of Software Engineering. Eliciting requirements is highly critical and a complex process as the software end product totally depends on the quality of requirements that were collected. The property of the requirements is dynamic that keeps changing and constantly evolving. The Traditional Strategies for Requirement Engineering lacked organization and change management was entirely manual which consumed a lot of time and skilled labor. A centralized strategy for Elicitation of Dynamic Requirements using the concept of Requirement Cloud is proposed with high level of organization and structuring. A novel idea of using Cloud Storage Service for Requirement Engineering is implemented using a heuristics approach. Change management is incorporated and a few activities like requirements document generation is automated in this approach. Finally a survey between the Traditional Requirement Engineering and Proposed Cloud Methodology is conducted to prove the proposed methodology is better than the traditional strategies of Requirement Engineering

Modeling the Structure and Complexity of Engineering Routine Design Problems

This paper proposes a model to structure routine design problems as well as a model of its design complexity. The idea is that having a proper model of the structure of such problems enables understanding its complexity, and likewise, a proper understanding of its complexity enables the development of systematic approaches to solve them. The end goal is to develop computer systems capable of taking over routine design tasks based on generic and systematic solving approaches. It is proposed to structure routine design in three main states: problem class, problem instance, and problem solution. Design complexity is related to the degree of uncertainty in knowing how to move a design problem from one state to another. Axiomatic Design Theory is used as reference for understanding complexity in routine design

Structuring visual exploratory analysis of skill demand

The analysis of increasingly large and diverse data for meaningful interpretation and question answering is handicapped by human cognitive limitations. Consequently, semi-automatic abstraction of complex data within structured information spaces becomes increasingly important, if its knowledge content is to support intuitive, exploratory discovery. Exploration of skill demand is an area where regularly updated, multi-dimensional data may be exploited to assess capability within the workforce to manage the demands of the modern, technology- and data-driven economy. The knowledge derived may be employed by skilled practitioners in defining career pathways, to identify where, when and how to update their skillsets in line with advancing technology and changing work demands. This same knowledge may also be used to identify the combination of skills essential in recruiting for new roles. To address the challenges inherent in exploring the complex, heterogeneous, dynamic data that feeds into such applications, we investigate the use of an ontology to guide structuring of the information space, to allow individuals and institutions to interactively explore and interpret the dynamic skill demand landscape for their specific needs. As a test case we consider the relatively new and highly dynamic field of Data Science, where insightful, exploratory data analysis and knowledge discovery are critical. We employ context-driven and task-centred scenarios to explore our research questions and guide iterative design, development and formative evaluation of our ontology-driven, visual exploratory discovery and analysis approach, to measure where it adds value to users’ analytical activity. Our findings reinforce the potential in our approach, and point us to future paths to build on

Supporting 'design for reuse' with modular design

Engineering design reuse refers to the utilization of any knowledge gained from the design activity to support future design. As such, engineering design reuse approaches are concerned with the support, exploration, and enhancement of design knowledge prior, during, and after a design activity. Modular design is a product structuring principle whereby products are developed with distinct modules for rapid product development, efficient upgrades, and possible reuse (of the physical modules). The benefits of modular design center on a greater capacity for structuring component parts to better manage the relation between market requirements and the designed product. This study explores the capabilities of modular design principles to provide improved support for the engineering design reuse concept. The correlations between modular design and 'reuse' are highlighted, with the aim of identifying its potential to aid the little-supported process of design for reuse. In fulfilment of this objective the authors not only identify the requirements of design for reuse, but also propose how modular design principles can be extended to support design for reuse

A design model for Open Distributed Processing systems

This paper proposes design concepts that allow the conception, understanding and development of complex technical structures for open distributed systems. The proposed concepts are related to, and partially motivated by, the present work on Open Distributed Processing (ODP). As opposed to the current ODP approach, the concepts are aimed at supporting a design trajectory with several, related abstraction levels. Simple examples are used to illustrate the proposed concepts

A Framework to Manage the Complex Organisation of Collaborating: Its Application to Autonomous Systems

In this paper we present an analysis of the complexities of large group collaboration and its application to develop detailed requirements for collaboration schema for Autonomous Systems (AS). These requirements flow from our development of a framework for collaboration that provides a basis for designing, supporting and managing complex collaborative systems that can be applied and tested in various real world settings. We present the concepts of "collaborative flow" and "working as one" as descriptive expressions of what good collaborative teamwork can be in such scenarios. The paper considers the application of the framework within different scenarios and discuses the utility of the framework in modelling and supporting collaboration in complex organisational structures