Scribd
Upload
115 views

Guidelines

This document outlines the template and guidelines for preparing a project report for a Computer Science and Engineering degree. It provides instructions on the required sections of the report including the title page, certificates, declarations, abstract, contents, introduction, literature review, system analysis, software requirements specification, system design, implementation, testing, screenshots, conclusion, and references. It also provides brief formatting guidelines and deadlines for submitting the project report.

Uploaded by

Irfan Ahmed
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
115 views

Guidelines

This document outlines the template and guidelines for preparing a project report for a Computer Science and Engineering degree. It provides instructions on the required sections of the report including the title page, certificates, declarations, abstract, contents, introduction, literature review, system analysis, software requirements specification, system design, implementation, testing, screenshots, conclusion, and references. It also provides brief formatting guidelines and deadlines for submitting the project report.

Uploaded by

Irfan Ahmed
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

4/4 B.E.

(Computer Science & Engineering) II Semester Template & Guidelines for preparing the Project Report
1. Title (Pl refer a previous project report from Dept. Library/Main Library) 2. Certificate from College (on a letter head, signed by the Head and the Int. Guide) 3. Certificate from the Company (Where the Project is done. e.g. TCS/WIPRO ) 4. Declaration (Given by the Project team members) 5. Acknowledgement (Given by the Project team members) 6. Abstract (One Page only). Abstract is the brief overview of the Project. 7. Contents (with page numbers) 8. Introduction (2-3 pages) 9. Literature Survey (Student should include details of Literature used viz. Software, Platform, UML concepts, Tools/Techniques used etc.) (About 20-30 pages and should be specific to your project.) 10. System Analysis - Problems with Existing System - Proposed System - Process Logic - Feasibility Study (Technical, Economical & Operational) - Effort, Duration and Cost Estimation using COCOMO, Function Point. (Exhaustive theoretical description of COCOMO, Function Point should be avoided) 11. Software Requirement Specification (as per any IEEE Std. of your choice, preferably IEEE std. 830-1998. The SRS should be around 15-30 pages.) 12. System Design - System Architecture - Data Flow Diagrams - Flow Charts - UML Diagrams (All the diagrams should be drawn. The Diagrams should be well documented) - If the project is Hardware related or on Embedded Systems, then the circuit diagram etc of hardware should also be included.

12. Implementation (The complete Source code should not be included. Important classes/functions should only be included. In case, if the organization does not permit you to take the source code outside, then the Pseudo code shall be included. ) 13. Testing (Should show how the software is tested. You can include the test cases for Unit & Black Box testing.) Wrong practice: Students usually write about Unit Testing, Integration Testing, Black Box Testing etc. i.e. they write about Testing Techniques in Software Engineering!! This should not be done. 14. Screenshots: (This is the GUI of the System. You can include a few important Screenshots.) 15. Conclusion (One Page)& Future Enhancements (One Page) 16. Bibliography/References (Should be in IEEE Format. You can include the names of Research Papers, Websites, books etc.) Example: 1. J. Gaffney, On Predicting Software Related Performance of Large-Scale Systems, CMG Proceedings,Philadelphia, 1984. 2. Roger S. Pressman, Software Engineering A Practitioners Approach, 6th Edition , Tata McGraw Hill, 2004 3. http://www.cmu.edu Brief Guidelines: 1. All the pages should be numbered and bottom centered. The Report should be printed with 1.5 line spacing, 12-point font, Times New Roman. Giving unnecessary blank spaces to increase the size of project report is strictly prohibited. 2. Last date for submitting the Project report is 14-April-2012. Buffer time: 1 week. 3. The project execution should be shown to the internal guide before the submission. 4. Three copies of project report should be submitted to the college. If three students are working on a project, six copies should be printed Three copies for students & three for the dept.) 5. The students are requested to show the draft copy of the Project report to Head/Concerned Internal guide before printing. 6. The Internal Guide followed by the Head shall sign the Project report. 7. The students are advised to report to their respective internal guides immediately. Further, they are supposed to update the progress of the project to their respective guides on a weekly basis.

Head-CSE

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy