Term
|
Definition
| expression of desired behavior |
|
|
Term
|
Definition
| during this time we determine which requirements will be fulfilled by our software system. |
|
|
Term
|
Definition
| during this time a plan is devised for how the specific behavior will be implemented. |
|
|
Term
| Requirements (systems) analyst |
|
Definition
| determines the requirements for a proposed software system. |
|
|
Term
|
Definition
| required behavior in terms of required activities, such as reactions to inputs, and the state of each entity before and after an activity occurs |
|
|
Term
| Quality (nonfunctional) requirement |
|
Definition
| some quality characteristic that the software solution must possess, such as a fast response time, ease of use, high reliability, or low maintenance costs |
|
|
Term
|
Definition
| design decision, such as platform choice or interface components, that has already been made and that restricts the set of solutions to our problems |
|
|
Term
|
Definition
| restriction on the techniques or resources that can be used to build the system |
|
|
Term
|
Definition
| establish clear-cut acceptance tests for these requirements |
|
|
Term
|
Definition
| aimed at a business audience, such as clients, customers, and users; complete listening of everything the customer wants to achieve |
|
|
Term
| Requirements specification |
|
Definition
| aimed at a technical audience, such as designers, testers and project managers; restates the requirements as a specification of how the proposed system should behave |
|
|
Term
|
Definition
| two requirements are inconsistent if it is impossible to satisfy both simultaneously |
|
|
Term
|
Definition
| a set of requirements is complete if it specifies the required behavior and output for all possible inputs in all possible states under all possible constraints |
|
|
Term
|
Definition
| all states, state changes, inputs, products and constraints are described by some requirement |
|
|
Term
|
Definition
| if there are no undefined terms among the requirements |
|
|
Term
|
Definition
| if the requirements suggest acceptance tests that would clearly demonstrate |
|
|
Term
|
Definition
| represents a collection of real-world objects that have common properties and behaviors |
|
|
Term
|
Definition
| annotation on an entity that describes data or properties associated with the entity |
|
|
Term
|
Definition
| membership or whose relations to members of other entities may change over time |
|
|
Term
| Unified Modeling Language |
|
Definition
| collection of notations used to document software specifications and designs |
|
|
Term
|
Definition
| sophisticated ER diagram related to the classes in the specification |
|
|
Term
|
Definition
| represents a collection of similarly typed entries |
|
|
Term
|
Definition
| represented as an underlined attribute, is a data value that is shared by all instances of the class |
|
|
Term
|
Definition
| operation performed by the abstract class, rather than by class members |
|
|
Term
|
Definition
| special type of aggregation, in which instances of the compound class are physically constructed from instances of the component classes |
|
|
Term
|
Definition
| graphical description of a sequence of events that are exchanged between real world entities |
|
|
Term
|
Definition
| software that is developed to learn more about a problem or about a proposed solution, and that is never intended to be part of the delivered software |
|
|
Term
|
Definition
| software that is developed not only to help us answer questions but also to be incorporated into the final product |
|
|
Term
|
Definition
| involving building software in order to answer questions about the requirement |
|
|
