Guidelines for final students: project reports

PROJECT WORK METHODOLOGY

FOR BCA SEMSTER VI STUDENTS

Objective

1. Students of Semester VI are to carry out a software project as part of curriculum of BCA.
At the end of the semester the students are to submit a written project report to be forwarded to
Dr BRAmbedkar University. The objective of this Teaching Note is to standardise the format of
submission of the project report and to lay guidelines to conduct the project.

University Scheme for Project

2. As per the syllabi of BCA (Paper No BCA-501611), students of Semester VI are to write
a dissertation/project report. The dissertation/project report has two components, viz.

(a) External : Dissertation where a written report is to be

Submitted. It involves external Viva and presentation.

(b) Internal : Dissertation it involves Viva and presentation

Scope of the Dissertation

3. It is partly responsibility of the student to find a relevant topic for his/her term
dissertation. If you are involved in research or development in this area, your dissertation can
relate to your work as long as your work can be public. The dissertation is to study the selected
problem and quality & shortcomings of available solutions. In the report, you must also include
any new solution you can think of and general comments on why the problem is important.

4. The dissertation work could be based on, simulation study, or implementation. You are
allowed to perform original work, if you so desire.

Final Report

6. The format of the project report is attached as Appendix ‘A’. The Guidelines for
methodology to be adopted for conducting the project is attached as Appendix ‘C’. The last
date of submission of the completed and bounded report is to be submitted as per the
schedule given below.

Important Dates
7. Following Schedule is to be adhered to by all the students:

To Be completed By the Date Progress/Activity

25th June Project Report submit

Appendix ‘A’

FORMAT OF THE PROJECT REPORT

Format

1. The final report should be written in the following the format:

(a) Title Page

(b) Certificate (s)
(c) Acknowledgements
(d) Synopsis/Executive Summary
(e) Contents
(f) List of Tables
(g) List of Figures
(h) List of Symbols
(j) Body of the Project Report
(k) Summary and Conclusions
(l) References
(m) Appendices

Title Page

2. The format of the title page is attached as Annexure-I.

Certificate

3. The format of the certificate is attached as Annexure-II. A certificate of the organisation

where the student has conducted the project may also be attached.

Acknowledgements

4. In the “Acknowledgements” page, the writer recognises his indebtedness for guidance
and assistance of the thesis adviser and other members of the faculty. Courtesy demands that he
also recognise specific contributions by other persons or institutions such as libraries and
research foundations. Acknowledgements should be expressed simply, tastefully, and tactfully
duly singed above the name.
Synopsis/Executive Summary

5. A synopsis is a brief or condensed summary of the project for higher-level management

positions. It should be about 3-4 pages in length. It should comprise problem definition,
objectives of the project, methodology and tools used, findings, limitations, directions for future
development, if any.
Contents & List of Tables/Figures/Symbols

6. The format of Contents and list of Tables/Figures/Symbols is attached as Annexure-III.

A publication is a research paper published/communicated during the current research work.

Body of the Project Report: Guidelines for Project Report/Dissertation Writing

7. The guidelines for Body of the Project Report (methodology) are detailed in Appendix
‘C’. Following aspects must be adhere to:

(a) Page Size: Good quality white A4 size executive bond paper should be used for
typing and duplication.

(b) Chapter/Para Numbering: The chapters are to be numbered as Chapter-1,

Chapter-2 etc. The heading/title of the chapter is to appear below the chapter number in
uppercase. Paragraphs are to be numbered as 1,2,3 etc in every chapter separately. Sub-
paras are to be numbered as 1.1, 1.2, 1.3----, 2.1, 2.2, 2.3-----etc. Sub-sub paras are to be
numbered as 1.11, 1.12, 1.13, 2.11, 2.12, 2.13 etc.

(c) Page Specifications:

(i) Left Margin : 1.25 inch

(ii) Right Margin : 1.25 inch
(iii) Top Margin : 1 inch
(iv) Bottom Margin : 1 inch

(d) Page Numbers: All text pages starting from Body of the Project Report as well
as program source code listings should be numbered at the bottom center of the pages.

(e) Normal Body Text:

(i) Font Size: 12, Times New Roman, Double Spacing, Single Side Writing.
(ii) Paragraphs Heading Font Size: 12, Times New Roman, Underlined
(iii) Page/Title Font Size: 14

