Problems and their mitigation in system and software architecting |
| |
| Affiliation: | 1. Department of Energy, Tezpur University, Tezpur 784028, Assam, India;2. Department of Electrical Engineering, National Institute of Technology, Silchar 788010, Assam, India;3. The Energy and Resources Institute, Darbari Seth Block, Lodhi Road, New Delhi 110 003, India;4. Assam Energy Development Agency, Bigyan Bhawan, Guwahati 781005, Assam, India;1. Department of Operational Research, University of Delhi, Delhi 110007, India;2. University School of Management and Entrepreneurship, Delhi Technological University, East Delhi Campus, India;1. Division of Infectious Diseases, Department of Medicine, Johns Hopkins University School of Medicine, Baltimore, MD;2. Armstrong Institute of Patient Safety and Quality, Johns Hopkins University School of Medicine, Baltimore, MD;3. Weill Cornell Medical College, New York, NY;4. Johns Hopkins Bloomberg School of Public Health, Baltimore, MD;5. Department of Quality Management, Johns Hopkins Home Care Group, Baltimore, MD;1. Department of Twin Research, King''s College London, St Thomas'' Hospital, London SE1 7EH, UK;2. Department of Infectious Diseases, School of Immunology & Microbial Sciences, King''s College London, London, UK;3. Department of Infectious Disease, Imperial College London, UK;4. Centre for Inflammation Biology and Cancer Immunology, Department of Inflammation Biology, School of Immunology & Microbial Sciences, King''s College London, London, UK;5. Department of Immunobiology, School of Immunology and Microbial Sciences, King''s College London, London, UK;6. Zoe Global Ltd., Westminster Bridge Rd, London, UK;7. School of Biomedical Engineering & Imaging Sciences, King''s College London, London, UK;8. Department of Medical & Molecular Genetics, Guy''s and St Thomas'' Hospital NHS Trust and King''s College London NIHR Biomedical Research Centre, London, UK |
| |
| Abstract: | ContextToday, software and embedded systems act as enablers for developing new functionality in traditional industries such as the automotive, process automation, and manufacturing automation domains. This differs from 25–30 years ago when these systems where based on electronics and electro-mechanical solutions. The architecture of the embedded system and of the software is important to ensure the qualities of these applications. However, the effort of designing and evolving the architecture is in practice often neglected during system development, whilst development efforts are centered on implementing new functionality.ObjectiveWe present problems and success factors that are central to the architectural development of software intensive systems in the domain of automotive and automation products as judged by practitioners.MethodThe method consisted of three steps. First, we used semi-structured interviews to collect data in an exploratory manner. As a second step, a survey based on problems extracted from the interview data was used to investigate the occurrence of these problems at a wider range of organizations. In order to identify and suggest how to mitigate the problems that were considered important, we finally performed root cause analysis workshops, and from these a number of success factors were elicited.ResultsA total of 21 problems have been identified based on the interview data, and these are related to the technical, organizational, project, and agreement processes. Based on the survey results, the following four problems were selected for a root cause analysis: (1) there is a lack of process for architecture development, (2) there is a lack of method or model to evaluate the business value when choosing the architecture, (3) there is a lack of clear long-term architectural strategy, and (4) processes and methods are less valued than knowledge and competence of individuals.ConclusionIn conclusion, the following identified success factors are crucial components to be successful in developing software intensive systems: (1) define an architectural strategy, (2) implement a process for architectural work, (3) ensure authority for architects, (4) clarify the business impact of the architecture, and (5) optimize on the project portfolio level instead of optimizing each project. |
| |
| Keywords: | |
| 本文献已被 ScienceDirect 等数据库收录！ |
|
