Non-functional requirements provide the glue between functional requirements and architectural decisions. Thus, it is important to elicit and specify the nonfunctional requirements precisely. In practice, however, they are mostly neglected. In this paper, we sketch an approach developed in the context of the EMPRESS project, which allows efficiency requirements to be elicited in conjunction with use case. This is part of a more general, experience -based approach to elicit and specify nonfunctional requirements in concert with functional requirements and architecture
