PROJECT PROPOSAL (SYNOPSIS)

The project proposal should be prepared in consultation with your guide. The project proposal
should clearly state the project objectives and the environment of the proposed project to be
undertaken. The project work should compulsorily include the software development. The
project proposal should contain complete details in the following form (not more than two
pages).

(1) Title of the Project.

(2) Introduction and Objectives of the Project.
(3) Project Category (web based/RDBMS/OOPS/Networking/Multimedia/Artificial
Intelligence/Expert Systems etc.).
(4) Tools / Platform, Hardware and Software Requirement specifications.
(5) Are you doing this project for any Industry/college? Mention Yes/No. If Yes, Mention the
(6) Name and Address of the Industry or Client.
(7) Future scope and further enhancement of the project. Also mention limitation of the project.
(8) Name of your guide
(9) Date of submission
 METHODOLOGY FOR THE PROJECT WORK

Note: Texts in black are the headings and subheadings they are to be
written as it is. Texts in green are the descriptions are also to be
written as it is. Texts in red are to be written according to your system.

Chapter 1. Systems Introduction

1.1 Brief Description of the System under Study: Describe the system under study in details. It
must clearly bring out how the existing information system works and achieves the task.

1.2 About the proposed System: Explain the Aim, Objectives and Scope for developing
information system vis-à-vis the referenced organisation. For the purpose of this project the
organisation could be a virtual set up. Clearly spell out what is proposes to be done in the project

1.3 Methodology used for Analysis, Design & Development: Explain which methodology you
will adopt for analysis and design for example System Development Life Cycle (SDLC)
approach or its variant, Object Oriented Method, Structured analysis and development method or
prototype method. You may follow a mixed methodology and tools; however, you should clearly
mention the steps and tools and techniques that you are going to follow in the current project
with brief justification.

1.4 Methodology used for Data Collection: To carryout systems analysis and establish user
requirements students can use either primary data (through a questionnaire, interview or
observation) or secondary data (through document analysis or published data) or both. In either
case, the method and source used must be mentioned with proper references.

1.5 System Requirement Tools: Explain the software and hardware tools and platform that you
proposed to use in the project.
Chapter 2 System Analysis
Software Requirement Specifications – A single paragraph about SRS
2.1 Introduction
The following subsections of Software Requirement Specifications Document should
facilitate in providing the entire overview of the Information system “Title of your Project”
under development. This document aims at defining the overall software requirements for
your end users. Efforts have been made to define the requirements of the Information system
exhaustively and accurately.
2.1.1 Purpose
The main purpose of Software Requirement Specifications Document is to describe in a
precise manner all the capabilities that will be provided by the Software Application “Your
Title”. It also states the various constraints which the system will be abide to. This document
further leads to clear vision of the software requirements, specifications and capabilities.
These are to be exposed to the development, testing team and end users of the software
2.1.2 Scope – scope of your proposed system
2.1.3 Definition, acronyms, abbreviations
2.1.4 References
2.1.5 Overview
The rest of this SRS document describes the various system requirements, interfaces, features
and functionality in detail.
2.2 Overall description of proposed system
2.2.1 Product Perspective
The application will be windows-based, self contained and independent software product.

Front End Client

Application (with Backend
data entry / update Database
/delete /view and
reporting facility)

2.2.1.1 System Interfaces

None
2.2.1.2 Interfaces
The application will have a user friendly and menu based interface. Following screens will be
provided.
(i) A Login Screen for entering username, password and role (Administrator, operator)
will be provided. Access to different screens will be based upon the role of the user.
And so on.
The following reports will be generated:
(i) And so on.

2.2.1.3 Hardware Interfaces

2.2.1.4 Software Interfaces
2.2.1.5 Communication Interfaces
None
2.2.1.6 Memory Constraints
2.2.1.7 Operations
This product will not cover any automated housekeeping aspects of database. The DBA at
client site will be manually deleting old/ non required data. Database backup and recovery
will also have to be handled by DBA.
2.2.1.8 Site Adaptation Requirement
The terminals at client side will have to support the hardware and software interfaces
specified.
2.2.2 Product functions
The system will allow access only to authorized users with specific roles (Administrator,
Operator). Depending upon the user’s role, he/she will be able to access only specific
modules of the system.
A summary of the major functions that the software will perform:
(i) A Login facility for enabling only authorized access to the system.
(ii) Users (with role operator) will add/update/delete the stored information and so on

