Test your basic knowledge |

Software Engineering Principles

Instructions:

Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can study here.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. What is metric- based testing?
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
Testing based on measurable factors.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
To 'do it right' to meet its requirements.

2. What is a software specification?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
A logical proposition that can be true or false.
A property when changes within a module do not result in changes in the modules that use it.
A detailed description of the function - inputs - processing - outputs - and special requirements of a software product; it provides the information needed to design and implement the program.

3. What is requirements elicitation?
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
A statement of what is to be provided by a computer system or software product.
Determining exactly what the program must do.

4. What does correct mean?

5. How can you verify the correctness of the software you develop?
(1) It works (2) It can be modified without excessive time and effort (3) It is reusable (4) It is completed on time and within budget
The program's inputs and outputs should be readable and understandable to users.
You can test the software to see if the correct outcome occurs
Simple statements like do this - then do this - then do that.

6. What is statement coverage?
When every statement in the program is executed at least once.
When you create your code - you break the problem into units called modules. Unit testing tests each individual module by itself. Later - you combine the working units together. Integration testing tests the group of units to see if they work togethe
Two less than symbols [<<].
The double colon operator (::).

7. What does efficient mean?
The program meets the demands of time or space in memory.
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.
The process of determining the degree to which software fulfills its intended purpose.
This is the idea that program verification activities can be performed throughout the program's life cycle - not just by testing the program after it is coded.

8. What is regression testing?
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.
A detailed description of the function - inputs - processing - outputs - and special requirements of a software product; it provides the information needed to design and implement the program.
The double colon operator (::).
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.

9. What is an acceptance test?
The process of testing the system in its real environment with real data.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Turning over the tested program to the customer or user (or instructor!).
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

10. What is top- down stepwise refinement?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
The approach in which the problem is first broken down into several large parts. Each of these parts is - in turn - divided into sections - the sections are subdivided - and so on. Details are deferred as long as possible.
This is the idea that program verification activities can be performed throughout the program's life cycle - not just by testing the program after it is coded.
Making changes to fix operational errors and to add or modify the function of the program.

11. What is a path?
The approach in which the problem is first broken down into several large parts. Each of these parts is - in turn - divided into sections - the sections are subdivided - and so on. Details are deferred as long as possible.
A combination of branches that might be traversed when a program or function is executed.
Coding a program in a computer language.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.

12. What is program verification?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Testing performed to integrate program modules that have already been independently unit tested.
When you create your code - you break the problem into units called modules. Unit testing tests each individual module by itself. Later - you combine the working units together. Integration testing tests the group of units to see if they work togethe
The process of determining the degree to which a software product fulfills its specifications.

13. What is bottom- up stepwise refinement?
A logical proposition that can be true or false.
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.
An object is an individual while a class is a description of a group of objects with similar properties and behaviors. Labrador dogs is an example of a class and Maggie is an example of an object.
The set of valid input data for a program or function.

14. What is an object?
(1) It works (2) It can be modified without excessive time and effort (3) It is reusable (4) It is completed on time and within budget
To 'do it right' to meet its requirements.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
The practice of only showing the information necessary for a user level and hiding the rest of the information. this makes programming in teams easier because you can see the big picture easier. Also - the programmer does not have to worry if the imp

15. What is testing and verification?
Detecting and fixing errors and demonstrating the correctness of the program.
A logical proposition that can be true or false.
Used to specify - visualize - construct - and document the components of a software system. This is particularly well suited for modeling object- oriented designs. The diagrams represent another form of abstraction.
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.

16. What is a test driver?
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
Specifying what the program must do (the functional requirements) and the constraints on the solution approach (non - functional requirements - such as what language to use).
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
The program's inputs and outputs should be readable and understandable to users.

17. What is implementation of the design?
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
The program meets the demands of time or space in memory.
The process of removing known errors.
Coding a program in a computer language.

18. What is testing?
It is possible to carry out exhaustive data coverage for this program.
Also called robustness. The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
The process of executing a program with data sets designed to discover errors.
Abstraction

