| 1. |
- Mellegård, Niklas, 1971, et al.
(författare)
-
Characterizing Model Usage in Embedded Software Engineering: A Case Study
- 2010
-
Ingår i: 8th Nordic Workshop on Model Driven Software Engineering (NW-MoDE). - New York, NY, USA : ACM. ; , s. 245-252
-
Konferensbidrag (refereegranskat)abstract
- During development of complex products, such as automotive software, models – formal and informal – are used throughout the development process by different roles and for different purposes – as requirement, as implementation or as documentation. This paper reports results from a case-study of the development of embedded software at a Swedish vehicle manufacturer. We investigated use of models from high-level product planning to low-level requirements specifications for software components. Furthermore, we investigated the distribution of effort among the models, requirements and other artefacts. The goal was to explore the spectrum of modelling techniques, methods and languages used and to establish a baseline for comparison with the state-of-the-art and other companies. The results show that there exist at least 8 different modelling notations. Moreover, we found that the majority of effort was spent on behaviour models, while static models – such as high-level design and requirements – were considered most important.
|
|
| 2. |
- Mellegård, Niklas, 1971, et al.
(författare)
-
Distribution of Effort Among Software Development Artefacts: An Initial Case Study
- 2010
-
Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642130502 ; 50, s. 234-246
-
Konferensbidrag (refereegranskat)abstract
- Model-driven development aims at increasing productivity by raising the abstraction level of software specifications and introducing automated transformations for replacing lower level specifications. To assess benefits of replacing a legacy development process with a model-driven approach, one needs to establish a baseline of the current process with respect to the effort invested in the development artefacts. In this paper we report on an initial case study in which we investigate the main artefacts in the analysis and design phase with respect to required effort and perceived importance. We studied a non-model driven development of software based automotive functionality and our initial results show that a few artefacts receive the majority of effort, and that the artefacts that receive the most effort are not the most important ones. The initial results indicate that the distribution of effort between models and other artefacts is similar to that of model-driven projects in spite of the project being perceived and characterized as code-centric.
|
|
| 3. |
- Mellegård, Niklas, 1971, et al.
(författare)
-
Improving Efficiency of Change Impact Assessment Using Graphical Requirement Specifications: An Experiment
- 2010
-
Ingår i: Lecture Notes in Computer Science. 11th International Conference on Product-Focused Software Process Improvement, PROFES 2010, Limerick, 21-23 June 2010. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 0302-9743 .- 1611-3349. - 9783642137914 ; 6156, s. 336-350
-
Konferensbidrag (refereegranskat)abstract
- Objective: Graphical requirements representation is often considered needed to advance model-driven development. Dedicated modelling languages include formalisms for graphically representing requirements, and together with new methods for structuring requirements, graphical modelling promises improvements such as more efficient change management. This paper examines whether the use of a graphical notation of a requirements affects the task of assessing the impact of a proposed change to a requirements specification. Method: The efficiency of using a graphical requirements representation was examined through an experiment – using 18 student subjects. Time, perceived confidence and accuracy were measured as dependent variables. Result: The results showed that using a graphical representation decreased the time required and increased the perceived confidence, but the accuracy decreased. However, the statistical analysis of the results showed that only the difference in time was significant. Furthermore, there was a large difference in variance within the dependent variables between the groups.
|
|
| 4. |
- Mellegård, Niklas, 1971, et al.
(författare)
-
Use of Models in Automotive Software Development: A Case-study
- 2010
-
Ingår i: M-BED Workshop on Model Based Engineering for Embedded Systems Design. ; , s. 35-39
-
Konferensbidrag (refereegranskat)abstract
- Models, formal and informal, can be used in product development for many purposes, e.g. to specify the desired behaviour of a function; to specify requirements; or as implementation. During the development of complex products, such as automotive software, models are used throughout the development process by different roles and for different purposes. This paper reports results of a case-study of the development process of automotive software at a Swedish vehicle manufacturer. The study investigates the use of modelling at different stages of the development process, from high-level product planning to low-level component requirements specifications.
|
|