(f) Table and Figure Number: Table and figure numbers are to be written at the
bottom of the table/ figure as given below:

(i) Table No-1: Number of Employees in Organisation ABC

 (ii) Figure No-1: Data Flow Diagram

(g) Binding & Color Code of the Report:

(i) Hard Bound Report

(ii) Background of the cover page - Navy Blue
(iii) Letters in Silver White
Summary & Conclusions

8. This section of the report/dissertation should cover findings of the work, whether the
stated objectives of the work is achieved with full justification, recommendations, limitations,
directions for future development.

References/Bibliography

9. Examples are given below:

1. D.L. Carney, J.I. Cochran, “The 5ESS Switching System: Architectural Overview,”
AT&T Technical Journal, vol. 64, no. 6, July-August 1985, pp. 1339-1356.

2. A. Stevens, C++ Database Development, MIS Press, New York, 1992, p. 34.

3. J. Martin, Computer Database Organization, Prentice-Hall, Englewood Cliffs, NJ,

1977, p. 53.

4. www.ibm.com/in

5. www.intel.com/india

Appendices

10. The appendices are to be attached at the end of the report/dissertation and to be numbered
as Appendix-A,. right justified at the top of the page. Below the world Appendix write in
parenthesis “Refer Para No__”. The para number is to be the number in the body of text where
the reference of appendix is given. An appendix may have annexure (s). If there are annexure,
there are to be attached immediately after the said appendix. The annexures are to be numbered
as Annexure-I, Annexure-II etc.
 Annexure-I

Title of The Project Report

(Font size = 18)

Submitted in partial fulfillment of the requirements

for the award of the degree of

Bachler of Computer Application (BCA)

To

Dr.BR Ambedkar, Agra

Logo of the
University

Guide(s): Submitted by:

(Guide Name) (Student name)
Roll No.:

Logo of the
Institute

Uttam Institute of Technology Management

Batch ( )
 Annexure-II

Certificate

I, Mr./Ms._______________________________, Roll No. ________________ certify that

the Project Report/Dissertation entitled “________________________________” is done by

me and it is an authentic work carried out by me at ___________________________ (Name

of the organisation or of the Institute). The matter embodied in this project work has not

been submitted earlier for the award of any degree or diploma to the best of my knowledge

and belief.

Signature of the Student

Date:

Certified that the Project Report/Dissertation entitled “__________________”

Done by Mr./Ms._______________________________, Roll No. ________________, is

completed under my guidance.

Signature of the Guide

Date:
Name of the Guide:
Countersigned Designation:
Address:
Uttam Institute of Technology
&Management, Agra

Director/HOD
 Annexure-III

FORMAT FOR CONTENTS & LIST OF TABLES/FIGURES/ SYMBOLS

CONTENTS

S No Topic Page No
1 Certificate (s) -
2 Acknowledgements -
3 Synopsis/Executive Summary -
4 List of Tables -
5 List of Figures -
6 List of Symbols -
7 Chapter-1: Introduction/Problem Definition
8 Chapter-2: Systems Analysis of Existing System
9 Chapter-3: Requirements Analysis
10 Summary and Conclusions
11 References
12 Appendices

LIST OF TABLES/LIST OF FIGURES

Similar tables (as shown above for Contents) are to be drawn for List of Tables and List
of Figures on separate pages.

LIST OF SYMBOLS
Symbols that are used in the body of the text are to be listed in tabular form as given
below:

S No Symbol Nomenclature & Meaning

1  Sigma (Summation)
2 kbps Kilo bits per second
 Appendix ‘C’

MEYHODOLOGY FOR PROJECT WORK/DISSERTATION

Chapter-1: Introduction/Problem Definition

1. Following aspects need to be covered in the first chapter:

(a) Brief Description of the Organisation: If the project work is being done outside
the Institute, describe the organisation, its nature of business, products, turnover, market
position etc.

(b) General Description of the System under Study: Briefly explain how the
existing information system achieving the task, which is under study.

(c) User Requirements: Explain in non-technical terms, why the existing

information system is not able to meet the current tasks against the
objectives/standards/benchmarks of the organisation. Problems faced by the existing
system.

