Software Engineering

133
7.6 
Step 6: Technical planning
plans should be identified for each risk abatement approach and the conditions that 
would warrant their activation must be identified. The dependencies among tasks 
must be aligned to establish the criteria for task initiation and provide a view of the 
overall workflow and schedules.
7.4 
 Step 4: Resource identification, estimation, and 
allocation
The resources required to execute each task must be identified in terms of man-
power, facilities, equipment, office supplies, and computer automated software 
engineering (CASE) tools. Resources may include any item that contributes to 
project costs including travel expenses, reproduction, and software-related skills 
training. The costs associated with resources should be allocated among techni-
cal organizations participating in executing the task. Lower-level tasks should be 
combined to establish higher-level task cost estimates. This exercise leads to the 
identification of budget estimates for organizational and integrated technical work 
packages. Work packages can be combined to summarize the cost of performing 
each element of the WBS.
Initial work package cost estimates must be reconciled against available project 
resources. Task scope and resource requirements may need to be revised to provide 
a complete set of work packages consistent with project budget constraints. Work 
packages that involve an identified risk should incorporate a contingency reserve 
budget based on the magnitude of the risk, its probability of occurring, and the 
resources needed to execute the contingency plan of action.