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 the functional domain?
The set of valid input data for a program or function.
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 functional domain consists of the whole numbers from 0 to 100.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.

2. What is operation?
Actually using the program.
A combination of branches that might be traversed when a program or function is executed.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
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.

3. What are postconditions?
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
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

4. What are software requirements?
A statement of what is to be provided by a computer system or software product.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
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

5. What is loose coupling?
A property when changes within a module do not result in changes in the modules that use it.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
The functional domain consists of the whole numbers from 0 to 100.

6. What is path testing?
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 program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
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.

7. Name some software tools that you have used in developing computer programs.
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.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
Turning over the tested program to the customer or user (or instructor!).
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.

8. What is a test plan?
A statement of what is to be provided by a computer system or software product.
Determining exactly what the program must do.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
It is possible to carry out exhaustive data coverage for this program.

9. What are the goals of quality software?
A structure of tasks with a main module and subsections.
(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
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 ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

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

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

12. What is the extraction operator?
Two greater than symbols [>>].
Abstraction
A cohesive system subunit that performs a share of the work.
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.

13. What is round- trip gestalt design?
Testing a module or function by itself.
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 set of valid input data for a program or function.
Testing a program or function based on the possible input values - treating the code as a 'black box.'

14. What is a path?
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
A combination of branches that might be traversed when a program or function is executed.
Testing based on measurable factors.
Two less than symbols [<<].

15. What is a detailed specification?
The process of removing known errors.
A special function that can be used in top- down testing to stand in for a lower- level function.
A formal definition of the problem your program must solve.
Running the program with the test cases listed in the test plan.

16. What is statement coverage?
When every statement in the program is executed at least once.
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
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 hiding details of a function or data structure with the goal of controlling access to the details of a module or structure.

17. What is requirements 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.
Turning over the tested program to the customer or user (or instructor!).
Testing a program or function based on the possible input values - treating the code as a 'black box.'
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).

18. 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.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A logical proposition that can be true or false.
To 'do everything' specified to meet its requirements.

19. What is the unified modeling language (UML)?
Coding a program in a computer language.
Abstraction
To 'do everything' specified to meet its requirements.
Used to specify - visualize - construct - and document the components of a software system. This is particularly well suited for modeling object- oriented designs. The diagrams represent another form of abstraction.

20. The difference between unit testing and integration 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 process of removing known errors.
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

21. 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.
Tracing an execution of a design or program on paper.
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.

22. What is a module?
A cohesive system subunit that performs a share of the work.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
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.

23. What is an algorithm?
A special function that can be used in top- down testing to stand in for a lower- level function.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

24. What is problem analysis?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
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
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.

25. What does correct mean?

26. What does efficient mean?
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 cohesive system subunit that performs a share of the work.
The program meets the demands of time or space in memory.
A combination of branches that might be traversed when a program or function is executed.

27. What is delivery?
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.
Turning over the tested program to the customer or user (or instructor!).
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
A cohesive system subunit that performs a share of the work.

28. What is a hierarchy of tasks?
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 property when changes within a module do not result in changes in the modules that use it.
A structure of tasks with a main module and subsections.
A combination of branches that might be traversed when a program or function is executed.

29. What is top- down stepwise refinement?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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 standard - integrated set of software engineering tools and techniques used on a project by an organization.
To 'do everything' specified to meet its requirements.

30. Explain what we mean by 'ideaware'.
A verification method in which a team performs a manual simulation of the program or design.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A shared body of knowledge.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

31. What is robustness?
Two less than symbols [<<].
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
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

32. What is requirements elicitation?
Determining exactly what the program must do.
A shared body of knowledge.
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 set of valid input data for a program or function.

33. What are preconditions?
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.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

34. What are functional subproblems?
Simple statements like do this - then do this - then do that.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Tracing an execution of a design or program on paper.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.

35. What is integration testing?
The process of executing a program with data sets designed to discover errors.
Running the program with the test cases listed in the test plan.
Testing performed to integrate program modules that have already been independently unit tested.
Detecting and fixing errors and demonstrating the correctness of the program.

36. What is clear- box testing?
To 'do everything' specified to meet its requirements.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
A statement of what is to be provided by a computer system or software product.
It is possible to carry out exhaustive data coverage for this program.

37. What is an object?
Testing based on measurable factors.
A cohesive system subunit that performs a share of the work.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator

38. What is program validation?
The process of determining the degree to which software fulfills its intended purpose.
A combination of branches that might be traversed when a program or function is executed.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.

39. 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
The program's inputs and outputs should be readable and understandable to users.
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
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.

40. 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.
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.
When every statement in the program is executed at least once.

41. What is stepwise refinement?

42. What is debugging?
You can test the software to see if the correct outcome occurs
Actually using the 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 process of removing known errors.

43. A program is to read in a numeric score (0 to 100) and display an appropriate letter grade (A - B - C - D - or F). Is exhaustive data coverage possible for this program?
It is possible to carry out exhaustive data coverage for this program.
Testing a module or function by itself.
The set of valid input data for a program or function.
The functional domain consists of the whole numbers from 0 to 100.

44. What is fault tolerance?
Testing a module or function by itself.
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Also called robustness. The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Two less than symbols [<<].

45. What is bottom- up stepwise refinement?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
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 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.

46. 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 practice of hiding details of a function or data structure with the goal of controlling access to the details of a module or structure.
Actually using 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.

47. 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?
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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 document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
The functional domain consists of the whole numbers from 0 to 100.

48. What is a hierarchy of objects?
The process of determining the degree to which software fulfills its intended purpose.
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
Reusing objects and processes to implement more complex objects and processes.
The set of valid input data for a program or function.

49. What does complete mean?

50. What is regression testing?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Specifying what the program must do (the functional requirements) and the constraints on the solution approach (non - functional requirements - such as what language to use).
[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.
(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