| 1. |
- Spalazzese, Romina, et al.
(författare)
-
INTERO: An Interoperability Model for Large Systems
- 2020
-
Ingår i: IEEE Software. - : IEEE. - 1937-4194 .- 0740-7459. ; 37:3, s. 38-45
-
Tidskriftsartikel (refereegranskat)abstract
- The INTERO (interoperability) model helps organizations manage and improve interoperability among their large, evolving software systems. They can analyze a specific interoperability problem, conceive strategies to enhance interoperability, and reevaluate the problem to determine whether interoperability has improved.
|
|
| 2. |
- Berger, Christian, 1980, et al.
(författare)
-
Expectations and Challenges from Scaling Agile in Mechatronics-Driven Companies - nA Comparative Case Study
- 2015
-
Ingår i: 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
-
Bokkapitel (refereegranskat)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.
|
|
| 3. |
- Eklund, Ulrik, 1967, et al.
(författare)
-
Architecture for embedded open software ecosystems
- 2014
-
Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 92:O, 2003, Std 11898, s. 128-142
-
Tidskriftsartikel (refereegranskat)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.
|
|
| 4. |
- Becanovic, Vlatko, et al.
(författare)
-
HUGIN: a small satellite trying to be intelligent
- 1999
-
Ingår i: Proc. SPIE. ; 3728, s. 98-
-
Konferensbidrag (refereegranskat)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.
|
|
| 5. |
- Berger, Christian, et al.
(författare)
-
Expectations and Challenges from Scaling Agile in Mechatronics-Driven Companies – A Comparative Case Study
- 2022
-
Ingår i: Accelerating Digital Transformation. - Cham : Springer. - 9783031108723 - 9783031108754 - 9783031108730 ; , s. 119-130
-
Bokkapitel (refereegranskat)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.
|
|
| 6. |
- Bosch, Jan, 1967, et al.
(författare)
-
Eternal Embedded Software: Towards Innovation Experiment Systems
- 2012
-
Ingår i: 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 LNCS:PART 1, s. 19-31
-
Konferensbidrag (refereegranskat)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.
|
|
| 7. |
- Eklund, Lina, et al.
(författare)
-
Using geographical information systems to analyse accessibility to health services in the West Bank, Occupied Palestinian Territory
- 2012
-
Ingår i: Eastern Mediterranean Health Journal. - 1020-3397. ; 18:8, s. 796-802
-
Tidskriftsartikel (refereegranskat)abstract
- Abstract in UndeterminedAccessibility to adequate health services is a basic human right. Israeli road blocks and checkpoints inhibit access to health care for the Palestinian population. While other studies have dealt with the impact of the barriers, few are based on actual measurements of transport times between locations. Geographical information systems (GIS) and network analysis were used to generate different estimations of accessibility based on the existing road network and transport barriers. The population negatively affected were mainly people living outside urban centres and in governorates with no general hospital. Quantitative measurements using GIS can be used to confirm qualitative studies based on interviews and questionnaires and improve the understanding of the results. Working with a spatial analysis tool also helps to pinpoint weaknesses in the current infrastructure, thus improving the efficiency of future investments to improve health care in the West Bank.
|
|
| 8. |
- Eklund, Ulrik, 1967, et al.
(författare)
-
A Case Study of the Architecture Business Cycle for an In-Vehicle Software Architecture
- 2009
-
Ingår i: Proceeedings of the 2009 Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture. - 9781424452958 ; , s. 91-100
-
Konferensbidrag (refereegranskat)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.
|
|
| 9. |
- Eklund, Ulrik, 1967, et al.
(författare)
-
A Classification of Value for Software Architecture Decisions
- 2010
-
Ingår i: 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. - 9783642151132 ; 6285, s. 368-375
-
Konferensbidrag (refereegranskat)abstract
- This paper introduces a classification for decisions originating from work performed by architects. With the creation of a new architecture, all observed decisions were documented using an existing taxonomy extended with the introduced classification.In the first four months, 80 decisions were documented. Not all decisions have the same value for the architecture and one needed a classification to reason about importance of decisions.After realization of the first increment of the architecture a sanity check was performed: The architects showed how the six most important design artefacts and the fifteen most important architectural constraints and prerequisites were related. The relationship was via decisions and the classification helps to reduce the work to make and maintain this connection over time.The classification is dynamic and over time decisions can be classified differently. This enables architectural learning by pointing out which decisions were taken too early or had little impact.
|
|
| 10. |
- Eklund, Ulrik, 1967, et al.
(författare)
-
A reference architecture template for software-intensive embedded systems
- 2012
-
Ingår i: ACM International Conference Proceeding Series. - New York, NY, USA : ACM. - 9781450315685 ; , s. 104-111
-
Konferensbidrag (refereegranskat)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.
|
|
