Project Guidelines

Bachelor of Engineering
Computer Science & Engineering
for

Major Project
Year 2015

by,
Department of Department of Computer Science &
Engineering

Gyan Ganga College of Technology

Jabalpur

GUIDELINES FOR THE PROJECT REPORT

1. The Project Report must be as per given format and cover all the topics, but
according to project requirement student can omit some topic.
2. Chapter-1 to chapter-4 should be complete in 7th semester and rest of the
chapters will complete in 8th semester.
3. The Project Documentation may be about 50 to 60 pages (excluding coding).
The project documentation details should not be too generic in nature.
4. Every chapter start with one title page that includes chapter number and
chapter name. see page 20
5. n+2 (n - No. of students) hard binded copies of project report as per given
format. A CD consisting of the executable file(s) and source code of the
complete project should be attached on the last page of the project report. The
student needs to retain the identical copy of the CD that should be carried
while appearing for the viva-voce along with the project report.
6. After the table of contents every page should have footer, as following
Dept. of CSE

Gyan Ganga College of Technology, Jabalpur

Page : <no>

7. Front page of hard binded file same as your project front page, having Navy
Blue with Silver forecolor.
Project Report Format
The project report documentation should contain 80 to 100 pages for analysis, design, and
testing phases, however, the size of complete report may vary depending upon the size of
coding/ implantation and appendices. The project documentation details should not be too
generic in nature. To be more specific, whatever theory in respect of these topics is available in
reface books should be avoided as far as possible. The project documentation should be in
respect of your project only. You should make sensible use of appendices. For example, soft
ware user instructions, detailed code listing, correspondence may be relegated to appendices.
Note that spiral bindings are not suitable for handing in the project report.

And figures should have titles. Detailed information about the layout for the
project proposal and report are also listed below:
Font size and margin
1. The report is to be bound with a clear front cover having navy blue background
and silver fore color.

2. The chapters are in 12-point Times new roman font.

3. Line spacing is in 1.25 point.
4. The pages are of A4 size, with margins as given below, except for the front cover,
which has a specific format given in unit 1. Margins of pages should follow the
following specifications.
a. Left margin-1.5 inch. From edge of paper.
b. Right margin-1 inch. From edge of paper.
c. Top margin-1 inch. From edge of paper.
d. Bottom margin-1 inch. From edge of paper.
5. The above margins shall be observed on charts, graphs, tables, and drawings.
Folded paper or large size paper will not be
accepted unless there is absolutely no other way for the material to be presented.
Heading
1. Headings used in the project report should follow the following convention:
2. Main Headings or chapter Headings
a.
b.
c.
d.

Times roman, 16 font size (1,2,3 etc.) numerals.

Capital and bold.
Must begin a new page and be centered.
Main headings are to be tilted names that reflect content of the that
follows. Main headings are not to be identified as chapters.
e. The number of the headings shall be followed by a period and two spaces.
f. Must precede the following text material by second heading by three spaces.
3. Second Headings
a. Times roman, 14 font size, bold,2.1,2.2,2.3, etc
b. Must be centered and be typed in capital and lower case (sentence case)
letters; i.e., the first letter of each word except conjunctions, prepositions, and
articles must be a capital letter. Omit period at the end of the heading.
c. The letter designation of the heading of the heading shall be followed by a
period and two spaces.
d. Must be four spaces below preceding text and three spaces ahead
of succeeding text.
4. First Sub-Headings
a. Times roman, 12 font size, bold, 2.2.1,2.2.2, etc
b. Must be typed on separate lines beginning at the left margin line of the text,
but need not begin on a new page.
c. Must be typed in capitals and lower case letters except
conjunctions, prepositition, and articles.
d. The number designation of the heading shall be followed by a period and
two spaces. Omit period at the end of the heading.

e. Must be separated from the succeeding text by three spaces.

5. Second sub-headings (second sub-headings should be avoided if possible).
a. Times roman, 12 font size, bold.
b. Must be typed on the same line as the text it introduces beginning at the
left margin line of the text.
c. Must be typed in sentence case.
d. Must be followed by a period at the end of the heading and must
be underscored by a line.
e. The letter designation shall be followed by a period and two spaces.
Appendices re-start the section numbering, using capital letter as section labels
and Arabic numerals as sub-section labels (i.e.,A.1,A.2,); appendix headers are in
decreasing-sized fonts.
If a section is divided into sub-sections, it has at least two subsections. Similarly
for subsections divided into sub-sections, and so on.
The font matter, conclusions, recommendations, Glossary, Acknowledgements, and
reference sections are not divided into sub-sections. (Include in main heading or
chapter heading).
6. Project should have footer having department name, college name and page no, and
footer start after table of index.

Contents List for Major Report

1.
2.
3.
4.
5.
6.
7.
8.

Title Page
Certificate of HOD & Guide
Certificate of Internal & External Examiner
Abstract
Declaration
Acknowledgment
Table of Contents
Table of Figures

1. Chapter 1 : Introduction
1.1. Background ................................................................................................. Page No
1.2. Objective ..................................................................................................... Page No
1.3. Purpose, Scope and Applicability.............................................................. - -- 1.3.1.
Purpose
1.3.2.
Scope
1.3.3.
Applicability
1.4.
Achievements
2. Chapter 2: Survey of Technologies
3. Chapter 3: Requirement and Analysis
3.1.
Problem Definition
3.2.
Identification of Need
3.3.
Feasibility Study
3.4.
Project Planning & Scheduling using PERT CHART, Gantt Chart
3.5.
Software Requirement Specification ( SRS)
3.6.
Software Engineering Paradigm applied.
4. Chapter 4 : System Design
4.1.
Basic Modules
4.2.
Data Design
4.2.1.
Database Design
4.2.2.
Data Integrity and Constraints
4.3.
Diagrams ( Depending upon your project requirement)
4.3.1.
Control Flow Diagram
4.3.2.
Data Flow Diagram
4.3.3.
Entity Relationship Diagram
4.3.4.
State Diagram
4.3.5.
Class Diagram
4.3.6.
Collaboration Diagram

4.3.7.
Use Case Diagram
4.4.
Object Oriented Design
4.5.
Use Interface Design
5. Chapter 5 : Implementation
5.1.
Implementation Approaches
5.2.
Coding Details and Code Efficiency
5.2.1.
Code Efficiency
5.2.2.
Comments and Description
5.2.3.
Error Handling
5.2.4.
Validation & Checks
6. Chapter 6 :Testing Approach
6.1.
Testing techniques and testing strategies
6.1.1.
Unit Testing
6.1.2.
Integrated Testing
6.2.
Test Reports / Test Cases
6.3.
Modifications and Improvement
7. Chapter 7 :Security Issues
7.1.
Database Security
7.2.
User Level Security & Access Rights
8. Chapter 8 : Results and Discussion
8.1.
Cost Estimation of the Project
8.2.
User Documentation
8.3.
Report Generation
9. Chapter 9 : SWOT Analysis
9.1.
Strength
9.2.
Weakness
9.3.
Opportunity
9.4.
Threads
10. Chapter 10 : Conclusions
10.1. Limitations of the System
10.2. Future Scope and Further Enhancement of the Project
REFERENCES
GLOSSARY
APPENDIX

DESCRIPTION OF THE CONTENTS

1. Title page
Sample format of Title Page is given in page 15. Students should follow the given format.
2. Certificate of HOD & Project Guide
Sample format of Certificate is given in page 16. Students should follow the given format.
3. Certificate of Internal & External Examiner
Sample format of Certificate is given in page 17. Students should follow the given format.
4. Abstract
This should be one/two short paragraphs (100-150 words total), summarizing the project
work. It is important that this is not just a re-statement of the original project outline. A
suggested flow is background. Project aims and main achievements. From the abstract, a
reader should be able to ascertain if the project is of interest to them and, it should
presents results of which they may wish to know more details.
5. Declaration
Sample format of Declaration as per given in page 18. Students should follow the
given format.
6. Acknowledgements
This should express your gratitude to those who have helped you in the preparation of
your project. Sample see in page 19.
Table of contents: the table of contents given the readers a view of the detailed structure of
the report. You would need to provide section and subsection headings with associated
pages. The formatting details of these sections and subsections you will find in unit 2 of this
block.
Table of figures: list of all figures. Table, Graphs, Charts etc, along with their page numbers
in a table of figures.
Chapter 1: Introduction
The introduction has several parts as given below.
Background: A description of the background and context of the project and its relation to
work already done in the area. Summarise existing work in the area concerned with your
project work.

Objectives: Concise statement of the aims and objectives of the project. Define exactly
what you are going to do in the project; the objectives should be about 100 words.
Purpose, scope and applicability: the description of purpose, scope, and applicability are
given below:
Purpose: description of the topic of your project that answers questions on why
you are doing this project. How your project could improve the system its
significance and theoretical framework.
Scope: A brief overview of the methodology, assumption and limitations. You should
answer the question: what are the main issues you are covering in your project? What
are the main functions of your project?
Applicability: you should explain the direct and indirect applications of your
work. briefly discuss how this project will serve the computer world and people.
Achievements: Explain what knowledge you achieved after the completion of your work.
What contributions has your project made to the chosen area? Goals achieved-describes the
degree to which the findings support the original objectives laid out by the project. The
goals may be partially or fully achieved, or exceeded.
Chapter 2: Survey of Technologies
In this chapter survey of technologies you should demonstrate your awareness and
understanding of available technologies related to the topic of your project. You should give
the detail of all the related technologies that are necessary to complete your project. you
should describe the technologies available in your chosen area and present a comparative
study of all those available technologies. Explain why you selected the one technology for
the completion of the objectives of your project.
Chapter 3: Requirements and Analysis
Problem Definition: Define the problem on which you are working in the project.
Provide details of the overall problem and then divide the problem in to sub-problems.
Define each sub-problem clearly.
Identification of Need: Initiation is where there is an identified need for a new system
Feasibility Study: The feasibility study is used to determine if the project should get the
go-ahead. If the project is to proceed, the feasibility study will produce a project plan
and budget estimates for the future stages of development.
Planning and Scheduling: planning and scheduling is a complicated part of software
development. Planning, for our purposes, can be thought of as determining all the small
tasks that must be carried out in order to accomplish the goal. Planning also takes into
account, rules, known as constraints, which, control when certain tasks can or cannot
happen. Scheduling can be thought of as determining whether adequate resources are

available to carry out the plan. you should show the GANTT chart and program evaluation
review technique (PERT).
Software Requirements Specification: In this phase you should define the requirements of
the system, independent of how these requirements will be accomplished. The requirements
specification describes the things in the system and the actions that can be done on these
things. Identify the operation and problems of the existing system. See Details in page 12
Software Engineering Paradigm applied : In this project, which software
engineering model you are used and why. Explain your project according to this model.
Chapter 4: System Design
Describes desired features and operations in detail, including screen layouts, business
rules, process diagrams, pseudo code and other documentation.
Basic Modules: you should follow the divide and conquer theory, so divide the overall
problem into more manageable parts and develop each part or module separately. When all
modules are ready. You should integrate all the modules into one system. In this phase, you
should briefly describe all the modules and the functionality of these modules.
Data Design: data design will consist of how you organize, managing and manipulate the
data.
Database Design: define the structure and explanation of schemas used in your
project.
Data Integrity and Constraints: define and explain all the validity checks
and constraints you are providing to maintain data integrity.
Diagrams: Student draws the diagrams, Depending upon your project requirement).
Object Oriented Design: Give the detail of Object Oriented Approach used in your project.
Define how many classes used in your project; also write which OOPs features you are used
in your project, like Inheritance, Overloading, Polymorphism, etc.
User Interface Design: define user, task, environment analysis and how you intend to map
those requirements in order to develop a user interface. Describe the external and internal
components and the architecture of your user interface. Show some rough pictorial views
of the user interface and its components.
Chapter 5: Implementation and Testing
Implementation Approaches: define the plan of implementation, and the standards you
have used in the implementation.