19. What is implementing a test plan?
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
Running the program with the test cases listed in the test plan.
A statement of what is to be provided by a computer system or software product.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

20. What are functional subproblems?
Turning over the tested program to the customer or user (or instructor!).
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
When every statement in the program is executed at least once.
Simple statements like do this - then do this - then do that.

21. What is delivery?
Abstraction
When you create your code - you break the problem into units called modules. Unit testing tests each individual module by itself. Later - you combine the working units together. Integration testing tests the group of units to see if they work togethe
You can test the software to see if the correct outcome occurs
Turning over the tested program to the customer or user (or instructor!).

22. What is software engineering?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
The discipline devoted to the design - production - and maintenance of computer programs that are developed on time and within cost estimates - using tools that help to manage the size and complexity of the resulting software products.
It is possible to carry out exhaustive data coverage for this program.
You can test the software to see if the correct outcome occurs

23. What is the difference between an object and an object class?
An object is an individual while a class is a description of a group of objects with similar properties and behaviors. Labrador dogs is an example of a class and Maggie is an example of an object.
This is the idea that program verification activities can be performed throughout the program's life cycle - not just by testing the program after it is coded.
To take an object and move it from a general perspective to a precise level of detail. Variations of stepwise refinement include: top- down - bottom- up - functional decomposition - and even 'round- trip gestalt design.'
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.

24. What is unit testing?
Testing a module or function by itself.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
To 'do it right' to meet its requirements.
Testing based on measurable factors.

25. What is the relationship between the cost of error correction in software development and where/when errors are detected in terms of the software life cycle?
A notational tool that helps us determine our initial designs. CRC cards always contain information about the class name - responsibilities of the class and collaborations. CRC cards are great tools for refining an object- oriented design - especiall
Running the program with the test cases listed in the test plan.
Research has shown that the sooner you detect an error - the lest costly it will be to fix it. catching an error near the end of the software life cycle can be 100 times more costly that catching it at the beginning.
When every statement in the program is executed at least once.

26. What is a walk- through?
The process of determining the degree to which a software product fulfills its specifications.
A verification method in which a team performs a manual simulation of the program or design.
The approach in which the problem is first broken down into several large parts. Each of these parts is - in turn - divided into sections - the sections are subdivided - and so on. Details are deferred as long as possible.
When every statement in the program is executed at least once.

27. What is the scope resolution operator?
Testing performed to integrate program modules that have already been independently unit tested.
Research has shown that the sooner you detect an error - the lest costly it will be to fix it. catching an error near the end of the software life cycle can be 100 times more costly that catching it at the beginning.
The double colon operator (::).
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.

28. What is loose coupling?
Two greater than symbols [>>].
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A property when changes within a module do not result in changes in the modules that use it.

29. Explain the phrase 'life- cycle verification.'

30. What is an exception?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
The approach in which the problem is first broken down into several large parts. Each of these parts is - in turn - divided into sections - the sections are subdivided - and so on. Details are deferred as long as possible.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
A shared body of knowledge.

31. What is the insertion operator?
Two less than symbols [<<].
An object is an individual while a class is a description of a group of objects with similar properties and behaviors. Labrador dogs is an example of a class and Maggie is an example of an object.
The process of determining the degree to which a software product fulfills its specifications.
Actually using the program.

32. What is fault tolerance?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
Also called robustness. The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
The process of testing the system in its real environment with real data.

33. What is a test plan?
A verification method in which a team performs a manual simulation of the program or design.
The process of executing a program with data sets designed to discover errors.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
Used to specify - visualize - construct - and document the components of a software system. This is particularly well suited for modeling object- oriented designs. The diagrams represent another form of abstraction.

34. What is a branch?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Turning over the tested program to the customer or user (or instructor!).
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.

35. What is stepwise refinement?

36. What are requirements?
The process of removing known errors.
A shared body of knowledge.
A statement of what is to be provided by a computer system or software product.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.

37. What are software requirements?
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
A formal definition of the problem your program must solve.
A statement of what is to be provided by a computer system or software product.

