A High Level Requirement is a description of a desirable behavior or property of the tool necessary or useful to carry out an activity or engage in a practice meaningful to the user. A HLR describes what is needed from the end-user’s point of view and not how this is to be achieved. High Level requirements encompass both functional requirements as well as non functional requirements such as interoperability with existing systems, maintainability, safety, usability, etc. Therefore, they can also refer to circumstances and context constraints relevant to a certain activity. HLRs are focused on the actual stakeholders needs. HLRs should be backed up in Driving Objectives as well as user’s activities and practices.

Back to the Co-Evolutionary Design Glossary
  Page Info My Prefs Log in
This page (revision-3) last changed on 18:24 25-Mar-2017 by ChristophRichter.

Referenced by

JSPWiki v2.4.102