| 11. |
- Lenberg, Per, 1976, et al.
(författare)
-
Human factors related challenges in software engineering - An industrial perspective
- 2015
-
Ingår i: 8th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE). - : IEEE. - 9781467370318
-
Konferensbidrag (refereegranskat)abstract
- © 2015 IEEE. It is increasingly recognised that successful Software Engineering not only depends on technical or process issues, but requires attention to human factors. Researchers include such aspects which has led to both new theories and refined methods. However, it is not clear if professionals in the software industry agree that human factors are critical and what the related challenges and possibilities are. The purpose of the present study is to address this discrepancy. Using a qualitative research method, we elicited information about how and why human factors affect Software Engineering projects, which challenges are of special interest and the context in which they arise. Thematic analysis of data from interviews with nine senior software professionals in multiple Swedish software companies of differing size identified four main challenging areas. As supported by existing research, customer relations and communications were highlighted as important, but so too is the need for more holistic and multi-dimensional solutions and the importance of human factors in software organisational change. In addition, quantitative results indicate that the professionals see the organisational and group aspects as more important than the individual aspect. Our results can help to focus future research on matters that software practitioners consider important.
|
|
| 12. |
- Lenberg, Per, 1976, et al.
(författare)
-
Towards a Behavioral Software Engineering
- 2014
-
Ingår i: CHASE 2014 Proceedings of the 7th International Workshop on Cooperative and Human Aspects of Software Engineering. - New York, NY, USA : ACM. - 9781450328609 ; , s. 48-55
-
Konferensbidrag (refereegranskat)abstract
- Throughout the history of Software Engineering (SE) it has been repeatedly found that the humans involved, i.e. the engineers and developers in addition to other stakeholders, are a key factor in determining project outcomes and success. However, the amount of research that focuses on human aspects has been limited compared to research with technology or process focus. With increasing maturity of the field, interest in agile methods and a growing dissatisfaction with the continued challenges of developing high-quality software on time, the amount of SE research putting human aspect in primary focus has increased. In this paper we argue that a synthesized view of the emerging human-focused SE research is needed and can add value through giving focus, direction and help identify gaps. Taking cues from the addition of Behavioral Economics as an important part of the area of Economics we propose the term Behavioral Software Engineering (BSE) as an umbrella concept for research that focus on behavioral and social aspects in the work activities of software engineers. We propose that a model based on three units of analysis can give structure and point to concepts that are important for BSE. To add detail to this model we are conducting a systematic review to map out what is currently known. To exemplify the model and the area we here present the results from a subset of the identified concepts.
|
|
| 13. |
- Marculescu, Bogdan, 1984, et al.
(författare)
-
Objective re-weighting to guide an interactive search based software testing system
- 2013
-
Ingår i: 2013 12th International Conference on Machine Learning and Applications, ICMLA 2013; Miami, FL; United States; 4 December 2013 through 7 December 2013. - Miami : IEEE. ; 2, s. 102-107
-
Konferensbidrag (refereegranskat)abstract
- Even hardware-focused industries today develop products where software is both a large and important component. Engineers tasked with developing and integrating these products do not always have a software engineering background. To ensure quality, tools are needed that automate and support software testing while allowing these domain specialists to leverage their knowledge and experience. Search-based testing could be a key aspect in creating an automated tool for supporting testing activities. However, domain specific quality criteria and trade-offs make it difficult to develop a general fitness function a priori, so interaction between domain specialists and such a tool would be critical to its success. In this paper we present a system for interactive search based software testing and investigate a way for domain specialists to guide the search by dynamically re-weighting quality goals. Our empirical investigation shows that objective reweighing can help a human domain specialist interactively guide the search, without requiring specialised knowledge of the system and without sacrificing population diversity.
|
|
| 14. |
- Berntsson Svensson, Richard, 1978-, et al.
(författare)
-
Selecting creativity techniques for creative requirements: An evaluation of four techniques using creativity workshops
- 2015
-
Ingår i: 23rd IEEE International Requirements Engineering Conference, RE 2015, Ottawa, Canada, 24-28 August. - : IEEE. - 9781467369053 ; , s. 66-75
-
Konferensbidrag (refereegranskat)abstract
- Requirements engineering is recognized as a creative process where stakeholders jointly discover new creative ideas for innovative and novel products that eventually are expressed as requirements. This paper evaluates four different creativity techniques, namely Hall of Fame, Constraint Removal, Brainstorming, and Idea Box, using creativity workshops with students and industry practitioners. In total, 34 creativity workshops were conducted with 90 students from two universities, and 86 industrial practitioners from six companies. The results from this study indicate that Brainstorming can generate by far the most ideas, while Hall of Fame generates most creative ideas. Idea Box generates the least number of ideas, and the least number of creative ideas. Finally, Hall of Fame was the technique that led to the most number of requirements that was included in future releases of the products. © 2015 IEEE.
|
|
| 15. |
- Kashfi, Pariya, 1980, et al.
(författare)
-
A conceptual ux-aware model of requirements
- 2016
-
Ingår i: 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. - 9783319449012 ; 9856, s. 234-245, s. 234-245
-
Konferensbidrag (refereegranskat)abstract
- User eXperience (UX) is becoming increasingly important for success of software products. Yet, many companies still face various challenges in their work with UX. Part of these challenges relate to inadequate knowledge and awareness of UX and that current UX models are commonly not practical nor well integrated into existing Software Engineering (SE) models and concepts. Therefore, we present a conceptual UX-aware model of requirements for software development practitioners. This layered model shows the interrelation between UX and functional and quality requirements. The model is developed based on current models of UX and software quality characteristics. Through the model we highlight the main differences between various requirement types in particular essentially subjective and accidentally subjective quality requirements. We also present the result of an initial validation of the model through interviews with 12 practitioners and researchers. Our results show that the model can raise practitioners’ knowledge and awareness of UX in particular in relation to requirement and testing activities. It can also facilitate UX-related communication among stakeholders with different backgrounds.
|
|
| 16. |
- Marculescu, Bogdan, 1984, et al.
(författare)
-
Using exploration focused techniques to augment search-based software testing: an experimental evaluation
- 2016
-
Ingår i: 2016 IEEE International Conference on Software Testing, Verification and Validation (ICST). - : IEEE. - 2381-2834. - 9781509018277 - 9780306406157 ; , s. 69-79
-
Konferensbidrag (refereegranskat)abstract
- Search-based software testing (SBST)often uses objective-based approaches to solve testing problems. There are, however, situations where the validity and completeness of objectives cannot be ascertained, or where there is insufficient information to define objectives at all. Incomplete or incorrect objectives may steer the search away from interesting behavior of the software under test (SUT) and from potentially useful test cases.This papers investigates the degree to whichexploration-based algorithms can be used tocomplement an objective-based tool we have previously developed and evaluated in industry. In particular, we would like to assess how exploration-based algorithms perform in situations where little information on the behavior space is available a priori. We have conducted an experiment comparing the performance of an exploration-based algorithm with an objective-based one on a problem with a high dimensional behavior space. In addition, we evaluate to what extent that performance degrades in situations where computational resources are limited.Our experiment shows that exploration-basedalgorithms are useful in covering a larger area of the behavior space and result in a more diverse solution population. Typically, of the candidate solutions that exploration-based algorithms propose, more than 80% were not covered by their objective-based counterpart. This increased diversity is present in the resulting population even when computational resources are limited. We conclude that exploration-focused algorithms are a useful means of investigating high-dimensional spaces, even in situations where limited information and limited resources are available.
|
|
| 17. |
- Berntsson Svensson, Richard, 1978-, et al.
(författare)
-
BAM : backlog assessment method
- 2019
-
Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer Verlag. - 1865-1348. - 9783030190330 ; , s. 53-68
-
Konferensbidrag (refereegranskat)abstract
- The necessity of software as stand-alone products, and as central parts of non-traditional software products have changed how software products are developed. It started with the introduction of the agile manifesto and has resulted in a change of how software process improvements (SPI) are conducted. Although there are agile SPI methods and several agile practices for evaluating and improving current processes and ways-of-working, no method or practices for evaluating the backlog exists. To address this gap, the Backlog Assessment Method (BAM) was developed and applied in collaboration with Telenor Sweden. BAM enables agile organizations to assess backlogs, and assure that the backlog items are good-enough for their needs and well aligned with the decision process. The results from the validation show that BAM is feasible and relevant in an industrial environment, and it indicates that BAM is useful as a tool to perform analysis of items in a specific backlog. © The Author(s) 2019.
|
|
| 18. |
- Gren, Lucas, 1984-, et al.
(författare)
-
What Makes Effective Leadership in Agile Software Development Teams?
- 2022
-
Ingår i: International Conference on Software Engineering. - New York, NY, USA : IEEE Computer Society. - 9781450392211 ; , s. 2402-2414
-
Konferensbidrag (refereegranskat)abstract
- Effective leadership is one of the key drivers of business and project success, and one of the most active areas of management research. But how does leadership work in agile software development, which emphasizes self-management and self-organization and marginalizes traditional leadership roles? To find out, this study examines agile leadership from the perspective of thirteen professionals who identify as agile leaders, in different roles, at ten different software development companies of varying sizes. Data from semi-structured interviews reveals that leadership: (1) is dynamically shared among team members; (2) engenders a sense of belonging to the team; and (3) involves balancing competing organizational cultures (e.g. balancing the new agile culture with the old milestone-driven culture). In other words, agile leadership is a property of a team, not a role, and effectiveness depends on agile team members' identifying with the team, accepting responsibility, and being sensitive to cultural conflict.
|
|
| 19. |
- Kuzniarz, Ludwik, et al.
(författare)
-
Generating Domain Models from Ontologies.
- 2002
-
Ingår i: International Conference on Object-Oriented Information Systems, LNCS, Springer. - Montpellier, France : SPRINGER-VERLAG BERLIN.
-
Konferensbidrag (refereegranskat)abstract
- The paper presents and elaborates on the idea of automatic acquisition of knowledge about domain structure from ontologies into an object-oriented software development process. The information required to be included in the domain model produced during the development process is identified. The existence of the knowledge in ontologies is investigated. Requirements for ontology description languages are formulated followed by brief evaluation of existing languages against these requirements. A schema for domain knowledge acquisition is outlined. A realization of the schema is sketched in the paper while the implementation details can be found in the technical report.
|
|
| 20. |
- Sourrouille, Jean Louis, et al.
(författare)
-
Third International Workshop on Quality in Modeling
- 2009
-
Konferensbidrag (refereegranskat)abstract
- Software quality management is widely researched within Model Driven Software Development (MDD), from both industry practices and academic research viewpoints. The goal of this workshop was to gather researchers and practitioners interested in the emerging issues of quality in the context of MDD. During the first part of the workshop, selected papers were presented and discussed. The second part was divided into two working sessions. The first session was devoted to the introduction of model quality into the software development process by drawing a parallel with quality of code. An invited practitioner introduced issues related to quality of code, followed by a guided discussion based on a list of predefined questions. The second session was dealing with future work and research interests of the participants.
|
|
