英语论文网

R>2.4 Project cost estimation breakdown and planned value projection
Section 3 – Risk Management (40%)
3.1 Risk Matrix
3.3 HAZOP Analysis
3.4 FTA Analysis
3.5 FMECA Analysis
More detail on what to include in each section is given in the next section.
Your quality plan should look professional (your company charge £1,500 per day for
your time – so the report is costing the council £10,500 - the cost of a small car!); be
straightforward for the city council to understand (clearly explaining assumptions
made and providing reasoning for any decisions); be original. The partners, with the
assistance of the EE2G1 lecturer, has a number of quality plans to assess. You should
therefore attempt to use methods that make your work stand out.
Quality Plan guidelines
• Keep you report short and succinct – approximately 30 pages long.
• Do not quote materials from course notes. Your comprehension of the
materials is assessed on your application, not the ability to summarise or cut
and paste lecture notes!
• Stay objective and to the point. Do not write the report as an opinionated
narrative – this is not an essay. Use bullet points and tables liberally.
• Keep headings and subheadings to that in this brief:
EE2G1 Project Management and Professional Practice 2008/9
Dr. Neil Cooke
3/4
Detailed breakdown of the Quality Plan
Because this course does not have an academic basis, the coursework is very different
to the most of the other subjects; you may find the following breakdown of the quality
plan useful:
Section 1 – Introduction (20%)
1.1 Statement of work: Project mission statement, scope and project boundary:
• Summarise the overall project (1 paragraph). Include major milestones
and the budget.
• Summarise your project and how it fits into the overall project (1-5
paragraphs)
• Include the major milestones and budget E.g. “The communications
networking infrastructure project will consist of 10 primary activities:
Fibre optic installation (Budget £1M complete by 5/2010) ;
Transmission equipments Budget £500K complete by 12/2010;
Television and Media suite….etc.
1.2 Stakeholder identification and needs
• List who is involved in your project. There should be at least a dozen
parties. E.g. Suppliers, project managers, consultants, surveyors etc.
• Your project will interface with other projects. List these projects and
include a brief description of what the interaction entails for each. E.g.
“The network infrastructure project interfaces with a number of utility
projects for cable laying. These are water, electricity, ….etc” (include a
one line description for each). Use a diagram to aid clarity.
1.2 System requirements breakdown and standards conformance.
• Requirements should be a numbered table of the requirements grouped
in terms of Mandatory, Preference and Operational. Each requirement
should have a brief textual description. You should aim for
approximately 20 requirements of each type. Ensure that the level of
detail of the requirements is consistent.
Section 2 – Project Management (40%)
2.1 Project Process Model
• Describe your key project processes by adapting those described in
CMMI. Use the standard notation for process diagrams given in the
notes.
2.2 Work breakdown structure
&