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?
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Detecting and fixing errors and demonstrating the correctness of the program.
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.


2. 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.
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 double colon operator (::).


3. What is a test plan?
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
Testing a program or function based on the possible input values - treating the code as a 'black box.'
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.


4. What are class - responsibility - and collaboration (CRC) cards?
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
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 practice of hiding details of a function or data structure with the goal of controlling access to the details of a module or structure.
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


5. What is software engineering?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
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.
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.


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


7. What is implementation of the 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.
Coding a program in a computer language.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Two less than symbols [<<].


8. What are postconditions?
Testing a program or function based on the possible input values - treating the code as a 'black box.'
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 clear- 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.


9. What is a detailed specification?
A formal definition of the problem your program must solve.
A special function that can be used in top- down testing to stand in for a lower- level function.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
(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


10. Explain what we mean by 'ideaware'.
A structure of tasks with a main module and subsections.
The double colon operator (::).
A shared body of knowledge.
Reusing objects and processes to implement more complex objects and processes.


11. What is an exception?
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 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
Making changes to fix operational errors and to add or modify the function of the program.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.


12. What is bottom- up stepwise refinement?
Actually using the 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.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
Coding a program in a computer language.


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 the functional domain?
The set of valid input data for a program or function.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.


15. What is a technique used by good problem solvers for dealing with complexity?
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
The process of executing a program with data sets designed to discover errors.
A combination of branches that might be traversed when a program or function is executed.
Abstraction


16. What is a test driver?
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
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.
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.


17. 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.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
The process of testing the system in its real environment with real data.
A shared body of knowledge.


18. What is a class?
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A statement of what is to be provided by a computer system or software product.
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 practice of hiding details of a function or data structure with the goal of controlling access to the details of a module or structure.


19. What is information hiding?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
The practice of 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.
Abstraction


20. What is implementing a test plan?
The process of executing a program with data sets designed to discover errors.
Running the program with the test cases listed in the test plan.
The functional domain consists of the whole numbers from 0 to 100.
Reusing objects and processes to implement more complex objects and processes.


21. What is the insertion operator?
The process of removing known errors.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
A property when changes within a module do not result in changes in the modules that use it.
Two less than symbols [<<].


22. 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.
To 'do it right' to meet its requirements.
A formal definition of the problem your program must solve.


23. What is abstraction?
(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
Tracing an execution of a design or program on paper.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
The double colon operator (::).


24. What is inspection?
Testing performed to integrate program modules that have already been independently unit tested.
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
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.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.


25. What is debugging?
The process of removing known errors.
Making changes to fix operational errors and to add or modify the function of the program.
To 'do it right' to meet its requirements.
Detecting and fixing errors and demonstrating the correctness of the program.


26. What is stepwise refinement?

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


27. What is fault tolerance?
Running the program with the test cases listed in the test plan.
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.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
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


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

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


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?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Two less than symbols [<<].
It is possible to carry out exhaustive data coverage for this program.
(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


30. What is deskchecking?
Determining exactly what the program must do.
Tracing an execution of a design or program on paper.
The double colon operator (::).
Coding a program in a computer language.


31. What is a branch?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
Tracing an execution of a design or program on paper.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.


32. What is requirements elicitation?
Determining exactly what the program must do.
Making changes to fix operational errors and to add or modify the function of the program.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
A cohesive system subunit that performs a share of the work.


33. What are preconditions?
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.
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
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.


34. What is a stub?
A logical proposition that can be true or false.
A special function that can be used in top- down testing to stand in for a lower- level function.
Two less than symbols [<<].
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.


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 an object?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Actually using the program.
A shared body of knowledge.
A special function that can be used in top- down testing to stand in for a lower- level function.


37. What is program verification?
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
Simple statements like do this - then do this - then do that.
The process of determining the degree to which a software product fulfills its specifications.
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.


38. What does usable mean?

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


39. What is integration testing?
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.
Testing performed to integrate program modules that have already been independently unit tested.
Research has shown that the sooner you detect an error - the lest costly it will be to fix it. catching an error near the end of the software life cycle can be 100 times more costly that catching it at the beginning.
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.


40. What is the extraction operator?
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
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 greater than symbols [>>].
A property when changes within a module do not result in changes in the modules that use it.


41. What is statement coverage?
Determining exactly what the program must do.
A cohesive system subunit that performs a share of the work.
When every statement in the program is executed at least once.
The process of testing the system in its real environment with real data.


42. What is testing and verification?
You can test the software to see if the correct outcome occurs
Two less than symbols [<<].
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.


43. What is functional decomposition?
[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.
Two less than symbols [<<].
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
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.


44. What is a walk- through?
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
A structure of tasks with a main module and subsections.
Determining exactly what the program must do.
A verification method in which a team performs a manual simulation of the program or design.


45. What is operation?
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
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A structure of tasks with a main module and subsections.


46. What is a hierarchy of tasks?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
A shared body of knowledge.
When every statement in the program is executed at least once.
A structure of tasks with a main module and subsections.


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). Devise a test plan for this program.
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).
[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.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.


48. What are software requirements?
Testing a program or function based on the possible input values - treating the code as a 'black box.'
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
A statement of what is to be provided by a computer system or software product.
To 'do everything' specified to meet its requirements.


49. What are functional subproblems?
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.
Simple statements like do this - then do this - then do that.
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.


50. What is maintenance?
Simple statements like do this - then do this - then do that.
Making changes to fix operational errors and to add or modify the function of the program.
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
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).