A project synopsis is the initial report that is submitted for the approval of the project that you have selected. The project synopsis is made in a specific format, it does not contain any finalized information; it just shows the basic idea of making the project, the problems that it will solve, the modules, data flow, databases, etc. Just follow these instructions to create a good project synopsis. This tutorial will show you how to create the project synopsis in a definite format.
Starting Page
The starting page consists of name of the project name, college name, college logo, name of the degree and your name. You can find it in the sample synopsis provided with this tutorial. The starting page contains no page numbers and no header and footer.
Table of Contents
Create this and put it after the first page. It will contain the list of the contents of the synopsis with their corresponding page number.
Abstract
In this part you will put the basic information about the project and the system which it will follow. Give the basic idea behind the project, the current problems and how the project will solve those problems. Keep all of these to one or at most two pages.
Introduction Part
Here comes the actual introduction part of the project. Explain in brief about the project in this part and give the information of all the major functionality that are to be incorporated into the project. Here, give the information about the existing system, its drawbacks and why it needs to be replaced. Then, explain about the proposed system. Tell about how the new system is better than older one. Use points in this part so that it can be better understood.
Design Principles and Explanation
Modules
List all the modules that you are to include in the project. First list them then explain them one by one.
Modules Description
Describe about all the modules in detail here. You may use pictorial representation if required to help it easier to understand.
Project Dictionary
- Data Flow Diagrams
Data flow diagrams represent the flow of data through a system. A DFD is composed of :
1. Data movement shown by tagged arrows.
2. Transformation or process of data shown by named bubbles.
3. Sources and destination of data represented by named rectangles.
4. Static storage or data at rest denoted by an open rectangle that is named.
The DFD is intended to represent information flow but it is not a flowchart and is not intended to indicate decision-making, flow of control, loops and other procedural aspects of the system. DFD is a useful graphical tool and is applied at the earlier stages of requirements analysis. It may be further refined at preliminary design stage and is used as mechanism for creating a top level structural design for software.
Have some DFDs included for your project. You can learn more about DFDs here :
- Entity Relationship diagram
An entity-relationship model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or ERDs.
Create the ER diagram for the database that you will use and put it in the project synopsis. You can learn more about ER diagrams here :
Summary
Write a brief summary about the project, about all the functionality, data models, advantages, disadvantages etc. Keep this to one page only, remember that a normal project synopsis is about 15-20 pages at most.
Download the sample project synopsis from here :
0 comments:
Post a Comment