LEVEL 5
BUSINESS IT PROJECT
Project Guidelines
1. Scope
This is an individual project that should cover, in detail, the analysis, design coding and testing
of a project as outlined in the learning outcomes for the module. It should also give an overview
of the approaches used for project management, configuration management and risk analysis.
2. The Project Proposal
The proposal is a blueprint for your project. The purpose of the proposal is to put forward your
ideas about the project and allow your supervisor to judge whether the project is viable. The
project proposal should be between 3 and 5 pages in length and include the following sections:
2.1 An overview of the computing artefact to be designed
What type of computing artefact you are going to produce? Why it is important to
produce the computing artefact? What are the project aims and objectives?
For example: ‘The computing artefact to be designed is an Information System because
… A small firm currently maintains its records in paper based form. This is inefficient for
the following reasons ... The solution will reduce overheads such as ... It will potentially
allow savings of £xxx per year and open up the following business opportunities ... The
aims of the project are … The objectives of the project are …’
2.2 The aims, objectives and scope
What are you going to design? What features will and will not be developed?
For example: ‘The system will automate the following transactions ... It will provide an
online Help system supporting the following features ... It will provide a user guide,
focusing on the following ... It will not incorporate the following … because ... It will be
developed in Java Version X and MySQL Version Y, to run on the following platforms ...’
2.3 Work Breakdown Structure and Gantt chart
This section needs to provide a breakdown of the main tasks and activities that you will
need to undertake for the successful completion of your project. Indicate the key
milestones with dates. It is suggested that you use a tool such as Microsoft Project for
producing this information.
The project will not proceed until the plan is approved by your supervisor.
3. The Project Report
Your project report is an account of the work done in terms of the development of the
computing artefact. It is important that you plan the report to effectively communicate with the
people reading it. This means producing a report that your supervisor will enjoy reading. The
project report should be a well-structured word processed document that is easy to read. The
project report should be 6000 (+/- 500) words in length. The precise structure of the project
report is presented below:
3.1 Title Page
This section should contain the following centred information:
The full title of the project
The full name of the author, followed by the student registration number in brackets
The centre at which the author is studying
3.2 Abstract
This section should consist of a synopsis of the project (150-200 words) stating the nature and
scope of the work undertaken, and a concise summary of the outcomes.
3.3 Contents Page
This section should show the page numbers of chapters, sections and sub-sections, a list of
figures and tables, and a list of appendices.
3.4 Acknowledgements
This section is optional, but you may wish to pay tribute to particular people who have given
you special assistance or support.
3.5 Introduction
This chapter provides the context of your work in terms of:
Background to the system
The design that emerged
The main aims and objectives of the project
A short overview of the remaining chapters
Further guidance with respect to the content of this chapter is provided in Topic 5.
3.6 Background
This chapter locates your work in the relevant academic and other literature. For example, if
your project involves designing a web site, you will need briefly to describe the main features of
web technology, and discuss its benefits in terms of information provision, efficiency gains, etc.
You will need to relate this material to the particular problem you are addressing and discuss
specific alternative solutions that might apply. This applies to any techniques, technology or
tools not described elsewhere in the report. Also, you should overview the method or
framework used to design your system and justify its use in your project.
3.7 Analysis
This chapter consists of the analysis specification of the proposed system in terms of:
Requirements
Use Cases
Further guidance with respect to the content of this chapter is provided in Topic 2.
3.8 Design
This chapter consists of the design specification for the proposed system in terms of:
Structural Model
Behavioural Model
Further guidance with respect to the content of this chapter is provided in Topic 3.
3.9 Other Project Matters
This chapter provides an account of your approach to project management and evaluation. You
need to describe what particular techniques you have used, why you have used these rather
than others, and present a summary of your main results.
Further guidance with respect to project management is provided in Topic 1, whilst Topic 4
provides further guidance with respect to testing.
3.10 Conclusion
This chapter evaluates the substantive aspects of your work, within the context you have
established in the Introduction. It also comments on the extent to which the original aims and
objectives have been met.
Further guidance with respect to the content of this chapter is provided in Topic 5.
3.11 References
All references you cite within the body of your report should be fully referenced in this section,
using the Harvard Style. No reference should appear here unless it has been cited in the body
of the report.
3.12 Appendices
Appendices may include any supporting material a reader might wish to refer to, but which is
not essential for the main body of the report. Appendices for the project may include some, or
all, of the following:
Requirements Catalogue
Use Case Descriptions
Detailed Class Definitions
Evaluation
External Client Documents where applicable (see Section 4 below)
4. The Project Presentation
Following completion of your project report, you will have 20 minutes to give a presentation
about the content of the business IT project. The presentation will be assessed and contribute
to your final mark.
The 20 minutes will be structured as follows:
Presentation (15 minutes)
Questions related to the presentation (5 minutes)
The presentation should contain between 10 and 15 slides and should be structured as follows:
An overview of the context/background of the project
An overview of the analysis and design activities (high level model of the system,
techniques used, key design decisions)
An overview of the evaluation (techniques, a summary results, conclusions)
A critique of the process (what went well, what didn't, what you have learned, what you
would do differently next time)
PC and projection equipment will be available, so it is expected that you will give a PowerPoint
presentation. The audience for the session will be your supervisor plus one other tutor.
5. Notes on Working with External Clients
You are not required to work with an external client to develop your project. However, if you are
working with an external client the following must be included in an appendix:
A letter of introduction from the Accredited Partner Centre to support the student.
A memorandum of understanding (MOU) between the student and client. This document is
typically prepared soon after a client has been chosen. Its purpose is to formally establish
the specific details of the project work with the intention of protecting both the client and the
student. It should cover:
- A specification of the system project, including expected functionality, timeline, and
resources to be committed.
- Confidentiality of documents which may be passed from client to student.
- Liabilities of student to client in case of failure to deliver a working product.
- Financial compensation or remuneration. The MOU should make clear that the
student is not to be paid for any project work undertaken.
