Acknowledgement

While presenting this project we expressed our sincere gratitude to almighty God
for his grace and blessing that helped us to complete this project work success
fully. We also want to say few heartfelt words for the people who were part of t
his project in numerous ways…………… First of all, We want to devote our special thank to our
Parents for their unconditional love, care and support and inspiration from tim
e to work on this project. We wish to place and record our sincere gratitude and
deep appreciation to the Coordinator of the MCA Department Mrs. Anshum Srivasta
va who provide us such a cooperative and healthy environment and all necessary i
nformation for the successful completion of our project. Project Management is a
people- intensive activity. Without motivation, a person is literally unable to
make his best efforts. It is indeed a matter of great pleasure to record sense
of gratitude towards our project guide Mr. Praveen Sachan for his guidance, cons
tant supervision and the motivation during our project work. We would like to th
ank Mr. Pramod Bhatnagar for their encouragement and insightful comments at virt
ually all stages of his project. The writing of this project was inspired, taugh
t, or assisted by numerous scholars or specials working in this area. We would l
ike to thank each of them for intellectual exchanges, valuable suggestions, crit
ical reviews and assistance.
Certificate
This is to certify that this report embodies the original work done by
vandana dwivedi , Taru Gupta , Priyanka mukhraiya and Monika Pandey
during the project submission as a partial fulfillment of the requirement for th
e Project of Masters of computer Application Vth Semester, Of
L.B.S.I.M.D.S LUCKNOW .
MR. PRAVEEN SACHAN
[PROJECT GUIDE]
MS ANSHUM SRIVASTAV
[HOD]
PREFACE
This project report is divided into numbers of section and sub sections. First s
ection is introduction & objective. In the second section complete analysis of t
he proposed system is discussed . The third section entitled Software Engineerin
g paradigm applied in which appropriate model has been chosen for the developmen
t of this project. Forth section contains Software Requirement specification, wh
ich is and important document. Fifth section is designing section in which ER-Di
agram, DFD’s & Data Structure are given. Sixth section is devoted to coding. Seven
th Section is for validation checks and testing of the news system. Eighth Secti
on tells how the system is implemented. Ninth section is to estimate over all co
st of the system. COCOMO model is being used for this purpose. Tenth section is
giving the screens of report generating by the system. Eleventh Section contains
PERT Chart and Gantt Chart. It is for the scheduling of the whole project work.
And the last but not least twelfth section is about the feature scope of this s
ystem.
CONTENTS
1- INTRODUCTION ABOUT ORGANIZATION OBJECTIVE ABOUT PROJECT 2- SYSTEM ANALYSIS RE
QUIREMENT ANALYSIS 3- FEASIBILITY STUDY TECHNICAL FEASIBILITY ECONOMICAL FEASIBI
LITY OPERATIONAL FEASIBILITY 4- SOFTWARE REQUIREMENT SPECIFICATION 5- DESIGN DAT
A FLOW DIAGRAM 6- CODING CODE CODE EFFICIENCY OPTIMIZATION OF CODE 7- TESTING TE
STING TECHNIQUE TESTING STRATEGIES 8- IMPLEMENTATION USER MANNUAL USER TRAINING
EVALUATION 9- MAINTENANCE SECURITY MEASURES TAKEN 10-COST ESTIMATION OF PROJECT
11- REPORTS 12- FUTURE SCOPE OF THE PROJECT
Chapter :1 Introduction
About Organization The TRAINING & PLACEMENT CELL is developed for LBSIMDS. SERVI
CES provided by LBSIMDS In addition to field of Software Engineering (Technical
Course like MCA), it also conducts • • • • MBA PGDCA PGDMSM PGDBA
Computerization – Its importance.
“As a rule [S] he who has the most information will have the greatest success” Infor
mation is the tool for management in any business environment and is in use for
effective decision making. The data collected is processed and the desired infor
mation obtained. Computerization is the need of hour is an undisputable fact tha
t without the help of IT, there is no possibility to sustain the organization. C
omputerization has to be implemented in a phased manner. To evaluate the differe
nt phase of the computerization, we first evaluate the different tires of the co
operatives. The computerization is absolute necessity, but it has to be taken in
a phased manner. The phase relate towards the objective of the whole exerciser
i.e. faster access of information, for speedier reporting, better planning and d
ecision making.
OBJECTIVE
Computer based information system are designed to improve existing system. The p
roposed system aims to achieve the following goals : • It will accept the answer o
f questions proposed by Administrator of organization. • It will provide exact pos
ition of project. • It will allow letting Administrator to change profile, to logi
n and all facilities provided by project.
•
It will reduce the paper work and utilize the maximum capabilities of the Setup
and organization as well as it will save time and money which are spending in ma
king reports and collecting data.
• It provides the facility of maintaining the details of the students and gets the
requested list of candidates for the companies who would like to recruit the st
udents based on given query. • It can be accessed throughout the organization and
outside as well with proper login provided. • This system can be used as an applic
ation for college to manage the student information with regards to placement. •
•
Students logging should be able to upload their information in the form of a CV.
Visitors/Company representatives logging in may also access/search any informat
ion put up by Students.
ABOUT PROJECT
This project is aimed at developing an online application for the Training and P
lacement Dept. of the college. The system is an online application that can be a
ccessed throughout the organization and outside as well with proper login provid
ed. This system can be used as an application for the TPO of the college to mana
ge the student information with regards to placement. Students logging should be
able to upload their information in the form of a CV. Visitors/Company represen
tatives logging in may also access/search any information put up by Students. Wo
rk in the application will be done in the following way: 1. The categories of CV
s are decided and uploaded and define it formally. 2. A server is used for stori
ng the CVs. 3. The front-page of the system is created giving a brief descriptio
n about the system and a login box . 4. Other sub-systems like automatic notific
ation, screens for various events are created. Like some companies visiting the
campus for placements. Statistics of the previous year’s placements. Current Place
ment scenario . 5. A role of approver is also introduced. When the student uploa
ds his/her CV, the approver should approve the document and only then can it be
uploaded.
CHAPTER :2 SYSTEM ANALYSIS
REQUIREMENT ANALYSIS
Requirement anlysis is a software engineering task that bridges the gap between
system level requirements engineering and software design.
System Engineeri ng
Software Requireme nt
Softwar e Design
(Analysis as a bridge between system engineering and software design) The softwa
re requirement analysis may be divided into five areas of effort: Problem recogn
ition Evaluation and synthesis Modeling Specification Review. Requirement analys
is is the first technical step in the software process. TECHNOLOGIES USED -: FRO
NT END – .NET FRAMEWORK
 IDE VISUAL STUDIO 2008 C# WITH ASP.NET BACK END SQL SERVER 7.0 MINIMUM HARDWARE
