Phonebook Management System: Enrolment No: 35490102017

Phonebook Management system
2019
Enrolment No: 35490102017

1
2019
DECLARATION
I hereby declare that this project report entitled “Phonebook management system”,
submitted in the Fairfield institute of management and science, Guru Gobind Singh
Indraprastha University in the partial fulfillment for the award of the Degree of
Bachelor of Computer Application is a authentic record of work done by me under the
guidance of Ms. AMANPREET KAUR during the session from 2011 to November
2011
The project has not previously formed the basis for the award of any other degree,
Diploma, Associate ship, Fellowship or other title.
Shelly Bhogal (BCA – 5th Semester)

Enrollment No.: 01790202009

2
2019

3
2019
ACKNOWLEDGEMENT
I am extremely grateful and remain indebted to my guide Ms. AMANPREET KAUR for
being a source of inspiration and for his constant support in the Design, Implementation and
Evaluation of the project. I am thankful to her for constant constructive criticism and
invaluable suggestions, which benefited me a lot while developing the project on “COLLEGE
WEBSITE”. She has been a constant source of inspiration and motivation for hard work. She
has been very co-operative throughout this project work. With Candor and Pleasure I take
opportunity to express my sincere thanks and obligation to my esteemed guide Ms.
AMANPREET KAUR. Through this column, it would be my utmost pleasure to express my
warm thanks to her for the encouragement, co-operation and consent without which we
mightn’t be able to accomplish this project.
I would like to express my gratitude towards Mr. KULDEEP SINGH, Mr. MANPREET
SINGH, Mr. RAJ KUMAR KASHYAP & member of Sri Guru Tegh Bahadur Institute Of
Management & Information Technology for their kind co-operation and encouragement
which help me in completion of this project.
My thanks and appreciations also go to my team members Ankita Aggarwal, Himani,

Shreya Gupta, Jagpreet Singh, Srishti Kapoor in developing the project and people who have
willingly helped me out with their abilities.
Finally, I gratefully acknowledge the support, encouragement & patience of my

family, and as always, nothing in my life would be possible without God, Thank You!
SHELLY BHOGAL

4
2019

5
2019
CERTIFICATE
This is to certify that Ms. Shelly Bhogal, University Enrollment Number- 01790202009 has
worked under my supervision to prepare this project report of “COLLEGE WEBSITE”. The
work embodied in this report is original and is of the standard expected of B.C.A Student and
has not been submitted in part or full to this or any university for the award of any degree or
diploma , She has completed all requirements of guidelines for research project and the work
is fit for evaluation.
Signature of Director: Dr. Prof. PL Sethi
Date:
Place: Delhi
Signature of HOD(IT) : Ms. Amanpreet Kaur
Signature of Guide: Ms. Amanpreet Kaur

6
2019

7
2019
ABSTRACT
This college website is designed to provide a more interactive and dynamic site because the
existing college website is static which makes it less interactive. It doesn't have database
connectivity. Moreover students didn't have an access to the details of the college through the
site, hence they were not updated about the latest events and placement drives.
The old website is less dynamic and there is no connectivity with database of website.
Students didn’t have any access to the details of college.
Every college website must be dynamic which can provide the whole information about the
college which facilitates the students, teachers, companies and even the young blood for
having admission in the college.
In order to make the site dynamic and more interactive we have tried to include a database
link to our college website. Hence the recruiters have been provided with the facility to post
their eligibility criteria, vacancies and salary packages. In response to which a student can
submit his willingness to appear for the drive along with his personal details. Provision has
also been made to display the latest events and announcements associated with the college
online.

8
2019

9
2019
CHAPTER 1
INTRODUCTION
1.1 ABOUT THE TOPIC
A website is a collection of Web pages, images, videos and other digital assets that is hosted
on one or several Web server, usually accessible via the Internet, cell phone or a LAN.
The pages of websites can usually be accessed from a common root URL called the
homepage, and usually reside on the same physical server. The URLs of the pages organize
them into a hierarchy, although the hyperlinks between them control how the reader perceives
the of links and images, which enables a browser to easily interpret and access the properties
of the site. Hence it provides the browser with adequate information and functionality about
the organization, community, network etc.
overall structure and how the traffic flows between the different parts of the sites. A website
requires attractive design and proper arrangement
1.2 ABOUT THE PROJECT
The website has been developed for our college (SGTBIM&IT) in an effort to make it as
attractive and dynamic as possible. Compared to the existing site a database has been added to
our project.
The working of the project is as follows:
The first page provides several links. The Home page contains several information about the
site like campus, management, facilities, infrastructure, about faculties etc.
Student and faculty Login module helps the user to login to the site. For that he must type the
username and password correctly. The login provision in this page helps the already
registered user to directly access the site and there is a link for registration to a user who is
new to this site.

10
2019
Member Registration module helps the new user to register into the site. The information
entered by the users is added into the table registration.
In the Login link a recruiter can login using the appropriate Username and password, through
which he can submit the required criteria for a student to appear for a placement drive. He can
also post the number of vacancies that are available and the salary packages offered.
The flash news and the events corner display the latest developments, announcements and
events associated with the college activities.
The administrator has the responsibility for displaying the recruiters form on the notice board,
in response to which student can submit his willingness to attend the drive along with his
resume.

11
2019

12
2019
CHAPTER 2
PROJECT DESCRIPTION
2.1 OBJECTIVE OF THE PROJECT
The objective of the project is to provide an interactive and more dynamic website to give a
full view of the college to the students for day to day activities of college, teachers for
uploading the notifications, companies for recruitments and the new students for admission.
2.2 SCOPE OF THE PROJECT
This website will be the centralized website which provide information about the admission
procedure, fee structure etc to the students and visitors and provide specific details about the
college. It really enhance the user satisfaction because it has full details about college.
2.3 SYSTEM ANALYSIS
System analysis is the process of gathering and interpreting facts, diagnosing problems and
using the information to recommend improvements on the system. System analysis is a
problem solving activity that requires intensive communication between the system users and
system developers.
System analysis or study is an important phase of any system development process. The
system is studied to the minutest detail and analyzed. The system analyst plays the role of an
interrogator and dwells deep into the working of the present system. The system is viewed as
a whole and the inputs to the system are identified. The outputs from the organization are
traced through the various processing that the inputs phase through in the organization.
A detailed study of these processes must be made by various techniques like Interviews,
Questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion. The conclusion is an understanding of how the system functions. This system is
called the existing system. Now, the existing system is subjected to close study and the
problem areas are identified. The designer now functions as a problem solver and tries to sort
out the difficulties that the enterprise faces. The solutions are given as a proposal. The
proposal is then weighed with the existing system analytically and the best one is selected.
The proposal is presented to the user for an endorsement by the user. The proposal is
reviewed on user request and suitable changes are made.

13
2019
2.4 EXISTING SYSTEM
The existing college website is static which makes it less interactive. It doesn't have database
connectivity. Moreover students didn't have an access to the details of the college through the
site, hence they were not updated about the latest events and placement drives.
2.5 PROPOSED SYSTEM
In order to make the site dynamic and more interactive we have tried to include a database
link to our college website. Hence the recruiters have been provided with the facility to post
their eligibility criteria, vacancies and salary packages. In response to which a student can
submit his willingness to appear for the drive along with his personal details. Provision has
also been made to display the latest events and announcements associated with the college
online. We have developed our project using the three tier architecture which uses the
following languages.
2.6 SDLC Approach
The software development life cycle (SDLC) is the process based standard practice to
develop any kind of software product. These processes are categories as phases in SDLC and
related to different activities. Different models are described in software engineering text
books, but none is fully satisfied all the need of a software companies. Some SDLC models
are Water Fall Model, Spiral Model, Prototype Model etc.
Our Project is based on Waterfall Model:

