Software Reference Architectures - Exploring Their Usage and Design in Practice

Angelov, Samuil; Trienekens, Jjm Jos; Kusters, Rob J.

doi:10.1007/978-3-642-39031-9_2

Cited by 14 publications

(48 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Finally, with respect to the benefits and drawbacks of software reference architectures, Angelov et al conducted a global webbased survey on using software reference architectures [3]. Also, some authors of this paper executed a case study on the benefits and drawbacks of using software reference architectures conducted in an IT consulting company [17].…”

Section: Related Workmentioning

confidence: 99%

A Survey on the Benefits and Drawbacks of AUTOSAR

Martínez‐Fernández

Ayala

Franch

et al. 2015

Proceedings of the First International Workshop on Automotive Software Architecture

View full text Add to dashboard Cite

The use of software reference architectures plays a fundamental role in software development, as it could bring several benefits such as providing means to design applications' software architectures with higher productivity and quality. However, many organizations still find scarce the existing empirical evidence about the benefits and drawbacks of software reference architectures. Organizations need such evidence to make informed decisions whether or not to adopt a software reference architecture for the development and maintenance of software applications. In this context, this paper aims to gather evidence on AUTOSAR, a mature and accepted software reference architecture for automotive applications used worldwide by more than 180 organizations. We designed and executed a web-based survey addressed to practitioners with experience in using AUTOSAR. We obtained 51 valid responses. The survey results indicate that the most popular benefits of AUTOSAR are standardization (88%), reuse (80%) and interoperability (51%) whereas its most important drawbacks are complexity (65%), initial investment (59%) and learning curve (51%). The respondents of the survey also gave directions to handle the major drawbacks of AUTOSAR, such as the need of a tool environment to improve its usability and handle its complexity, and the need of more stable releases of AUTOSAR to decrease the cost of migrating among versions.

show abstract

Section: Related Workmentioning

confidence: 99%

A Survey on the Benefits and Drawbacks of AUTOSAR

Martínez‐Fernández

Ayala

Franch

et al. 2015

Proceedings of the First International Workshop on Automotive Software Architecture

View full text Add to dashboard Cite

show abstract

“…(i) We evaluated the TSPACE SRAs and their respective implementations for functional completeness corresponding to the functional and quality requirements. (ii) We implemented the prototype systems for TSPACE SRAs using Amazon IaaS cloud 1 . Interface modules of TSPACE have been implemented using Service Oriented Architecture (SOA) [25] and REST [26] architecture styles using JavaEE service technologies (JAX-RS 2 , JAX-WS 3 ) for enabling easy interoperability of different types of tools with the systems.…”

Section: Architecture Design Decisionsmentioning

confidence: 99%

“…One of the most comprehensive and detailed guidelines have been reported by Angelov et al [1,2,7,16]. Their work provides a classification technique of the reference architectures based upon the domain-specific maturity and how the reference architectures are designed.…”

Section: Related Workmentioning

confidence: 99%

“…For the mature domains, the aim of a reference architecture is to provide the standardization of the architectures, whereas, for the emerging domains, the purpose is to facilitate the design of concrete architectures in multiple organizations. Some of the problems associated with designing a reference architecture are missing design methods, challenges in defining nonfunctional requirements, problems with selecting appropriate views, lack of suitable architecture documentation methods and relatively little support for evaluating the reference architectures [1]. In our TSPACE SRA design process, we have explicitly catered all of the above-mentioned challenges to support the process of designing the reference architecture and have explicit stages for design and documentation methods, define non-functional requirements, select appropriate views and choose appropriate evaluation strategies.…”

Section: Related Workmentioning

confidence: 99%

“…A Software Reference Architecture (SRA) provides an abstraction for designing and reasoning about a concrete software architecture of a specific system domain [1][2].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations