Scribd
Upload
12 views

Documentation of Project

The document provides guidelines for formatting and structuring a project documentation report. It outlines the expected content and formatting for each page or section, including the title page, table of contents, abstract, introduction, existing and proposed systems, requirements, methodology, analysis, design, coding, testing, implementation, maintenance, future enhancement, conclusion, acknowledgements, and references sections.

Uploaded by

kavyanjalv0218.sse
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
12 views

Documentation of Project

The document provides guidelines for formatting and structuring a project documentation report. It outlines the expected content and formatting for each page or section, including the title page, table of contents, abstract, introduction, existing and proposed systems, requirements, methodology, analysis, design, coding, testing, implementation, maintenance, future enhancement, conclusion, acknowledgements, and references sections.

Uploaded by

kavyanjalv0218.sse
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

DOCUMENTATION OF PROJECT

Page 1: Label page

TITLE NAME : Font name: Times new roman

Font size 24

Page 2: BONAFIDE CERTIFICATE

HEADING: sentence case format

Font size 20

Bold

Font name: IMPRINT MT SHADOW

Content: font size 20

No bold

Font name: IMPRINT MT SHADOW

Page 3: Table Of Contents

Heading: Font name: times new roman

Bold

Font size 14

Content: Font name: times new roman

No bold

Font size 12

Page 4: Abstract

Heading: Left align

Small caps

Font name: times new roman

Font size 14

Bold
CONTENT: should contain 8 lines

Font name: times new roman

font size 10

Without any gap involve 5 Keywords for your project.

Keywords: Heading: font name: times new roman

Font size:10

Bold and italics

Content: Font name: times new roman

Font size: 10

 AFTER ABSTRACT ALL HEADINGS SHOULD BE WRITTEN IN MIDDLE WITH ROMAN


NUMBER OF FONT TIMES NEW ROMAN WITH FONT SIZE 14 AND CENTRE ALIGNED,
BOLD.

Page 5: Introduction:

Content: font name: times new roman

Font size:12

It should contain 4 paragraphs 1st paragraph should contain about general things what is your
project in 5 lines and 2nd paragraph should contain why it is needed (5 lines) and 3 rd paragraph
should contain of how you are going to do this project(5lines) and final paragraph must contain
advantages of your project and where and how it is used(5lines).

Page 6: Existing System

It should contain two paragraphs. 1st paragraph must discuss about current existing system in 5
lines and 2nd paragraph should explain about what is problem with existing system in 6 lines.

Page 7: proposed System

It should contain 2 paragraphs. 1st paragraph must contain about how you are going to overcome
the problems and challenges that are found in existing system in 8 lines and 2 nd Paragraph must
contain about what is uniqueness of your project in 7 lines.

Page 8: Requirements Specification

Start like this, Below are requirements that are identified and used in our project.
SUB HEADINGS: 1. Hardware requirements: Times new roman, Font size 12, Sentence case format.

2.Software requirements: Times new roman, Font size 12, Sentence case format.

3.Human requirements: Times new roman, Font Size 12, sentence case format.

4.Financial requirements: Times new roman, Font size 12, Sentence case format.

Page 9: METHODOLOGY

Page 10 and Page 11: ANALYSIS

1st paragraph in 4 lines explain about things to analyze in your project.

SUB HEADINGS: 1. Data Analysis (3 to 4 points use black dot bullet symbol)

2. Software analysis (4 to points use black dot bullet symbol)

3.Hardware analysis (4 to 5 points use black dot bullet symbol)

4. Human Resources (2 to 3 points use black dot bullet symbol)

5.External Resources (3 to 4 points use black dot bullet symbol)

Page 12 and page 13: Design

Start with 2 lines of introduction and include architecture diagram and there should
be two uml diagrams and sequence diagrams if back end is used in project draw ER diagrams other
wise use case or activity diagrams can be used.

Page 14 and page 15: coding

Must include syntax and source code (1 page ) if code is big paste partial code screen shot.

Page 16: Testing (Any 5 testing according to your projects)

Page 17 and page 18: Implementation.

Paragraph of 4 lines about how to implement your project and paste output screenshots.

Page 19: Maintenance (4 points use black dot bullet symbol)

Page 20: Future Enhancement

Page 21: Conclusion

Page 22: Acknowledgement


Page 23: References

Total 10(4 from journal and conference papers and 3 from international online books and 3
from online websites).

Format: Author name, title, JOURNAL NAME, Year of publishment.

NOTE: BEFORE WRITING CONTENT USE ONE TAB AND CHANGE TAB SETTINGS TO 0.2.

You might also like