14
2019
Requirement Analysis and Software Definition:
This is the first phase of waterfall model which includes a meeting with the customer to
understand his requirements. This is the most crucial phase as any misinterpretation at this
stage may give rise to validation issues later. The software definition must be detailed and
accurate with no ambiguities. It is very important to understand the customer requirements
and expectations so that the end product meets his specifications.
System Design:
The customer requirements are broken down into logical modules for the ease of
implementation. Hardware and software requirements for every module are identified and
designed accordingly. Also the inter relation between the various logical modules is
established at this stage. Algorithms and diagrams defining the scope and objective of each
logical model are developed. In short, this phase lays a fundamental for actual programming
and implementation.
System Implementation:
This is the software process in which actual coding takes place. A software program is written
based upon the algorithm designed in the system design phase. A piece of code is written for
every module and checked for the output.

15
2019
System Testing:
The programmatically implemented software module is tested for the correct output. Bugs,
errors are removed at this stage. In the process of software testing, a series of tests and test
cases are performed to check the module for bugs, faults and other errors. Erroneous codes
are rewritten and tested again until desired output is achieved.
System Deployment and Maintenance:
This is the final phase of the waterfall model, in which the completed software product is
handed over to the client after alpha, beta testing. After the software has been deployed on the
client site, it is the duty of the software development team to undertake routine maintenance
activities by visiting the client site. If the customer suggests changes or enhancements the
software process has to be followed all over again right from the first phase i.e requirement
analysis. This is the biggest shortcoming of the waterfall model.
The different phases of a typical SDLC are as:

1. Request for Project (RFP)
The first stage is the RFP wherein a request to start a project is made. The request can be
made either by the tip management or end users .
2. Detailed requirement Gathering
As the PRF is signed off /approved, requirement gathering starts.Business Analysts gather
the requirements from the user and prepare a SRS document. This document then needs to be
signed off by the user to approve that the requirements mentioned in SRS have been rightly
comprehended.

16
2019
3. Design
After the SRS sign off, design phase starts, wherein the software development starts at the
vendors end. Here also, two types of documents are prepared.
a. High Level design Documents

These documents contain Data Flow diagrams, Process Flow Charts etc. This document some
time called Architecture Design Document, because it described the architecture view of the
proposed software product.
b. Low Level Design Documents

These contain the database level design information i.e. the details about the fields etc. This
document described the pseudo code for the various algorithms or logic used to build the
software. This documents contained module level design of the software .
4. Development
Post finalization of the software design, development team uses the design document to
develop individual software units.
Post completion of development, the development team does the unit testing and initiate
System Integration Testing (SIT).
On successful completion of testing, the software is released for UAT ( User Acceptance
Testing).
5. Testing
Before software is deployed it is tested to check if it meets all the requirement criteria. For
this, a System Test Plan with System Test Cases is prepared.
6. Implementation
After the User signs off the developed software, a pilot is implemented.
7. Maintenance
It is the post implementation maintenance, wherein the performance of the software is
monitored.

17
2019

18
2019
CHAPTER 3
REQUIREMENT ANAYLISIS
3.1 INTRODUCTION:
Requirements analysis in systems engineering and software engineering, encompasses those

tasks that go into determining the needs or conditions to meet for a new or altered product,
taking account of the possibly conflicting requirements of the various stakeholders, such as
beneficiaries or users. It is an early stage in the more general activity of requirements
engineering which encompasses all activities concerned with eliciting, analyzing,
documenting, validating and managing software or system requirements.
Requirements analysis is critical to the success of a systems or software project. The

Requirements should be documented, actionable, measurable, testable, traceable, related to
identified business needs or opportunities, and defined to a level of detail sufficient for
system design.
Requirements analysis involves frequent communication with system users to determine
specific feature expectations, resolution of conflict or ambiguity in requirements as demanded
by the various users or groups of users, avoidance of feature creep and documentation of all
aspects of the project development process from start to finish. Energy should be directed
towards ensuring that the final system or product conforms to client needs rather than
attempting to mold user expectations to fit the requirements.
Requirements analysis is a team effort that demands a combination of hardware, software and
human factors engineering expertise as well as skills in dealing with people.

19
2019
Software Requirements Specification
Some key points that need to be evaluated on the Requirements Specification document are:
1. Clarity of the specification document

2. Validity of the assumptions made
3. Understanding of the same by all the team-members
4. Quality of the presentation
No. Requirement Essential Description of the Remarks

or Requirement
Desirable
RS The system should Essential A user can login by The logins are
1 have a login opening login assigned by the
window. Admin
RS The system must not Essential This feature will
2 allow anyone else to improve the
login if one user is robustness of the
already logged in application
RS The system should Essential Only Admin can
3 provide page for new create or delete
registration creating users
new user / removing
old users.
RS The system should Essential Visitors can search This will make
4 provide Search for the the details available it easy for
College details in website without students to get
logging in. details about
college

20
2019
3.2 MINIMUM SOFTWARE REQUIREMENTS
OPERATING SYSTEM WINDOWS ,

BROWSER INTERNET EXPLORER 6.0 OR ANY
HTTP BROWSER
FRONT END ASP.NET
DATABASE SQL SERVER 2000
WEB SERVER IIS
SERVER SIDE SCRIPTING C#.NET,VB.NET
CLIENT SIDE SCRIPTING JAVA SCRIPT
CONNECTION PROTOCOL TCP / IP
3.3 MINIMUM HARDWARE REQUIREMENTS
PROCESSOR P IV
RAM 128 MB
HDD 40GB
MODEM 56 KBPS
RESOLUTION 800X600

21
2019
3.4 REQUIREMENT CAPTURE PROCESS
To get the requirements down on paper, you can to do one or more of the following:
 Conduct a brainstorming session

 Interview users
 Send questionnaires
 Work in the target environment
 Study analogous systems
 Examine suggestions and problem reports
 Talk to support teams
 Study improvements made by users
 Look at unintended uses
 Conduct workshops
 Demonstrate prototypes to stakeholders
In this project we have used following techniques for gathering the requirements for our
project: COLLEGE WEBSITE
Conduct a brainstorming session:
Brainstorming is a short group session where everyone is allowed to say whatever they feel is
important to the topic of discussion. After that, a facilitator leads the group in organizing and
prioritizing the results. The following basic rules for brainstorming ensures better results:
 Start out by clearly stating the objective of the brainstorming session.

 Generate as may ideas as possible.
 Let your imagination soar.
 Do not allow criticism or debate while you are gathering information.
 Once information is gathered, reshape and combine ideas.
We have discussed our project with our HOD, faculty members, students about their
requirements which they want in their college website.