SPECIFICATION 265MB RAM, 2 GB Hard Disk.
CHAPTER:3 FEASIBILITY STUDY
To find out whether the proposed project is feasible or not I did three types of
feasibility study these are given below: Feasibility is the determination of wh
ether or not a project is worth doing. The process followed in making this deter
mination is called a feasibility study. This type of study determined that a pro
ject is feasible;we can go ahead and prepare the project specification which fin
alizes project requirements. In this project report , we will consider three typ
es of feasibility study. These are described below:
3.1 Technical Feasibility
Technical Feasibility is a measure of availability of technical recourses. The h
ardware and software requirements are already available with the organization.
3.2 Economical Feasibility
Economic Feasibility is the measure of cost effectiveness of a project. No extra
costs are involved as the hardware and software recourses are already available
with the organization.
3.3 Operational Feasibility
Operation Feasibility is the feature of how well the system will work in the org
anization and how the user feels about the system. For checking out operational
feasibility of the system first of all I find out answer to the following questi
ons these are given below :
• • Is there sufficient for the project from the management ? Are current business m
ethods acceptable to the user ? • • Have the users been involved in the planning and
development of the project ?
Will the purposed system cause harm ?
CHAPTER : 4 SOFTWARE REQUIREMENT SPECIFICATION
The software requirements specification is produced at the culmination of the an
alysis task. The function and performance allocated to software as part of syste
m engineering are refined by establishing a complete information description a d
etailed functional and behavioral description, an indication of performance requ
irements and design constraints, appropriate validation criteria and other data
pertinent to requirements
1. Introduction Purpose : The purpose of this documentation is to
describe all external requirements of software for project information Managemen
t system.
Scope : This document is the only one that describes
the requirements of the system. It is meant for use by the developers and will a
lso be the basis for validating the final delivered system. Any changes made to
the requirements in the future will have to go through a formal change approval
process.
The scope of study is limited to
Suggest the proposed solution to achieve defined objectives. Suggest hardware co
nfiguration requirement for the proposed solution. Formulate the applications so
ftware specifications. Provide budgetary estimates for implementation of the pro
posed solution.
 Suggest prioritization and phasing of the proposed solution . Suggest infrastruc