2.2.3 User Characteristics

1. Educational Level: At least graduate and should be comfortable with English language.
2. Technical Expertise: Should be a high or middle level employee of the organization
comfortable with using general purpose applications on a computer
 2.2.4 Constraints
None
2.2.5 Assumptions and Dependencies – if any
2.2.6 Apportioning Requirement
Not Required
2.3 Specific Requirements
This section contains the software requirements to a level of detail sufficient to enable
designers to design the system, and testers to test the system.
2.3.1 External Interfaces
2.3.1.1 User Interfaces
The following screens will be provided:
2.3.1.2 Hardware Interfaces
2.3.1.3 Software interfaces
2.3.1.4 Communication Interfaces
None
2.3.2 System Features
Module name
Description
One paragraph in brief about module
Validity Checks
Sequencing Information
Error Handling / Response to abnormal situations
2.3.3 Performance Requirements
None
2.3.4 Logical Database Requirements
The proposed information system contains the following data tables in its database
collection.
1. Table name

2.3.5 Design Constraints

2.3.5.1 Standard Compliance
None
 2.3.6 Software System Attributes
Reliability
This application is a reliable product that produces fast and verified output of all its
processes.
Availability
This application will be available to use for your end users and help them to carry out their
operations conveniently.
Security
The application will be password protected. User will have to enter correct username,
password and role in order to access the application.
Maintainability
The application will be designed in a maintainable manner. It will be easy to to incorporate
new requirements in the individual modules.
Portability
The application will be easily portable on any windows-based system that has oracle
installed.
2.3.7 Other Requirements
None
3 Methodologies for Data Collection
3.1 Primary Data Collection
3.2 Secondary Data Collection
4. Methodology used for Analysis, Design and Development
4.1 Stages of Model
4.2 Block Diagram of Model
4.3 Reasons for choosing Model/
5 Project Planning Gantt chart
 Chapter 3: System Design
1. Physical Design- about your system
Block Diagram- about block diagram followed by properly labelled diagram
2. Use Case
3. DFD
4. ER Diagram
Description and ER diagram
5. Database Design
The information system of “your title” performs its function with the help of the data
store in certain repositories called Databases of the system. Detailed descriptions of the
various databases included in the information systems are tabulated as follows:
Login database
Schema of each table properly labeled
For each table follow the given format
S.NO. Field Name Field Type Field Size Constraint Description

6. Site Map
Description and site map

3. Interface Design
The interface design consists of the input and output source layouts. i.e. the input forms and
screens and the report layouts that form as a source of outcome and income in the design and
implementation of the information system under study

3.1 Input Design

The input specifications of the existing information system include the illustration of the
detailed characteristics of contents included in each Input Screen and documents. The
description for each graphical user interface has been mentioned.
EXISTING SYSTEM DESIGN (Graphical User Interface)
1. Main Form
Snap shot of your main screen
Description and so on
3.2 Output Design
The output specifications of the existing information system include the detailed
characteristics of contents included in each Report. The description for each Visual Basic
Output Report has been mentioned.
1. Report 1
Snap shot of your report properly labelled
Description
File Linked to: name of the table and so on
 FORMAT OF THE PROJECT REPORT
1. The format for compilation of final report is given below:

(a) Title Page

(b) Certificate
(c) Acknowledgements
(d) Table of Contents
(e) List of Tables
(f) List of Figures
(g) List of Symbols
(h) Body of the Project Report
(j) Appendices

Title Page

2. The format of the title page is attached as Annexure-I.

Certificate

3. The format of the certificate is attached as Annexure-II. A certificate by the student,

guide and duly authenticated by the Director is to be attached.

Acknowledgement

4. In the “Acknowledgement” page, the writer recognises his indebtedness for guidance and
assistance by the guide and other members of the faculty. Courtesy demands that he/she also
recognises specific contributions by other persons or institutions such as libraries and research
foundations. Acknowledgements should be expressed simply, tastefully, and tactfully duly
signed above the name.
Table of Contents

