Project Plan Report for Software Engineering Course - Semester 1

This report presents a comprehensive project plan for a software engineering coursework assignment. It outlines the project's scope, time management, and human resource management strategies. The report includes a detailed overview of the project's context, team composition, and roles, along with salary information. It covers organizational structure, risk management, and software quality management strategies. A crucial component is the Work Breakdown Structure (WBS) based on ISO 12207-2008, accompanied by a Gantt chart that allocates team members to project tasks. The report also addresses software product names in accordance with IEEE 12207.1-1997 standards. This assignment is a valuable resource for students seeking to understand and implement effective project planning in software engineering.

1. The Task
This part of your Coursework is to write a Project Plan Report, 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 file
attached 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. 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.