Sie sind auf Seite 1von 81

TITLE

S.NO CONTENT PAGE NO.


INTRODUCTION
1 1.1 SYNOPSIS
1.2 COMPANY PROFILE
SYSTEM ANALYSIS
2 2.1 EXISTING SYSTEM
2.2 PROPOSED SYSTEM
SYSTEM REQUIREMENT
3.1 HARDWARE REQUIREMENT
3
3.2 SOFTWARE REQUIREMENT
3.3 SOFTWARE SPECIFICATION
SYSTEM DESIGN
4.1 MODULES DESCRIPTION
4
4.2 DATA FLOW DIAGRAM
4.3 DATA DICTIONARY
5 SOURCE CODE
SYSTEM TESTING
6.1 UNIT TESTING
6
6.2 INTEGRATED TESTING
6.3 BLACK BOX TESTING/WHITE BOX TESTING
7 SCREEN SHOT
PROJECT IMPLEMENTATION AND
8
MAINTENANCE
9 FUTURE ENHANCEMENT
10 CONCLUSION
11 BIBLIOGRAPHY
1. INTRODUCTION
1.1 SYNOPSIS
Overall description consists of background of the entire specific requirement. It also
gives explanation about actor and function which is used. It gives explanation about architecture
diagram and it also gives what we are assumed and dependencies. It also support specific
requirement and also it support functional requirement, supplementary requirement other than
actor which is used. It also gives index and appendices. It also gives explanation about any doubt
and queries.

Once a student graduates from the institute, his/her professional life or career begins,
with higher education playing an important role in establishing himself/herself in the profession.
In respect of College, it has been our experience that from the very beginning, the alumni have
maintained personal contacts with one another, rather than use the channel of Alumni
Association.

The advancements in information technology have certainly helped in creating new


resources such as alumni web pages, list servers etc., so as to permit greater interactions between
the alumni.
1.2 COMPANY PROFILE

The world today Software Solution Integrated Limited reflects the cataclysmic environment in
which we endeavor new challenges that leaders across the stream are facing include standards of
corporate social responsibility, sustainable development, resource and energy efficiency and
increasing level of automation. Technology has been advancing at an incredible pace and to keep
pace with this change it becomes imperative to have a forum to experiment perspectives in a
multicultural atmosphere.

The leader of tomorrow has to work within a context that extends far beyond the classic
conventional concepts to consider and foretell the jigsaw of relationships across the society and
technologies. SSI wants to be a focal point for radiating a quest of innovation and excellence in
multicultural atmosphere. Our inception strives to cater to the learning needs of individuals. We
recognize the need for vocational education in India.

To accelerate the pace of development emerging economies like India require growth in
knowledge based resources rather than material resources. This can be further enhanced by the
potential of information technology. We propose to ponder over training and application skills.
Thus our mission is to establish in the academic map of high end training. We are looking
forward to having academic collaborations.
2. SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
The Existing system is a computerized system but which is maintained at individual
databases i.e. in excels sheets, it’s a time delay process. And maintaining all the records in Excel
sheets is difficult. If they want any record they have to search all the records. It doesn’t provide
multiple user accessibility and also doesn’t have different user privileges. So the system is not
accessible for all the employees of the organization.

 Limitations in Existing System  

 The current system is not completely complete computerized and manual system in
entering students and staff data and handling it.
 There is no centralized database maintenance
 There is no easy access to the particular students record
 The student cannot easily navigate through the database
2.2 PROPOSED SYSTEM
The Proposed system is a computerized system but which is maintained at Centralized
databases i.e. in automated forms it’s a very fast process. And maintaining all the records in
online systems database which makes it very easy to access and retrieve data from the database.
If they want any record they can easily search all the records. It provides multiple user
accessibility and also has different user privileges. So the system is accessible for all the
employees of the organization. 

Advantages over Existing System  

 It is completely automated system in handling the college database


 This system provides centralized database maintenance
 This system provides easy access to the particular students account or his complete
details
 This system provides student to easily navigate through the application for more
information in a most secure manner.
3. SYSTEM REQUIREMENT
3.1 HARDWARE REQUIREMENT
The Below Hardware Specifications were used in both Server and Client machines when
developing.
Processor : Intel(R) Core(TM) i3
Processor Speed : 3.06 GHz
RAM : 2 GB
Hard Disk Drive : 250 GB
CD-ROM Drive : Sony
Monitor : “17” inches
Keyboard : TVS Gold
Mouse : Logitech
3.2 SOFTWARE REQUIREMENT
SERVER

Operating System : Windows 7

Technology Used : Microsoft ASP.NET

Database : SQL Server

Database Connectivity : ActiveX Data Object (ADO)

Web Server : Internet Information Server

Browser : Internet Explorer 6.0

CLIENT

Operating System : Windows 7

Browser : Internet Explorer 6.0


3.3 SOFTWARE SPECIFICATION

FRONT END

ASP.NET
ASP.NET, the next version of ASP, is a programming Framework that is used to create
enterprise – class web applications. The enterprise class web applications are accessible on a
global basis loading to efficient information management. However, the advantages that
ASP.NET offers make it more than just next version of ASP.NET.
ASP.NET is integrated with visual studio.Net, which provides a GUI designer, a rich
toolbox and a fully integrated debugger. This allows the development of applications in a what
you see is what you get (WYSIWYG) MANNER.
The .NET Framework is a common environment for building, deploying, and running
Web Services and Web Applications. The .NET Framework contains common class libraries -
like ADO.NET, ASP.NET and Windows Forms - to provide advanced standard services that can
be integrated into a variety of computer systems.
The .NET Framework is language neutral. Currently it supports C++, C#, Visual Basic,
JScript (The Microsoft version of JavaScript) .The new Visual Studio.NET is a common
development environment for the new .NET Framework. It provides a feature-rich application
execution environment, simplified development and easy integration between a number of
different development languages.
Unique Features Of .Net Environment
1. Internet Inside

