Usability Engineering
Agile Software Development with Scrum
Agile Software Development with Scrum
Designing from Both Sides of the Screen: How Designers and Engineers Can Collaborate to Build Cooperative Technology
Populating a Release History Database from Version Control and Bug Tracking Systems
ICSM '03 Proceedings of the International Conference on Software Maintenance
ACM SIGPLAN Notices
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
Tracking defect warnings across versions
Proceedings of the 2006 international workshop on Mining software repositories
Proceedings of the 44th annual Southeast regional conference
Continuous Integration: Improving Software Quality and Reducing Risk (The Addison-Wesley Signature Series)
Semantic clustering: Identifying topics in source code
Information and Software Technology
Visual identification of software evolution patterns
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
Beautiful Code: Leading Programmers Explain How They Think (Theory in Practice (O'Reilly))
Beautiful Code: Leading Programmers Explain How They Think (Theory in Practice (O'Reilly))
Extracting structural information from bug reports
Proceedings of the 2008 international working conference on Mining software repositories
MSR '09 Proceedings of the 2009 6th IEEE International Working Conference on Mining Software Repositories
| Hi-index | 0.00 |
During the iterative development of interactive software, formative evaluation is often performed to find and fix usability problems early on. The output of a formative evaluation usually takes the form of a prioritised list of usability findings, each finding typically consisting of a description of the problem, how often it occurred, and sometimes a recommendation for a possible solution. Unfortunately, the valuable results of formative evaluations are usually collected into a written document. This makes it extremely difficult to automate the handling of usability findings. A more formalised, electronic format for the handover of usability findings would make much more sense. UsabML is a formalised structure for reporting usability findings expressed in XML. It allows usability experts and software engineers to import usability findings into bug (issue) tracking systems, to associate usability issues with parts of source code, and to track progress in fixing them.