Coursework Project: Proposal, Plan, Risk Analysis, SRS Document, Process Model, Design, Estimation,

Part 1: Proposal and Project Plan

Part 1 Details:
Your group must first choose a project title and prepare a proposal to specify the project aim and objectives. An important part of the proposal is to ensure feasibility of the project given the specified project timescales therefore some research into the chosen project topic will be
required. Note that the project should lead to some form of tangible results, product or deliverable that can be used or applied in some way.

Your project plan is to be prepared by your group and will be assessed on the quality of the documentation you produce. Your group documentation should consist of a proposal, project plan (a work breakdown structure, PERT and Gantt charts), a QA plan, and a record of your group meetings to show your teamwork.

 

Additionally, each team member must produce a report of their individual contribution. One of the first things you will need to do as a group is deciding who does what. When you do this, bear in mind the marking scheme, and spread the workload evenly so that everyone is contributing
work that will be worth a fair share of the total marks. 

1. The Project Proposal
The project proposal can be written following the guidelines given on the selected system so you should include:

A rationale, aim and objectives for the project.
Adequate research and a literature review sufficient to define the project context and scope.
A process section to specify briefly how the project will be conducted and how the project objectives can be assessed.
A quality assurance section describing briefly how the specific project objectives and the quality of the deliverables can be assessed.
The resources required to complete the project. 

2. The Project Plan (Work Breakdown Structure, PERT and Gantt Charts)
The work breakdown structure for each group project will define the specific development activities required. These activities can be product oriented or can divide into technical, quality and management activities. The work breakdown structure can form a framework for the project schedule. The PERT and Gantt Charts can be drawn by hand or electronically (e.g. Visio or Word) or Microsoft Project can be used. On the PERT chart ensure that milestones are indicated and critical path/s clearly indicated. 

3. Quality Assurance Plan
Your project specification should include the validation procedures required to ensure that the project objectives and quality criteria have been met. For example, this could include software testing on a software development project.

1. The Project Proposal

4. Teamwork Report and Minutes of Group Meetings
Undertaking this group assignment effectively will require good teamwork and cooperation. Group meetings should be held regularly and documented to record development decisions, progress, and delegation of tasks and updating of team members. These meetings can best be recorded chronologically. The teamwork report should also explain the roles and responsibilities of the individual team members. 

 

Marking Scheme
Project Proposal 
Project Plan: WBS, PERT and Gantt Charts
Quality Assurance Plan

 

Part 2: Risk Analysis, SRS document, Process Model, Design and Estimation [60%]

Inroductions:
The task in this group coursework is to provide a risk management plan with relevant risk factors,System Requirements Specification, process model, design, estimations and testing for the System you chose. Marks will be awarded for overall achievement, teamwork cooperation and
group effort but marks for individuals within a group may vary according to individual contribution, effort and achievement. State which group members did each task (use student numbers not names). If no participants are stated, then marks will be evenly split. 

 

Part 2 Details:

Your report is to be prepared by your group and will be assessed on the quality of the documentation you produce. Your group documentation should consist of a risk analysis, a process model, design, an estimate and testing. One of the first things you will need to do as a group is deciding who does what. When you do this, bear in mind the marking scheme, and spread the workload evenly so that everyone is contributing work that will be worth a fair share of the total marks. 

 

1. Risk Management Plan
You are required to produce a risk management plan for this project. Identify the major risks to achieving success on this project. Group members should identify risks and prepare an argument as to why this is a major risk and how you propose to minimize it for this project. For each risk you should specify contingency arrangements and show the effect on timescales on your project plan. Your report must cover the following:

 

Description of the risk – what is the risk? How is it related to this project?
Give appropriate justification for the selection of the risk.
Likely impact of the risk on the project if it is not dealt with.
Risk management – a description of the process you will use for managing the risk.
Describe the research study conducted to investigate this risk analysis. 

2. System Requirements Specification
You are required to describe the need for the system, a brief description of the system’s functions and how it will work, similar systems and overlapping functionality. Provid details on the method used to elicit the requirements and how you applied this method,
the User requirements definition, and the services provided for the user, the functional and non-functional requirements.

 

3. Process Model
It is important to choose an appropriate process model for the proposed project. Selection should be based on the analysis of the proposed development approach and should include discussing the pros and cons of adopting different processes. You should provide appropriate reasoning to justify why one process is preferred over others.

 

4. Design of the System
The modelling and mock-up document should include context, interaction, structural, and behavioral models of your system together with mock-ups of the system’s User Interface 

 

5. Estimation
Estimate the time duration and effort required for your project. Choose a method such as the Intermediate COCOMO method, the function point method or a combination of methods and clearly state any assumptions you make.

6. Testing
The testing documentation includes details on the design, execution, and result of the testing process run on the system developed. 

 

Marking Scheme
Risk Analysis
System Requirements Specification
Process Model
Design
Estimation
Testing

 

Part 3: Presentation [20%] 

Introductions:

The task in this coursework is to present the project proposal, project plan, QA plan, risk management plan, process model, design, estimates and Prototype demo you prepared for parts 1 and 2. Presentations will be scheduled according to the groups to which you have been
allocated. You should be well prepared and able to answer any question related to the contents of the presentation. 

Part 3 Details:

The presentation contents should be appropriate and related to the project. They should also be informative giving a clear sense of knowledge being applied. The presentation should be properly structured with clear introduction, main contents and conclusion. The delivery of the
presentation should also be clear.

 

Each group will have approximately 15 minutes to give the presentation. Each member of the group is required to contribute to the group presentation and to answer questions. As a group you must decide who does what.

In your presentation you should support your arguments with evidence and references to good practice in project management. 

Marking Scheme
Contents
Presentation Style and Timekeeping
Individual Effort and Answer