2. Common Language support

3. Common Class Libraries

4. Common Language Runtime

5. Garbage Collection.

6. Cross Language Reference

7. Web Services

INTERNET INFORMATION SERVICE 6.0


IIS 6.0 has strong support for more programming to take place on the server, to allow the
new Web Applications to run in any browser on any platform.

ASP.NET

 ASP.NET is a server side scripting technology that enables scripts (embedded in web pages)
to be executed by an Internet server.

 ASP.NET is a Microsoft Technology

 ASP.NET stands for Active Server Pages

 ASP.NET is a program that runs inside IIS

 IIS stands for Internet Information Services

 IIS comes as a free component with Windows 2008

 IIS is also a part of the Windows NT 4.0 Option Pack

 The Option Pack can be downloaded from Microsoft PWS is a smaller - but fully functional -
version of IIS PWS can be found on your Windows 95/98 CD.

 ASP.NET 3.0 is the latest version of ASP.NET, but there will never be an ASP.NET 4.0
version.

 ASP.NET is the next generation ASP.NET, but it's not an upgraded version of ASP.NET.
ASP.NET is an entirely new paradigm for server-side ASP.NET script

 ASP.NET is a part of the new .NET (dotnet) Framework. Microsoft spent three years
rewriting ASP.NET from the ground up, and ASP.NET is not fully backward compatible
with ASP.NET 3.0.

 ASP.NET has better language support, a large set of new controls and XML based
components, and better user authentication.

 ASP.NET provides increased performance by running compiled code.

 ASP.NET code is not fully backward compatible with ASP.NET.

 ASP.NET is a server side programming language.


 ASP.NET is an object oriented programming language.

 Active Server Pages - ASP.NET

 ASP.NET is the latest version of ASP.NET. It includes Web Services to link applications,
services and devices using HTTP, HTML, XML and SOAP.

NEW IN ASP.NET
1. New Language Support
2. Programmable Controls
3. Event Driven Programming
4. XML Based Components
5. User Authentication
6. User Accounts and Roles
7. High Scalability
8. Compiled Code
9. Easy Configuration
10. Easy Deployment
11. Includes ADO .NET

WEB SERVICES
 Web services are small units of code
 Web services are designed to handle a limited set of tasks
 Web services use XML based communicating protocols
 Web services are independent of operating systems
 Web services are independent of programming languages .
 .NET Web Services
 Web services are small units of code built to handle a limited task.
 Small Units of Code
 Web services are small units of code designed to handle a limited set of tasks.

XML BASEDWEB PROTOCOLS


Web services use the standard web protocols HTTP, XML, SOAP, WSDL, and UDDI.
HTTP
HTTP (Hypertext Transfer Protocol) is the World Wide Web standard for communication
over the Internet.

XML
XML (extensible Markup Language) is a well-known standard for storing, carrying, and
Exchanging data.

SOAP
Simple Object Access Protocol is a lightweight platform and language neutral
Communication protocol that allows programs to communicate via standard Internet
HTTP

WSDL
WSDL (Web Services Description Language) is an XML-based language used to define
web services and to describe how to access them.

UDDI
Universal Description, Discovery and Integration is a directory service where businesses
can register and search for web services.
UDDI is a public registry, where one can publish and inquire about web services.

INDEPENDENT OF OPERATING SYSTEM


Since web services use XML based protocols to communicate with other systems, web
services are independent of both operating systems and programming languages.
An application calling a web service will always send its requests using XML, and get
its answer returned as XML. The calling application will never be concerned about the
operating system or the programming language running on the other computer.

BENEFITS OF WEB SERVICES


 Easier to communicate between applications.
 Easier to distribute information to more consumers.
 Rapid development.
 Web services make it easier to communicate between different applications.
 They also make it possible for developers to reuse existing web services.
 Instead of writing new ones.
Web services can create new possibilities for many businesses because it provides an
easy way to distribute information to a large number of consumers. One example could be flight
schedules and ticket reservation systems.

BACK END
SQL SERVER

The database component of Microsoft® SQL Server™ 2008 is a Structured Query


Language (SQL)–based, scalable, relational database with integrated Extensible Markup
Language (XML) support for Internet applications. Each of the following terms describes a
fundamental part of the architecture of the SQL Server 2008 database component:
DATABASE

A database is similar to a data file in that it is a storage place for data. Like a data file, a
database does not present information directly to a user; the user runs an application that
accesses data from the database and presents it to the user in an understandable format.

Database systems are more powerful than data files in that data is more highly organized.
In a well-designed database, there are no duplicate pieces of data that the user or application
must update at the same time. Related pieces of data are grouped together in a single structure or
record, and relationships can be defined between these structures and records.

When working with data files, an application must be coded to work with the specific
structure of each data file. In contrast, a database contains a catalog that applications use to
determine how data is organized. Generic database applications can use the catalog to present
users with data from different databases dynamically, without being tied to a specific data
format.
A database typically has two main parts: first, the files holding the physical database and second,
the database management system (DBMS) software that applications use to access data. The
DBMS is responsible for enforcing the database structure, including:

 Maintaining relationships between data in the database.


 Ensuring that data is stored correctly, and that the rules defining data relationships