22
2019
Interview users:
Face-to-face contact with users through individual interviewing is the primary source of
requirements and an important way you gather and validate their requirements. Remember
that it is not the only possible technique, and that you can conduct interviews many different
ways. Develop a repertoire of styles to fit different situations. Unless you use the system
yourself, you will need to make an effort to understand and experience the user's problem to
describe it clearly and correctly.
We have taken an interview of our college administrator officer Mr. Kuldeep Singh for
requirements of college website. As the administrator officer, he suggested us about the
modules and the working of their modules.
He gave us many information related to our college website such as:
 Introduction about college
 History of college
 Messages of Chairman, President, Director, Director General, Treasurer, General
Secretary of our college
 Fee structure
 Mark sheets
 Attendance sheet
 Information of Faculties
 Information about students
 Information about infrastructure( Computer Lab, Library, Classrooms, Sports Room,
Medical Room, Canteen)
 Information about achievements and activities
 KUDOS
Talk to support teams:
In this project we have six team members :
 Shelly Bhogal (TEAM LEADER)

 Ankita Aggarwal
 Himani
 Shreya Gupta
 Jagpreet Singh
 Srishti Kapoor
While gathering the requirement of our college website project, we have also discussed with
our team members about their requirements.

23
2019

24
2019
CHAPTER 4
TOOLS AND TECHNOLOGIES USED
Front End ASP.NET
Middle End C#.Net,VB.Net
Back End SQL SERVER 2000
Connectivity ADO.NET
4.1 ASP.NET - FRONT END
ASP.NET is not just a simple upgrade or the latest version of ASP. ASP.NET
combines unprecedented developer productivity with performance, reliability, and
deployment. ASP.NET redesigns the whole process. It's still easy to grasp for new
comers but it provides many new ways of managing projects. Displaying data,
validating user input, and uploading files are all amazingly easy. Best of all, ASP.NET
pages work in all browsers including Netscape, Opera, AOL, and Internet Explorer.
 Flexible Language Options :

