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. Give a specific C++ language attribute that supports information hiding.

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


2. What is clear- box testing?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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
When every statement in the program is executed at least once.
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.


3. Explain what we mean by 'ideaware'.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
Tracing an execution of a design or program on paper.
A property when changes within a module do not result in changes in the modules that use it.
A shared body of knowledge.


4. What is a module?
The program's inputs and outputs should be readable and understandable to users.
A special function that can be used in top- down testing to stand in for a lower- level 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.
A cohesive system subunit that performs a share of the work.


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

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


6. What is program verification?
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 robustness. The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
The process of determining the degree to which a software product fulfills its specifications.


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


8. What is maintenance?
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A verification method in which a team performs a manual simulation of the program or design.
Making changes to fix operational errors and to add or modify the function of the program.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.


9. What is a hierarchy of tasks?
A structure of tasks with a main module and subsections.
A verification method in which a team performs a manual simulation of the program or design.
Turning over the tested program to the customer or user (or instructor!).
Making changes to fix operational errors and to add or modify the function of the program.


10. What is loose coupling?
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 property when changes within a module do not result in changes in the modules that use it.
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.


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 problem analysis?
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.
Understanding the nature of the problem to be solved.
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


13. 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.
A statement of what is to be provided by a computer system or software product.
The process of determining the degree to which a software product fulfills its specifications.
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.


14. What is a detailed specification?
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 special function that can be used in top- down testing to stand in for a lower- level function.
A formal definition of the problem your program must solve.
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.


15. What is inspection?
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
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.
It is possible to carry out exhaustive data coverage for this program.


16. What is program validation?
The process of determining the degree to which software fulfills its intended purpose.
Two less than symbols [<<].
The program's inputs and outputs should be readable and understandable to users.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.


17. What is an exception?
Tracing an execution of a design or program on paper.
The process of testing the system in its real environment with real data.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
A testing technique whereby the tester tries to execute all possible paths in a program or function.


18. What are postconditions?
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.
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 one member of a team reads the program or design line by line and the other members point out errors.


19. What is an acceptance test?
The set of valid input data for a program or function.
The program's inputs and outputs should be readable and understandable to users.
The process of testing the system in its real environment with real data.
Two less than symbols [<<].


20. What is path 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.
To 'do it right' to meet its requirements.
Used to specify - visualize - construct - and document the components of a software system. This is particularly well suited for modeling object- oriented designs. The diagrams represent another form of abstraction.
A testing technique whereby the tester tries to execute all possible paths in a program or function.


21. What is a walk- through?
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 verification method in which a team performs a manual simulation of the program or design.
A structure of tasks with a main module and subsections.
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.


22. What is a path?
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.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A combination of branches that might be traversed when a program or function is executed.


23. Differentiate between unit testing and integration testing.
A statement of what is to be provided by a computer system or software product.
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 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 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


24. What is metric- based testing?
The process of executing a program with data sets designed to discover errors.
A cohesive system subunit that performs a share of the work.
When every statement in the program is executed at least once.
Testing based on measurable factors.


25. 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


26. What is implementation of the design?
A cohesive system subunit that performs a share of the work.
A logical proposition that can be true or false.
Coding a program in a computer language.
The functional domain consists of the whole numbers from 0 to 100.


27. The difference between unit testing and integration testing.
A special function that can be used in top- down testing to stand in for a lower- level function.
Tracing an execution of a design or program on paper.
The program's inputs and outputs should be readable and understandable to users.
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


28. What is a hierarchy of objects?
Reusing objects and processes to implement more complex objects and processes.
Making changes to fix operational errors and to add or modify the function 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 program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.


29. What is information hiding?
Testing performed to integrate program modules that have already been independently unit tested.
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 process of executing a program with data sets designed to discover errors.
Reusing objects and processes to implement more complex objects and processes.


30. What is requirements elicitation?
Determining exactly what the program must do.
Actually using the program.
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 executing a program with data sets designed to discover errors.


31. What is debugging?
(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 removing known errors.
Reusing objects and processes to implement more complex objects and processes.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.


32. What is unit testing?
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).
Testing a module or function by itself.
Detecting and fixing errors and demonstrating the correctness of the program.
The process of testing the system in its real environment with real data.


33. What is information hiding and why is it considered a good software development practice.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
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 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 statement of what is to be provided by a computer system or software product.


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


35. What is a class?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
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 an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.


36. What is integration testing?
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Testing performed to integrate program modules that have already been independently unit tested.
The practice of only showing the information necessary for a user level and hiding the rest of the information. this makes programming in teams easier because you can see the big picture easier. Also - the programmer does not have to worry if the imp
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.


37. What is the functional domain?
The set of valid input data for a program or function.
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.
To 'do everything' specified to meet its requirements.
This is the idea that program verification activities can be performed throughout the program's life cycle - not just by testing the program after it is coded.


38. What is operation?
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
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.
A testing technique whereby the tester tries to execute all possible paths in a program or function.


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?
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 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 program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be 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.


40. What are requirements?
A statement of what is to be provided by a computer system or software product.
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.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
The set of valid input data for a program or function.


41. What is top- down stepwise refinement?
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.
An object is an individual while a class is a description of a group of objects with similar properties and behaviors. Labrador dogs is an example of a class and Maggie is an example of an object.
The program's inputs and outputs should be readable and understandable to users.
A special function that can be used in top- down testing to stand in for a lower- level function.


42. How can you verify the correctness of the software you develop?
You can test the software to see if the correct outcome occurs
Actually using the program.
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.


43. What is functional decomposition?
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 executing a program with data sets designed to discover errors.
Simple statements like do this - then do this - then do that.
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


44. What does usable mean?

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


45. What are the goals of quality software?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
(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
Turning over the tested program to the customer or user (or instructor!).


46. What is software engineering?
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 structure of tasks with a main module and subsections.
The program's inputs and outputs should be readable and understandable to users.
A shared body of knowledge.


47. What does efficient mean?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
The program meets the demands of time or space in memory.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.


48. What is statement coverage?
The program's inputs and outputs should be readable and understandable to users.
Also called an object. 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.
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.'


49. What is the scope resolution operator?
Testing performed to integrate program modules that have already been independently unit tested.
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.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
The double colon operator (::).


50. What is implementing a test plan?
(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 ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
Running the program with the test cases listed in the test plan.