Software / System Process

Question 1

Process Specifications Logic can be expressed in 4 ways:

Answer 1

Structured English
Pseudocode
Decision Trees
Decision Tables

Question 2

Describe Decision Tables:

Answer 2

Conditions and Actions on left hand side separated by thick line. Upper half has rules which are combinations of conditions. Must be action for each rule. If n binary conditions then n^2 rules.

Question 3

What does software design stage focus on?

Answer 3

On how to build the system.

Question 4

Software pyramid with design:

Answer 4

Design, code, test, maintenance.

Question 5

Software Design three important concepts:

Answer 5

abstraction, refinement, modularity.

Question 6

Software Design has 4 outputs:

Answer 6

architectural design, data design, component design, interface design.

Question 7

Software design must focus on more than just functional requirements, list 3:

Answer 7

Non-functional requirements: maintainability, security (encapsulation), availability (fault tolerance).

Question 8

Two metrics to evaluate Design Quality.

Answer 8

Coupling and Cohesion.

Question 9

Coupling?

Answer 9

The degree of the closeness of
the relationship between classes. Good coupling is when methods do not refer to each other. Bad = method refers to inside of another method.

Question 10

Cohesion?

Answer 10

The degree to which attributes
and methods of a class support a single object. Bad = class represents many objects, not just one.

Question 11

Two types of coupling?

Answer 11

Interaction (message passing) and Inheritance.

Question 12

Three types of cohesion:

Answer 12

Method cohesion. Class cohesion. Generalisation/specialisation cohesion (ie hierarchy extends cohesion)

Question 13

3 design strategies:

Answer 13

Custom development (in house), Purchase packaged software, outsource.

Question 14

Design Quality - maximise and minimise what?

Answer 14

Maximise cohesion, minimise coupling.

Question 15

Levels of coupling:

Answer 15

No coupling, Data (used entirely), Stamp (used partly), Control (variable passed controls method), Global(refers to global data), Pathological (method1 refers to inside method2).

Question 16

4 levels of method cohesion:

Answer 16

Functional (1 job to do), Sequential (output of function1 used ofr function2), Communicational (2 functions use same attributes), Coincidental (multiple unrelated functions).

Question 17

System testing can be classified by purpose: 4

Answer 17

correctness testing
performance testing
reliability testing
security testing

Question 18

System testing can be classified by life-cycle phase: 7

Answer 18

requirements phase testing
design phase testing
program phase testing
evaluating test results
installation phase testing
acceptance testing
maintenance testing

Question 19

What is a test case (3):

Answer 19

represents typical, critical or abnormal use of system.

Question 20

Three levels of system testing:

Answer 20

Unit testing (modules), integration testing (modules together), system testing (everything).

Question 21

Three static techniques for testing:

Answer 21

Inspection (examine code), Walkthrough (group review), Desk Checking (execute manually).

Question 22

Two types of acceptance testing:

Answer 22

Alpha (on site, simulated data). Beta (customers computer, real data).

Question 23

Test Driven Development?

Answer 23

First write tests, then write code. JUnit.

Question 24

Testing should begin…

Answer 24

in the small and progress to in the large.

Question 25

Dynamic testing techniques (2):

Answer 25

White box and Black box.

Question 26

white box test cases can ensure: 3

Answer 26

all paths exercised once, all logical decisions exercised, execute all loops.

Question 27

black box finds errors like…. : 4

Answer 27

incorrect or missing functions, interface errors, behaviour errors, initialization and termination errors.

Question 28

black box goal:

Answer 28

all inputs tested, outputs match expected outputs.

Question 29

white box goal:

Answer 29

all statements and conditions executed at least once.

Question 30

Software testing is part of broader topic called.. : 2

Answer 30

Verification and Validation.

Question 31

Verification:

Answer 31

Are we building the product right (verify source code)

Question 32

Validation:

Answer 32

Are we building the right product. (validate system against requirements).

Question 33

Unit test requires …. as component is not standalone.

Answer 33

Driver (main program) and stubs (modules called by module being tested).

Question 34

Two approaches to unit testing:

Answer 34

Top-down and Bottom up (clusters).

Question 35

4 different types of whole system testing:

Answer 35

Recovery testing:
Security testing:
Stress testing:
Performance Testing: