certificate - bca.mlparmar.org file · web view1.3. definition, acronyms, and abbreviations [an...

TITLE OF PROJECT IN CAPITAL (Times new roman- 18 )

A Project submitted to

M.L.Parmar College of Computer Science and IT, Shree Sarvoday College Campus, Opp. G3+ Show room,

Behind F-Studio, Ghod Dod Road, Surat -395007

Affiliated to Veer Narmad South Gujarat Uiversity, Surat

in Fulfilment of the Requirements for the Degree of

Bachelor of Computer Application

By(Name of Student)

Enrolment No.

Guided byName of Assistant Professor

Designation: Assistant Professor

APRIL / MAY -2019

CERTIFICATE

This is to certify that research work embodied in this dissertation

entitled “Title”was carried out by Mr./Ms.Name of Student(Enrolment

no.: E161122301100xxx) at M.L.Parmar College of Computer Science

and IT for the fulfilment of B.C.A degree to be awarded by Veer Narmad

South Gujarat University. This Project work has been carried out under

my supervision and is to my satisfaction.

Date:

Place:

Signature and name of Supervisor Signature and name of HOD

DECLARATION

I hereby certify that I am the sole author of this project and that

neither any part of this project nor the whole of the project has been

submitted for a degree to any other University or Institution.

I certify that, to the best of my knowledge, my project does not

infringe upon anyone’s copyright nor violate any proprietary rights and

that any ideas, techniques, quotations, or any other material from the

work of other people included in my thesis, published or otherwise, are

fully acknowledged in accordance with the standard referencing

practices.

I declare that this is a true copy of my thesis, including any final

revisions, as approved by my project review committee.

Date:

Place: Signature and name of studentName

Enrolment No.: E16112230110xxx

Verified

Signature and name of Supervisor

ACKNOWLEDGMENT

Write an Acknowledgement of nearly 250 words.

4

ABSTRACT

Abstract in Time new roman 12 point fonts,

5

TABLE OF CONTENTS

CERTIFICATE..............................................................................................IDECLARATION...........................................................................................IIACKNOWLEDGMENT................................................................................IIIABSTRACT..................................................................................................VTABLE OF CONTENTS...............................................................................VI1 INTRODUCTION....................................................................................11

1.1 PROJECT PROFILE................................................................................111.2 BACKGROUND.......................................................................................111.3 PROJECT OUTLINE...............................................................................11

2 ENVIRONMENT DESCRIPTION.............................................................122.1 HARDWARE AND SOFTWARE REQUIREMENTS...................................122.2 TECHNOLOGY USED..............................................................................12

3 EXISTING SYSTEM................................................................................133.1 SYSTEM COMPONENTS.........................................................................133.2 DRAWBACKS OF EXISTING SYSTEM.....................................................13

4 SYSTEM PLANNING..............................................................................144.1 FEASIBILITY STUDY...............................................................................144.2 REQUIREMENT ANALYSIS AND DATA GATHERING............................14

5 PROPOSED SYSTEM..............................................................................155.1 SCOPE.....................................................................................................155.2 OBJECTIVES............................................................................................155.3 CONSTRAINTS........................................................................................155.4 EXPECTED ADVANTAGES......................................................................15

6 DETAILS PLANNING..............................................................................166.1 DATA FLOW DIAGRAM...........................................................................166.2 PROCESS SPECIFICATION.....................................................................166.3 DATA DICTIONARY.................................................................................166.4 ENTITY RELATIONSHIP DIAGRAM........................................................16

7 SYSTEM DESIGN...................................................................................177.2 DIRECTORY STRUCTURE.......................................................................177.3 INPUT DESIGN.......................................................................................177.4 OUTPUT DESIGN....................................................................................17

8 SOFTWARE TESTING.............................................................................189 LIMITATION AND SYSTEM ENHANCEMENT........................................19

6

Report Format:

i. Title Page

ii. Project Certification Form [The certificate should be duly filled signed by

internal project guide and program coordinator.]

iii. Acknowledgement [All persons (e.g. guide technician, friends, and

relatives) and organization/authorities who/which have helped in the

understanding of the project shall be acknowledged.]

iv. Table of Contents with page numbering

v. List of Tables, Figures, schemes

1. Introduction

1.1. Purpose [Purpose means the objective to develop a project.

Purpose describes what a project is trying to achieve.]

1.2. Scope [Project scope should have a good idea of what the project

consists of (and what will not be part of the project). This statement

will give a view of the project.]

1.3. Definition, Acronyms, and Abbreviations [An

abbreviation/acronym is a shortened form of a word or phrase.

Abbreviation example: O.S. means Operating System Acronym

example: GHz, which stands for GigaHertz etc., which stands for et

cetera Definition: a statement of the exact meaning of a word]

1.4. Technologies to be used [Mention the technologies i.e. hardware

and software to be used in your project development and required

for deployment.]

2. System Analysis

2.1. Identification of Need [Need describes the problem or issue, or

situation where something needs to change to make things

better, for a person, a group of people, an environment or an

organization.]

2.2. Functionalities [This phase describes the functionality in system in

following two parts:

Usual functionalities.

Distinct functionalities.

7

2.3. User Characteristics [Identify classifications of users of your

system. E.g. System administrator, client. And write user wise

functionality available in proposed system.]

2.4. Software development process [Software development process

model methodology to be used, like e.g. Waterfall

development, Prototyping or Other] Note: Content should be

placed which must be related to concerned project only.

3. Conceptual Diagram

3.1. Use case diagram [A use case diagram defines interactions

between external actors and the system to attain particular

goals.]

3.2. Activity diagram [Activity diagrams are graphical representations

of workflows of stepwise activities and actions with support for

choice, iteration and concurrency.]

3.3. Sequential diagram [Sequence diagram is an interaction diagram

that shows how processes operate with one another and in what

order by time sequence.]

4. System Design

4.1. Data Dictionary, integrity constraints [A set of information

describing the contents, format, and structure of a database and

the relationship between its elements used to control access to

and manipulation of the database.]

4.2. User Interface Design [Snapshot of a project including validation

with caption below]

4.3. Reports (if any) [Snapshot of a project reports including input with

caption below]

5. Testing

5.1. Test cases

5.2. Testing Reports including description

6. Future scope and further enhancement of the Project

7. Learning during Project Work, i.e. “Experience of Journey during

Project Duration”

8. References [Enter the reference i.e. web, book or any other reference

document taken for project development.]

8

Guideline for Report Formatting: Use A4 size page with 1" margin all sides. Header should include Project tile and footer should contain page number

and enrolment numbers. Chapter Name should be of Cambria font, 26 points, Bold. Main Heading should be of Cambria font, 16 points, Bold. Sub Heading should be of Cambria font, 12 points, Bold. Sub Heading of sub heading should be of Cambria font, 12 points, Bold,

Italic. Paragraph should be of Cambria font, 12 points. Line spacing - 1.5 lines, before - 0, after - 0. No chapter number for references. Before chapter 1, give page number in roman letter (Title Page, Project

Certification Form, Acknowledgements, Table of Contents/Index with page numbering, List of

Tables, Figures, Schemes and Summary/abstract of the project work)

1 INTRODUCTION

Times New roman – 12 point font

1.1 PROJECT PROFILE


1.2 BACKGROUND


1.3 THESIS OUTLINE


9

2 ENVIRONMENT DESCRIPTION

2.1 HARDWARE AND SOFTWARE REQUIREMENTS


2.2 TECHNOLOGY USED


10

3 EXISTING SYSTEM 3.1 SYSTEM COMPONENTS


3.2 DRAWBACKS OF EXISTING SYSTEM


11

4 SYSTEM PLANNING

4.1 FEASIBILITY STUDY


4.2 REQUIREMENT ANALYSIS AND DATA GATHERING


12

5 PROPOSED SYSTEM5.1 SCOPE


5.2 OBJECTIVES


5.3 CONSTRAINTS


5.4 EXPECTED ADVANTAGES


13

6 DETAILS PLANNING6.1 DATA FLOW DIAGRAM


6.2 PROCESS SPECIFICATION


6.3 DATA DICTIONARY


6.4 ENTITY RELATIONSHIP DIAGRAM


14

7 SYSTEM DESIGN7.1 DATABASE DESIGN


7.2 DIRECTORY STRUCTURE


7.3 INPUT DESIGN


7.4 OUTPUT DESIGN


15

8 SOFTWARE TESTING

16

9 LIMITATION AND SYSTEM ENHANCEMENT

17

certificate - bca.mlparmar.org file · web view1.3. definition, acronyms, and abbreviations [an...

Documents