Page 208 -

CHAPTER 7 PROJECT SCHEDULING AND TRACKING 179

FIGURE 7.2
Preliminary concept planning
Concept Technology risk assessment
development Planning
tasks using an
evolutionary Engineering/
model Project definition
construction
Concept scoping
Proof of concept

New Application
Application development
Application enhancement
Re-engineering maintenance
Concept implementation
Customer reaction
Release
Customer
evaluation

Task definition: Task I.1 Concept Scoping
I.1.1 Identify need, benefits and potential customers;
I.1.2 Define desired output/control and input events that drive the application;
Begin Task I.1.2
I.1.2.1 FTR: Review written description of need 9
I.1.2.2 Derive a list of customer visible outputs/inputs
case of: mechanics
mechanics = quality function deployment
meet with customer to isolate major concept requirements;
interview end-users;
The adaptable process observe current approach to problem, current process;
model (APM) contains a review past requests and complaints;
complete process design
language description for mechanics = structured analysis
all software engineering make list of major data objects;
tasks. define relationships between objects;
define object attributes;
mechanics = object view
make list of problem classes;
develop class hierarchy and class connections;
define attributes for classes;
endcase
I.1.2.3 FTR: Review outputs/inputs with customer and revise as required;
endtask Task I.1.2
I.1.3 Define the functionality/behavior for each major function;
Begin Task I.1.3

9 FTR indicates that a formal technical review (Chapter 8) is to be conducted.