Data and process requirements for product recall coordination

When an organisation becomes aware that one of its products may pose a safety risk to customers, it must take appropriate action as soon as possible or it can be held liable. The ability to automatically trace potentially dangerous goods through the supply chain would thus help organisations fulfil their legal obligations in a timely and effective manner. Furthermore, product recall legislation requires manufacturers to separately notify various government agencies, the health department and the public about recall incidents. This duplication of effort and paperwork can introduce errors and data inconsistencies. In this paper, we examine traceability and notification requirements in the product recall domain from two perspectives: the activities carried out during the manufacturing and recall processes and the data collected during the enactment of these processes. We then propose a workflow-based coordination framework to support these data and process requirements.     

A computational framework for authoring and searching product design specifications

The development of product design specifications (PDS) is an important part of the product development process. Incompleteness, ambiguity, or inconsistency in the PDS can lead to problems during the design process and may require unnecessary design iterations. This generally results in increased design time and cost. Currently, in many organizations, PDS are written using word processors. Since documents written by different authors can be inconsistent in style and word choice, it is difficult to automatically search for specific requirements. Moreover, this approach does not allow the possibility of automated design verification and validation against the design requirements and specifications.In this paper, we present a computational framework and a software tool based on this framework for writing, annotating, and searching computer-interpretable PDS. Our approach allows authors to write requirement statements in natural language to be consistent with the existing authoring practice. However, using mathematical expressions, keywords from predefined taxonomies, and other metadata the author of PDS can then annotate different parts of the requirement statements. This approach provides unambiguous meaning to the information contained in PDS, and helps to eliminate mistakes later in the process when designers must interpret requirements. Our approach also enables users to construct a new PDS document from the results of the search for requirements of similar devices and in similar contexts. This capability speeds up the process of creating PDS and helps authors write more detailed documents by utilizing previous, well written PDS documents. Our approach also enables checking for internal inconsistencies in the requirement statements.     

The agile requirements refinery: Applying SCRUM principles to software product management

Context

Although agile software development methods such as SCRUM and DSDM are gaining popularity, the consequences of applying agile principles to software product management have received little attention until now.

Objective

In this paper, this gap is filled by the introduction of a method for the application of SCRUM principles to software product management.

Method

A case study research approach is employed to describe and evaluate this method.

Results

This has resulted in the ‘agile requirements refinery’, an extension to the SCRUM process that enables product managers to cope with complex requirements in an agile development environment. A case study is presented to illustrate how agile methods can be applied to software product management.

Conclusions

The experiences of the case study company are provided as a set of lessons learned that will help others to apply agile principles to their software product management process.     

An experiment on linguistic tool support for consolidation of requirements from multiple sources in market-driven product development

This paper presents an experiment with a linguistic support tool for consolidation of requirements sets. The experiment is designed based on the requirements management process at a large market-driven software development company that develops generic solutions to satisfy many different customers. New requirements and requests for information are continuously issued, which must be analyzed and responded to. The new requirements should first be consolidated with the old to avoid reanalysis of previously elicited requirements and to complement existing requirements with new information. In the presented experiment, a new open-source tool is evaluated in a laboratory setting. The tool uses linguistic engineering techniques to calculate similarities between requirements and presents a ranked list of suggested similar requirements, between which links may be assigned. It is hypothesized that the proposed technique for finding and linking similar requirements makes the consolidation more efficient. The results show that subjects that are given the support provided by the tool are significantly more efficient and more correct in consolidating two requirements sets, than are subjects that do not get the support. The results suggest that the proposed techniques may give valuable support and save time in an industrial requirements consolidation process.     

Software product line scoping and requirements engineering in a small and medium-sized enterprise: An industrial case study

Software product line (SPL) engineering has been applied in several domains, especially in large-scale software development. Given the benefits experienced and reported, SPL engineering has increasingly garnered interest from small to medium-sized companies. It is possible to find a wide range of studies reporting on the challenges of running a SPL project in large companies. However, very little reports exist that consider the situation for small to medium-sized enterprises and these studies try develop universal truths for SPL without lessons learned from empirical evidence need to be contextualized. This study is a step towards bridging this gap in contextual evidence by characterizing the weaknesses discovered in the scoping (SC) and requirements (RE) disciplines of SPL. Moreover, in this study we conducted a case study in a small to medium sized enterprises (SMEs) to justify the use of agile methods when introducing the SPL SC and RE disciplines through the characterization of their bottlenecks. The results of the characterization indicated that ineffective communication and collaboration, long iteration cycles, and the absence of adaptability and flexibility can increase the effort and reduce motivation during project development. These issues can be mitigated by agile methods.     

