SwePub
Sök i SwePub databas

  Extended search

Träfflista för sökning "WFRF:(Heldal Rogardt 1964) "

Search: WFRF:(Heldal Rogardt 1964)

  • Result 1-50 of 80
Sort/group result
   
EnumerationReferenceCoverFind
1.
  • Peters, Anne-Kathrin, Dr. 1984-, et al. (author)
  • Sustainability in Computing Education : A Systematic Literature Review
  • 2024
  • In: ACM Transactions on Computing Education. - : Association for Computing Machinery (ACM). - 1946-6226. ; 24:1
  • Research review (peer-reviewed)abstract
    • Research shows that the global society as organized today, with our current technological and economic system, is impossible to sustain. We are living in an era in which human activities in highly industrialized countries are responsible for overshooting several planetary boundaries, with poorer communities contributing the least to the problems but being impacted the most. At the same time, technical and economic gains fail to provide society at large with equal opportunities and improved quality of life. This article describes approaches taken in computing education to address the issue of sustainability. It presents results of a systematic review of the literature on sustainability in computing education. From a set of 572 publications extracted from six large digital libraries plus snowballing, we distilled and analyzed 89 relevant primary studies. Using an inductive and deductive thematic analysis, we study (i) conceptions of sustainability, computing, and education; (ii) implementations of sustainability in computing education; and (iii) research on sustainability in computing education. We present a framework capturing learning objectives and outcomes as well as pedagogical methods for sustainability in computing education. These results can be mapped to existing standards and curricula in future work. We find that only a few of the articles engage with the challenges as calling for drastic systemic change, along with radically new understandings of computing and education. We suggest that future work should connect to the substantial body of critical theory, such as feminist theories of science and technology. Existing research on sustainability in computing education may be considered rather immature, as the majority of articles are experience reports with limited empirical research.
  •  
2.
  • Peters, Anne-Kathrin, Dr. 1984-, et al. (author)
  • Sustainability in Computing Education: A Systematic Literature Review
  • 2024
  • In: ACM Transactions on Computing Education. - : Association for Computing Machinery (ACM). - 1946-6226. ; 24
  • Journal article (peer-reviewed)abstract
    • Research shows that the global society as organized today, with our current technological and economic system, is impossible to sustain. We are living in an era in which human activities in highly industrialized countries are responsible for overshooting several planetary boundaries, with poorer communities contributing the least to the problems but being impacted the most. At the same time, technical and economic gains fail to provide society at large with equal opportunities and improved quality of life. This article describes approaches taken in computing education to address the issue of sustainability. It presents results of a systematic review of the literature on sustainability in computing education. From a set of 572 publications extracted from six large digital libraries plus snowballing, we distilled and analyzed 89 relevant primary studies. Using an inductive and deductive thematic analysis, we study (i) conceptions of sustainability, computing, and education; (ii) implementations of sustainability in computing education; and (iii) research on sustainability in computing education. We present a framework capturing learning objectives and outcomes as well as pedagogical methods for sustainability in computing education. These results can be mapped to existing standards and curricula in future work. We find that only a few of the articles engage with the challenges as calling for drastic systemic change, along with radically new understandings of computing and education. We suggest that future work should connect to the substantial body of critical theory, such as feminist theories of science and technology. Existing research on sustainability in computing education may be considered rather immature, as the majority of articles are experience reports with limited empirical research.
  •  
3.
  • Andersson, Malin, et al. (author)
  • Applying Task-based Division in Multi-layered Design - An Industrial Case Study
  • 2005
  • In: Proc. of The IASTED International Conference on Human-Computer Interaction (IASTED-HCI).
  • Journal article (peer-reviewed)abstract
    • The user interface often has a tendency to be too complex, e.g. provide more functionality than needed. By creating a Multi-Layered interface the complexity can be handled. Each layer is adapted to the user, e.g. tasks or knowledge. In this paper we show how the layers are obtained by using the concept of a Role Based Access Control(RBAC). The purpose of RBAC is to prevent any unauthorized user to maliciously destroy or access data. Though the choice of RBAC in this case was not primary to stop unauthorized ac cess to the system, but to stop the users in harming the data accidently. The field study was carried out at Volvo Aero Corporation(VAC) in Trollh¨attan, Sweden. The application built permitted several users from different organizations inside VAC to obtain and manipulate data concerning test ing of airplane engines. The fact that the system is currently in use shows the usefulness of the concept.
  •  
4.
  • Berger, Christian, 1980, et al. (author)
  • Model-based, Composable Simulation for the Development of Autonomous Miniature Vehicles
  • 2013
  • In: Mod4Sim'13: 3rd International Workshop on Model-driven Approaches for Simulation Engineering at SCS/IEEE Symposium on Theory of Modeling and Simulation in conjunction with SpringSim 2013. - 0735-9276. - 9781627480321 ; 45, s. 118-125
  • Conference paper (peer-reviewed)abstract
    • Modern vehicles contain nearly 100 embedded control units to realize various comfort and safety functions. These vehicle functions consist of a sensor, a data processing, and an actor layer to react intelligently to stimuli from their context. Recently, these sensors do not only perceive data from the own vehicle but more often also data from the vehicle's surroundings to understand the current traffic situation. Thus, traditional development and testing processes need to be rethought to ensure the required quality especially for safety-critical systems like a collision prevention system. On the example of 1:10 scale model cars, we outline our model-based and composable simulation approach that enabled the virtualized development of autonomous driving capabilities for model cars to compete in an international competition.
  •  
