Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Product-line architectures in industry: a case study
Proceedings of the 21st international conference on Software engineering
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Value based software reuse investment
Annals of Software Engineering
Product and project challenges in electronic commerce software development
ACM SIGMIS Database
Software Architecture in Practice
Software Architecture in Practice
Software technology in an automotive company: major challenges
Proceedings of the 25th International Conference on Software Engineering
Embedded Software Engineering: The State of the Practice
IEEE Software
Product Line Engineering: The State of the Practice
IEEE Software
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
Towards verified automotive software
SEAS '05 Proceedings of the second international workshop on Software engineering for automotive systems
Capturing and Using Software Architecture Knowledge for Architecture-Based Software Development
QSIC '05 Proceedings of the Fifth International Conference on Quality Software
System and software architecture reconciliation
Systems Engineering
Challenges in automotive software engineering
Proceedings of the 28th international conference on Software engineering
Software Engineering for Automotive Systems: A Roadmap
FOSE '07 2007 Future of Software Engineering
An Economics-Driven Approach for Valuing Scalability in Distributed Architectures
WICSA '08 Proceedings of the Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008)
Software architecting without requirements knowledge and experience: What are the repercussions?
Journal of Systems and Software
A Case Study of Issues Related to Automotive E/E System Architecture Development
ECBS '08 Proceedings of the 15th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems
Improving the effectiveness of root cause analysis in post mortem analysis: A controlled experiment
Information and Software Technology
Issues Related to Development of E/E Product Line Architectures in Heavy Vehicles
HICSS '09 Proceedings of the 42nd Hawaii International Conference on System Sciences
Towards a process maturity model for evolutionary architecting of embedded system product lines
Proceedings of the Fourth European Conference on Software Architecture: Companion Volume
Software architecture design: evaluation and transformation
ECBS'99 Proceedings of the 1999 IEEE conference on Engineering of computer-based systems
Hi-index | 0.00 |
Context: Today, 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-30years 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. Objective: We 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. Method: The 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. Results: A 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. Conclusion: In 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.