Coding Details and Code Efficiency: students not need include full source code, instead,
include only the important codes (algorithms, applets code, forms code etc). the program
code should contain comments needed for explaining the work a piece of code does.
Comments may be needed to explain why it does it, or, why it does a particular way.

Code Efficiency: you should explain how your code is efficient and how you have
handled code optimization.
Comments and Description : Should have comments with functional description which
include the input, output, total function calls to/from other functions, function
parameters, description of main variable, data types, logic description etc.
Error Handling : Explain exceptions handling and conditional checking.
Validations & Checks: Write the detail of all validations, like date, range, numberalphabet & expression validations and also mentions the check for input data.
Chapter 6: Testing Approach
Testing approach: testing should be according to the scheme presented in the system
design chapter and should follow some suitable model-e.g., category partition state
machine-based. Both functional testing and user-acceptance testing are appropriate.
Explain your approach of testing.
Unit Testing: unit testing deals with testing a unit or module as a whole. This would
test the interaction of many functions but, do confine the test within one module.

Integrated Testing: brings all the modules together into a special testing
environment, then checks for errors, dugs and interoperability. It deals with tests for
the entire application. Application limits and features are tested here.
Test Reports: explain the test results and reports based on your test cases, which should
show that your soft ware is capable of facing any problematic situation and that it works
fine in different conditions. Take the different sample and show the outputs.
Modifications and Improvements: once you finish the testing you are bound to be faced with
dugs, errors and you will need to modify your source code to improve the system. Define what
modification you implemented in the system and how it improved your system.

Chapter 7 : Security Issues: Discuss real-time considerations and security issues related to
your project and explain how you intend avoiding those security problems. What are your
security policy plans and architecture?
Database Security: The student should mention the how your data is secure. Write the
deferent security levels provided by you and your selected database software.

User Level Security & Access Rights: The student should clearly emphasize the various
levels of security measures implemented in the project.
Chapter 8: Results and Discussion
Cost Estimation of the Project: The student need to incorporate the estimated cost of the
project using the suitable mechanism/model given in the Software Engineering, such as
COCOMO.

User Documentation: Define the working of the soft ware; explain its different
functions, components with screen shots. The user document should provide all the details
of your product in such a way that any user reading the manual. Is able to understand the
working and functionality of the document.
Report Generation : The project report should include the various sample report for
ready reference.
Chapter 9 : SWOT Analysis
Explain the Strength, Weakness, Opportunity and Threads of your project, 50-80 words for
each.
Chapter 10: Conclusions The conclusions can be summarized in a fairly short chapter (1
to 3 pages). This chapter brings. Together many of the points that you would have made in
the other chapter.
Limitation of the System: Explain the limitations you encountered during the testing of
your soft ware that you ware not able to modify. List the criticisms you accepted during
the demonstrations of your software.
Future scope and further enhancement of the project: Firstly, new areas of investigation
prompted by developments in this project, and secondly, parts of the current works that
were not completed due to time constraints and/or problems encountered.
REFERENCES
It is very important that you acknowledge the work of others that you have used or adapted
in your own work, or that provides the essential background or context to your project.
The use of reference is the standard way to do this. Please follow the given standard for the
reference for books. Journals, and online material.
GLOSSARY
If you use any acronyms, abbreviations, symbols, or uncommon terms in the project reports
then their meaning should be explained where they first occur. If you go on to muse any of
them extensively then it is helpful to list them in this section and define the meaning.

10

APPENDICES
These may be provided to include further details of results of results, mathematical
derivations, certain illustrative parts of the program code (e.g.-class interfaces), user
documentation etc.
In particular, if there are technical details of the work done that might be useful to
others who wish to build on this work, but that are not sufficiently important to the
project as a whole to justify being discussed in the main body of the project, then they
should be included appendices.

11

Software Requirement Specification

1 INTRODUCTION
1.1 Product Overview
1.2 Purpose
1.3 Scope
1.4 Reference
1.5 Definition And Abbreviation
2 OVERALL DESCRIPTION
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
2.4 General Constraints
2.5 Assumptions and Dependencies
3 SPECIFIC REQUIREMENTS
3.1 External Interface Requirements
3.1.1 User Interfaces
3.1.2 Hardware Interfaces
3.1.3 Software Interfaces
3.1.4 Communications Protocols
3.1.5 Memory Constraints
3.1.6 Operation
3.1.7 Product function
3.1.8 Assumption and Dependency
3.2 Software Product Features
3.3 Software System Attributes
3.3.1 Reliability
3.3.2 Availability
3.3.3 Security
3.3.4 Maintainability
3.3.5 Portability 3.3.6
Performance
3.4 Database Requirements
3.5 Other Requirements
4 ADDITIONAL MATERIALS
SRS for UMS (University Management System):
1. GENERAL DESCRIPTION UMS is University Management System for managing the
records of the alumnis of the university as well as staff, faculty and higher authorities.

12