5. The format of ‘Table of Contents’ and list of Tables/Figures/Symbols is attached as

Annexure-III.

Body of the Project Report: Guidelines for Project Report Writing

6. The guidelines for the Body of the Project Report (methodology) are detailed in
Appendix-A. Following aspects must be adhered to:
(a) Page Size: Good quality white A4 size executive bond paper should be used for
typing and duplication.

(b) Chapter/Para Numbering: The chapters are to be numbered as Chapter-1,

Chapter-2 etc. The heading/title of the chapter is to appear below the chapter number in
uppercase. Paragraphs are to be numbered as 1,2,3 etc in every chapter separately. Sub-
paras are to be numbered as 1.1, 1.2, 1.3----, 2.1, 2.2, 2.3-----etc. Sub-sub paras are to be
numbered as 1.11, 1.12, 1.13, 2.11, 2.12, 2.13 etc.

(c) Page Specifications:

(i) Left Margin : 1.25 inch

(ii) Right Margin : 1.25 inch
(iii) Top Margin : 1 inch
(iv) Bottom Margin : 1 inch

(d) Page Numbers: All text pages starting from Body of the Project Report as well
as program source code listings should be numbered at the bottom center of the pages.

(e) Normal Body Text:

 (i) Font Size: 12, Times New Roman, Double Spacing, Single Side Writing.
(ii) Paragraphs Heading Font Size: 12, Times New Roman, Underlined
(iii) Page/Title Font Size: 14

(f) Table and Figure Number: Table and figure numbers are to be written at the
bottom of the table/ figure as given below:

(i) Table No-1: File Design for Employee Record

(ii) Figure No-1: Data Flow Diagram

(g) Binding & Color Code of the Report: Each team is to submit a joint written
project report in spiral binding along with a CD.

Appendices

7. The appendices are to be attached at the end of the report and to be numbered as
Appendix-A, Appendix-B etc right justified at the top of the page. Below the word Appendix
write in parenthesis “Refer Para No__”. The para number is to be the number in the body of text
where the reference of appendix is given. An appendix may have annexure (s). If there are
annexure, these are to be attached immediately after the said appendix. The annexures are to be
numbered as Annexure-I, Annexure-II etc.
Annexure 1

Title of The Project Report

(Font size = 18)

Submitted in partial fulfillment of the requirements

for the award of the degree of

Bachelor of Computer Applications

To

Guru Gobind Singh Indraprastha University, Delhi

Guide: Submitted by:

(Guide Name) 1. (Student name Roll No)
2. (Student name Roll No)
 Nurturing Excellence

Institute of Innovation In Technology & Management,

New Delhi – 110058
Batch (2015-2018)
Annexure II

Certificate

We, 1. (Name & Roll No) & 2. (Name & Roll No) certify that the Summer Training Project
Report (BCA-355) entitled “________________________________” is done by us and it is
an authentic work carried out by us at ___________________________ (Name of the
organisation or of the Institute). The matter embodied in this project work has not been
submitted earlier for the award of any degree or diploma to the best of my knowledge and
belief.

1. Signature of the Student 2. Signature of the Student

Date:

Certified that the Project Report (BCA-355) entitled“__________________________”

done by the above students is completed under my guidance.

Signature of the Guide

Date:
Name of the Guide:
Designation:
Countersigned

Director
Annexure-III

FORMAT FOR TABLE OF CONTENTS

TABLE OF CONTENTS

S No Topic Page No
1 Certificate -
2 Acknowledgements -
3 List of Tables/Figures/Symbols -
4 Chapter-1: Introduction
5 Chapter-2: System Analysis
6 Chapter-3: System Design
8 Appendices

FORMAT FOR LIST OF TABLES/FIGURES/ SYMBOLS

LIST OF TABLES

Table No Title Page No

1 File Design for Employee Record
2 File Design for Personal Details

LIST OF FIGURES

Figure No Title Page No

1 Data Flow Diagram
2 Input Screen for Data Entry

LIST OF SYMBOLS

S No Symbol Nomenclature & Meaning

1  Sigma (Summation)
2 kbps Kilo bits per second