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 a detailed specification?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
[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 formal definition of the problem your program must solve.
Abstraction


2. What is a class?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
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
It is possible to carry out exhaustive data coverage for this program.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.


3. What is maintenance?
Two greater than symbols [>>].
Making changes to fix operational errors and to add or modify the function of the program.
Testing a module or function by itself.
The process of removing known errors.


4. What is a stub?
The process of determining the degree to which a software product fulfills its specifications.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
A special function that can be used in top- down testing to stand in for a lower- level function.
A statement of what is to be provided by a computer system or software product.


5. What does efficient mean?
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
Reusing objects and processes to implement more complex objects and processes.
Two greater than symbols [>>].
The program meets the demands of time or space in memory.


6. 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.
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
Determining exactly what the program must do.
A verification method in which a team performs a manual simulation of the program or design.


7. What does usable mean?

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


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 insertion operator?
Reusing objects and processes to implement more complex objects and processes.
[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 [<<].
A shared body of knowledge.


10. What is an exception?
The process of removing known errors.
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 a team performs a manual simulation of the program or design.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.


11. What is regression testing?
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.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.


12. 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
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 process of determining the degree to which software fulfills its intended purpose.
[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.


13. How can you verify the correctness of the software you develop?
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Determining exactly what the program must do.
You can test the software to see if the correct outcome occurs


14. What is statement coverage?
The process of determining the degree to which software fulfills its intended purpose.
When every statement in the program is executed at least once.
Simple statements like do this - then do this - then do that.
A statement of what is to be provided by a computer system or software product.


15. What is black- box testing?

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


16. What are class - responsibility - and collaboration (CRC) cards?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
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.
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


17. What is requirements specification?
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
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.
A statement of what is to be provided by a computer system or software product.


18. 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.
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.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
The double colon operator (::).


19. What is integration testing?
A formal definition of the problem your program must solve.
Testing performed to integrate program modules that have already been independently unit tested.
Making changes to fix operational errors and to add or modify the function of the program.
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.'


20. What is implementation of the design?
A property when changes within a module do not result in changes in the modules that use it.
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
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Coding a program in a computer language.


21. What is fault tolerance?
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.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
Determining exactly what the program must do.
Actually using the program.


22. What is a software specification?
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 program meets the demands of time or space in memory.
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.


23. What are postconditions?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
Reusing objects and processes to implement more complex objects and processes.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.


24. 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?
Reusing objects and processes to implement more complex objects and processes.
It is possible to carry out exhaustive data coverage for this program.
Coding a program in a computer language.
The functional domain consists of the whole numbers from 0 to 100.


25. What is inspection?
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 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 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
Testing performed to integrate program modules that have already been independently unit tested.


26. What is the functional domain?
A shared body of knowledge.
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.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.


27. What is robustness?
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.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.


28. What are functional subproblems?
Simple statements like do this - then do this - then do that.
A combination of branches that might be traversed when a program or function is executed.
A structure of tasks with a main module and subsections.
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.


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). Devise a test plan for this program.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
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.
[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.


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


31. What is deskchecking?
Tracing an execution of a design or program on paper.
A structure of tasks with a main module and subsections.
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.


32. What is a path?
A combination of branches that might be traversed when a program or function is executed.
Two greater than symbols [>>].
Testing based on measurable factors.
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.


33. What is bottom- up stepwise refinement?
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 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 logical proposition that can be true or false.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.


34. What are software requirements?
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.
The process of removing known errors.
A statement of what is to be provided by a computer system or software product.


35. What is round- trip gestalt design?
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
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
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.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.


36. What are the goals of quality software?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
(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
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
Two less than symbols [<<].


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 requirements elicitation?
Testing a module or function by itself.
You can test the software to see if the correct outcome occurs
Determining exactly what the program must do.
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.


39. What is the unified modeling language (UML)?
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
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.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
The process of determining the degree to which software fulfills its intended purpose.


40. What is top- down stepwise refinement?
The process of determining the degree to which software fulfills its intended purpose.
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.
Turning over the tested program to the customer or user (or instructor!).
You can test the software to see if the correct outcome occurs


41. What is information hiding?
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 'do it right' to meet its requirements.
Testing a module or function by itself.
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


42. What is a hierarchy of objects?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
Reusing objects and processes to implement more complex objects and processes.
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


43. What is program validation?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
The functional domain consists of the whole numbers from 0 to 100.
The process of determining the degree to which software fulfills its intended purpose.
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.


44. What is functional decomposition?
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
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 code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.


45. What is a test driver?
To 'do it right' to meet its requirements.
(1) It works (2) It can be modified without excessive time and effort (3) It is reusable (4) It is completed on time and within budget
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
When every statement in the program is executed at least once.


46. What is an acceptance test?
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
Also called a class. 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.
The process of testing the system in its real environment with real data.


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


48. What are requirements?
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 special function that can be used in top- down testing to stand in for a lower- level function.
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 delivery?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
Testing performed to integrate program modules that have already been independently unit tested.
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.


50. Name some software tools that you have used in developing computer programs.
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.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)