Scrum versus Rational Unified Process in facing the main challenges of product configuration systems development

2020 ◽  
Vol 170 ◽  
pp. 110732
Author(s):  
Sara Shafiee ◽  
Yves Wautelet ◽  
Lars Hvam ◽  
Enrico Sandrin ◽  
Cipriano Forza
2018 ◽  
Vol 100 ◽  
pp. 57-69 ◽  
Author(s):  
Katrin Kristjansdottir ◽  
Sara Shafiee ◽  
Lars Hvam ◽  
Martin Bonev ◽  
Anna Myrodia

Author(s):  
ALEXANDER FELFERNIG ◽  
GERHARD E. FRIEDRICH ◽  
DIETMAR JANNACH

In many domains, software development has to meet the challenges of developing highly adaptable software very rapidly. In order to accomplish this task, domain specific, formal description languages and knowledge-based systems are employed. From the viewpoint of the industrial software development process, it is important to integrate the construction and maintenance of these systems into standard software engineering processes. In addition, the descriptions should be comprehensible for the domain experts in order to facilitate the review process. For the realization of product configuration systems, we show how these requirements can be met by using a standard design language (UML-Unified Modeling Language) as notation in order to simplify the construction of a logic-based description of the domain knowledge. We show how classical description concepts for expressing configuration knowledge can be introduced into UML and be translated into logical sentences automatically. These sentences are exploited by a general inference engine solving the configuration task.


Author(s):  
Kasper Edwards

Product configuration systems (PCS) are a technology well suited for mass customization and support the task of configuring the product to the individual customer’s needs. PCS are at the same time complex software systems that may be tailored to solve a variety of problems for a firm, e.g. supporting the quotation process or validating the structure of a product. This chapter reports findings from a study of 12 Danish firms, which at the time of the study have implemented or are in the process of implementing product configuration systems. 12 costs and 12 benefits are identified in literature, and using radar diagrams as a tool for data collection the relative difference are identified. While several of the firms are mass customizers it is not the primary driver for implementing PCS. The analysis reveals that expected and realized benefits are consistent: 1) Improved quality in specifications, 2) Using less resources, and 3) Lower turnaround time. Interestingly, the realized benefits are all higher than the expected benefits. The expected benefits highlight the motivation, and this has implications for human factors as they point in the direction of significant changes to come in the adopting organization. It is observed that product configuration projects are treated as simple technical projects although they should be regarded as organizational change projects.


Sign in / Sign up

Export Citation Format

Share Document