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 program verification?
The process of determining the degree to which a software product fulfills its specifications.
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 program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
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.'

2. How can you verify the correctness of the software you develop?
You can test the software to see if the correct outcome occurs
A statement of what is to be provided by a computer system or software product.
A shared body of knowledge.
A logical proposition that can be true or false.

3. What is delivery?
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.
To 'do everything' specified to meet its requirements.
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.'
Turning over the tested program to the customer or user (or instructor!).

4. What is a hierarchy of tasks?
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.
A structure of tasks with a main module and subsections.
Turning over the tested program to the customer or user (or instructor!).

5. What is debugging?
The process of removing known errors.
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 functional domain consists of the whole numbers from 0 to 100.
A cohesive system subunit that performs a share of the work.

6. 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 verification method in which a team performs a manual simulation of the program or design.
[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.
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.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.

7. What are software requirements?
A shared body of knowledge.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
The process of testing the system in its real environment with real data.
A statement of what is to be provided by a computer system or software product.

8. What is statement coverage?
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
When every statement in the program is executed at least once.
The process of removing known errors.

9. What is unit testing?
To 'do it right' to meet its requirements.
Testing a module or function by itself.
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 statement of what is to be provided by a computer system or software product.

10. What is round- trip gestalt design?
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 statement of what is to be provided by a computer system or software product.
You can test the software to see if the correct outcome occurs
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

11. What is a branch?
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
Actually using the program.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
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

12. What is a hierarchy of objects?
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 model of a complex system that includes only the details essential to the perspective of the viewer of the system.
A cohesive system subunit that performs a share of the work.
Reusing objects and processes to implement more complex objects and processes.

13. What is program validation?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
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.
The program's inputs and outputs should be readable and understandable to users.

14. What are class - responsibility - and collaboration (CRC) cards?
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.
Testing performed to integrate program modules that have already been independently unit tested.
The process of determining the degree to which a software product fulfills its specifications.

15. 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?
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
When every statement in the program is executed at least once.
The functional domain consists of the whole numbers from 0 to 100.
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.

16. What is a technique used by good problem solvers for dealing with complexity?
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
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
The double colon operator (::).
Abstraction

17. What is stepwise refinement?

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

18. What are the goals of quality software?
Abstraction
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
(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 process of testing the system in its real environment with real data.

19. What is an assertion?
Determining exactly what the program must do.
A statement of what is to be provided by a computer system or software product.
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.

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

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

21. What is the insertion operator?
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.'
Two less than symbols [<<].
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 statement of what is to be provided by a computer system or software product.

22. What is top- down stepwise refinement?
Tracing an execution of a design or program on paper.
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.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
The set of valid input data for a program or function.

23. What does efficient mean?
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.
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.
The program meets the demands of time or space in memory.
A special function that can be used in top- down testing to stand in for a lower- level function.

24. What is requirements elicitation?
Reusing objects and processes to implement more complex objects and processes.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A cohesive system subunit that performs a share of the work.
Determining exactly what the program must do.

25. What is regression testing?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
Two less than symbols [<<].
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Two greater than symbols [>>].

26. What is problem analysis?
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.
Understanding the nature of the problem to be solved.
The process of testing the system in its real environment with real data.

27. 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.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
Actually using the program.
A structure of tasks with a main module and subsections.
The functional domain consists of the whole numbers from 0 to 100.

28. What is metric- based testing?
Testing based on measurable factors.
Making changes to fix operational errors and to add or modify the function of the program.
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.
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.'

29. What is black- box testing?

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

30. What is information hiding?
The double colon operator (::).
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 practice of hiding details of a function or data structure with the goal of controlling access to the details of a module or structure.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.

31. What is a walk- through?
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 verification method in which a team performs a manual simulation of the program or design.
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.
Actually using the program.

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

33. What is testing and verification?
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
Turning over the tested program to the customer or user (or instructor!).
Detecting and fixing errors and demonstrating the correctness of the program.

34. What is an algorithm?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Simple statements like do this - then do this - then do that.
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.

35. What is an object?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Actually using the program.
A property when changes within a module do not result in changes in the modules that use it.

36. What is a path?
The process of executing a program with data sets designed to discover errors.
Actually using the program.
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.

37. What are requirements?
A verification method in which a team performs a manual simulation of the program or design.
Two greater than symbols [>>].
A statement of what is to be provided by a computer system or software product.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

38. What is a test driver?
A cohesive system subunit that performs a share of the work.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
A formal definition of the problem your program must solve.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

39. What is a module?
A formal definition of the problem your program must solve.
Detecting and fixing errors and demonstrating the correctness of the program.
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 cohesive system subunit that performs a share of the work.

40. What is an acceptance test?
The process of testing the system in its real environment with real data.
It is possible to carry out exhaustive data coverage for this program.
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.

41. What is requirements specification?
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).
Making changes to fix operational errors and to add or modify the function of the program.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
Running the program with the test cases listed in the test plan.

42. What is the extraction operator?
Two greater than symbols [>>].
It is possible to carry out exhaustive data coverage for this program.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

43. What is the scope resolution operator?
Turning over the tested program to the customer or user (or instructor!).
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
The double colon operator (::).
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.

44. Name some software tools that you have used in developing computer programs.
Testing a module or function by itself.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
The process of determining the degree to which a software product fulfills its specifications.
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

45. The difference between unit testing and integration testing.
You can test the software to see if the correct outcome occurs
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 greater than symbols [>>].
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

46. What is loose coupling?
A property when changes within a module do not result in changes in the modules that use it.
A verification method in which a team performs a manual simulation of the program or design.
The process of removing known errors.
A logical proposition that can be true or false.

47. What is clear- box testing?
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

48. What is the difference between an object and an object class?
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
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 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.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.

49. What is a test plan?
Reusing objects and processes to implement more complex objects and processes.
Testing based on measurable factors.
Testing performed to integrate program modules that have already been independently unit tested.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.

50. What is an exception?
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
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
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.