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 program verification?
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 determining the degree to which a software product fulfills its specifications.
A formal definition of the problem your program must solve.
Testing performed to integrate program modules that have already been independently unit tested.

2. What is implementation of the design?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
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.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.

3. What does correct mean?

4. What is the unified modeling language (UML)?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Two less than symbols [<<].
Recording how the program meets the requirements - from the 'big picture' overview to the detailed 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.

5. What is a module?
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
Testing based on measurable factors.
A cohesive system subunit that performs a share of the work.
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

6. What does efficient mean?
The program meets the demands of time or space in memory.
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.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)

7. 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)
A cohesive system subunit that performs a share of the work.
A document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.

8. 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.
When every statement in the program is executed at least once.
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.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator

9. What is the scope resolution operator?
The double colon operator (::).
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 special function that can be used in top- down testing to stand in for a lower- level 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.

10. What is unit testing?
Testing a module or function by itself.
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 program meets the demands of time or space in memory.
A property when changes within a module do not result in changes in the modules that use it.

11. What is the software process?
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
The program's inputs and outputs should be readable and understandable to users.
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.
Abstraction

12. What is a class?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
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.
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.

13. What is operation?
The set of valid input data for a program or function.
Testing based on measurable factors.
The double colon operator (::).
Actually using the program.

14. What is stepwise refinement?

15. What is robustness?
The ability of a program to recover following an error; the ability of a program to continue to operate within its environment.
Understanding the nature of the problem to be solved.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
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

16. What is inspection?
Testing a module or function by itself.
To 'do it right' to meet its requirements.
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 one member of a team reads the program or design line by line and the other members point out errors.

17. What is debugging?
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 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.
A special function that can be used in top- down testing to stand in for a lower- level function.

18. 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?
(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
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.
The functional domain consists of the whole numbers from 0 to 100.
Detecting and fixing errors and demonstrating the correctness of the program.

19. What does usable mean?

20. What is requirements elicitation?
Making changes to fix operational errors and to add or modify the function of the program.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
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.
Determining exactly what the program must do.

21. What is the difference between an object and an object class?
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.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.

22. What are functional subproblems?
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
Simple statements like do this - then do this - then do that.
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.
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).

23. What is a hierarchy of tasks?
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
When every statement in the program is executed at least once.
A structure of tasks with a main module and subsections.
A formal definition of the problem your program must solve.

24. How can you verify the correctness of the software you develop?
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
You can test the software to see if the correct outcome occurs
Two greater than symbols [>>].
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.

25. What is requirements specification?
To 'do everything' specified to meet its requirements.
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.
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).
Abstraction

26. What are preconditions?
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.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
A statement of what is to be provided by a computer system or software product.

27. What is testing?
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.
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).

28. What is implementing a 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
The process of determining the degree to which software fulfills its intended purpose.
Testing based on measurable factors.
Running the program with the test cases listed in the test plan.

29. What is the extraction operator?
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 property when changes within a module do not result in changes in the modules that use it.
The process of executing a program with data sets designed to discover errors.
Two greater than symbols [>>].

30. What is software engineering?
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.
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.

31. What is deskchecking?
Tracing an execution of a design or program on paper.
(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 standard - integrated set of software engineering tools and techniques used on a project by an organization.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

32. What is an assertion?
[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.
A logical proposition that can be true or false.
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.

33. What is regression testing?
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 program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
The functional domain consists of the whole numbers from 0 to 100.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.

34. What is maintenance?
To 'do everything' specified to meet its requirements.
Detecting and fixing errors and demonstrating the correctness of the program.
Making changes to fix operational errors and to add or modify the function of the program.
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).

35. What is functional decomposition?
It is possible to carry out exhaustive data coverage for this program.
Coding a program in a computer language.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
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 delivery?
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
Turning over the tested program to the customer or user (or instructor!).
Also called clear- 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.

37. What is top- down stepwise refinement?
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 process of removing known errors.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
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.

38. What is a walk- through?
A verification method in which a team performs a manual simulation of the program or design.
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.
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

39. What are postconditions?
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
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
A shared body of knowledge.
Tracing an execution of a design or program on paper.

40. What is an object?
A structure of tasks with a main module and subsections.
The functional domain consists of the whole numbers from 0 to 100.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

41. Explain what we mean by 'ideaware'.
A shared body of knowledge.
It is possible to carry out exhaustive data coverage for this program.
Testing a program or function based on the possible input values - treating the code as a 'black box.'
To 'do everything' specified to meet its requirements.

42. What is black- box testing?

43. What is abstraction?
[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.
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
A model of a complex system that includes only the details essential to the perspective of the viewer of the system.
The process of determining the degree to which software fulfills its intended purpose.

44. 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.
A verification method in which a team performs a manual simulation of the program or design.
Running the program with the test cases listed in the test plan.
A statement of what is to be provided by a computer system or software product.

45. What is fault tolerance?
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
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.
Turning over the tested program to the customer or user (or instructor!).
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.

46. What is a branch?
Detecting and fixing errors and demonstrating the correctness of the program.
(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.'
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.

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

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

49. What are the goals of quality software?
A testing technique whereby the tester tries to execute all possible paths in a program or function.
(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
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

50. What are software requirements?
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 statement of what is to be provided by a computer system or software product.
The process of testing the system in its real environment with real data.
When every statement in the program is executed at least once.