Software Engineering Project Proposal Support Notes 2009-10 V1.0

Project Proposal Support Notes

(Software Engineering Version)

Related Post

6BU020+Assessment+Brief++202425

June 9, 2025

Individual Assignment Rubrics V1 (1)

June 9, 2025

Individual Case Assignment Brief V11 (1)

June 9, 2025

Individual Assignment Rubrics V1 (1)

June 9, 2025

Introduction

The following notes supplement the material provided in the dissertation support lectures (by Iain Craig) providing additional specific pointers for SE students.

The first project deliverable (e.g. the abstract) provided a brief synopsis of your proposed project.

The project proposal should expand upon the ideas outlined in the abstract and give the reader a more detailed account of the project problem and the steps that you will be undertaking in order to achieve meaningful project problem resolution

A typical Software Engineering proposal should include the following essential content :-

■ Title Page

■ Contents Page

■ The Report Body (with several key sub-sections)

■ Bibliography/References

■ Appendix 1 – Project Gantt Chart

■ Additional Appendices (Where appropriate)

The following sections will examine each of these essential components

1) Title Page

The proposal title page should include the following information

a) Title

b) Name

c) Degree Title

d) Year

e) University Name

A good example can be found in Appendix A

2) Contents Page

The contents page should provide a clearly labelled list of the sections (and sub-sections) with page numbers, for each part of the proposal.

A good example can be found in Appendix B

3) The Report Body

The report body will likely include the following essential sections and content, as illustrated in Table 1.1 – Typical Proposal Body Content.

Table 1.1 – Typical Proposal Body Content

4) References

All references sited in your proposal should be refernced in this section.

The Harvard reference style should be employed throughout the work. (See additional notes available on NILE)

5) Appendix 1 – Project Plan Gantt Chart

A Project Plan Gantt Chart should be submitted as the first appendix to your proposal. It should list all project milestones and deliverables and establish a clear timescale for the work to be completed.

6) Additional Appendices

Additional appendices can be included for other relevant subject/topics.

Common appendices included with proposals include, provisional system specifciation and designs.

Appendix A – Example Proposal Title Page

CSY 4010 Computing Dissertation

Project Proposal

A STRATEGY FOR THE EFFECTIVE SCHEDULING OF UNSOCIABLE OPENING HOURS FOR DUTY CHEMIST SHOPS

By

Simon James-Jones

A proposal submitted in partial fulfillment of the requirements for the degree of

Bsc Computing (Software Engineering)

The University Northampton

2007

Appendix B – Example Proposal Contents Page

Contents

1 Background 1 2 Project Rationale 2 3 Project Aims and Objectives 3 4 Research Methodology 4

4.1 Research Activity Overview 5 4.2 Problem Domain Investigation 6 4.3 Requirements Engineering 7 4.4 System Analysis and Design 8 4.5 System Construction Strategy 9 4.6 System Test Strategy 10

4.7 System Evaluation Strategy 11 5 Ethical/Legal Considerations 12 6 References 13 Appendix

Appendix 1 – Project Plan Gantt Chart 15 Appendix 2 – Provisional System Specification 16 Appendix 3 – Provisional System Designs 17

Appendix C- Example Project Aims and Objects

With the design, development and evaluation of the Dyslexics User’s Interface Support Tool (DUIST) framework representing the fundamental objective of the proposed research, the identification of implicit research goals is appropriate. These research goals include: –

1) Identification of the design limitations of conventionally built interfaces for dyslexic users.

2) The formulation of a set of design principles for the effective construction of interfaces for dyslexic users.

3) An examination of emergent interface technology, including adaptive interface techniques, for evaluation and possible utilisation within the DUIST framework.

4) The formulation of a strategy to facilitate framework portability, for derived interface modifications

5) The design of suitable underlying models of dyslexia symptoms and interface specific symptom alleviation strategies.

6) The derivation of a suitable strategy for interface performance evaluation.

7) The development of a robust, reliable, user-friendly software environment to support dyslexic computer users and facilitate the evaluation of the performance impact of the previously formulated embedded system models

Appendix D- Example Project Gantt Chart