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. Explain the phrase 'life- cycle verification.'

2. What is a test driver?
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be 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
Making changes to fix operational errors and to add or modify the function of the program.

3. What is unit testing?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
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
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.
Testing a module or function by itself.

4. What is metric- based testing?
Detecting and fixing errors and demonstrating the correctness of the program.
The double colon operator (::).
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Testing based on measurable factors.

5. What are class - responsibility - and collaboration (CRC) cards?
Determining exactly what the program must do.
Making changes to fix operational errors and to add or modify the function of the program.
The program's inputs and outputs should be readable and understandable to users.
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

6. What is a hierarchy of objects?
Coding a program in a computer language.
Reusing objects and processes to implement more complex objects and processes.
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.
Testing a program or function based on the possible input values - treating the code as a 'black box.'

7. What are postconditions?
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
A combination of branches that might be traversed when a program or function is executed.
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.'
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.

8. What is a path?
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.
Turning over the tested program to the customer or user (or instructor!).
A combination of branches that might be traversed when a program or function is executed.
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.'

9. What is the extraction operator?
A statement of what is to be provided by a computer system or software product.
Two greater than symbols [>>].
You can test the software to see if the correct outcome occurs
Tracing an execution of a design or program on paper.

10. What is a module?
This program design approach encourages programming in logical action units - called functions. The main module of the design becomes the main program (also called the main function) - and subsections develop into functions. This is top- down stepwis
The program meets the demands of time or space in memory.
The process of removing known errors.
A cohesive system subunit that performs a share of the work.

11. Differentiate between unit testing and integration testing.
Unit testing is the testing of a single unit of the program (for instance - a function). Integration testing is the testing of groups of already tested units to make sure that they interact correctly and that the whole program works according to its
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
The functional domain consists of the whole numbers from 0 to 100.

12. What does correct mean?

13. The difference between unit testing and integration testing.
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 software fulfills its intended purpose.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
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

14. What are the goals of quality software?
Two greater than symbols [>>].
Two less than symbols [<<].
(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 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.

15. What is problem analysis?
Making changes to fix operational errors and to add or modify the function of the program.
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
Understanding the nature of the problem to be solved.
Testing performed to integrate program modules that have already been independently unit tested.

16. What is information hiding and why is it considered a good software development practice.
The program's inputs and outputs should be readable and understandable to users.
The program meets the demands of time or space in memory.
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 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

17. What are preconditions?
A verification method in which a team performs a manual simulation of the program or design.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
It is possible to carry out exhaustive data coverage for this program.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.

18. What does usable mean?

19. What is robustness?
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
(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
[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.
The double colon operator (::).

20. What is a software specification?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
Defines the stepwise refinement approach to object- oriented design suggested by Grady Booch. First - the tangible items and events in the problem domain are identified and assigned to candidate classes and objects. Next - the external properties and
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.

21. What is the insertion operator?
A logical proposition that can be true or false.
Testing performed to integrate program modules that have already been independently unit tested.
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
Two less than symbols [<<].

22. What is statement coverage?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
When every statement in the program is executed at least once.
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.

23. What are software requirements?
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.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
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.

24. What is path testing?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Defines the stepwise refinement approach to object- oriented design suggested by Grady Booch. First - the tangible items and events in the problem domain are identified and assigned to candidate classes and objects. Next - the external properties and
Understanding the nature of the problem to be solved.
A cohesive system subunit that performs a share of the work.

25. What is program verification?
Abstraction
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.
The process of determining the degree to which a software product fulfills its specifications.
A logical proposition that can be true or false.

26. What is maintenance?
Making changes to fix operational errors and to add or modify the function of the program.
Testing a module or function by itself.
[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.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

27. What is a walk- through?
A statement of what is to be provided by a computer system or software product.
A verification method in which a team performs a manual simulation of the program or design.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
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.

28. What is inspection?
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
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
A verification method in which one member of a team reads the program or design line by line and the other members point out errors.
Unit testing is the testing of a single unit of the program (for instance - a function). Integration testing is the testing of groups of already tested units to make sure that they interact correctly and that the whole program works according to its

29. What is round- trip gestalt design?
You can test the software to see if the correct outcome occurs
Two greater than symbols [>>].
[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.
Defines the stepwise refinement approach to object- oriented design suggested by Grady Booch. First - the tangible items and events in the problem domain are identified and assigned to candidate classes and objects. Next - the external properties and

30. What are requirements?
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.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
A statement of what is to be provided by a computer system or software product.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.

31. 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).
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
A verification method in which a team performs a manual simulation of the program or design.

32. What is a branch?
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.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
A property when changes within a module do not result in changes in the modules that use it.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.

33. What is a detailed specification?
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
The process of removing known errors.
A statement of what is to be provided by a computer system or software product.
A formal definition of the problem your program must solve.

34. What is the functional domain?
Reusing objects and processes to implement more complex objects and processes.
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).
The set of valid input data for a program or function.

35. What is a test plan?
A property when changes within a module do not result in changes in the modules that use it.
Two greater than symbols [>>].
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.

36. What are functional subproblems?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
The program meets the demands of time or space in memory.
Simple statements like do this - then do this - then do that.

37. What is information hiding?
Two less than symbols [<<].
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.
It is possible to carry out exhaustive data coverage for this 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.

38. What is requirements elicitation?
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.
Determining exactly what the program must do.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

39. Give a specific C++ language attribute that supports information hiding.

40. What is testing?
The process of executing a program with data sets designed to discover errors.
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.
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.
A special function that can be used in top- down testing to stand in for a lower- level function.

41. What is testing and verification?
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
Detecting and fixing errors and demonstrating the correctness of the program.
The process of removing known errors.
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.

42. 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?
Understanding the nature of the problem to be solved.
Detecting and fixing errors and demonstrating the correctness of 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.
It is possible to carry out exhaustive data coverage for this program.

43. What is an acceptance test?
This program design approach encourages programming in logical action units - called functions. The main module of the design becomes the main program (also called the main function) - and subsections develop into functions. This is top- down stepwis
The process of testing the system in its real environment with real data.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

44. What is the software process?
You can test the software to see if the correct outcome occurs
The process of testing the system in its real environment with real data.
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 standard - integrated set of software engineering tools and techniques used on a project by an organization.

45. What is a class?
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
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
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
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

46. What is clear- box testing?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

47. A program is to read in a numeric score (0 to 100) and display an appropriate letter grade (A - B - C - D - or F). What is the functional domain of this program?
The program meets the demands of time or space in memory.
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 functional domain consists of the whole numbers from 0 to 100.
A cohesive system subunit that performs a share of the work.

48. What is software engineering?
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
A special function that can be used in top- down testing to stand in for a lower- level function.
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 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.

49. What is debugging?
Running the program with the test cases listed in the test plan.
The process of removing known errors.
The program's inputs and outputs should be readable and understandable to users.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.

50. What is integration testing?
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
Testing performed to integrate program modules that have already been independently unit tested.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
(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