tures and training requirements for the proposed solution.
CHAPTER : 5 SYSTEM DESIGN
The goals of this phase are :
To determine which system components will cover which requirements in the system
specification, and How these system specification will work together ?
The important activities of design include :
Designing system architecture. Designing underlying logical data model. Designin
g the algorithmic structure of the system components, and Validating the system
architecture and the algorithms to realize the individual system components.
The outcome of this phase are :
Description of logical data model. Description of system architecture. Descripti
on of algorithmic structure of the system components. Documentation of design de
cisions. The goal of this phase is to transform requirements specification in to
a structure that is suitable for implementation in some programming language. I
n technical terms we derive the software architecture from the SRS document.
DATA FLOW DIAGRAM
RECRUITERS
TRAINING AND PLACEMENT
STUDENT
TRAINING AND PLACEMENT INCHARGE
CONTEXT LEVEL DIAGRAM
STUDENT
REGISTRATIO N 1.0
dob password name
PERSONAL DATA
FIRST LEVEL OF DFD
Company tr
providing training Company placement
1.1 Alumni form
Alumni database
STUDENT
SECOND LEVEL OF DFD
CHAPTER : 6 CODING
Purpose
Purpose of this phase is to translate the software design in to source code. Dur
ing this phase each components of this design is implemented as the program modu
le and then each of this module is tested.
Code Efficiency
Code Efficiency means how much time this software takes to give response and als
o which recourses it requires. This package is purely database and in this a lot
of data are stored. It takes less time to give response to user. Employees can
fetch out any information relating to project easily and fast.
Optimization of Code
Optimization of examining the application’s performance, and then making decision
about which part of the code to modify to enhance that performance. Performance
refers to Algorithm performances Images size (disk space) Memory Utilization Use
r interface performances Most of the time, we will not be able to optimize for i
ndividual performances characteristic. For example: Optimizing to reduce the com
plied size of an executable (called the image) typically reduces execution speed
, and optimization for speed often results in an increased disc image size.
CHAPTER : 7 TESTING
Software testing is the process of executing software in a controlled manner in
order to answer the question. “Does
the software behaves as specified?”
Software testing is often used in the association with the terms Verification an
d Validation.
Testing Technique
One of the main requirement of the software development is to develop bug free,
reliable system. During the process of development of any application there is a
lways a possibility of some errors being developed.
Testing Approaches :
Following are main types of tests software undergoes :
Black Box Testing
Black Box Testing relates to tests that are performed the at the software interf
ace.
Black Box Testing attempts to finds errors in the following categories:

Incorrect or missing functions. Interface errors. Errors in data structure or ex

ternal database access. Behaviors or performance error. Initialization and termi
nation error.
White Box Testing
White Box Testing is test case design approach that employees the control archit
ecture of the procedural design to produce test cases.
Other types of testing strategies are :

Defect testing Interface testing Alpha and beta testing Object oriented testing
Real time testing
Testing Strategies Unit Testing
This test focuses verification effort on the small unit id design module. Here u
sing test plans prepared in design descriptions as guide, important control path
s are tested to uncover errors within boundary of the modules. Boundary conditio
ns are tested to ensure module operate properly at boundaries established to lim
it or restrict processing. All paths in the control structure are exercised to e
nsure all statements in a module are executed at least once and finally all erro
rs handling paths are tested to see message are intelligent. Corresponds to erro
rs, encountered and provide enough description for the cause of error.
Integration testing : Validation Testing : Output Testing Use Acceptance Testing
CHAPTER : 8 IMPLEMENTATION
User Testing/ User Manual
Even well designed system can succeed or fail because of the way they are operat
ed and used. Therefore the training received by the personnel involved with the
system in various capacities helps and hinders and my even prevent the successfu
l implementation of management information system.
System operators Training
Running of the system successfully depend on the personal working in the compute
r. They are responsible depends on the personal working in the computer center.
User Training
User must be trained on use of equipment. It is imperative that user be properly
trained in methods of entering transactions, editing data formulating queries,
deleting and inserting of records. Weakness in any aspect of training my lead to
awkward situations that creates errors. 1. Fundamentals of computer 2. Training
to provide input to the system 3. Training to get all required information’s from
the system
PROPOSED SOLUTIONS:To develop a system that would recomplish the following: Reduc
e the paperwork and storage area. Improve the output of operators. Improve accur
acy in result. Allow easy navigation through CV’s and company information. Manage
the man and machine resources efficiently. It has user friendly interface having
quick authenticated access to documents.
Easily scalable to grow with changing system requirement. Secured check in, chec
k out & updates. Locate CV’s easily by various parameters.

CHAPTER : 9 MAINTENANCE
Software maintenance is an extremely important activity. The activity is defined
as the process of modifying existing operational software while leaving its pri
mary function intact.
It is useful to divides software maintenance into two categories-
• Software updates – which results in a functional specification for the software. • S
oftware repairwhich leaves the functional specification intact.
H/W Maintenance : The AMC (Annual Maintenance Cost) is
free for one year run the s/w smoothly on h/w in their organization.
S/W Maintenance : I (developer) am responsible for loading
the software and I will provide the fee maintenance of this software for one yea
r but this does not include future up graduation.
Security Measures Taken Authorization- The person who is in change of authorizat
ion
is usually called the authorizer. User identification and password provision to
prevent unauthorized access.
Database Security – Security From Viruses – Authenticate Virus Software Norton
Antivirus 2004 was installed on every machine for virus prevention. Registration
was done so as to get automatic updates in future.
Security of Software – Passwords of the system user and
administrator were aesthetically kept eight characters long and not easily guess
able thought at the development time this was avoided and it was only shared wit
h database administrator and asked to change from time to time.
Backup Backups were designed in proper manner. This
include system backup of NT, Oracle server backup and file system backup. There
is a backup option in the utility menu.
CHAPTER : 10 COST ESTIMATION OF PROJECT
The software project management process begins with a set of activities that are
collectively called project planning. The first of these activities is estimati
on software cost and effort estimation will never be an exact the ultimate cost
of software and effort applied to develop it. The estimation of cost of the proj
ect is a difficult task but we can estimate the cost of the project by various m
ethods. I am using the COCOMO (Constructive Cost Model.). Model 1- The basic COC
OMO model computed software development effort land cost as a function of progra
m size expressed in estimated line of code. The intermediate COCOMO model comput
er software development effort as a function of program size and a set of “cost dr
ivers” that include subjective assessments of product, hardware personnel and proj
ect attributes.
Model 2Model 3- The advanced COCOMO model incorporates all
characteristics of the intermediate version with an assessment of the cost drive
rs impact on each step (analysis, design etc.) of the software engineering proce
ss.
Types of projects :
The COCOMO model are defined for three classes of software projects are-
Organic Project- Relatively small, simple projects in which
small teams with good application experience work to a set of less than rigid re
quirements. Semidetached Project- An intermediate (in size and complexity) softw
are project in which teams with experience levels must meet a mix of rigid and l
ess than rigid requirements. A software project that must development within a s
et of tight hardware, software and operational constraints.
Embedded project-
CHAPTER –11 REPORTS
Reports
The report is the document that contains the information about the document cont
ains what type of matter. There are basically two types of reports 1. User Repor
t 2. System Report
User Report
The user report contains the document how to use the software, what are the vari
ous links. In this project the user have to open only on file. i.e. main program
file, then all the various parts will be display by clicking on the related but
tons.
System Report
While in the system report there are many file having each source code and can b
e maintained by the programmer. The system report is basically use for the syste
m analyst it contains the necessary information which file is associated with ot
her file. It carries information and the source code. So that in future use any
changes can be mode easily. Like here some files.
CHAPTER : 12 FUTURE SCOPE OF THIS PROJECT
This software (Project information Management System) is to be developed as a ge
neralized software package. project has a big scope to do. We can store informat
ion of all the students. CV’s are categorized according to various streams. Variou
s companies can access the information. Students can maintain their information
and can update it. Notifications are sent to students about the companies. Stude
nts can access previous information about placement. This system has scope of im
provement/ amendments. In future, sector can communicate with each other online.
All currently active enquires can also be added in the website to view if onlin
e.
Login Form
Registration Form
Home Page
Recruiters Page
Events Page
Placement staff Page
COMPANY REGISTRATION FORM PAGE
ALLUMNI REGISTRATION PAGE
PHOTO GALLERY PAGE
DATABASE TABLE - ALLUMNI
DATABASE TABLE – COMPANY
Database Table -
Education Info
Database table - Registration
BIBLIOGRAPHY
.Net With C# Software Engineering System Analysis and Design Shibi Panikkar Pank
aj Jalote Elias M. Awad
THANKS TO
Respected
Mr. Pramod Bhatnagar Mrs. Anshum Srivastava Mr. Praveen Sachan & all the Faculty
of LBSIMDS.