1.1 Purpose The purpose for developing this type of software or introducing this
UMS is to facilitate everyone who is concerned with the university.
1.2 Scope The scope of UMS is global i.e. it should be able to be accessed from
anywhere through internet i.e. registered users must be able to login to their
accounts by directly accessing the universitys website and then signing in with their
username and password anytime and anywhere.
1.3 Abbreviation UMS University Management System
1.4 Overview As the ums is able to have a user interface. It should have a drop down
boxes and if we drag mouse on any control at our welcome screen information
regarding that the control should be displayed. Help menu should be there. As a
teacher it should provide them to upload the various assignments and the attendance
of the students. As a developer it should make a user interface which is user friendly.
He should make the UMS as simple as he can. Backup at the main server should be
made.
2. OVERALL DESCRIPTION
2.1 Product Perspective product i.e. UMS should be able to provide a basic and easy
interchange of information i.e. it should be able to remove the communication gaps
between a teacher and the student. It should have chat facilities for all the users that
are online. It should be compatible with all the operating systems.
2.2 Product Functions - The following are the product functions of the UMS:
The UMS login box should on the official website of the university.
The password field should be secured.
After signing in all updates and new announcements for users should be
displayed. By clicking on the dropdown box of the options the user should be able
to view progress reports, assignments, notes, attendance, placement services and
results. User should be able to change the passwords.
Web pages should support pdf, ppt, doc and similar supported formats so that they
can be easily downloadable and unloadable.
2.3 User Characteristics A user can only have his/her registration number as
username so if he joins the university then only he can then only he can login. This
prevents misuse, unauthorized access and hacking of the product.
2.4 General Constraints Server capacity is how many users can access or can be
online at once. More is the number of users more will be the network traffic and
hence the server comes in a down state. Personal firewall and updating is a tough
task, it should be such that it should not block the network traffic, making the system
slower. Firewall of the UMS should not collide with the firewall of the user system.

13

2.5 Assumptions and Dependencies UMS should work even at when the network traffic is
high. Server should have a power backup as well as a database backup. The UMS should be
compatible with most of the operating systems i.e. previous and latest ones.
3. SPECIFIC REQUIREMENTS
3.1 External Interface Required
3.1.1
User Interfaces The external users are the students and the teachers of the
university. The students can have an access to their accounts for their attendance,
assignments etc. The teachers have also an account to access their account for
uploading of the students attendance and the assignments to be submitted by them.
3.1.2
Hardware Interfaces The external hardware interface used for accessing
the UMS is the personal computers of the teachers and the students. The PCs may be
laptops with wireless LAN as the internet connections provided will be wireless.
3.1.3
Software Interfaces The Operating Systems can be any version of
Windows, Linux, Unix or Mac which supports TCP/IP protocols.
3.1.4
Communication Interfaces The communication interface is a local
area network through wireless network routers.
3.2 Performance Requirements The PCs used must be at least Pentium 4 machines so
that they can give optimum performance of the product.
3.3 Design Constraints The constraints at the designing time are that the needs of the
university students and the teachers may keep on changing so the designers must
keep this in view and design the product in this way that it is easily updatable.
3.4 Attributes The following are the attributes of the product UMS:
It should be equipped with current and archive database.
All records can easily be updated.
It should have its personal firewall.
It should facilitate student with updating his/her account, downloading or
uploading of assignments from anywhere.
It should also do the same for teachers they can also have their pay checks online
i.e. UMS should be capable of online transaction.
3.5 Other Requirements The software is such that as the time goes by the need of
the university management, students and teachers may keep on changing thus it is made
to change from time to time.
4 ADDITIONAL MATERIALS
Data Flow Diagram for UMS:

14

Gyan Ganga College of Technology,

Jabalpur (M.P.)

A
MAJOR PROJECT/SINOPSIS REPORT

TRAINING & PLACEMENT

MANAGEMENT
Submitted to the

Department of Computer Science & Engineering

Submitted by
Nandini Raikwar ( 0208CS121078)
Neha Sharma
( 0208CS121080)
Priyanka Gontiya ( 0208CS121099)

Under
Guida
nce of

Vineet Chaturvedi
Asst.Professor
in partial fulfillment of the requirements for the award of the degree of

BACHELOR OF ENGINEERING
(Computer Science & Engineering)
VII / VIII Semester

under

RAJIV GANDHI PRODYOGIKI VISHWAVIDYALAYA, BHOPAL

(M.P.)
15

Gyan Ganga College of Technology,

Jabalpur

Department of Computer Science & Engineering

Certificate
This is to certify that the Major Project report entitled Training &
Placement Management submitted by Nandini Raikwar, Neha Sharma,
Priyanka Gontiya has been carried out under my guidance & supervision. The
project report is approved for submission towards partial fulfillment of the
requirement for the award of degree of Bachelor of Engineering in
Department of Computer Science & Engineering from
Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal (M.P).

Prof.Vineet Chaturvedi
Project Guide
Dept. of CSE

Dr.Neeraj Shukla
HOD
Dept of CSE,GGCT

16

Gyan Ganga College of

Technology, Jabalpur

Department of Computer Science & Engineering

Certificate
This is to certify that the Major Project report entitled
Online Technical Discussion Forum is submitted
Nandini Raikwar, Neha Sharma for the partial fulfillment of
their Requirement for the award of degree of Bachelor of
Engineering in Department of Computer Science&
Engineering from Rajiv Gandhi ProudyogikiVishwavidyalaya,
Bhopal (M.P).

Internal Examiner

External Examiner

Date :

Date :

17

Declaration
We hereby declare that the project entitled Online Technical
Discussion Forum which is being submitted in partial fulfillment of the
requirement for award of the Degree of Bachelor of Engineering in Computer
Science

and

Engineering

to

RAJIV

GANDHI

PROUDYOGIKI

VISHWAVIDYALAYA, BHOPAL(M.P.) is an authentic record of our own

work done under the guidance of Prof.Vineet Chaturvedi, Department of
Computer Science & Engineering, GYAN GANGA COLLEGE OF
TECHNOLOGY, JABALPUR..

The matter reported in this Project has not been submitted earlier
for the award of any other degree.

Dated : dd/mm/yyyy
Place :

Karamveer Singh(0208CS121062)

18

Acknowledgment
We sincerely express indebtedness to esteemed and revered guide
Vineet Chaturvedi, Assistant Professor for his invaluable guidance,
supervision and encouragement throughout the work. Without his kind
patronage and guidance the project would not have taken shape.
We take this opportunity to express deep sense of gratitude to
Dr.Neeraj Shukla, Head of Department of Computer Science &
Engineering for his encouragement and kind approval. Also we thank him
in providing the computer lab facility. We would like to express our sincere
regards to him for advice and counseling from time to time.
We owe sincere thanks to all the lecturers in Department of
Computer Science & Engineering for their advice and counseling time
to time.

Dated : dd/mm/yyyy
Place :

<<student_name>>
<<roll no>>

Chapter 1

Introduction
The project entitled online technical discussion forum is
aimed at developing online forum for the group discussion.
This is web-based tool.
Any user can post the doubts topic and can reply for the
other user doubts.this is useful for a school or a department
or for

The online technical discussion forum is useful for the beginners

to get information related to various topics. There is a centralized
database in which all the information is managed. The administrator acts
as the highest authority and has the rights to update the database.

Our site can help the new comers about getting information
about programming languages. It will also be useful for getting
information about various technical questions. Users can satisfy their
needs of getting information related to various programming languages
from a single source. To make a form that give information about
various technical questions. The questions are based on various
programming languages. The various questions are like how to setup the
languages, data types etc.

Now a days, computers are mostly used in every organization

for their database management, for this purpose client/server
architecture and object oriented programming have become very popular
technologies for customized software.

1.1 Background
Present State:

No Software present at all.

Time consumed in accessing the records of the students.
Manual creation of lists of eligible and not eligible students.
Students are informed by sending mail to them manually.
Headache of placement cell is more to manage the information of
students manually.
More time taken to registration of students on registration forms.

After implementation of project:

 Easy to use GUI.

Students can register online no rush for registration in Placement
department.

Respective eligible students can get informed by email automatically.

List of eligible students can be made on single click.
Report of students according to need of placement cell can be

generated easily.
Burden of Placement cell decreases.

1.2Objective
The objectives of the system are To reduce paperwork.
Reduced operational time.
Increased accuracy and reliability.
Increased operational efficiency.
Data security.
This software package can be readily used by non-programming
personal avoiding human handled chance of error.

1.3 Purpose,Scope
1.3.1 Purpose
The significance of project is to automate the Placement
process of the institute.
There is no worry of checking the Placement department time
to time.
Students get emails for updates related to companies for which
they are eligible.
Placement cell also can create lists on the basis of requirement
of company there is no need to do it manually.
Placement reports i.e. Company wise report, Branch wise
report etc.

1.3.2 Scope
This project has a large scope as it has the following
help in making it easy to use, understand and modify it.

Automation of Placement Procedure

No Need to do Paper Work.
To save the environment by using paper free
work.
To increase the accuracy and efficiency of the
placement
procedure.
Management of Student Data.

Chapter 2
20

Survey of Technologies
About the Java Technology
Java technology is both a programming language and a platform.

The Java Programming Language

The Java programming language is a high-level language that can be
characterized by all of the following buzzwords:
Simple

Architecture neutral

Object oriented

Portable

Distributed

High performance

Interpreted

Multithreaded

Robust

Dynamic

Secure

With most programming languages, you either compile or interpret a

program so that you can run it on your computer. The Java programming
language is unusual in that a program is both compiled and interpreted.
With the compiler, first you translate a program into an intermediate
language called Java byte codes the platform-independent codes
interpreted by the interpreter on the Java platform. The interpreter parses
and runs each Java byte code instruction on the computer. Compilation
happens just once; interpretation occurs each time the program is
executed.

The Java Platform

A platform is the hardware or software environment in which a

program runs. We've already mentioned some of the most popular

platforms like Windows 2000, Linux, Solaris, and MacOS. Most
platforms can be described as a combination of the operating system
and hardware. The Java platform differs system and hardware. The Java
platform differs from most other platforms in that it's a software-only
platform that runs on top of other hardware-based platforms
.
The Java platform has two components
The Java Virtual Machine (Java VM)
The Java Application Programming Interface (Java API)
Java VM is the base for the Java platform and is ported onto various
hardware-based platforms.
The Java API is a large collection of ready-made software components
that provide many useful capabilities, such as graphical user interface
(GUI) widgets. The Java API is grouped into libraries of related classes
and interfaces; these libraries are known as packages.

Net beans
All the tools software developers need to create cross-platform Java
desktop, enterprise and web applications. Runs on Windows, Linux,
MacOS, as well as Solaris. It is easy to install and use, works right out
of the box -- and it is open-source and free.

Features of the Net Beans (Rich Client) Platform

With the Net Beans Platform, developers get to concentrate
on the important parts of an application - the business logic that makes

that application unique. The result is a huge savings in time and effort.
Some of the features of the platform are:

User interface management: Windows, menus,

toolbars and other presentation components are provided by the
Platform. Developers write actions and components that the system will
manage - saving time, and producing cleaner, more bug-free code.

Data and presentation management: The Net

Beans Platform contains a rich toolset for presentating data to the user
and manipulating that data.
Setting management: Saving and restoring settings - even complex
business objects - is safe, simple, transparent and often automatic

Graphical Editing: Creating drag and drop, graphical views

of data is a snap with the graph library

The Editor: Available as an extension to the Platform,

applications built on Net Beans can use the Net Beans Editor, a powerful
and extensible toolset for building custom editors.

The Wizard framework: A toolset for easily building

