Essentially, the goal of creating a WBS is to break the overall task into manageable pieces. An example WBS for military UAV projects is given in Figure 8.5. These are often broken
Figure 8.5 Typical military UAV work-breakdown structure interface definitions, from MIL-HDBK-881C for UAVs.
down in one of three ways: by “object,” or by “system,” or by task or deliverable. An object breakdown, for example, might break the airframe into “front fuselage,” “center fuselage,” and “rear fuselage.” In other words, it breaks a physical artifact into logical regional “chunks.” A “systems” breakdown might include “electrical power” that might not be restricted to a particular region. A good WBS includes not only the artifact being designed but the contextual deliverables as shown in Figure 8.5. A WBS element that is very relevant to student UAV projects is “test and evaluation,” which is also shown in Figure 8.5. Even a student UAV team needs to think about how the subsystems and overall system will be tested.