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 requirements specification?
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 ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Reusing objects and processes to implement more complex objects and processes.
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).

2. What is the scope resolution operator?
The double colon operator (::).
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
To 'do everything' specified to meet its requirements.
Coding a program in a computer language.

3. What does complete mean?

4. 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 cohesive system subunit that performs a share of the work.
The functional domain consists of the whole numbers from 0 to 100.
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.

5. What does usable mean?

6. What is a hierarchy of objects?
Reusing objects and processes to implement more complex objects and processes.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
[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.

7. What is program validation?
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.
The functional domain consists of the whole numbers from 0 to 100.
A detailed description of the function - inputs - processing - outputs - and special requirements of a software product; it provides the information needed to design and implement the program.
The process of determining the degree to which software fulfills its intended purpose.

8. The difference between unit testing and integration testing.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
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
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Actually using the program.

9. What is a hierarchy of tasks?
A structure of tasks with a main module and subsections.
The process of removing known errors.
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.
Actually using the program.

10. What is the software process?
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
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 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

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

12. What is program verification?
The process of determining the degree to which a software product fulfills its specifications.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
A verification method in which a team performs a manual simulation of the program or design.
Abstraction

13. 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
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.
Running the program with the test cases listed in the test plan.

14. What is black- box testing?

15. What is a test driver?
A combination of branches that might be traversed when a program or function is executed.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
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).

16. What is regression testing?
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.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Coding a program in a computer language.
Making changes to fix operational errors and to add or modify the function of the program.

17. How can you verify the correctness of the software you develop?
Two less than symbols [<<].
You can test the software to see if the correct outcome occurs
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
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.

18. What is software engineering?
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.
Coding a program in a computer language.
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 testing technique whereby the tester tries to execute all possible paths in a program or function.

19. What is a class?
Tracing an execution of a design or program on paper.
The process of determining the degree to which a software product fulfills its specifications.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Making changes to fix operational errors and to add or modify the function of the program.

20. What is statement coverage?
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.
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.
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.'

21. Name some software tools that you have used in developing computer programs.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
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.'
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
When every statement in the program is executed at least once.

22. 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
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.'
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
Turning over the tested program to the customer or user (or instructor!).

23. What is integration testing?
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.
Testing performed to integrate program modules that have already been independently unit tested.
Tracing an execution of a design or program on paper.

24. What is operation?
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
Actually using the program.
The program's inputs and outputs should be readable and understandable to users.
You can test the software to see if the correct outcome occurs

25. What is debugging?
Abstraction
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.
The program's inputs and outputs should be readable and understandable to users.

26. What are class - responsibility - and collaboration (CRC) cards?
Testing a module or function by itself.
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 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
Turning over the tested program to the customer or user (or instructor!).

27. What is path testing?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
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.
Two greater than symbols [>>].
Testing based on measurable factors.

28. What is high- and low- level design?

29. What is inspection?
Testing a program or function based on the possible input values - treating the code as a 'black box.'
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
The process of determining the degree to which a software product fulfills its specifications.
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.

30. What is deskchecking?
A logical proposition that can be true or false.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
Tracing an execution of a design or program on paper.

31. What is stepwise refinement?

32. What is round- trip gestalt design?
To 'do everything' specified to meet its requirements.
Running the program with the test cases listed in the test plan.
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 software fulfills its intended purpose.

33. What are postconditions?
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
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.
It is possible to carry out exhaustive data coverage for this program.
Actually using the program.

34. What does correct mean?

35. 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?
To 'do it right' to meet its requirements.
Abstraction
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
The functional domain consists of the whole numbers from 0 to 100.

36. What is a branch?
Running the program with the test cases listed in the test plan.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
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 a software specification?
Detecting and fixing errors and demonstrating the correctness of the program.
A notational tool that helps us determine our initial designs. CRC cards always contain information about the class name - responsibilities of the class and collaborations. CRC cards are great tools for refining an object- oriented design - especiall
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

38. What is an assertion?
When every statement in the program is executed at least once.
A statement of what is to be provided by a computer system or software product.
A logical proposition that can be true or false.
Testing performed to integrate program modules that have already been independently unit tested.

39. What is the extraction operator?
Two greater than symbols [>>].
Reusing objects and processes to implement more complex objects and processes.
The double colon operator (::).
The process of determining the degree to which software fulfills its intended purpose.

40. What is clear- box testing?
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.
The process of removing known errors.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Detecting and fixing errors and demonstrating the correctness of the program.

41. What is problem analysis?
Understanding the nature of the problem to be solved.
A statement of what is to be provided by a computer system or software product.
You can test the software to see if the correct outcome occurs
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.

42. What are the goals of quality software?
(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 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 practice of hiding details of a function or data structure with the goal of controlling access to the details of a module or structure.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.

43. What is a path?
A combination of branches that might be traversed when a program or function is executed.
Two greater than symbols [>>].
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.
Running the program with the test cases listed in the test plan.

44. What is an object?
The program's inputs and outputs should be readable and understandable to users.
Two greater than symbols [>>].
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.

45. What are preconditions?
A combination of branches that might be traversed when a program or function is executed.
Reusing objects and processes to implement more complex objects and processes.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.

46. What is a module?
To 'do it right' to meet its requirements.
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.
A cohesive system subunit that performs a share of the work.
A formal definition of the problem your program must solve.

47. What is maintenance?
A statement of what is to be provided by a computer system or software product.
Making changes to fix operational errors and to add or modify the function of the program.
The program meets the demands of time or space in memory.
A testing technique whereby the tester tries to execute all possible paths in a program or function.

48. 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.
Coding a program in a computer language.
Running the program with the test cases listed in the test plan.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
[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 unit testing?
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.
A property when changes within a module do not result in changes in the modules that use it.
Testing based on measurable factors.

50. What is an acceptance test?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Testing performed to integrate program modules that have already been independently unit tested.
Reusing objects and processes to implement more complex objects and processes.
The process of testing the system in its real environment with real data.