5.
  • Burden, Håkan, 1976, et al. (author)
  • Assessing individuals in team projects: A case study from computer science
  • 2011
  • In: Conference on Teaching and Learning - KUL.
  • Conference paper (peer-reviewed)abstract
    • In this paper we describe an ongoing action research (Kember & Gow, 1992) project to improve teaching and learning in the course “Model-driven software development” given by Computer Science and Engineering. It is a project-based course and after taking the course the students should be better able to analyse and specify software through models. There were two drivers for the course reform. Before the reform in 2009, the software models were used in an informal way and therefore it was hard to validate the correctness of the system from them. The students were instead assessed through a final written exam even if most of the work was done in the team project. But from contacts with industry, we got hold of a tool that enables testing and verification of model behaviour. So it was now possible to assess the teams by testing their models. The second driver for the reform was John Biggs’ idea of constructive alignment (Biggs, 1996). The idea is that there should be a consistency between the learning objectives, the teaching methods and the assessment methods. If the assessment methods, in particular, do not match the learning objectives students tend to take a surface approach to learning. Since this was a project course we wanted our assessments to be more focused on the project, so we dropped the written exam. The question then became: How can we assign fair grades to individual members of the teams? We introduced a variety of new assessment methods in order to better judge the contribution of each student and what they had learned during the course. These methods comprised: voluntary written exams, peer assessment (grading and ranking of team members, and mid-course review of a report by another team), self assessment and an oral group exam at the end of the course. By introducing these new assessment methods, the purpose of assessment in the course shifted from being only summative (i.e. assigning a grade at the end of the course) to also being formative (i.e. helping the students to learn during the whole course). From the course evaluations we could draw several conclusions. Overall, the students were satisfied with the new assessment package. Only a few of them wanted a written exam at the end. This is encouraging since it was the first time the reformed course was given and many things were new both to the students and the teachers. Most of the students found the voluntary exams to be helpful, but the peer assessment part turned out to be more controversial. The mid-course review of reports by other teams was only mentioned in positive terms, while all the comments on peer grading/ranking were negative. The students did not mind criticizing each other face-to-face but found it disturbing to grade each other anonymously. In general, they also found it difficult to evaluate team members and the reports by other teams. And most of them believed that they were doing the job of the teacher when grading/ranking the team members. From a teacher's point of view, the new assessment package is more efficient. We are now more confident in the grades we are giving. Moreover, it did not take more time to use the new assessment methods compared to using the written exam. Finally, the work we put into assessment is now done during the course, not after. Action research consists of a spiral of cycles, where each cycle involves a new process of problem solving, generated by the previous cycle. We have only completed the first cycle. A key lesson from the first cycle is the importance of making the assessment process and criteria clear to the students at the beginning of the course. In the next cycle, we will address the following questions: What models have other teachers used for assigning grades to individual students in team projects? Is it possible to improve the peer assessment part? How can we give more rapid feedback on the voluntary exams? How can we make the most of the oral group exam? The review by Segers et al. (2003) will provide us with a starting point for a more extensive exploration of the literature in the area. References Biggs (1996). Enhancing teaching through constructive alignment. Higher Education, 32, 347-364. Kember & Gow (1992). Action research as a form of staff development in higher education. Higher Education, 23, 297-310. Segers, Dochy & Cascallar (2003). Optimising new modes of assessment. Kluwer Academic Publishers.
  •  
6.
  • Burden, Håkan, 1976, et al. (author)
  • Assessing individuals in team projects: A case study from computer science
  • 2011
  • In: Conference on Teaching and Learning - KUL.
  • Conference paper (peer-reviewed)abstract
    • In this paper we describe an ongoing action research (Kember & Gow, 1992) project to improve teaching andlearning in the course “Model-driven software development” given by Computer Science and Engineering. It isa project-based course and after taking the course the students should be better able to analyse and specifysoftware through models.There were two drivers for the course reform. Before the reform in 2009, the software models were used in aninformal way and therefore it was hard to validate the correctness of the system from them. The students wereinstead assessed through a final written exam even if most of the work was done in the team project. But fromcontacts with industry, we got hold of a tool that enables testing and verification of model behaviour. So it wasnow possible to assess the teams by testing their models. The second driver for the reform was John Biggs’ ideaof constructive alignment (Biggs, 1996). The idea is that there should be a consistency between the learningobjectives, the teaching methods and the assessment methods. If the assessment methods, in particular, donot match the learning objectives students tend to take a surface approach to learning. Since this was a projectcourse we wanted our assessments to be more focused on the project, so we dropped the written exam.The question then became: How can we assign fair grades to individual members of the teams? We introduceda variety of new assessment methods in order to better judge the contribution of each student and what theyhad learned during the course. These methods comprised: voluntary written exams, peer assessment (gradingand ranking of team members, and mid-course review of a report by another team), self assessment and anoral group exam at the end of the course. By introducing these new assessment methods, the purpose ofassessment in the course shifted from being only summative (i.e. assigning a grade at the end of the course) toalso being formative (i.e. helping the students to learn during the whole course).From the course evaluations we could draw several conclusions. Overall, the students were satisfied with thenew assessment package. Only a few of them wanted a written exam at the end. This is encouraging since itwas the first time the reformed course was given and many things were new both to the students and theteachers. Most of the students found the voluntary exams to be helpful, but the peer assessment part turnedout to be more controversial. The mid-course review of reports by other teams was only mentioned in positiveterms, while all the comments on peer grading/ranking were negative. The students did not mind criticizingeach other face-to-face but found it disturbing to grade each other anonymously. In general, they also found itdifficult to evaluate team members and the reports by other teams. And most of them believed that they weredoing the job of the teacher when grading/ranking the team members.From a teacher's point of view, the new assessment package is more efficient. We are now more confident inthe grades we are giving. Moreover, it did not take more time to use the new assessment methods comparedto using the written exam. Finally, the work we put into assessment is now done during the course, not after.Action research consists of a spiral of cycles, where each cycle involves a new process of problem solving,generated by the previous cycle. We have only completed the first cycle. A key lesson from the first cycle is theimportance of making the assessment process and criteria clear to the students at the beginning of the course.In the next cycle, we will address the following questions: What models have other teachers used for assigninggrades to individual students in team projects? Is it possible to improve the peer assessment part? How can wegive more rapid feedback on the voluntary exams? How can we make the most of the oral group exam? Thereview by Segers et al. (2003) will provide us with a starting point for a more extensive exploration of theliterature in the area.ReferencesBiggs (1996). Enhancing teaching through constructive alignment. Higher Education, 32, 347-364.Kember & Gow (1992). Action research as a form of staff development in higher education. Higher Education, 23, 297-310.Segers, Dochy & Cascallar (2003). Optimising new modes of assessment. Kluwer Academic Publishers.
  •  
7.
  • Burden, Håkan, 1976, et al. (author)
  • Comparing and Contrasting Model-Driven Engineering at Three Large Companies
  • 2014
  • In: Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement. - New York, NY, USA : Association for Computing Machinery (ACM). - 1949-3789 .- 1949-3770. - 9781450327749
  • Conference paper (peer-reviewed)abstract
    • Hutchinson et al. conducted an interview-based study of how model-driven engineering, MDE, is practiced in 17 companies. Their results include that successful MDE companies develop domain-specific languages; are motivated by a clear business case; and are committed at all levels of the organization. Goal: Whilst the results are useful, the study is a very broad one, with one or two interviewees per company. This paper supplements Hutchinson's study by focusing on three large companies that are applying MDE and undergoing a parallel transition to agile methods. Method: Formal data collection strategies -- 25 semi-structured interviews, observations and progress meetings -- were combined with informal interaction. The data was analysed both inductively for new insights and deductively for comparison with the results of Hutchinson et al. Results: Our findings show how MDE can include domain experts in software development and how agile development and MDE can coexist. In general our results validate the findings of Hutchinson et al. There are two areas where our results differ -- the engineers' sense of control and the appropriateness of their skills and training. Conclusions: Using a combination of data collection strategies and analysis techniques our study casts new light on earlier research as well as contributes with novel insights regarding the adoption of MDE.
  •  
8.
  •  
