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 operation?
Actually using the program.
A verification method in which a team performs a manual simulation of the program or design.
Testing a module or function by itself.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.


2. What is metric- based testing?
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.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
This program design approach encourages programming in logical action units - called functions. The main module of the design becomes the main program (also called the main function) - and subsections develop into functions. This is top- down stepwis
Testing based on measurable factors.


3. What is a stub?
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 verification method in which one member of a team reads the program or design line by line and the other members point out errors.
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.


4. What does efficient mean?
Reusing objects and processes to implement more complex objects and processes.
The program meets the demands of time or space in memory.
Understanding the nature of the problem to be solved.
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.


5. What is a hierarchy of objects?
Reusing objects and processes to implement more complex objects and processes.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
To 'do it right' to meet its requirements.
The program meets the demands of time or space in memory.


6. What are functional subproblems?
Simple statements like do this - then do this - then do that.
Understanding the nature of the problem to be solved.
Testing based on measurable factors.
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


7. What is an assertion?
You can test the software to see if the correct outcome occurs
A logical proposition that can be true or false.
Running the program with the test cases listed in the test plan.
A formal definition of the problem your program must solve.


8. What does correct mean?

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


9. 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 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.
Tracing an execution of a design or program on paper.
Turning over the tested program to the customer or user (or instructor!).


10. What is black- box testing?

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


11. What is robustness?
Detecting and fixing errors and demonstrating the correctness of the program.
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 ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Understanding the nature of the problem to be solved.


12. What is path testing?
This is the idea that program verification activities can be performed throughout the program's life cycle - not just by testing the program after it is coded.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
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 set of valid input data for a program or function.


13. What is information hiding and why is it considered a good software development practice.
Testing a module or function by itself.
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 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
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.


14. What are postconditions?
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.
Tracing an execution of a design or program on paper.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.


15. What are the goals of quality software?
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.
(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
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.


16. What are requirements?
The discipline devoted to the design - production - and maintenance of computer programs that are developed on time and within cost estimates - using tools that help to manage the size and complexity of the resulting software products.
When you create your code - you break the problem into units called modules. Unit testing tests each individual module by itself. Later - you combine the working units together. Integration testing tests the group of units to see if they work togethe
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.


17. Differentiate between unit testing and integration testing.
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.
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 ability of a program to recover following an error; the ability of a program to continue to operate within its environment.


18. What is deskchecking?
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.
A property when changes within a module do not result in changes in the modules that use it.
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
Tracing an execution of a design or program on paper.


19. What is an exception?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
A 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 testing technique whereby the tester tries to execute all possible paths in a program or function.
The program's inputs and outputs should be readable and understandable to users.


20. What is a module?
A formal definition of the problem your program must solve.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Actually using the program.
A cohesive system subunit that performs a share of the work.


21. What is program validation?
The process of determining the degree to which software fulfills its intended purpose.
To 'do it right' to meet its requirements.
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
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.


22. What is software engineering?
A formal definition of the problem your program must solve.
You can test the software to see if the correct outcome occurs
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 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.


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


24. Explain what we mean by 'ideaware'.
A shared body of knowledge.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
To 'do everything' specified to meet its requirements.
Abstraction


25. What does usable mean?

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


26. What is delivery?
Turning over the tested program to the customer or user (or instructor!).
Two less than symbols [<<].
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
To 'do it right' to meet its requirements.


27. What is requirements elicitation?
Making changes to fix operational errors and to add or modify the function of the program.
Determining exactly what the program must do.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
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.


28. 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.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Tracing an execution of a design or program on paper.


29. What are class - responsibility - and collaboration (CRC) cards?
Running the program with the test cases listed in the test plan.
A statement of what is to be provided by a computer system or software product.
Detecting and fixing errors and demonstrating the correctness 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


30. What is maintenance?
The functional domain consists of the whole numbers from 0 to 100.
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 testing technique whereby the tester tries to execute all possible paths in a program or function.
Making changes to fix operational errors and to add or modify the function of the program.


31. What is implementing a test plan?
A statement of what is to be provided by a computer system or software product.
Making changes to fix operational errors and to add or modify the function of 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.
Running the program with the test cases listed in the test plan.


32. A program is to read in a numeric score (0 to 100) and display an appropriate letter grade (A - B - C - D - or F). What is the functional domain of this program?
The functional domain consists of the whole numbers from 0 to 100.
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.
Tracing an execution of a design or program on paper.
A formal definition of the problem your program must solve.


33. What is the insertion operator?
Two less than symbols [<<].
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
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.


34. What is program verification?
The process of determining the degree to which a software product fulfills its specifications.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
When every statement in the program is executed at least once.


35. 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).
Simple statements like do this - then do this - then do that.
The process of determining the degree to which software fulfills its intended purpose.
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.


36. What is abstraction?
A combination of branches that might be traversed when a program or function is executed.
When every statement in the program is executed at least once.
Testing based on measurable factors.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.


37. What does complete mean?

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


38. What is clear- box 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
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.
A shared body of knowledge.


39. What is bottom- up stepwise refinement?
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.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
It is possible to carry out exhaustive data coverage for this program.


40. What is a detailed specification?
A formal definition of the problem your program must solve.
Understanding the nature of the problem to be solved.
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 combination of branches that might be traversed when a program or function is executed.


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

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


42. What is inspection?
A property when changes within a module do not result in changes in the modules that use it.
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.
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 removing known errors.


43. The difference between unit testing and integration testing.
Reusing objects and processes to implement more complex objects and processes.
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.'
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 logical proposition that can be true or false.


44. What is a hierarchy of tasks?
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 functional domain consists of the whole numbers from 0 to 100.
A structure of tasks with a main module and subsections.
When every statement in the program is executed at least once.


45. What is testing and verification?
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Simple statements like do this - then do this - then do that.
Coding a program in a computer language.
Detecting and fixing errors and demonstrating the correctness of the program.


46. What is a test driver?
Tracing an execution of a design or program on paper.
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 approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.


47. What is integration testing?
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 shared body of knowledge.
Two greater than symbols [>>].


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


49. 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.
The process of testing the system in its real environment with real data.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed 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.
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


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