NDLI: Business situation reflected in automotive electronic architectures:analysis of four commercial cases

Content Provider	ACM Digital Library
Author	Sandström, Kristian Fröberg, Joakim Norström, Christer
Abstract	Automotive vehicle electronic systems are developed facing a complex and large set of inter-related requirements from numerous stakeholders, many of which are internal to the Original Equipment Manufacturer, OEM. The electronic architecture, of the product, or its structure and design principles, form an equally complex construct; including technology and methods, which ultimately should be chosen to optimally support the organization's own business situation.In this paper, we have analyzed the relationship of four automotive electronic architectures to their respective business requirements and business context. The study shows four functionally rather similar products with computer controlled power train, body functions, and instrument. In the light of the business situation, we explain the solutions and why design principles are pursued. The analysis shows that despite a common base of similar vehicle functionality the resulting electronic architectures used by the four organizations are quite different. The reason for this becomes apparent when looking at different business context and business requirements and their affect on the architecture. Differences in business situation drive the use of different methods for integration, different standards, different number of configurations, and different focus in the development effort. Some key parameters in business situation affecting architectural design decisions are shown to be product volume, size of market, and business requirements on openness and customer adaptation.An important lesson from this is that one should be very careful to uncritically apply technical solutions from one industry in another, even when they are as closely related as the applications described in this work. Understanding the requirements from the business case is the key to choosing architectural solutions.
Starting Page	1
Ending Page	6
Page Count	6
File Format	PDF
ISSN	01635948
DOI	10.1145/1082983.1083197
Journal	ACM SIGSOFT Software Engineering Notes (SOEN)
Volume Number	30
Issue Number	4
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	1979-04-01
Publisher Place	New York
Access Restriction	One Nation One Subscription (ONOS)
Subject Keyword	Case-study Automotive Requirements Electronic architecture
Content Type	Text
Resource Type	Article

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in

Business situation reflected in automotive electronic architectures: analysis of four commercial cases

Experience of introducing reference architectures in the development of automotive electronic systems

Automotive behavioral requirements expressed in a specification pattern system: a case study at BOSCH

Automotive use case standard for embedded systems

A case study of the architecture business cycle for an in-vehicle software architecture.

Engineering Requirements Through Use Cases in Complex Business Environment

Playscript for use cases

Gap Analysis of Human Resource Situation with EFQM Requirements in Iranian Automotive Industries(Case Study

Requirements management in practice: findings from an empirical study in the automotive industry

Business situation reflected in automotive electronic architectures:analysis of four commercial cases

Similar Documents

Business situation reflected in automotive electronic architectures: analysis of four commercial cases

Experience of introducing reference architectures in the development of automotive electronic systems

Automotive behavioral requirements expressed in a specification pattern system: a case study at BOSCH

Automotive use case standard for embedded systems

A case study of the architecture business cycle for an in-vehicle software architecture.

Engineering Requirements Through Use Cases in Complex Business Environment

Playscript for use cases

Gap Analysis of Human Resource Situation with EFQM Requirements in Iranian Automotive Industries(Case Study

Requirements management in practice: findings from an empirical study in the automotive industry

Business situation reflected in automotive electronic architectures:analysis of four commercial cases