38. What is problem analysis?
When every statement in the program is executed at least once.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
Understanding the nature of the problem to be solved.
Tracing an execution of a design or program on paper.

39. What is path testing?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Tracing an execution of a design or program on paper.
You can test the software to see if the correct outcome occurs
A testing technique whereby the tester tries to execute all possible paths in a program or function.

40. A program is to read in a numeric score (0 to 100) and display an appropriate letter grade (A - B - C - D - or F). Is exhaustive data coverage possible for this program?
It is possible to carry out exhaustive data coverage for this program.
The process of removing known errors.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
(1) It works (2) It can be modified without excessive time and effort (3) It is reusable (4) It is completed on time and within budget

41. What is a detailed specification?
Determining exactly what the program must do.
A formal definition of the problem your program must solve.
(1) It works (2) It can be modified without excessive time and effort (3) It is reusable (4) It is completed on time and within budget
The discipline devoted to the design - production - and maintenance of computer programs that are developed on time and within cost estimates - using tools that help to manage the size and complexity of the resulting software products.

42. What is the unified modeling language (UML)?
Testing based on measurable factors.
Used to specify - visualize - construct - and document the components of a software system. This is particularly well suited for modeling object- oriented designs. The diagrams represent another form of abstraction.
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

43. What is integration testing?
Testing performed to integrate program modules that have already been independently unit tested.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
You can test the software to see if the correct outcome occurs
Used to specify - visualize - construct - and document the components of a software system. This is particularly well suited for modeling object- oriented designs. The diagrams represent another form of abstraction.

44. What is information hiding?
The practice of hiding details of a function or data structure with the goal of controlling access to the details of a module or structure.
Running the program with the test cases listed in the test plan.
The program's inputs and outputs should be readable and understandable to users.
[Input] All values from 1 to 100. [Expected Output] For input 0-59 => F. For input 60-69 => D. For input 70-79 => C. For input 80-89 => B. For input 90-100 => A.

45. What is requirements specification?
A detailed description of the function - inputs - processing - outputs - and special requirements of a software product; it provides the information needed to design and implement the program.
This is the idea that program verification activities can be performed throughout the program's life cycle - not just by testing the program after it is coded.
A combination of branches that might be traversed when a program or function is executed.
Specifying what the program must do (the functional requirements) and the constraints on the solution approach (non - functional requirements - such as what language to use).

46. What is abstraction?
Specifying what the program must do (the functional requirements) and the constraints on the solution approach (non - functional requirements - such as what language to use).
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
[Input] All values from 1 to 100. [Expected Output] For input 0-59 => F. For input 60-69 => D. For input 70-79 => C. For input 80-89 => B. For input 90-100 => A.

47. What are class - responsibility - and collaboration (CRC) cards?
When you create your code - you break the problem into units called modules. Unit testing tests each individual module by itself. Later - you combine the working units together. Integration testing tests the group of units to see if they work togethe
A notational tool that helps us determine our initial designs. CRC cards always contain information about the class name - responsibilities of the class and collaborations. CRC cards are great tools for refining an object- oriented design - especiall
It is possible to carry out exhaustive data coverage for this program.
Actually using the program.

48. What are preconditions?
The program's inputs and outputs should be readable and understandable to users.
The discipline devoted to the design - production - and maintenance of computer programs that are developed on time and within cost estimates - using tools that help to manage the size and complexity of the resulting software products.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
Specifying what the program must do (the functional requirements) and the constraints on the solution approach (non - functional requirements - such as what language to use).

49. What is white- box testing?
Two less than symbols [<<].
A detailed description of the function - inputs - processing - outputs - and special requirements of a software product; it provides the information needed to design and implement the program.
Running the program with the test cases listed in the test plan.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

50. What is the functional domain?
Research has shown that the sooner you detect an error - the lest costly it will be to fix it. catching an error near the end of the software life cycle can be 100 times more costly that catching it at the beginning.
This is the idea that program verification activities can be performed throughout the program's life cycle - not just by testing the program after it is coded.
The set of valid input data for a program or function.
A property when changes within a module do not result in changes in the modules that use it.