Term
|
Definition
|
breaking a problem up by breaking it into pieces that we can understand and try to deal with
|
|
|
Term
|
Definition
|
putting together a large structure from small building blocks
|
|
|
Term
|
Definition
|
formal procedure for producing some result
|
|
|
Term
|
Definition
|
an instrument or automated system for accomplishing something in a better way
|
|
|
Term
|
Definition
|
a combination of tools and techniques that produce a particular product
|
|
|
Term
|
Definition
|
it represents a particular approach or philosophy for building software.
|
|
|
Term
|
Definition
|
human makes a mistake (error) in performing some software activity.
|
|
|
Term
|
Definition
|
departure from the system’s required behavior.
|
|
|
Term
|
Definition
|
something whose failure poses a threat to life or health
|
|
|
Term
|
Definition
|
quality is something we can recognize but not define
|
|
|
Term
|
Definition
|
quality is fitness for purpose
|
|
|
Term
|
Definition
|
quality is conformance to specification
|
|
|
Term
|
Definition
|
quality is tied to inherent product characteristics
|
|
|
Term
|
Definition
|
quality depends on the amount the customer is willing to pay
|
|
|
Term
|
Definition
|
the investment in terms of what is given up for other purposes
|
|
|
Term
|
Definition
|
company, organization, or person who is paying for the software system to be developed.
|
|
|
Term
|
Definition
|
the company, organization, or person who is building the software system for the customer
|
|
|
Term
|
Definition
|
the person or people who will actually use the system
|
|
|
Term
|
Definition
|
commercial off the shelf software.
|
|
|
Term
|
Definition
|
additional developers who build a subsystem and deliver it to the developers to be included in the final product
|
|
|
Term
|
Definition
|
code is incorporated whole (without additional code for integration), or it may require a separate integration process for building the links from the major system to the subsystem(s)
|
|
|
Term
|
Definition
|
what is included in a project and what is not
|
|
|
Term
|
Definition
|
something that happens in the system
|
|
|
Term
|
Definition
|
elements involved in the activities
|
|
|
Term
|
Definition
|
|
Term
|
Definition
|
incorporates a series of stages, each of which frees the previous system from another such constraint
|
|
|
Term
| Software development process |
|
Definition
|
any description of software development that contains some of the nine activities listed, organized so that together they produce tested code
|
|
|
Term
|
Definition
|
works with the customer, breaking down what the customer wants into discrete requirements
|
|
|
Term
|
Definition
|
generate a system-level description of what the system is to do
|
|
|
Term
|
Definition
|
write lines of code that implement what the requirements specify.
|
|
|
Term
|
Definition
|
catch faults that the programmers overlook
|
|
|
Term
|
Definition
|
fixes faults that are discovered in a system after it has been accepted
|
|
|
Term
|
Definition
|
prepare and store documents that are used during the life of the system, including requirements specifications, design descriptions, program documentation, training modules, test data, schedules, and more
|
|
|
Term
| Configuration management team |
|
Definition
|
maintains correspondence among the requirements of the design, the implementation, and the tests
|
|
|
Term
|
Definition
|
input converted to output
|
|
|
Term
|
Definition
|
input determined which function would be performed
|
|
|
Term
|
Definition
|
description of the problem at some level of generalization that allows us to concentrate on the key aspects of the problem without getting mired in the details
|
|
|
Term
|
Definition
|
translate the problem to another environment that we understand better
|
|
|
Term
|
Definition
|
the part of the system with which the user interacts
|
|
|
Term
|
Definition
|
systems where the software functions are not explicitly visible to the user
|
|
|