This action might not be possible to undo. Are you sure you want to continue?
Guidelines for Project Report/Dissertation Writing
The guidelines for Body of the Project Report (methodology) are to be adhered 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. Sub-headings within a chapter are to be numbered as 1.1, 1.2, 1.3----, 2.1, 2.2, 2.3-----etc. Sub-sub headings are to be numbered as 1.1.1, 1.1.2, 1.1.3, 2.1.1, 2.1.2, 2.1.3 etc. (c) Page Specifications: (i) (ii) (iii) (iv) Left Margin Right Margin Top Margin Bottom Margin : 1.25 inch : 1.25 inch : 1 inch : 1 inch
(d) Page Numbers: All pages begore the chapter-1 to be numbered in small roman numerals I, ii, iii, iv, v, vi, …. All text pages starting from Body (chapter-1) of the Project Report as well as program source code listings should be numbered in decimal digits as 1, 2,, 3, 4 …. 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, Bold (iii) Major Headings: Font Size: 14, Bold (iv) Chapter Headings: Font size 16, Bold (f) Table and Figure Number: Table and figure numbers are to be written at the bottom of the table/ figure as given below: (i) (ii) (g) Table No-1: Number of Employees in Organisation ABC Figure No-1: Data Flow Diagram
Binding & Color Code of the Report:
Project Report Format (i) (ii) (iii) Hard Bound Report Background of the cover page .Navy Blue Letters in Silver White 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 consisting of Chapters (chapter contents given at end) Chapter – 1: INTRODUCTION/PROBLEM DEFINITION Chapter – 2: SYSTEMS REQUIREMENT ANALYSIS Chapter – 3: SYSTEMS DESIGN Chapter – 4: SYSTEMS DEVELOPMENT Chapter – 5: SYSTEMS IMPLEMENTATION Chapter – 6: Summary and Conclusions Chapter – 7: Limitations of the Project Chapter – 8: Future Directions Chapter – 9: References Chapter – 10: Appendices .
: .Project Report Format Title of The Project Report (Font size = 18) Submitted in partial organization of the requirements for the award of the degree of Master of Computer Application (MCA) to Guru Gobind Singh Indraprastha University. Delhi Supervisor: (Guide Name) name) Designation Submitted by: (Student Roll No.
Project Report Format Banarsidas Chandiwala Institute of Information Technology. New Delhi – 110019 Batch (2004-2007) .
(Signature) Student Name . tastefully. and tactfully duly singed above the name. Acknowledgements should be expressed simply. the writer recognises his indebtedness for guidance and assistance of the thesis adviser and other members of the faculty.Project Report Format ACKNOWLEDGEMENT In the “Acknowledgements” page. Courtesy demands that he also recognise specific contributions by other persons or institutions such as libraries and research foundations.
/Ms. Countersigned Signature of the Guide Date: Name of the Guide: . 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. Roll No._______________________________./Ms.Project Report Format CERTIFICATE A certificate of the organisation where the student has conducted the project may also be attached._______________________________. ________________ certify that the Project Report/Dissertation (MCA-302) entitled “________________________________” is done by me and it is an authentic work carried out by me at ___________________________ (Name of the 6rganization or of the Institute). ________________. Roll No. is completed under my guidance. This certificate would be additional to attached certificate I. Signature of the Student Date: Certified that the Project Report/Dissertation (MCA-331) entitled _________________” done by Mr. Mr.
methodology and tools used. findings. objectives of the project. BCIIT Director /HOD. . BCIIT SYNOPSIS/PROJECT PROPOSAL A synopsis is a brief or condensed summary of the project for higher-level management positions. It should comprise problem definition. It should be about 3-4 pages in length. directions for future development. if any.Project Report Format Designation: Assistant Professor. limitations.
. Chapter-2: Systems Analysis of Existing System . . . . . Chapter-3: Requirements Analysis . . . Chapter.Project Report Format CONTENTS S No 1 2 3 4 5 6 7 Topic Certificate (s) Acknowledgements Synopsis/Executive Summary List of Tables List of Figures List of Symbols Chapter-1: Introduction/Problem Definition . Summary and Conclusions Limitations of the Project Future Direction References Appendices Page No i ii iii 1 8 9 . .
Project Report Format 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 1 2 Symbol Σ kbps Nomenclature & Meaning Sigma (Summation) Kilo bits per second .
. better control. you should clearly mention the steps and tools and techniques that you are going to follow in the current project with brief justification. You may follow a mixed methodology and tools. which is under study.g. Clearly spell out what is proposed to be done in the project. Problems faced by the existing system. its nature of business. market position etc. questionnaire. why the existing information system is not able to meet the current tasks against the objectives/standards/benchmarks of the organisation. effectiveness. . security and achievement of objectives/standards/benchmarks? (e) Objectives of the Project: Keeping in view the user requirements and needs. turnover. lay down the objectives of the project. available time and expertise. e. Object Oriented Design method or Prototype method. however. products. Structured Analysis & Design. (g) Data Required & Data Collection Method: You should establish requirement of data and methodology/technique of data collection. (f) Methodology: SDLC. How & Why without the new system user requirements cannot be fulfilled. (c) User Requirements: Explain in non-technical terms. describe the organisation.Project Report Format CHAPTER-1: INTRODUCTION/PROBLEM DEFINITION 1. attach a copy of the questionnaire as appendix. (b) General Description of the System under Study: Briefly explain how the existing information system achieving the task. How will the proposed solution enhance the efficiency. (d) Establish the Need of the New System: (i) (ii) Give justification. 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. document analysis. If questionnaire is developed. interview.
Decision Table/Tree or Pseudo codes. input. security needs and your suggestions for removing the deficiencies. CHAPTER-3: SYSTEMS DESIGN 4. codes to be used. access and control rights. validation (error detection) requirements & the file to which it is linked. analyse it and interact with the management for any changes in process (es).. . (f) Identify deficiencies in existing system. Draw DFDs and other diagrams..g. (d) Identify the procedures/rules/mathematical relationships used for converting input into output. 6. In every organisation a system does exist in some rudimentary or manual form. if not computerised. (b) Input (Form or Screen) Design: For keying-in data. 3. i. The activities that are required to be carried out and to be described in the project are: (a) Identify the process (es). security needs. format. Having collected the data on the above aspects. validation rules and codes used for data elements. Give fields. 5. Interface Design: (a) Output Design: Screen & Print layouts. output. procedures. output & entities) of the system. Physical Design: Explain relationship between various components (processes. input. e.e. (e) Identify the controls (for I/O & access). (c) Identify the data elements (fields) in each input and output. the format and contents (fields) to be included – along with the file to which it is linked. for Rail Reservation System input is the form and output is a ticket. Explain Processing Logic: Using Programme Flow Charts. Algorithm. (b) Identify the Input to and Output of each process. 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.Project Report Format CHAPTER-2: SYSTEMS REQUIREMENT ANALYSIS 2.
(You may like to include the test reports in the project to show the errors. and a write-up on their rectification). Data Element S No FIELD NAME TYPE& SIZE FIELD DESCRI PTION FILE NAME/No PROCESS NAME/No CHAPTER-4: SYSTEMS DEVELOPMENT 8. (c) Validation: Check the system with Real-time Data for input. Purpose: To carry out the activities of writing actual programmes. Codes may be attached as appendix. computational processing & controls. testing and validation. input and output designs and outputs using the real data in this chapter. Attach programme codes. (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. their debugging. System Testing: Integrated module Testing for the entire system.Project Report Format 7. (b) Testing & Debugging: Use Past Data to check whether the programmes work as intended by (i) (ii) Module Testing: Individual programme testing. Type. 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). Database & File Design: (a) Database Files/Tables Design: Depending on the DBMS/RDBMS package used. Size & Description. give contents of each file including Field Name. 9. output. if any. .
. and senior staff. output. clerical/nonclerical staff. (b) Conversion: Suggest change over procedures (Parallel. Following activities are required to be conducted: (a) Acquisition: Workout the memory requirement. help etc). List out HW. (ii) User Manual-Giving instructions & procedures for end-users (for data entry. Direct or Partial Change over) with justification.Project Report Format CHAPTER-5: SYSTEMS IMPLEMENTATION 10. (c) Training Needs: Establish the training needs of operating personnel. supervisors. disk space required for programme (s) and database (s). (d) Documentation: (i) Include Operation Manual (instructions for running programmes). SW and people resources required and indicate the cost of the system.
etc. 8. limitations.Project Report Format 6. These limitations could be the assumptions on which the project is based or some work which could not be implemented. usability. directions for future development. 7. FUTURE DIRECTIONS The future work which could be carried on this project to enhance its functionality. LIMITATIONS OF THE PROJECT Highlight the limitations of the current project developed. . security. SUMMARY & CONCLUSIONS 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.
NJ. Stevens. 53. p. 10. J. New York. 5. “The 5ESS Switching System: Architectural Overview.com/india 2. July-August 1985. right justified at the top of the page. vol.Project Report Format 9. If there are annexure. 1992. Martin. pp. The annexures are to be numbered as Annexure-I. A. p. 64.com/in www. there are to be attached immediately after the said appendix.L. Below the world Appendix write in parenthesis “Refer Para No__”. no. An appendix may have annexure (s). 4. Annexure-II etc.intel. C++ Database Development. Prentice-Hall. Englewood Cliffs. 1977. REFERENCES/BIBLIOGRAPHY Examples are given below: 1. 1339-1356. 3. . 34. Carney. APPENDICES The appendices are to be attached at the end of the report/dissertation and to be numbered as Appendix-A. Appendix-B etc.I. MIS Press. J.ibm. D. www. The para number is to be the number in the body of text where the reference of appendix is given. Cochran.” AT&T Technical Journal. Computer Database Organization. 6.