CS 3140 FINAL EXAM QUESTIONS &
ANSWERS(RATED A+)
External Quality - ANSWERPerspective of the stakeholders (Usability, efficiency,
portability, reliability, functionality)
Java Development Kit (JDK) - ANSWERCompiles code in portable .class file
Java Runtime Environment (JRE) - ANSWERStandardized interface used to run
Java programs
Java Virtual Machine (JVM) - ANSWERSoftware that acts like a separate computer
borrowed from the host machine by interpreting code at runtime
Just In Time Compiler (JIT) - ANSWERHandles executing the code
How are packages named? - ANSWERReverse internet domain name
(edu.virginia.cs)
Internal Quality - ANSWERPerspective of the programmer (Maintainability,
changeability, analyzability, reusability, stability, testability)
Verification - ANSWEREvaluating a system to determine whether the products
satisfy the conditions imposed at the start phase
Validation - ANSWEREvaluating a system to determine whether it satisfies the
specified requirements
Defect - ANSWERAn existing problem according to the software specification in the
product that has yet to be discovered
Failure - ANSWERThe inability of the software system to perform its function
according to specification
Mistake - ANSWERA human error that produces something incorrect
Error - ANSWERThe difference between the current state and the correct state
Equivalence Test Case - ANSWERTest cases with the assumption the software
behaves under normal, predictable conditions
Boundary Test Case - ANSWERTest cases with the assumption of interesting,
unique conditions
, Exception Case - ANSWERTest cases that cannot be meaningfully executed
correctly and should throw exception
Robustness Test Case - ANSWERTest cases that are syntactically valid but
semantically meaningless
Test Driven Development (TDD) - ANSWERProcess of writing tests first before
writing code
Black Box Testing - ANSWERSelect tests considering the specification and interface
of a module (Focus on interface opposed to the implementation)
Coincidental Cohesion - ANSWERWhen elements are combined into a module by
coincidence (Not related to each other)
Logical Cohesion - ANSWERElements are grouped on the basis of the same general
activity or similar interface (Vastly different implementations)
Temporal Cohesion - ANSWERWhen elements are grouped as they occur at around
the same time and are otherwise unrelated
Procedural Cohesion - ANSWERUnrelated elements that are passed in a particular
order (Does not contribute to a single functional purpose in a clear way)
Exhaustive Testing - ANSWERTest cases includes all possible inputs (Almost never
feasible)
Random Testing - ANSWERTest cases try different random inputs (Not efficient)
Equivalence Partitioning - ANSWERTest cases try to find inputs that behave similarly
and test the groups of inputs at least once
White Box Testing - ANSWERDesigning tests to take into the structure and contents
of the source code into account (Emphasis on code coverage)
Statement Coverage - ANSWERPercentage of statements were executed by a test
Condition Coverage - ANSWERBoolean variables have both true and false in at
least one test
Branch Coverage - ANSWERFor each if, are enter and skip/else evaluated and
for every loop, is each normal iteration and passes evaluated
Path Coverage - ANSWEREvery possible path through the code taken
Defensive Programming - ANSWERConsider all the ways the program could fail that
are not the fault of the program's developer (User error)
ANSWERS(RATED A+)
External Quality - ANSWERPerspective of the stakeholders (Usability, efficiency,
portability, reliability, functionality)
Java Development Kit (JDK) - ANSWERCompiles code in portable .class file
Java Runtime Environment (JRE) - ANSWERStandardized interface used to run
Java programs
Java Virtual Machine (JVM) - ANSWERSoftware that acts like a separate computer
borrowed from the host machine by interpreting code at runtime
Just In Time Compiler (JIT) - ANSWERHandles executing the code
How are packages named? - ANSWERReverse internet domain name
(edu.virginia.cs)
Internal Quality - ANSWERPerspective of the programmer (Maintainability,
changeability, analyzability, reusability, stability, testability)
Verification - ANSWEREvaluating a system to determine whether the products
satisfy the conditions imposed at the start phase
Validation - ANSWEREvaluating a system to determine whether it satisfies the
specified requirements
Defect - ANSWERAn existing problem according to the software specification in the
product that has yet to be discovered
Failure - ANSWERThe inability of the software system to perform its function
according to specification
Mistake - ANSWERA human error that produces something incorrect
Error - ANSWERThe difference between the current state and the correct state
Equivalence Test Case - ANSWERTest cases with the assumption the software
behaves under normal, predictable conditions
Boundary Test Case - ANSWERTest cases with the assumption of interesting,
unique conditions
, Exception Case - ANSWERTest cases that cannot be meaningfully executed
correctly and should throw exception
Robustness Test Case - ANSWERTest cases that are syntactically valid but
semantically meaningless
Test Driven Development (TDD) - ANSWERProcess of writing tests first before
writing code
Black Box Testing - ANSWERSelect tests considering the specification and interface
of a module (Focus on interface opposed to the implementation)
Coincidental Cohesion - ANSWERWhen elements are combined into a module by
coincidence (Not related to each other)
Logical Cohesion - ANSWERElements are grouped on the basis of the same general
activity or similar interface (Vastly different implementations)
Temporal Cohesion - ANSWERWhen elements are grouped as they occur at around
the same time and are otherwise unrelated
Procedural Cohesion - ANSWERUnrelated elements that are passed in a particular
order (Does not contribute to a single functional purpose in a clear way)
Exhaustive Testing - ANSWERTest cases includes all possible inputs (Almost never
feasible)
Random Testing - ANSWERTest cases try different random inputs (Not efficient)
Equivalence Partitioning - ANSWERTest cases try to find inputs that behave similarly
and test the groups of inputs at least once
White Box Testing - ANSWERDesigning tests to take into the structure and contents
of the source code into account (Emphasis on code coverage)
Statement Coverage - ANSWERPercentage of statements were executed by a test
Condition Coverage - ANSWERBoolean variables have both true and false in at
least one test
Branch Coverage - ANSWERFor each if, are enter and skip/else evaluated and
for every loop, is each normal iteration and passes evaluated
Path Coverage - ANSWEREvery possible path through the code taken
Defensive Programming - ANSWERConsider all the ways the program could fail that
are not the fault of the program's developer (User error)
