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 testing?
When every statement in the program is executed at least once.
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
The process of executing a program with data sets designed to discover errors.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.

2. What is a stub?
A special function that can be used in top- down testing to stand in for a lower- level function.
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 document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.

3. What is the scope resolution operator?
The double colon operator (::).
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
Making changes to fix operational errors and to add or modify the function of the program.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.

4. What does usable mean?

5. What is the software process?
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
Coding a program in a computer language.
The program meets the demands of time or space in memory.
The program's inputs and outputs should be readable and understandable to users.

6. 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.
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 process of removing known errors.
A property when changes within a module do not result in changes in the modules that use it.

7. Differentiate between unit testing and integration testing.
[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.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
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.

8. What is information hiding and why is it considered a good software development practice.
Detecting and fixing errors and demonstrating the correctness of the program.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
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 formal definition of the problem your program must solve.

9. What is black- box testing?

10. What is high- and low- level design?

11. A program is to read in a numeric score (0 to 100) and display an appropriate letter grade (A - B - C - D - or F). Devise a test plan for this program.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
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
[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.
Abstraction

12. What is information hiding?
To 'do it right' to meet its requirements.
The process of determining the degree to which software fulfills its intended purpose.
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.

13. What is statement coverage?
When every statement in the program is executed at least once.
The set of valid input data for a program or function.
The double colon operator (::).
The process of removing known errors.

14. What does complete mean?

15. What is integration testing?
A special function that can be used in top- down testing to stand in for a lower- level function.
Testing performed to integrate program modules that have already been independently unit tested.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
The program meets the demands of time or space in memory.

16. 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 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 functional domain consists of the whole numbers from 0 to 100.
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
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.

17. What is fault tolerance?
A logical proposition that can be true or false.
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.
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 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

18. What is delivery?
Turning over the tested program to the customer or user (or instructor!).
Determining exactly what the program must do.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)

19. What is metric- based testing?
Tracing an execution of a design or program on paper.
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
Testing based on measurable factors.
You can test the software to see if the correct outcome occurs

20. What is a module?
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.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Testing performed to integrate program modules that have already been independently unit tested.
A cohesive system subunit that performs a share of the work.

21. What is the unified modeling language (UML)?
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.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
A formal definition of the problem your program must solve.
Simple statements like do this - then do this - then do that.

22. What is an object?
Making changes to fix operational errors and to add or modify the function of the program.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
The process of testing the system in its real environment with real data.
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.

23. 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 verification method in which a team performs a manual simulation of the program or design.
(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
A standard - integrated set of software engineering tools and techniques used on a project by an organization.

24. What is operation?
Actually using the program.
Two greater than symbols [>>].
When every statement in the program is executed at least once.
To 'do everything' specified to meet its requirements.

25. Give examples of the relationship between the cost of error correction in software development and when/where errors are detected in terms of the software life cycle.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
A verification method in which a team performs a manual simulation of the program or design.
Coding a program in a computer language.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator

26. What is robustness?
Abstraction
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.
Making changes to fix operational errors and to add or modify the function of the program.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

27. What is a path?
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
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.
Simple statements like do this - then do this - then do that.
A combination of branches that might be traversed when a program or function is executed.

28. What is inspection?
A shared body of knowledge.
Detecting and fixing errors and demonstrating the correctness of the program.
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.
Making changes to fix operational errors and to add or modify the function of the program.

29. What is regression testing?
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.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
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

30. What is an assertion?
A logical proposition that can be true or false.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
To 'do it right' to meet its requirements.

31. What is clear- box testing?
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 process of determining the degree to which software fulfills its intended purpose.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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.

32. What is a walk- through?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
A verification method in which a team performs a manual simulation of the program or design.
To 'do everything' specified to meet its requirements.
A shared body of knowledge.

33. What is requirements specification?
Testing based on measurable factors.
A statement of what is to be provided by a computer system or software product.
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).

34. What is program validation?
Understanding the nature of the problem to be solved.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
The process of determining the degree to which software fulfills its intended purpose.
The process of determining the degree to which a software product fulfills its specifications.

35. What is round- trip gestalt design?
Coding a program in a computer language.
The set of valid input data for a program or function.
Testing based on measurable factors.
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

36. What is white- box testing?
(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.
The process of executing a program with data sets designed to discover errors.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

37. 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
Simple statements like do this - then do this - then do that.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
You can test the software to see if the correct outcome occurs

38. What is bottom- up stepwise refinement?
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
Testing based on measurable factors.
A combination of branches that might be traversed when a program or function is executed.
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.

39. What is a hierarchy of objects?
Reusing objects and processes to implement more complex objects and processes.
Running the program with the test cases listed in the test plan.
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.

40. What does correct mean?

41. What is problem analysis?
Understanding the nature of the problem to be solved.
Testing based on measurable factors.
Actually using the program.
To 'do everything' specified to meet its requirements.

42. What is a technique used by good problem solvers for dealing with complexity?
Abstraction
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.
A verification method in which a team performs a manual simulation of the program or design.
You can test the software to see if the correct outcome occurs

43. What is the insertion 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.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Two less than symbols [<<].

44. What is a branch?
Testing based on measurable factors.
A shared body of knowledge.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
The functional domain consists of the whole numbers from 0 to 100.

45. What is an exception?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
A structure of tasks with a main module and subsections.
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).
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.

46. What is implementing a test plan?
Running the program with the test cases listed in the test plan.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
It is possible to carry out exhaustive data coverage for this program.
The program's inputs and outputs should be readable and understandable to users.

47. What is requirements elicitation?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
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.
Determining exactly what the program must do.

48. The difference between unit testing and integration testing.
(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.
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 testing the system in its real environment with real data.

49. What is testing and verification?
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.'
Reusing objects and processes to implement more complex objects and processes.
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.
Detecting and fixing errors and demonstrating the correctness of the program.

50. What is implementation of the design?
Determining exactly what the program must do.
Coding a program in a computer language.
Abstraction
Testing based on measurable factors.