A spatiotemporal information management framework for product design and assembly process planning reconciliation

This paper introduces an innovative framework for product design and assembly process planning reconciliation. Nowadays, both product lifecycle phases are quasi concurrently performed in industry and this configuration has led to competitive gains in efficiency and flexibility by improving designers’ awareness and product quality. Despite these efforts, some limitations/barriers are still encountered regarding the lack of dynamical representation, information consistency and information flow continuity. It is due to the inherent nature of the information created and managed in both phases and the lack of interoperability between the related information systems. Product design and assembly process planning phases actually generate heterogeneous information, since the first one describes all information related to “what to be delivered” and the latter rationalises all information with regards to “how to be assembled”. In other words, the integration of assembly planning issue in product design requires reconciliation means with appropriate relationships of the architectural product definition in space with its assembly sequence in terms of time. Therefore, the main objective is to provide a spatiotemporal information management framework based on a strong semantic and logical foundation in product lifecycle management (PLM) systems, increasing therefore actors’ awareness, flexibility and efficiency with a better abstraction of the physical reality and appropriate information management procedures. A case study is presented to illustrate the relevance of the proposed framework and its hub-based implementation within PLM systems.     

An overlapping process model to assess schedule risk for new product development

Faster time-to-market for new products is important for hi-tech corporations to gain premium pricing and higher sales volume. An activity overlapping strategy is a frequently used technique in practice for quicker product launch. However, complex interaction patterns between components and activities increase the chance of unanticipated iterations that may lead to late time-to-market. This paper presents an overlapping process model to analyze the impact of process structure on the lead-time of a complex development project. Information evolution and change sensitivity, which are two major factors for activity overlapping, are considered in the proposed model and a simulation algorithm is developed to analyze the impacts of process structure on the development lead-time. The example of a battle tank simulator project is used to illustrate the proposed approach. The computational experiment shows that the proposed approach allows project managers to design a better process structure to minimize the risk of being late-to-market.     

Agile product line planning: A collaborative approach and a case study

Agile methods and product line engineering (PLE) have both proven successful in increasing customer satisfaction and decreasing time to market under certain conditions. Key characteristics of agile methods are lean and highly iterative development with a strong emphasis on stakeholder involvement. PLE leverages reuse through systematic approaches such as variability modeling or product derivation. Integrating agile approaches with product line engineering is an interesting proposition which – not surprisingly – entails several challenges: Product lines (PL) rely on complex plans and models to ensure their long-term evolution while agile methods emphasize simplicity and short-term value-creation for customers. When incorporating agility in product line engineering, it is thus essential to define carefully how agile principles can support particular PLE processes. For instance, the processes of defining and setting up a product line (domain engineering) and deriving products (application engineering) differ significantly in practices and focus with implications on the suitability of agile principles. This paper presents practical experiences of adopting agile principles in product line planning (a domain engineering activity). ThinkLets, i.e., collaborative practices from the area of collaboration engineering, are the building blocks of the presented approach as they codify agile principles such as stakeholder involvement, rapid feedback, or value-based prioritization. We discuss how our approach balances agility and the intrinsic needs of product line planning. A case study carried out with an industrial partner indicates that the approach is practicable, usable, and useful.     

Survey on mechatronic engineering: A focus on design methods and product models

According to the principles of concurrent engineering and integrated design, engineers intend to develop a mechatronic system with a high level integration (functional and physical integrations) based on a well-organised design method. As a result, two main categories of issues have been pointed out: the process-based problems and the design data-related problems. Several approaches to overcome these issues have been put forward. To solve process-based problems, a dynamic perspective is generally used to present how collaboration can be improved during the mechatronic design. For design data-related problems, solutions generally come from product models and how to structure and store the data thanks to the functionality of data and documents management of Product Lifecycle Management systems. To be able to assess design methods and product models, some criteria are proposed in the paper and used to evaluate their added value on integrated design of mechatronic system. After this assessment, main outcomes which focus on the combination of design method and product model for improving the design of mechatronic system are finally discussed.     