extensible, user-friendly Wizards to guide users through more complex
tasks.

Storage management: An abstraction of file-based data

access. "Files" in the Net Beans paradigm may be local files, or exist
remotely, for example, on an FTP server, CVS repository, in an XML
file or in a database. Where this data is stored is completely transparent
to other modules that work with this data.

A huge selection of additional components:

such as versioning support, specialized editors, specialized UI
components, remote data access via FTP and other transports, and
convenient ways to work with a variety of Java and internet
technologies are available as plug-in any application can use.

Internet-based update delivery: Net Beans-based

applications can use Java Web Start technology to deliver custom sets of

modules based on a user's role, for complex applications. And a Web

Start enabled application is always up-to-date and combines the
advantages of centralized management and deployment with the
advantages of a rich client user experience. For non-Web Start
applications, an optional component is the AutoUpdate module, which
downloads updates or new functionality via the web.

Building on the Net Beans Platform

Developing applications on top of the Net Beans Platform
means you are developing on top of the Net Beans IDE's core. The Net
Beans Platform is a generic web application, and most web applications
have common requirements - menus, document management, settings
and so forth. Instead of writing the same code over and over again, write
modules to implement what you need, bundle them up with the Net
Beans Platform, and you have a beautiful, branded, cross-platform
application.

Consistency
Net Beans-based applications are writing-once, run-anywhere.
You get prebuilt components for free and you solve common problems
by reusing, mixing and matching them. Use the platform and the
modules you develop as the basis for multiple applications that share
common logic. The Net Beans Platform is a solid foundation and set of
standards for clear design.

Modularity
Applications based on the Net Beans Platform can install
modules dynamically, so users no longer need to download the entire
application to get an upgrade or a new release. You can even assemble
an application from already existing modules and benefit from the opensource work already done by others. There are lots of useful modules
written by the Net Beans community (task list, spellchecker, etc.) that
are ready to be embedded.

Chapter 3

Requirement &
Analysis
3.1 Problem Definition

In Various colleges, training and placement officers have to

manage the CVs and documents of students for their training
and placement manually.

TPOs have to collect the information of various companies who

want to recruit students and notify students time to time about
them.

TPOs have to arrange CVs of students according to various

streams and notify them according to company requirements.

If any modifications or updating are required in CV of any

student, it has to searched and to be done it manually.

3.1Identification of Need:
Our main focus on some of the features is: Home

Profile

TPO

TPO

Student Entry

List of Companies

Selected Candidates

Campus Information
Preliminary Investigation:
The system requires below mentioned options:

Home This will be the home page for all the users and for
opting any available choices. This will help us login into own
Account and then carrying out any operations that are available
after login.

Student Entry This page is available to create and view the

profiles of the students under various courses. Profile page also
provides with the option of editing. The editing is possible of any
student details.

TPO View all the companies available via this page. One can
view the campus interviews that are going to be arranged or
either can have the view of the selective candidates.

Search This is very interesting option available, with this

option one can search candidates depending on the company
name criteria.

Company Maintenance of the company information and at the

same time the selection status for the company.

This site is an indispensable work for understanding different

things and how those things interact with each other and how the whole
system works. This is basically a practical implementation of the work,
which is already being carried out. But we are implementing with new
tools, so it is different.

3.3 Feasibility Study

Feasibility is the determination of whether or not a project is

worth. The process following in making this determination is called a
feasibility study. A feasibility study is conducted to select the best
system that meets performance requirements. Once it has been
determined that a project is feasible, the analyst can go ahead and
prepare the project specification which finalizes project requirements.
The feasibility of the system developed has been discussed in the
following points:

Operational Feasibility
The system being developed is using Netbeans as a front-end
tool and oracle 10g as a back-end tool. The system works under
Windows environment PCs which is quite common today and the users
of the system are familiar with this environment and also the developed
system is menu-driven and user friendly.
User does not have to constantly worry about duplication/loss of
data since the system developed would prevent this if it happens.
Information about any customer can be accessed whenever
required by using menus. This makes the system user friendly and even
a user who doesnt know computer can access the required information.
Advanced security measures are taken in this system to prevent
unauthorized access, malicious destruction of data.
Due to these reasons the accepted system making operationally
feasible.

Technical Feasibility
Technical analysis showed that the hardware and software
requirement is sufficient and Netbeans is suitable for the project.
The system will be developing in the present environment that is
Windows. The system runs on Pentium Computers.
System will be developed using Netbeans as front-end tool;
which has various features like:


Data access features allow us to create
databases and front end applications for most popular
database formats.

Finished application is a true .exe file that uses a run time

dynamic link library (DLL) that we can freely distribute.
Oracle 10g is the back-end tool used in the system. It is a
relational database package, which is known for security and control. It
maintains the integrity of the database; hence there is consistency and
reliability.
Since the manual work is required in the existing system and
also security could not be maintain in the existing system so it is feasible
to switch over to proposed new system.

Economic/Financial Feasibility
Highlights of the economic feasibility are as follows:

There is no direct cost since the developed

system does not require any special hardware e.g. dedicated
computer system.

Because of the nature of the system,

activities do not require a machine all the time during a
normal working day.

The system does not require any new

software since licensed Netbeans and Apache Derby for
Windows 2000 Server are already there in the computer
center under WINDOWS operating system. Software
developed under these environments is more user friendly.

3.4 Project Planning

The project can be decomposed into following:Organization Selection The first step is for selection of the
company which took me 10 days
Project / Problem Selection The problem statement was
assigned by the company.
Information collect The necessary information required for
the project has been collected in parts and by me by
interaction with the client.
Analysis of Information The information thus required in the
project was refined and set aside for usage.
Design of the application The design of the application took
time but was in satisfaction with client.
Review the Specification The specification refined was again
visited for changes.
Coding the coding required has been done.
Verification/Validation proper verification and validation has
been done on the form.
Testing the unit testing and integration testing was done and
then the code handed over for black box and white box
testing.

