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 a class?
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
The process of determining the degree to which software fulfills its intended purpose.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
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

2. What are functional subproblems?
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.
The process of determining the degree to which a software product fulfills its specifications.
Simple statements like do this - then do this - then do that.
Testing a program or function based on the possible input values - treating the code as a 'black box.'

3. What is an exception?
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
Testing a module or function by itself.
It is possible to carry out exhaustive data coverage for this program.
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

4. Give a specific C++ language attribute that supports information hiding.

5. What is integration testing?
A combination of branches that might be traversed when a program or function is executed.
A cohesive system subunit that performs a share of the work.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
Testing performed to integrate program modules that have already been independently unit tested.

6. What is a stub?
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.
The program's inputs and outputs should be readable and understandable to users.
A special function that can be used in top- down testing to stand in for a lower- level function.

7. What is a path?
A verification method in which a team performs a manual simulation of the program or design.
A combination of branches that might be traversed when a program or function is executed.
[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.
Abstraction

8. 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?
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
Making changes to fix operational errors and to add or modify the function of the program.
It is possible to carry out exhaustive data coverage for this program.
The program meets the demands of time or space in memory.

9. What is functional decomposition?
To 'do everything' specified to meet its requirements.
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
Understanding the nature of the problem to be solved.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

10. 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 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 verification method in which a team performs a manual simulation of the program or design.
It is possible to carry out exhaustive data coverage for this program.

11. What is operation?
Actually using the program.
Coding a program in a computer language.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
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

12. What is problem analysis?
A formal definition of the problem your program must solve.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
Two greater than symbols [>>].
Understanding the nature of the problem to be solved.

13. What is inspection?
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 verification method in which one member of a team reads the program or design line by line and the other members point out errors.
Reusing objects and processes to implement more complex objects and processes.
Making changes to fix operational errors and to add or modify the function of the program.

14. What is stepwise refinement?

15. What is path testing?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
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.

16. What is implementation of the design?
Coding a program in a computer language.
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 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.
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

17. What is testing?
The process of executing a program with data sets designed to discover errors.
The program meets the demands of time or space in memory.
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 document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.

18. What is the extraction operator?
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Two greater than symbols [>>].

19. What does usable mean?

20. Explain what we mean by 'ideaware'.
A shared body of knowledge.
Determining exactly what the program must do.
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.
Coding a program in a computer language.

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

22. What does efficient mean?
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
The program meets the demands of time or space in memory.
The functional domain consists of the whole numbers from 0 to 100.
Simple statements like do this - then do this - then do that.

23. What is black- box testing?

24. What is regression testing?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
The program's inputs and outputs should be readable and understandable to users.
A shared body of knowledge.

25. What is an assertion?
A shared body of knowledge.
Testing a module or function by itself.
A logical proposition that can be true or false.
Turning over the tested program to the customer or user (or instructor!).

26. What is the difference between an object and an object class?
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 logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Running the program with the test cases listed in the test plan.
An object is an individual while a class is a description of a group of objects with similar properties and behaviors. Labrador dogs is an example of a class and Maggie is an example of an object.

27. Name some software tools that you have used in developing computer programs.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
To 'do everything' specified to meet its requirements.
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

28. What is program verification?
When every statement in the program is executed at least once.
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 process of determining the degree to which a software product fulfills its specifications.
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.

29. What are preconditions?
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
Tracing an execution of a design or program on paper.
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.
Turning over the tested program to the customer or user (or instructor!).

30. What is a software specification?
Simple statements like do this - then do this - then do that.
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 program meets the demands of time or space in memory.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.

31. What is bottom- up stepwise refinement?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
The set of valid input data for a program or function.
Detecting and fixing errors and demonstrating the correctness of 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.

32. How can you verify the correctness of the software you develop?
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.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
You can test the software to see if the correct outcome occurs
Also called robustness. The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.

33. What is round- trip gestalt design?
The process of removing known errors.
[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.
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
To 'do everything' specified to meet its requirements.

34. What is a branch?
To take an object and move it from a general perspective to a precise level of detail. Variations of stepwise refinement include: top- down - bottom- up - functional decomposition - and even 'round- trip gestalt design.'
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
A testing technique whereby the tester tries to execute all possible paths in a program or function.

35. What is requirements elicitation?
A verification method in which a team performs a manual simulation of the program or design.
Determining exactly what the program must do.
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.
Coding a program in a computer language.

36. 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.
The program meets the demands of time or space in memory.
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.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator

37. What is maintenance?
A special function that can be used in top- down testing to stand in for a lower- level function.
Making changes to fix operational errors and to add or modify the function of the program.
The process of testing the system in its real environment with real data.
A verification method in which a team performs a manual simulation of the program or design.

38. What are class - responsibility - and collaboration (CRC) cards?
The process of determining the degree to which a software product fulfills its specifications.
Simple statements like do this - then do this - then do that.
(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 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

39. What is testing and verification?
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 verification method in which one member of a team reads the program or design line by line and the other members point out errors.
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

40. What are the goals of quality software?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
(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

41. What is software engineering?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
A verification method in which a team performs a manual simulation of the program or design.
The functional domain consists of the whole numbers from 0 to 100.
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.

42. What is the functional domain?
Tracing an execution of a design or program on paper.
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.
The set of valid input data for a program or function.

43. The difference between unit testing and integration testing.
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
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 structure of tasks with a main module and subsections.

44. What is a detailed specification?
A formal definition of the problem your program must solve.
Abstraction
Two greater than symbols [>>].
A cohesive system subunit that performs a share of the work.

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

46. What is white- box testing?
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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.
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 formal definition of the problem your program must solve.

47. What is deskchecking?
(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
Abstraction
Tracing an execution of a design or program on paper.

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.
[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 based on measurable factors.
Abstraction
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

49. What is a module?
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
A cohesive system subunit that performs a share of the work.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.

50. What is a walk- through?
A statement of what is to be provided by a computer system or software product.
Testing a module or function by itself.
A verification method in which a team performs a manual simulation of the program or design.
A shared body of knowledge.