Home Engineering Small Unmanned Fixed-Wing Aircraft Design. A Practical Approach
Allocation of Responsibility
As the team progresses into the preliminary and detailed design phases, it is very important that there are clear allocations of responsibilities. This is essentially a project management function, but as the product definition becomes more detailed, this allocation becomes more important. Often, people use a “responsibility allocation matrix” (RAM), an example of which is given in Table 8.1. This example adds the sophistication of several roles as follows:
All projects have a purpose, and even student projects will have hypothetical “customers.” In general, projects have “stakeholders.” In student projects, the participants themselves are
Table 8.1 Example responsibility allocation matrix for a maintenance team.
Responsible (R), the Doer; accountable (A), the buck stops here; consulted (C), in the loop; informed (I), kept in the picture.
stakeholders who probably want to get the best mark possible as well as gaining relevant knowledge and experience. The supervisor might want a deliverable as part of a wider academic research roadmap.
In order to ensure that the needs of the stakeholders are addressed, it is worth documenting the goals, requirements, and deliverables at an early stage, that is, the design brief. In the discipline of systems engineering, these requirements are then broken down logically and functionally such that each of the items in the WBS has a clear set of auditable requirements that “flow down” from the top level requirements, as shown in Figure 8.6.
|< Prev||CONTENTS||Next >|