ASP.NET lets you leverage your current programming language skills. Unlike classic
ASP, which supports only interpreted VBScript and J Script, ASP.NET now supports
more than 25 .NET languages (built-in support for VB.NET, C#, and JScript.NET),
giving us unprecedented flexibility in the choice of language.

25
2019
 Great Tool Support :
We can harness the full power of ASP.NET using any text editor, even Notepad. But Visual
Studio .NET adds the productivity of Visual Basic-style development to the Web. Now we
can visually design ASP.NET Web Forms using familiar drag-drop-double click techniques,
and enjoy full-fledged code support including statement completion and color-coding.
VS.NET also provides integrated
Below are the features of ASP.NET :
 Easy Programming Model:

ASP.NET makes building real world Web applications dramatically easier.ASP.NET
server controls enable an HTML-like style of declarative programming that let you
build great pages with far less code than with classic ASP.
support for debugging and deploying ASP.NET Web applications. The Enterprise
versions of Visual Studio .NET deliver life-cycle features to help organizations plan,
analyze, design, build, test, and coordinate teams that develop ASP.NET Web
applications. These include UML class modeling, database modeling (conceptual,
logical, and physical models), testing tools (functional, performance and scalability),
and enterprise frameworks and templates, all available within the integrated Visual
Studio .NET environment.
 Rich Class Framework:

Application features that used to be hard to implement, or required a 3rd-party
component, can now be added in just a few lines of code using the .NET Framework.
The .NET Framework offers over 4500 classes that encapsulate rich functionality like
XML, data access, file upload, regular expressions, image generation, performance
monitoring and logging, transactions, message queuing, SMTP mail, and much more.
With Improved Performance and Scalability ASP.NET lets we use serve more users
with the same hardware.

26
2019
 Compiled execution:
ASP.NET is much faster than classic ASP, while preserving the "just hit save" update
model of ASP. However, no explicit compile step is required. ASP.NET will
automatically detect any changes, dynamically compile the files if needed, and store
the compiled results to reuse for subsequent requests. Dynamic compilation ensures
that the application is always up to date, and compiled execution makes it fast. Most
applications migrated from classic ASP see a 3x to 5x increase in pages served.
 Enhanced Reliability:
ASP.NET ensures that the application is always available to the users.
 Memory Leak, Dead Lock and Crash Protection:

ASP.NET automatically detects and recovers from errors like deadlocks and memory
leaks to ensure our application is always available to our users. For example, say that
our application has a small memory leak, and that after a week the leak has tied up a
significant percentage of our server's virtual memory. ASP.NET will detect this
condition, automatically start up another copy of the ASP.NET worker process, and
direct all new requests to the new process. Once the old process has finished
processing its pending requests, it is gracefully disposed and the leaked memory is
released. Automatically, without administrator intervention or any interruption of
service, ASP.NET has recovered from the error.
 Easy Deployment:
ASP.NET takes the pain out of deploying server applications. "No touch" application
deployment. ASP.NET dramatically simplifies installation of our application. With
ASP.NET, we can deploy an entire application as easily as an HTML page, just copy it
to the server. No need to run regsvr32 to register any components, and configuration
settings are stored in an XML file within the application.
 Dynamic update of running application

ASP.NET now lets we update compiled components without restarting the web server.
In the past with classic COM components, the developer would have to restart the web
server each time he deployed an update. With ASP.NET, we simply copy the
component over the existing DLL, ASP.NET will automatically detect the change and
start using the new code.

27
2019
4.2 C#.NET - MIDDLE END
4.2.1 Introduction to C#.NET

In brief, C#.NET a next generation of ASP (Active Server Pages) introduced by Microsoft.
Similar to previous server-side scripting technologies, C#.NET allows us to build powerful,
reliable, and scalable distributed applications. C#.NET is based on the Microsoft .NET
framework and uses the .NET features and tools to develop Web applications and Web
services.
Even though C#.NET sounds like ASP and syntaxes are compatible with ASP but C#.NET is
much more than that. It provides many features and tools, which let we develop more reliable
and scalable, Web applications and Web services in less time and resources. Since C#.NET is
a compiled, .NET-based environment; we can use any .NET supported languages, including
VB.NET, C#, JScript.NET, and VBScript.NET to develop C#.NET applications.
4.2.2 Advantages of C#.NET
1 .NET Compatible
.NET compatibility feature of C#.NET provides applications to use the features provides by
.NET. Some of these features are multi-language support, compiled code, automatic memory
management, and .NET base class library.
We have choice to select a programming language. We can write Web applications using any
.NET supported language, including C#, VB.NET, JScript.NET and VBScript.NET.
All C#.NET code is compiled, rather than interpreted, which allows early binding, strong
typing, and just-in-time (JIT) compilation to native code, automatic memory management,
and caching.
The .NET base class library (BCL) provides hundreds of useful classes. This library can be
accessed from any. NET supported language.
2. Web Forms and Rapid Development

Web Forms allows you to build rapid Web GUI applications. Web Forms provides us web
pages and server side controls. We can use web forms and server side controls in VS.NET
similar to we write Windows applications. VS.NET provides Windows application similar
drag and drop features, which allows us to drag server side controls on a page and set control
properties and write event handlers by using wizard property page. The VS.NET framework
writes code for us under the hood and our application is ready in no time. In most of the
cases, we don't even need to know what wizards write for us under the hood.
3. Native XML Support and XML Web Services

XML is a vital part of entire .NET framework. . NET uses XML to store and transfer data
among applications. The .NET base class library provides high-level programming model
classes, which can be used to work with XML.

28
2019
An XML Web service provides the means to access server functionality remotely. Web
services use SOAP (Simple Object Access Protocol) to provide access to clients. Web
services can be used to build different layers of distributed applications and we can use
different layers remote
4. Databases and ADO.NET

ADO.NET is a new version of ADO (ActiveX Data Objects). Event though ADO.NET
sounds like ADO, but it are a complete redesigned database access technology. ADO.NET
allows us to access different kinds of databases using only one programming model. We must
be familiar with DAO, ADO, ODBC, RDO and other database access technologies previous
to ADO.NET. Each of these technologies had its own pros and cons. ADO.NET combines
features of all of these techniques and provides a single higher level-programming model and
hides all details for us. It makes our job much simpler and provides a way to write rapid
development. See ADO.NET section of C# Corner for ADO.NET source code samples and
tutorials.
5. Graphics and GDI+

GDI+ is an improved version of GDI (Graphics Device Interface) to write Windows and Web
graphics applications. The .NET base class library provides GDI classes to write graphics
applications. Using these classes not only we can write Windows applications, but we can
also write Web graphics applications. See GDI+ section of C# Corner for sample applications
and tutorials of GDI+.
6. Caching and State Management

One of the most important factors in building high-performance, scalable Web applications is
the ability to store items, whether data objects, pages, or parts of a page, in memory the initial
time they are requested. We can store these objects on the server or on the client machine.
Storing data on a server or a client is called caching.
C#.NET provides two types of caching - page caching and request caching. We use request
caching to improve code efficiency and to share common data across the pages and we use
page caching to provide fast access to the Web applications from clients.
C#.NET provides easy-to-use application-state and session-state management, which allows
managing states of Web applications. C#.NET also provides cookie less state management,
means we don't need to use cookies to for state storage.
7. Enhanced Security
C#.NET provide us to authenticate and authorize users for our applications. We can easily
remove, add to, or replace these schemes, depending upon the needs of our application.

29
2019
4.3 SQL SERVER 2000 - BACK END
SQL Server 2000 exceeds dependability requirements and provides innovative capabilities
that increase employee effectiveness, integrate heterogeneous IT ecosystems, and maximize
capital and operating budgets. SQL Server 2000 provides the enterprise data management
platform our organization needs to adapt quickly in a fast-changing environment. With the
lowest implementation and maintenance costs in the industry, SQL Server 2000 delivers rapid
return on the data management investment. SQL Server 2000 supports the rapid development
of enterprise-class business applications that can give our company a critical competitive
advantage.
4.4 ADO.NET - DATABASE CONNECTIVITY
Most applications need data access at one point of time making it a crucial component when
working with applications. Data access is making the application interact with a database,
where all the data is stored. Different applications have different requirements for database
access. ASP.NET uses ADO .NET (Active X Data Object) as its data access and
manipulation protocol which also enables us to work with data on the Internet.
ADO.NET Data Architecture
Data Access in ADO.NET relies on main two components: DataSet and Data Provider.
1. Dataset
The dataset is a disconnected, in-memory representation of data. It can be considered as a

local copy of the relevant portions of the database. The Dataset is persisted in memory and
the data in it can be manipulated and updated independent of the database. When the use of
this Dataset is finished, changes can be made back to the central database for updating. The
data in Dataset can be loaded from any valid data source like Microsoft SQL server database,
an Oracle database or from a Microsoft Access database.
2. Data Provider
The Data Provider is responsible for providing and maintaining the connection to the
database. A Data Provider is a set of related components that work together to provide data in
an efficient and performance driven manner. The .NET Framework currently comes with two
Data Providers: the SQL Data Provider which is designed only to work with Microsoft's SQL
Server 7.0 or later and the Ole Db Data Provider which allows us to connect to other types of
databases like Access and Oracle.

30
2019
Each Data Provider consists of the following component classes:
1. The Connection Object
The Connection object creates the connection to the database. Microsoft Visual Studio
.NET provides two types of Connection classes: the SqlConnection object, which is
designed specifically to connect to Microsoft SQL Server 7.0 or later, and the
OleDbConnection object, which can provide connections to a wide range of database
types like Microsoft Access and Oracle. The Connection object contains all of the
information required to open a connection to the database.
2. The Command Object
The Command object is represented by two corresponding classes: SqlCommand and

OleDbCommand. Command objects are used to execute commands to a database across a
data connection. The Command objects can be used to execute stored procedures on the
database, SQL commands, or return complete tables directly.
3. The DataReader Object
The DataReader object provides a forward-only, read-only, connected stream recordset

from a database. Unlike other components of the Data Provider, DataReader objects
cannot be directly instantiated. Rather, the DataReader is returned as the result of the
Command object's ExecuteReader method. The SqlCommand.ExecuteReader method
returns a SqlDataReader object, and the OleDbCommand.ExecuteReader method returns
an OleDbDataReader object. The DataReader can provide rows of data directly to
application logic when we do not need to keep the data cached in memory.
4. The Data Adapter Object
The Data Adapter is the class at the core of ADO .NET's disconnected data access. It is
essentially the middleman facilitating all communication between the database and a
Dataset. The Data Adapter is used either to fill a Data Table or Dataset with data from the
database with its Fill method. After the memory-resident data has been manipulated, the
Data Adapter can commit the changes to the database by calling the Update method.

31
2019
The Data Adapter provides four properties that represent database commands:
SelectCommand, InsertCommand, DeleteCommand and UpdateCommand

When the Update method is called, changes in the Dataset are copied back to the database and
the appropriate Insert Command, Delete Command, or Update Command is executed.
Data access with ADO.NET can be summarized as follows:

A connection object establishes the connection for the application with the database. The
command object provides direct execution of the command to the database. If the command
returns more than a single value, the command object returns a Data Reader to provide the
data. Alternatively, the Data Adapter can be used to fill the Dataset object. The database can
be updated using the command object or the Data Adapter.

32
2019

33
2019
CHAPTER 5
SYSTEM DESIGN
5.1 INTRODUCTION:
System design is the solution to the creation of a new system. This phase is composed of
several systems. This phase focuses on the detailed implementation of the feasible system. It
emphasis on translating design specifications to performance specification. System design
has two phases of development logical and physical design.
During logical design phase the analyst describes inputs (sources), out puts (destinations),
databases (data stores) and procedures (data flows) all in a format that meats the uses
requirements. The analyst also specifies the user needs and at a level that virtually determines
the information flow into and out of the system and the data resources. Here the logical
design is done through data flow diagrams and database design.
The physical design is followed by physical design or coding. Physical design produces the
working system by defining the design specifications, which tell the programmers exactly
what the candidate system must do. The programmers write the necessary programs that
accept input from the user, perform necessary processing on accepted data through call and
produce the required report on a hard copy or display it on the screen.
5.2 TABLE DESIGN

34
2019
5.2.1 TABLE1:
REGISTRATION TABLE
Field Name Data Type Description Key constraint

loginid Int Userid Primary key
username Char(50) Username Not null
Email Varchar(50) User email id Not null
Username Varchar(50) username Not null
Password Varchar(50) Password Not null
Gender Char(10) Gender Not null
Country Char(50) Country name Not null
Address Varchar(50) Address Not null
Marital_status Char(30) Marital status Not null
Date_of_birth Varchar(50) Date of birth Not null
Occupation Char(60) occupation -
5.2.2 TABLE2:
PLACEMENT TABLE
FIELD NAME DATA TYPE DESCRIPTION

Student_name Char (range: upto 10) It includes the names
of the students
Email_id Varchar(range: upto 50) It includes the email
id of the students

35
2019
5.2.3 TABLE3:
FAQ
FIELD NAME DATA TYPE

Question1 nvarchar(100)
Answer1 nvarchar(100)
Answer 4 nvarchar(100)
DESCRIPTION :- At a time user may go for 4 question & answer.
5.2.4 TABLE4:
FEEDBACK
FIELD NAME DATA TYPE DESCRIPTION

name Char (range: upto 10) It stores the name
who gives feedback
Email nvarchar(range: upto 50) It stores the email id
of the user
Category Char(range: upto 10) It select the category
from faculty or
student
Feedbackquery Nvarchar(range: upto It stores the feedback
100) from student and
faculty

36
2019
5.3 DATABASE DESIGN
The overall objective in the development of database technology has been to treat data as an
organizational resource and as an integrated whole. DBMS allow data to be protected and
organized separately from other resources. Database is an integrated collection of data. The
most significant form of data as seen by the programmers is data as stored on the direct access
storage devices. This is the difference between logical and physical data.
Database files are the key source of information into the system. It is the process of designing
database files, which are the key source of information to the system. The files should be
properly designed and planned for collection, accumulation, editing and retrieving the
required information.
The organization of data in database aims to achieve three major objectives: -
 Data integration.
 Data integrity.
 Data independence.
The proposed system stores the information relevant for processing in the MS SQL SERVER
database. This database contains tables, where each table corresponds to one particular type
of information. Each piece of information in table is called a field or column. A table also
contains records, which is a set of fields. All records in a table have the same set of fields
with different information. There are primary key fields that uniquely identify a record in a
table. There are also fields that contain primary key from another table called foreign keys.

37
2019
5.5 DIAGRAMS

38
2019
5.5.1 USE CASE DIAGRAM
1.1 use case diagram for faculty
Login to the
website
Upload notes
Upload
faculty notification

39
2019
1.2 use case diagram for admin
Login to the
website
Register the
students and
faculty
admin

40
2019

41
2019
5.5.2 DATA FLOW DIAGRAM
DATA FLOW DIAGRAM
SYMBOL NAME FUNCTION
Data Flow Connect process
Perform some
Process transformation of its
input data to yield output
data.
A source of system inputs

Source or sink or
sink of system outputs
A repository of data, the
arrowhead indicate net
Data Store input and net outputs
to store

42
2019
5.5.2.1 DATA FLOW DIAGRAM (0 level)
Faculty Students
College website
Visitors Admin

43
2019
Account info Retrieve account info
Display Student & Register student

faculty info & faculty Access
students &
Enter/Update faculty info
/Delete
ADMINISTRATOR
Login
Enter user Enter user
id & id &
STUDENT password password FACULTY
TT
UPLOADS
VIEW DOWNLOD
Notes Notes Notification

s
Resul Attendance
t

44
2019
a.) DATA FLOW DIAGRAM FOR ADMIN
Access students & faculty info