3.5 Project Scheduling

The estimate of no. of days for each task as follows: -Selection
of Organization-10 days, Selection of problem-7days, Collection of
information 25 days, Analysis of information 10 days, Designing the
application 40 days, Coding for the application -45 days, Review the
specification 7 days, Verification/Validation 7 days, Testing -18 days,
Dummy activity 5 days, Implementation and follow-up 10 days, user
training 7 days.

PERT Chart & GANTT Chart

Pert Chart
The success of any large-scale project is very much dependent upon the
quality of planning, scheduling and controlling of the various phase of
the project. Unless some type of planning and coordinating tool is used,
the number of phases does not to be very large before management starts
losing controls. One such OR tool used on large-scale project to aid
management in expanding and controlling the utilization of personal,
material, facilities, and time is the program evaluation and review
technique (PERT). This technique is used to pinpoint critical areas in a
project necessary adjustments can be made in order to meet the schedule
completion date the project.
Project scheduling by PERT consist of four main steps:Planning
Scheduling
Allocating of resources
Controlling
The Pert chart of the overall implementation is shown in following
figures:NODE

DESCRIPTION

UTILIZE THE NO. OF DA

Selection of organization

10 Days

Selection of problem

7 Days

Collecting the information

25 Days

Analysis of information

10 Days

Designing of the Application

40 Days

Coding for the Application

45 Days

Review the specification

7 Days

Validation / Verification

7 Days

Testing

18 Days

10

Dummy activity

5 Days

THE PERT Chart is representing the interdependencies among

tasks. The PERT provides quantitative tools that allow the
software planner to determine the critical path. The PERT Chart
use is justified in large projects.
THE PERT Chart Diagram

Node 1 - Organization Selection

Node 2 - Proj / Prob Selection
Notations:
Notations : =>Critical Path
->

Activity

--- > Dummy Activity

Node
Node 3 - Information collect
Node 4 Analysis of Information
Node 5 - Design of the application
Node 6 - Review the Specification
Node 7 - Coding
Node 8 - Verification/Validation
Node 9 Testing

Node 10 Dummy Activity

GANTT Chart
Which uses a calendaroriented chart to represent the project schedule.
Each activity is represented as a bar in the calendar, starting from the
starting date of activity and ending at the ending date for that activity.
The start and end of each activity become milestones (or check points)
for the project. Coloring each milestone when completed can represent
progress. The milestone or checkpoints are usually at the completion of
each task.
Let us draw the Gantt chart for each task identified in these project .the
horizontal bars indicates the duration of each task and all project tasks
are listed in the left handed column. We estimate the no. of days for each
task as follows: -Selection of Organization-10 days, Selection of
problem-7days,Collection of information 25 days ,Analysis of
information 10 days ,Designing the application 40 days ,Coding for
the application -45 days , Review the specification 7days,
Verification/Validation 7 days, Testing -18 days , Dummy activity 5
days , Implementation and follow-up 10 days, user training 7 days
Drawback of GANNT Chart: The main drawback of Gantt chart is that it
does not depict the dependency relationships among the different
activity.

3.5 Software Requirement Specification

Hardware Interface Requirement

Processor: A general-purpose microprocessor with 1GHz or Higher

clock speed.

Primary Memory: 1 GB or Higher RAM.

Secondary Memory: 10 GB of Hard Disk Space (including Oracle

installation).

Microsoft Windows XP Professional or Server 2003.

A Modem and internet connection.

A LAN card.

Software Interface Requirement

Servers - Microsoft Windows 2000

Clients - Microsoft Internet Explorer 6.0

Tools Netbeans 6.8

Software System Attributes

The various factors, which influence the software, are termed as
software factors. They can be broadly divided into two categories. The
classification is done on the basis of measurability. The first category of
the factors is of those that can be measured directly such as number of
logical errors and the second category clubs those factors which can be
measured only indirectly for example maintainability but the each of the
factors are to be measured to check for the content and the quality
control. Few factors of quality are available and they are mentioned
below.

 Correctness - extent to which a program satisfies its specification and

fulfills the client's objective.
Reliability - extent to which a program is supposed to perform its
function with the required precision.
Efficiency - amount of computing and code required by a program to
perform its function.
Integrity - extent to which access to software and data is denied to
unauthorized users.
Usability- labor required to understand, operate, prepare input and
interpret output of a program.
Maintainability- effort required to locate and fix an error in a program.
Flexibility- effort needed to modify an operational program.
Testability- effort required to test the programs for their functionality.
Portability- effort required to run the program from one platform to
other or to different hardware.
Reusability- extent to which the program or its parts can be used as
building blocks or as prototypes for other programs.
Interoperability- effort required to couple one system to another.
Auditability- ease with which the conformance to standards can be
verified.
Accuracy- precision of computations and control.
Communication commonality- degree to which standard interfaces,
protocols and bandwidth are used.
Completeness- degree to which full implementation of functionality
required has been achieved.

 Conciseness- programs compactness in terms of lines of code.

Consistency- use of uniform design and documentation techniques
throughout the software development.
Data commonality- use of standard data structures and types
throughout the program.
Error tolerance damage done when program encounters an error.
Execution efficiency- run-time performance of a program.
Expandability- degree to which one can extend architectural, data and
procedural design.
Hardware independence- degree to which the software is de-coupled
from its operating hardware.
Instrumentation- degree to which the program monitors its own
operation and identifies errors that do occur.
Modularity- functional independence of program components.
Operability- eases of programs operation.
Security- control and protection of programs and database from the
unauthorized users.
Self-documentation- degree to which the source code provides
meaningful documentation.
Simplicity- degree to which a program is understandable without much
difficulty.
Software system independence- degree to which program is
independent of nonstandard programming language features, operating
system characteristics and other environment constraints.

 Traceability- ability to trace a design representation or actual program