9.
  • Burden, Håkan, 1976, et al. (author)
  • Executable and Translatable UML - How Difficult Can It Be?
  • 2011
  • In: 18th Asia Pacific Software Engineering Conference, APSEC 2011; Ho Chi Minh; Viet Nam; 5 December 2011 through 8 December 2011. - 1530-1362. - 9781457721991 ; , s. 114-121
  • Conference paper (peer-reviewed)abstract
    • Executable and Translatable UML enables Model-Driven Architecture by specifying Platform-Independent Models that can be automatically transformed into Platform-Specific Models through model compilation. Previous research shows that the transformations result in both efficient code and consistency between the models. However, there are neither results for the effort of introducing the technology in a new context nor on the level of expertise needed for designing the Platform-Independent Models. We wanted to know if teams of novice software developers could design Executable and Translatable UML models without prior experiences of software modelling. As part of a new university course we conducted an exploratory case study with two data collections over two years. Bachelor students were given the task to design a hotel reservation system and the necessary test cases for verifying the functionality and structure of the models within 300 hours, using Executable and Translatable UML. In total, 43 out of 50 teams succeeded in delivering verified and consistent models within the time frame. During the second data collection the students were given limited tool training. This gave a raise in the quality of the models. Due to the executable feature of the models the students were given constant feedback on their design until the models behaved as expected, with the required level of detail and structure. Our results show that using Executable and Translatable UML does not require more expertise than a bachelor program in computer science. All in all, Executable and Translatable UML could play an important role in future software development.
  •  
10.
  • Burden, Håkan, 1976, et al. (author)
  • Industrial Experiences from Multi-Paradigmatic Modelling of Signal Processing
  • 2012
  • In: 6th International Workshop on Multi-Paradigm Modeling, MPM 2012; Innsbruck; Austria; 1 October 2012 through 1 October 2012. - New York, NY, USA : ACM. - 9781450318051 ; , s. 7-12
  • Conference paper (peer-reviewed)abstract
    • Embedded software is often composed of interacting domains. A common problem is that the implementation intertwines the different domain solutions with each other and the platform-specific details. The result is a code mass that is hard to understand, maintain and reuse. We report on an effort to overcome these problems by using a domain-specific executable modelling language for each included domain. The application was delivered for the Ericsson LTE-A uplink test bed as part of the 4G telecommunications system that was presented at the Mobile World Congress in Barcelona, February 2011. The requirements for the delivered software included efficient real-time performance for signal processing on new hardware as well as a firm non-negotiable delivery deadline. Our results show that the chosen modelling languages allowed independent implementation and validation of each domain. Neither did the integration of the separate solutions imply additional problems.
  •  
11.
  • Burden, Håkan, 1976, et al. (author)
  • Natural Language Generation from Class Diagrams
  • 2011
  • In: MoDeVVa 2011, MoDELS Workshop on Model-Driven Engineering, Verification and Validation. - New York, NY, USA : ACM. - 9781450309141
  • Conference paper (peer-reviewed)abstract
    • A Platform-Independent Model (PIM) is supposed to capture the requirements specified in the Computational Independent Model (CIM). It can be hard to validate that this is the case since the stakeholders might lack the necessary training to access the information of the software models in the PIM. In contrast, a description of the PIM in natural language will enable all stakeholders to be included in the validation. We have conducted a case study to investigate the possibilities to generate natural language text from Executable and Translatable UML. In our case study we have considered a static part of the PIM; the structure of the class diagram. The transformation was done in two steps. In the first step, the class diagram was transformed into an intermediate linguistic model using Grammatical Framework. In the second step, the linguistic model is transformed into natural language text. The PIM was enhanced in such a way that the generated texts can both paraphrase the original software models as well as include the underlying motivations behind the design decisions.
  •  
12.
  •  
13.
  •  
14.
  •  
15.
  •  
16.
  •  
17.
  •  
18.
  • Burden, Håkan, 1976, et al. (author)
  • Translating Platform-Independent Code into Natural Language Texts
  • 2013
  • In: MODELSWARD 2013, 1st International Conference on Model-Driven Engineering and Software Development. - 9789898565426 ; , s. 281-290
  • Conference paper (peer-reviewed)abstract
    • Understanding software artifacts is not only time-consuming, without the proper training and experience it can be impossible. From a model-driven perspective there are two benefits from translating platform-independent models into natural language texts: First, the non-functional properties of the solution have already been omitted meaning that the translations focus on describing the functional behaviour of the system. Second, the platform-independent models are reusable across platforms and so are the translations generated from them. As a proof-of-concept a platform-independent Action language is translated into natural language texts through the framework of model transformations.
  •  
19.
  • Eliasson, Ulf, 1984, et al. (author)
  • Agile Model-Driven Engineering in Mechatronic Systems - An Industrial Case Study
  • 2014
  • In: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer International Publishing. - 1611-3349 .- 0302-9743. - 9783319116532 ; 8767, s. 433-449
  • Journal article (peer-reviewed)abstract
    • Model-driven engineering focuses on structuring systems as well as permitting domain experts to be directly involved in the software development. Agile methods aim for fast feedback and providing crucial knowledge early in the project. In our study, we have seen a successful combination of MDE and agile methods to support the development of complex, software-driven mechatronic systems. We have investigated how combining MDE and agile methods can reduce the number of issues caused by erroneous assumptions in the software of these mechatronic systems. Our results show that plant models to simulate mechanical systems are needed to enable agile MDE during the mechatronic development. They enable developers to run, verify, and validate models before the mechanical systems are delivered from suppliers. While two case studies conducted at Volvo Car Group confirm that combining MDE and agile works, there are still challenges e.g. how to optimize the development of plant models.
  •  
20.
  • Eliasson, Ulf, 1984, et al. (author)
  • Architecting in the Automotive Domain: Descriptive vs Prescriptive Architecture
  • 2015
  • In: 12th Working IEEE/IFIP Conference on Software Architecture (WICSA), 2015. - : IEEE. - 9781479919222 ; , s. 115-118
  • Conference paper (peer-reviewed)abstract
    • To investigate the new requirements and challenges of architecting often safety critical software in the automotive domain, we have performed two case studies on Volvo Car Group and Volvo Group Truck Technology. Our findings suggest that automotive software architects produce two different architectures (or views) of the same system. The first one is a high-level descriptive architecture, mainly documenting system design decisions and describing principles and guidelines that should govern the overall system. The second architecture is the working architecture, defining the actual blueprint for the implementation teams and being used in their daily work. The working architecture is characterized by high complexity and considerably lower readability than the high-level architecture. Unfortunately, the team responsible for the high-level architecture tends to get isolated from the rest of the development organization, with few communications except regarding the working architecture. This creates tensions within the organizations, sub-optimal design of the communication matrix and limited usage of the high-level architecture in the development teams. To adapt to the current pace of software development and rapidly growing software systems new ways of working are required, both on technical and on an organizational level.
  •  
