Glossary: U
- Unit Test
- Test of a product or software program to show whether it satisfies its functional specifications or intended design structure while in the development process.
- Upgrade Test
- Comprehensive test performed for SAP application releases. A combination of regression, integration, follow-up, and endorsement tests normally performed over a six-week period.
- Usability
- Measure of effectiveness, efficiency, and satisfaction with a user interface by seeing how users can achieve specified goals in a particular environment by using it.
- Usability Inspection
- A set of techniques for evaluating a user interface by examining and critiquing it, as opposed to testing the interface on users.
- Usability Lab
- A lab designed for user testing, usually with computer equipment for a tester and space for an observer to sit. There is also a special observation room with audio/visual equipment to record the session and to accommodate developers, stakeholders, and others who are interested in seeing the outcome.
- Usability Test
- In general, a usability test encompasses
a range of methods that examine how users in the target audience
interact with a software application in order to measure its usability.
The usability test at MIT involves testing ECAT, SAPweb, and SAPweb Self Service applications for compliance with the MIT SAP Web Development Standards and ease of use by the MIT community. See also ECAT, SAPweb, and SAPweb Self Service. - Upgrade Test
- Comprehensive test performed for SAP application releases. A combination of regression, integration, follow-up, and endorsement tests normally performed over a six-week period.
- User Interface Design
- The overall process of designing how well a user will be able to interact with a software application.
- User Needs Analysis
- This technique uncovers the goals a user has and the capabilities needed from a technology to assist the user in meeting those goals. This involves understanding the target audience, their typical tasks, and their specific constraints, usually through a combination of observational techniques, including interviews, surveys, artifact analysis, and consulting with field experts. The results provide user interface objectives, system requirements, and feature requirements.
