Project Dissertation Semester V and Project

Implementation Semester VI
Chapter 1 to 4 should be submitted in Semester V in spiral binding. These chapters have also to be included in
Semester VI report. Semester VI report has to be hard bound with golden embossing. Students will be evaluated
based on the dissertation in semester V and dissertation and viva voce in Semester VI.

I. OBJECTIVES
• Describe the Systems Development Life Cycle (SDLC).
• Evaluate systems requirements.
• Complete a problem definition.
• Evaluate a problem definition.
• Determine how to collect information to determine requirements.
• Perform and evaluate feasibility studies like cost-benefit analysis, technical feasibility, time feasibility and
Operational feasibility for the project.
• Work on data collection methods for fact finding.
• Construct and evaluate data flow diagrams.
• Construct and evaluate data dictionaries.
• Evaluate methods of process description to include structured English, decision tables and decision trees.
• Evaluate alternative tools for the analysis process.
• Create and evaluate such alternative graphical tools as systems flow charts and state transition diagrams.
• Decide the S/W requirement specifications and H/W requirement specifications.
• Plan the systems design phase of the SDLC.
• Distinguish between logical and physical design requirements.
• Design and evaluate system outputs.
• Design and evaluate systems inputs.
• Design and evaluate validity checks for input data.
• Design and evaluate user interfaces for input.
• Design and evaluate file structures to include the use of indexes.
• Estimate storage requirements.
• Explain the various file update processes based on the standard file organizations.
• Decide various data structures.
• Construct and evaluate entity-relationship (ER) diagrams for RDBMS related projects.
• Perform normalization for the unnormalized tables for RDBMS related projects
• Decide the various processing systems to include distributed, client/server, online and others.
• Perform project cost estimates using various techniques.
• Schedule projects using both GANTT and PERT charts.
• Perform coding for the project.
• Documentation requirements and prepare and evaluate systems documentation.
• Perform various systems testing techniques/strategies to include the phases of testing.
• Systems implementation and its key problems.
• Generate various reports.
Page 1 of 22
• Be able to prepare and evaluate a final report.
• Brief the maintenance procedures and the role of configuration management in operations.
• To decide the future scope and further enhancement of the system.
• Plan for several appendices to be placed in support with the project report documentation.
• Decide the various processing systems to include distributed, client/server, online and others.
• Perform project cost estimates using various techniques.
• Schedule projects using both GANTT and PERT charts.
• Perform coding for the project.
• Documentation requirements and prepare and evaluate systems documentation.
• Perform various systems testing techniques/strategies to include the phases of testing.
• Systems implementation and its key problems.
• Generate various reports.
• Be able to prepare and evaluate a final report.
• Brief the maintenance procedures and the role of configuration management in operations.
• To decide the future scope and further enhancement of the system.
• Plan for several appendices to be placed in support with the project report documentation.
• Work effectively as an individual or as a team member to produce correct, efficient, well-organized and
documented programs in a reasonable time.
• Recognize problems that are amenable to computer solutions, and knowledge of the tool necessary for
solving such problems.
• Develop of the ability to assess the implications of work performed.
• Get good exposure and command in one or more application areas and on the software
• Develop quality software using the software engineering principles
• Develop of the ability to communicate effectively.

II . SOFTWARE AND BROAD AREAS OF APPLICATION

FRONT END / GUI Tools .Net Technologies,Java

DBMS/BACK END Oracle, SQL Plus, MY SQL, SQL Server,
LANGUAGES C, C++, Java, VC++, C#, R,Python
SCRIPTING LANGUAGES PHP,JSP, SHELL Scripts (Unix), TcL/TK,
.NET Platform F#,C#. Net, Visual C#. Net, ASP.Net
MIDDLE WARE (COMPONENT) COM/DCOM, Active-X, EJB
TECHNOLOGIES
UNIX INTERNALS Device Drivers, RPC, Threads, Socket programming
NETWORK/WIRELESS TECHNOLOGIES -
REALTIME OPERATING SYSTEM/ LINUX, Raspberry Pi, Arduino, 8051
EMBEDDED SKILLS
APPLICATION AREAS Financial / Insurance / Manufacturing / Multimedia /
Computer Graphics / Instructional Design/ Database
Management System/ Internet / Intranet / Computer
Networking-Communication Software development/ E-
Commerce/ ERP/ MRP/ TCP-IP programming / Routing
protocols programming/ Socket programming
Page 2 of 22
III. PROJECT REPORT:

Title Page (Refer APPENDIX 1)

Original Copy of the Approved Proforma of the Project Proposal (Refer APPENDIX 2)
Certificate of Authenticated work (Refer APPENDIX 3)
COMPANY CERTIFICATE (If applicable)
Role and Responsibility Form (Refer APPENDIX 4)
Abstract (Refer APPENDIX 5)
Acknowledgement (Refer APPENDIX 6)
Declaration (Refer APPENDIX 7)
Table of Contents (Refer APPENDIX 8)
List of Tables and Figures (Refer APPENDIX 9)

CHAPTER 1: INTRODUCTION
1.1 Background
1.2 Objectives
1.3 Purpose, Scope, and Applicability
1.3.1 Purpose
1.3.2 Scope
1.3.3 Applicability
1.4 Achievements
1.5 Organisation of Report

CHAPTER 2: SYSTEM ANALYSIS

………………………….

Page 3 of 22
Page 4 of 22
 (APPENDIX 1 :Title Page )
(All the text in the report should be in times new roman)

TITLE OF THE PROJECT

(NOT EXCEEDING 2 LINES, 24 BOLD, ALL CAPS)

A Project Report (12 Bold)

Submitted in partial fulfillment of the
Requirements for the award of the Degree of (size-12)

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

(14 BOLD, CAPS)

By(12 Bold)

Name of The Student (size-15, title case)

Seat Number (size-15)

Under the esteemed guidance of (13 bold)

Mr./Ms. Name of The Guide (15 bold, title case)

Designation (14 Bold, title case)

COLLEGE LOGO

DEPARTMENT OF INFORMATION TECHNOLOGY(12 BOLD, CAPS)

COLLEGE NAME (14 BOLD, CAPS)
(Affiliated to University of Mumbai) (12, Title case, bold, italic)
CITY, PIN CODE(12 bold, CAPS)
MAHARASHTRA (12 bold, CAPS)
YEAR (12 bold)
Page 5 of 22
 (APPENDIX 2 :Original Copy of the Approved Proforma of the Project Proposal )

(Note: All entries of the proforma of approval should be filled up with appropriate and
complete information. Incomplete proforma of approval in any respect will be summarily
rejected.)

PNR No.: …………………… Roll no:

1. Name of the Student:

2. Title of the Project:

3. Name of the Guide:

4. Teaching/Industry experience of the Guide:

5. Is this your first submission? Yes No

Signature of the Student: Signature of the Guide:

Date: ………………… Date: …………………….

Signature of the Coordinator:

Date: …………………

Page 6 of 22
 (APPENDIX 3 :Certificate of Authenticated work )

COLLEGE NAME (14 BOLD, CAPS)

(Affiliated to University of Mumbai) (13, bold, italic)

CITY-MAHARASHTRA-PINCODE(13 bold, CAPS)

DEPARTMENT OF INFORMATION TECHNOLOGY (14 BOLD, CAPS)

College Logo

CERTIFICATE(14 BOLD, CAPS, underlined, centered)

This is to certify that the project titled, "Title of The Project ", is bonafied work of NAME OF
THE STUDENT bearing Seat.No: (NUMBER) submitted in partial fulfillment of the
requirements for the award of degree of BACHELOR OF SCIENCE in INFORMATION
TECHNOLOGY from University of Mumbai. (12, times new roman, justified)

Internal Guide (12 bold) Coordinator

(Don’t write names of lecturers or HOD)

External Examiner

Date: CollegeSeal

Page 7 of 22
COMPANY CERTIFICATE (if applicable)

Page 8 of 22
 (APPENDIX 4: Role and Responsibility Form )

Name of the Project:

Name and Signature of the *Role Tasks and Responsibilities

Team Members

Signature of the Project Guide: Date:

Page 9 of 22
 (APPENDIX 5: Project Abstract)

Abstract (20bold, caps, centered)

Content (12, justified)

Note: Entire document should be with 1.5

line spacing and all paragraphs should start with 1 tab space.

Page 10 of 22
 (APPENDIX 6: Acknowledgement)

ACKNOWLEDGEMENT
(20, BOLD, ALL CAPS, CENTERED)

The acknowledgement should be in times new roman, 12 font with 1.5 line spacing,
justified.

Page 11 of 22
 (APPENDIX 7: DECLARATION)

DECLARATION (20 bold, centered, all caps)

Content (12, justified)

I hereby declare that the project entitled, “Title of the Project” done at place where the
project is done, has not been in any case duplicated to submit to any other university for the award
of any degree. To the best of my knowledge other than me, no one has submitted to any other
university.
The project is done in partial fulfillment of the requirements for the award of degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final
semester project as part of our curriculum.

Name and Signature of the Student

Page 12 of 22
 (APPENDIX 8: Table of Contents)

TABLE OF CONTENTS (20 bold, caps, centered)

Should be generated automatically using word processing software.

Chapter 1: Introduction 01(no bold)

1.1 Background 02(no bold)
1.2 Objectives ….
1.3 Purpose and Scope ….
1.2.1 Purpose ….
1.2.2 Scope
………………………………
Chapter 2: System Analysis
2.1 Existing System
2.2 Proposed System
2.3 Requirement Analysis
2.4 Hardware Requirements
2.5 Software Requirements
2.6 Justification of selection of Technology

Chapter 3: System Design

3.1 Module Division
3.2 Data Dictionary
3.3 ER Diagrams
3.4 DFD/UML Diagrams

Chapter 4: Implementation and Testing

4.1 Code (Place Core segments)

4.2 Testing Approach
4.2.1 Unit Testing (Test cases and Test Results)
4.2.2 Integration System (Test cases and Test Results)

Chapter 5: Results and Discussions (Output Screens)

Chapter 6: Conclusion and Future Work
Chapter 7: References
Chapter 8: Glossary

Page 13 of 22
 (APPENDIX 9: List of Tables and Figures)

List of Tables (20 bold, centered, Title Case)

Should be generated automatically using word processing software.

List of Figures (20 bold, centered, Title Case)

Should be generated automatically using word processing software.

Page 14 of 22
 (Project Introduction page format)

Chapter 1
Introduction (20 Bold, centered)
Content or text (12, justified)

Note: Introduction has to cover brief description of the project with minimum 4 pages.

Page 15 of 22
 Chapter 2

System Analysis (20 bold, Centered)

Subheadings are as shown below with following format (16 bold, CAPS)
2.1 Existing System (16 Bold)
2.1.1 (14 bold, title case)
2.1.1.1 (12 bold, title case)

2.2 Proposed System

2.3 Requirement Analysis
2.4 Hardware Requirements
2.5 Software Requirements
2.6 Justification of Platform – (how h/w & s/w satisfying the project)
Table 2.1: Caption

Page 16 of 22
 Chapter 3

System Design (20 bold, centered)

Subheadings are as shown below with following format (16 bold, CAPS)
Specify figures as Fig 11.1 – caption
3.1 Module Division
3.2 Data Dictionary

3.3 E-R Diagrams

3.4 Data Flow Diagrams / UML

Note: write brief description at the bottom of all diagrams

Fig. 3.1: Caption

Page 17 of 22
 Chapter 4

Implementation and Testing (20 bold, centered)

4.1 Code (Place Core segments)
Content includes description about coding phase in your project (Font-12)
(* don’t include complete code just description)

4.2 Testing Approach

Subheadings are as shown below with following format (16 bold, CAPS)
4.2.1 Unit Testing
4.2.2 Integration Testing
Note:

➢ Explain about above testing methods

➢ Explain how the above techniques are applied in your project
➢ Provide Test plans, test cases, etc relevant to your project

Page 18 of 22
 Chapter 5

Results and Discussions (20 bold, centered)

Note: Place Screen Shots and write the functionality of each screen at the bottom

Page 19 of 22
 Chapter 6

Conclusion and Future Work (20 bold, centered)

The conclusions can be summarized in a fairly short chapter around 300 words. Also
include limitations of your system and future scope (12, justified)

Page 20 of 22
 Chapter 7

References (20 bold, centered)

Content (12, LEFT)

[1] Title of the book, Author

[2] Full URL of online references

[3] ------------

Page 21 of 22
 Chapter 8

Glossary (20 bold, centered)

Explain a list of technical terms, abbreviations or phrases in this document which are
difficult to understand (Preferably in alphabetical order) (12, justified)

Page 22 of 22