Statistical testing of software based on a usage model
Software—Practice & Experience
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Writing Effective Use Cases
Software Reliability Engineered Testing
Software Reliability Engineered Testing
The Inmates Are Running the Asylum
The Inmates Are Running the Asylum
Improving the use case driven approach to requirements engineering
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Derivation of an Integrated Operational Profile and Use Case Model
ISSRE '98 Proceedings of the The Ninth International Symposium on Software Reliability Engineering
Translating user experience to requirements
ICDHM'07 Proceedings of the 1st international conference on Digital human modeling
Understanding users' behavior with software operation data mining
Computers in Human Behavior
| Hi-index | 0.00 |
User-centered design influences product differentiation, especially in competitive markets. For industrial and interaction designers to be effective, they require a rich description of product usage and the resulting requirements. Historically, people involved in system design and development have described product usage in various ways, some more successful than others. Among the more common formats for capturing usage are use cases, scenarios, and concept-of-operations documents. Several years ago, Intel designers began to use the term usage model to describe product use in a stated context. While the concept was appealing and intuitive, agreeing on the usage model's structure and content proved far more challenging. A recently established usage model structure has three separate tiers: supporting data, overview, and usage details. Teams can use the description throughout product planning, design, development, and validation.This article is part of a special issue on requirements engineering.