Test your basic knowledge |

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 delivery?
Actually using the program.
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.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Turning over the tested program to the customer or user (or instructor!).

2. 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.
The set of valid input data for a program or function.
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
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator

3. The difference between unit testing and integration testing.
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
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
Testing performed to integrate program modules that have already been independently unit tested.
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.

4. What is a hierarchy of objects?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
To 'do everything' specified to meet its requirements.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Reusing objects and processes to implement more complex objects and processes.

5. What is regression testing?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
Two greater than symbols [>>].
The functional domain consists of the whole numbers from 0 to 100.

6. What is the unified modeling language (UML)?
A verification method in which a team performs a manual simulation of the program or design.
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 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 statement of what is to be provided by a computer system or software product.

7. What is a technique used by good problem solvers for dealing with complexity?
You can test the software to see if the correct outcome occurs
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Abstraction

8. What is round- trip gestalt design?
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
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 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.

9. What are class - responsibility - and collaboration (CRC) cards?
Two less than symbols [<<].
It is possible to carry out exhaustive data coverage for this 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
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.

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

11. What is stepwise refinement?

12. What is an acceptance test?
A verification method in which a team performs a manual simulation of the program or 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
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.

13. What are functional subproblems?
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.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
Simple statements like do this - then do this - then do that.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.

14. What is white- box testing?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
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 everything' specified to meet its requirements.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

15. What is implementation of the design?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Coding a program in a computer language.
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.

16. 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.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
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
Reusing objects and processes to implement more complex objects and processes.

17. What is a test plan?
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
A logical proposition that can be true or false.
A statement of what is to be provided by a computer system or software product.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.

18. What is a software specification?
Running the program with the test cases listed in the test plan.
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).
Reusing objects and processes to implement more complex objects and processes.
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.

19. What is abstraction?
A statement of what is to be provided by a computer system or software product.
The double colon operator (::).
Testing a module or function by itself.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.

20. What is testing?
Two greater than symbols [>>].
The process of executing a program with data sets designed to discover errors.
The process of testing the system in its real environment with real data.
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.

21. What is operation?
Reusing objects and processes to implement more complex objects and processes.
A property when changes within a module do not result in changes in the modules that use it.
Actually using the program.
The functional domain consists of the whole numbers from 0 to 100.

22. What is information hiding?
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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.
Unit testing is the testing of a single unit of the program (for instance - a function). Integration testing is the testing of groups of already tested units to make sure that they interact correctly and that the whole program works according to its
The practice of hiding details of a function or data structure with the goal of controlling access to the details of a module or structure.

23. What is an assertion?
Testing a program or function based on the possible input values - treating the code as a 'black box.'
A logical proposition that can be true or false.
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 set of valid input data for a program or function.

24. Differentiate between unit testing and integration testing.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Actually using the program.
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 program's inputs and outputs should be readable and understandable to users.

25. 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.
Tracing an execution of a design or program on paper.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
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 verification method in which one member of a team reads the program or design line by line and the other members point out errors.

26. What is requirements elicitation?
Determining exactly what the program must do.
Testing a module or function by itself.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
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.'

27. What is loose coupling?
To 'do it right' to meet its requirements.
The program's inputs and outputs should be readable and understandable to users.
A combination of branches that might be traversed when a program or function is executed.
A property when changes within a module do not result in changes in the modules that use it.

28. What are preconditions?
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.
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 document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.

29. What is testing and verification?
Detecting and fixing errors and demonstrating the correctness of the program.
The process of determining the degree to which software fulfills its intended purpose.
Coding a program in a computer language.
[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 the insertion operator?
Two less than symbols [<<].
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.
Two greater than symbols [>>].
Determining exactly what the program must do.

31. 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.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
The process of determining the degree to which software fulfills its intended purpose.
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.

32. What is requirements specification?
[Input] All values from 1 to 100. [Expected Output] For input 0-59 => F. For input 60-69 => D. For input 70-79 => C. For input 80-89 => B. For input 90-100 => A.
Testing performed to integrate program modules that have already been independently unit 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).
Two less than symbols [<<].

33. What is information hiding and why is it considered a good software development practice.
The practice of only showing the information necessary for a user level and hiding the rest of the information. this makes programming in teams easier because you can see the big picture easier. Also - the programmer does not have to worry if the imp
The 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.
To 'do it right' 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.

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

35. What is the functional domain?
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 set of valid input data for a program or function.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
You can test the software to see if the correct outcome occurs

36. What is a branch?
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.
It is possible to carry out exhaustive data coverage for this program.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.

37. What is unit testing?
Reusing objects and processes to implement more complex objects and processes.
The program meets the demands of time or space in memory.
Testing a module or function by itself.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.

38. What is path testing?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
The double colon operator (::).
Testing a program or function based on the possible input values - treating the code as a 'black box.'
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.

39. How can you verify the correctness of the software you develop?
A shared body of knowledge.
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.
You can test the software to see if the correct outcome occurs
The process of removing known errors.

40. What is inspection?
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 testing the system in its real environment with real data.
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.
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

41. What is functional decomposition?
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 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.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.

42. What is implementing a test plan?
Running the program with the test cases listed in the test plan.
You can test the software to see if the correct outcome occurs
The process of determining the degree to which software fulfills its intended purpose.
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 the relationship between the cost of error correction in software development and where/when errors are detected in terms of the software life cycle?
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.
Detecting and fixing errors and demonstrating the correctness of the program.
The program meets the demands of time or space in memory.
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

44. What is a detailed specification?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
It is possible to carry out exhaustive data coverage for this program.
A formal definition of the problem your program must solve.
To 'do it right' to meet its requirements.

45. What is the difference between an object and an object class?
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.
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.
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 ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

46. What is a class?
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.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
To 'do it right' to meet its requirements.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

47. What is metric- based testing?
Testing based on measurable factors.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
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.
Two less than symbols [<<].

48. What is a hierarchy of tasks?
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A structure of tasks with a main module and subsections.
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.

49. What is the extraction operator?
A statement of what is to be provided by a computer system or software product.
A logical proposition that can be true or false.
Two greater than symbols [>>].
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.

50. What is a path?
A cohesive system subunit that performs a share of the work.
A combination of branches that might be traversed when a program or function is executed.
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 a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.