| 1. |
- Alvaro, Alexandre, et al.
(författare)
-
Software Component Evaluation: A Theoretical Study on Component Selection and Certification
- 2007
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- Software components need to be evaluated at several points during their life cycle, by different actors and for different purposes. Besides the quality assurance performed by component developers, there are two main activities which include evaluation of components: component selection (i.e. evaluation performed by the system developer in order to select the best fit component to use in a system) and an envisioned component certification (i.e. evaluation made by an independent actor in order to increase the trust in the component). This paper examines the fundamental similarities and differences between these two types of component evaluations and elaborates how these fit in the overall process views of component-based development for both COTS-based development and software product line development.
|
|
| 2. |
- Björnander, Stefan, et al.
(författare)
-
A method to formally evaluate safety case arguments against a system architecture model
- 2012
-
Ingår i: Proceedings of International Symposium on Software Reliability Engineering Workshops, ISSREW. - 9780769549286 ; , s. 337-342
-
Konferensbidrag (refereegranskat)abstract
- For a large and complex safety-critical system, where safety is ensured by a strict control over many properties, the safety information is structured into a safety case. As a small change to the system design may potentially affect a large section of the safety argumentation, a systematic method for evaluating the impact of system changes on the safety argumentation would be valuable. We have chosen two of the most common notations: the Goal Structuring Notation (GSN) for the safety argumentation and the Architecture Analysis and Design Language (AADL) for the system architecture model. In this paper, we address the problem of impact analysis by introducing the GSN and AADL Graph Evaluation (GAGE) method that maps safety argumentation structure against system architecture, which is also a prerequisite for successful composition of modular safety cases. In order to validate the method, we have implemented the GAGE tool that supports the mapping between the GSN and AADL notations and highlight changes in impact on the argumentation. © 2012 IEEE.
|
|
| 3. |
- Björnander, Stefan, et al.
(författare)
-
Towards Automatic Verification of Safety Properties in AADL System Models
- 2013
-
Ingår i: Proceedings of the 31st International System Safety Conference (ISSC).
-
Konferensbidrag (refereegranskat)abstract
- In some domains, standards such as ISO 26262 or the UK Ministry of DefenceÂ’s Defence Standard 00-56 require developers to produce a safety case. As the safety case for a complex system can be rather large, automated verification of all or part of it would be valuable. We have approached the issue by designing a method supported by a framework including analysers for safety cases defined in the Goal Structuring Notation (GSN) and systems modelled in the Architecture Analysis and Design Language (AADL). In our approach, the safety case predicates are defined in a subset of the functional language Meta Language (ML). Our approach facilities formalising some parts of a typical safety argument in an ML-like notation, enabling automatic verification of some reasoning steps in the safety argument. Automatic verification not only justifies increased confidence, it can ease the burden of re-checking the safety argument as it (and the system) change.
|
|
| 4. |
- Bosnic, Ivana, et al.
(författare)
-
Customers' Role in Teaching Distributed Software Development
- 2010
-
Ingår i: Software Engineering Education Conference, Proceedings. - Pittsburgh, PA, USA. ; , s. 73-80
-
Konferensbidrag (refereegranskat)abstract
- This paper describes different aspects of teaching distributed software development, regarding the types of project customers: industry and academia. These approaches enable students to be more engaged in real-world situations, by having customers from the industry, local or distributed customers in universities, distributed customers in software engineering contests or being involved in an ongoing project, thus simulating the company merging. The methods we describe are used in a distributed project-oriented course, which is jointly carried out by two universities from Sweden and Croatia. The paper presents our experiences of such projects being done during the course, the differences in each approach, issues observed and ways to solve them, in order to create a more engaging education for better-prepared engineers of tomorrow.
|
|
| 5. |
- Causevic, Adnan, et al.
(författare)
-
A Survey on Industrial Software Engineering
- 2009
-
Ingår i: AGILE PROCESSES IN SOFTWARE ENGINEERING AND EXTREME PROGRAMMING. - Berlin, Heidelberg : Springer. - 9783642018527 ; , s. 240-241
-
Bokkapitel (refereegranskat)abstract
- In this paper, we present on-going work on data collected by a questionnaire surveying process practices, preferences, and methods in industrial software engineering.
|
|
| 6. |
- Causevic, Adnan, et al.
(författare)
-
An Industrial Survey on Software Process Practices, Preferences and Methods
- 2009
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- This report presents the questionnaire questions and responses of a web-based survey conducted during early spring 2009. It was intended to survey current processes, practices, and methods in the software industry. The report contains no analysis of the data, but is intended to be a reference for other publications, both by ourselves, but by making the data publicly available, also by others.
|
|
| 7. |
- Čaušević, Adnan, 1981-, et al.
(författare)
-
Automated Regression Test Generation Using Record & Replay Approach: A Case Study on Train Control Management System
- 2016
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- Organizations tend to limit their investment in test automation due to the lack of information on the actual tests reuse and when will automated tests really pay off. However, to perform efficient regression testing of software systems, it is expected from a development team to posses a certain level of test automation infrastructure in place, where at the minimum the test execution is scripted and automated. In this paper we are proposing the usage of record & replay approach to observe the functional usage of a component under test, while its being invoked as part of the whole system or only in a certain portion of it. Afterwords, executable tests are automatically derived, containing both test inputs and test verdict, allowing its later usage as part of a regression testing. With as minimal effort as one manual test execution, developers are provided with automated tests, minimizing any concerns on the investment in automation. A case study from Bombardier Transportation is provided showing how the proposed approach substantially reduced the test effort needed when performing regression testing of the train control management system for the Stockholm C30 metro train.
|
|
| 8. |
- Crnkovic, Ivica, et al.
(författare)
-
Is software engineering training enough for software engineers?
- 2003
-
Ingår i: Software Engineering Education Conference, Proceedings. - 0769518699 ; , s. 140-147
-
Konferensbidrag (refereegranskat)abstract
- Most software engineering courses focus exclusively on the software development process, often referring to problems related to the complexity of software products and processes. In practice, however, many problems of a complex nature arise in which system engineering and other engineering disciplines are important in the development of systems. In such cases software engineers may have difficulty in coping with the entire problem, in the same way that engineers in other fields may have difficulty in understanding the software part. This suggests that the software engineering education of today is inadequate in certain respects. This paper presents a case study of a software engineering course and discusses the difficulty for computer science students to understand and to develop a system which also requires skills in engineering of a non-software nature.
|
|
| 9. |
- Dersten, Sara, et al.
(författare)
-
Analysis of the Business Effects of Software Architecture Refactoring in an Automotive Development Organization
- 2010
-
Ingår i: Proceedings - 36th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2010. - 9780769541709 ; , s. 269-278
-
Konferensbidrag (refereegranskat)abstract
- This paper presents an exploratory study of an automotive manufacturer, which develops embedded software for over 150 products and has adopted a company-wide software product-line approach. The company is facing the introduction of a new software architecture in all products in near time. This architecture introduces new paradigms more explicitly, such as explicit software components and signal-based communication, newer technologies, and adheres to new standards. Concretely, the architecture consists of common infrastructure and other generic components. Such a fundamental and drastic technology change can be expected to have far-reaching consequences, both of technical and non-technical nature. In this study we systematically investigate the introduction of the new software architecture, by mapping individual elements of the architectural change to system properties and company functions. The study implies that the whole organization is affected, and the new architecture also influences the cooperation with suppliers.
|
|
| 10. |
- Fredriksson, Johan, et al.
(författare)
-
Packaging Component-Analysis for Reuse
- 2007
-
Konferensbidrag (refereegranskat)abstract
- Component-Based Software Engineering (CBSE) promises an improved ability to reuse software which would potentially decrease the development time while also improving the quality of the system, since the components are (re-)used by many. However, CBSE has not been as successful in the embedded systems domain as in the desktop domain, partly because requirements on embedded systems are stricter (e.g. requirements on safety, real-time and minimizing hardware resources). Moreover these requirements differ between industrial domains. Paradoxically, components should be context-unaware to be reusable at the same time as they should be context sensitive in order to be predictable and resource efficient. This seems to be a fundamental problem to overcome before the CBSE paradigm will be successful also in the embedded systems domain. Another problem is that some of the stricter requirements for embedded systems require certain analyses to be made, which may be very complicated and time-consuming for the system developer.This paper describes how one particular kind of analysis, of worst-case execution time, would fit into the CBSE development processes so that the component developer performs some analyses and presents the results in a form that is easily used for component and system verification during system development. This process model is not restricted to worst-case execution time analysis, but we believe other types of analyses could be performed in a similar way.
|
|
