 | Helmut A. Partsch - 1990 - 493 lapas
...defined by 1) 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 document.... | |
 | Jan A. Bergstra, Loe M.G. Feijs - 1991 - 434 lapas
...by 1. "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 document.... | |
 | Allen Kent, James G. Williams - 1997 - 400 lapas
...as (1) 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 document.... | |
 | Dean Leffingwell, Don Widrig - 2000 - 491 lapas
...solve a prohlem to achieve an ohjective A software capahility that must he met or possessed hy a system or a system component to satisfy a contract,...standard, specification, or other formally imposed documentation Software requirements are those things that the software does on hehalf of the user or... | |
 | Michael J. Smith, Gavriel Salvendy - 2001 - 1128 lapas
...as (l) 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 documents.... | |
 | Dirk Draheim, Gerald Weber - 2005 - 372 lapas
...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 a contract, standard, specification, or other formally imposed documents,... | |
 | S. A. KELKAR - 2004 - 324 lapas
...REQUIREMENTS 1. 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 to satisfy contract, standard, specification, or other formally imposed document... Here the reference... | |
 | Ayba1/4ke Aurum - 2005 - 478 lapas
...as: (1) 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 documents,... | |
 | John Clarkson, Claudia Eckert - 2005 - 560 lapas
...as: 1. 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 document.... | |
 | Marvin Zelkowitz - 2006 - 344 lapas
...as: "(1) 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 documents.... | |
| |
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... 