Administrator
Enter/update/delete
Display student & faculty
info
Register student &

faculty
Account info

45
2019
B.) DATA FLOW DIAGRAM FOR LOGIN
ACCOUNT INFO
FACULTY ENTER USER_ID, PASSWORD LOGIN
STUDENT ENTER USER_ID, PASSWORD

46
2019
C.) DATA FLOW DIAGRAM FOR STUDENT
Student details
GIVES
LOGIN
FAQ FEEDBACK
VIEW
Result Course
Attendance
Activities

47
2019
D.) DATA FLOW DIAGRAM FOR FACULTY
FACULTY ACCESS INFORMATION
DISPLAY INFO
FILE
UPLOAD
UPLOAD NOTES&
NOTIFICATIONS

48
2019
5.6 HOME PAGE
The home page of a website is the first page that a user perceives upon entering the website
URL at the browser address area. The entire website depends on how the home page is
designed which forms the platform for viewing other web forms. In short, a home page forms
the abstract of the entire website.
The SGTBIM&IT website begins with an interactive home page in which a recruiter
username and password can be entered. A validation is performed at the database to verify
whether the recruiter is an already authorized user, if not a recruiter is allowed to sign in by
filling up the necessary details on a form. The home page appears as given below.
5.6.1 HOME PAGE
Home page is the first look of our website. There are photo gallery of college campus,
information about college and many more options to explore our college website.

49
2019
There is a menu in which many menu items are there which gives information about our
faculties, students, infrastructure, departments etc.
5.6.2 LINKS AND WEBPAGES
Through the home page a number of other web pages can be linked. Each link gives an
elaborated detail about itself with adequate lists and photos
Quick links are there through which you can easily go to that option without navigating so
much.

50
2019

51
2019
CHAPTER 6
MY ROLES AND RESPOSNSIBILITY
As team leader of the website project, I was given the following responsibilities:
 I was involved in the requirement gathering for Phone Book management system.
 Divide the work among the team members
 I was responsible for documenting the requirement.
 I was responsible for creating the code and checking whether it is working properly or
not.
 I am also responsible for coding and implementation of the following modules:
 Designing of Pages including Master Page, Home page and other main pages for
Website
 Academics module
 Kudos module
 Notes Upload
 Location Map
 Search Module

52
2019

53
2019
CHAPTER 7
PROTOTYPE

54
2019
Code:
#include<fstream.h>
#include<conio.h>
#include<stdio.h>
//Prototypes of Functions used in the project
void menu(); //Function to display menu options and run project
void AddNumber(); //Function to add new record in a Binary File.
void DisplayRecords(); //Function to read data file & display on screen.
void SearchBySrNo(); //Function to search and display record by sr no.
void deleteRecord(); //Function to delete a specific record from file.
void modifyRecord(); //Function to modify a specific record in file.
//Declaration and Definition of Class
class PhoneBook{
int srno;
char name[25];
char mobile[15];
char email[30];
char group[20];
public:
int getSrNo() {return srno;}
void storeData()
cout<<"\n...............CREATE NEW PHONE RECORD...............\n";
cout<<"Enter Serial Number : "; cin>>srno; cin.ignore();

55
2019
cout<<"Enter Record Name : "; cin.getline(name,25);
cout<<"Enter Mobile Number : "; cin.getline(mobile,15);
cout<<"Enter E-Mail I. D. : "; cin.getline(email,30);
cout<<"Enter Record Group : "; cin.getline(group,20);
cout<<endl;
void showData()
cout<<"\n...............PHONE BOOK RECORD...............\n";
cout<<"Sr. No. : "<<srno<<endl;
cout<<"Name : "<<name<<endl;
cout<<"Mobile No. : "<<mobile<<endl;
cout<<"Email ID : "<<email<<endl;
cout<<"Group : "<<group<<endl;
}b;
void AddNumber()
ofstream fout;
fout.open("PhonBook.dat",ios::out|ios::binary|ios::app);
b.storeData();
fout.write((char*)&b,sizeof(b));
fout.close();
cout<<"\nRecord Saved to File......\n";

56
2019
}
void DisplayRecords()
ifstream fin;
fin.open("PhonBook.dat",ios::out|ios::binary|ios::app);
while(fin.read((char*)&b,sizeof(b)))
b.showData();
fin.close();
cout<<"\nReading of Data File Completed......\n";
void SearchBySrNo()
ifstream fin;
int n, flag=0;
cout<<"Enter Serial Number of Record To Display: ";
cin>>n;

