| 1. |
- Abdelraheem, Mohamed Ahmed, et al.
(författare)
-
Executing Boolean queries on an encrypted Bitmap index
- 2016
-
Ingår i: CCSW 2016 - Proceedings of the 2016 ACM Cloud Computing Security Workshop, co-located with CCS 2016. - New York, NY, USA : Association for Computing Machinery (ACM). - 9781450345729 ; , s. 11-22
-
Konferensbidrag (refereegranskat)abstract
- We propose a simple and efficient searchable symmetric encryption scheme based on a Bitmap index that evaluates Boolean queries. Our scheme provides a practical solution in settings where communications and computations are very constrained as it offers a suitable trade-off between privacy and performance.
|
|
| 2. |
- Badampudi, Deepika, 1984-, et al.
(författare)
-
A decision-making process-line for selection of software asset origins and components
- 2018
-
Ingår i: Journal of Systems and Software. - : Elsevier Inc.. - 0164-1212 .- 1873-1228. ; 135, s. 88-104
-
Tidskriftsartikel (refereegranskat)abstract
- Selecting sourcing options for software assets and components is an important process that helps companies to gain and keep their competitive advantage. The sourcing options include: in-house, COTS, open source and outsourcing. The objective of this paper is to further refine, extend and validate a solution presented in our previous work. The refinement includes a set of decision-making activities, which are described in the form of a process-line that can be used by decision-makers to build their specific decision-making process. We conducted five case studies in three companies to validate the coverage of the set of decision-making activities. The solution in our previous work was validated in two cases in the first two companies. In the validation, it was observed that no activity in the proposed set was perceived to be missing, although not all activities were conducted and the activities that were conducted were not executed in a specific order. Therefore, the refinement of the solution into a process-line approach increases the flexibility and hence it is better in capturing the differences in the decision-making processes observed in the case studies. The applicability of the process-line was then validated in three case studies in a third company. © 2017 Elsevier Inc.
|
|
| 3. |
- Barlo, Alexander, et al.
(författare)
-
A Study of the Boundary Conditions in the ISO-16630 Hole Expansion Test
- 2022
-
Ingår i: IOP Conference Series. - : IOP Publishing. - 1757-8981 .- 1757-899X. ; 1238
-
Tidskriftsartikel (refereegranskat)abstract
- As new and more advanced sheet metal materials are introduced to the market, more accurate techniques for determination of failure limits are needed. One area that needs attention is edge formability, where the ISO-16630 standardized Hole Expansion Test currently is used to express this through the Hole Expansion Ratio. Over the years, this standard has been criticized for producing a large scatter in repeated tests. This paper investigates a new setup for the Hole Expansion Test which introduces draw beads into the setup to ensure sufficient restraining of the specimen during the test in an effort to reduced the scatter. In total 62 tests of a DP800 steel alloy were executed, but a large scatter in the results were still seen. It was therefore concluded that a lack of restraining force in the Hole Expansion Test was not the primary cause of the reported scatter seen in other tests.
|
|
| 4. |
- Berntsson Svensson, Richard, et al.
(författare)
-
An investigation of how quality requirements are specified in industrial practice
- 2013
-
Ingår i: Information and Software Technology. - : Elsevier BV. - 0950-5849 .- 1873-6025. ; 55:7, s. 1224-1236
-
Tidskriftsartikel (refereegranskat)abstract
- Context: This paper analyses a sub-contractor specification in the mobile handset domain. Objective: The objective is to understand how quality requirements are specified and which types of requirements exist in a requirements specification from industry. Method: The case study is performed in the mobile handset domain, where a requirements specification was analyzed by categorizing and characterizing the pertaining requirements. Results: The requirements specification is written in structured natural language with unique identifiers for the requirements. Of the 2178 requirements, 827 (38%) are quality requirements. Of the quality requirements, 56% are quantified, i.e., having a direct metric in the requirement. The variation across the different sub-domains within the requirements specification is large. Conclusion: The findings from this study suggest that methods for quality requirements need to encompass many aspects to comprehensively support working with quality requirements. Solely focusing on, for example, quantification of quality requirements might overlook important requirements since there are many quality requirements in the studied specification where quantification is not appropriate. (C) 2013 Elsevier B.V. All rights reserved.
|
|
| 5. |
- Bjarnason, Elizabeth, et al.
(författare)
-
A Multi-Case Study of Agile Requirements Engineering and the Use of Test Cases as Requirements
- 2016. - 16
-
Ingår i: Information and Software Technology. - : Elsevier. - 0950-5849 .- 1873-6025. ; 77, s. 61-79
-
Tidskriftsartikel (refereegranskat)abstract
- [Context] It is an enigma that agile projects can succeed "without requirements" when weak requirements engineering is a known cause for project failures. While agile development projects often manage well without extensive requirements test cases are commonly viewed as requirements and detailed requirements are documented as test cases. [Objective] We have investigated this agile practice of using test cases as requirements to understand how test cases can support the main requirements activities, and how this practice varies. [Method] We performed an iterative case study at three companies and collected data through 14 interviews and 2 focus groups. [Results] The use of test cases as requirements poses both benefits and challenges when eliciting, validating, verifying, and managing requirements, and when used as a documented agreement. We have identified five variants of the test-cases-as-requirements practice, namely de facto, behaviour-driven, story-test driven, stand-alone strict and stand-alone manual for which the application of the practice varies concerning the time frame of requirements documentation, the requirements format, the extent to which the test cases are a machine executable specification and the use of tools which provide specific support for the practice of using test cases as requirements. [Conclusions] The findings provide empirical insight into how agile development projects manage and communicate requirements. The identified variants of the practice of using test cases as requirements can be used to perform in-depth investigations into agile requirements engineering. Practitioners can use the provided recommendations as a guide in designing and improving their agile requirements practices based on project characteristics such as number of stakeholders and rate of change.
|
|
| 6. |
- Borg, Markus, et al.
(författare)
-
Illuminating a Blind Spot in Digitalization - Software Development in Sweden's Private and Public Sector
- 2020
-
Ingår i: Proceedings - 2020 IEEE/ACM 42nd International Conference on Software Engineering Workshops, ICSEW 2020. - New York, NY, USA : Association for Computing Machinery, Inc. - 9781450379632 ; , s. 299-302
-
Konferensbidrag (refereegranskat)abstract
- As Netscape co-founder Marc Andreessen famously remarked in 2011, software is eating the world - becoming a pervasive invisible critical infrastructure. Data on the distribution of software use and development in society is scarce, but we compile results from two novel surveys to provide a fuller picture of the role software plays in the public and private sectors in Sweden, respectively. Three out of ten Swedish firms, across industry sectors, develop software in-house. The corresponding figure for Sweden's government agencies is four out of ten, i.e., the public sector should not be underestimated. The digitalization of society will continue, thus the demand for software developers will further increase. Many private firms report that the limited supply of software developers in Sweden is directly affecting their expansion plans. Based on our findings, we outline directions that need additional research to allow evidence-informed policy-making. We argue that such work should ideally be conducted by academic researchers and national statistics agencies in collaboration. © 2020 ACM.
|
|
| 7. |
- Borg, Markus, et al.
(författare)
-
Practitioners' Perspectives on Change Impact Analysis for Safety-Critical Software - A Preliminary Analysis
- 2016. - 11
-
Ingår i: Computer Safety, Reliability, and Security. - Cham : Springer International Publishing. - 9783319454795 - 9783319454801 ; , s. 346-358
-
Konferensbidrag (refereegranskat)abstract
- Safety standards prescribe change impact analysis (CIA) during evolution of safety-critical software systems. Although CIA is a fundamental activity, there is a lack of empirical studies about how it is performed in practice. We present a case study on CIA in the context of an evolving automation system, based on 14 interviews in Sweden and India. Our analysis suggests that engineers on average spend 50-100 hours on CIA per year, but the effort varies considerably with the phases of projects. Also, the respondents presented different connotations to CIA and perceived the importance of CIA differently. We report the most pressing CIA challenges, and several ideas on how to support future CIA. However, we show that measuring the effect of such improvement solutions is non-trivial, as CIA is intertwined with other development activities. While this paper only reports preliminary results, our work contributes empirical insights into practical CIA.
|
|
| 8. |
- Borg, Markus, et al.
(författare)
-
Selecting component sourcing options : A survey of software engineering's broader make-or-buy decisions
- 2019
-
Ingår i: Information and Software Technology. - : Elsevier B.V.. - 0950-5849 .- 1873-6025. ; 112, s. 18-34
-
Tidskriftsartikel (refereegranskat)abstract
- Context: Component-based software engineering (CBSE) is a common approach to develop and evolve contemporary software systems. When evolving a system based on components, make-or-buy decisions are frequent, i.e., whether to develop components internally or to acquire them from external sources. In CBSE, several different sourcing options are available: (1) developing software in-house, (2) outsourcing development, (3) buying commercial-off-the-shelf software, and (4) integrating open source software components. Objective: Unfortunately, there is little available research on how organizations select component sourcing options (CSO) in industry practice. In this work, we seek to contribute empirical evidence to CSO selection. Method: We conduct a cross-domain survey on CSO selection in industry, implemented as an online questionnaire. Results: Based on 188 responses, we find that most organizations consider multiple CSOs during software evolution, and that the CSO decisions in industry are dominated by expert judgment. When choosing between candidate components, functional suitability acts as an initial filter, then reliability is the most important quality. Conclusion: We stress that future solution-oriented work on decision support has to account for the dominance of expert judgment in industry. Moreover, we identify considerable variation in CSO decision processes in industry. Finally, we encourage software development organizations to reflect on their decision processes when choosing whether to make or buy components, and we recommend using our survey for a first benchmarking.
|
|
| 9. |
- Borg, Markus, et al.
(författare)
-
Selecting Software Component Sourcing Options : Detailed Survey Description and Analysis
- 2018
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- Component-based software engineering (CBSE) is a common approach to develop and evolve contemporary software systems. When evolving a system based on components, make-or-buy decisions are frequent, i.e., whether to develop components internally or to acquire them fromexternal sources. In CBSE, several different sourcing options are available: 1) developing software in-house, 2) outsourcing development, 3) buying commercial-off-the-shelf software, and 4) integrating open source software components. Unfortunately, there is little available research on howorganizations select component sourcing options (CSO) in industry practice. In this work, we seek to contribute empirical evidence to CSO selection. Method: We conduct a cross-domain survey on CSO selection in industry, implemented as an online questionnaire. Based on 188 responses, we find that most organizations consider multiple CSOs during software evolution, and that the CSO decisions in industry are dominated by expert judgment. When choosing between candidate components, functional suitability acts as an initial filter, then reliability is the most important quality. We stress that future solution-oriented work on decision support has to account for the dominance of expert judgment in industry. Moreover, we identify considerable variation in CSO decision processes in industry. Finally, we encourage software development organizations to reflect on their decision processes when choosing whether to make or buy components, and we recommend using our survey for a first benchmarking.
|
|
| 10. |
- Borg, Markus, et al.
(författare)
-
Software Engineers' Information Seeking Behavior in Change Impact Analysis : An Interview Study
- 2017
-
Ingår i: IEEE International Conference on Program Comprehension. - : IEEE Computer Society. - 9781538605356 ; , s. 12-22, s. 12-22
-
Konferensbidrag (refereegranskat)abstract
- Software engineers working in large projects must navigate complex information landscapes. Change Impact Analysis (CIA) is a task that relies on engineers' successful information seeking in databases storing, e.g., source code, requirements, design descriptions, and test case specifications. Several previous approaches to support information seeking are task-specific, thus understanding engineers' seeking behavior in specific tasks is fundamental. We present an industrial case study on how engineers seek information in CIA, with a particular focus on traceability and development artifacts that are not source code. We show that engineers have different information seeking behavior, and that some do not consider traceability particularly useful when conducting CIA. Furthermore, we observe a tendency for engineers to prefer less rigid types of support rather than formal approaches, i.e., engineers value support that allows flexibility in how to practically conduct CIA. Finally, due to diverse information seeking behavior, we argue that future CIA support should embrace individual preferences to identify change impact by empowering several seeking alternatives, including searching, browsing, and tracing. © 2017 IEEE.
|
|