21.
  • Eliasson, Ulf, 1984, et al. (author)
  • The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group
  • 2015
  • In: 23rd IEEE International Requirements Engineering Conference, RE 2015, Ottawa, Canada, 24-28 August. - : IEEE. - 9781467369053
  • Conference paper (peer-reviewed)abstract
    • The automotive industry is currently going through an enormous change, transitioning from being pure hardware and mechanical companies to becoming more software focused. Currently, software development is embedded into a V-Model process that defines how software requirements are extracted from system requirements. In recent years, OEMs have come to recognize the importance and opportunities offered by software, which include better management and shorter time-to-market of distinguishing features. Strategies to better utilize software include in-house software development and new ways to collaborate with suppliers. However, in their effort to take advantage of these opportunities, engineers struggle with the formal process imposed on software development. In this paper, we investigate the impact of this struggle on the flow of requirements, including challenges and practices. We found that new ways of working with requirements had emerged that are partly not supported, partly hindered by the old tooling and processes for requirements engineering. Requirements flow both vertical and horizontal in the organization and across the supply-chain. Support for the new way of working should allow us to refine requirements iteratively throughout their life-cycle, handle the discussion of rationales, and to manage assumptions. We found strategies of achieving this to differ not only between OEMs, but also between different divisions inside the OEMs.
  •  
22.
  • Etemaadi, Ramin, et al. (author)
  • Quality-Driven Optimization of System Architecture : Industrial Case Study on an Automotive Sub-System
  • 2013
  • In: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 86:10, s. 2559-2573
  • Journal article (peer-reviewed)abstract
    • Due to the complexity of today's embedded systems and time-to-market competition between companies developing embedded systems, system architects have to perform a complex task. To design a system which meets all its quality requirements becomes increasingly difficult because of customer demand for new innovative user functions. Methods and tools are needed to assist the architect during system design. The goal of this paper is to show how metaheuristic optimization approaches can improve the process of designing efficient architectures for a set of given quality attributes. A case study is conducted in which an architecture optimization framework is applied to an existing sub-system in the automotive industry. The case study shows that metaheuristic optimization approaches can find efficient solutions for all quality attributes while fulfilling given constraints. By optimizing multiple quality attributes the framework proposes revolutionary architecture solutions in contrast to human architects, who tend to propose solutions based on previous architectures. Although the case study shows savings in manual effort, it also shows that the proposed architecture solutions should be assessed by the human architect. So, the paper demonstrates how an architecture optimization framework complements the domain knowledge and experience of the architect.
  •  
23.
  • Franch, Xavier, et al. (author)
  • How do Practitioners Perceive the Relevance of Requirements Engineering Research? An Ongoing Study
  • 2017
  • In: 2017 IEEE 25TH INTERNATIONAL REQUIREMENTS ENGINEERING CONFERENCE (RE). - : IEEE. - 2332-6441. - 9781538631911 ; , s. 382-387
  • Conference paper (peer-reviewed)abstract
    • The relevance of Requirements Engineering (RE) research to practitioners is a prerequisite for problem-driven research in the area and key for a long-term dissemination of research results to everyday practice. To understand better how industry practitioners perceive the practical relevance of RE research, we have initiated the RE-Pract project, an international collaboration conducting an empirical study. This project opts for a replication of previous work done in two different domains and relies on survey research. To this end, we have designed a survey to be sent to several hundred industry practitioners at various companies around the world and ask them to rate their perceived practical relevance of the research described in a sample of 418 RE papers published between 2010 and 2015 at the RE, ICSE, FSE, ESEC/FSE, ESEM and REFSQ conferences. In this paper, we summarize our research protocol and present the current status of our study and the planned future steps.
  •  
24.
  • Gencel, Cigdem, et al. (author)
  • On the Relationship between Different Size Measures in the Software Life Cycle
  • 2009
  • In: 16th Asia-Pacific Software Engineering Conference, APSEC 2009; Penang; Malaysia; 1 December 2009 through 3 December 2009. - Penang, Malaysia : IEEE Computer Society. - 1530-1362. - 9780769539096 ; , s. 19-26
  • Conference paper (peer-reviewed)abstract
    • Various measures and methods have been developed to measure the sizes of different software entities produced throughout the software life cycle. Understanding the nature of the relationship between the sizes of these products has become significant due to various reasons. One major reason is the ability to predict the size of the later phase products by using the sizes of early life cycle products. For example, we need to predict the Source Lines of Code (SLOC) from Function Points (FP) since SLOC is being used as the main input for most of the estimation models when this measure is not available yet. SLOC/FP ratios have been used by the industry for such purposes even though the assumed linear relationship has not been validated yet. Similarly, FP has recently started to be used to predict the Bytes of code for estimating the amount of spare memory needed in systems. In this paper, we aim to investigate further the nature of the relationship between the software functional size and the code size by conducting a series of empirical studies.
  •  
25.
  • Giese, Martin, 1970, et al. (author)
  • From Informal to Formal Specifications in UML
  • 2004
  • 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. - 3540233075 ; 3273, s. 197-211
  • Journal article (peer-reviewed)abstract
    • In this paper, we consider a way of bridging informal and formal specification. Most projects have a need for an informal description of the requirements of the system which all people involved can understand. At the same time, there is a need to make some of the requirements more formal. We present a way to relate informal requirements, in form of use cases, to more formal specifications, written in the Object Constraint Language (OCL). Our approach gives the customers of software systems a way of guiding the development of formal specifications. Conversely, the formal specification can improve the informal understanding of the system by exposing gaps and ambiguities in the informal specification.
  •  
26.
  •  
27.
  • Heldal, Rogardt, 1964 (author)
  • Bridging model-based and language-based security
  • 2003
  • In: Computer Security - ESORICS 2003, 8th European Symposium on Research in Computer Security, Gjøvik, Norway, October 13-15. Proceedings. Lecture Notes in Computer Science. - 3540203001 ; 2808, s. 235-252
  • Conference paper (peer-reviewed)abstract
    • We present a way to support the development of software applications that takes into account confidentiality issues, and how the developed code can be automatically verified. We use the Unified Modelling Language (UML) together with annotations to permit confidentiality to be considered during the whole development process from requirements to code. We have provided support for software development using UML diagrams so that the code produced can be be validated by a language-based checker, in our case Jif (Java information flow). We demonstrate that the combination of model-based and language-based security is compelling.
  •  