Data management of green product development with generic modularized product architecture

Many manufacturers are facing a complex situation in the mixed production environment, in which green and non-green products are fabricated simultaneously. They are losing competitiveness as a downstream supplier due to lacking of a cost-effective approach to managing product variations compliant with different green directives. This paper presents a methodology based on generic modularized product architecture that facilitates data management of green product development. The four-level architecture allows one unified representation for multiple product models. An option control mechanism enables a quick generation of their BOMs (bills of material). A procedure consisting of seven steps is proposed to accomplish this. PDM functions are implemented to demonstrate the effectiveness of the methodology using a real LCD TV family as an example. This work complements the past studies on green product development, which mainly tackled the problem from design, process, and supply chain improvement. In contrast, from a management perspective, the proposed methodology provides a simple but useful tool for small-to-medium-sized enterprises (SMEs) to perform green product development in an economical manner.     

Modeling workflow activities for collaborative process planning with product lifecycle management tools

Process planning activities are critical in manu- facturing distributed environments where different companies need to collaborate in product development. In this work, we propose a workflow model for a collaborative process planning environment in which original equipment manufacturer and suppliers companies interact with the help of Product Lifecycle Management and CAD/CAM tools. The proposed workflow model establishes the different activities, the information flows and the different stages that must be followed by all the participants. A pilot implementation has been made in order to validate the model in a realistic industrial scenario.     

Computer aided innovation—State of the art from a new product development perspective

In this paper we present the state of the art in the field of computer aided innovation (CAI) from a new product development (NPD) perspective. Based on a holistic understanding of the innovation process and its support by ICT, we provide an overview of the emerging issue of CAI in the NPD field. In particular, the latest research on the concept of CAI, its categorization, potential benefits of CAI, trends in the CAI supply, and issues of CAI usage and implementation are discussed and summarized in this article. Current publications indicate that the emerging field of CAI has recently been getting more attention in the NPD area, but this research needs to integrate further the insights from other research areas in the CAI field. It must also make a better distinction between generic ICT and CAI to achieve a more specific and holistic perspective on CAI in the future.     

Integrated product and process design: a multi-objective modeling framework

In this paper we present an analytical multi-objective framework for the concurrent design of product and processes. The objective is to simultaneously consider the tolerance specification on the product or the component dimensions along with the selection of the manufacturing processes. For this purpose we consider three objectives: to minimize unit cost, to minimize quality loss and to minimize manufacturing lead time. We characterize the properties of the non-dominated solutions. These solutions provide flexibility needed in an agile manufacturing environment. The min–max approach is used to obtain trade-off solutions.     

Product relationships management enabler for concurrent engineering and product lifecycle management

The current competitive industrial context requires more flexible, intelligent and compact product lifecycles, especially in the product development process where several lifecycle issues have to be considered, so as to deliver lifecycle oriented products. This paper describes the application of a novel product relationships management approach, in the context of product lifecycle management (PLM), enabling concurrent product design and assembly sequence planning. Previous work has provided a foundation through a theoretical framework, enhanced by the paradigm of product relational design and management. This statement therefore highlights the concurrent and proactive aspect of assembly oriented design vision. Central to this approach is the establishment and implementation of a complex and multiple viewpoints of product development addressing various stakeholders design and assembly planning points of view. By establishing such comprehensive relationships and identifying related relationships among several lifecycle phases, it is then possible to undertake the product design and assembly phases concurrently. Specifically, the proposed work and its application enable the management of product relationship information at the interface of product-process data management techniques. Based on the theory, models and techniques such as described in previous work, the implementation of a new hub application called PEGASUS is then described. Also based on web service technology, PEGASUS can be considered as a mediator application and/or an enabler for PLM that externalises product relationships and enables the control of information flow with internal regulation procedures. The feasibility of the approach is justified and the associated benefits are reported with a mechanical assembly as a case study.     

A measurement framework for assessing the maturity of requirements engineering process