are not violated.

 Recovering all data to a point of known consistency in case of system failures.

RELATIONAL DATABASE

Although there are different ways to organize data in a database, relational databases are
one of the most effective. Relational database systems are an application of mathematical set
theory to the problem of effectively organizing data. In a relational database, data is collected
into tables (called relations in relational theory).

A table represents some class of objects that are important to an organization. For example, a
company may have a database with a table for employees, another table for customers, and
another for stores. Each table is built of columns and rows (called attributes and tuples in
relational theory). Each column represents some attribute of the object represented by the table.
For example, an Employee table would typically have columns for attributes such as first name,
last name, employee ID, department, pay grade, and job title. Each row represents an instance of
the object represented by the table. For example, one row in the Employee table represents the
employee who has employee ID 12345.

When organizing data into tables, you can usually find many different ways to define tables.
Relational database theory defines a process called normalization, which ensures that the set of
tables you define will organize your data effectively.

SCALABLE

SQL Server 2008 supports having a wide range of users access it at the same time. An
instance of SQL Server 2008 includes the files that make up a set of databases and a copy of the
DBMS software. Applications running on separate computers use a SQL Server 2008
communications component to transmit commands over a network to the SQL Server 2008
instance. When an application connects to an instance of SQL Server 2008, it can reference any
of the databases in that instance that the user is authorized to access. The communication
component also allows communication between an instance of SQL Server 2008 and an
application running on the same computer. You can run multiple instances of SQL Server 2008
on a single computer.

SQL Server 2008 is designed to support the traffic of the largest Web sites or enterprise
data processing systems. Instances of SQL Server 2008 running on large, multiprocessor servers
are capable of supporting connections to thousands of users at the same time. Although SQL
Server 2008 is designed to work as the data storage engine for thousands of concurrent users who
connect over a network, it is also capable of working as a stand-alone database directly on the
same computer as an application. The scalability and ease-of-use features of SQL Server 2008
allow it to work efficiently on a single computer without consuming too many resources or
requiring administrative work by the stand-alone user. The same features allow SQL Server 2008
to dynamically acquire the resources required to support thousands of users, while minimizing
database administration and tuning. The SQL Server 2008 relational database engine
dynamically tunes itself to acquire or free the appropriate computer resources required to support
a varying load of users accessing an instance of SQL Server 2008 at any specific time. The SQL
Server 2008 relational database engine has features to prevent the logical problems that occur if a
user tries to read or modify data currently used by others.

STRUCTURED QUERY LANGUAGE

To work with data in a database, you have to use a set of commands and statements
(language) defined by the DBMS software. Several different languages can be used with
relational databases; the most common is SQL. The American National Standards Institute
(ANSI) and the International Standards Organization (ISO) define software standards, including
standards for the SQL language. SQL Server 2008 supports the Entry Level of SQL-92, the SQL
standard published by ANSI and ISO in 1992. The dialect of SQL supported by Microsoft SQL
Server is called Transact-SQL (T-SQL). T-SQL is the primary language used by Microsoft SQL
Server applications.
EXTENSIBLE MARKUP LANGUAGE

XML is the emerging Internet standard for data. XML is a set of tags that can be used to
define the structure of a hypertext document. XML documents can be easily processed by the
Hypertext Markup Language, which is the most important language for displaying Web pages.

Although most SQL statements return their results in a relational, or tabular, result set,
the SQL Server 2008 database component supports a FOR XML clause that returns results as an
XML document. SQL Server 2008 also supports XPath queries from Internet and intranet
applications. XML documents can be added to SQL Server databases, and the OPENXML clause
can be used to expose data from an XML document as a relational result set.
4. SYSTEM DESIGN
4.1 MODULE DESCRIPTION
1. Admin Login
2. New Alumni
3. Student Login
4. Contact Us
5. View Alumni Details
6. View Student Status
7. Pass Out Students
8. Event Details

Admin Login

In this module, the admin can view the details of the alumni and student details.

New Alumni

In this module, the alumni has to register their details such as alumni id, name, dob,
gender, email, contact number, password, confirm password, passout year, etc.,

Student Login

In this module, the student has to register their details such as student id, name, dob,
gender, email id, contact number, password, confirm password, department, etc.,

Contact Us

Through this module, the alumni / student has to contact the person and given phone
number details.

View Alumni Details

In this module, the alumni can view the details of the student id, name, dob, gender,
email id, contact number, department, etc., The admin has to activate the alumni details. Without
the activation the alumni cant login to his account.
View Student Status

In this module, the student details can be viewed by the admin. It contains the student id,
student name, dob, gender, email id, contact number, department name, etc.,. The admin has to
activate / deactivate the student. After activation only the student can access their account.

Pass Out Students

In this module, the students who are passed out details are viewed in this form depending
upon the year.

Event Details

This module contains the event details such as event id, headline, news, uploaded date,
etc.,
4.2 DATA FLOW DIAGRAM

Homepage

Admin Alumni

Admin Login

Authenti
cation

Search Pass
Search
Outs Events Logout

View All Add New Quit To The


A Pass Outs Events System

Alumnireg Events
A

Company Search By Alumnireg


Company

Experience Search By Alumnireg


Experience

Alumni Name Search By Alumnireg


Alumni
Name

Gender Search By Alumnireg


Gender

Position Search By Alumnireg


Position
Alumni Login

Authe
nticat
ion

Modify Info Update


Search Edit Status Batchmates Events
Status

Update Edit View View


Change Their Their Batchma Events
Personal Job Info Job tes Online
Info Status Details

Status Status Alumnireg Events


Alumnireg
4.3 DATA DICTIONARY
Alumni Register

Filed Name Data Type


Alumniid Varchar(50)
Name Varchar(50)
Dob Varchar(50)
Gender Varchar(50)
Email Varchar(50)
Cno Varchar(50)
Pass Varchar(50)
Passout Varchar(50)
Status Varchar(50)

Alumni Status

Filed Name Data Type


Statusid Varchar(50)
Alumniid Varchar(50)
Compname Varchar(50)
Compaddr Varchar(100)
City Varchar(50)
State Varchar(50)
Country Varchar(50)
Position Varchar(50)
Exp Varchar(50)
Syear Varchar(50)
Eyear Varchar(50)

Events Update

Filed Name Data Type


Eventid Varchar(50)
Ehead Varchar(50)
Enews Varchar(50)
Edate Date
Fanswer

Filed Name Data Type


Refno Varchar(50)
Name Varchar(50)
Tno Numeric(5, 0)
Answer Varchar(400)
Adate Datetime

Forum

Filed Name Data Type


Tno Numeric(5, 0)
Heading Varchar(50)
Description Varchar(250)
Pdate Datetime
Uname Varchar(50)

Student Registration

Filed Name Data Type


Sid Varchar(50)
Sname Varchar(50)
Dob Datetime
Gender Varchar(20)
Email Varchar(50)
Cno Numeric(10, 0)
Pass Varchar(50)
Dname Varchar(50)
Status Varchar(50)
5. SOURCE CODE
AdminLogin.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class AdminLogin : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{
Label1.Text = "";
}
protected void LinkButton1_Click(object sender, EventArgs e)
{
if (TextBox1.Text == "Admin")
{ if (TextBox2.Text == "Admin")
//Response.Redirect("AdminMain.aspx");
Response.Redirect("AdminViewStudentDetails.aspx");
else
Label1.Text = "Incorrect Password";
}
else
Label1.Text = "Invalid UserName";
}
protected void LinkButton2_Click(object sender, EventArgs e)
{ TextBox1.Text = TextBox2.Text = "";
}
}

AdminMain.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class AdminMain : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{
}
}