57
2019
{
if(n==b.getSrNo())
b.showData();
flag++;
cout<<"\n\n.....Record Found and Displayed......\n";
fin.close();
if(flag==0)
cout<<"\nThe Record of Serial Number "<<n<<" is not in file....\n";
void deleteRecord()
ifstream fin;
ofstream fout;
int n, flag=0;
fout.open("temp.dat",ios::out|ios::binary);
cout<<"Enter Serial Number of Record To Delete : ";
cin>>n;

58
2019
{
if(n==b.getSrNo())
cout<<"\nThe Following record is deleted....\n";
b.showData();
flag++;
else
fout.write((char*)&b,sizeof(b));
fin.close();
fout.close();
if(flag==0)
remove("PhonBook.dat");
rename("temp.dat","PhonBook.dat");
void modifyRecord()
fstream fio;
int n, flag=0,pos;

59
2019
fio.open("PhonBook.dat",ios::out|ios::binary|ios::in);
cout<<"Enter Serial Number of Record To Modify : ";
cin>>n;
while(fio.read((char*)&b,sizeof(b)))
pos=fio.tellg();
if(n==b.getSrNo())
cout<<"\nThe Following record will be modified....\n";
b.showData();
flag++;
cout<<"\nRe-Enter the New Details.....\n";
b.storeData();
fio.seekg(pos-sizeof(b));
fio.write((char*)&b,sizeof(b));
cout<<"\n....Data Modified Successfully....\n";
fio.close();
if(flag==0)

60
2019
void menu()
int ch;
do
clrscr();
cout<<"............................................\n";
cout<<" PHONE BOOK MANAGEMENT\n";
cout<<"............................................\n\n";
cout<<"::::::::::::::: PROGRAM MENU :::::::::::::::\n";
cout<<"0. Exit\n";
cout<<"1. Save New Phone Record\n";
cout<<"2. Display All Saved Records\n";
cout<<"3. Search Specific Record\n";
cout<<"4. Delete Specific Record\n";
cout<<"5. Modify Existing Record\n";
cout<<"Enter Your Choice : ";
cin>>ch;
clrscr();
switch(ch)
case 1: AddNumber(); break;
case 2: DisplayRecords(); break;
case 3: SearchBySrNo(); break;

61
2019
case 4: deleteRecord(); break;
case 5: modifyRecord(); break;
getch();
}while(ch);
void main()
menu();

62
2019
PREVIOUS YEAR QUESTION PAPERS
SYLLABUS

63
2019
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master" AutoEventWireup="true"

CodeFile="Feedback.aspx.cs" Inherits="Feedback" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<style type="text/css">
.style31
{
color: #006666;
font-size: 20pt;
}
.style32
{
width: 56%;
height: 112px;
border-style: solid;
border-width: 2px;
border-color:Teal;
}
.style33
{
text-align: center;
}
.style34
{
text-align: left;
width: 190px;
}
.style35
{
width: 190px;
64
2019
}
.style36
{
color: #C0C0C0;
font-size: 15pt;
}
.style38
{
width: 100%;
border-style: solid;
border-width: 2px;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
<p>
<br />
;<span class="style31">        FEEDBACK</span></p>
<p>
<asp:Label
ID="Label6" runat="server" Text="Hello, Give Your Feedback here !!! "></asp:Label>
<table align="center" class="style32">
<tr>
<td bgcolor="#006666" colspan="2">


<span class="style36">   ENTER YOUR FEEDBACK </span></td>
</tr>
<tr>
<td class="style33">
<asp:Label ID="Label1" runat="server" Text="Name"></asp:Label>
</td>
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="TextBox1"
ErrorMessage="RequiredFieldValidator"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<asp:Label ID="Label2" runat="server" Text="Email ID"></asp:Label>
</td>
<asp:TextBox ID="TextBox2" runat="server"></asp:TextBox>
<asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server"
ControlToValidate="TextBox2" ErrorMessage="Email is not valid"
ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*"
Width="146px"></asp:RegularExpressionValidator>
</td>
</tr>
65
2019
<tr>
<asp:Label ID="Label4" runat="server" Text="Category"></asp:Label>
</td>
<asp:DropDownList ID="DropDownList1" runat="server">
<asp:ListItem>Student</asp:ListItem>
<asp:ListItem>Faculty</asp:ListItem>
</asp:DropDownList>
</td>
</tr>
<tr>
<asp:Label ID="Label5" runat="server" Text="Feedback"></asp:Label>
</td>
<asp:TextBox ID="TextBox4" runat="server" Rows="5"
TextMode="MultiLine"></asp:TextBox>
<br />
<asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server"
ControlToValidate="TextBox4"
ErrorMessage="RequiredFieldValidator"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
</td>
<asp:Button ID="Button1" runat="server" Text="Submitt" onclick="Button1_Click"
style="height: 26px" />

<asp:Button ID="Button2" runat="server" onclick="Button2_Click" Text="Clear" />
</td>
</tr>
</table>
</p>
</asp:Content>
<table class="style38" style="border-color: #800080">
<tr>
<td>
<asp:Image ID="Image2" runat="server"
ImageUrl="~/sidebarimages/coollogo_com-48371766.png" />
</td>
</tr>
66
2019
<tr>

<asp:ImageButton ID="ImageButton11" runat="server" Height="50px"
ImageUrl="~/sidebarimages/sitemap.jpg" onclick="ImageButton11_Click"
Width="90px" />
</td>
</tr>
</table>
<br />
<tr>
</td>
</tr>
<tr>
<td>

ImageUrl="~/sidebarimages/events.jpg" onclick="ImageButton13_Click"
Width="90px" />
</td>
</tr>
</table>
             <br />
<br />
<br />
<tr>
<td>
</td>
</tr>
<tr>
<td>

ImageUrl="~/sidebarimages/kudos.jpg" onclick="ImageButton14_Click"
Width="90px" />
</td>
</tr>
</table>
             <br />
<br />
<tr>
<td>
67
2019
</td>
</tr>
<tr>
<td>

ImageUrl="~/sidebarimages/stduent.jpg" onclick="ImageButton15_Click"
Width="90px" />
</td>
</tr>
</table>
             <br />
<br />
<br />
<table class="style38" style="border-color: #99FF33">
<tr>
<td>
</td>
</tr>
<tr>
<td>

ImageUrl="~/sidebarimages/faculty.jpg" onclick="ImageButton17_Click"
Width="90px" />
</td>
</tr>
</table>
</asp:Content>
<marquee runat="server">
"Always remember ,action speaks louder than word.!!"
</marquee>
</asp:Content>
<p>
<strong> <span class="style25; All
rights are © www.sgtbimit.com</span> </strong></p>
</asp:Content>
using System;
using System.Collections.Generic;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;

68
2019
public partial class Feedback : System.Web.UI.Page
{
SqlConnection con;
protected void Page_Load(object sender, EventArgs e)
{
con = new SqlConnection(@"Data
Source=(local)\SqlExpress;AttachDbFilename=|DataDirectory|\collegedetails.mdf;Integrated
Security=True;User Instance=True ");
con.Open();
}
protected void Button2_Click(object sender, EventArgs e)
{
TextBox1.Text = "";
TextBox2.Text = "";
TextBox4.Text = "";
}
protected void Button1_Click(object sender, EventArgs e)
{
SqlCommand cmd = new SqlCommand("insert into feedback

values(@name,@email,@category,@feedbackquery)", con);
cmd.Parameters.Add(new SqlParameter("@name", TextBox1.Text));

cmd.Parameters.Add(new SqlParameter("@email", TextBox2.Text));
cmd.Parameters.Add(new SqlParameter("@category", DropDownList1.Text));
cmd.Parameters.Add(new SqlParameter("@feedbackquery", TextBox4.Text));
//try
//{
int res = cmd.ExecuteNonQuery();
if (res > 0)
{
Response.Redirect("~/home.aspx");
}
else
{
Label6.Text = "Try Again!!!!";
}
//}
//catch
//{
// TextBox1.Text = "";
//}
//cmd = new SqlCommand("insert into userid values(@id,@password)", con);
//cmd.Parameters.AddWithValue("@id", TextBox19.Text);
//cmd.Parameters.AddWithValue("@password", TextBox20.Text);
//cmd.ExecuteNonQuery();
con.Close();
}
69
2019
protected void ImageButton11_Click(object sender, ImageClickEventArgs e)
{
Response.Redirect("~/sitemap.aspx");
}
{
Response.Redirect("~/FEST.aspx");
}
{
Response.Redirect("~/KUDOS.aspx");
}
{
Response.Redirect("~/student.aspx");
}
{
Response.Redirect("~/facultyinfo.aspx");
}
}
UPLOAD
using System;
public partial class _Default : System.Web.UI.Page

{

70
2019
protected void btnAddNew_Click(object sender, EventArgs e)
{
Response.Redirect("~/UploadFile.aspx");
}
protected void GridView1_RowDataBound(object sender, GridViewRowEventArgs e)

{
switch (e.Row.RowType)
{
case DataControlRowType.DataRow:
FileInfo myFileInfo = (FileInfo)e.Row.DataItem;
switch (myFileInfo.ContentType.ToLower())
{
case "image/pjpeg": // .jpg files
case "image/gif": // .gif files
case "application/msword": // .doc files
case "text/plain": // .txt files
// Do nothing. When the row contains a viewable type,
// we want the View link to be enabled.
break;
default:
// Find the View link and disable it.
HyperLink myLink = (HyperLink)e.Row.FindControl("lnkView");
myLink.Enabled = false;
break;
}
break;
}
}
protected void odsFiles_Selecting(object sender, ObjectDataSourceSelectingEventArgs e)
{
}
}

71
2019
using System;
using System.Collections.Generic;
using System.IO;
using System.Web;
using System.Web.UI;
public partial class UploadFile : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void btnUpload_Click(object sender, EventArgs e)
{
if (FileUpload1.HasFile)
{
string contentType = FileUpload1.PostedFile.ContentType;
// Get the bytes from the uploaded file

byte[] fileData = new byte[FileUpload1.PostedFile.InputStream.Length];
FileUpload1.PostedFile.InputStream.Read(fileData, 0, fileData.Length);
// Get the name without folder information from the uploaded file.
string originalName = Path.GetFileName(FileUpload1.PostedFile.FileName);
72
2019
// Create a new instance of the File class based on the uploaded file.
File myFile = new File(contentType, originalName, fileData);
// Save the file, and tell the Save method what data store to use.
switch (AppConfiguration.DataStoreType)
{
case DataStoreType.Database:
myFile.Save();
break;
case DataStoreType.FileSystem:
myFile.Save(Server.MapPath(Path.Combine(AppConfiguration.UploadsFolder, myFile.FileUrl)));
break;
}
Response.Redirect("~/");
}
}
}
DATESHEET

73
2019
LOCATION

74
2019

75
2019
CHAPTER 8
VALIDATION
Data given as an input to the system has to be validated so that correct information is stored in
the database.
The users may commit errors while filling the fields with data. Thus data value entered has to
be checked for the correctness as soon as it is entered into the system.
Checks & Controls:

System Security refers to various validations on data in form of checks and controls to avoid
the system from failing. It is always important to ensure that only valid data is entered and
only valid operations are performed on the system. The various checks and controls allow
system to work in extreme conditions. The system employs two types of checks and controls:
Client Side Validations
Various client side validations are used to ensure on the client side that only valid data is
entered. Client side validation saves server time and load to handle invalid data. Some checks
imposed are:
 A program, in which it is required to fill up date in the date fields, validates any date
entered so that meaningless dates are not entered.
 Checks ensure that numeric fields are filled with numeric data only.
 Maximum lengths of the fields of the forms are appropriately defined.
 Forms cannot be submitted without filling up the mandatory data so that manual
mistakes of submitting empty fields that are mandatory can be sorted out at the client
side to save the server time and load. Appropriate messages are displayed to the user if
any mandatory field is left empty.

76
2019
Server side Validations:
Some checks can’t be applied at the client side. Server side checks are necessary to save
the system from failing and intimating the user that same invalid operations have been
performed or the performed operation is restricted. Some of the server side checks
imposed are:
 User is intimated through appropriate messages about the successful operations or

exceptions occurring at server side.
 Access permissions to various types of users are controlled according to the
organizational structure. Only permitted users can log on to the system and can have
access according to their category. User name, Passwords and Permissions are
controlled on the server side. This way unauthorized users cannot intrude into the
system.
 Using server side validation, constraints on several restricted operations are imposed.

77
2019
&

78
2019
CHAPTER 9
TESTING
9.1 Introduction
Executing a program with the intent of finding errors is called testing. Testing is vital to the
success of any system. Testing is done at different stages within the development phase.
System testing makes a logical assumption that if all parts of the system arte correct, the goals
will be achieved successfully. Inadequate testing or no testing at all leads to errors that may
come up after a long time when correction would be extremely implementation. The testing
of the system was done on both artificial and live data. In order to test data test cases are
developed. Following are the various methods that are employed for testing:
Unit Testing
In unit testing the module is tested independently. It is done to test that the module does
satisfy the functional specification. This is done to check syntax and logical errors in
programs. At the time of preparation of technical specifications, unit test data was also
prepared. The coding for that program was considered after verifying its output against this
test data.
Following are the unit testing methods:

In Conditional Testing, the logical conditions that are given in the module were checked to
see whether they satisfy the functionality of the module. This is done by using the test data
was prepared.
In Loop Testing, different loops in the module like nested loops were tested using the data.
Attempts to execute the loops to their maximum range are done.
Integration Testing
In Integration testing whole system was checked when all the individual modules were
integrated together in order to test whether the system is performing as according to the
requirements specified. Interface errors if any were corrected.
Test data was prepared was fed into the system to check whether the system fails to detects an
error.

79
2019
Functional Testing
This is done for each module/sub module of the system. Functional testing serve as a means
of validating whether the functionality of the system confers the original user requirement i.e.
does the module do what it was supposed to do? Separate schedules were made for functional
testing. It involves preparation of test data, writing of test cases, testing for conformance to
test cases and preparation of bugs’ listing for non-conformities.
System Testing
System testing is done when the entire system has been fully integrated. The purpose of the
system testing is to test how the different modules interact with each other and whether the
entire system provides the functionality that was expected. System testing consists of the
following steps:
 Program Testing
 System Testing
 System Documentation
 User Acceptance Testing

80
2019
Test-Plan (TP)
The test-plan is basically a list of testcases that need to be run on the system. Some of the
testcases can be run independently for some componentsand some of the testcases require the
whole system to be ready for their execution. It is better to test each component as and when
it is ready before integrating the components.
It is important to note that the testcases cover all the aspects of the system (ie, all the
requirements stated in the RS document).
No. Testcase Description Expected The requirement Result

Title Outcome in RS that is being
tested
1 Successful The login to the Login should RS1 Passed
User system should be be successful
Verification tried with the login and the user
assigned by the should enter in
admin and the to the system
correct password
2 Unsuccessful Login to the Login should RS1 Passed
User system with a fail with an
Verification wrong password error ‘Invalid
due to wrong Password’
password
3 Unsuccessful Login to the Login should RS1 Passed
User system with a fail with an
Verification invalid login id error ‘Invalid
due to invalid user id’
login id
4 The system A Page for creating Page for RS3 Passed
should new users and adding/removi
provide Page deleting old users ng users is
for creating of the system shown
new
user/deleting
old user
5 The system provide searching Search RS4 Passed
should of details of pages
provide college for the opened
Search for the visitors
visitors

81
2019

82
2019
Chapter10
Conclusion
10.1 INTRODUCTION
The reason to have the college website is to encourage the students to take admissions in this
college and to encourage the towardsstudying dynamically through notes online which our
upload in this website. This website provide a facility to faculties to upload the notes and
notifications. And provide faciltty to students to download the notes, notification and forms.
Learnings
 The project has been an excellent learning opportunity for me and has helped me in
understanding and developing a project using the SDLC model.
 The project helped me understanding the layered (User Interface, Business Logic and
the Data access layer) approach followed in the company which makes the
management of modules quite easy.
 Technical Knowledge is something one can always get sitting at home and devouring
books. But being a part of a team which is working on a deliverable live Project means
a lot more other things apart from the technical knowledge gained.
 It was a total new experience to see how a software industry function what are the
Processes involved right from the time of Project inception. What are the standards
adhered in terms of compliance, quality standards, coding standards, testing etc.
 I learned it’s the team work and working in tandem with the team, complimenting the
team efforts that hold more priority than individual skills.
 I learned how important deadlines are, and that clients are like gods, we just have to
provide them what they want .The ultimate goal is to meet client’s requirements.
 I learned to take responsibilities and to handle the work pressure.
 I learned the importance of team camaraderie and bonhomie among the team members.

83
2019

84
2019
Future scope
It is directly dependent on the lay stone of the project that is we will have to design a system
which when the time passes having a better system initially should not become a joke later.
It is highly likely that the scope will change as the web application project moves forward; the
web-E process model should be incremental. This allows the development team to “freeze” the
scope for one increment so that an operational web application release can be created. The next
increment may scope changes suggested by a review of the preceding increment, but once the
second increment commences, scope is again frozen temporarily. This approach enables the
Web App team to work without having to accommodate a continual stream of changes but still
recognizes the continuous evolution characteristics of most web application. Besides that, the
following basic quality in the software always safeguards the future scope of the software.
Reusability: Reusability is possible as and when we require in this application. We can update
it next version. Reusable software reduces design, coding and testing cost by amortizing effort
over several designs. Reducing the amount of code also simplifies understanding, which
increases the likelihood that the code is correct. We follow up both types of reusability: Sharing
of newly written code within a project and reuse of previously written code on new projects.
Extensibility: This software is extended in ways that its original developers may not expect.
The following principles enhance extensibility like Hide data structure, Avoid traversing
multiple links or methods, Avoid case statements on object type and distinguish public and
private operations.
Robustness: Its method is robust if it does not fail even if it receives improper parameters.
There is some facilities like Protect against errors, Optimize after the program runs, validate
arguments and Avoid predefined limits.
Understandability: A method is understandable if someone other than the creator of the

method can understand the code (as well as the creator after a time lapse). We use the method
with small and coherent helps to accomplish this.
In the future scope Optimized search engine, Online attendance etc modules are considered

85
2019

86
2019
BIBLIOGRAPHY
 Software Engineering by K.K.Aggarwal & Yougesh Singh
 Programming In ASP.NET ,NIIT
 Querying and Managing Data using SQL Server 2005, NIIT
 Beginning ASP.NET 2.0 with C#, NIIT
 Essentials of .NET Programming
 VB.NET Black Book
 http://keshav.du.ac.in/index.htm
 www.sgtbimit.com
 http://www.free-css.com/free-css-menus/page5.php#bookmarks
 www.google.com
 http://ipu.ac.in/

87

Phonebook Management System: Enrolment No: 35490102017

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Phonebook Management System: Enrolment No: 35490102017

Hochgeladen von

Copyright:

Verfügbare Formate

Phonebook Management system

Enrolment No: 35490102017

Shelly Bhogal (BCA – 5th Semester)

Enrolment No: 35490102017

Enrolment No: 35490102017

My thanks and appreciations also go to my team members Ankita Aggarwal, Himani,

Finally, I gratefully acknowledge the support, encouragement & patience of my

Enrolment No: 35490102017

Enrolment No: 35490102017

Signature of Director: Dr. Prof. PL Sethi

Signature of HOD(IT) : Ms. Amanpreet Kaur

Signature of Guide: Ms. Amanpreet Kaur

Enrolment No: 35490102017

Enrolment No: 35490102017

Enrolment No: 35490102017

Enrolment No: 35490102017

1.1 ABOUT THE TOPIC

1.2 ABOUT THE PROJECT

The working of the project is as follows:

Enrolment No: 35490102017

Enrolment No: 35490102017

Enrolment No: 35490102017

2.1 OBJECTIVE OF THE PROJECT

2.2 SCOPE OF THE PROJECT

2.3 SYSTEM ANALYSIS

Enrolment No: 35490102017

2.4 EXISTING SYSTEM

2.5 PROPOSED SYSTEM

2.6 SDLC Approach

Our Project is based on Waterfall Model:

Enrolment No: 35490102017

Requirement Analysis and Software Definition:

Enrolment No: 35490102017

System Deployment and Maintenance:

The different phases of a typical SDLC are as:

Enrolment No: 35490102017

a. High Level design Documents

b. Low Level Design Documents

Enrolment No: 35490102017

Enrolment No: 35490102017

Requirements analysis in systems engineering and software engineering, encompasses those

Requirements analysis is critical to the success of a systems or software project. The

Enrolment No: 35490102017

Software Requirements Specification

1. Clarity of the specification document

No. Requirement Essential Description of the Remarks

Enrolment No: 35490102017

3.2 MINIMUM SOFTWARE REQUIREMENTS

OPERATING SYSTEM WINDOWS ,

3.3 MINIMUM HARDWARE REQUIREMENTS

Enrolment No: 35490102017

3.4 REQUIREMENT CAPTURE PROCESS

 Conduct a brainstorming session

Conduct a brainstorming session:

 Start out by clearly stating the objective of the brainstorming session.

Enrolment No: 35490102017

Talk to support teams:

In this project we have six team members :

 Shelly Bhogal (TEAM LEADER)

Enrolment No: 35490102017

Enrolment No: 35490102017

TOOLS AND TECHNOLOGIES USED

Front End ASP.NET