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 requirements elicitation?
The functional domain consists of the whole numbers from 0 to 100.
Actually using the program.
Determining exactly what the program must do.
To 'do it right' to meet its requirements.


2. What is a software specification?
Running the program with the test cases listed in the test plan.
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.
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 process of determining the degree to which a software product fulfills its specifications.


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


4. What is a test plan?
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 document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
Reusing objects and processes to implement more complex objects and processes.
Turning over the tested program to the customer or user (or instructor!).


5. What is an acceptance test?
(1) It works (2) It can be modified without excessive time and effort (3) It is reusable (4) It is completed on time and within budget
The process of testing the system in its real environment with real data.
The process of removing known errors.
When every statement in the program is executed at least once.


6. What is information hiding and why is it considered a good software development practice.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
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
Making changes to fix operational errors and to add or modify the function of the program.


7. What is clear- box testing?
To 'do everything' specified to meet its requirements.
A statement of what is to be provided by a computer system or software product.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
The functional domain consists of the whole numbers from 0 to 100.


8. What is the insertion operator?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Two less than symbols [<<].
A statement of what is to be provided by a computer system or software product.
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


9. What is the software process?
Also called clear- 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.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
A logical proposition that can be true or false.


10. What is round- trip gestalt design?
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.
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
It is possible to carry out exhaustive data coverage for this 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.


11. What is a hierarchy of tasks?
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.'
A formal definition of the problem your program must solve.
A structure of tasks with a main module and subsections.
Testing a program or function based on the possible input values - treating the code as a 'black box.'


12. What is debugging?
The process of removing known errors.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
Simple statements like do this - then do this - then do that.
Tracing an execution of a design or program on paper.


13. What is metric- based testing?
Testing based on measurable factors.
A formal definition of the problem your program must solve.
The functional domain consists of the whole numbers from 0 to 100.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.


14. 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
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
Determining exactly what the program must do.


15. A program is to read in a numeric score (0 to 100) and display an appropriate letter grade (A - B - C - D - or F). Devise a test plan for this program.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
[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.
Reusing objects and processes to implement more complex objects and processes.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.


16. What is the unified modeling language (UML)?
To 'do it right' to meet its requirements.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
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 standard - integrated set of software engineering tools and techniques used on a project by an organization.


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


18. What is maintenance?
The functional domain consists of the whole numbers from 0 to 100.
Understanding the nature of the problem to be solved.
Making changes to fix operational errors and to add or modify the function of the program.
The program meets the demands of time or space in memory.


19. What is a class?
Determining exactly what the program must do.
The double colon operator (::).
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.


20. What is fault tolerance?
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
A verification method in which a team performs a manual simulation of the program or design.
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.


21. What are functional subproblems?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
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).
Tracing an execution of a design or program on paper.
Simple statements like do this - then do this - then do that.


22. What is program validation?
Testing a program or function based on the possible input values - treating the code as a 'black box.'
(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
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
The process of determining the degree to which software fulfills its intended purpose.


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

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


24. What is information hiding?
A verification method in which a team performs a manual simulation of the program or design.
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 program meets the demands of time or space in memory.
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.


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


26. What is robustness?
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
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.
Two less than symbols [<<].
The set of valid input data for a program or function.


27. How can you verify the correctness of the software you develop?
A structure of tasks with a main module and subsections.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
You can test the software to see if the correct outcome occurs
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.


28. Name some software tools that you have used in developing computer programs.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
The double colon operator (::).
Reusing objects and processes to implement more complex objects and processes.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)


29. What are requirements?
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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.
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.


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


31. 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
A testing technique whereby the tester tries to execute all possible paths in a program or function.
A property when changes within a module do not result in changes in the modules that use it.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator


32. What is a detailed specification?
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
To 'do everything' specified to meet its requirements.
Turning over the tested program to the customer or user (or instructor!).
A formal definition of the problem your program must solve.


33. What is the difference between an object and an object class?
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.
It is possible to carry out exhaustive data coverage for this program.
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 program's inputs and outputs should be readable and understandable to users.


34. What does complete mean?

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


35. What are software requirements?
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
Determining exactly what the program must do.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
A statement of what is to be provided by a computer system or software product.


36. What does correct mean?

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


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


38. What does efficient mean?
Tracing an execution of a design or program on paper.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
Understanding the nature of the problem to be solved.
The program meets the demands of time or space in memory.


39. What is a module?
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 cohesive system subunit that performs a share of the work.
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.


40. What is delivery?
Turning over the tested program to the customer or user (or instructor!).
The process of testing the system in its real environment with real data.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
To 'do everything' specified to meet its requirements.


41. What is deskchecking?
Tracing an execution of a design or program on paper.
Determining exactly what the program must do.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
The process of executing a program with data sets designed to discover errors.


42. What is an algorithm?
A structure of tasks with a main module and subsections.
The double colon operator (::).
Running the program with the test cases listed in the test plan.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.


43. What is testing?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
You can test the software to see if the correct outcome occurs
The process of executing a program with data sets designed to discover errors.


44. What is a walk- through?
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!).
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 testing the system in its real environment with real data.


45. What is statement coverage?
The process of determining the degree to which a software product fulfills its specifications.
When every statement in the program is executed at least once.
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 structure of tasks with a main module and subsections.


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


47. What is path testing?
Coding a program in a computer language.
A verification method in which a team performs a manual simulation of the program or design.
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.


48. What is implementation of the design?
Coding a program in a computer language.
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).
Detecting and fixing errors and demonstrating the correctness of the program.
The process of removing known errors.


49. What is software engineering?
Making changes to fix operational errors and to add or modify the function of the program.
A formal definition of the problem your program must solve.
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.
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.


50. 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.
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.
A structure of tasks with a main module and subsections.