AdminViewAlumniDetails.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Data;
using System.Configuration;
public partial class AdminViewAlumniDetails : System.Web.UI.Page
{
SqlConnection con;
SqlDataAdapter adp;
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
try
{
Label1.Text = "";
con = (SqlConnection)Application["Alumni"];
if (!IsPostBack)
bindgrid();
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
void bindgrid()
{
try
{
adp = new SqlDataAdapter("Select * from alumnireg ", con);
ds = new DataSet();
adp.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
protected void GridView1_PageIndexChanging(object sender, GridViewPageEventArgs e)
{
GridView1.PageIndex = e.NewPageIndex;
bindgrid();
}

protected void GridView1_RowCommand(object sender, GridViewCommandEventArgs e)


{
try
{
if (e.CommandName == "ss")
{
string alumniid = GridView1.DataKeys[int.Parse (e.CommandArgument.ToString
())].Value.ToString();
Session.Add("AlumniID", alumniid );
Response.Redirect("AdminViewAlumniStatus.aspx");
}
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
}

AdminViewAlumniStatus.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Data;
using System.Configuration;
public partial class AdminViewAlumniStatus : System.Web.UI.Page
{
SqlConnection con;
SqlDataAdapter adp;
DataSet ds;
SqlCommand cmd;
protected void Page_Load(object sender, EventArgs e)
{
try
{
Label1.Text = "";
con = (SqlConnection)Application["Alumni"];
if (!IsPostBack)
if (Session["AlumniID"] != null)
bindview();
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
void bindview()
{
try
{
adp = new SqlDataAdapter("Select * from alumnireg where alumniid=@alumniid",
con);
adp.SelectCommand.Parameters.AddWithValue("alumniid",
Session["AlumniID"].ToString());
ds = new DataSet();
adp.Fill(ds);
DetailsView1.DataSource = ds;
DetailsView1.DataBind();
string status = ds.Tables[0].Rows[0]["status"].ToString ();
RadioButtonList1.Text = status;
if (status.Equals("Activated"))
RadioButtonList1.Enabled = false;
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
protected void RadioButtonList1_SelectedIndexChanged(object sender, EventArgs e)
{
try
{
if (Session["AlumniID"] != null)
{
cmd = new SqlCommand("update alumnireg set status=@status where
alumniid=@alumniid", con);
cmd.Parameters.AddWithValue("status", RadioButtonList1.SelectedItem.Text);
cmd.Parameters.AddWithValue("alumniid", Session["AlumniID"].ToString());
cmd.ExecuteNonQuery();
cmd.Dispose();
Label1.Text = "Your Status Is Updated.....";
bindview();
}
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
}

AlumniLogin.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
public partial class AlumniLogin : System.Web.UI.Page
{
SqlConnection con;
SqlCommand cmd;
SqlDataReader dr;
protected void Page_Load(object sender, EventArgs e)
{
try
{
Label1.Text = "";
con = (SqlConnection)Application["Alumni"];
}
catch (Exception ex)
{
Label1.Text = ex.ToString();
}
}
protected void LinkButton1_Click(object sender, EventArgs e)
{
try
{
cmd = new SqlCommand("select * from AlumniReg where email=@email and
pass=@pass", con);
cmd.Parameters.AddWithValue("email", TextBox1.Text);
cmd.Parameters.AddWithValue("pass", TextBox2.Text);
dr = cmd.ExecuteReader();
string status = "";
string alumniid = "";
string passout = "";
if (dr.Read())
{
alumniid = dr["alumniid"].ToString();
status = dr["status"].ToString().ToLower ();
passout = dr["passout"].ToString();
dr.Close();
cmd.Dispose();
}
else
{
dr.Close();
cmd.Dispose();
Label1.Text = "Invalid EMailID Or Password......";
return;
}
if (status.Equals("register"))
{
Label1.Text = "Your Status is Registed......";
}
else if (status .Equals ("notactivated"))
{
Label1 .Text ="Your Status is Not Activated.....";
}
else if (status.Equals("activated"))
{
Session.Add("AEMailID", TextBox1.Text);
Session.Add("alumniid", alumniid);
Session.Add("pass", passout);
Response.Redirect("AlumniMain.aspx");
}
}
catch (Exception ex)
{
if (dr != null)
dr.Close();

Label1.Text = ex.ToString();
}
}
protected void LinkButton2_Click(object sender, EventArgs e)
{
Response.Redirect("HomePage.aspx");
}
protected void LinkButton3_Click(object sender, EventArgs e)
{
Response.Redirect("NewAlumni.aspx");
}
}

Batchmates.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Data;
public partial class Batchmates : System.Web.UI.Page
{
SqlConnection con;
SqlCommand cmd;
SqlDataReader dr;
SqlDataAdapter adp;
DataTable dt;
protected void Page_Load(object sender, EventArgs e)
{
try
{
con = (SqlConnection)Application["Alumni"];

if (Request.QueryString["arg"] != null)
{
bind();
}
if(!IsPostBack)
autobind();
}
catch (Exception ex)
{
Label1.Text = ex.ToString();
}
}
public void autobind()
{
try{
cmd = new SqlCommand("select * from AlumniReg where passout
='"+Session["pass"].ToString()+"' and alumniid!= '"+Session["alumniid"].ToString()+"'",con);
dr = cmd.ExecuteReader();
GridView1.DataSource = dr;
GridView1.DataBind();
dr.Close();
cmd.Dispose();
}catch(Exception ex)
{
if(dr!=null)
dr.Close();
Label1.Text = ex.ToString();
}
}
public void bind()
{
try
{
cmd = new SqlCommand("select * from AlumniStatus where alumniid='" +
Request.QueryString["arg"] + "'", con);
dr = cmd.ExecuteReader();
DetailsView1.DataSource = dr;
DetailsView1.DataBind();
dr.Close();
cmd.Dispose();
}
catch (Exception ex)
{
if (dr != null)
dr.Close();
Label1.Text = ex.ToString();
}
}
protected void GridView1_RowCommand(object sender, GridViewCommandEventArgs e)
{
try
{
if (e.CommandName == "aa")
{
string alumniid =
GridView1.DataKeys[int.Parse(e.CommandArgument.ToString())].Value.ToString();
adp = new SqlDataAdapter("select * from alumnistatus where alumniid=@alumniid",
con);
adp.SelectCommand.Parameters.AddWithValue("alumniid", alumniid);
dt = new DataTable();
adp.Fill(dt);
DetailsView1.DataSource = dt;
DetailsView1.DataBind();
}
}
catch (Exception ex)
{
if (dr != null)
dr.Close();
Label1.Text = ex.ToString();
}
}
}

ForumAnswer.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
public partial class ForumAnswer : System.Web.UI.Page
{
public string i;
SqlCommand cmd;
string s1;
string s;
protected void Page_Load(object sender, EventArgs e)
{
try
{
Label1.Text = "";
TextBox5.Focus();
i = Request.QueryString["no"];
Page.DataBind();
cmd = new SqlCommand("select * from forum where tno=@tno",
(SqlConnection)Application["Alumni"]);
cmd.Parameters.AddWithValue("@tno", i);

SqlDataReader rs = cmd.ExecuteReader();
if (rs.Read())
{
TextBox1.Text = rs[1].ToString();
TextBox2.Text = rs[2].ToString();
TextBox3.Text = DateTime.Parse(rs[3].ToString()).ToString("dd-MMM-yyyy
hh:mm:ss");
TextBox4.Text = rs[4].ToString();
}
rs.Close();
cmd.Dispose();
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
protected void Button1_Click(object sender, EventArgs e)
{
try
{
cmd = new SqlCommand("select isnull(max(refno),100)+1 from fanswer",
(SqlConnection)Application["Alumni"]);
int refno = int.Parse(cmd.ExecuteScalar().ToString());
cmd.Dispose();
cmd = new SqlCommand("insert into fanswer
values(@refno,@name,@tno,@answer,@adate)", (SqlConnection)Application["Alumni"]);
cmd.Parameters.AddWithValue("@refno", refno);
cmd.Parameters.AddWithValue("@name", Session["AEMailID"].ToString());
// cmd.Parameters.AddWithValue("@refno", s);
// cmd.Parameters.AddWithValue("@name", s1);
cmd.Parameters.AddWithValue("@tno", i);
cmd.Parameters.AddWithValue("@answer", TextBox5.Text);
cmd.Parameters.AddWithValue("@adate", DateTime.Now);
cmd.ExecuteNonQuery();
Label1.Text = "Your Answer Has Been Accepted";
TextBox5.Text = "";
TextBox5.Focus();
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
}

Events(alumni).aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;

public partial class Events_alumni_ : System.Web.UI.Page


{
SqlConnection con;
SqlCommand cmd;
SqlDataReader dr;
protected void Page_Load(object sender, EventArgs e)
{
try
{
Label1.Text = "";
con = (SqlConnection)Application["Alumni"];

if (!IsPostBack)
bind();
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
public void bind()
{
cmd = new SqlCommand("select * from EventUpdate", con);
dr = cmd.ExecuteReader();

GridView1.DataSource = dr;
GridView1.DataBind();

dr.Close();
cmd.Dispose();
}
}
Forums.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data .SqlClient ;
using System.Data ;
using System.Configuration ;
public partial class Forums : System.Web.UI.Page
{
public string i = "";
SqlConnection con;

SqlCommand cmd;
SqlDataReader rs;
protected void Page_Load(object sender, EventArgs e)
{
try
{
Label1.Text = "";
con = (SqlConnection)Application["alumni"];
if (!IsPostBack)
autonumber();
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
void autonumber()
{
cmd = new SqlCommand("select isnull(max(tno),0)+1 from forum", con);
rs = cmd.ExecuteReader();
if (rs.Read())
TextBox3 .Text = rs[0].ToString();
rs.Close();
cmd.Dispose();
Page.DataBind();
}
protected void Button1_Click(object sender, EventArgs e)
{
//Response.Write(DateTime.Now.ToString("dd-MMM-yyyy hh:mm:ss"));
try
{
cmd = new SqlCommand("insert into forum(tno,heading,description,pdate,uname)
values(@tno,@heading,@description,@pdate,@uname)", con);
cmd.Parameters.AddWithValue("@tno",TextBox3 .Text );
cmd.Parameters.AddWithValue("@heading", TextBox1.Text);
cmd.Parameters.AddWithValue("@description", TextBox2.Text);
cmd.Parameters.AddWithValue("@pdate", DateTime.Now);
cmd.Parameters.AddWithValue("@uname", Session["SEMail"].ToString());
cmd.ExecuteNonQuery();
Label1.Text = "'Your Queries has been accepted";
TextBox1.Text = "";
TextBox2.Text = "";
TextBox1.Focus();
autonumber();
}
catch (Exception ex)
{
Label1.Text = ex.Message;
}
}
}

NewAlumni.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Collections;
public partial class NewAlumni : System.Web.UI.Page
{
SqlConnection con;
SqlCommand cmd;
SqlDataReader dr;
protected void Page_Load(object sender, EventArgs e)
{
try
{
Label2 .Text ="";
con = (SqlConnection)Application["Alumni"];

if (!IsPostBack)
{
string[] mon = { "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct",
"Nov", "Dec" };
for (int i = 1; i <= 31; i++)
DropDownList1.Items.Add("" + i);
for (int i = 1960; i < 2005; i++)
{
DropDownList3.Items.Add("" + i);
}
for (int i = 1990; i < DateTime.Now.Year; i++)
{
DropDownList4.Items.Add("" + i);
}
for (int i = 0; i < mon.Length; i++)
DropDownList2.Items.Add(mon[i]);
DropDownList1.Items.Insert(0, "--Date--");
DropDownList2.Items.Insert(0, "--Month--");
DropDownList3.Items.Insert(0, "--Year--");
DropDownList4.Items.Insert(0, "--Year--");
autonum();
}
}
catch (Exception ex)
{
Label2.Text = ex.Message;
}
}
public void autonum()
{
try
{
cmd = new SqlCommand("select count(*) from AlumniReg", con);
int no = int.Parse(cmd.ExecuteScalar().ToString());
if (no == 0)
{
Label1.Text = "AL1";
}
else
{
string[] s = new string[no];
cmd = new SqlCommand("select alumniid from AlumniReg", con);
dr = cmd.ExecuteReader();
ArrayList a = new ArrayList();
int i = 0;
while (dr.Read())
{
s[i] = dr["alumniid"].ToString();
i++;
}

dr.Close();
cmd.Dispose();
for (i = 0; i < s.Length; i++)
a.Add(s[i].Substring(2));
a.Sort();
int no1 = int.Parse((a[a.Count - 1].ToString())) + 1;

Label1.Text = "AL" + no1;


}
}
catch (Exception ex)
{
if (dr != null)
dr.Close();
Label2.Text = ex.ToString();
}
}
protected void LinkButton1_Click(object sender, EventArgs e)
{
string s = DropDownList1.SelectedItem.ToString()
+"-"+DropDownList2.SelectedItem.ToString()+"-"+DropDownList3.SelectedItem.ToString();
try
{
cmd = new SqlCommand("select email from alumnireg where email=@email", con);
cmd.Parameters.AddWithValue("email", TextBox2.Text);
dr = cmd.ExecuteReader();
bool b = dr.Read();
dr.Close();
cmd.Dispose();
if (b)
{
Label2.Text = "EMailID Already Found.....";
return;
}

cmd = new SqlCommand("insert into AlumniReg


values(@alumniid,@name,@dob,@gender,@email,@cno,@pass,@passout,@status)", con);
cmd.Parameters.AddWithValue("alumniid", Label1.Text);
cmd.Parameters.AddWithValue("name", TextBox1.Text);
cmd.Parameters.AddWithValue("dob", s);
cmd.Parameters.AddWithValue("gender", RadioButtonList1.SelectedItem.ToString());
cmd.Parameters.AddWithValue("email", TextBox2.Text);
cmd.Parameters.AddWithValue("cno", TextBox5.Text);
cmd.Parameters.AddWithValue("pass", TextBox3.Text);
cmd.Parameters.AddWithValue("passout", DropDownList4.SelectedItem.ToString());
cmd.Parameters.AddWithValue("status", "Register");
cmd.ExecuteNonQuery();
cmd.Dispose();
Label2.Text = "Record Inserted..";
}
catch (Exception ex)
{
Label2.Text = ex.ToString();
}
}
protected void LinkButton2_Click(object sender, EventArgs e)
{
Response.Redirect("HomePage.aspx");
}
//protected void TextBox2_TextChanged(object sender, EventArgs e)
//{
// try
// {
// cmd = new SqlCommand("select email from AlumniReg", con);
// dr = cmd.ExecuteReader();

// while (dr.Read())
// {
// if (dr["email"].ToString() == TextBox2.Text)
// {
// Label3.Text = "Mail Id Is Not Available";
// }
// else
// {
// Label3.Text = "Mail Id Is Available";
// }
// }
// dr.Close();
// cmd.Dispose();
// catch (Exception ex)
// {
// if (dr != null)
// dr.Close();
// Label2.Text = ex.ToString();
protected void LinkButton3_Click(object sender, EventArgs e)
{
Response.Redirect("AlumniLogin.aspx");
}
}
6. SYSTEM TESTING
The important phase of software development is concerned with translating the design
specification into the error-free source code. Testing is carried out to ensure that the system does
not fail, that it meets the specification and it satisfies the user. The system testing was carried out
in a systematic manner with a test data containing all possible combinations of data to check the
features of the system. A test data was prepared for each module, which took care of all the
modules of the program.

System Testing is an important stage where the system developed is tested with duplicate
or original data. It is a process of executing a program with the intent of finding an error. It is a
critical process that can consume fifty percent of the development time.

The following are the attributes of good test :


 A good test has a high probability of finding an error.
 A good test is not redundant.
 A good test should be "best of breed".
 A good test should be neither simple nor too complex.

6.1 UNIT TESTING


In the unit testing the analyst tests the program making up a system. The software units in
a system are the modules and routines that are assembled and integrated to perform a specific
function. In a large system, many modules on different levels are needed.
Unit testing can be performed from the bottom up starting with the smallest and lowest
level modules and proceeding one at a time. For each module in a bottom-up testing, a short
program executes the module and provides the needed data.
6.2 INTERGRATED TESTING
Integration testing is a systematic technique for constructing the program structure while
conducting test to uncover errors associate with interfacing. Objectives are used to take unit test
modules and built program structure that has been directed by design.
The integration testing is performed for this Airport Management System when all the
modules where to make it a complete system. After integration the project works successfully.

6.3 BLOCK BOX/WHITE BOX TESTING


White Box Testing or Error Code Testing :

The Code Testing Strategy checks for the correctness of the every statement in a
program. To follow this testing strategy , there should be cases that result in the executing of
every instructions in the program or module. That is every path in the program is tested. The test
cases should be guarantee that independent paths within the module are executed once. We
derive test cases that,
 Exercise all logical decision on their true or false sides.
 Execute all loops at their boundaries and within their operational bounds.
 Exercise internal data structures to ensure that validity.

Black Box Testing or Specification Testing

Black box testing methods focus on the functional requirements of the software. That is,
black box testing enabled us to derive sets of input conditions that will fully exercise all
functional requirements for a program. Black box testing is not an alternative to white box
techniques. Rather it is a complementary approach that is likely to uncover a different class of
errors than white box methods. Black box testing attempts to find errors in the following
categories
 Incorrect or missing functions.
 Interface errors.
 Errors in data structures or external data access.
7. SCREEN SHOT

Home Page
Admin Login
Add New Events
New Alumni Registration
New Student Registration
View Alumni
Alumni Status
View All Student Details
View Student Status
Alumni Login
Alumni Main Page
Modify Alumni Details
Update Alumni Status
Edit Details
View Batch Mate
View Events
Student Login
Student Main Page
Edit Details
Posting of Queries
Alumni view Queries
Answer
Student View Answer
Search Alumni
Search by Position
Admin View Pass out Student Details
8. PROJECT IMPLEMENTATION AND MAINTANENCE
SYSTEM IMPLEMENTATION
Implementation is the state in the system where the theoretical design is turned into a
working system. The most crucial stage in achieving a new successful system and in giving
confidence on the new system for the users that will work efficiently and effectively. The
system can be implemented only after thorough testing in done and if found to work according to
the specification.

If involves careful planning, investigation of the current system and its constraints on
implementation, design of methods to achieve the changeover, an evaluation of changeover
methods apart from planning. Two major tasks of preparing the implementation are education,
training of the users and testing the systems. System analysis and design efforts will be more for
complex systems beings implemented. Based on policies of individuals organization an
implementation coordinating committee has been appointed.

The implementation process begins with preparing a plan for the implementation system.
According to this plan, the other activities are to be carried out. In this plan, discussion has been
made regarding the equipment, resources and how to test the activities. Thus a clear plan is
preparing for the activities.

Equipment Acquisition
According to the above plan, the necessary equipment has to be acquired to implement
the new system. Prime Tech has all the hardware requirements for installing and maintaining the
package.

Program code preparation


One of the most important development activities is the code of programming. The
system DFD’s and other channels are converted to modular programs. They have to be
complied, tested and debugged.
User Manuals

Once planning has been completed the major effort of the computer department is to
ensure that the user department consists of education and trained staff, as the system becomes
more complex. The success of a system depends upon how they are operated and used. Thus the
quality of training, the personnel is connected to the success of the system.

For this purpose system and user manuals are prepared. In system manuals, details about
the forms and blocks triggers. Which were used to develop them, were specified. In user
manuals data flow diagrams, charts and screen formats are given. Also error messages
associated were explained in details. The users were shown the success and they were taught
how to operate the system. Live demonstration and visuals aids were used to teach them.
SYSTEM MAINTENANCE

The term “software maintenance” is used to describe the software engineering activities
that occur following delivery of a software product to the customer. The maintenance phase of
the software life cycle is the time period in which a software product performs useful work.

Maintenance activities involve making enhancements to software products, adapting


products to new environments, and correcting problems. Software product enhancement may
involve providing new functional capabilities, improving user displays and modes of interaction,
upgrading external documents and internal documentation, or upgrading the performance
characteristics of a system. Adaptation of software to a new environment may involve moving
the software to different machine etc.

Problem correction involves modification and revalidation of software to correct errors.


Some errors require immediate attention and some can be corrected on a scheduled, periodic
basis, and other are known but never corrected.

After the launch of the site, the maintenance phases begun. There was a problem in
viewing some of the pages of the site in one of the major browser Netscape browser. The
Netscape browser did not support some tags of HTML. Then, those tags were removed from the
HTML documents and validated again. It worked well.

As the site is developed in Active Server Pages, it can be viewed in any platform. It is not
a platform dependent site. Linux, Mac OS, Sun Solaris operating system supports ASP, so that
any one can view the site. The web server must be platform dependent and it should be Windows
NT. All the components of ASP are available within the IIS 4.0. which is shipping along with
Windows NT as NT option pack.

Additional features were added to the admin part of the site after implementation. As the
administrator needed some easier way of uploading for the prediction part of the site, that section
was developed at this stage of the project. The daily prediction uploading section needed the date
should be incremented automatically for each day of the following week. Those sections were
done at this stage of the site development.
Netscape Navigator does not support the VBScript. Some of the pages were validated at
the client side using the VBScript. Those pages were reconstructed with the JavaScript as almost
all browsers in the market support it. Basically, the VBS is the scripting language from Microsoft
and it is fully supported by Internet Explorer only. So during the development of any site,
JavaScript should be used to validate at the client side.

All of these tasks must be accomplished using a systematic, orderly approach to tracking
and analysis of change requests and careful redesign, re-implementation, revalidation and re-
documentation of the changes. Otherwise, the software product quickly degrades as a result of
the maintenance process.

It is not unusual for a well designed, properly implemented and adequately documented
initial version of a software product to become unmentionable due to inadequate maintenance
procedures. This can result in situation in which it becomes easier and less expensive to re
implement a module or subsystem than to modify the existing version.

Software maintenance activities must not destroy the maintainability of the software. A
small change in the source code often requires extensive changes to the test suite and the
supporting documents. Failure to recognize the true cost of a “small change” in the source code
is one of the most significant problems in software maintenance.
9. FUTURE ENHANCEMENT
The newly developed system, in its present form, is eminently suited to the existing
needs. But in order to meet the future needs, which can become progressively more complex the
efficiency of the system can be improved by making some simple modifications in the programs.

The project is still developing in many ways. The site is being added new section and
new services to the visitors. In future the site will be providing the service of modifying the
website to the users.

The user is given a blank website so as to design the website or web page of his own, by
activating links, changing images and changing the text using editor.

In future the project will be altered by which the user is given more options to design
more number of pages. This will be achieved by providing more links ,more customizing options
and we may offer the user possibility of creating domain of its won.
10. CONCLUSION
Working with computer gives us a pleasant experience and delivers the expected results
excellently.
The project “Alumni Database Management System” is to access all old student details
and student performance and achievement details are provided successfully. This project is of
great importance and it is widely used countrywide.
The project is done in the computerized form. It is a Quick process and therefore saves
time and money.
Thus the project has been designed and implemented successfully within the stipulated
time and cost. Proper care has been taken in giving all types of both invalid and valid inputs and
tested for the expected output and robustness of the software developed.
All the modules has been properly integrated, debugged and tested based on the Top
Down design strategy.
The project after implementation is found to be properly working and satisfying the user
requirements under the problem definition. Thus the proposed system has been identified as
successful project.
11. BIBLIOGRAPHY
BOOKS

1. “Microsoft ASP.NET” by Mirdula Pariha, Jeff Webb, Tata Mac Graw Hill.
2. Microsoft SQL SERVER2000 by Ray Rankings, Paul Bertucci, Paul Jensen
3. Gerry O’Brien,” Microsoft IIS 5.0 Administration”
4. Sql Server - The complete Reference-Gayle Coffman
5. Teach yourself Sql Server-Richard Way Mire
6. Asp.Net-Stephen Walther (Second Edition)
7. Asp.Net-Daniel Maharry
WEBSITES

ASP.NET

1. www.asp.net/(S(pdfrohu0ajmwt445fanvj2r3))/learn/data-access/
2. www.w3schools.com/aspnet/default.asp
3. www.411asp.net/home/sites
4. www.cristiandarie.ro/asp-net-tutorial/
5. www.asp.net-tutorials.com/basics/first-website/
SQL SERVER

1. www.functionx.com/sqlserver/
2. www.technet.microsoft.com/en-us/library/ms169620.aspx
3. www.msdn.microsoft.com/en-us/library/ms169620(SQL.90).aspx
4. www.softwaretrainingtutorials.com/ms-sql-server-2005.php

Das könnte Ihnen auch gefallen