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 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.
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
Understanding the nature of the problem to be solved.
A combination of branches that might be traversed when a program or function is executed.

2. What are the goals of quality software?
C++ classes promote information hiding. You can declare private functions and private variables that don't need to be accessable to use the class.
It is possible to carry out exhaustive data coverage for this program.
The program's inputs and outputs should be readable and understandable to users.
(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

3. What are class - responsibility - and collaboration (CRC) cards?
A logical proposition that can be true or false.
Running the program with the test cases listed in the 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
Turning over the tested program to the customer or user (or instructor!).

4. 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.
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.
Determining exactly what the program must do.

5. What is the functional domain?
The set of valid input data for a program or function.
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 cohesive system subunit that performs a share of the work.

6. What is the software process?
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
Coding a program in a computer language.
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.
To 'do it right' to meet its requirements.

7. What is a class?
A statement of what is to be provided by a computer system or software product.
To 'do everything' specified to meet its requirements.
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

8. What is the extraction operator?
The process of determining the degree to which software fulfills its intended purpose.
Also called a class. 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.
Two greater than symbols [>>].

9. 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?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
The program's inputs and outputs should be readable and understandable to users.
It is possible to carry out exhaustive data coverage for this program.
An unusual - generally unpredictable event - detectable by software or hardware - that requires special processing; the event may or may not be erroneous.

10. What is functional decomposition?
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
The set of valid input data for a program or function.
(1) Wasted programmer/planning hours (2) Wasted dollars (salaries - etc) (3) More difficult for a new programmer to fix - not the creator
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

11. What is a hierarchy of objects?
Reusing objects and processes to implement more complex objects and processes.
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.
To 'do everything' specified to meet its requirements.
Two less than symbols [<<].

12. What is requirements elicitation?
The double colon operator (::).
Determining exactly what the program must do.
Understanding the nature of the problem to be solved.
A combination of branches that might be traversed when a program or function is executed.

13. What is debugging?
Turning over the tested program to the customer or user (or instructor!).
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
To 'do everything' specified to meet its requirements.
The process of removing known errors.

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

15. What is program verification?
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 removing known errors.
It is possible to carry out exhaustive data coverage for this program.
The process of determining the degree to which a software product fulfills its specifications.

16. What is the insertion operator?
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 statement of what is to be provided by a computer system or software product.
Two less than symbols [<<].
A structure of tasks with a main module and subsections.

17. What is a detailed specification?
Making changes to fix operational errors and to add or modify the function of the program.
A formal definition of the problem your program must solve.
Two greater than symbols [>>].
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.

18. Name some software tools that you have used in developing computer programs.
To 'do everything' specified to meet its requirements.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
Running the program with the test cases listed in the test plan.
Determining exactly what the program must do.

19. 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?
The functional domain consists of the whole numbers from 0 to 100.
The process of executing a program with data sets designed to discover errors.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
You can test the software to see if the correct outcome occurs

20. What is stepwise refinement?

21. What is requirements specification?
A standard - integrated set of software engineering tools and techniques used on a project by an organization.
Simple statements like do this - then do this - then do that.
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).
Testing based on measurable factors.

22. Explain what we mean by 'ideaware'.
A shared body of knowledge.
Two greater than symbols [>>].
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
When every statement in the program is executed at least once.

23. How can you verify the correctness of the software you develop?
Understanding the nature of the problem to be solved.
You can test the software to see if the correct outcome occurs
A code segment that is not always executed; for example - a switch statement has as many branches as there are case labels.
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.

24. What is information hiding?
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 document showing the test cases planned for a program or module - their purposes - inputs - expected outputs - and criteria for success.
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 logical proposition that can be true or false.

25. What are software requirements?
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.
The process of testing the system in its real environment with real data.
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.

26. What is an acceptance test?
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
The process of testing the system in its real environment with real data.
Two greater than symbols [>>].
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.

27. 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.
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 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.

28. What is statement coverage?
When every statement in the program is executed at least once.
Running the program with the test cases listed in the test plan.
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.

29. What is top- down stepwise refinement?
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.
[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 standard - integrated set of software engineering tools and techniques used on a project by an organization.
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

30. What is path testing?
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 testing technique whereby the tester tries to execute all possible paths in a program or function.
The program meets the demands of time or space in memory.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

31. What is program validation?
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
[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.
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.

32. What is black- box testing?

33. 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.
The program's inputs and outputs should be readable and understandable to users.
Testing a module or function by itself.
Also called a class. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.

34. What is a module?
A cohesive system subunit that performs a share of the work.
A statement of what is to be provided by a computer system or software product.
Recording how the program meets the requirements - from the 'big picture' overview to the detailed design.
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.

35. What is an algorithm?
A shared body of knowledge.
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.
Testing performed to integrate program modules that have already been independently unit tested.

36. What is maintenance?
Making changes to fix operational errors and to add or modify the function of the program.
Also called an object. The description of a group of objects with similar properties and behaviors; a pattern for creating individual objects.
Assertions that state what results are expected at the exit of an operation or function - assuming that the preconditions are true.
The functional domain consists of the whole numbers from 0 to 100.

37. 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
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
Two less than symbols [<<].
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.

38. What is delivery?
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 process of determining the degree to which software fulfills its intended purpose.
Turning over the tested program to the customer or user (or instructor!).
A combination of branches that might be traversed when a program or function is executed.

39. What is a software specification?
You can test the software to see if the correct outcome occurs
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 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 a software product fulfills its specifications.

40. What is problem analysis?
A logical set of discrete steps that describes a complete solution to a given problem - computable in a finite amount of time.
Reusing objects and processes to implement more complex objects and processes.
It is possible to carry out exhaustive data coverage for this program.
Understanding the nature of the problem to be solved.

41. What is testing?
A structure of tasks with a main module and subsections.
The process of executing a program with data sets designed to discover errors.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)
(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

42. What is implementing a test plan?
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).
Running the program with the test cases listed in the test plan.
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.

43. What is a test driver?
A program that sets up the testing environment by declaring and assigning initial values to variables - then calls the subprogram to be tested.
To 'do everything' specified to meet its requirements.
A shared body of knowledge.
These tools are text editors - compilers - assemblers - operating systems - and debugging programs. (p5)

44. What is deskchecking?
Also called white- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
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 cohesive system subunit that performs a share of the work.

45. What is the difference between an object and an object class?
Simple statements like do this - then do this - then do that.
Assertions that must be true on entry into an operation or function for the postconditions to be guaranteed.
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.
Two less than symbols [<<].

46. What is information hiding and why is it considered a good software development practice.
Testing based on measurable factors.
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
Actually using 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).

47. What is metric- based testing?
The double colon operator (::).
Abstraction
Testing based on measurable factors.
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.

48. What are functional subproblems?
Also called clear- box testing. Testing a program or function based on covering all the statements - branches - or paths of code.
Simple statements like do this - then do this - then do that.
Two less than symbols [<<].
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.

49. What is a hierarchy of tasks?
The program's inputs and outputs should be readable and understandable to users.
The set of valid input data for a program or function.
To 'do everything' specified to meet its requirements.
A structure of tasks with a main module and subsections.

50. What is loose coupling?
Two less than symbols [<<].
Re- execution of program tests after modifications have been made to ensure that the program still works correctly.
A property when changes within a module do not result in changes in the modules that use it.
Testing performed to integrate program modules that have already been independently unit tested.