 | British Computer Society. Working Group on Testing - 1986 - 140 lapas
...section covers. The first thing we must do is define what a requirement is. In this book we define it as a condition or capability needed by a user to solve a problem or achieve an objective. So, a requirement docs not involve any design work, but is just a consequence of the business (or any... | |
 | Wilhelm Schäfer, Pere Botella - 1995 - 540 lapas
...have used. REMAP introduces new primitive types for requirements rationale management: Requirements: a capability needed by a user to solve a problem or achieve an objective. A capability that must be met or possessed by a system or system component to satisfy a contract, standard,... | |
 | Pankaj Jalote - 1997 - 520 lapas
...used throughout the book. 3.1 Software Requirements IEEE defines a requirement as "(1) A condition of capability needed by a user to solve a problem or achieve an objective; (2) A condition or a capability that must be met or possessed by a system ... to satisfy a contract, standard, specification,... | |
 | Shirley A. Becker, James A. Whittaker - 1997 - 212 lapas
...requirement is a condition or capability a system must possess to satisfy a contract or standard, or needed by a user to solve a problem or achieve an objective. (IEEE Computer Society, 1990). The above definition indicates that there may be two kinds of requirements:... | |
 | Dirk Draheim, Gerald Weber - 2005 - 396 lapas
...capability offered to a user, or (ii) a defined behaviour. In [157] a requirement is defined as: (i) a condition or capability needed by a user to solve a problem or achieve an objective, (ii) a condition or capability that must be met or possessed by a system or system component to satisfy... | |
 | Nandish V. Patel - 2005 - 328 lapas
...requirements. The Institute for Electrical and Electronic Engineers (IEEE) Standard 610 defines requirements as: 1 A condition or capability needed by a user to...problem or achieve an objective. 2 A condition or capacity that must be met or possessed by a system or system component to satisfy a contract, standard,... | |
 | Siva G. Narendra, Anantha P. Chandrakasan - 2006 - 308 lapas
...determines if violations of defined, acceptable behavior have occurred. requirement A requirement is: • A condition or capability needed by a user to solve a problem or achieve an objective. • A condition or capability that must be met or possessed by a system or a system component to satisfy... | |
 | Tom Gilb - 2005 - 480 lapas
...requirements, condition constraints and design constraints. Given below are some IEEE definitions: Requirement: "a condition or capability needed by a user to solve a problem or achieve an objective." <- IEEE 610.12-1990. Example of an IEEE definition of'requirement': the term 'user' is probably not... | |
 | Grant Martin, Brian Bailey, Andrew Piziali - 2010 - 488 lapas
...an invalid path. See section 13.6, "Properties and Assertions." Requirement (IEEE) A requirement is a: • Condition or capability needed by a user to solve a problem or achieve an objective. • Condition or capability that must be met or possessed by a system or a system component to satisfy... | |
 | Hakeem Shittu - 2007 - 220 lapas
...stated conditions for a specified period of time, or for a specified number of operations. requirement - A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification,... | |
| |
A condition or capability needed by a user to solve a problem or achieve an objective. (2) A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed... 