Anda di halaman 1dari 8

Greetings friends, In colleges you might have to submit Synopsis before proceeding to actual project and sadly there

is no documentation team so you have to start working on it. Quite irritating na yes its irritating when the programmer has to do such kind of jobs. But unfortunately sometimes we have to. Its no use right now to criticize the system we just have to learn how to write a synopsis. before proceeding let me tell Define it: Synopsis : It is a formal document which gives brief description of the

problem statement and how it will be solved using proposed system up-to which extent. In real life synopsis is quite important as it is the written document and acts a legal document between the developer and the client and also for the programming team as synopsis makes it clear for them to understand what exactly the client expect from them. so lets begin with How to write the synopsis Synopsis should preferably should be of 5-6 pages. The contents should be as brief as is sufficient enough to explain the implementation and the objective and implementation of the project that the

candidate is going to take up. The write up must be athere to the guidelines and should include the following (not necessarily in the order given below).

A beautiful but professional cover page Team member(s) name Name/ title of the project Problem statement why is this particular topic Chosen ? Objective and scope of the project Innovativeness and usefulness.

Methodology (including summary of the project) Hardware and software to be used Testing technology to be used What contribution would the project make ? Guide's Resume and his/her willingness to guide.

Topic of the project This topic should be explicitly mentioned at the beginning of the Synopsis.Since the topic itself gives a peep into the project to be taken up, candidate is advised to be prudent on naming the

project. This being the overall impression on the future work, the topic should corroborate the work. Objective & scope this should give clear picture of the project. Objective should be clearly specified. What the project ends upto and in what way the user is going to help the end user has been mentioned. Process Description The process of the whole software system proposed, to be developed, should be mentioned in brief. This may be supported by DFD's / Flowcharts to explain the flow of the information. Resource Limitation The requirement of the resource for

designing and developing the proposed system must be given. The resources might be in the form of the hardware / software or the data from the industry. The limitations of the proposed system in respect of a larger and comprehensive system must be given. Conclusion The write-up must end with a concluding remark - briefly describing innovations in the approach for implementing the project, main achievement and also any other important feature that makes the system stand out from the rest. Typing and Binding instructions Page Dimension And Binding Specifications

The dimension of the project report should be in A4 size. The project report should be bound using flexible cover of the thick white art paper. The cover should be printed in black letters and the text for printing should be identical.

Typing instructions

The impression on the typed copies should be black in colour. One and a half spacing should be used

for typing the general text. The general text shall be typed in the Font style Times New Roman and Font size 14.

Anda mungkin juga menyukai