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. Name some software tools that you have used in developing computer programs.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
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.
You can test the software to see if the correct outcome occurs

2. What is problem analysis?
Coding a program in a computer language.
Understanding the nature of the problem to be solved.
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.
A logical proposition that can be true or false.

3. What does usable mean?

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

5. What is a test plan?
Two less than symbols [<<].
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
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 process of executing a program with data sets designed to discover errors.

6. What is top- down stepwise refinement?
A combination of branches that might be traversed when a program or function is executed.
Making changes to fix operational errors and to add or modify the function of the program.
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 cohesive system subunit that performs a share of the work.

7. What is white- box testing?
The set of valid input data for a program or function.
A notational tool that helps us determine our initial designs. CRC cards always contain information about the class name - responsibilities of the class and collaborations. CRC cards are great tools for refining an object- oriented design - especiall
Also called 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.

8. What is implementation of the design?
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
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.
Coding a program in a computer language.

9. What is round- trip gestalt design?
Defines the stepwise refinement approach to object- oriented design suggested by Grady Booch. First - the tangible items and events in the problem domain are identified and assigned to candidate classes and objects. Next - the external properties and
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A property when changes within a module do not result in changes in the modules that use it.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.

10. What is requirements elicitation?
Detecting and fixing errors and demonstrating the correctness of the program.
Determining exactly what the program must do.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
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.

11. What is the insertion operator?
The process of executing a program with data sets designed to discover 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).
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.

12. What does complete mean?

13. What is the scope resolution operator?
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
Understanding the nature of the problem to be solved.
The double colon operator (::).
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

14. 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?
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
It is possible to carry out exhaustive data coverage for this program.
A logical proposition that can be true or false.
Testing performed to integrate program modules that have already been independently unit tested.

15. What is path testing?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Testing performed to integrate program modules that have already been independently unit tested.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
To 'do it right' to meet its requirements.

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

17. What is a walk- through?
A verification method in which a team performs a manual simulation of the program or design.
Simple statements like do this - then do this - then do that.
A formal definition of the problem your program must solve.
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.

18. What is program validation?
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
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
The process of determining the degree to which software fulfills its intended purpose.
Two less than symbols [<<].

19. What is fault tolerance?
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 standard - integrated set of software engineering tools and techniques used on a project by an organization.
To 'do everything' specified 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.

20. What is black- box testing?

21. What is a hierarchy of 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.
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 process of determining the degree to which a software product fulfills its specifications.
Reusing objects and processes to implement more complex objects and processes.

22. What are postconditions?
To 'do it right' to meet its requirements.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
Turning over the tested program to the customer or user (or instructor!).
A shared body of knowledge.

23. What is the functional domain?
A special function that can be used in top- down testing to stand in for a lower- level function.
A verification method in which a team performs a manual simulation of the program or design.
Abstraction
The set of valid input data for a program or function.

24. What is a stub?
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
A special function that can be used in top- down testing to stand in for a lower- level function.
To take an object and move it from a general perspective to a precise level of detail. Variations of stepwise refinement include: top- down - bottom- up - functional decomposition - and even 'round- trip gestalt design.'

25. What is a module?
A cohesive system subunit that performs a share of the work.
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.
Two less than symbols [<<].

26. What is the extraction operator?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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 greater than symbols [>>].
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?
When every statement in the program is executed at least once.
A property when changes within a module do not result in changes in the modules that use it.
A combination of branches that might be traversed when a program or function is executed.
The process of executing a program with data sets designed to discover errors.

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

29. What is information hiding and why is it considered a good software development practice.
A verification method in which one member of a team reads the program or design line by line and the other members point out errors.
The practice of only showing the information necessary for a user level and hiding the rest of the information. this makes programming in teams easier because you can see the big picture easier. Also - the programmer does not have to worry if the imp
A statement of what is to be provided by a computer system or software product.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.

30. 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?
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.
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.
Turning over the tested program to the customer or user (or instructor!).

31. What is a path?
A combination of branches that might be traversed when a program or function is executed.
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.
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 code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.

32. 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
A logical proposition that can be true or false.
The program's inputs and outputs should be readable and understandable to users.
A shared body of knowledge.

33. What is testing and verification?
Detecting and fixing errors and demonstrating the correctness of the program.
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 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.

34. What is deskchecking?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
A structure of tasks with a main module and subsections.
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.
Tracing an execution of a design or program on paper.

35. What is an assertion?
The process of determining the degree to which a software product fulfills its specifications.
A logical proposition that can be true or false.
Tracing an execution of a design or program on paper.
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

36. What is statement coverage?
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 testing technique whereby the tester tries to execute all possible paths in a program or function.
When every statement in the program is executed at least once.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

37. What is the unified modeling language (UML)?
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.
Detecting and fixing errors and demonstrating the correctness of the 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.
Two greater than symbols [>>].

38. What is maintenance?
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.
Making changes to fix operational errors and to add or modify the function of the program.
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 approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.

39. What is the difference between an object and an object 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
A formal definition of the problem your program must solve.
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.
To 'do it right' to meet its requirements.

40. What is software engineering?
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 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 statement of what is to be provided by a computer system or software product.
Reusing objects and processes to implement more complex objects and processes.

41. 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?
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.
A combination of branches that might be traversed when a program or function is executed.
Testing a module or function by itself.

42. What does correct mean?

43. What is implementing a test plan?
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
Running the program with the test cases listed in the test plan.
It is possible to carry out exhaustive data coverage for this program.
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

44. What is a technique used by good problem solvers for dealing with complexity?
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.
Abstraction
Running the program with the test cases listed in the test plan.
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

45. What is regression testing?
Turning over the tested program to the customer or user (or instructor!).
A logical proposition that can be true or false.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
Testing performed to integrate program modules that have already been independently unit tested.

46. 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.
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 cohesive system subunit that performs a share of the work.
[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.
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.

47. What is bottom- up stepwise refinement?
The approach in which the details come first. After the detailed components are identified and designed - they are brought together into increasingly higher- level components.
The set of valid input data for a program or function.
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.

48. What are requirements?
A property when changes within a module do not result in changes in the modules that use it.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
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 statement of what is to be provided by a computer system or software product.

49. What is testing?
To 'do it right' to meet its requirements.
The process of executing a program with data sets designed to discover errors.
A structure of tasks with a main module and subsections.
You can test the software to see if the correct outcome occurs

50. What is stepwise refinement?