Page 209 -

180 PART TWO MANAGING SOFTWARE PROJECTS

I.1.3.1 FTR: Review output and input data objects derived in task I.1.2;
I.1.3.2 Derive a model of functions/behaviors;
case of: mechanics
mechanics = quality function deployment
meet with customer to review major concept requirements;
interview end-users;
observe current approach to problem, current process;
develop a hierarchical outline of functions/behaviors;
mechanics = structured analysis
derive a context level data flow diagram;
refine the data flow diagram to provide more detail;
write processing narratives for functions at lowest level of refinement;
mechanics = object view
define operations/methods that are relevant for each class;
endcase
I.1.3.3 FTR: Review functions/behaviors with customer and revise as required;
endtask Task I.1.3
I.1.4 Isolate those elements of the technology to be implemented in software;
I.1.5 Research availability of existing software;
I.1.6 Define technical feasibility;
I.1.7 Make quick estimate of size;
I.1.8 Create a Scope Definition;
endTask definition: Task I.1
The tasks and subtasks noted in the process design language refinement form the
basis for a detailed schedule for the concept scoping activity.

7.6 DEFINING A TASK NETWORK
Individual tasks and subtasks have interdependencies based on their sequence. In
addition, when more than one person is involved in a software engineering project,
it is likely that development activities and tasks will be performed in parallel. When
this occurs, concurrent tasks must be coordinated so that they will be complete when
The task network is a later tasks require their work product(s).
useful mechanism for
depicting intertask A task network, also called an activity network, is a graphic representation of the
dependencies and task flow for a project. It is sometimes used as the mechanism through which task
determining the critical sequence and dependencies are input to an automated project scheduling tool. In its
path. simplest form (used when creating a macroscopic schedule), the task network depicts

major software engineering tasks. Figure 7.3 shows a schematic task network for a
concept development project.
The concurrent nature of software engineering activities leads to a number of
important scheduling requirements. Because parallel tasks occur asynchronously, the
planner must determine intertask dependencies to ensure continuous progress toward
completion. In addition, the project manager should be aware of those tasks that lie
on the critical path. That is, tasks that must be completed on schedule if the project