component back to initial objectives.
Training- degree to which the software is user-friendly to new users.
There are various checklists for software quality. One of them was
given by Hewlett- Packard that has been given the acronym FURPS
for Functionality, Usability, Reliability, Performance and Supportability.
Functionality is measured via the evaluation of the feature set and the
program capabilities, the generality of the functions that are derived and
the overall security of the system.
Considering human factors, overall aesthetics, consistency and
documentation assesses usability. Reliability is figured out by evaluating
the frequency and severity of failure, the accuracy of output results, the
mean time between failures (MTBF), the ability to recover from failure
and the predictability of the program. Performance is measured by
measuring processing speed, response time, resource consumption,
throughput and efficiency.
Supportability combines the ability to extend the program,
adaptability, serviceability or in other terms maintainability and also
testability, compatibility, configurability and the ease with which a
system can be installed.

3.6 Software Engineering Paradigm

Iterative Model:

Iterative and Incremental development is any combination of

both iterative design or iterative method and incremental build model for
software development. The combination is of long standing and has
been widely suggested for large development efforts. For example, the
1985 "During software development, more than one iteration of the
software development cycle may be in progress at the same time." and
"This process may be described as an 'evolutionary acquisition' or
'incremental build' approach." The relationship between iterations and
increments is determined by the overall software development
methodology and software development process. The exact number and
nature of the particular incremental builds and what is iterated will be
specific to each individual development effort.

Iterative development model

Iterative and incremental development are essential parts of

the Modified waterfall models, Rational Unified Process, Extreme
Programming and generally the various agile software
development frameworks.
It follows a similar process to the plan-do-check-act cycle of business
process improvement.

Chapter 4

System Design
4.1 Basic Modules
Module 1:
Home- This will be the home page for all the users and for

opting any available choices. This will help us login into own
Account and then carrying out any operations that are available
after login.
Module 2:
Student Entry This page is available to create and view the
profiles of the students under various courses. Profile page also
provides with the option of editing. The editing is possible of any
student details.
Module 3 :
TPO View all the companies available via this page. One can
view the campus interviews that are going to be arranged or
either can have the view of the selective candidates.
Module 4 :
Faculty- Maintenance of the student information and entry
Of the student information.

4.2 DATA DESIGN

4.2.1 Data integrity constraints
Primary key is the enrollment number for the student which is unique
Companyname is unique for the company.
4.2.2 DATABASE DESIGN
Student Table
CREATE TABLE STUDENT (ENROLL VARCHAR2(50) NOT NULL,
"NAME" VARCHAR2(50) NOT NULL,

"YEAR" VARCHAR2(50) NOT NULL, SEM NUMBER(38) NOT

NULL, BRANCH VARCHAR2(50) NOT
NULL, EMAIL VARCHAR2(50) NOT NULL, CGPA NUMBER(50),
HSC NUMBER(126), SSC
NUMBER(50), PRIMARY KEY (ENROLL));
Company Table
CREATE TABLE CAMPUS (ADDRESS VARCHAR2(50) NOT
NULL, URL VARCHAR2(50) NOT NULL, HR
VARCHAR2(50) NOT NULL, EMAIL VARCHAR2(50) NOT NULL,
PHONE VARCHAR2(50) NOT NULL,
"NAME" VARCHAR2(50) NOT NULL, PRIMARY KEY ("NAME"));
Campus Table
create table `tpo`.campus
(
cname VARCHAR(100),
dateofcampus DATE,
reqc VARCHAR(5),
highsch VARCHAR(5),
highsecondary VARCHAR(5),
be VARCHAR(5),
passingyear VARCHAR(4),
status BIT(1) default b'0' not null
)

4.3 DATA DIAGRAM

USE CASE DIAGRAM

4.4 USER INTERFACE DESIGN

HOME PAGE

ADMIN PAGE

FACULTY PAGE

STUDENT LOGIN

ADMIN DASHBOARD

Chapter 5
Implementation &
Testing

Chapter 6
Testing Approach

Chapter 7

Security Issues
Database security

Database is password protected.

No one can access until they are aware of the Username and
password .

GUI is only in English.

Login and Password is used for identification .

This system is working for single server.

Chapter 8

Result
&
Discussion
Cost Estimation of the Project
By taking reference from the software engineering book named
SOFTWARE
ENGINEERING BY Roger S. Pressman, (Fourth Edition), An
Intregated Approach To
Software Engineering By Pankaj Jalote,(second edition); cost of the
designed application has been done.
The following table provides the rough estimates of the average number
of lines of code required to build one function point in various
programming languages
Programming Languages LOC/FP (average)
I have taken graphical user interface Netbeans as front-end tool.
Therefore, I take cost per LOC/FP as 4 Rs.
Now the Estimated Line Of Code (For vital part of the Project) is

No. Of pages =
Lines are =
Estimated Line Of Code is =
Therefore the estimated cost is = 4000 * 4 = Rs. 16000
So the Approx estimated cost of project is = Rs. 16,000/-

Chapter 9

SWOT
ANALYSIS
Strength
The strength of project is that it provides the best solution to the
Training and placement Information Provider to any student.

Weakness
Due to lack of resources cannot handle clients beyond a certain limit.

Opportunity
This project will be extended in future and can be integrated on online
and mobile. Through mobile, students would be able receive any kind
of information.

Threats
If any trouble occur in this software all the data and information of the
software is lost.

Refrences
The time when we started and the time till we ended we read and
referred all these books, publications and Internet.
Herbert Scheldt

- Java Complete Refrence

Pressman RS - Software engineering and design

Galgotia Korth Publication - Database system concept