| 1. |
- Bosch, Jan, 1967, et al.
(author)
-
Eternal Embedded Software: Towards Innovation Experiment Systems
- 2012
-
In: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1611-3349 .- 0302-9743. - 9783642340253 ; 7609:PART 1, s. 19-31
-
Conference paper (peer-reviewed)abstract
- The paper discusses the concept of innovation experiment systems in the context of long-lived embedded systems. These systems need to evolve continuously to stay competitive and provide value to the customer and end-user, especially in domains where the pace of change is increasing.Innovation experiment systems provide a natural mechanism that allows an embedded system, its architecture and underlying platform to continuously evolve in response to changes in the user requirements and system context. It uses a rapid feedback loop to evaluate the benefits of small variations to users with the intent of continuous improvements.The paper explores the architectural implications as the ability to continuously evolve and conduct experiences in the deployed product context in a safe and controlled manner must be supported by the architecture of the embedded systems.Finally, the paper illustrates these concepts using a case study concerning an infotainment system in the automotive industry.
|
|
| 2. |
- Eklund, Ulrik, 1967, et al.
(author)
-
A reference architecture template for software-intensive embedded systems
- 2012
-
In: ACM International Conference Proceeding Series. - New York, NY, USA : ACM. - 9781450315685 ; , s. 104-111
-
Conference paper (peer-reviewed)abstract
- The paper presents a document template for reference architectures for the domain of software-intensive embedded systems. The template addresses the somewhat conflicting needs when documenting a reference architecture of readability, overview, details, evolution and different background of the stakeholders. The first novel idea is the template prescribes two separate documents describing a reference architecture beside the product architecture documentation. The information in the two documents concern different stakeholders and evolve at different paces. The other novelty in describing reference architectures is to introduce a perspective of time, in the form of horizons, rather than focusing on a snapshot a release date. In addition, a case is presented giving an example of how a reference architecture was documented according to the template, how stakeholder needs were captured, and how the different types of information was identified or recovered from existing product architectures.
|
|
| 3. |
- Eklund, Ulrik, 1967, et al.
(author)
-
Applying Agile Development in Mass-Produced Embedded Systems
- 2012
-
In: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642303494 ; 111, s. 31-46
-
Conference paper (peer-reviewed)abstract
- The paper presents a method to manage critical interactions to manage when introducing agile software development in mass-produced embedded systems. The method consists of a context model together with a set of measures, and is validated by empirical evidence from three cases.From an industrial perspective, the paper provides a prescription on how to implement agile software development outside the typical domains for agile, in this case for mass-produced products with embedded software governed by a stage-gate process for mechanics and hardware.From a research perspective, the paper provides an analysis of the software development cycle for products with embedded software, especially where product development as a whole is driven by a plan-driven process. The main contribution is a method for introducing agile in areas where by necessity the full R&D process cannot be agile.
|
|
| 4. |
- Eklund, Ulrik, 1967, et al.
(author)
-
Architecture for embedded open software ecosystems
- 2014
-
In: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 92:O, 2003, Std 11898, s. 128-142
-
Journal article (peer-reviewed)abstract
- Software is prevalent in embedded products and may be critical for the success of the products, but manufacturers may view software as a necessary evil rather than as a key strategic opportunity and business differentiator. One of the reasons for this can be extensive supplier and subcontractor relationships and the cost, effort or unpredictability of the deliverables from the subcontractors are experienced as a major problem. The paper proposes open software ecosystem as an alternative approach to develop software for embedded systems, and elaborates on the necessary quality attributes of an embedded platform underlying such an ecosystem. The paper then defines a reference architecture consisting of 17 key decisions together with four architectural patterns, and provides the rationale why they are essential for an open software ecosystem platform for embedded systems in general and automotive systems in particular. The reference architecture is validated through a prototypical platform implementation in an industrial setting, providing a deeper understanding of how the architecture could be realised in the automotive domain. Four potential existing platforms, all targeted at the embedded domain (Android, OKL4, AUTOSAR and Robocop), are evaluated against the identified quality attributes to see how they could serve as a basis for an open software ecosystem platform with the conclusion that while none of them is a perfect fit they all have fundamental mechanisms necessary for an open software ecosystem approach.
|
|
| 5. |
- Eklund, Ulrik, 1967, et al.
(author)
-
Architecture for Large-Scale Innovation Experiment Systems
- 2012
-
In: Proceedings of the Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture. - 9780769548272 ; , s. 244-248
-
Conference paper (peer-reviewed)abstract
- Business and design decisions regarding software development should be based on data, not opinions among developers, domain experts or managers. The company running the most and fastest experiments among the customer base against the lowest cost per experiment outcompetes others by having the data to engineer products with outstanding qualities such as power consumption and user experience. Innovation experiment systems for mass-produced devices with embedded software is an evolution of current R&D practices, going from where innovations are internally evaluated by the original equipment manufacturer to where they are tried by real users in a scale relevant to the full customer base. The turnaround time from developing and deploying an embedded product to getting customer feedback is decreased to weeks, the limit being the speed of the software development teams. The paper presents an embedded architecture for realising such a novel innovation experiment system based on a set of scenarios of what to evaluate in the experiments. A case is presented implementing an architecture in a prototype in-vehicle infotainment system where comparative testing between two software alternatives was performed.
|
|
| 6. |
- Eklund, Ulrik, 1967, et al.
(author)
-
Introducing Software Ecosystems for Mass-Produced Embedded Systems
- 2012
-
In: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642307461 ; 114, s. 248-254
-
Conference paper (peer-reviewed)abstract
- Embedded systems are today predominantly developed with an integration-centric approach. The paper identifies the need to remove full-scale integration and process synchronisation of involved development teams. The paper presents software ecosystem as an alternative approach to develop embedded software and identifies a set of key activities for how an original equipment manufacturer can introduce an ecosystem.An example of a software ecosystem is presented for the carindustry together a case which implemented some of the ecosystem platform properties.
|
|
| 7. |
- Eklund, Ulrik, 1967, et al.
(author)
-
Using architecture for multiple levels of access to an ecosystem platform
- 2012
-
In: Proceedings of the 8th international ACM SIGSOFT conference on Quality of Software Architectures. - New York, NY, USA : ACM. - 9781450313469 ; 2012, s. 143-148
-
Conference paper (peer-reviewed)abstract
- The paper presents a novel ecosystem for software-intensive embedded systems as an alternative to integration-centric software development. A set of necessary qualities is identified for the embedded platform enabling the ecosystem, i.e. deployability of new functions, maintainability over time, and configurability according to hardware within the product family. The embedded platform must support composability of software from different development stakeholders, such as the original equipment manufacturer, strategic and 3rd-party developers.The paper presents some key mechanisms for implementing the necessary certification in the platform that facilitates composability while still preserving dependability. A theoretical example of how this would look like in the automotive domain is presented, and an actual case of an in-vehicle platform implementing some of the mechanisms is shown.
|
|
| 8. |
- Becanovic, Vlatko, et al.
(author)
-
HUGIN: a small satellite trying to be intelligent
- 1999
-
In: Proc. SPIE. ; 3728, s. 98-
-
Conference paper (peer-reviewed)abstract
- Micro and nano-satellites are important tools to explore and test new ideas and various new devices for space missions without spending extreme amounts of money. The actual launch cost per kilogram payload on a micro or nano-satellite can be as high or even higher than ordinary satellites but the turn around time and quick responses are extremely important. The HUGIN project is a nano-satellite (less than 10 kg) explicitly designed to test magnetic coils and adaptive artificial neural network (ANN) algorithms for attitude control purposes. A small PC video camera is also included and if the control function is successful then also tests of adaptive image processing using other ANN and biologically inspired methods will be performed.
|
|
| 9. |
- Berger, Christian, 1980, et al.
(author)
-
Expectations and Challenges from Scaling Agile in Mechatronics-Driven Companies - nA Comparative Case Study
- 2015
-
In: Agile Processes, in Software Engineering, and Extreme Programming, Xp 2015. - Berlin : Springer-Verlag Berlin. - 9783319186122 ; 212, s. 15-26, s. 15-26, s. 15-26
-
Book chapter (peer-reviewed)abstract
- Agile software development is increasingly adopted by companies evolving and maintaining software products to support better planning and tracking the realization of user stories and features. While convincing success stories help to further spread the adoption of Agile, mechatronics-driven companies need guidance to implement Agile for non-software teams. In this comparative case study of three companies from the Nordic region, we systematically investigate expectations and challenges from scaling Agile in organizations dealing with mechatronics development by conducting on-site workshops and surveys. Our findings show that all companies have already successfully implemented Agile in their software teams. The expected main benefit of successfully scaling agile development is a faster time-to-market product development; however, the two main challenges are: (a) An inflexible test environment that inhibits fast feedback to changed or added features, and (b) the existing organizational structure including the company's mind-set that needs to be opened-up for agile principles.
|
|
| 10. |
- Eklund, Ulrik, 1967, et al.
(author)
-
A Case Study of the Architecture Business Cycle for an In-Vehicle Software Architecture
- 2009
-
In: Proceeedings of the 2009 Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture. - 9781424452958 ; , s. 91-100
-
Conference paper (peer-reviewed)abstract
- This paper presents the theoretical and practical benefits from a case study using a the Architecture Business Cycle to understand the management of software architecture at an automotive manufacturer. The study was done to prepare for architectural changes driven by new technology and in the automotive business environment. Our results show that the architecture business cycle worked well in defining the theoretical context for the study after some modifications; the architecture had to be precisely defined in the interview situation to gain more useful data rather than broad generalisations. Further contributions of the study were a deeper understanding of role of the architecture and it's position among other artefacts in the organisation, and an increased focus on architectural issues in management meetings. The study also indirectly affected a subsequent re-organisation.
|
|
