Exam Glossary
| Term | Main definition |
|---|---|
| use case | A technique using realistic practical scenarios to define functional requirements and to design tests. |
| user | A person who uses services. |
| user experience UX | The sum of the functional and emotional interactions with a service and service provider as perceived by a user. |
| user story | A technique in Agile software development that uses natural language to describe desired outcomes and benefits from the point of view of a specific persona (typically the end-user), usually in the form of ‘who, what, and why’. |
| utility | The functionality offered by a product or service to meet a particular need. Utility can be summarized as ‘what the service does’ and can be used to determine whether a service is ‘fit for purpose’. To have utility, a service must either support the performance of the consumer or remove constraints from the consumer. Many services do both. |
| utility requirements | Functional requirements which have been defined by the customer and are unique to a specific product. |
