6th Sem Project Format [2012][f2]

COVER PAGE & FIRST PAGE

A Project report on

(Title of the Project)

Submitted in partial fulfillment of requirement

for the VI sem MCA Project

UnderVisvesvaraya Technological University, Belgaum

Karnataka

By

(Name and Reg.No. of the candidate)

Under the guidance of

(Internal Guides name, (External guides name designation& address) Designation& address)

R. V. COLLEGE OF ENGINEERINGMYSORE ROAD, BANGALORE – 560 059

MONTH / YEAR

of 14

SECOND PAGE

College Certificate

R. V. COLLEGE OF ENGINEERING, DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

AFFILIATED TO VISVESVARAYA TECHNOLOGICAL UNIVERSITY, BELGAUMAPPROVED BY ALL INDIA COUNCIL FOR TECHNICAL EDUCATION, NEW DELHI

ACCREDITED BY NATIONAL BOARD OF ACCREDITATION, NEW DELHIBANGALORE - 560059

MONTH / YEAR

CERTIFICATE

This is to certify that the project entitled(name of the project)

Submitted in partial fulfillment of the VI sem MCA Projectis a result of the bonafide work carried out by

(name of the student with reg. no.)

during the academic year – YYYY

Internal Guide Director, Department of MCA Department of MCA, R. V. College of Engineering R.V.College of Engineering Bangalore – 560 0 59 Bangalore – 560 059

PRINCIPALR. V. COLLEGE OF ENGINEERING

MYSORE ROAD, BANGALORE - 560059

of 14

THIRD PAGE

Undertaking by the student

I, <<Student Name>>, <<USN>>, hereby declare that the project <<Project Title>> is

carried out and completed successfully by me and is my original work.

Student Signature with Name

of 14

FOURTH PAGE

Company Certificate

[For projects carried outside the college]

(Industry/Institute Certificate)

A certificate on the letterhead of the Industry/Institute with the necessary signatures and Seal.

of 14

FIFTH PAGE

ACKNOWLEDGEMENT

(IN ORDER OF POSITION)

[contents]

Name of the student Reg.No

of 14

SIXTH PAGE

Table of contents (Index)

Particulars Page No:Table of Contents iList of Figures iiList of Tables iii Synopsis iv

Chapter 1: Preamble 1.1 Introduction.1.2 Problem Statement1.3 Objective of the work1.4 Scope of the work.1.5 Literature Survey (With Quoted References)1.6 Methodology1.7 Limitation of the work1.8 Dissertation / Report Organization (Chapter wise brief explanation).

Chapter 2: Software Requirement Specification2.1 Introduction

Purpose Scope Definition / Acronyms / Abbreviations. References. Overview of the Document.

2.2 General Descriptions2.3 Functional Requirements

Data Integration Data Analysis Reporting External Interface Requirement Performance Requirement Design constraints Other Requirements (If any)

Chapter 3: Design Specification3.1 Architecture Design

Problem specification Module Specification Assumptions Made (if any)

3.2 System Design Dynamic Model Functional Model Module Design Deployment Design

3.3 Detailed Design

of 14

Design Decision Data Dictionery Program Design Language

(A Common format in representing the detailed design is attached for student’s information in order to maintain uniformity in the design flow)

Chapter 4: Testing and Results4.1 Testing

(Testing: Do not explain all the testing techniques available. Explain only the testing methods adopted in the respective projects).

4.2 Results:(Include the tested output screens/ Results)

4.3 Conclusion:(This should be a technical conslusion based on the project work)

4.4 Future enhancements: (Possible future improvements to be mentioned with the project Limitations.)

Annexures:(Annexures relevant to the project such as figures, graphs, Photographs, etc. to be included here)

Bibliography:(All these are references to be quoted in the respective chapters in order)Note: Web site references must have proper link which is been used. Text book references must have the chapter / topic referred

TEXT PAGE FORMAT

of 14

Title of the project or abbreviated title page no 1/x.

R. V. College of Engineering Department of MCA Month / Year

DFD Format:

of 14

Gane and Sarson - Process Notations

General Data Flow Rules

1. Entities are either 'sources of' or 'sinks' for data input and outputs - i.e. they are the originators or terminators for data flows. 2. Data flows from Entities must flow into Processes 3. Data flows to Entities must come from Processes 4. Processes and Data Stores must have both inputs and outputs (What goes in must come out) 5. Inputs to Data Stores only come from Processes. 6 Outputs from Data Stores only go to Processes.

Each Process box in the Top Level diagram will itself be made up of a number of

of 14

Processes, and will need to be decomposed as a second level diagram. Each box in a diagram has an identification number derived from the parent - in the top left corner. (The Context level is seen as box 0) Any box in the second level decomposition may be decomposed to a third and then a fourth level. Very complex systems may possibly require decomposition of some boxes to further levels. Decomposition stops when a process box can be described with an Elementary

Flowchart Notation

CLASS DIAGRAM’S

of 14

Generalization

Realization

Assosiation

of 14

Aggregation

Composition

of 14

Interaction Notation:Interaction is basically message

of 14

exchange between two UML components. The following diagram represents different notations used in an interaction.

State machine Notation:State machine describes the different states of a component in its life cycle. The notations are described in the following diagram.

of 14

6th Sem Project Format [2012][f2]

Documents

Transcript of 6th Sem Project Format [2012][f2]