Multiparadigm description of system development processes

Author(s):  
C. Hoffmann ◽  
B. KrÄmer ◽  
B. Dinler
Author(s):  
Kerstin Schmidt ◽  
Grit Walther ◽  
Thomas S. Spengler ◽  
Rolf Ernst

Author(s):  
Jonas Heimicke ◽  
Manuel Niever ◽  
Valentin Zimmermann ◽  
Monika Klippert ◽  
Florian Marthaler ◽  
...  

AbstractThe development of mechatronic systems has always been characterized by continuous handling of uncertainties. This challenge, which is associated with dynamic changes in the development context, is increasingly met by companies in the development of physical systems with the implementation of agile approaches in their development processes. However, since established approaches have their origin in software development, they reach various limits in the context of the development of mechatronic systems, e.g. due to the physical properties of the systems. Other features, such as transparent and flexible project management or targeted and early involvement of customers and users in development processes, can also be implemented in mechatronic system development. In order to derive the potentials and limits of existing agile approaches for the context of mechatronic system development, the present paper compares existing approaches with regard to relevant factors from the context of mechatronic system development. The aim is to create a basis for the targeted development, adaptation and use of agile approaches in the field of mechatronic system development.


2021 ◽  
Vol 33 (1) ◽  
Author(s):  
Trevor Chawana ◽  
Funmi Adebesin

Incorporating user experience (UX) design into system development processes can give an organisation competitive advantage over its rivals. Embedding UX design into system development processes requires investment in skilled professionals, who in turn follow a methodical process to make UX design an integral part of the organisation. Despite the value that can be added by UX design, demonstrating the return on investment (ROI) in UX remains a perennial challenge because of the difficulty associated with explicitly linking UX design with good ROI, to the exclusion of other system development processes. In this paper, we report on the current state of measuring ROI in UX design in a selection of South African organisations. We interviewed 33 UX professionals from four organisations to get insight into how ROI in UX design is measured in their respective organisations. The results showed that some participants were aware of the metrics that could be used to measure ROI in UX design. However, none of the four organisations were specifically calculating ROI in UX. Rather, ROI was being calculated on entire project.


Author(s):  
Sara Allabar ◽  
Christian Bettinger ◽  
Michael Müllen ◽  
Georg Rock

Nowadays, industrial products as well as software applications are expected to be tailored to the user’s needs in an increasingly distinct manner. This often makes it necessary to design a vast number of customized variants, which leads to complex and error prone analysis and development processes. Generally, requirements engineering is considered to be one of the most significant activities in software and system development. Variant management has proven to play an important role in handling the complexity arising from mass-customization of products. However, there are only a few, often rather complex-to-use, applications which allow adding variance information directly to requirements. Especially in case of small and medium sized enterprises, approaches to meet this challenge often result in isolated solutions that are not driven by state-of-the-art analysis methods and do not cope with future requirements. This paper introduces a lightweight requirements management tool called scone, which will be embedded into an overall variability management methodology. scone enables the user to create and manage requirement specifications and augment them with variability information. Based on this specification, the requirements can be analyzed in a formal way with respect to their variability using the variability management tool Glencoe. scone was created as a single-page web application to eliminate the need for installation and allow it to run on many devices, while offering the experience of working with a native application, rather than a website. Both tools are designed to provide a proof of concept for the seamless integration of variability information within a system development process as well as to show how variability can be handled in an easy-to-use way from the very beginning within this process.


2019 ◽  
Vol 26 (2) ◽  
pp. 851-870 ◽  
Author(s):  
Benjamin Strenge ◽  
Thomas Schack

Abstract Ethical, legal and social implications are widely regarded as important considerations with respect to technological developments. Agile Worth-Oriented Systems Engineering (AWOSE) is an innovative approach to incorporating ethically relevant criteria during agile development processes through a flexibly applicable methodology. First, a predefined model for the ethical evaluation of socio-technical systems is used to assess ethical issues according to different dimensions. The second part of AWOSE ensures that ethical issues are not only identified, but also systematically considered during the design of systems based on information and communication technology. For this purpose, the findings from the first step are integrated with approaches from worth-centered development into a process model that, unlike previous approaches to ethical system development, is thoroughly compatible with agile methodologies like Scrum or Extreme Programming. Artifacts of worth-centered development called Worth Maps have been improved to guide the prioritization of development tasks as well as choices among design alternatives with respect to ethical implications. Furthermore, the improved Worth Maps facilitate the identification of suitable criteria for system evaluations in association to ethical concerns and desired positive outcomes of system usage. The potential of the AWOSE methodology has been demonstrated in the context of a technical system (smart glasses for cognitive assistance) that supports elderly and people with particular handicaps.


Author(s):  
Vahid Salehi ◽  
Shirui Wang

AbstractModel-based systems engineering (MBSE) is well-known in gaining the control over the complexity of systems and the development processes, while agile is a project management methodology originally from software development that uses short development cycles to focus on continuous improvement in the development of a product or service. In this paper, we adopt the concept of agile into MBSE and then proposed the new approach - Munich Agile MBSE Concept (MAGIC). The highlights of the MAGIC approach can be concluded as 1) the requirements which have been defined in the first stage will be examined and traced at each following stages; 2) communication between every 2 stages always exists in order to have a close connection during each system development phase; 3) the idea of Industry 4.0 has been included and reflected to achieve automation and data exchange with manufacturing technologies; 4) the concept of IOT (Internet of Things) is also considered when it comes to the usage and service of the system to satisfy the customer's needs; 5) the whole spirit of agile is reflected as the iterative and incremental design and development


Author(s):  
Eran Rubin ◽  
Hillel Rubin

Agile processes emphasize operational system code rather than its documentation. Ironically, however, some traditional documentation artefacts come to support system-stakeholders interaction, which is another core aspect of agile development processes. In this chapter, the authors examine the relationship between system development and knowledge documentation. They develop an approach that enables incorporating domain documentation to agile development while keeping the processes adaptive. The authors also provide a system design that actively uses domain knowledge documentation.


Author(s):  
Kristin Goevert ◽  
Jonas Heimicke ◽  
Udo Lindemann ◽  
Albert Albers

AbstractIn order to be as responsive as possible to changes in the dynamic context of mechatronic system development, companies are increasingly integrating agile approaches into their development processes. They are confronted with the challenges of adapting approaches that originate in software development to the conditions of physical development, without neglecting the experiences gained over many years regarding product and process knowledge. In addition, agile development approaches must be integrated into existing processes through a systematic implementation strategy. In order to gain an initial understanding of the current situation in mechatronic companies with regard to agile development approaches, an interview study was conducted with 18 participants from real development practice. This could show that the companies in mechatronic system development are currently at the beginning of agile transformation and need approaches that are modelled on the basis of real development projects and are best possible tailored to the needs of these companies through a clear technical orientation. The findings gained are not universally valid, but represent a basis for further research work.


Sign in / Sign up

Export Citation Format

Share Document