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 deskchecking?
To 'do it right' to meet its requirements.
Tracing an execution of a design or program on paper.
When every statement in the program is executed at least once.
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 are preconditions?
Reusing objects and processes to implement more complex objects and processes.
When every statement in the program is executed at least once.
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.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.

3. What is the insertion operator?
To 'do everything' specified to meet its requirements.
A statement of what is to be provided by a computer system or software product.
Two less than symbols [<<].
A statement of what is to be provided by a computer system or software product.

4. What is information hiding?
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.
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
The program's inputs and outputs should be readable and understandable to users.

5. Explain what we mean by 'ideaware'.
The program meets the demands of time or space in memory.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
A shared body of knowledge.
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.

6. What is top- down stepwise refinement?
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 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.
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 property when changes within a module do not result in changes in the modules that use it.

7. What is a technique used by good problem solvers for dealing with complexity?
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.
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.
Abstraction

8. How can you verify the correctness of the software you develop?
Testing a program or function based on the possible input values - treating the code as a 'black box.'
The set of valid input data for a program or function.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
You can test the software to see if the correct outcome occurs

9. What are class - responsibility - and collaboration (CRC) cards?
Tracing an execution of a design or program on paper.
A statement of what is to be provided by a computer system or software product.
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
Turning over the tested program to the customer or user (or instructor!).

10. What is program verification?
A structure of tasks with a main module and subsections.
The process of determining the degree to which a software product fulfills its specifications.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Actually using the program.

11. What is black- box testing?

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

12. What is a detailed specification?
A formal definition of the problem your program must solve.
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
Detecting and fixing errors and demonstrating the correctness of the program.
Making changes to fix operational errors and to add or modify the function of the program.

13. What does complete mean?

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

14. What is a stub?
A special function that can be used in top- down testing to stand in for a lower- level function.
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
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.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.

15. 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 removing known errors.
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.
When every statement in the program is executed at least once.

16. What is implementing a test plan?
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.
Running the program with the test cases listed in the test plan.
Two greater than symbols [>>].

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

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

18. What is round- trip gestalt design?
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.
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
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.

19. What are requirements?
It is possible to carry out exhaustive data coverage for this program.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
A statement of what is to be provided by a computer system or software product.
The process of determining the degree to which software fulfills its intended purpose.

20. What is an algorithm?
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator

21. What is information hiding and why is it considered a good software development practice.
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 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.
Two greater than symbols [>>].
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

22. What is problem analysis?
Understanding the nature of the problem to be solved.
To 'do it right' to meet its requirements.
A shared body of knowledge.
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

23. What is a software 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
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.
Testing a program or function based on the possible input values - treating the code as a 'black box.'

24. 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 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
A testing technique whereby the tester tries to execute all possible paths in a program or function.

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.
Abstraction
Detecting and fixing errors and demonstrating the correctness of the program.
Actually using the program.
(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 fault tolerance?
The set of valid input data for a program or function.
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.
To 'do everything' specified to meet its 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.

27. What is the unified modeling language (UML)?
The double colon operator (::).
The process of testing the system in its real environment with real data.
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 process of removing known errors.

28. What is program validation?
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 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 process of determining the degree to which software fulfills its intended purpose.

29. 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.
Making changes to fix operational errors and to add or modify the function of the program.
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.

30. What is unit testing?
Testing a module or function by itself.
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 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 functional domain consists of the whole numbers from 0 to 100.

31. 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.
The program meets the demands of time or space in memory.
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.
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

32. What are the goals of quality software?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
The process of determining the degree to which software fulfills its intended purpose.
Testing performed to integrate program modules that have already been independently unit tested.
(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

33. What is clear- box testing?
Reusing objects and processes to implement more complex objects and processes.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Running the program with the test cases listed in the test plan.
Actually using the program.

34. Name some software tools that you have used in developing computer programs.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
The process of testing the system in its real environment with real data.
A cohesive system subunit that performs a share of the work.

35. What does correct mean?

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

36. What is a branch?
To 'do everything' specified to meet its requirements.
A logical proposition that can be true or false.
The set of valid input data for a program or function.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.

37. What is an assertion?
A verification method in which a team performs a manual simulation of the program or design.
A logical proposition that can be true or false.
You can test the software to see if the correct outcome occurs
A cohesive system subunit that performs a share of the work.

38. What does efficient mean?
The program meets the demands of time or space in memory.
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
Determining exactly what the program must do.

39. 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?
Actually using the program.
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 combination of branches that might be traversed when a program or function is executed.
Coding a program in a computer language.

40. What is robustness?
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
Two less than symbols [<<].
A structure of tasks with a main module and subsections.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

41. What is an object?
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
The program meets the demands of time or space in memory.
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 a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

42. What is debugging?
A logical proposition that can be true or false.
Turning over the tested program to the customer or user (or instructor!).
Testing a module or function by itself.
The process of removing known errors.

43. What is a module?
To 'do it right' to meet its requirements.
A cohesive system subunit that performs a share of the work.
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.
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

44. What is statement coverage?
When every statement in the program is executed at least once.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
A property when changes within a module do not result in changes in the modules that use it.
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.

45. What is operation?
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.
Actually using the program.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
(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

46. What is maintenance?
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
Making changes to fix operational errors and to add or modify the function of the program.

47. What is requirements specification?
The process of determining the degree to which a software product fulfills its specifications.
The program's inputs and outputs should be readable and understandable to users.
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).
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.

48. Differentiate between unit testing and integration testing.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
Actually using the program.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
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

49. What is a 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
A special function that can be used in top- down testing to stand in for a lower- level function.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
A shared body of knowledge.

50. What are software requirements?
Testing performed to integrate program modules that have already been independently unit tested.
The process of executing a program with data sets designed to discover errors.
A statement of what is to be provided by a computer system or software product.
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