3.2 Technical Performance Checklist

Table 3-1 is the Technical Performance Checklist. Use this table to check the

content of your plans and processes when planning the project or to confirm the

Technical Plan when the project is running. The Technical Recovery Checklist is

presented in Chapter 5 of this book.

T a b l e 3 - 1 — T e c h n i c a l P e r f o r m a n c e C h e c k l i s t

51 ARCHITECTURE Explain Yes

51a All Critical Success Factors (CSFs) such as Mean Time To Repair 41

(MTTR), Mean Time Between Failure (MTBF), etc., have been

documented and understood

51b All modules/subsystems are well defined 41

51c All key functions such as time, length, weight, performance 42

requirements, and interfaces, etc., listed in the requirements are

appropriately covered

51d All major elements (physical and data) are described and justified 42

51e All key aspects of user interfaces are well defined 42

51f The Architecture hangs together conceptually 42

52 DESIGN Explain Yes

52a The design process is correct and traceable to enterprise, customer, 42

and standard processes

52b The design is correct and traceable to the requirements 43

52c The design is efficient 43

52d The design adequately addresses issues that were identified and 43

deferred to design at the architectural level

52e The design is partitioned into manageable segments 44

52f The design accounts for supportability, Life Cycle Cost (LCC), total 44

cost of ownership, and future expansions

52g Technical Performance Measures (TPMs) such as data retrieval 45

time, weight, error rate, etc., have been defined and accommodated

53 DESIGN REVIEWS Explain Yes

53a All Design Reviews were completed according to required processes 45

53b The customer approved each Design Review 45

54 IN-PROCESS REVIEWS Explain Yes

54a All required In-Process Reviews were conducted according to 45

required processes

54b Each In-Process Review was approved by the appropriate authority 46

55 PROTOTYPES Explain Yes

55a The prototypes reflect the requirements 46

55b Prototypes were constructed incrementally 47

55c Prototype changes were incorporated into the design using the 47

Change Control Process

55d Each prototype change was reviewed and accepted by the originator 47

of the requirements

(continues)

T a b l e 3 - 1 — ( C o n t i n u e d )

56 SUBCONTRACTS Explain Yes

56a The sum of all subcontracts reflects all tasks allocated 48

56b Each subcontract contains all tasks allocated 48

57 PURCHASE ORDERS Explain Yes

57a The sum of all Purchase Orders reflects all purchases to be made 48

57b Each Purchase Order is complete 49

58 PRODUCTION/MANUFACTURING Explain Yes

58a All production/manufacturing processes are traceable to standard, 49

customer, or enterprise processes

58b The line(s) were properly designed and set up for this (these) 50

product(s)

58c Shop orders were correct and thorough 50

58d The materials were proper for the processes and the product(s) and 50

do meet the requirements

59 UNIT TEST Explain Yes

59a Each Unit Test correctly reflects the requirement 51

59b Each design element that applies to the routine/module/subsystem 51

has its own test case

59c Unit Test findings were reviewed for completeness and forwarded 51

to be incorporated into Subsystem Tests and the System Test

59d All Problem Test Reports (PTRs) were captured, dispositioned 52

(allocated for action), and worked off

60 SYSTEM TEST Explain Yes

60a The System Test Plan/Procedure was approved by the customer 52

60b The System Test is traceable to the requirements 52

60c The System Test tested all elements of the system concurrently 52

60d The System Test was performed under appropriate load(s) 53

60e The System Test was performed using the same kind of personnel 53

that will be used by the customer

60f The System Test was properly documented and incorporated the 53

test results of all prior-level tests

61 CONFIGURATION MANAGEMENT Explain Yes

61a The Configuration Management Plan (CMP) is thorough, 53

complete, and authorized

61b Change requests were presented and approved by an appropriate 54

level of the Review Board

61c Version controls are in place and are reflected on (in) the product 54

62 SYSTEM EFFECTIVENESS FACTORS Explain Yes

62a All required System Effectiveness Factors have been appropriately 54

considered

Starting at 51a, read each assertion in the table. If you can answer YES to the

assertion, check it off and proceed to the next one. If you need an explanation

of the assertion, go to the page number listed under the ‘‘Explain’’ column for

that assertion.