28.
  • Heldal, Rogardt, 1964, et al. (author)
  • Customer Validation of Formal Contracts
  • 2006
  • In: Technical Reports of the Technische Universität Dresden. - 1430-211X.
  • Conference paper (peer-reviewed)abstract
    • This paper shows how to write formal OCL contracts for system operations in such way that a translation to natural language (a subset of English), understandable by a customer, can be obtained automatically. To achieve natural language text understandable by a customer we use the vocabulary of the problem domain when writing formal contracts for system operations. The benefits of our approach are that we increase the precision of the model by using formal specifications, and that a customer is able to validate (by viewing the natural language rendering) if a contract actually describes the behavior desired from the system. Without validation of this kind there is generally no guarantee that the formal specification states the correct properties.
  •  
29.
  •  
30.
  • Heldal, Rogardt, 1964, et al. (author)
  • Descriptive vs Prescriptive Models in Industry
  • 2016
  • In: Proceedings of the ACM/IEEE 19th International Conference on Model Driven Engineering Languages and Systems (MODELS 2016). - New York, NY, USA : ACM. - 9781450343213 ; , s. 216-226
  • Conference paper (peer-reviewed)abstract
    • To understand the importance, characteristics, and limitations of modeling we need to consider the context where models are used. Different organizations within the same company can use models for different purposes and modelling can involve different stakeholders and tools. Recently, several papers discussing how industries use MDE have been published and they have contradictory findings. In this paper we report lessons learned from our collaborations with three large companies. We found that it is important to distinguish between descriptive models (used for documentation) and prescriptive models (used for development) to better understand the adoption of modelling in industry. Our findings are valuable for both academia and industry. A better understanding of modeling in large companies can help academia conceiving innovative MDE solutions that can have a real impact in industry. On the other hand, industry can better understand how to properly exploit MDE and what to expect from it.
  •  
31.
  • Heldal, Rogardt, 1964, et al. (author)
  • Estimation of Real-Time Software Code Size using COSMIC FSM
  • 2009
  • In: 12th IEEE International Symposium on Object/Component/sevice-oriented Real-time distributed Computing. - 1555-0885. - 9780769535739 ; , s. 244-248
  • Conference paper (peer-reviewed)abstract
    • For distributed networks which will be mass produced, such as computer systems in modern vehicles, it is crucial to find cost efficient hardware. A distributed network in a vehicle consists of several ECUs (electronic control unit). In this paper we consider the amount of memory needed for these ECUs. They should contain enough memory to survive several software generations, without inducing unnecessary cost of too much memory. Our earlier work shows that UML component diagrams can be used to collect enough information for estimating memory size using a functional size measurement method. This paper replicates our earlier experiment with more software components of a different type. We compare the results from the two experiments.
  •  
32.
  • Heldal, Rogardt, 1964, et al. (author)
  • Limits of Model Transformations for Embedded Software
  • 2012
  • In: SEW-35, The 35th Annual IEEE Software Engineering Workshop.
  • Conference paper (peer-reviewed)abstract
    • We report on an effort to use executable modeling languages for developing software for the Ericsson LTE-A uplink test bed. The test bed was a part of a 4G telecommunications system, that was presented at the Mobile World Congress in Barcelona, February 2011. The requirements for the delivered software included efficient real-time performance for signal processing on new hardware as well as a firm non-negotiable delivery deadline. Our results show that the existing model transformations were not efficient enough on the new platform and that model transformations across paradigms is a challenging task; to meet the deadline and the requirements the generated code had to be manually optimised.
  •  
33.
  • Heldal, Rogardt, 1964, et al. (author)
  • Modeling executable test actors: Exploratory study done in executable and translatable UML
  • 2012
  • In: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - 1530-1362. - 9780769549224 ; 1, s. 784-789
  • Conference paper (peer-reviewed)abstract
    • Model-based testing presents new challenges in how to perform software testing due to the fact that models offer testing on several abstraction levels. This is largely an unexplored area. We propose a pattern to construct test actors which can be used to test Platform-Independent Models. In addition, these test actors can also be automatically transformed to Platform-Specific Model level to test the implementation deployed on target. Our work is one step in the direction of permitting early testing without any waste, since the test models can be reused at a lower level of abstraction.
  •  
34.
  • Heldal, Rogardt, 1964, et al. (author)
  • Sustainability competencies and skills in software engineering: An industry perspective
  • 2024
  • In: Journal of Systems and Software. - 0164-1212. ; 211
  • Journal article (peer-reviewed)abstract
    • Context: Achieving the UN Sustainable Development Goals (SDGs) demands a shift by industry, governments, society, and individuals to reach adequate levels of awareness and actions to address sustainability challenges. Software systems will play an important role in moving towards these targets. Sustainability skills are necessary to support the development of software systems and to provide sustainable IT-supported services for citizens. Gap: While there is a growing number of academic bodies including sustainability education in engineering and computer science curricula, there is not yet comprehensive research on the competencies and skills required by IT professionals to develop such systems. Research goal: This study aims to identify the industrial sustainability needs for education and training from software engineers’ perspective. For this, we answer the following questions: (1) what are the interests of organisations with an IT division with respect to sustainability? (2) what do organisations want to achieve with respect to sustainability, and how? and (3) what are the sustainability-related competencies and skills that organisations need to achieve their sustainability goals? Methodology: We conducted a qualitative study with interviews and focus groups with experts from twenty-eight organisations with an IT division from nine countries to understand their interests, goals, and achievements related to sustainability, and the skills and competencies needed to achieve their goals. Results: Our findings show that organisations are interested in sustainability, both idealistically and increasingly for core business reasons. They seek to improve the sustainability of software processes and products but encounter difficulties, like the trade-off between short-term financial profitability and long-term sustainability goals or an unclear understanding of sustainability concepts from a software engineering perspective. To fill these gaps, they have promoted in-house training courses, collaborated with universities, and sent employees to external training. The acquired competencies should support translating environmental and social benefits into economic ones and make sustainability an integral part of software development.
  •  
35.
  • Heldal, Rogardt, 1964, et al. (author)
  • Sustainability competencies and skills in software engineering: An industry perspective
  • 2024
  • In: Journal of Systems and Software. - 0164-1212. ; 211
  • Journal article (peer-reviewed)abstract
    • Context: Achieving the UN Sustainable Development Goals (SDGs) demands a shift by industry, governments, society, and individuals to reach adequate levels of awareness and actions to address sustainability challenges. Software systems will play an important role in moving towards these targets. Sustainability skills are necessary to support the development of software systems and to provide sustainable IT-supported services for citizens. Gap: While there is a growing number of academic bodies including sustainability education in engineering and computer science curricula, there is not yet comprehensive research on the competencies and skills required by IT professionals to develop such systems. Research goal: This study aims to identify the industrial sustainability needs for education and training from software engineers’ perspective. For this, we answer the following questions: (1) what are the interests of organisations with an IT division with respect to sustainability? (2) what do organisations want to achieve with respect to sustainability, and how? and (3) what are the sustainability-related competencies and skills that organisations need to achieve their sustainability goals? Methodology: We conducted a qualitative study with interviews and focus groups with experts from twenty-eight organisations with an IT division from nine countries to understand their interests, goals, and achievements related to sustainability, and the skills and competencies needed to achieve their goals. Results: Our findings show that organisations are interested in sustainability, both idealistically and increasingly for core business reasons. They seek to improve the sustainability of software processes and products but encounter difficulties, like the trade-off between short-term financial profitability and long-term sustainability goals or an unclear understanding of sustainability concepts from a software engineering perspective. To fill these gaps, they have promoted in-house training courses, collaborated with universities, and sent employees to external training. The acquired competencies should support translating environmental and social benefits into economic ones and make sustainability an integral part of software development.
  •  
36.
  • Heldal, Rogardt, 1964 (author)
  • The Treatment of Polymorphism and Modules in a Partial Evaluator
  • 2001
  • Doctoral thesis (other academic/artistic)abstract
    • In this thesis we study aspects of specialisation by partial evaluation and compiler generation. After significant research during the last two decades, there are now powerful specialisers for several programming languages, such as LISP, Scheme, ML, and C. But some features of programming languages are still not handled by specialisers. We consider two such features: polymorphic types and modules. In our formalism of the binding-time analyser, we provide a solution to how to treat coercions in the context of polymorphism: coercions are used to make values more dynamic. Furthermore, since the semantics of the partial evaluator affect the binding-time analyser, we have formalised both the binding-time rules and the specialiser. We also discuss practical issues arising from our integration of a polymorphic binding-time analyser with a specialiser: the treatment of fix-points, program points, and bounded static variation. Where modules are concerned, we consider specialising a program consisting of several modules into a specialised version that also consists of several modules. This work relies heavily on a polymorphic binding-time analyser and a compiler generator. The polymorphic binding-time analyser works independently on each module. For each annotated module, we use a compiler generator to create a generating extension. Then we build generating extensions for complete programs, in much the same way as the original modules were put together into complete programs. The result of running all generating extensions is a collection of residual modules, which have a structure derived from the original program. But modules cause another problem. Previous specialisers produced a program consisting of one module, derived from a source program of one module. It is a weakness that the program being specialised imposes a limitation on the structure of the program generated, in this case, the number of modules. In this thesis we remove the restriction. Since we can obtain many modules by specialising one module, we remove an ``inherited limit'' on the total number of modules. In this work, we need new types of annotation to control the specialisation. We have formalised a binding-time analyser for finding such annotations. We have also given the semantics of the partial evaluator.
  •  
37.
  • Heldal, Rogardt, 1964 (author)
  • Use Cases are more than System Operations
  • 2005
  • In: 2nd International Workshop on Use Case Modeling (WUsCaM-05).
  • Conference paper (peer-reviewed)abstract
    • Abstract. Correctly written use cases can be an important artifact for describing how a software system should behave. Use cases should be informal enough to permit anyone in a software project to understand them, in particular the customer (often lacking a formal background). One consequence of adopting use cases to, for example, MDA (Model Driven Architecture) can be an increasing level of formalism, which can severely limit understanding of use cases. Also, too few guidelines for how to write use cases make them both hard to write and understand. Finding the right level of formalism is the topic of this paper. We suggest a new way of writing the action steps of use cases by introducing action blocks. The introduction of action blocks makes use cases more formal, but still understandable. In addition, action blocks supports the creation of contracts for system operations. In this paper we also argue that treating system operations as use cases is a misuse of use cases system operations and use cases should be separate artifacts. One should be able to obtain several system operations from a use case, otherwise there is no dialog (process) between actors and use cases. We believe that having a clear distinction between use cases and contracts will improve the quality of both.
  •  
38.
  • Klunder, J., et al. (author)
  • Catching up with Method and Process Practice: An Industry-Informed Baseline for Researchers
  • 2019
  • In: IEEE/ACM 41st International Conference on Software Engineering, 25-31 May 2019: Software Engineering in Practice (ICSE-SEIP). - : IEEE. - 9781728117607
  • Conference paper (peer-reviewed)abstract
    • Software development methods are usually not applied by the book. Companies are under pressure to continuously deploy software products that meet market needs and stakeholders' requests. To implement efficient and effective development processes, companies utilize multiple frameworks, methods and practices, and combine these into hybrid methods. A common combination contains a rich management framework to organize and steer projects complemented with a number of smaller practices providing the development teams with tools to complete their tasks. In this paper, based on 732 data points collected through an international survey, we study the software development process use in practice. Our results show that 76.8% of the companies implement hybrid methods. Company size as well as the strategy in devising and evolving hybrid methods affect the suitability of the chosen process to reach company or project goals. Our findings show that companies that combine planned improvement programs with process evolution can increase their process' suitability by up to 5%.
  •  
39.
  • Klünder, Jil, et al. (author)
  • Catching up with Method and Process Practice: An Industry-Informed Baseline for Researchers
  • 2019
  • In: Proceedings - 2019 IEEE/ACM 41st International Conference on Software Engineering: Software Engineering in Practice, ICSE-SEIP 2019. ; May 2019, s. 255-264
  • Conference paper (peer-reviewed)abstract
    • Software development methods are usually not applied by the book.companies are under pressure to continuously deploy software products that meet market needs and stakeholders' requests. To implement efficient and effective development processes, companies utilize multiple frameworks, methods and practices, and combine these into hybrid methods. A common combination contains a rich management framework to organize and steer projects complemented with a number of smaller practices providing the development teams with tools to complete their tasks. In this paper, based on 732 data points collected through an international survey, we study the software development process use in practice. Our results show that 76.8% of the companies implement hybrid methods.company size as well as the strategy in devising and evolving hybrid methods affect the suitability of the chosen process to reach company or project goals. Our findings show that companies that combine planned improvement programs with process evolution can increase their process' suitability by up to 5%.
  •  
40.
  • Knauss, Eric, 1977, et al. (author)
  • Continuous Integration Beyond the Team: A Tooling Perspective on Challenges in the Automotive Industry
  • 2016
  • In: Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM '16). - New York, NY, USA : ACM. - 1949-3770 .- 1949-3789. - 9781450344272
  • Conference paper (peer-reviewed)abstract
    • The practice of Continuous Integration (CI) has a big impact on how software is developed today. Shortening integration and feedback cycles promises to increase software quality, feature throughput, and customer satisfaction. Thus, it is not a surprise that companies try to embrace CI in domains where it is rather difficult to implement. In this paper we present our findings from two rounds of interviews with a car manufacturer on the use of tools in system engineering and how these tools would support wider adoption of CI. Our findings suggest a complex tool landscape with immense requirements that are not easily fulfilled by existing tools; this holds also for tools that well support CI in other domains. From this notion, we fur- ther explore what makes the automotive domain challeng- ing when it comes to CI (namely complexity of system and value chain). We hope that our findings will help address such challenges.
  •  
