<<Group Project Topic>>

A group project submitted for Higher National Diploma in Information Technology

Advanced Technological Institute <<Institute Name>>

<<Student Name>>

<<Registration No>>

<<Month , Year>>

1
Declaration

This report is my original work and has not been submitted previously for a Higher National
Diploma at this or any other university / Institute. To the best of my knowledge it does not
contain any material published or written by another person, except as acknowledged in the
text.

Signature of Candidate: . . . . . . . . . . . . . . . . . . . . . . .

Date:..../....../….....

Name of Candidate: . . . . . . . . . . . . . . . . . . . . . . . . . . .

Countersigned by:

Signature of Supervisor(s)/Advisor(s): . . . . . . . . . . . . . . . . . . . . .

Date:..../....../….....

Name(s) of Supervisor(s)/Advisor(s): . . . . . . . . . . . . . . . . . . . . . . . . . . .”

2
Acknowledgement

It is mandatory that a candidate thanks whoever has helped him technically or otherwise,

during the project. Your supervisor and your client will obviously be pleased to be

acknowledged as they would have invested a quite a lot of time overseeing your progress.

Acknowledgements should be brief and to the point and should not exceed one page.

3
Chapter 1 – Introduction

This chapter describes the motivation for the project, brief discussion about the topic you have
selected, aims, objectives and scope of the project. This chapter should have a outline of the other
chapters available in this document.

Chapter 2 – Analysis

you can review two or three existing software systems or manual systems which is similar to the
proposed system. The review should clearly describe the functions which can be used for the
proposed system and the functions which cannot used for the proposed system.

What ever the refered contents should be cited at the reference section of the system [Link]
analysis of the requirements should also be provided in this chapter. For example, the

requirements of the system could be listed. A specification of the number of users, the

frequency of use, and the jobs of the users could be provided. The development method and the
model used should be clearly justified in this seciton.

Chapter 3 – Design

In this chapter design strategies for the system is described.(developing from beginning or using
some API or Open source components) Standalone or Client server environment and operating
system for the software is selected.

The architectural design of the proposed system is described in this chapter. This chapter includes
use case diagrams and use case narratives, class diagrams, sequence diagrams, etc. What ever the
diagrams , tables and figures should be referred with correct numbering. User Interfaces and the
design justifications made for the interfaces should be mentioned.

Chapter 4 – Implementation

Code structure and the modules of the system should be identified in this chapter. Chapter should
explain hardware and software environment existing code resuin , development tools should be
explained under this section.

If some reused code is used for your project user should clearly acknowledge for the authors of the
code.

Chapter 5 – Evaluation

This chapter should prove that proper testing of system was done. For this purpose, a

comprehensive test plan that was used to verify and validate the system should be

4
provided. This section should clearly mention how much of testing is done for the software system
you created.

Chapter 6 – Conclusion

This chapter will conclude the dissertation with a critical evaluation of the system and

suggestions for any future work. The evaluation should include a critical discussion and

assessment of results of project. This chapter should discuss whether the project objectives

were satisfied and if not, the reasons for them.

Lessons learnt during the course of the project should also be expanded upon. It is

important that any failures to achieve given objectives should be discussed and analyzed.

References

It is very important to acknowledge any of the work of others that the candidate used or

adapted in the project.

Example 1:

[6] J.L. Whitten and L.D. Bentley, Systems Analysis and Design Methods, 7th ed. Tata

McGraw-Hill, 2007.

Appendices

The appendices include further information that is not essential to be included in the

project report.

Appendix A - System Manual

Technical documentation is included under this section. This provides program installation,
compilation and execution details of your project.

Appendix B - Design Documentation

Design documents which cannot be included in main project report can be included under this
section. Ex: DFD or any other design diagrams.

5
Appendix C - User Manual

Technical documentation used by the end users. Each and every system should have a technical
documentataion.

Appendix D - Management Reports

The reports generated by the systems should be included in this section. The usability of the system
can be measured by using these reports.

Appendix E – Test Results

Test plan of the system should be provided in tabular format. The verified or validated data should be
attached.

Appendix F - Client Certificate

Letter given by the client describing the fulfillment of the software with respect to clients
requirements. The letter should be signed by at least a head of the sectional head.