Report

Venus..
“Providing VISION for Campus Recruitment”

Submitted in B.Tech VI Semester.
Year 2009-2010
University For Women:

University with a difference
Project Guide Submitted by

Ms.Manisha Agarwal Nimisha Agarwal
Niyati Jha
Sakshi Mathur
Saloni Gupta
Apaji Institute of Mathematics and Applied Computer Technology

Banasthali Vidyapith
Year 2007-11
Acknowledgement
We extend our thanks to to Prof. G.N. Purohit , Dean Apaji Institute, for his inspiration ,
guidance , for the constructive suggestions , affectionate guidance in our work , extra
machine time and extended facility provided without which it would have been very difficult
to complete the project.
We are deeply indebted to our project guide Ms. Manisha Agarwal for all the guidance and
encouragement she gave in the subsequent months . Her help and advice has helped us
immensely in working of this project to our satisfaction.
Whatever intellectual effort may be reflected from this report is the direct result of the
informative and stimulating discussions that we had in the course of the semester.
Last but not the least we would like to thanks all our friends for giving useful suggestions
and ideas for improving our work.
Nimisha Agarwal
Niyati Jha
Sakshi Mathur
Saloni Gupta
Venus…Providing VISION for Campus Recruitment

Certificate
It is certified that the work contained in the project entitled “ Venus… Providing VISION
For Campus Recruitment “, by “Nimisha Agarwal, Niyati Jha, Sakshi Mathur, Saloni
Gupta ”, has been carried out under our supervision at Banasthali University. It is bonafide
work of them.
Project Guide Prof.G.N.Purohit

Ms. Manisha Agarwal Dean
(Lecturer) AIM & ACT

Synopsis
Name of Students: Nimisha Agarwal (IT-6072)

Niyati Jha (CS-5884)
Sakshi Mathur (IT-6090)
Saloni Gupta (IT-6092)
Degree for which submitted : B.Tech in Information Technology.
Department : AIM & ACT
Project Title : Venus… Providing VISION For Campus Recruitment.
Name of Project Supervisor : Ms. Manisha Agarwal
Month and Year of Project Submission : April , 2010

Contents
Title Page No.
1. Introduction
1.1 Objective and Scope of Project
1.2 Theoretical Background
1.3 Problem Definition
2. Analysis
2.1. System Planning
2.2. System Requirement Specification
3. Design
3.1. System Design Specification
3.2. Module description according to team members
4. Coding
5. Implementation
5.1. Methodology Adopted
5.2. Input and Output Screen Design
6. Testing
6.1. Methodolies used for testing
6.2. Testing Techniques
6.3. Application Function Tests
6.4. Test Report
7. Documentation
7.1. User Operational Manual
7.2. Read Me
7.3. Limitations
8. Annexure
8.1. References
8.1.1. Bibliography
8.1.2. Websites

Introduction

1.1 Objective & Scope of Project:
The purpose of our web application “Venus…Providing VISION For Campus

Recruitment” developed for “Banathali University ” is:
• To provide all campus placement related information to the students of Banasthali

Univesity.
• To maintain a database of students of (Aim and Act Dept) final year.
• To maintain alumni database.
• Searching and updating the database (Student and Company).
• Providing detailed information and placement papers for every company that recruit
students of Banasthali.
The objective of our project is to design a web application that will be useful for the
students of Banasthali University.
1.2 Theoretical Background:
The basic idea of developing online web application “Venus… Providing VISION
for Campus Recruitment” is to provide all placement related information to the students of
Banasthali University.Our web application aims to save the time of students that they spend
in searching the company profiles, company placement papers etc.
Moreover Venus is providing facility of online papers so that students can check their
aptitude , vocabulary and technical skills online.
1.3 Problem Definition:
We are developing a web application which aims to provide all placement related
information to the students of Banasthali University .In our system general user can view
limited information on the home page and Registered user can access all the information
after logging in through her Smartcard-Id. All the data is entered into the database by the
data entry operator .The task of maintenance of website is done by the administrator.

Analysis

2.1. System Planning

Week 1till (19 Week 2till Week 3till Week 4till Week Week Week Week 17 till Week 23
Dec 2Jan) 2Jan 9Jan 16Jan 5,6,7,8,9,10,11,12 13,14 15,16 16 april april

Coding Phase
Requirment
Problem Defination
Software Design
Evaluation
Work Task 23apr
Mid-Term
Testing
Last Submission
Specifati Software
Specifation
2.2. System Requirement Specification
2.2.1. Introduction
The purpose of the System Requirements Specification document is :
• To capture all the information necessary to have a complete and comprehensive

description of the software requirements.
• To completely describe what the proposed system will do, without describing how
the software will do it.
• To provide a reference for validation of the final product.
• To translate the ideas in the minds of the clients (the inputs), into a formal document
( the output of the requirement phase).
• To ensure that the developer and the client have the same perception of the system.
• To present the system in easily viewable and understandable manner.
• To bridge the communication gap between the client and developer.
2.2.1.1. Purpose:
The main purpose of our web application is :
• To provide all campus placement related information to the students of Banasthali

University.
• To maintain a database of students of (Aim and Act Dept) final year.
• To maintain alumni database.
• Searching and updating the database (student and company).

• Providing detailed information and placement papers for every company that recruit
students of Banasthali.
2.2.1.2 Scope:
The software product ‘Venus..Providing VISION for Campus Recruitment’ will be an

online web application that will be used for providing all campus placement related
information for the students of Banasthali University..The application will manage the
information about various students of (Aim and Act Dept) final year,alumni data,the basic
information and placement papers of the companies visiting Banasthali and online papers.All
the information desired by the user and the scores for online paper solving will be
generated.The system will assist the students in preparation for the campus placement to a
great extent.
2.2.1.3. Definitions ,Acronyms and Abbreviations :

Topic Description
ASP Active Server Pages

ASP lets the user exploit the power of the web server to
process his requests and provide
dynamic,individualized,context based on logic,files and
database.
Browser A Software application used to locate and display web pages.
Client Server A network architecture in which each computer or process in

Architecture the network is either a client or a server at a time.
Client Any computer that is looked up to a computer networks.
Database A data structure that stores the data.
Database Management System

DBMS A collection of computer programs that allow storage,
modification and extraction of information from a database.
Graphical user Interface

GUI The primary output means for displaying the animation
images,diagrams and textual description of concepts.
Hyper Text Markup Language

The publishing language of the world wide web.In addition to
HTML text ,multimedia,hyperlink features,later version of the HTML
support scripting language,style sheets and better printing

facilities.
JavaScript A scripting language developed by Netscape to enable web

authors to design interactive websites.
Login The process by which a user enters an account name and

password to access a time-sharing computer.
Operating Software that controls the execution of the program or

System application.
Server A computer or a device on a network that manages network
resources.
2.2.1.4. References :
2.2.1.4.1. Books:
• Roger S.Pressman ,Software Engineering:A Practitioner’s Approach,6th

