Project Phase 1 Report Format-1
Project Phase 1 Report Format-1
which includes University name and its logo, Project title, Team members name, Guide name
and their designation & lastly department name and college name.
which includes a Project title , team members name & Principal, guide & external name &
signature.
● it should list the project’s results or product (or projected or intended results or product,
if project is not yet complete),
● and it should draw conclusions about the implications of your project
1.1 overview[section such as 1.1 should be left justified with font size 16, bold,
subsection such as 1.1.1 should be left justified with font size 14]
[1 tab space at beginning of each para]A project overview is similar to an outline and
should not exceed one page. In the project overview you must include many of the main
ideas of the project. You do not have to go into details since this is an overview and hence
the main ideas should be included [font size of inner text 12].
[Top-Margin : 1; Bottom-Margin : 1 ; Left-Margin : 1.25 ; Right-Margin : 0.75 ; Font-
Family : Times New Roman; text should be justified ; Line Spacing : 1.5]
For your literature survey review information from various sources (books, journals,
conference proceedings, web sites, product literature, etc.). The goal is to show that you have
read the information about the system from various sources and understand the problems/issues
of the system.
Your goal at this point is to “present an overview of what your source offers its topic,
problem.
Include the following content:
a) What the topic is
b) What problems and issues it addresses
c) What are the different technical approaches (explain in detail in context of Existing System
and proposed System), and a comparison of their specific benefits and issues.
Sub systems, modules, sub modules, functions and sub functions along with their
interactions, relationship with external environments and human interaction with them,
networking capabilities, internal interfaces among the components should be mentioned in detail.
Should show the interaction of devices, appliances, systems and modules completely. Possibly
should contain Control flow, data flow and process flow schematics.
5.2.2 DB Design: Use data flow diagrams to explain the flow of data in sub systems and
modules
5.2.3 DB table structure: Should specify the tables with their various fields, indexes and
relations with an ER diagram. Show the normalization done on the tables. Highlight the
maximum number of records that the DB will hold with the design for testing.
Detailed description of each module should be given. Should use class diagram,
sequence diagram, Activity diagram, data flow diagram, deployment diagram (any one is
compulsory, can use more than one diagrams to show the low level design).
This section should in simple English explain logic of the program using Pseudo code.
REFERENCES
Include all the references and sources which helped you in the execution of the project work.