(d) Establish the Need of the New System:

 Give justification, How & Why without the new system user requirements
cannot be fulfilled.
 How will the proposed solution enhance the efficiency, effectiveness, better
control, security and achievement of objectives/standards/benchmarks?

(e) Objectives of the Project: Keeping in view the user requirements and needs,
available time and expertise, lay down the objectives of the project. Clearly spell out
what is proposed to be done in the project.

(f) Methodology: SDLC, Structured Analysis & Design, Object Oriented Design
method or Prototype method. You may follow a mixed methodology and tools; however,
you should clearly mention the steps and tools and techniques that you are going to
follow in the current project with brief justification.

(g) Data Required & Data Collection Method: You should establish requirement
of data and methodology/technique of data collection, e.g., interview, questionnaire,
document analysis. If questionnaire is developed, attach a copy of the questionnaire as
appendix.
Chapter-2: Systems Requirement Analysis

2. In this chapter students are required to establish the user requirements by doing the
systems analysis of the existing system in vogue and by interacting with the management/staff of
the organisation. In every organisation a system does exist in some rudimentary or manual form,
if not computerised. The activities that are required to be carried out and to be described in the
project are:

(a) Identify the process (es).

(b) Identify the Input to and Output of each process, e.g., for Rail Reservation System
input is the form and output is a ticket.

(c) Identify the data elements (fields) in each input and output.

(d) Identify the procedures/rules/mathematical relationships used for converting input

into output.

(e) Identify the controls (for I/O & access), security needs, validation rules and codes
used for data elements.

(f) Identify deficiencies in existing system.

3. Having collected the data on the above aspects, analyse it and interact with the
management for any changes in process (es), input, output, procedures, access and control rights,
security needs and your suggestions for removing the deficiencies.

Chapter-3: Systems Design

4. Physical Design: Explain relationship between various components (processes, input,

output & entities) of the system. Draw DFDs and other diagrams.

5. Explain Processing Logic: Using Programme Flow Charts, Algorithm, Decision

Table/Tree or Pseudo codes.

6. Interface Design:

(a) Output Design: Screen & Print layouts, i.e., the format and contents (fields) to be
included – along with the file to which it is linked.

(b) Input (Form or Screen) Design: For keying-in data. Give fields, format, codes to be
used, validation (error detection) requirements & the file to which it is linked.
7. Database & File Design:

(a) Database Files/Tables Design: Depending on the DBMS/RDBMS package

used, give contents of each file including Field Name, Type, Size & Description.

(b) Programme Files or Query Design: Give purpose and detailed working of each
programme file or a Query and link it to the processing logic and Process/Input/Output.

(c) Compose Data Element Dictionary: List all the fields in all the files in
alphabetical order in a tabular form and serially numbered them.

Data FIELD TYPE& FIELD FILE PROCESS

Element NAME SIZE DESCRI NAME/No NAME/No
S No PTION

Chapter-4: Systems Development

8. Purpose: To carry out the activities of writing actual programmes, their debugging,
testing and validation. Following activities are to be carried out:

(a) Programme Development: Explain the language or package used for developing
the programmes (both back-end and front-end).

(b) Testing & Debugging: Use Past Data to check whether the programmes work as
intended by

(i) Module Testing: Individual programme testing.

(ii) System Testing: Integrated module Testing for the entire system.

(You may like to include the test reports in the project to show the errors, if any, and a
write-up on their rectification).

(c) Validation: Check the system with Real-time Data for input, output,
computational processing & controls.

9. Attach programme codes, input and output designs and outputs using the real data in this
chapter. Codes may be attached as appendix.

Chapter-5: Systems Implementation

10. Following activities are required to be conducted:

(a) Acquisition: Workout the memory requirement, disk space required for
programme (s) and database (s). List out HW, SW and people resources required and
indicate the cost of the system.
(b) Conversion: Suggest change over procedures (Parallel, Direct or Partial Change
over) with justification.

(c) Training Needs: Establish the training needs of operating personnel, clerical/non-
clerical staff, supervisors, and senior staff.

(d) Documentation:

(i) Include Operation Manual (instructions for running programmes).

(ii) User Manual-Giving instructions & procedures for end-users (for data
entry, output, help etc).