Edition,McGraw-Hill Professional.
• K.K. Aggarwal ,Software Engineering ,3rd Edition,New Age International Publishers.
• Pankaj Jalote, An Integrated Approach to Software Engineering,3rd Edition,Narosa

Publishing House.
2.2.1.4.2. Websites:
• www.standards.ieee.org
• www.w3schools.com
2.2.1.5. Document Overview:
This document consists of three sections as follows:
2.2.1.5.1 Introduction:
This section comprises of purpose of this document along with brief description of the
product.It describes the purpose of the document ,scope,definitions and references for this
product.
2.2.1.5.2. General Requirement:
It gives the general description of the product.It outlines the user’s view while using the
product ,product perspective and functional requirements.It provides the general
constraints and assumptions made during the development of product.

1.5.3. System Requirements:
It describes specific technical requirements for the database.It provides the external
Interface requirements and detailed functional requirements.Performance requirements
,quality attributes and any other special requirements are also included.It contains a brief
description of all inputs and outputs of product.
2.2.2. General Description:
2.2.2.1. Product perspective:
Our product is an online dynamic website providing a user friendly GUI which deals with
on-campus recruitment of students of .,Banasthali.
Front End Client

Application ( with
Backend
data
Database
entry/update/dele
te and view
facility ).
2.2.2.1.1. Product Activity:
Our project provides links to various other pages from the main page and by clicking on
various links a person can move to the respective pages.The database administrator as
well as the specific users have to enter the authentic login and password for making
changes in the database such as Insert ,Delete and Update.
2.2.2.1.2. User Interfaces:
The application will be user friendly and it will provide graphical user interface.The user will
interact with tools through the following interfaces:
• A login screen for entering the user-id and password (students,

administrator).Access to different screens will be based upon the role of user.
• There will be screens for capturing and displaying information regarding various
queries submitted by different users.
2.2.2.1.3. Hardware Interfaces:

Client Requirements
Processor : Intel Pentium 3 & above
RAM : 128 MB
Hard Disk : 1.5 GB & above.
Server Requirements
RAM : 512 MB
Hard Disk : 10 GB & above.
Developer Requirements
RAM : 512 MB
Hard Disk : 10 GB & above.
2.2.2.1.4. Software Interfaces:
Operating System : Windows XP.
Technology : ASP(VBScript,JavaScript).
DBMS : MS-SQL Server 2000.
2.2.2.1.5. Communication Interfaces:
The connectivity for the database will be done by using ASP technology.
2.2.2.1.6. Operations:

Database backup and recovery will be handled by the Data Entry Operator . However , the
system will provide a ‘Reset System’ function that will shift the current batch’s data to
alumni database and delete all existing information in the student database.
2.2.2.1.7. Site Adaptation requirements:
The terminals at the client site will have to support the hardware and software interfaces
specified in above sections.
2.2.2.2. Product Functions:
The system allows limited access to guests and data entry operator and full access to
authorized users with specific roles(administrator,registered users).Depending upon the
roles ,he/she will be able to access only specific module of the system.The major functions
that the software will perform are given below:
2.2.2.2.1. Functions available to the Guests:
• The Guests can view
a. Basic information about companies visiting Banasthali .
b. The Placement status of the Institute.
c. Tips about how to prepare for Placement.
d. Latest news about IT market on news board.
• The Guests can give their reviews.
2.2.2.2.2. Functions available to Registered users:
• Registered users will login with their login-id’s and password.
• These users can access :
a. Detailed information and Placement papers of different companies visiting

Banasthali.
b. Frequently Asked Questions(FAQ’s) and Technical Questions.
c. Online paper solving facility.
• Registered users can :
a. Change their password.
b. View photo Gallery.
c. Search Alumni and companies on the basis of various criteria.

d. Upload papers and pictures in photo Gallery and give reply to the Technical
Questions .
e. Post Queries through mails to administrator.
2.2.2.2.3. Functions available to Data Entry Operator:
• Data Entry Operator can enter data of students and alumni in the database.
2.2.2.2.4. Functions available to the administrator:
• Administrator will login with a login-id and password.
• Administrator will review the papers uploaded by the user and if relevant add them to
database .
• Update :
a. the database regularly.

b. the Placement status.
c. the news board.
2.2.2.3. User characteristics:
This subsection describes those characteristics of the eventual user of the product that will
affect the specific requirements.
Users interacting with the system are:

a. Students.
b. Faculty members.
c. Administration members.
2.2.2.4. Constraints:
• Registered users cannot create their own login-id.
• Guests cannot login the system and are authorized to view only some pages of
website and can give their reviews.
• Project is made in ASP,SQL ,so further enhancements will have to be done in these
languages only.
2.2.2.5. Assumptions and Dependencies:

Assumptions :
This application is a customized application for Banasthali University,thus following

assumptions are taken-
• The working of the present manual system will remain the same.
• The smartcard -id of the users will work as login-id for registered users of our
system.
Dependencies :
• The updating in the database depends upon :
a. Changes in IT market.
b .The information supplied by the various users.
• Database would be updated with the start of new session.
2.2.3. Specific Requirements:
2.2.3.1. External Actor Description:
2.2.3.1.1. Human Actors
a) Administrator
b) Data Entry Operator
c) Registered User
d) Guest
2.2.3.1.2. Software System Actors
a) Student Database
b) Company Database
c) Alumni Database
d) User Account Information Database
e) Online paper Database
f) Review & FAQ’s Database
2.2.3.2. Performance Requirements:

There is a large difference between processing by human being and machine. The new
system is far better in terms of speed than old conventional manual system. Our system is
designed so as to provide a repository of placement information.
2.2.3.3. Document Requirements:
Documentation is an essential part of the software design. It is a literature provided along

with the end products, which provides a better understanding of the product and also forms
the basis for maintainability.
2.2.3.4. Design Constraints:
• Web browser is must for our application.
• It is a customized application ( Banasthali University).
2.2.3.5. Software System Attributes:
We emphasize on delivering high quality solutions by strictly following software engineering

methodologies.
We have included following software system attributes:
• Availability:
With an IT system it is desirable that the system and its components are up and running
and fully functional for as long as possible, at it’s highest availability. All the sercives
provided by the system would be available almost every time. A good deal of planning for
high availability centers on backup and failure processing and data storage and access.
• Robustness:
Robustness is the condition of a product or process

design that remains relatively stable with minimum
of variation even though factors that influence operations or uses are constantly changing.
• Security:
The system is made secure by checking the authentication of the user accessing the
services of the system. Services are rendered to the user according to the privileges he/she
is having. Internal checks are also provided so that maliciously and accidentally data is not
changed.
• Reliability:

The software product is expected to perform its intended function with specified precision or
scope.
The software will be thoroughly tested under all conditions.
• Maintainability:
Our software will be including a good quality of documentation and indentation, which
would make it very easy to maintain the software in future.
• Usability:
This software provides a good interface with clearly defined names of the labels and
controls used.
• Extendibility:
The software product being delivered will be designed , keeping in view the dynamic
nature of organization. Our application will be made flexible enough to incorporate
changes in certain features ,like it is allowed to incorporate any increasing number of user
and personal computer.

Design

3.1. System Design Specification :
3.1.1. Introduction
Software design is a solution to the creation of a new system. The software design is a
process through which the requirements are translated into a blue print for constructing the
software.
The data design transforms the information domain model created during analysis into data
structure that will be required to implement the software. The architectural design defines
the relationship between structural element of the software communicate with the user. The
component level design transforms the structural elements of software architecture into
procedural description of software components.
The specification adds further details to the SRS. The SDS document serves as a form of
support for implementation phase at the very same time acts as an attestation that the
designers of the project are implementing the same functions as describing in the SDS
document. The document has various merits, which in turn gives the reason why this
document should be designed before actually implementing the project.
The merits of SDS are:

• It allows in understanding the problem in a better and in well-defined way.
• It assists in catching the potential errors before the implementation phase itself,
which had been very costly to remove otherwise.
3.1.1.1. Purpose
This document is the SDS for an online web application for campus recruitment for
Banasthali University.. It includes project system architecture, detailed description of
components, relationship and design decision trade offs. This document provides a high
quality basis for implementation phase.
The major objective of SDS is to understand the domain, understanding of the system and
implementing it using the software development tool.

3.1.1.2. Scope
3.1.1.2.1. Product Name:
“Venus…Providing VISION for Campus Recruitment”
3.1.1.2.2. Tasks performed by the software:
Our web application will perform the following tasks:

• Providing an electronic alternative to the manual system of the campus recruitment
system followed by Banasthali University.
• To provide detailed information and placement paper for every company that recruits
students of Banasthali University.
• To provide the Placement graph of the University.
• To provide tips for cracking interviews and GDs and preparing CVs.
• To provide online paper solving facility to the registered users.
• To provide facility to view and post reviews, FAQ’s and technical Questions that are
answered by administrator.
• To generate a list of students who can appear for a company.
• To provide a news board on home page.
There are 4 types of users in our system.
• Administrator can:
1. Update and delete company information.

2. Answer technical Questions and FAQ’s.
3. Upload Online Papers.
4. Validate the website.
• Data Entry Operator can:
1. Enter data into database.
• Guest can:
1. View company information.

2. Post reviews, FAQ’s and technical Questions.
3. View other selected features on the home page.
• Registered User can:
1. Access company information and papers.

2. Access alumni information.
3. View and add Reviews.
4. Post FAQs and Technical Questions.
5. Solve online Papers.
6. Edit Specific Personal information.

3.1.1.3. Definitions, Acronyms and Abbreviations:
• DEO – Data Entry Operator.

• FAQ – Frequently asked Questions.
• DFD – Data Flow Diagram.
Definitions :
• Database – It contains the information relevant to enterprise.

• Password – The string, which validates the authentication of the users with respect
to the
Login - Id
• Login-Id – The unique identification provides to user for accessing software.
• Structure Chart – A structure chart partitions a system into black boxes.
• Class Diagram – A Class Diagram shows the interaction between various entities of
a class.
• Use Case Diagram – It visually represents what happens when an actor interacts
with a system .
• Sequence Diagram – It represents the various activities of a process as a sequence
.
3.1.2. References:
• Pressman, Roger, Software Engineering, 6th edition , TataMcGraw Hill.
• IEEE standard of Software Design Description.
• Mastering ASP by A. Russell Jones
• ASP in 21 days by Teach Yourself by SAMS
3.1.3. Decomposition Description :
3.1.3.1. Module Description:
3.1.3.1.1. Login module:
• Purpose: If the user is valid user then he/she is allowed to proceed further and do
all operations as per requirements else he/she will be prompted with an invalid user
declaration and will have to re-enter the login-id and password.
• Input: The developer assigns Login-id.
• Processing: The login-id and password will be checked with the entries in the
database by a query. If it matches page corresponding to the user is displayed.
• Output: An authorised login display form or page according to user will be

displayed.

3.1.3.1.2. Change Password:
• Purpose: Allows user to change his/her password.
• Input: Login-id , old password and new password.
• Processing: Old new password entry in the database is replaced by new password.
• Output: Acknowledgement about validation.
3.1.3.1.3. Forgot Password:
• Purpose: To provide hint to the user who forgot his/her password.
• Input: Login-id.
• Processing: Hint is retrieved from the database.
• Output: Hint is displayed.
3.1.3.1.4. Edit Personal information Module:

• Purpose: To edit personal information of the registered user.
• Input: Student’s Personal information form.
• Processing: The date entered in the corresponding entries will be sent to the
database.
• Output: Database of the Registered user is updated.
3.1.3.1.5. Alumni information Management Module:
• Purpose: To manage database of the Alumni.
• Input: Information of Alumni.
database.
• Output: Database of the alumni is updated.
3.1.3.1.6. Registered User information Management Module:
• Purpose: To manage database of the registered user.
• Input: Information of Registered User.
database.
• Output: Database of the Registered user is updated.

3.1.3.1.7. Company information Management Module:
• Purpose: To manage database of the companies.
• Input: Information of the company.
database.
• Output: Required information is retrieved from database and company’s database

is updated .
3.1.3.1.8. Online Paper Solving Module:
• Purpose: To provide online papers to the Registered user so that they can test their
skills.
• Input: Paper type.

• Processing: When the user selects a paper type, a Random set of Questions are
displayed to the user.
• Output: Score of test is displayed.
3.1.3.1.9. Reviews, FAQ’s and Technical Questions Management Module:
• Purpose: To post reviews, FAQ’s and Technical Questions.
• Input: Reviews, FAQ’s and Technical Questions forms.
• Processing: Reviews are verified and the administrator answers FAQ’s and
Technical questions.
• Output: Reviews, FAQ’s and Technical questions are displayed.

3.1.3.3. Use Case Diagrams:
Logi
n
Admnistrator
Company Data Entry Operator
Info
Mgmt
Alumni
Info
Mgmt
Online
Info
Mgmt
Registered User
Reviews
, Guest
FAQ’s ,
Tech Q’s.
Edit
Personal
Student Info
Info
Mgmt

3.1.3.4. Use Case Descriptions:
3.1.3.4.1. Login
3.1.3.4.1.1. Brief Description
This use case describes how a user logs into the system.
3.1.3.4.1.2. Actors
The following actor(s) interact and participate in this use case:
1. Data Entry Operator .

2. Administrator,
3. Registered User
3.1.3.4.1.3. Flow of Events
3.1.3.4.1.3.1. Basic Flow
This use case starts when the actor wishes to Login to the system.
1) The system requests that the actor enter her user-id and password.
2) The system validates the entered user-id and password and logs the actor
into the system.
1.3.2. Alternative flows
Invalid user-id/password
If in the Basic Flow , the actor enters an invalid user-id and/or password ,the system
displays an error message. The actor can choose to either return to the beginning of the
basic Flow or cancel the login,at which point the use case ends.
3.1.3.4.1.4. Special Requirements
None
3.1.3.4.1.5. Pre-Conditions
All users must have a User Account(user-id,password) created for them in the system (through the
Administrator),prior to executing the use cases.
3.1.3.4.1.6. Post-Conditions
If the use case was successful,the actor is logged into the system.If not,the system state is
unchanged.

