| 11. |
|
|
| 12. |
|
|
| 13. |
- Johansson, Conny, et al.
(author)
-
Commitment as an Underlying Principle for Learning
- 2004
-
Conference paper (peer-reviewed)abstract
- The prevailingmodel of software development on which most educational programs are based is in conflict with general practice in industry. As following paper demonstrates Software Engineering education lacks an approach to teach the skills needed to master coalitions of existing recourses that are hard to control. In order to prepare students to handle unpredictable, non-technical and moving targets, an adequate curriculum is needed. Since 1990 software engineering education at Blekinge Institute of Technology has used commitment as the underlying principle for learning. This principle has made it possible to address the discrepancies between education and industry. This paper describes and evaluates our experience of using six elements of commitment in the education of software engineers.
|
|
| 14. |
- Petersen, Kai, et al.
(author)
-
The impact of time controlled reading on software inspection effectiveness and efficiency : a controlled experiment
- 2008
-
Conference paper (peer-reviewed)abstract
- Reading techniques help to guide reviewers during individual software inspections. In this experiment, we completely transfer the principle of statistical usage testing to inspection reading techniques for the first time. Statistical usage testing relies on a usage profile to determine how intensively certain parts of the system shall be tested from the users' perspective. Usage-based reading applies statistical usage testing principles by utilizing prioritized use cases as a driver for inspecting software artifacts (e.g., design). In order to reflect how intensively certain use cases should be inspected, time budgets are introduced to usage-based reading where a maximum inspection time is assigned to each use case. High priority use cases receive more time than low priority use cases. A controlled experiment is conducted with 23 Software Engineering M.Sc. students inspecting a design document. In this experiment, usage-based reading without time budgets is compared with time controlled usage-based reading. The result of the experiment is that time budgets do not significantly improve inspection performance. In conclusion, it is sufficient to only use prioritized use cases to successfully transfer statistical usage testing to inspections.
|
|
| 15. |
- Petersen, Kai, et al.
(author)
-
The impact of time controlled reading on software inspection effectiveness and efficiency a controlled experiment
- 2008
-
In: ESEM'08. - : ASSOC COMPUTING MACHINERY. ; , s. 139-148
-
Conference paper (peer-reviewed)abstract
- Reading techniques help to guide reviewers during individual software inspections. In this experiment, we completely transfer the principle of statistical usage testing to inspection reading techniques for the first time. Statistical usage testing relies on a usage profile to determine how intensively certain parts of the system shall be tested from the users' perspective. Usage-based reading applies statistical usage testing principles by utilizing prioritized use cases as a driver for inspecting software artifacts (e.g., design). In order to reflect how intensively certain use cases should be inspected, time budgets are introduced to usage-based reading where a maximum inspection time is assigned to each use case. High priority use cases receive more time than low priority use cases. A controlled experiment is conducted with 23 Software Engineering M.Sc. students inspecting a design document. In this experiment, usage-based reading without time budgets is compared with time controlled usage-based reading. The result of the experiment is that time budgets do not significantly improve inspection performance. In conclusion, it is sufficient to only use prioritized use cases to successfully transfer statistical usage testing to inspections.
|
|
| 16. |
- Tan, Jia, et al.
(author)
-
A framework for software usability & user experience measurement in mobile industry
- 2013
-
Conference paper (peer-reviewed)abstract
- The mobile industry faces challenges in designing software usability and user experience (UX) measurement instruments. The major difficulties arise due to: 1) diversity of definitions and terminology used for usability and UX aspects and attributes, which lead to inconsistencies, and 2) lack of a taxonomy for these attributes with links to well-defined measures in the literature. In this paper, we present a framework to support mobile industry to overcome these challenges. We first unified the terminology and definitions for usability and UX attributes in the literature. Then, we created taxonomy of attributes and sub-attributes. By using the well-known Goal Question Metric (GQM) approach, we identified a comprehensive set of questions and measures for each attribute that could be used as a basis for developing measurement instruments. The framework was evaluated through a case study conducted in a usability research, development and consultancy company for mobile industry in Sweden.
|
|
| 17. |
- Winter, Jeff, et al.
(author)
-
Developing Quality through Measuring Usability--The UTUM Test Package
- 2007
-
Conference paper (peer-reviewed)abstract
- This paper presents a tool for building quality of use into software and the software process, in the form of a test package for mass market devices. It is developed for measuring user experience, which is seen as a more encompassing term than usability. The test package, which is under constant development, is the result of a long term cooperation between industry and academia, and is in use in indutrial development projects. It shows usability through the use of metrics, for efficiency, effectiveness and satisfaction, supported by qualitative judgements made by a test leader/usability expert. It gives a clear demonstration of quality, from the customer and end-user point of view. The case presented here, where the test has been performed concurrently in two countries, has been a quality assurance of the test package, which has been found to work efficiently and flexibly in a complex industrial environment, with complicated relationships between customers, partners and end-users.
|
|
| 18. |
- Winter, Jeff, et al.
(author)
-
Meeting organisational needs and quality assurance through balancing agile and formal usability testing results
- 2011
-
In: Lecture Notes in Computer Science. - Berlin, Heidelberg : Springer. ; , s. 275-289
-
Conference paper (peer-reviewed)abstract
- This paper deals with a case study of testing with a usability testing package (UTUM), which is also a tool for quality assurance, developed in cooperation between industry and research. It shows that within the studied company, there is a need to balance agility and formalism when producing and presenting results of usability testing to groups who we have called Designers and Product Owners. We have found that these groups have different needs, which can be placed on opposite sides of a scale, based on the agile manifesto. This becomes a Designer and a Product Owner Manifesto. The test package is seen as a successful hybrid method combining agility with formalism, satisfying organisational needs, and fulfilling the desire to create a closer relation between industry and research.
|
|
| 19. |
|
|
| 20. |
- Winter, Jeff, et al.
(author)
-
Reporting Usability Metrics Experiences
- 2009
-
Conference paper (peer-reviewed)abstract
- It is often claimed that software development is negatively affected by infrequent, incomplete and inconsistent measurements; improving with the help of metrics is an obvious solution. Software testing provides opportunities for measurement that give organizations insight in to processes. Usability testing is part of the testing area, although it is not a commonly addressed area within software engineering, perhaps because of a split between qualitative and quantitative paradigms. We compare a usability testing framework called UTUM with principles for Software Process Improvement, and find areas of close agreement as well as areas where our work illuminates new characteristics. UTUM is found to be a useful vehicle for improvement in software engineering, dealing as it does with both product and process. Our work emphasises the importance of the neglected area of usability testing. Our experience also illustrates how the metrics have been tailored to act as a boundary object between different disciplines.
|
|