41.
  • Kuhrmann, Marco, et al. (author)
  • What Makes Agile Software Development Agile
  • 2022
  • In: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520. ; 48:9, s. 3523-3539
  • Journal article (peer-reviewed)abstract
    • Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.
  •  
42.
  • Liebel, Grischa, 1987, et al. (author)
  • For Free: Continuity and Change by Team Teaching
  • 2017
  • In: Teaching in Higher Education. - : Informa UK Limited. - 1356-2517 .- 1470-1294. ; 22:1, s. 62-77
  • Journal article (peer-reviewed)abstract
    • Team teaching is advocated in education to offer students multiple explanations to complex concepts and to improve teacher development. However, team teaching is typically associated with high staff cost due to the increased amount of teachers involved. The authors argue that team teaching can be conducted in a cheap way by including novice teaching assistants in the lectures and train them ‘on the job’. Additionally, novice assistants cause reflection on action and prevent a mechanization of the course. The authors use Brookfield’s four lenses to reflect on the application of team teaching in a Swedish undergraduate course on software modeling over three years, involving 3 teachers and collecting evaluation data from close to 400 students. The reflection shows that team teaching can be used as a cost-effective way to introduce novice teachers to a course, while at the same time receiving benefits from their participation in lectures and course development.
  •  
43.
  • Liebel, Grischa, 1987, et al. (author)
  • Impact of the use of industrial modelling tools on modelling education
  • 2016
  • In: 29th IEEE Conference on Software Engineering Education and Training, CSEEandT 2016; Dallas; United States; 5 April 2016 through 6 April 2016. - : IEEE. - 9781509007653 ; , s. 18-27
  • Conference paper (peer-reviewed)abstract
    • It has been stated that industrial-grade modelling tools are unsuitable for teaching modelling. We assume, however, that the experiences of the teachers and the students is strongly connected to the support available. In this paper, we present our experience with a university course on software modelling. In the first year of the course, we used a commercial modelling tool, in the second year the open-source alternative Papyrus. Our quantitative analysis shows that the industrial-grade modelling tools with all their complexity did not have a negative impact on the students' experience of modelling. We analyse why our experience differs from published accounts and conclude that the availability of a tool champion and tailored instruction material is key. From this, we derive lessons learned and give recommendations on how to successfully use industrial-strength modelling tools in the classroom.
  •  
44.
  • Liebel, Grischa, 1987, et al. (author)
  • Model Driven Software Engineering in Education: A Multi-Case Study on Perception of Tools and UML
  • 2017
  • In: 30th IEEE Conference on Software Engineering Education and Training (CSEE&T). ; 2017-January
  • Conference paper (peer-reviewed)abstract
    • While several benefits of using models in software engineering have been observed in practice, the adoption of modeling remains low. Multiple challenges of using models, especially related to tools, have been reported both for industrial use and for education. However, there is a lack of systematic, empirical investigations of the challenges in modeling education and their relation to industrial challenges. Therefore, we conducted a multiple-case study with two cases, in the U.S and Sweden, focusing on students' perceptions towards tooling and UML in education. Our data collected from 369 student evaluation surveys, enriched with qualitative data, shows that the students' perception of modeling tools depends not only on the complexity of tools, but rather on multiple contextual factors, including tool characteristics, scope of course and project contents, nature of the required models, and the tools' role in generating executable artifacts. We conclude that there is a need for tailoring modeling tools for education beyond focusing on simplification and usability. Furthermore, due to the broad diversity within the modeling domain, there is a need for adapting the use of tools to the specific curriculum and course learning objectives.
  •  
45.
  • Liebel, Grischa, 1987, et al. (author)
  • Ready for Prime Time, - Yes, Industrial-Grade Modelling Tools can be Used in Education
  • 2015
  • Reports (other academic/artistic)abstract
    • It has been stated that industrial-grade modelling tools are unsuitable for teaching modelling. In this paper, we present our experience with a university course on software modelling. In the first year of the course, we used a commercial modelling tool, in the second year the open-source alternative Papyrus. Both tools are considered to be of industrial grade and used in industry. Our quantitative analysis shows that the industrial-grade modelling tools with all their complexity did not have a negative impact on the students' experience of modelling. This shows that industrial-grade modelling tools can be used in the classroom. We analyse why our experience differs from published accounts and conclude that the availability of a tool champion and tailored instruction material is key. From this, we derive recommendations for teacher support from tool-providers (vendors and open source), research directions for researchers and teachers, and for training efforts in the industry.
  •  
46.
  • Lima, Keila, et al. (author)
  • A Data-Flow Oriented Software Architecture for Heterogeneous Marine Data Streams
  • 2024
  • In: Proceedings - IEEE 21st International Conference on Software Architecture, ICSA 2024. ; , s. 146-157
  • Conference paper (peer-reviewed)abstract
    • Marine in-situ data is collected by sensors mounted on fixed or mobile systems deployed into the ocean. This type of data is crucial both for the ocean industries and public authorities, e.g., for monitoring and forecasting the state of marine ecosystems and/or climate changes. Various public organizations have collected, managed, and openly shared in-situ marine data in the past decade. Recently, initiatives like the Ocean Decade Corporate Data Group have incentivized the sharing of marine data of public interest from private companies aiding in ocean management. However, there is no clear understanding of the impact of data quality in the engineering of systems, as well as on how to manage and exploit the collected data. In this paper, we propose main architectural decisions and a data flow-oriented component and connector view for marine in-situ data streams. Our results are based on a longitudinal empirical software engineering process, and driven by knowledge extracted from the experts in the marine domain from public and private organizations, and challenges identified in the literature. The proposed software architecture is instantiated and exemplified in a prototype implementation.
  •  
47.
  • Lima, Keila, et al. (author)
  • Marine Data Sharing: Challenges, Technology Drivers and Quality Attributes
  • 2022
  • In: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer International Publishing. - 1611-3349 .- 0302-9743. ; 13709 LNCS, s. 124-140
  • Conference paper (peer-reviewed)abstract
    • Context: Many companies have been adopting data-driven applications in which products and services are centered around data analysis to approach new segments of the marketplace. Data ecosystems rise from data sharing among organizations premeditatedly. However, this migration to this new data sharing paradigm has not come that far in the marine domain. Nevertheless, better utilizing the ocean data might be crucial for humankind in the future, for food production, and minerals, to ensure the ocean’s health. Research goal: We investigate the state-of-the-art regarding data sharing in the marine domain with a focus on aspects that impact the speed of establishing a data ecosystem for the ocean. Methodology: We conducted an exploratory case study based on focus groups and workshops to understand the sharing of data in this context. Results: We identified main challenges of current systems that need to be addressed with respect to data sharing. Additionally, aspects related to the establishment of a data ecosystem were elicited and analyzed in terms of benefits, conflicts, and solutions.
  •  