Because requirements engineering (RE) problems are widely acknowledged as having a major impact on the effectiveness of the software development process, Sommerville et al. have developed a requirements maturity model. However, research has shown that the measurement process within Sommerville’s model is ambiguous, and implementation of his requirements maturity model leads to confusion. Hence, the objective of our research is to propose a new RE maturity measurement framework (REMMF) based on Sommerville’s model and to provide initial validation of REMMF. The main purpose of proposing REMMF is to allow us to more effectively measure the maturity of the RE processes being used within organisations and to assist practitioners in measuring the maturity of their RE processes. In order to evaluate REMMF, two organisations implemented the measurement framework within their IT divisions, provided us with an assessment of their requirements process and gave feedback on the REMMF measurement process. The results show that our measurement framework is clear, easy to use and provides an entry point through which the practitioners can effectively judge the strengths and weakness of their RE processes. When an organisation knows where it is, it can more effectively plan for improvement.

Development of a computer-based interviewing tool to enhance the requirements gathering process

Software design is an area where it is most important to elicit an accurate and complete set of requirements. Determining the users requirements and their qualitative satisfaction with a developing product are two major problems which arise, often due to the different backgrounds and perspectives of the different stakeholders, including the software engineer, the domain expert and the end-user. Involving users throughout the design and development process is an essential part of any project. Computer-based interviewing has been found to be a valuable tool in eliciting information, which can also enhance interpersonal communication afterwards. This paper discusses the development of a computer interviewing tool to facilitate the gathering of user requirements and conducting user evaluations.     

Analyzing evolution of variability in a software product line: From contexts and requirements to features

Context

In the long run, features of a software product line (SPL) evolve with respect to changes in stakeholder requirements and system contexts. Neither domain engineering nor requirements engineering handles such co-evolution of requirements and contexts explicitly, making it especially hard to reason about the impact of co-changes in complex scenarios.

Objective

In this paper, we propose a problem-oriented and value-based analysis method for variability evolution analysis. The method takes into account both kinds of changes (requirements and contexts) during the life of an evolving software product line.

Method

The proposed method extends the core requirements engineering ontology with the notions to represent variability-intensive problem decomposition and evolution. On the basis of problemorientation, the analysis method identifies candidate changes, detects influenced features, and evaluates their contributions to the value of the SPL.

Results and Conclusion

The process of applying the analysis method is illustrated using a concrete case study of an evolving enterprise software system, which has confirmed that tracing back to requirements and contextual changes is an effective way to understand the evolution of variability in the software product line.     

A methodology of developing product family architecture for mass customization

Mass customization, aiming at delivering an increasing product variety that best serves customer needs while keeping mass production efficiency, has recently received numerous attention and popularity in industry and academia alike. This paper presents a methodology of developing product family architecture (PFA) to rationalize product development for mass customization. Systematic steps are developed to formulate a PFA in terms of functional, technical and physical views. The diverse needs of customers are matched with the capabilities of a firm through systematic planning of modularity in three consecutive views. The development of a PFA provides a unifying integration platform to synchronize market positioning, commonality employment and manufacturing scale of economy across the entire product realization process. A case study in an electronics company is reported to illustrate the potential and the feasibility of PFA methodology.     

Linking business and requirements engineering: is solution planning a missing activity in software product companies?

A strong link between strategy and product development is important, since companies need to select requirements for forthcoming releases. However, in practice, connecting requirements engineering (RE) and business planning is far from trivial. This paper describes the lessons learned from four software product companies that have recognized the need for more business-oriented long-term planning. The study was conducted using the action research approach. We identified five practices that seem to strengthen the link between business decisions and RE. These are (1) explicating the planning levels and time horizons; (2) separating the planning of products’ business goals from R&D resource allocation; (3) planning open-endedly with a pre-defined rhythm; (4) emphasizing whole-product thinking; and (5) making solution planning visible. To support whole-product thinking and solution planning, we suggest that companies create solution concepts. The purpose of the solution concept is to provide a big picture of the solution and guide RE activities.     

Development of a new software for comprehensive management and traceability of hospital radiopharmacies

A database software application for comprehensive management and traceability of hospital radiopharmacies has been developed and implemented. This software is a customizable shareware called Radiolab, which provides an immediate and complete traceability of all preparations, controls and radiopharmaceuticals, as well as a great help in the management of reports, orders, stock and radioactive waste. Available by now in five languages (English, Spanish, French, Portuguese and Italian) this software and its manual can be downloaded from the Internet at www.radiopharmacy.net.