Scribd
Upload
86 views2 pages

Project Synopsis Guidelines

This document provides guidelines for 6th semester MCA/BCA students to follow when writing a project synopsis. The synopsis should be 6-8 pages and include: 1) the title of the project, 2) the objectives and scope, 3) hardware and software resources needed, 4) a project schedule plan using a Gantt chart, 5) a description of the project team and each member's contributions, 6) a process description using diagrams, 7) the student's contributions, and 8) a conclusion describing innovations and achievements. References are provided to help with topics like UML diagrams, database design, methodology, and Gantt charts.

Uploaded by

shruti rai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
86 views2 pages

Project Synopsis Guidelines

This document provides guidelines for 6th semester MCA/BCA students to follow when writing a project synopsis. The synopsis should be 6-8 pages and include: 1) the title of the project, 2) the objectives and scope, 3) hardware and software resources needed, 4) a project schedule plan using a Gantt chart, 5) a description of the project team and each member's contributions, 6) a process description using diagrams, 7) the student's contributions, and 8) a conclusion describing innovations and achievements. References are provided to help with topics like UML diagrams, database design, methodology, and Gantt charts.

Uploaded by

shruti rai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

PROJECT SYNOPSIS FORMAT FOR 6TH SEMESTER MCA/BCA STUDENTS 2022-23 BATCH

Synopsis, preferably, should be of about 6-8pages. The content should be as brief


as is sufficient enough to explain the objective and implementation of the project
that the candidate is going to take up. The write up must adhere to the guidelines
and should include the following in order as given below:

1. Title of the Project


2. Objective and Scope of the project
3. Resources (Hardware & Software) to be used
4. Project Schedule Plan
5. Project Team
6. Process Description
7. Contribution of the student in the project
8. Conclusion

1. Titleof the Project:


This should be explicitly mentioned at the beginning of the Synopsis. Since
thetopic itself gives a peep into the project to be taken up, candidate is advised to
beprudent on naming the project. This being the overall impression on the
futurework, the topic should corroborate the work.

2. Objective and Scope:


This should give a clear picture of the project. Objective should be
clearlyspecified. What the project ends up to and in what way this is going to help
theend user should be mentioned.

3. Resources (Hardware &Software) to be used:


The requirement of the resources for designing and developing the
proposedsystem must be given. The resources might be in form of the hardware /
softwaretools or the development environment from the industry.

4. Project Schedule Plan:


Every activity of the project is to be shown using Gantt chart covering the
timeschedule of each.
5. Project Team:
The description of the whole project team should be mentioned along with
thecontribution of every team member in terms of modules covered by them
(nottheir description)

6. Process Description:
The process of the whole software system proposed, to be developed, should
bementioned in brief. This may be supported by the necessary diagrams to
explainthe flow of the information(i.e,UML model for example ,activity diagram ,
use case diagram,Class Diagram, Communication Diagram, for each module) . It
must contain the listing of the modules and theirbrief description.

7.Contribution of the student in the project:


Detailed description of the modules covered by the student is tobe shown.

8. Conclusion:
The write-up must end with the concluding remarks-briefly describing innovations
in the approach for implementing the Project, main achievements and also any
other important feature that makes the system stands out from the rest.

Note:
You may refer the following books for the specified topics during Project
Documentation:
UML Diagrams :Martin Flower,-"UML Distilled :A Brief Guide to the Standard Object Modeling
Language"
DBDesign:Elmasri, Navathe, -“FundamentalsofDataBaseSystems”‖, Addision Wesley.
Methodology:R. S. Pressman, -“SoftwareEngineering: APractitionersApproach”‖, TMH
GanttChart:Bob Hughes and Mike Cotterell, -“SoftwareProjectManagement”‖, TMH

You might also like