| 1. |
|
|
| 2. |
|
|
| 3. |
- Dittrich, Yvonne, et al.
(author)
-
Co-Operative Method Development revisited
- 2005
-
Conference paper (peer-reviewed)abstract
- During the last five years, we applied a research approach we call 'Co-operative Method Development' formulated on first experience with empirical research focusing especially on the social side of software engineering. This position paper summarizes the experiences and discusses the improvement and further development of this research approach based on our experiences in different research projects in co-operation with industrial partners.
|
|
| 4. |
|
|
| 5. |
|
|
| 6. |
- 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.
|
|
| 7. |
- 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.
|
|
| 8. |
|
|
| 9. |
- 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.
|
|