3.1.3.4.2.User Account Information Management
3.1.3.4.2.1.Brief Description
This use case allows the Data Entry Operator (DEO) to maintain User Accounts.This
includes adding , changing and deleting user account information from the system.
3.1.3.4.2.2. Actors
The following actor(s) interact and participate in this use case: Data Entry Operator
3.1.3.4.2.3.1. Basic Flow
This use case starts when the DEO wishes to update user account information in the
system. The system requests that the DEO specify the action she would like to
Perform (either add/modify/delete a user account).
3.1.3.4.2.3.1.1. Alternative flows
User Not Found

If during the “Update a user account” or “Delete a user account” flows,a user account with
the specified user-id does not exist,the system displays an error message. The
administrator can then either enter a new user-id or cancel the operation,at which point the
use case ends.
None
The Administrator must be logged onto the system before the use case begins.
If the use case was successful , the user account information is added , updated or deleted
from the system .If not , the system state is unchanged.
3.1.3.4.3. Online Paper Solving:
3.1.3.4.3.1. Brief Discription
This use case describes how a user avails the online paper solving facility.
3.1.3.4.3.2. Actors

Administrator
Registered User

3.1.3.4.3.3.1. Basic Flow
This use case starts when either the Registered Users wants to solve online papers and
view the score or when the Administrator wants to upload a new paper himself or validate
and upload a new paper submitted by the Registered User.
3.1.3.4.3.3.2. Alternative flows
Inappropriate Paper
If in the Basic Flow,the Registered User submits an inappropriate paper ,the

administrator does not upload the paper and displays an error message. At this
point the use case ends.
None
The Administrator and the Registered User must be logged onto the system before this use case.
If the use case was successful , either a new paper is uploaded or some paper is solved
online . Otherwise , the system state is unchanged.
3.1.3.4.4. FAQ’s and Reviews Management
3.1.3.4.4.1 Brief Discription
This use case describes how an actor views the FAQ’s and view/post reviews .
3.1.3.4.4.2. Actors

Data Entry Operator
Administrator
Registered User
Guest.
3.1.3.4.4.3.1. Basic Flow
This use case starts when the actor wishes to view FAQ’s or view/post reviews onto the
system.
1) The system requests that the Registered User enter the review.

2) The Administrator validates the reviews .If so ,then uploads them onto the system.
3.1.3.4.4.3.2. Alternative flows
Inappropriate Reviews
If in the Basic Flow,the actor enters an inappropriate review/slang ,the review is
ignored.At this point the use case ends.
None
None
3.1.3.4.4.6. Post - Conditions

If the use case was successful,then either the user views the FAQ’s or the new reviews are
uploaded onto the system.If not,the system state is unchanged.
3.1.3.5. Context Free Diagrams:
Administrator
Login –id & pwd
Login –id &

pwd
Online Web Required
Registered User Application Information
for Campus according to
Recruitment user
Data Entry Operator
Login –id & pwd
Guest

3.1.3.6. Data Flow Diagrams:
3.1.3.6.1. Level 1 Diagrams -
View Company Info

Guest
Edit Edit
R.U Verified Pwd Personal
View and Informatio
Add n
Online Paper
Upload
Online
Paper
Solving
Solve Reviews DB
Registered
User
Enter Id Answer
& Pwd
Reviews, FAQs DB
FAQs,
Technical
Enter Id Questions
Management
& Pwd Logi Query
n Technical
Administrator Questions DB
Enter Id
& Pwd
User Account Company
Information Information Company
Data Manageme
DB
Entry nt
Operator
D.E.O Pwd Company Info Entry

Verified
Access Alumni
Alumni Information
Info Manageme
Alumni nt
Alumni DB
Info Entry
Student
Information
Manageme
nt
Student info
Entry
Student DB

3.1.3.6.2. Level 2 Diagrams -
Login Module:
User Account
Information
Registered
User
Enter login & Pwd
Enter login & Pwd
Administrator Verify
User
Data Entry
Operator Enter login & Pwd
Check Update
Enter login , old &

New Pwd
Change
Pwd Update
Forgot
Pwd
Retrieve Hint
Return Pwd Hint

3.1.3.6.2.2. Edit Personal Information Module:
View , Edit Validate Student DB

Person
Registered User al
Personal Info Retrieve User Information
Info
Updated User Information
3.1.3.6.2.3. Registered User Information Management Module:
View Registered User Info

DEO
Display Retrieve Registered User Info

Registered
User Info
Registered User DB
Retrieve Info
Enter / Update /Delete
Validate
Registered
Registered User Info Updated Registered User Info
User Info

3.1.3.6.2.4. Alumni Information Management Module:
View Alumni Info

DEO
Display Retrieve Alumni Info

Alumni
Info
Alumni DB
Validate Retrieve Alumni Info

Alumni
Info
Registered
User Updated Info
Process
Alumni
Info Retrieve Alumni Info
Return Required Info
3.1.3.6.2.5. Company Information Management Module:
Administrator
View Update / Delete

Company DB
View Display Retrieve Info

DEO Company
Info
Retrieve Info
Update
Enter Company Info Update Info
Company
Info
Guest
Search Retrieve Company Info

Process
Company
Info
Registered
User
Return Required Info

3.1.3.6.2.6. Online Paper Solving Module:
Administrator Uploa
d Update DB
Paper
Alumni DB
Display
Registered View Paper Online Retrieve Info
User Paper
Solve Paper
Solve Paper
Paper Checking
3.1.3.6.2.7. FAQs, Reviews, Technical Questions Module:
View
View
Registered Retrieve Info
View Reviews ,
User
Technical
Ques ,
Faqs
Guest
Review DB
Add Process
Updated DB
Answer Faq’s
Reviews ,
Administrator Technical
Tech Q’s Ques ,
Faqs

3.1.3.7. Class Diagram :
Review ,
User FAQ’s,Technical
Question
viewCompany ()
postFAQs() 1..* Name
postReviews () Question
postTechnicalQues() Answer
Q-type
postReviewFaqTech()
ansQuery
Alumni
Name
Email-Id
Registered User Company
PlacedYear
EnrollNumber 1…*
Name searchAlumni()
DateOfBirth viewAlumni()
Class
Address
Phone
EmailId
Percentage10th
Percentage12th 1…*
PercentageUG Company
PercentagePGSem1
PercentagePGSem2 Name
AggregatePG Website
DreamCompany1 1…* Centers
DreamCompany2 TrainingProvided
DreamCompany3 RequiredPercentage10
DreamCompany4 RequiredPercentage12
DreamCompany5 RequiredPercentageUG
PlacedCompany RequiredPercentagePG
OnlinePaper
EditPersonalInfo ()
login() searchCompany()
1..* 1..* Paper-id viewCompanyDetail()
reset ()
PaperType updateCompanyInfo()
Question addNewCompany()
Answer deleteCompany()
solve()
upload()
check()

3.1.4. Detailed Description :
3.1.4.1. Structure Chart :
Online Campus Recruitment System
User
Guest Registered User Administrator Data Entry Operator
Detail to be
Clear
View Review View edited
Request or Request Enter Required Data
Qs. Query Details
Enter Reset
View Search Edit data data
View Post
FAQs,
View Upload online paper
Reviews &
Request
DDe
Technical
Update
Question
Request
Delete
Request
View Update Delete Upload

3.1.4.1. Database Schema
3.1.4.1.1. Alumni Table
Design View
Database

3.1.4.1.1. Company Table
Design View
Database

3.1.4.1.2. Company Centres Table
Design View
Database
3.1.4.1.3. FAQ’s Table

Design View
Database

3.1.4.1.4. Login Table
Design View
Database
3.1.4.1.5. News Table

Design View
Database

3.1.4.1.6. Online Paper Table
Design View
Database

3.1.4.1.7. Registered User Info Table
Design View
Database

3.1.4.1.8. Technical Questions Table
Design View
Database

3.2. Module Description according to Team Members :
We have a team of four persons
• Nimisha Agarwal
• Niyati Jha
• Sakshi Mathur
• Saloni Gupta
We have divided the whole Project in modules . Each person has contributed of her
knowledge equally in each module , so the project is a complete output of team work
and none of us is unaware of any phase of the project , but then we have distributed the
responsibility of modules as follows :
• Registered User and Guest Modules
i) Page layout & Designing – Nimisha Agarwal

Niyati Jha
ii) Database Connectivity & ASP Programming– Sakshi

Mathur
Saloni Gupta
• Data Entry Operator and Administrator Modules
i) Page layout & Designing – Sakshi Mathur

Saloni Gupta
ii) Database Connectivity & ASP Programming – Nimisha

Agarwal
Niyati Jha
• Data Entry – Sakshi Mathur

Niyati Jha
• Report Writing – Nimisha Agarwal

Saloni Gupta

Coding

4.1. connection.asp
<%
Dim Conn,acon
Set Conn=Server.CreateObject("ADODB.Connection")
acon="provider=SQLOLEDB;datasource=local;database=campus;Uid=sa;pwd=;"
conn.ConnectionString=acon
conn.open()
%>
4.2. shownews.asp
<%
strsql="select * from newsTable where isdelete like 'false'"
set rs=Server.CreateObject("ADODB.Recordset")
rs.Open strsql,Conn,2,3
do while not rs.EOF
news1=rs("news")
Response.Write(news1)
Response.Write("<BR><BR>")
rs.MoveNext
loop
rs.close
%>
4.3.login.asp
<%
ln=Request.Form("loginid")
if ln <> "" then
ps=Trim(Request.Form("pass"))
rs.Open "loginTable",Conn,2,3
flag=false
Do until rs.EOF or flag
if strComp(rs("login-id"),ln)=0 and strComp(rs("password"),ps)=0 then
flag=true
else
rs.moveNext
end if
loop
if flag then
if ln="dapaji" then
Response.Redirect "deo/deohome.asp"

elseif ln="admin" Then
Response.Redirect "admin/admin_main.htm"
else
session("ln")=Request.Form("loginid")
Response.Redirect "regUser/reguser.asp"
end If
else%>
<script language="javascript">

</script>
<% end if
Response.End
end if
%>
4.4. change Password.asp
<%
ln=Request.Form("loginId")
if ln <> "" then
ps=trim(Request.Form("password"))
nps=trim(Request.Form("NewPassword"))
rps=trim(Request.Form("RePassword"))
f = false
flag=false
if strComp(rs("login-id"),ln)=0 and strComp(rs("password"),ps)=0 then
flag=true
else
rs.moveNext
end if
loop
if not flag then
Response.Write ("<center><b><I>Invalid Login-id or
Password</I></B></center>")
Response.End
elseif flag and rps<>nps Then
Response.Write ("<center><b><I>re-entered password doesnot match
with new password</I></B></center>")
else
rs("password")=nps
rs("hint")=Request.Form("Password hint")
rs.Update
Response.Write ("<center><b><I>Password successfully
changed</I></B></center>")
end if

end if
%>
4.5. forgotpassword.asp
<%
ln=ucase(Request.Form("loginId"))
if ln <> "" then
flag=false
if strComp(rs("login-id"),ln)=0 then
flag=true
else
rs.moveNext
end if
loop
if not flag then
Response.Write("<font color=red><b>* Invalid Login-id</b></font>")
else
hin=rs("hint")
Response.Write("<font color=red><b>Hint-"&hin&"</b></font>")
end if
Response.End
end if
%>
4.6. searchcompany.asp
<%
dim crt
crt=Request.Form("criteria")
if crt="comp_cent" then
strsql="select distinct cname from companycentresTable"
Response.Write "<form name=f1 method=post
action='trying1.asp?id=centre'>"
Response.Write("<Table align=center width='100%' cellpadding=5>")
Response.Write("<Td width='25%'></td>")
Response.Write("<Td width='25%' align=middle>")
Response.Write("<SELECT id=select1 align=center name='nameCentre'
onChange='f();'>")

Response.Write("<OPTION value=''>Select any company</OPTION>")
do while not rs.EOF
cna=trim(rs("cname"))
Response.Write("<OPTION value="&cna&">"&cna&"</OPTION>")
rs.MoveNext
loop
Response.write("</select>")
Response.Write("</td>")
Response.Write("</Table>")
Response.Write("</form>")
rs.close
set rs=nothing
end if
if crt="pkg" then
Response.Write "<form name=f1 onload
='document.f1.pack.focus();'method=post
action='trying1.asp?id=pkg'>"
Response.Write("<b>Enter Package (in lacs)     ")
Response.Write("<Input type='text' name='pack' value=''>")
Response.Write("<Input type='button' name='go' value='Go' onclick='f();'>")
Response.Write("<Td width='15%'> </td>")
end if
if crt="trn" then
Response.Redirect "trying1.asp?id=tr"
end if
if crt="elg_crt" then
strsql="select cname from CompanyTable"
Response.Write "<form name=f1 method=post action='trying1.asp?id=elg'>"
Response.Write("<SELECT id=select1 align=center name='nameCentre'
onChange='f();'>")
Response.Write("<OPTION value=''>Select any company</OPTION>")
do while not rs.EOF
cna=trim(rs("cname"))
Response.Write("<OPTION value="&cna&">"&cna&"</OPTION>")
rs.MoveNext
loop
Response.write("</select>")

rs.close
set rs=nothing
end if
if crt="elg_usr" then
Response.Redirect "trying1.asp?id=usr"
End if
%>
4.7. faqadd.asp
<%
ques1=Request.Form("ques")
uname=Request.Form("username")
int count
if ques1 <> "" then
if uname="" then
uname="anonymous"
end if
rs.Open "faqsTable",Conn,2,3
count=0
Do while not rs.EOF
count=count+1
rs.MoveNext
loop
count=count+1
rs.AddNew
rs("sno")=count
rs("question")=ques1
rs("name")=uname
rs("answer")="Yet to be answered !"
rs("date1")=date()
rs("isdelete")="false"
rs.Update
rs.Close
set rs=nothing
end if
%>
<%
strsql="Select * from faqsTable where isdelete like 'false' order by date1 desc"
Do while not rs.EOF
sn=rs("sno")
nm=rs("name")
qs=rs("question")
ans=rs("answer")
Response.Write("<fieldset class=back>")

Response.Write("<br>")
Response.Write("<span class=qans>")
Response.Write("<font face=tahoma>")
Response.Write("  ")
Response.Write("<u>Question</u> ")
Response.Write("</span>")
Response.Write("<span class=question>")
Response.Write(" ")
Response.Write(qs)
Response.Write("<br><br>")
Response.Write("<span class=qans>")
Response.Write("  <u>Answer</u> : ")
Response.Write("<span class=answer>")
Response.Write(ans)
Response.Write("<p class=name1>")
Response.Write("By : ")
Response.Write(nm)
Response.Write("   (")
Response.Write(rs("date1"))
Response.Write(")   ")
Response.Write("</p>")
Response.Write("</fieldset>")
Response.Write("<br><br>")
rs.MoveNext
loop
%>
4.8. delfaqs.asp
<%
int s
ans1=Request.Form("txt")
s=Request.Form("sn")
strsql="select * from faqsTable where sno='"&s&"'"
rs.Open strsql,conn,2,3
rs("isdelete")="true"
rs.Update
rs.Close
set rs=nothing
session("cnt2")=0
Response.Redirect "del_faqs.asp"
%>
4.9. onlinepaper.asp
<%
var=Request.Form("selcat")

Dim sn(30),rno(10),i
count=Request.Form("count")
if count=1 then
Session("c")=1
Session("score")=0
Session("r")=""
end if
cnt=session("c")
if (var<>"")or cnt>1 then
if cnt>10 then
for i=1 to 30
sn(i)= session("qn")(i)
Next
for i=1 to 10
rno(i)=session("rn")(i)
next
qno=sn(rno(cnt-1))
dim strsql2
strsql2="select answer from onlineTable where
sno="&qno
rs.Open strsql2,Conn,2,3
ans=trim(rs("answer"))
if ans=trim(Request.Form("radio1")) then
session("score")=session("score")+1
end if
sc=session("score")
rs.close
set rs=nothing
Response.Write("<Table width='100%'height='40%'
cellpadding=5>")
Response.Write("<Tr>")
Response.Write("<td align=left width='25%'>")
if sc >= 8 then
Response.Write("<imgsrc='../Images/general/
best.gif' height='100%'>")
elseif sc>=5 then
Response.Write("<imgsrc='../Images/general
/good.gif'height='100%'>")
else
Response.Write("<imgsrc='../Images/
general/worst1.gif' height='100%'>")
end if
Response.Write("<td width='50%' align=center>")
Response.Write("<h4><font color=red>Test Completed
Successfully !!</font></h4>")
Response.Write("<td align=right>")
Response.Write("<img src='../Images/general/blast.gif'
height='100%'>")

Response.Write("</tr>")
Response.Write("<tr>")
Response.Write("<td width='25%'>")
Response.Write("<b><font color=black>Score =
</font><font color=red>
"&session("score")&"
</font></b>")
Response.Write("<td width='50%' align=left nowrap>")
if sc >= 8 then
Response.Write("Congratulations !! Excellent
performance")
elseif sc>=5 then
Response.Write("Congratulations !! You can do
better")
else
Response.Write("Sorry ! You must work hard")
end if
Response.Write("<td width='25%'> </td>")
Response.Write ("</tr></table>")
set rs=nothing
usrans=trim(Request.Form("radio1"))
set rs1=Server.CreateObject("ADODB.Recordset")
if(usrans="") then
strsql="select "&ans&" from onlineTable where
sno="&qno
else
strsql="select "&ans&","&usrans&" from
onlineTable where sno="&qno
end if
rs1.Open strsql,Conn,2,3
crtans=rs1(ans)
if(usrans<>"") then
yrans=rs1(usrans)
else
yrans="-"
end if
result=session("r")
result=result+","+crtans+","+yrans
session("r")=result
val=cstr(Session("r"))
r1=split(val,",")
i=0 ,j=1
Response.Write("<Table class=tbl align=center
width='50%' cellpadding=5 >")
Response.Write("<tr><th>Q.No.</th>")
Response.Write("<th>Correct Answer</th>")
Response.Write("<th>Your Answer</th></tr>")
while i<Ubound(r1)
Response.Write("<Tr><Td class=c>"&j&"
</Td>")

Response.Write("<Td class=c>"&r1(i)&"
</Td>")
Response.Write("<td class=c>"&r1(i+1)&"
</td></tr>")
i=i+2
j=j+1
wend
Response.Write ("<p align=right><a href ='display.asp'>
Back to Online Test</a></p>")
Else if cnt="1" then
Randomize
strsql="Select sno from onlineTable where ptype like '"&var&"'"
n=1
while not rs.Eof
sn(n)=rs("sno")
rs.MoveNext
n=n+1
wend
n=n-1
i=1
while(i<=10)
flag=true
t=Cint(Rnd*n)
for j=1 to i-1
if(rno(j)=t)or t=0then
flag=false
Exit for
end if
Next
if(flag=true) then
rno(i)=t
i=i+1
end if
Wend
rs.close
set rs=nothing
session("qn")=sn
session("rn")=rno
else
for i=1 to 30
sn(i)= session("qn")(i)
Next
for i=1 to 10
rno(i)=session("rn")(i)
next
qno=trim(sn(rno(cnt-1)))
dim strsql
strsql="select answer from onlineTable where sno="&qno

ans=trim(rs("answer"))
usrans=trim(Request.Form("radio1"))
if ans=usrans then
session("score")=session("score")+1
end if
rs.close
set rs=nothing
set rs1=Server.CreateObject("ADODB.Recordset")
if(usrans="") then
strsql="select "&ans&" from onlineTable where sno="&qno
else
strsql="select "&ans&","&usrans&" from onlineTable where sno="&qno
end if
rs1.Open strsql,Conn,2,3
crtans=rs1(ans)
if(usrans<>"") then
yrans=rs1(usrans)
else
yrans="-"
end if
result=session("r")
if (cnt-1)=9 then
result=result+crtans+","+yrans
else
result=result+crtans+","+yrans+","
end if
session("r")=result
end if
dim rs
dim strsql1
strsql1="Select * from onlineTable where sno="&sn(rno(cnt))
rs.Open strsql1,Conn,2,3
Response.Write("<fieldset style='border-style:ridge ; border-width:4 ; border-
color:gold ; background-color:#d3e1ff ' >")
Response.Write("<Table width='100%' align=center cellspacing=5>")
Response.Write("<tr><td width='10%' align=center>Question : </td>")
Response.Write ("<td>"&rs("question")&"</td></tr>")
Response.Write ("<tr><td> </td>")
Response.Write ("<td><INPUT type='radio' name=radio1
value='option1'>  "&rs("option1")&"</td></tr>")

Response.Write("</fieldset>")
Response.Write("<Table width='100%' align=center cellspacing=5>")
Response.Write("<tr><td width='10%' align=center>Score : </td>")
Response.Write ("<td><font color=red>"&session("score")&"</font></td>")
Response.Write ("<td align=right><INPUT class=buttn type=submit
value=Next></td>")
Response.Write ("<td width='10%'> </td></tr></table>")
session("c")=session("c")+1
end if
else
Response.Redirect "display.asp"
end if
%>

Implementation

5.1 Methodology Adopted
We have adopted a “ Linear Sequential Model “ or “ Waterfall Model ” .
This model states that the phases are organized in a linear order . In this model the project
begins with feasibility analysis on successfully demonstrating the feasibility of the project .
The requirement analysis and project planning begins .
The design starts after the requirement analysis is complete and coding begins after design
is complete .
Once the programming is completed the code is integrated and testing is done .
On successful completion of the testing , the system is installed .
Analysis Design Coding Testing Support

5.2. Input and Output Screen Design :
Home Page
Registered User Home Page

Administrator Home Page
Data Entry Operator Home Page

Company Profile
Placements

Technical Questions
Reviews

Search Alumni
Online Test

User Queries
Photo Gallery - Banasthali

Edit Personal Details
Update Company Details

Enter Student Details by Data Entry Operator
Change Password

Forgot Password

Contact Us
Testing
6. Testing:
Testing is the major quality control measure used during software development. Its basic
function is to detect errors in the software. During requirement analysis and design, the
output is a document that is usually textual and non-executable. After the coding phase,
computers programs are available that can be executed for testing purpose. This implies
that testing not only has to uncover errors introduced during coding, but also errors
introduce during the previous phases. Thus, the goal of testing is to uncover requirements,
design and coding errors in the programs. Consequently, different levels of testing are
used.
6.1 Methodologies Used for Testing:
Top down Approach:
This approach is used as top-down programming where an application is constructed

starting with a high level description of what it is supposed to do and breaking the
specification down into simpler pieces, until a level a level has been reached that
corresponds to the primitives of programming language to be used in the overall task is first
defined in terms of generalized sub tasks which are subsequently further defined & so on.
This process is continued downwards until subtasks are defined in a form suitable for
execution of computer.
6.1.1 Unit Testing

The starting point of testing is unit testing. In this, a module is tested separately and is often
performed by the coder himself simultaneously along with the coding of the module. The
purpose is to exercise the different parts of the module code to detect coding errors.
6.1.2 Integration Testing:
After this, the modules are gradually integrated to eventually from the entire system. During
integration of the modules, integration testing is performed to detect design errors by
focusing on testing the inter-connection between modules.
6.1.3 System Testing:
After the system is put together, system testing is performed. Here the system is tested
against the system requirements to see if all the requirements are met and if system
performs as specified by the requirements. Various type of testing under this are
• Performance testing
• Load testing
• Volume testing
• Stress testing
6.2 Testing Techniques
We have both white Box and Black Box testing strategies:
6.2.1 White Box testing strategies:
This strategy deals with the internal logic & statements of the code. White box testing is
also called Glass, Structural, Open box or Clear box testing strategy incorporates converge
of the code written, branches, paths, statements & logic of the code & etc.
We could implement White box testing scheme.We processed knowledge of coding & logic
i.e. internal working of the code.
Testing is the process of identifying the no test cases which have a high probability of
finding errors.
This is a client-server application & in general testing for client-server software testing
occurs at three levels:
• Individual’s client applications are tested in a disconnected mode, the operation of

the server, and the underlying network are not considered.
• The client software & associated sever application are tested is concern, but
hardware operation are not explicitly exercised.
• The complete client-server architecture, including network operation & performance
is tested.

6.2.2.1 Advantages of White Box Testing:
• As knowledge of internal coding structure is prerequisite, it become very easy to find

out which type of input data can help in help in the application effectively.
• The other advantage of white box was that, it helps in optimizing the code.
• It helped in removing the extra lines of codes, which could have in hidden defects.
6.2.2 Black Box Testing Strategy:
Aims to test a given program’s behavior against its specification or components without
making any references to the internal structure of the program or the algorithm used.
Therefore, the source code is not needed. We study the system by examining its inputs and
related outputs. The key is to devise that have a higher likelihood of causing outputs that
reveals the present of defects. We use experience and knowledge of the domain to identify
such test cases.
Black box testing is rarely exhaustive and sometimes fails to reveals corruption defects
caused by wired combination of inputs.
6.3 Application function tests:
The functionality of the client application is tested using different methods. In essence the
application is tested in stand-alone fashion in an attempt to uncover errors in its operation.
The various testing methodologies adopted at the client side are as follows:
6.3.1 Unit Testing
It includes the following:
6.3.1.1 Function Tests:
This involves exercising the code with nominal input values for which the expected results
are known. Function tests are conducted.
6.3.1.2 Performance Test:
This determines the amount of execution time spent in various parts of the unit. Program
throughput, response time and device utilization by the program unit. Performance tests
have been partly conducted.
6.3.1.3 Stress Test:
These test are those designed internally to break the unit. This testing has been partly
conducted.

6.3.1.4 Structured Testing:
These tests are concerned with the exercising the internal logic of the program and
traversing execution paths. These tests have been conducted.
6.3.2 Integration Testing:
We have followed bottom-up integration to integrate the components of software System

into a functional whole. It consist of Unit testing followed by Subsystem testing followed by
testing of the entire system.
6.3.3 User Acceptance Testing:
It involves planning and execution of functional tests, performance test and stress tests in
order to demonstrate that the implemented system satisfies its requirements. These are
two sets of acceptance tests: those developed by the quality assurance group and those
developed by the users.
6.3.4 Server Testing:
The co-Ordination and Data Management functions of the server are tested. Server
performance (overall response time and data throughput) is also considered.
6.3.5 Database Testing:
The accuracy and the integration of data stored by the server is tested.
Transaction posted by client application is examined to ensure that data are properly
stored, updated and retrieved.
6.3.6 Transaction Testing:
A series of tests are created to ensure that each class of transaction is processed
according to requirements. Tests focus on the correctness of processing and also on
performance issues (e.g.: transaction processing times and transaction volumes) .
6.4 Test Report:
Test Cases:
Test Case 1: Login Empty

If Login , Password field is empty then
Appropriate message is displayed.
Test Case 2: Login Incorrect

If Login , Password entered is incorrect then
“Invalid Login-id or Password” message is displayed
Corresponding fields are reset.

Test Case 3: Correct Insertion
Correct entries are inserted in the database.
Verification done after inserting new dummy entries in the database.
Test Case 4: Correct Deletion

Entries are deleted from the database.
Verification done after deleting existing entries in the database.
Test Case 5: Correct Updation

Correct entries are updated in the database.
Verification done after updating database with dummy entries.
Test Case 6: User Reviews on the Website

Reviews are displayed on the website as posted by website viewer.
Irrelevant reviews are deleted from the database by the administrator.
Test Case 7: Technical Questions and FAQ’s

All queries regarding the website and placement preparation are answered and
displayed on the website.

Documentation
7.1. User Operational Manual

Getting Started
7.1.1. To check for IIS server
1. Click on start -> Internet Explorer

2. Type the following URL in the address bar http://localhost and press “Enter”
3. After pressing , “Enter” if you get a new window opens with Microsoft Internet
Information Services then you have IIS on your system.
7.1.2. Loading the Information Website
1. Insert the CD drive and open it .

2. Right Click on the icon “Venus” and click copy
Click :- My Computer -> C: -> Inetpub -> wwwroot
Open the folder wwwroot ; Right click and click Paste.
3. A folder named Venus will appear in the parent folder “wwwroot”.

7.1.3. Running the Website
1. Click Start -> Internet Explorer.

2. Click on the address bar of the Explorer and type the link
http://localhost/Venus/home.asp and press Enter.
7.2. Read Me
Project Summary
Class : B.Tech(IT) Group Number: 36 Session : 2009-2010

Project Name: Venus… Providing VISION For Campus Recruitment
Project Category : Online Project
Group Members Guide
1.Ms. Manisha Agarwal
1.Nimisha Agarwal
2.Niyati Jha
3.Sakhi Mathur
4.Saloni Gupta
Minimum Requirement for running this Project:

Software Hardware
1.O.S. :Windows 1. CPU : Intel Pentium 3 & above

2.Web Server : IIS 2. Memory (Primary) : 256 MB
3. Browser : Internet Explorer 3. Memory (Secondary) : 10 GB
4. Front End :HTML & above
5 Back End : SQL
6. Language : HTML
7. Technology : ASP
8. Scripting Language:VBScript,JavaScript
Database Used :SQL DSN Name : None

Startup File Name : home.asp
User Name : admin Password : admin
User Name : dapaji Password : dapaji
User Name : SmartCardId Password : SmartCardId
Project Description (Max 100 words) including different types of user for your
project.
The software product ‘Venus..Providing VISION for Campus Recruitement’ will be an online
web application that will be used for providing all campus placement related information for
the students of Banasthali University..The application will manage the information about
various students of(Aim and Act Dept) final year,alumni data,the basic information and
placement papers of the companies visiting Banasthali and online papers.All the
information desired by the user and the scores for online paper solving will be
generated.The system will assist the students in preparation for the campus placement to a
great extent.Our web application will have four types of users:
1.Guest(General User)
2.Registered User
3.Administrator
4.Data Entry Operator(DEO)
7.3. Limitations

• Our software is limited only to Banasthali University , .
• At the end of every session , Data Entry Operator needs to change the Student and
Alumni Database .
• The user is not authorized to upload the placement papers of the companies .
• Registered Users cannot create their own Login-Ids.
• Guest cannot login into the system and are authorized to view only few features of
website and can give their reviews .
• Project is made in ASP , SQL so further enhancements will have to be done in these
languages only.

Annexure
8.1. References
8.1.1. Bibliography
1. Pressman, Roger S. Software Engineering : A Practitioner’s Approach

6th Edition , McGraw-Hill International Edition .
2. Aggarwal, K.K. Software Engineering

3rd Edition , New Age International Publishers.
3. Jalote, Pankaj .An Integrated Approach to Software Engineering

3rd Edition , Narosa Publishing House
4. Ray S., Deborah . Mastering HTML 4

Premium Edition , BPB Publications
5. Jones , A. Russell . Mastering Active Server Pages 3

BPB Publications

6. Aggarwal , R.S. .A Modern Approach to Verbal Reasoning
S.Chand & Company Ltd
7. Green , Sharon Weiner . Barron’s GRE

17th Edition , Galgotia Publications Pvt. Ltd.
8.1.2. Websites
1. www.indiastudychannel.com
2. www.freshersworld.com
3. www.freshersonline.com
4. www.geekinterview.com
5. www.ieee.org
6. www.banasthali.ac.in
7. www.w3schools.com

Report

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Report

Uploaded by

Copyright:

Available Formats

Venus..

“Providing VISION for Campus Recruitment”

University For Women:

Project Guide Submitted by

Apaji Institute of Mathematics and Applied Computer Technology

Venus…Providing VISION for Campus Recruitment

Project Guide Prof.G.N.Purohit

Venus…Providing VISION for Campus Recruitment

Name of Students: Nimisha Agarwal (IT-6072)

Degree for which submitted : B.Tech in Information Technology.

Department : AIM & ACT

Project Title : Venus… Providing VISION For Campus Recruitment.

Name of Project Supervisor : Ms. Manisha Agarwal

Month and Year of Project Submission : April , 2010

Venus…Providing VISION for Campus Recruitment

Venus…Providing VISION for Campus Recruitment

Venus…Providing VISION for Campus Recruitment

The purpose of our web application “Venus…Providing VISION For Campus

• To provide all campus placement related information to the students of Banasthali

• To maintain a database of students of (Aim and Act Dept) final year.

• To maintain alumni database.

• Searching and updating the database (Student and Company).

1.2 Theoretical Background:

1.3 Problem Definition:

Venus…Providing VISION for Campus Recruitment

Venus…Providing VISION for Campus Recruitment

Venus…Providing VISION for Campus Recruitment

Venus…Providing VISION for Campus Recruitment

• To capture all the information necessary to have a complete and comprehensive

• To provide a reference for validation of the final product.

• To present the system in easily viewable and understandable manner.

• To bridge the communication gap between the client and developer.

The main purpose of our web application is :

• To provide all campus placement related information to the students of Banasthali

• To maintain a database of students of (Aim and Act Dept) final year.

• To maintain alumni database.

• Searching and updating the database (student and company).

Venus…Providing VISION for Campus Recruitment

The software product ‘Venus..Providing VISION for Campus Recruitment’ will be an

2.2.1.3. Definitions ,Acronyms and Abbreviations :

ASP Active Server Pages

Browser A Software application used to locate and display web pages.

Client Server A network architecture in which each computer or process in

Client Any computer that is looked up to a computer networks.

Database A data structure that stores the data.

Database Management System

Graphical user Interface

Hyper Text Markup Language

Venus…Providing VISION for Campus Recruitment

JavaScript A scripting language developed by Netscape to enable web

Login The process by which a user enters an account name and

Operating Software that controls the execution of the program or

• Roger S.Pressman ,Software Engineering:A Practitioner’s Approach,6th

• K.K. Aggarwal ,Software Engineering ,3rd Edition,New Age International Publishers.

• Pankaj Jalote, An Integrated Approach to Software Engineering,3rd Edition,Narosa

2.2.1.5. Document Overview:

This document consists of three sections as follows:

2.2.1.5.2. General Requirement:

Venus…Providing VISION for Campus Recruitment

2.2.2. General Description:

2.2.2.1. Product perspective:

Front End Client

2.2.2.1.1. Product Activity: