CSCI 310 Final Exam Questions with Verified
Correct Answers
test adequacy criteria
the adequacy score of a test suite is the percentage of "coverable" items (as defined by the
criteria) that are covered by the test suite
code-and-fix
write some code, debug it, repeat until finished
👎 lack of structure
👎 uncertain design requirements
spiral model
deals with risks early in the software life-cycle when there is more time to deal with problems
the risks may cause and before there is significant amount of work completed which can be
affected
V-model
an extension of waterfall that includes testing at each phase, ensuring verification and
validation each time
fault
bug
related to the code - necessary (but not sufficient) condition for occurrence of a failure
error
the cause of a fault (usually human error)
,coincidental correctness
when a program executes a fault but does not fail
black-box test selection criterion
test selection criterion based on a specification
white-box test test selection criterion
test selection criterion based on the code
functional software quality
how well the behavior conforms to design/specifications
structural software quality
how well the functionality is implemented
throwaway prototyping
creation of a model that will eventually be discarded rather than incorporated into the final
version of the software
evolutionary prototyping
building a very robust prototype in a structured manner and then constantly refining it
rational unified process (RUP)
development process that divides itself into four distinct phases: inception, elaboration,
construction, and transition
- develop iteratively
- manage requirements
- use components
, - model visually
- verify quality
- control changes
cleanroom
a software development philosophy that is based on avoiding software defects by using
formal methods of development and a rigorous inspection process
three boxes model
begins with external view (black box), transformed into a state machine (state box), fully
developed into a procedure (clear box)
the black box
a view of an object that hides data implementation and process implementation - describes
how a system responds to stimuli, usually in a formal specification language
the state box
a view of an object that shows data implementation but hides process implementation -
describes how "state" information is transformed
the clear box
a view of an object that shows both data implementation and process implementation - goal
of stepwise refining procedures to prove them correct
formal specification
the software to be developed is formally specified. a state-transition model which shows
system responses to stimuli is used to express the specification.
incremental development
Correct Answers
test adequacy criteria
the adequacy score of a test suite is the percentage of "coverable" items (as defined by the
criteria) that are covered by the test suite
code-and-fix
write some code, debug it, repeat until finished
👎 lack of structure
👎 uncertain design requirements
spiral model
deals with risks early in the software life-cycle when there is more time to deal with problems
the risks may cause and before there is significant amount of work completed which can be
affected
V-model
an extension of waterfall that includes testing at each phase, ensuring verification and
validation each time
fault
bug
related to the code - necessary (but not sufficient) condition for occurrence of a failure
error
the cause of a fault (usually human error)
,coincidental correctness
when a program executes a fault but does not fail
black-box test selection criterion
test selection criterion based on a specification
white-box test test selection criterion
test selection criterion based on the code
functional software quality
how well the behavior conforms to design/specifications
structural software quality
how well the functionality is implemented
throwaway prototyping
creation of a model that will eventually be discarded rather than incorporated into the final
version of the software
evolutionary prototyping
building a very robust prototype in a structured manner and then constantly refining it
rational unified process (RUP)
development process that divides itself into four distinct phases: inception, elaboration,
construction, and transition
- develop iteratively
- manage requirements
- use components
, - model visually
- verify quality
- control changes
cleanroom
a software development philosophy that is based on avoiding software defects by using
formal methods of development and a rigorous inspection process
three boxes model
begins with external view (black box), transformed into a state machine (state box), fully
developed into a procedure (clear box)
the black box
a view of an object that hides data implementation and process implementation - describes
how a system responds to stimuli, usually in a formal specification language
the state box
a view of an object that shows data implementation but hides process implementation -
describes how "state" information is transformed
the clear box
a view of an object that shows both data implementation and process implementation - goal
of stepwise refining procedures to prove them correct
formal specification
the software to be developed is formally specified. a state-transition model which shows
system responses to stimuli is used to express the specification.
incremental development
