Cs 221 - Software Engineering

Front 1

List and define the "Five Steps in Software Development"

Back 1

Requirements Specification
Analysis
Design
Implementation
Testing: Verification and Validation

Front 2

Define "Requirements Specification"

Back 2

Determine what the software must do to satisfy the customer's needs.

Front 3

Define "Analysis"

Back 3

Study the requirements to fully understand what the software must do and restate the requirements in more detailed, technical terms.

Front 4

Define "Design"

Back 4

Develop a plan detailing how the software will be implemented.

Front 5

Define "Implementation"

Back 5

Write the source code in the chosen programming language.

Front 6

Define "Testing"

Back 6

Test to insure all parts of the application work correctly and all requirements have been met.

Front 7

Define "Software Engineering"

Back 7

A disciplined approach to the design, production, and maintenance of computer programs that are developed on time and within cost estimates, using tools to help manage the size and complexity of the resulting software products.

Front 8

Define "Requirements"

Back 8

A statement of what is to be provided by a computer system or software product.

Front 9

Define "Software Specification"

Back 9

A detailed description of the functions, inputs, processing, outputs, and special requirements of a software product.

Front 10

Define "Algorithm"

Back 10

A logical sequence of discrete steps that describes a complete solution to a given problem computable in a finite amount of time.

Front 11

Define "Driver"

Back 11

A special function written to use as a testing function. It passes known inputs to selected functions and reports the return values.

Front 12

Define "Stub"

Back 12

A special function written to use as a testing function. A stub returns known outputs to a calling function to determine how the calling function handles the returned values.

Front 13

Define "Verification"

Back 13

The process of determining the degree to which software functions properly. (Did we build the software right?)

Front 14

Define "Validation"

Back 14

The process of determining the degree to which software does, in fact, produces results that satisfy the original requirements. (Did we build the right software?)

Front 15

Define "Module"

Back 15

A unit of organization of a software system.

Front 16

What is "Algorithm Analysis"?

Back 16

A measure of the amount of resources necessary to execute a section of code.

Front 17

What is "Big O Notation"?

Back 17

A notation that expresses computing time (complexity) as a term in a function that increases most rapidly relative to the size of a problem.

Front 18

List from best to worst the eight standard measures used in Big O notation.

Back 18

O(1) - Constant
O(log n) - Logarithmic
O(n) - Linear
O(n log n) - n log n
O(n^2) - Quadratic
O(n^3) - Cubic
O(2^n) - Exponential
O(10^n) - Exponential

Front 19

What is meant by "Program Design"?

Back 19

An organized plan consisting of a detailed description of the software system from the top level down to the individual functions level.

Front 20

Define "Top-down" program design.

Back 20

Procedural programming. The focus is on the processes.

Front 21

Define "Bottom-up" program design.

Back 21

Object oriented programming. The focus is on the data objects.

Front 22

What is the "Requirements Definition Document"?

Back 22

A document written for the customer in terms the customer will understand, stating what the product will do.

Front 23

What is the "Requirements Specification Document"?

Back 23

A document written for the SW designers in more technical terms that they understand, describing the information needed to design and implement the program.

Front 24

What is the "Software Design Document"?

Back 24

A document that contains all of the details of how the software will be implemented. It is written for the programmers.

Front 25

What is the "Test Plan"?

Back 25

A document written for the SW testers, including detailed testing procedures.

Front 26

What is the "Statement of Work"?

Back 26

A document written by the customer, outlining the requirements of what the software product should do.

Front 27

What is "Top-down" testing?

Back 27

Testing using function "Stubs" which mimic the actions of functions which are called by upper level functions.

Front 28

What is "Bottom-up" testing?

Back 28

Testing using function "Drivers" which mimic the actions of functions which are calling lower level functions.

Front 29

What are the four types of software testing?

Back 29

Unit - Testing single functions.
Integration - Testing how functions work together.
Acceptance - Testing against stated software requirements.
Regression - Testing after fixing bugs or adding new features.

Front 30

What is "Black-box" testing?

Back 30

All that is known about the software is the inputs and expected outputs. Nothing about what the software does or how things are done is known to the tester.

Front 31

What is "White-box" or "Clear-box" testing?

Back 31

The specifics of what the software does and how it is done is known to the tester.