CS6003 Advanced Software Engineering Project Plan

This document outlines the requirements for a project plan report for the CS6003 Advanced Software Engineering course. Students are tasked with creating a project plan as a Senior Software Engineer for a fictional company, focusing on scope, time, and human resource management. The report must include generic plan information, a project overview, team structure, risk and quality management strategies, a Work Breakdown Structure (WBS), and a Gantt chart. The report should adhere to the SE documentation template and follow IEEE 12207.1 standards. The marking scheme emphasizes the content of the report body, including the WBS, Gantt chart, and milestones, as well as adherence to the documentation template.

CS6003 – Advanced Software Engineering COURSEWORK PART 2
SUBMISSION DEADLINE: week 26 Tuesday (2nd May 2017)
1. The Task of part 2 of the Coursework
This part of your Coursework is to write a Project Plan Report1, prepared with MS Word (your
file must be submitted in a MS Word 2007/2010 format).
The form and structure of the Report must correspond to the SE documentation template
2. Task Description
You are a Senior Software Engineer in Best Software Ltd. Your company specialises mainly in
development of mid-size software products.
Your company is involved in development of a Bloemendhal City Campus. (see the scenario
attached called scenario).
In this Part, you are playing the role of the project manager and do some Scope Management,
Time Management, and Human Resource Management tasks for your software project. You shall
do the following:
1) Write Generic Report (Plan) Information (page 12 of IEEE 12207.1):
a) Date of issue and status;
b) Issuing organisation;
c) Glossary
2) Write an Overview (Project Summary) for your software project.
2) 'Hand-pick' your team. The team consists of you, three full-time members and three people
working not more than 25% of their time. You, as the project manager, shall take part in
Project Process (see ISO 12207-2008) activities only (that is definitely part-time, <= 25%)
and cannot take part in any Software Implementation Processes. Full-time people may be
used in Software Implementation Processes activities mainly; part-time people may be used
in any process. If you find that '25%-people' cannot cover all support and other processes,
give an explanation why and give estimation what load should be put on part-time workers.2
You earn £30 per hour. Two members of your team and a part-time member earn £35 per
hour and others earn £25 per hour.
In your plan, give a short description of each member of your team: name, background,
specialisation, salary, etc.
Plan your project for three months (11 weeks) to complete; it will cost £80,000. This
amount of money is the salary of your team only; there is no need to plan other expenses.
4) Describe organisational structure (as a chart + an explanation) of your team and give a
budget summary.
5) Present the project risk management and software quality management strategies.
6) Develop a Work Breakdown Structure (WBS) for your software project and schedule the
Project. The WBS must be based on the ISO 12207-2008 tasks, activities, and
processes.
1 Suggestion: using MS Project to develop the project planning.

In addition to your WBS, allocate members of your team to the project tasks and develop a
Gantt chart. Do not forget to include all Project and Software Support Processes in your
Gantt chart.
All software product names in your Report must correspond to ones from IEEE 12207.1-1997.
The Criteria (Marking Scheme)
Component Marks
1. Contents of this Report Body: (90%)
1) Generic plan information for managing the project:
a) Date of issue and status; b)Issuing organisation;
c) Glossary
5%
2) Overview (Project summary):
a) Purpose, scope, and objectives; b) Assumptions and constraints;
c) Project deliverables; d) Schedule and budget summary.
15%
3) Project organisational structure:
a) Description of the team structure,
b) Identification of team member responsibilities for software processes,
activities and tasks;
15%
4) Present the project risk management and software quality
management strategies. 10%
5) Work breakdown structure (WBS):
a) WBS itself as a set of tasks of ISO 12207-2008 processes;
b) Rationale for this WBS (with explanations for particular pieces of
work on your particular software products corresponding to Part 1
and IEEE 12207.1)
c) Gantt chart (with corresponding explanation)
d) Milestones that can be assessed using objective indicators to evaluate
the scope and quality of work products completed at those milestones
e) Rationale for this set of milestones
( 45%)
12%
13%
10%
4%
6%
2. Correspondence to SE documentation template:
Cover page, Table of contents, Introduction, Format of references, Format of
glossary, Format of illustrations, Format of body text, Structure of the
document, Page format
10%
Total 100%