48.
  • Lind, Kenneth, 1966, et al. (author)
  • A Model-Based and Automated Approach to Size Estimation of Embedded Software Components
  • 2011
  • 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. - 9783642244841 ; 6981, s. 334-348
  • Conference paper (peer-reviewed)abstract
    • Accurate estimation of Software Code Size is important for developing cost-efficient embedded systems. The Code Size affects the amount of system resources needed, like ROM and RAM memory, and processing capacity. In our previous work, we have estimated the Code Size based on CFP (COSMIC Function Points) within 15% accuracy, with the purpose of deciding how much ROM memory to fit into products with high cost pressure. Our manual CFP measurement process would require 2,5 man years to estimate the ROM size required in a typical car. In this paper, we want to investigate how the manual effort involved in estimation of Code Size can be minimized. We define a UML Profile capturing all information needed for estimation of Code Size, and develop a tool for automated estimation of Code Size based on CFP. A case study will show how UML models save manual effort in a realistic case.
  •  
49.
  • Lind, Kenneth, et al. (author)
  • Automotive system development using reference architectures
  • 2012
  • In: Proceedings of the 2012 IEEE 35th Software Engineering Workshop, SEW 2012. - 9780769549477 ; , s. 42-51
  • Conference paper (peer-reviewed)abstract
    • The E/E (Electrical/Electronic) Architecture is the key enabler for new innovative user functions in the automotive domain. The E/E Architecture needs to manage the complexity of the E/E System in a cost-efficient manner. This is a fact for all domains developing mass-produced distributed systems containing embedded software. However, many companies in these domains are missing a clear description of the development process for E/E Architectures. In addition, the relation between development of E/E Architectures and the development of E/E Systems is not clear. This paper proposes a development process for E/E Architectures in the automotive domain. Furthermore, it shows the relation between development of E/E Architectures and development of E/E Systems. The development process is based on post mortem analysis of E/E System development projects conducted at an automotive company during the period 1998-2009, and it was validated in an E/E Architecture development project conducted during the period 2010-2011. The contribution of this paper is a detailed E/E System development process describing how to create and maintain an E/E Architecture and how to refine this into a Product-specific Architecture in Product development projects. Furthermore, the paper reports on experiences from working with RA development both as a small stand-alone company with few different products, and as part of a large global company with several different products.
  •  
50.
  • Lind, Kenneth, 1966, et al. (author)
  • Categorization of Real-Time Software Components for Code Size Estimation
  • 2010
  • In: International Symposium on Empirical Software Engineering and Measurement (ESEM 2010). - New York, NY, USA : ACM. - 9781450300391
  • Conference paper (peer-reviewed)abstract
    • Background: To estimate Software Code Size early in the development process is important both for Cost/Effort estimation and electronic hardware design reasons. The COSMIC FSM (Functional Size Measurement) method treats the intended software to be measured as a black box, and measures CFP (COSMIC Function Points) based only on data movement in and out of the software. Therefore, CFP can be measured on requirements defined early, and be used to estimate Code Size if there exists a strong correlation between CFP and Code Size. We have conducted four experiments in the automotive industry showing strong correlation between CFP and implemented Code Size in Bytes. All four experiments, of which two have not been published before, show equally strong correlation but the linear relationship is different between the experiments. Goal: This paper aims to identify the factors affecting the linear relationship. With these factors, we can categorize new requirements to be measured and select the proper linear relationship to convert CFP into Bytes, i.e. estimate Code Size. Method: We replicate our earlier experiments with software components of new types, and review the results from all our experiments. Potential factors affecting implemented Code Size are identified by performing open-ended interviews with domain experts. Results: We have in the automotive industry identified a set of factors that can be used to categorize the software components we want to measure; functionality type, quality constraints, and development methods and tools. Conclusions: COSMIC can produce accurate Code Size Estimates provided that sub-sets of cohesive and uniform requirements can be identified. Moreover, similar requirements must have been measured before to establish the linear relationship between CFP and Bytes. Finally, the sub-sets of requirements need to be able to categorize based on factors that affect the linear relationship. With this approach, even complex calculations can be measured, provided that they are proportional to the number of data movements. © 2010 ACM.
  •  
Skapa referenser, mejla, bekava och länka
  • Result 1-50 of 80
Type of publication
conference paper (54)
journal article (23)
reports (1)
doctoral thesis (1)
research review (1)
Type of content
peer-reviewed (75)
other academic/artistic (5)
Author/Editor
Heldal, Rogardt, 196 ... (80)
Burden, Håkan, 1976 (21)
Knauss, Eric, 1977 (19)
Pelliccione, Patrizi ... (15)
Ågren, Magnus, 1984 (9)
Lind, Kenneth, 1966 (8)
show more...
Eliasson, Ulf, 1984 (7)
Pelliccione, Patrizi ... (6)
Adawi, Tom, 1970 (6)
Chaudron, Michel, 19 ... (5)
Nguyen, Ngoc-Thanh (5)
Porras, Jari (5)
Venters, Colin C. (5)
Whittle, Jon (5)
Hebig, Regina, 1984 (4)
Liebel, Grischa, 198 ... (4)
Penzenstadler, Birgi ... (3)
Nakatumba-Nabende, J ... (3)
Pfahl, Dietmar (3)
Lind, Kenneth (3)
Betz, Stefanie (3)
Duboc, Leticia (3)
Brooks, Ian (3)
Oyedeji, Shola (3)
Alminger, Anders (3)
Penzenstadler, Birgi ... (2)
Prikladnicki, Rafael (2)
Capilla, R. (2)
Steghöfer, Jan-Phili ... (2)
Leifler, Ola (2)
Wohlrab, Rebekka, 19 ... (2)
Berger, Christian, 1 ... (2)
Yang, Chen (2)
Lundqvist, Martin (2)
Peters, Anne-Kathrin ... (2)
Avgeriou, Paris (2)
Lago, Patricia, 1967 (2)
Ljunglöf, Peter, 197 ... (2)
Coroama, Vlad C. (2)
Schneider, Kurt (2)
Bergenhem, Carl, 197 ... (2)
Felderer, Michael (2)
Krusche, Stephan (2)
Capilla, Rafael, 196 ... (2)
Tell, Paolo (2)
Lantz, Jonn A. (2)
Tüzün, Eray (2)
Fernandes, Joao (2)
Kuhrmann, Marco (2)
Rouncefield, Mark (2)
show less...
University
Chalmers University of Technology (75)
University of Gothenburg (49)
RISE (7)
Royal Institute of Technology (2)
Halmstad University (2)
Linköping University (2)
show more...
Blekinge Institute of Technology (1)
VTI - The Swedish National Road and Transport Research Institute (1)
show less...
Language
English (80)
Research subject (UKÄ/SCB)
Natural sciences (72)
Social Sciences (15)
Engineering and Technology (11)
Humanities (2)

Year

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Close

Copy and save the link in order to return to this view