Project Report Student Help Desk

A PROJECT REPORT ON

STUDENT HELP DESK

Submitted to ******************** University for the partial

fulfillment of the Requirement for the

Award of Degree for

***********Course Name*************

Done By

Mr. /Miss *********************************************

**************Institute of Management and Computer Science

1
 CERTIFICATE

This is to certify that Mr., /Miss ****************** bearing Roll

No. ********************** have developed software project
Titled **************** For ********************* Software
Solutions as Partial fulfillment for the award of the Degree of
**************

Head of the Department Principal

******College Name******

External

ACKNOWLEDGEMENT

2
At every outset I express my gratitude to almighty lord for showering his
grace and blessings upon me to complete this project.
Although our name appears on the cover of this book, many people had
contributed in some form or the other form to this project Development. I
could not have done this project without the assistance or support of each of
the following and I thank you all for the same.
I wish to place on my record my deep sense of gratitude to my project
guide, Mr. ******, ***** Software Solutions, for his constant
motivation and valuable help through the project work. Express my
gratitude to Mr. ******, Director of ******* Institute of Management
& Computer Sciences for his valuable suggestions and advices throughout
the ***** course. I also extend my thanks to other Faculties for their
Cooperation during my Course.
Finally I would like to thank my friends for their cooperation to complete this
project.

*******Your
Name*********

3
 ABSTRACT

ABSTRACT

Project Title : STUDENT HELP DESK

Project Description

4
This Project is basically aimed in providing latest technologies & trends to
the College sector service, so that college can store there student’s records
like details of student , attendance & semester marks which can be viewed
by the student & there parents also when they login into this site. Student’s
can maintain online forum’s to share their views and questions. This site also
has facility of placement cell where percentages of students can be find by
seeing those Percentages college authority can display students list in notice
board

User friendly:

This project provides very simple and modified features, which are very
easy to view and operate. This project is designed and organized in a very
simplified manner to hold the details of students and also to maintain
online forums.

Security:

Site security features include

Username/Password authentication

Per-user, feature-by-feature, and field-by-field access control

Granular administrative privileges

5
 TABLE OF CONTENTS

Table of Contents

1. INTRODUCTION
1.1 ORGANIZATION PROFILE
1.2 INTRODUCTION TO PROJECT
1.3 PROBLEMS IN EXISTING SYSTEM
1.4 SOLUTION TO THESE PROBLEMS
2. SYSTEM ANALYSIS

6
 2.1 INTRODUCTION
2.2 ANALYSIS MODEL
2.3 STUDY OF THE SYSTEM
2.4 PROPOSED SYSTEM
2.5 SYSTEM MODULES AND H/W-S/W REQUIREMENTS
2.6 INPUT AND OUTPUT DESIGN
3. FEASIBILITY REPORT
3.1 TECHNICAL FEASIBILITY
3.2 OPERATIONAL FEASIBILITY
3.3 ECONOMICAL FEASIBILTY
4. SOFTWARE REQUIREMENT SPECIFICATIONS
4.1 SCOPE OF THE PROJECT
4.2 FUNCTIONAL REQUIREMENTS
4.3 NON-FUNCTIONAL REQUIREMENTS
5. SELECTED SOFTWARE
5.1 INTRODUCTION TO .NET FRAME WORK
5.2 ASP.NET
5.3 C#.NET / VB.NET
5.4 SQL SERVER
6. SYSTEM DESIGN
6.1 INTRODUCTION
6.2 NORMALIZATION
6.3 E-R DIAGRAMS
6.4 DATA DICTIONARY
6.5 DATA FLOW DIAGRAMS
6.6 UML DIAGRAMS
7. OUTPUT SCREENS
8. SYSTEM TESTING
8.1 INTRODUCTION

7
 8.2 STRATEGIC APPROACH OF SOFTWARE TESTING
8.3 UNIT TESTING
8.4 SYSTEM TESTING
9. SYSTEM SECURITY
9.1 INTRODUCTION
9.2 SECURITY IN SOFTWARE
10. CONCLUSION
11. BIBLIOGRAPHY

8
 INTRODUCTION

1.1 Copy Organization Profile from the CD

1. INTRODUCTION
1. Background:
Client of this project is a college .College Authority wants to
maintain a website for helping students and also wants to maintain
information about student’s attendance, marks , registration details and also

9
wants to percentages of final year students for placements in different
companies
.1.2 Objectives:
The main objective of this project is to design a website for any
Specific College to keep track the information about the students and also
to maintain a online forum which helps student.

1.3 Purpose, Scope and Applicability:

1.3.1 Purpose:

This Project is basically aimed in providing latest technologies &

trends to the College sector service, so that college can store there student’s
records like details of student & attendance & semester marks which can be
viewed by the student & there parents also when they login into this site.
And school can search the student’s records when they require it and also
student’s can maintain online forum’s to share their views and questions
1.3.2 Scope:

Once the Administrator sign’s into the site. He can add course,
branches, semester and subject details. He can also maintain Student Marks
details, Attendance. Admin can get final year students percentages in
placement cell. Admin maintains groups.

1.3.3 Applicability:

This Project is mainly use full in Colleges who wants to

maintain there students details and mainly for knowing the percentages of
students

1.4. Achievements:
This project gives me an opportunity of
improving my Designing, coding, analyzing and testing skills

10
SYSTEM ANALYSIS

11
2.1 INTRODUCTION
After analyzing the requirements of the task to be performed, the next
step is to analyze the problem and understand its context. The first activity
in the phase is studying the existing system and other is to understand the
requirements and domain of the new system. Both the activities are equally
important, but the first activity serves as a basis of giving the functional
specifications and then successful design of the proposed system.
Understanding the properties and requirements of a new system is more
difficult and requires creative thinking and understanding of existing running
system is also difficult, improper understanding of present system can lead
diversion from solution.
2.2 ANALYSIS MODEL
SDLC METHDOLOGIES
This document play a vital role in the development of life cycle (SDLC)
as it describes the complete requirement of the system. It means for use by
developers and will be the basic during testing phase. Any changes made to
the requirements in the future will have to go through formal change
approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral
Model of Software Development and Enhancement. This model was not the
first model to discuss iterative development, but it was the first model to
explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years
long. Each phase starts with a design goal and ends with a client reviewing
the progress thus far. Analysis and engineering efforts are applied at each
phase of the project, with an eye toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:
 The new system requirements are defined in as much details as
possible. This usually involves interviewing a number of users
representing all the external or internal users and other aspects of
the existing system.

12
 A preliminary design is created for the new system.
 A first prototype of the new system is constructed from the
preliminary design. This is usually a scaled-down system, and
represents an approximation of the characteristics of the final
product.
 A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths,
weakness, and risks.
2. Defining the requirements of the second prototype.
3. Planning an designing the second prototype.
4. Constructing and testing the second prototype.
 At the customer option, the entire project can be aborted if the risk
is deemed too great. Risk factors might involved development cost
overruns, operating-cost miscalculation, or any other factor that
could, in the customer’s judgment, result in a less-than-satisfactory
final product.
 The existing prototype is evaluated in the same manner as was the
previous prototype, and if necessary, another prototype is
developed from it according to the fourfold procedure outlined
above.
 The preceding steps are iterated until the customer is satisfied that
the refined prototype represents the final product desired.
 The final system is constructed, based on the refined prototype.
 The final system is thoroughly evaluated and tested. Routine
maintenance is carried on a continuing basis to prevent large scale
failures and to minimize down time.

The following diagram shows how a spiral model acts like:

13
 Fig 1.0-Spiral Model

2.3 STUDY OF THE SYSTEM

In the flexibility of the uses the interface has been developed a
graphics concept in mind, associated through a browser interface. The GUI’S
at the top level have been categorized as

1. Administrative user interface

14
 2. The operational or generic user interface
The administrative user interface concentrates on the consistent
information that is practically, part of the organizational activities and which
needs proper authentication for the data collection. The interfaces help the
administrations with all the transactional states like Data insertion, Data
deletion and Data updating along with the extensive data search capabilities.
The operational or generic user interface helps the users upon the
system in transactions through the existing data and required services. The
operational user interface also helps the ordinary users in managing their
own information helps the ordinary users in managing their own information
in a customized manner as per the assisted flexibilities

2.4 PROPOSED SYSTEM

In this system, we proposed a novel authentication protocol based on Gen2

called Gen2+, for low-cost RFID tags. Our protocol follows every message
flow in Gen2 to provide backward compatibility. Gen2+ is a multiple round
protocol using shared pseudonyms and Cyclic Redundancy Check (CRC) to
achieve reader-to-tag authentication. Conversely, Gen2+ uses the memory
read command defined in gen2 to achieve tag-to-reader authentication. We
show that Gen2+ is more secure under tracing and cloning attacks.
The main idea is to randomize each session and provide mutual
authentication between legitimate readers and tags, like other pseudonym-
based approaches we assume that each tag shares an l-word-long random
string, called keypool, with the back-end database. This string is randomly
generated by the back-end server and is written into the tag’s user-bank
memory before deployment. The string is considered as a keypool where we
can randomly draw keys. A threshold value is set in each tag to tolerate
error bits of the received value and to boost the reading speed. Therefore,

15
we need an extra circuitry element in the tag to calculate the Hamming
distance of two 16-bit numbers. Hamming distance calculators are often
seen in error-correcting hardware’s. We believe the new tag can be
implemented easily.
2.5 NUMBER OF MODULES

The system is proposed to have the following modules:

1. Registration

2. Editing

3. Viewing

4. Deleting

5. Authentication

1. Registration:-

In this Module the admin will register the other administrators

and other users, while registering the users the admin will provide the RFID
for the users.

2. Editing:-

In this Module the administrator can search the user’s

information with the help of given RFID and he can modify the details and he
can change his details also.
3. Viewing :-

In this Module the administrator can view all the Employees and
other Administrators or he can view the details by typing the Employee id.
4. Deleting:-

16
 In this module the administrator can search the Employees
details and by typing the RFID and Employee Id and he can delete the
particular Employee Details.

5. Authentication:-

Authentication is nothing but providing security to the system.

Here every administrator must enter into the system throw login page. The
login page will restrict the UN authorized users. A user must provide his
credential like user Id and password for log into the system. For that the
system maintains data for all users. Whenever a user enters his user id and
password, it checks in the database for user existence. If the user is exists
he can be treated as a valid user. Otherwise the request will throw back.
By using this Authentication we can encrypt and store the unique
RFID in database and we can decrypt the Employee RFID and view his
details.

The implementation requires the following resources:

Hardware requirements:
Processor == P VI 2.8 GHz
Ram == 1GB
Hard Disk == 160GB
Software requirements:
 IDE( Integrated Development Environment) Microsoft Visual Studio.NET
2008
Database SQL Server 2008
 Frameworks  .NET FrameWorks3.5
 Programming Language  C#
2.6 INPUT AND OUTPUT

17
 The major inputs and outputs and major functions of the system are
follows:
Inputs:
 Admin enter his user id and password for login.
 User enters his user id and password for login.
 User Create new folder for personnel usage.
 Admin enter user id or date for track the user login information
 New user gives his completed personnel, address and phone details for
registration.
 Admin gives different kind of user information for search the user data.
 User gives his user id, hint question, answer for getting the forgotten
password.
 Administrator giving information to generate various kinds of reports.

Outputs:
 Admin can have his own home page.
 Users enter their own home page.
 The user defined folders can store in the centralized database.
 Admin will get the login information of a particular user.
 The new user’s data will be stored in the centralized database.
 Admin get the search details of different criteria.
 User can get his forgot password.
 Different kind of reports is generated by administrator.

18
FEASIBILITY REPORT

19
 Preliminary investigation examine project feasibility, the likelihood the
system will be useful to the organization. The main objective of the
feasibility study is to test the Technical, Operational and Economical
feasibility for adding new modules and debugging old running system. All
system is feasible if they are unlimited resources and infinite time. There are
aspects in the feasibility study portion of the preliminary investigation:
 Technical Feasibility
 Operational Feasibility
 Economical Feasibility

3.1. TECHNICAL FEASIBILITY

The technical issue usually raised during the feasibility stage of the
investigation includes the following:
 Does the necessary technology exist to do what is suggested?
 Do the proposed equipments have the technical capacity to hold the
data required to use the new system?

20
  Will the proposed system provide adequate response to inquiries,
regardless of the number or location of users?
 Can the system be upgraded if developed?
 Are there technical guarantees of accuracy, reliability, ease of access
and data security?
Earlier no system existed to cater to the needs of ‘Secure
Infrastructure Implementation System’. The current system developed is
technically feasible. It is a web based user interface for audit workflow at
NIC-CSD. Thus it provides an easy access to the users. The database’s
purpose is to create, establish and maintain a workflow among various
entities in order to facilitate all concerned users in their various capacities or
roles. Permission to the users would be granted based on the roles specified.
Therefore, it provides the technical guarantee of accuracy, reliability
and security. The software and hard requirements for the development of
this project are not many and are already available in-house at NIC or are
available as free as open source. The work for the project is done with the
current equipment and existing software technology. Necessary bandwidth
exists for providing a fast feedback to the users irrespective of the number
of users using the system.
3.2. OPERATIONAL FEASIBILITY
Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organization’s operating
requirements. Operational feasibility aspects of the project are to be taken
as an important part of the project implementation. Some of the important
issues raised are to test the operational feasibility of a project includes the
following: -
 Is there sufficient support for the management from the users?
 Will the system be used and work properly if it is being developed and
implemented?

21
  Will there be any resistance from the user that will undermine the
possible application benefits?

This system is targeted to be in accordance with the above-mentioned

issues. Beforehand, the management issues and user requirements have
been taken into consideration. So there is no question of resistance from the
users that can undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer
resources and would help in the improvement of performance status.
3.3. ECONOMICAL FEASIBILITY
A system can be developed technically and that will be used if installed
must still be a good investment for the organization. In the economical
feasibility, the development cost in creating the system is evaluated against
the ultimate benefit derived from the new systems. Financial benefits must
equal or exceed the costs.
The system is economically feasible. It does not require any addition
hardware or software. Since the interface for this system is developed using
the existing resources and technologies available at NIC, There is nominal
expenditure and economical feasibility for certain.

22
SOFTWARE REQUIREMENT SPECIFICATION

23
4.1 SCOPE OF THE PROJECT
The software, Site Explorer is designed for management of web sites
from a remote location.
Purpose: The main purpose for preparing this document is to give a general
insight into the analysis and requirements of the existing system or situation
and for determining the operating characteristics of the system.
Scope: This Document plays a vital role in the development life cycle
(SDLC) and it describes the complete requirement of the system. It is meant
for use by the developers and will be the basic during testing phase. Any
changes made to the requirements in the future will have to go through
formal change approval process.
DEVELOPERS RESPONSIBILITIES OVERVIEW:
The developer is responsible for:
 Developing the system, which meets the SRS and solving all the
requirements of the system?
 Demonstrating the system and installing the system at client's location
after the acceptance testing is successful.
 Submitting the required user manual describing the system interfaces
to work on it and also the documents of the system.
 Conducting any user training that might be needed for using the
system.
 Maintaining the system for a period of one year after installation.

4.2. FUNCTIONAL REQUIREMENTS

Functional Requirements refer to very important system requirements in
a software engineering process (or at micro level, a sub part of requirement
engineering) such as technical specifications, system design parameters and
guidelines, data manipulation, data processing and calculation modules etc.

Functional Requirements are in contrast to other software design

requirements referred to as Non-Functional Requirements which are

24
primarily based on parameters of system performance, software quality
attributes, reliability and security, cost, constraints in design/implementation
etc.

The key goal of determining “functional requirements” in a software product

design and implementation is to capture the required behavior of a software
system in terms of functionality and the technology implementation of the
business processes.

The Functional Requirement document (also called Functional

Specifications or Functional Requirement Specifications), defines the
capabilities and functions that a System must be able to perform
successfully.

Functional Requirements should include:

 Descriptions of data to be entered into the system

 Descriptions of operations performed by each screen
 Descriptions of work-flows performed by the system
 Descriptions of system reports or other outputs
 Who can enter the data into the system?
 How the system meets applicable regulatory requirements

The functional specification is designed to be read by a general audience.

Readers should understand the system, but no particular technical
knowledge should be required to understand the document.

25
Examples of Functional Requirements

Functional requirements should include functions performed by specific

screens, outlines of work-flows performed by the system and other business
or compliance requirements the system must meet.

Interface requirements

 Field accepts numeric data entry

 Field only accepts dates before the current date
 Screen can print on-screen data to the printer

Business Requirements

 Data must be entered before a request can approved

 Clicking the Approve Button moves the request to the Approval
Workflow
 All personnel using the system will be trained according to internal
training strategies

Regulatory/Compliance Requirements

 The database will have a functional audit trail

 The system will limit access to authorized users
 The spreadsheet can secure data with electronic signatures

Security Requirements

 Member of the Data Entry group can enter requests but not approve or
delete requests
 Members of the Managers group can enter or approve a request, but

26
 not delete requests
 Members of the Administrators group cannot enter or approve
requests, but can delete requests

The functional specification describes what the system must do; how the
system does it is described in the Design Specification.

If a User Requirement Specification was written, all requirements outlined in

the user requirement specification should be addressed in the functional
requirements.

4.3 NON FUNCTIONAL REQUIREMENTS

All the other requirements which do not form a part of the above
specification are categorized as Non-Functional Requirements.

A system may be required to present the user with a display of the number
of records in a database. This is a functional requirement.

How up-to-date this number needs to be is a non-functional

requirement. If the number needs to be updated in real time, the system
architects must ensure that the system is capable of updating the displayed
record count within an acceptably short interval of the number of records
changing.

Sufficient network bandwidth may also be a non-functional requirement of a

system.

Other examples:

 Accessibility
 Availability
 Backup

27
 Certification
 Compliance
 Configuration Management
 Documentation
 Disaster Recovery
 Efficiency (resource consumption for given load)
 Effectiveness (resulting performance in relation to effort)
 Extensibility (adding features, and carry-forward of customizations at
next major version upgrade)
 Failure Management
 Interoperability
 Maintainability
 Modifiability
 Open Source
 Operability
 Performance
 Platform compatibility
 Price
 Portability
 Quality (e.g. Faults Discovered, Faults Delivered, Fault Removal
Efficacy)
 Recoverability
 Resilience
 Resource constraints (processor speed, memory, disk space, network
bandwidth etc.)
 Response time
 Robustness
 Scalability (horizontal, vertical)
 Security

28
  Software, tools, standards etc.
 Stability
 Safety
 Supportability
 Testability
 Usability by target user community

Accessibility is a general term used to describe the degree to which a

product, device, service, or environment is accessible by as many people as
possible. Accessibility can be viewed as the "ability to access" and possible
benefit of some system or entity. Accessibility is often used to focus on
people with disabilities and their right of access to the system.

Availability is the degree to which a system, subsystem, or equipment is

operable and in a committable state at the start of a mission, when the
mission is called for at an unknown, i.e., a random, time. Simply put,
availability is the proportion of time a system is in a functioning condition.

Expressed mathematically, availability is 1 minus the unavailability.

A backup or the process of backing up refers to making copies of data so

that these additional copies may be used to restore the original after a data
loss event. These additional copies are typically called "backups."

Certification refers to the confirmation of certain characteristics of an

object, system, or organization. This confirmation is often, but not always,
provided by some form of external review, education, or assessment
Compliance is the act of adhering to, and demonstrating adherence to, a
standard or regulation.
Configuration management (CM) is a field that focuses on establishing
and maintaining consistency of a system's or product's performance and its

29
functional and physical attributes with its requirements, design, and
operational information throughout its life.
Documentation may refer to the process of providing evidence ("to
document something") or to the communicable material used to provide
such documentation (i.e. a document). Documentation may also (seldom)
refer to tools aiming at identifying documents or to the field of study
devoted to the study of documents and bibliographies

Disaster recovery is the process, policies and procedures related to

preparing for recovery or continuation of technology infrastructure critical to
an organization after a natural or human-induced disaster.

Disaster recovery planning is a subset of a larger process known as business

continuity planning and should include planning for resumption of
applications, data, hardware, communications (such as networking) and
other IT infrastructure

Extensibility (sometimes confused with forward compatibility) is a system

design principle where the implementation takes into consideration future
growth. It is a systemic measure of the ability to extend a system and the
level of effort required to implement the extension. Extensions can be
through the addition of new functionality or through modification of existing
functionality. The central theme is to provide for change while minimizing
impact to existing system functions.

Interoperability is a property referring to the ability of diverse systems

and organizations to work together (inter-operate). The term is often used in
a technical systems engineering sense, or alternatively in a broad sense,
taking into account social, political, and organizational factors that impact
system to system performance.

30
Maintenance is the ease with which a software product can be modified in
order to:

 correct defects
 meet new requirements
 make future maintenance easier, or
 cope with a changed environment;

Open source describes practices in production and development that

promote access to the end product's source materials—typically, their source
code

Operability is the ability to keep equipment, a system or a whole industrial

installation in a safe and reliable functioning condition, according to pre-
defined operational requirements.

In a computing systems environment with multiple systems this includes the

ability of products, systems and business processes to work together to
accomplish a common task.

Computer performance is characterized by the amount of useful work

accomplished by a computer system compared to the time and resources
used.

Depending on the context, good computer performance may involve one or

more of the following:

 Short response time for a given piece of work

 High throughput (rate of processing work)
 Low utilization of computing resource(s)
 High availability of the computing system or application
 Fast (or highly compact) data compression and decompression

31
  High bandwidth / short data transmission time

Price in economics and business is the result of an exchange and from that
trade we assign a numerical monetary value to a good, service or asset

Portability is one of the key concepts of high-level programming. Portability

is the software-code base feature to be able to reuse the existing code
instead of creating new code when moving software from an environment to
another. When one is targeting several platforms with the same application,
portability is the key issue for development cost reduction.

Quality: The common element of the business definitions is that the quality
of a product or service refers to the perception of the degree to which the
product or service meets the customer's expectations. Quality has no
specific meaning unless related to a specific function and/or object. Quality
is a perceptual, conditional and somewhat subjective attribute.

Reliability may be defined in several ways:

 The idea that something is fit for purpose with respect to time;
 The capacity of a device or system to perform as designed;
 The resistance to failure of a device or system;
 The ability of a device or system to perform a required function under
stated conditions for a specified period of time;
 The probability that a functional unit will perform its required function
for a specified interval under stated conditions.
 The ability of something to "fail well" (fail without catastrophic
consequences

Resilience is the ability to provide and maintain an acceptable level of

service in the face of faults and challenges to normal operation.

32
These services include:

 supporting distributed processing

 supporting networked storage
 maintaining service of communication services such as
o video conferencing
o instant messaging
o online collaboration
 access to applications and data as needed

Response time perceived by the end user is the interval between

(a) The instant at which an operator at a terminal enters a request for

a response from a computer and
(b) The instant at which the first character of the response is received
at a terminal.

In a data system, the system response time is the interval between the
receipt of the end of transmission of an inquiry message and the beginning
of the transmission of a response message to the station originating the
inquiry.

Robustness is the quality of being able to withstand stresses, pressures, or

changes in procedure or circumstance. A system or design may be said to
be "robust" if it is capable of coping well with variations (sometimes
unpredictable variations) in its operating environment with minimal damage,
alteration or loss of functionality.

The concept of scalability applies to technology and business settings.

Regardless of the setting, the base concept is consistent - The ability for a

33
business or technology to accept increased volume without impacting the
system.

In telecommunications and software engineering, scalability is a desirable

property of a system, a network, or a process, which indicates its ability to
either handle growing amounts of work in a graceful manner or to be readily
enlarged.

Security is the degree of protection against danger, loss, and criminals.

Security has to be compared and contrasted with other related concepts:

Safety, continuity, reliability. The key difference between security and
reliability is that security must take into account the actions of people
attempting to cause destruction.

Security as a state or condition is resistance to harm. From an objective

perspective, it is a structure's actual (conceptual and never fully knowable)
degree of resistance to harm.
Stability - it means much of the objects will be stable over time and will not
need changes.
Safety is the state of being "safe", the condition of being protected against
physical, social, spiritual, financial, political, emotional, occupational,
psychological, educational or other types or consequences of failure,
damage, error, accidents, harm or any other event which could be
considered non-desirable. This can take the form of being protected from the
event or from exposure to something that causes health or economical
losses. It can include protection of people or of possessions

Supportability (also known as serviceability) is one of the aspects of

RASU (Reliability, Availability, Serviceability, and Usability)). It refers to the
ability of technical support personnel to install, configure, and monitor
products, identify exceptions or faults, debug or isolate faults to root cause
analysis, and provide hardware or software maintenance in pursuit of solving

34
a problem and restoring the product into service. Incorporating serviceability
facilitating features typically results in more efficient product maintenance
and reduces operational costs and maintains business continuity.

Testability, a property applying to an empirical hypothesis, involves two

components: (1) the logical property that is variously described as
contingency, defeasibility, which means that counter examples to the
hypothesis are logically possible, and (2) the practical feasibility of observing
a reproducible series of such counter examples if they do exist. In short it
refers to the capability of an equipment or system to be tested

Usability is a term used to denote the ease with which people can employ a
particular tool or other human-made object in order to achieve a particular
goal. In human-computer interaction and computer science, usability often
refers to the elegance and clarity with which the interaction with a computer
program or a web site is designed.

35
 SELECTED SOFTWARE

Microsoft.NET Framework

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfill the following objectives:

36
  To provide a consistent object-oriented programming environment
whether object code is stored and executed locally, executed locally
but Internet-distributed, or executed remotely.

 To provide a code-execution environment that minimizes software

deployment and versioning conflicts.

 To provide a code-execution environment that guarantees safe

execution of code, including code created by an unknown or semi-
trusted third party.

 To provide a code-execution environment that eliminates the

performance problems of scripted or interpreted environments.

 To make the developer experience consistent across widely varying

types of applications, such as Windows-based applications and Web-
based applications.

 To build all communication on industry standards to ensure that code

based on the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language
runtime and the .NET Framework class library. The common language
runtime is the foundation of the .NET Framework. You can think of the
runtime as an agent that manages code at execution time, providing core
services such as memory management, thread management, and remoting,
while also enforcing strict type safety and other forms of code accuracy that
ensure security and robustness. In fact, the concept of code management is
a fundamental principle of the runtime. Code that targets the runtime is
known as managed code, while code that does not target the runtime is
known as unmanaged code. The class library, the other main component of
the .NET Framework, is a comprehensive, object-oriented collection of
reusable types that you can use to develop applications ranging from

37
traditional command-line or graphical user interface (GUI) applications to
applications based on the latest innovations provided by ASP.NET, such as
Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load

the common language runtime into their processes and initiate the execution
of managed code, thereby creating a software environment that can exploit
both managed and unmanaged features. The .NET Framework not only
provides several runtime hosts, but also supports the development of third-
party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side

environment for managed code. ASP.NET works directly with the runtime to
enable Web Forms applications and XML Web services, both of which are
discussed later in this topic.

Internet Explorer is an example of an unmanaged application that hosts the

runtime (in the form of a MIME type extension). Using Internet Explorer to
host the runtime enables you to embed managed components or Windows
Forms controls in HTML documents. Hosting the runtime in this way makes
managed mobile code (similar to Microsoft® ActiveX® controls) possible,
but with significant improvements that only managed code can offer, such as
semi-trusted execution and secure isolated file storage.

The following illustration shows the relationship of the common language

runtime and the class library to your applications and to the overall system.
The illustration also shows how managed code operates within a larger
architecture.

Features of the Common Language Runtime

The common language runtime manages memory, thread execution, code

execution, code safety verification, compilation, and other system services.

38
These features are intrinsic to the managed code that runs on the common
language runtime.

With regards to security, managed components are awarded varying degrees

of trust, depending on a number of factors that include their origin (such as
the Internet, enterprise network, or local computer). This means that a
managed component might or might not be able to perform file-access
operations, registry-access operations, or other sensitive functions, even if it
is being used in the same active application.

The runtime enforces code access security. For example, users can trust that
an executable embedded in a Web page can play an animation on screen or
sing a song, but cannot access their personal data, file system, or network.
The security features of the runtime thus enable legitimate Internet-
deployed software to be exceptionally feature rich.

The runtime also enforces code robustness by implementing a strict type-

and code-verification infrastructure called the common type system (CTS).
The CTS ensures that all managed code is self-describing. The various
Microsoft and third-party language compilers

Generate managed code that conforms to the CTS. This means that
managed code can consume other managed types and instances, while
strictly enforcing type fidelity and type safety.

In addition, the managed environment of the runtime eliminates many

common software issues. For example, the runtime automatically handles
object layout and manages references to objects, releasing them when they
are no longer being used. This automatic memory management resolves the
two most common application errors, memory leaks and invalid memory
references.

39
The runtime also accelerates developer productivity. For example,
programmers can write applications in their development language of choice,
yet take full advantage of the runtime, the class library, and components
written in other languages by other developers. Any compiler vendor who
chooses to target the runtime can do so. Language compilers that target
the .NET Framework make the features of the .NET Framework available to
existing code written in that language, greatly easing the migration process
for existing applications.

While the runtime is designed for the software of the future, it also supports
software of today and yesterday. Interoperability between managed and
unmanaged code enables developers to continue to use necessary COM
components and DLLs.

The runtime is designed to enhance performance. Although the common

language runtime provides many standard runtime services, managed code
is never interpreted. A feature called just-in-time (JIT) compiling enables all
managed code to run in the native machine language of the system on which
it is executing. Meanwhile, the memory manager removes the possibilities of
fragmented memory and increases memory locality-of-reference to further
increase performance.

Finally, the runtime can be hosted by high-performance, server-side

applications, such as Microsoft® MS Access™ and Internet Information
Services (IIS). This infrastructure enables you to use managed code to write
your business logic, while still enjoying the superior performance of the
industry's best enterprise servers that support runtime hosting.

.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly
integrate with the common language runtime. The class library is object
oriented, providing types from which your own managed code can derive

40
functionality. This not only makes the .NET Framework types easy to use,
but also reduces the time associated with learning new

features of the .NET Framework. In addition, third-party components can

integrate seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of

interfaces that you can use to develop your own collection classes. Your
collection classes will blend seamlessly with the classes in the .NET
Framework.

As you would expect from an object-oriented class library, the .NET

Framework types enable you to accomplish a range of common
programming tasks, including tasks such as string management, data
collection, database connectivity, and file access. In addition to these
common tasks, the class library includes types that support a variety of
specialized development scenarios. For example, you can use the .NET
Framework to develop the following types of applications and services:

 Console applications.

 Scripted or hosted applications.

 Windows GUI applications (Windows Forms).

 ASP.NET applications.

 XML Web services.

 Windows services.

For example, the Windows Forms classes are a comprehensive set of

reusable types that vastly simplify Windows GUI development. If you write
an ASP.NET Web Form application, you can use the Web Forms classes.

41
Client Application Development

Client applications are the closest to a traditional style of application in

Windows-based programming. These are the types of applications that
display windows or forms on the desktop, enabling a user to perform a task.
Client applications include applications such as word processors and
spreadsheets, as well as custom business applications such as data-entry
tools, reporting tools, and so on. Client applications usually employ windows,
menus, buttons, and other GUI elements, and they likely access local
resources such as the file system and peripherals such as printers.

Another kind of client application is the traditional ActiveX control (now

replaced by the managed Windows Forms control) deployed over the
Internet as a Web page. This application is much like other client
applications: it is executed natively, has access to local resources, and
includes graphical elements.

In the past, developers created such applications using C/C++ in

conjunction with the Microsoft Foundation Classes (MFC) or with a rapid
application development (RAD) environment such as Microsoft® Visual
Basic®. The .NET Framework incorporates aspects of these existing products
into a single, consistent development environment that drastically simplifies
the development of client applications.

The Windows Forms classes contained in the .NET Framework are designed
to be used for GUI development. You can easily create command windows,
buttons, menus, toolbars, and other screen elements with the flexibility
necessary to accommodate shifting business needs.

For example, the .NET Framework provides simple properties to adjust visual
attributes associated with forms. In some cases the underlying operating
system does not support changing these attributes directly, and in these

42
cases the .NET Framework automatically recreates the forms. This is one of
many ways in which the .NET Framework integrates the developer interface,
making coding simpler and more consistent.

Unlike ActiveX controls, Windows Forms controls have semi-trusted access

to a user's computer. This means that binary or natively executing code can
access some of the resources on the user's system (such as GUI elements
and limited file access) without being able to access or compromise other
resources. Because of code access security, many applications that once
needed to be installed on a user's system can now be safely deployed
through the Web. Your applications can implement the features of a local
application while being deployed like a Web page.

ASP.Net
Server Application Development

Server-side applications in the managed world are implemented through

runtime hosts. Unmanaged applications host the common language runtime,
which allows your custom managed code to control the behavior of the
server. This model provides you with all the features of the common
language runtime and class library while gaining the performance and
scalability of the host server.

The following illustration shows a basic network schema with managed code
running in different server environments. Servers such as IIS and MS Access
can perform standard operations while your application logic executes
through the managed code.

Server-side managed code

ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more
than just a runtime host; it is a complete architecture for developing Web

43
sites and Internet-distributed objects using managed code. Both Web Forms
and XML Web services use IIS and ASP.NET as the publishing mechanism for
applications, and both have a collection of supporting classes in the .NET
Framework.

XML Web services, an important evolution in Web-based technology, are

distributed, server-side application components similar to common Web
sites. However, unlike Web-based applications, XML Web services
components have no UI and are not targeted for browsers such as Internet
Explorer and Netscape Navigator. Instead, XML Web services consist of
reusable software components designed to be consumed by other
applications, such as traditional client applications, Web-based applications,
or even other XML Web services. As a result, XML Web services technology
is rapidly moving application development and deployment into the highly
distributed environment of the Internet.

If you have used earlier versions of ASP technology, you will immediately
notice the improvements that ASP.NET and Web Forms offers. For example,
you can develop Web Forms pages in any language that supports the .NET
Framework. In addition, your code no longer needs to share the same file
with your HTTP text (although it can continue to do so if you prefer). Web
Forms pages execute in native machine language because, like any other
managed application, they take full advantage of the runtime. In contrast,
unmanaged ASP pages are always scripted and interpreted. ASP.NET pages
are faster, more functional, and easier to develop than unmanaged ASP
pages because they interact with the runtime like any managed application.

The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web
services are built on standards such as SOAP (a remote procedure-call
protocol), XML (an extensible data format), and WSDL ( the Web Services

44
Description Language). The .NET Framework is built on these standards to
promote interoperability with non-Microsoft solutions.

For example, the Web Services Description Language tool included with
the .NET Framework SDK can query an XML Web service published on the
Web, parse its WSDL description, and produce C# or Visual Basic source
code that your application can use to become a client of the XML Web
service. The source code can create classes derived from classes in the class
library that handle all the underlying communication using SOAP and XML
parsing. Although you can use the class library to consume XML Web
services directly, the Web Services Description Language tool and the other
tools contained in the SDK facilitate your development efforts with the .NET
Framework.

If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication
standards, such as SOAP, WSDL, and XML. Using those classes enables you
to focus on the logic of your service, without concerning yourself with the
communications infrastructure required by distributed software
development.

Finally, like Web Forms pages in the managed environment, your XML Web
service will run with the speed of native machine language using the scalable
communication of IIS.

Active Server Pages.NET

ASP.NET is a programming framework built on the common language

runtime that can be used on a server to build powerful Web applications.
ASP.NET offers several important advantages over previous Web
development models:

45
  Enhanced Performance. ASP.NET is compiled common
language runtime code running on the server. Unlike its interpreted
predecessors, ASP.NET can take advantage of early binding, just-in-time
compilation, native optimization, and caching services right out of the box.
This amounts to dramatically better performance before you ever write a line
of code.

 World-Class Tool Support. The ASP.NET framework is

complemented by a rich toolbox and designer in the Visual Studio integrated
development environment. WYSIWYG editing, drag-and-drop server
controls, and automatic deployment are just a few of the features this
powerful tool provides.

 Power and Flexibility. Because ASP.NET is based on the

common language runtime, the power and flexibility of that entire platform
is available to Web application developers. The .NET Framework class
library, Messaging, and Data Access solutions are all seamlessly accessible
from the Web. ASP.NET is also language-independent, so you can choose the
language that best applies to your application or partition your application
across many languages. Further, common language runtime interoperability
guarantees that your existing investment in COM-based development is
preserved when migrating to ASP.NET.

 Simplicity. ASP.NET makes it easy to perform common tasks,

from simple form submission and client authentication to deployment and
site configuration. For example, the ASP.NET page framework allows you to
build user interfaces that cleanly separate application logic from presentation
code and to handle events in a simple, Visual Basic - like forms processing
model. Additionally, the common language runtime simplifies development,

46
with managed code services such as automatic reference counting and
garbage collection.

 Manageability. ASP.NET employs a text-based, hierarchical

configuration system, which simplifies applying settings to your server
environment and Web applications. Because configuration information is
stored as plain text, new settings may be applied without the aid of local
administration tools. This "zero local administration" philosophy extends to
deploying ASP.NET Framework applications as well. An ASP.NET Framework
application is deployed to a server simply by copying the necessary files to
the server. No server restart is required, even to deploy or replace running
compiled code.

 Scalability and Availability. ASP.NET has been designed with

scalability in mind, with features specifically tailored to improve performance
in clustered and multiprocessor environments. Further, processes are closely
monitored and managed by the ASP.NET runtime, so that if one misbehaves
(leaks, deadlocks), a new process can be created in its place, which helps
keep your application constantly available to handle requests.

 Customizability and Extensibility. ASP.NET delivers a well-

factored architecture that allows developers to "plug-in" their code at the
appropriate level. In fact, it is possible to extend or replace any
subcomponent of the ASP.NET runtime with your own custom-written
component. Implementing custom authentication or state services has never
been easier.Security. With built in Windows authentication and per-
application configuration, you can be assured that your applications are
secure.

47
 Language Support
The Microsoft .NET Platform currently offers built-in support for three
languages: C#, Visual Basic, and JScript.
What is ASP.NET Web Forms?

The ASP.NET Web Forms page framework is a scalable common

language runtime programming model that can be used on the server to
dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax

compatibility with existing pages), the ASP.NET Web Forms framework has
been specifically designed to address a number of key deficiencies in the
previous model. In particular, it provides:

 The ability to create and use reusable UI controls that can

encapsulate common functionality and thus reduce the amount of code that
a page developer has to write.

 The ability for developers to cleanly structure their page logic in

an orderly fashion (not "spaghetti code").

 The ability for development tools to provide strong WYSIWYG

design support for pages (existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name
extension. They can be deployed throughout an IIS virtual root directory
tree. When a browser client requests .aspx resources, the ASP.NET runtime
parses and compiles the target file into a .NET Framework class. This class
can then be used to dynamically process incoming requests. (Note that
the .aspx file is compiled only the first time it is accessed; the compiled type
instance is then reused across multiple requests).

48
 An ASP.NET page can be created simply by taking an existing HTML
file and changing its file name extension to .aspx (no modification of code is
required). For example, the following sample demonstrates a simple HTML
page that collects a user's name and category preference and then performs
a form postback to the originating page when a button is clicked:

ASP.NET provides syntax compatibility with existing ASP pages. This

includes support for <% %> code render blocks that can be intermixed with
HTML content within an .aspx file. These code blocks execute in a top-down
manner at page render time.

Code-Behind Web Forms

ASP.NET supports two methods of authoring dynamic pages. The first

is the method shown in the preceding samples, where the page code is
physically declared within the originating .aspx file. An alternative
approach--known as the code-behind method--enables the page code to be
more cleanly separated from the HTML content into an entirely separate file.

Introduction to ASP.NET Server Controls

In addition to (or instead of) using <% %> code blocks to program
dynamic content, ASP.NET page developers can use ASP.NET server controls
to program Web pages. Server controls are declared within an .aspx file
using custom tags or intrinsic HTML tags that contain a runat="server"
attribute value. Intrinsic HTML tags are handled by one of the controls in the
System.Web.UI.HtmlControls namespace. Any tag that doesn't explicitly
map to one of the controls is assigned the type of
System.Web.UI.HtmlControls.HtmlGenericControl.

Server controls automatically maintain any client-entered values

between round trips to the server. This control state is not stored on the
server (it is instead stored within an <input type="hidden"> form field

49
that is round-tripped between requests). Note also that no client-side script
is required.

In addition to supporting standard HTML input controls, ASP.NET

enables developers to utilize richer custom controls on their pages. For
example, the following sample demonstrates how the <asp:adrotator>
control can be used to dynamically display rotating ads on a page.

1. ASP.NET Web Forms provide an easy and powerful way to build

dynamic Web UI.

2. ASP.NET Web Forms pages can target any browser client (there
are no script library or cookie requirements).

3. ASP.NET Web Forms pages provide syntax compatibility with

existing ASP pages.

4. ASP.NET server controls provide an easy way to encapsulate

common functionality.

5. ASP.NET ships with 45 built-in server controls. Developers can

also use controls built by third parties.

SQL SERVER 2005

Microsoft SQL Server 2005 is comprehensive, integrated data

management and analysis software that enables organizations to reliably
manage mission-critical information and confidently run today’s increasingly
complex business applications. SQL Server 2005 allows companies to gain
greater insight from their business information and achieve faster results for
a competitive advantage.

Top-10 Features of SqlServer-2005

50
1. T-SQL (Transaction SQL) enhancements
T-SQL is the native set-based RDBMS programming language offering high-
performance data access. It now incorporates many new features including
error handling via the TRY and CATCH paradigm, Common Table Expressions
(CTE), which return a record set in a statement, and the ability to shift
columns to rows and vice versa with the PIVOT and UNPIVOT commands.

2. CLR (Common Language Runtime)

The next major enhancement in SQL Server 2005 is the integration of a .NET
compliant language such as C#, ASP.NET or VB.NET to build objects (stored
procedures, triggers, functions, etc.). This enables you to execute .NET code
in the DBMS to take advantage of the .NET functionality. It is expected to
replace extended stored procedures in the SQL Server 2000 environment as
well as expand the traditional relational engine capabilities.

3. Service Broker
The Service Broker handles messaging between a sender and receiver in a
loosely coupled manner. A message is sent, processed and responded to,
completing the transaction. This greatly expands the capabilities of data-
driven applications to meet workflow or custom business needs.

4. Data encryption
SQL Server 2000 had no documented or publicly supported functions to
encrypt data in a table natively. Organizations had to rely on third-party
products to address this need. SQL Server 2005 has native capabilities to
support encryption of data stored in user-defined databases.

5. SMTP mail
Sending mail directly from SQL Server 2000 is possible, but challenging.
With SQL Server 2005, Microsoft incorporates SMTP mail to improve the
native mail capabilities. Say "see-ya" to Outlook on SQL Server!

51
6. HTTP endpoints
you can easily create HTTP endpoints via a simple T-SQL statement exposing
an object that can be accessed over the Internet. This allows a simple object
to be called across the Internet for the needed data.

7. Multiple Active Result Sets (MARS)

MARS allow a persistent database connection from a single client to have
more than one active request per connection. This should be a major
performance improvement, allowing developers to give users new
capabilities when working with SQL Server. For example, it allows multiple
searches, or a search and data entry. The bottom line is that one client
connection can have multiple active processes simultaneously.

8. Dedicated administrator connection

If all else fails, stop the SQL Server service or push the power button. That
mentality is finished with the dedicated administrator connection. This
functionality will allow a DBA to make a single diagnostic connection to SQL
Server even if the server is having an issue.

9. SQL Server Integration Services (SSIS)

SSIS has replaced DTS (Data Transformation Services) as the primary ETL
(Extraction, Transformation and Loading) tool and ships with SQL Server
free of charge. This tool, completely rewritten since SQL Server 2000, now
has a great deal of flexibility to address complex data movement.

10. Database mirroring

It's not expected to be released with SQL Server 2005 at the RTM in
November, but I think this feature has great potential. Database mirroring is
an extension of the native high-availability capabilities. So, stay tuned for
more details…. For now, here's

52
 REQUIREMENTS

AND

ANALYSIS

3. REQUIREMENTS AND ANALYSIS

3.1 Problem Definition:

This project is mainly built for College Services. The college authority wants
to computerized there data such as student marks,attendance.college also

53
wants to maintain online forum where college authority will create group
and students can join in to those groups. College authority also wants to
maintain the percentages of the final year students for placing the students
in different companies according to there percentages.

3.2 Scheduling:
Pert chart:
Program Evaluation Review Technique, PERT can be both a cost and a time
management system. PERT is organized by events and activities or tasks.
PERT has several advantages over bar charts and is likely to be used with
more complex projects. One advantage of PERT is that it is scheduling device
that also shows graphically which tasks must be completed before others are
begun.
.

PERT CHART

START I/O DESIGN

INTEGRATION
AND TESTING

ANALYSIS

CODING
FINISH

WRITE
MANUAL

54
Gantt chart (Bar Chart):
A Bar Chart is perhaps the simplest form of formal project management.
The bar chart is also known as Gantt chart. It is used almost exclusively for
scheduling purposes and therefore controls only the time of projects. Gantt
Charts are a project control technique that can be used for several
purposes, including scheduling, budgeting and resource planning. A Gantt
chart is a Bar Chart, with each bar representing an activity. The bars are
drawn against a time line. The length of each bar is proportional to the
length of time planned for the activity.

GANTT CHART

JAN 25,09 FEB 15,09 MAR 12,09 APR 01,09 APR 24,09

START

ANALYSIS

I /O DESIGN

CODING

WRITE MANUAL

INTEGRATION
AND
TESTING

SLACK TIME, i.e., the LATEST TIME by which a task must be finished

White part of the bar shows the length of time each task is estimated to take

55
3.3 HARDWARE & SOFTWARE SPECIFICATIONS

 HARDWARE REQUIREMENTS:

Processor : Pentium-IV

Ram : 128 MB Ram or above

HDD : 20 GB

 SOFTWARE REQUIREMENTS:

Operating System Windows XP Professional

(sp2)

Technology Net Framework 2.0

Language ASP.Net with C#.Net

Data Base SqlServer 2005

Web server IIS 5.0

56
 SYSTEM DESIGN

Conceptual Models:

Entity Relationship Diagram

57
An entity relationship diagram is a graphical representation of an
organization’s data storage
Requirements. Entity relationship diagrams are abstractions of the real world
which simplify the problem to be solved while retaining its essential features.

Entities:

 An entity is an object of concern used to represent the things in the

real world, e.g., car, table, book, etc.
 An entity need not be a physical entity; it can also represent a concept
in real world, e.g., project, loan, etc.
Attributes:
An attribute is a property used to describe the specific feature of the
entity. So to describe an entity entirely, a set of attributes is used.For
example, a student entity may be described by the student’s name,
age, address, course, etc.
Relationships:
A relationship can be defined as:
 A connection or set of associations, or
 A rule for communication among entities.
Relationship Cardinality:
Cardinality specifies the number of instances of an entity associated
with another entity participating in a relationship. Based on the
cardinality binary relationship can be further classified into the
following categories:
One-to-one:
An entity in A is associated with at most one entity in B, and an entity
in B is associated with at most one entity in A.
Ex: Relationship between college and principal
1 as
College H Principal
1
One-to-many:

58
 An entity in A is associated with any number of entities in B. An entity
in B is associated with at the most one entity in A.
Ex: Relationship between department and faculty.

k
or
Department W in Faculty
s-
Many-to-one: 1 M

An entity in A is associated with at most one entity in B. An

entity in B is associated with any number in A.
Ex: Relationship between course and instructor. An instructor can
teach various courses but a course can be taught only by one instructor.

M 1
ac
Course Te es Instructor
h

Many-to-many:

Entities in A and B are associated with any number of entities from

each other.
Ex: Taught-by relationship between course and faculty.

M M
ug
Course Ta - Faculty
ht
by

E-R Diagram:

We can also express the overall logical structure of a database

using ER model graphically with the help of an E-R diagram.

59
Features of ER-Diagram:

The basic features of ER diagrams are sufficient to design many

database situations. However, with more complex relations, it is
required to move to enhanced features of ER models, the three such
features are:
 Generalization
 Specialization
 Aggregation
ER diagram are composed of:
 Rectangles representing entity sets.
 Ellipses representing attributes.
 Diamonds representing relationship sets.
Let us define the symbols used in the ER diagram.

Entity

Relationship

Identifying relationship

Weak entity

Relationship between Admin and student entity

60
 Password
User Name
Student name
Hallticketn
o
1
M
Admin Student
Registe
rs
1
1
M
Maintai
ns
Views
Details
M

Courses

Course Id

UML Diagrams

Unified Modeling Language (UML) is a standard language for specifying,

visualizing, constructing, and documenting the artifacts of software systems,
as well as for business modeling and other non-software systems. The UML
represents a collection of best engineering practices that have proven
successful in the modeling of large and complex systems. The UML is a very
important part of developing objects oriented software and the software
development process. The UML uses mostly graphical notations to express
the design of software projects. Using the UML helps project teams
communicate, explore potential designs, and validate the architectural
design of the software.

61
Use Case Diagram
Displays the relationship among actors and use cases. A use case is a set of
scenarios that describing an interaction between a user and a system. A use
case diagram displays the relationship among actors and use cases. The two
main components of a use case diagram are use cases and actors.

62
 Register Student

Course

Semester

Subject
Admin
Attendance Student

Marks
Login

Group Login

Messages to
registered Group

Add Branch

Status of Member in a
group

63
Class Diagrams:

64
Sequence diagrams

65
Sequence diagrams show a detailed flow for a specific use case or even just
part of a specific use case. They are almost self explanatory; they show the
calls between the different objects in their sequence and can show, at a
detailed level, different calls to different objects.
Objects - oblong boxes at the top or actors, named or just shown as
belonging to a class from or to which messages are sent to other objects.
Messages - solid lines for calls and dotted lines to data returns, showing the
messages that are send between objects. This includes the order of the
messages which is from top of the diagram to the bottom.
Object lifelines - dotted vertical lines showing the lifetime of the objects
Activation - the vertical oblong boxes on the object lifelines showing the
thread of control in a synchronous system.

66
1. Administrator

:Login
LoginForm
Form : Home : Course Details : Course Details

Type url

On Submit ()
View ()

Manage ()

Logout

Logout ()

Manage Add / Edit /Change

Status

67
Admin : Branch Details : Semester Details : Subject Details

Manage ()
Manage ()

Logout ()

Insert ()

Logout ()

Insert ()

Logout ()

Manage Add / Edit

68
 : Student : Update Student
Admin Registration Details : View Details

insert ()
Manage ()

Logout () Edit studetails

()

Logout ()
View all
students

Logout ()

69
 : Marks
Admin : Update Marks : Insert Attendance : Placement
Cell

Insert()
Manage ()

Logout () Edit stu mks()

Logout ()
Insert()

Logout ()

View
Percentages

Logout

70
Admin : Create Group : Update Group : View Group : Delete Group

Insert a
new group
()

Update
existing group
()

Logout ()

Logout () View existing

group ()

Logout ()

Delete group

Logout()

71
Student:

:Login Form
Login Form : Home : Student Info : Marks

Type url

On Submit ()
View ()

Manage()

logout

Logout ()

72
 State Chart Diagrams

A state chart diagram shows the behavior of classes in response to external

stimuli. This diagram models the dynamic flow of control from state to state
within a system. These diagrams give an architectural and high-level view of
a system. In a typical software life cycle, the business or functional domain
experts define Use Case diagrams
States

States represent situations during the life of an object. You can easily
illustrate a state in Smart Draw by using a rectangle with rounded corners.

Transition

A solid arrow represents the path between different states of an object.

Label the transition with the event that triggered it and the action that
results from it.

Initial State

A filled circle followed by an arrow represents the object's initial state.

Final State

73
An arrow pointing to a filled circle nested inside another circle represents the
object's final state.

Change Password:

Ask for change Password

Ask for old password

Ask for new password Redirect

Check new password

Confirm Password not matched

Passwor Display Error
d

Redirect to Login Page

74
 For Login:

Waiting for login

Enter username password

Not valid user

Validating

Redirection to
Next page

Activity Diagrams:

Activity diagrams are a loosely defined diagram technique for showing

workflows of stepwise activities and actions, with support for choice,
iteration and concurrency. In the Unified Modeling Language, activity
diagrams can be used to describe the business and operational step-by-step
workflows of components in a system. An activity diagram shows the overall
flow of control.

Activity diagrams are typically used for business process modeling. They
consist of:

75
  Initial node.

 Activity final node.

 Activities

The starting point of the diagram is the initial node, and the activity final
node is the ending. An activity diagram can have zero or more activity final
nodes. In between activities are represented by rounded rectangles.
A swimlane is a way to group activities performed by the same actor on an
activity diagram or to group activities in a single thread.

Initial Activity:

This shows the starting point or first activity of the flow. Denoted by a
solid circle. This is similar to the notation used for Initial State.
Activity:

Represented by a rectangle with rounded (almost oval) edges.

Decisions:

Similar to flowcharts, a logic where a decision is to be

made is depicted by a diamond, with the options written on either side of the
arrows emerging from the diamond, within box brackets.

Signal:

76
 When an activity sends or receives a message, that activity is
called a signal. Signals are of two types: Input signal (Message receiving
activity) shown by a concave polygon and Output signal (Message sending
activity) shown by a convex polygon.
Concurrent Activities:

Some activities occur simultaneously or in parallel.

Such activities are called concurrent activities. For example, listening to the
lecturer and looking at the blackboard is a parallel activity. This is
represented by a horizontal split (thick dark line) and the two concurrent
activities next to each other, and the horizontal line again to show the end of
the parallel activity.
Final Activity:

The end of the Activity diagram is shown by a bull's eye symbol, also
called as a final activity.

Activity Diagram

77
 Administrator User

Open
Site
Click login form

Submit id & pwd [not valid]

[valid]

Placement Student
cell Details

Student

Student Student Student Complaints

Registrati Attendance Marks
on

View
Add Edit

78
 User
Administrator

Group

[not valid]

Add Edit delete

Course Branch Semester

Details Details Details

Logout

79
Collaboration Diagram:

For Admin:

For Student:

80
6.5. DATA DICTONARY
After carefully understanding the requirements of the client the the
entire data storage requirements are divided into tables. The below tables
are normalized to avoid any anomalies during the course of data entry.

TABLE OF FIGURES

 Admin Login Info

2.Course

81
3.Branch

4. Semester

5. Subject

82
6. Type Master

7. Login Info

8. StudentInfo

83
9. Student Marks

10. StudentAttendence

84
 11. Group Info

12. Register Group

85
13. Member Message

86
DATA FLOW DIAGRAM:

A data flow diagram is graphical tool used to describe and analyze

movement of data through a system. These are the central tool and the
basis from which the other components are developed. The transformation
of data from input to output, through processed, may be described logically
and independently of physical components associated with the system.
These are known as the logical data flow diagrams. The physical data flow
diagrams show the actual implements and movement of data between
people, departments and workstations. A full description of a system
actually consists of a set of data flow diagrams. Using two familiar notations
Yourdon, Gane and Sarson notation develops the data flow diagrams. Each
component in a DFD is labeled with a descriptive name. Process is further
identified with a number that will be used for identification purpose. The
development of DFD’s is done in several levels. Each process in lower level
diagrams can be broken down into a more detailed DFD in the next level.
The lop-level diagram is often called context diagram. It consists a single
process bit, which plays vital role in studying the current system. The
process in the context level diagram is exploded into other process at the
first level DFD.
The idea behind the explosion of a process into more process is that
understanding at one level of detail is exploded into greater detail at the
next level. This is done until further explosion is necessary and an adequate
amount of detail is described for analyst to understand the process.

87
 Larry Constantine first developed the DFD as a way of expressing
system requirements in a graphical from, this lead to the modular design.
A DFD is also known as a “bubble Chart” has the purpose of clarifying
system requirements and identifying major transformations that will become
programs in system design. So it is the starting point of the design to the
lowest level of detail. A DFD consists of a series of bubbles joined by data
flows in the system.
DFD SYMBOLS:
In the DFD, there are four symbols
1. A square defines a source(originator) or destination of system data
2. An arrow identifies data flow. It is the pipeline through which the
information flows
3. A circle or a bubble represents a process that transforms incoming data
flow into outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository
of data
Process that transforms data flow.

Source or Destination of data

Data flow

Data Store

88
CONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFD’s:
1. Process should be named and numbered for an easy reference. Each
name should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow
back to the source. One way to indicate this is to draw long flow line
back to a source. An alternative way is to repeat the source symbol as a
destination. Since it is used more than once in the DFD it is marked with
a short diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters.
Process and dataflow names have the first letter of each work capitalized
A DFD typically shows the minimum contents of data store. Each data
store should contain all the data elements that flow in and out.
Questionnaires should contain all the data elements that flow in and out.
Missing interfaces redundancies and like is then accounted for often
through interviews.
SAILENT FEATURES OF DFD’s

1. The DFD shows flow of data, not of control loops and decision are
controlled considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process
whether the dataflows take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.
Context Level Diagram

89
 Admin

Admin
Student Help
Desk
Student
Student

Create Group
Insert Marks View Marks
View Attendance
Insert Attendance View
Account Details
View Attendance View all
groups
0.0
View Student
Online
Student Student
Admin Community

Create User
Change Password
Forgot Password View Group
Course Details
Branch Details
Semester Details
Subject Details
Register Student

90
Admin Module
Dfd for Login Process
Admin Form

User name
1.0 Verified & 1. 1
Admin
& Password Validation of Valid User Home Page
Password

Not valid user

Try again

Dfd for Level 2 for admin

studentAttendance

Student
attendance Course
Subject

Course Details Subject Details

91
 Adminlogininfo
Semester

Create User Semester

2.0
Details
Admin Home

Branch

Student info Student Registration

Branch Details

Group Student Marks

Student marks

Group info

92
Student Module
Dfd Level for Student login

Hallticketno no
1.0 Verified &
Student 1. 1
& Password Validation of Valid User
Password Redirect to
next page

Not valid user

Try again

Dfd Level 2 for student

Student

Student info
2.0 Account Details

Redirection

LoginChange
Info
Password Group

Marks Details

93
Group Info

Student Marks

Dfd Level 3 for student

Student

Member Message
3.0 Messages

Group

Member Message

Post Messages Join another group

Members

Group Info

Register Group

94
Flow Chart
A flow chart is defined as a pictorial representation describing a process
being studied or even used to plan stages of a project. Flow charts tend to
provide people with a common language or reference point when dealing
with a project or process.

A flowchart is one of the seven basic tools of quality control, which also
includes the histogram, Pareto chart, check sheet, control chart, cause-and-
effect diagram, and scatter diagram (see Quality Management Glossary).
They are commonly used in business/economic presentations to help the
audience visualize the content better, or to find flaws in the process.

BASIC FLOWCHARTING SHAPES AND SYMBOLS

Flowcharts use special shapes to represent different types of actions or steps

in a process. Lines and arrows show the sequence of the steps, and the
relationships among them.

Start/End
The terminator symbol marks the starting or ending point of the system. It
usually contains the word "Start" or "End."

Action or Process
A box can represent a single step ("add two cups of flour"), or and entire
sub-process ("make bread") within a larger process.

Document
A printed document or report.

95
Flow chart for Login Screen

START

Enter User
And Password

Verify from
Database

Print bad Username

Is and
Correct Password
?

Allow Permission as
Per access

STOP

96
SYSTEM DESIGN

97
4.1 Basic Modules

This Project contains basically 2 main Modules

 Admin Module
 Student Module
Admin Module
Admin Module contains the following sub modules
1. Course Details
2. Branch Details
3. Semester Details
4. Subject Details
5. Student Registration
6. Student Attendance
7. Student Marks
8. Student Update Marks
9. Student Details Update
10. Create Group
11. Update Group
12. Delete Group
13. View Group
14. Placement Cell
Course Details

98
In this Module Admin can insert Courses which he wants to Maintain in his
college and also admin has Permission to update name of the course.
Branch Details
In this module admin will insert branches according to courses.
Semester Details
This Module maintains the details about the semester in a Particular
course.Admin has permission to update the name of the semester

Subject Details
This Module maintains the details about the subjects belonging to a
particular semester.Admin has a Permission to change the name of the
subjects.
Student Registration
In this Module admin registers the student details who will be joining in the
college
Student Attendance
In this module admin maintains attendance of student Day wise for every
subject for which classes are held.
Student Marks
This module maintains the details about the marks of the student semester
wise and also the type of the exam for which they are appearing .here type
of the exam may be Internal I, Internal II or External.
Student Update Marks
In this Module admin can update marks of the students According to type of
the type of the exam written by the Student.
Student Details Update
In this Module admin can update details of the students

99
Create Group
In this module can create a group. Group can be created on a Basic category
Update Group
Here Admin can update his group.admin can change the name of his group
name also description of group
Delete Group
In this module admin has permission to delete a group
View Group
In this module admin can view the members in each group. Here admin
changes the status of the member in the group .Initially when the member
registers into a group his status will be pending admin changes as
approved.Admin can also Change the status of the messages which are
posted
by the student.

Placement Cell
In this module admin will find percentages of final year student’s .seeing
those percentages he can pick some of the students and place them in the
notice board
Student Module
Student Module Contains sub modules
Student Information
In this Module Student can view his details when he login into the
system .he/she can view his marks details and attendance details.
Group Display
When the student log in to system. He will find a hyperlink Called group if
the student is already registered then and If he is approved student then he
will be able to see all the approved messages of that group. if the student is

100
not registered in any of the group then he will get search screen Where he
can find a group and can join in to the group

OUTPUT SCREENS

101
Output Screens:
Home Page:

102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
 IMPLEMENTATION
AND
SYSTEM
TESTING

8. IMPLEMENTATION AND TESTING

8.1 Coding Details

Course Details:
using System;
using System.Data;

124
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;

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

{

string coursename = "", c1 = "",CourseStatus="";

bool b;
int CourseId;
protected void Page_Load(object sender, EventArgs e)
{
helpdeskclass.connectmethod();
if (!IsPostBack)
{
FillGrid();
}
}
protected void btnSubmit1_Click(object sender, EventArgs e)
{

DataSet ds = helpdeskclass.GetCourse();
if (ds.Tables[0].Rows.Count > 0)
{
lblcourse.Visible = false;
for (int i = 0; i < ds.Tables[0].Rows.Count; i++)
{
coursename = ds.Tables[0].Rows[i]["CourseName"].ToString();
if (coursename == txtCourse.Text)
{
lblcourse.Visible = false;
c1 = coursename;
lblc.Visible = true;

txtCourse.Focus();
}//ifcoursename
}//for
}//ifds.tables[0]

125
 if (c1 != txtCourse.Text)
{
CourseStatus = "Available";
b = helpdeskclass.insertcourse(txtCourse.Text,CourseStatus);
if (b)
lblcourse.Visible = true;
lblc.Visible = false;
txtCourse.Text = String.Empty;
FillGrid();
}//if
}

public void FillGrid()

{
DataSet ds = helpdeskclass.GetCourse();
if (ds.Tables[0].Rows.Count > 0)
{
gvCourseDetails.DataSource = ds.Tables[0];
gvCourseDetails.DataBind();
}
}

protected void gvCourseDetails_RowEditing(object sender,

GridViewEditEventArgs e)
{
gvCourseDetails.EditIndex = e.NewEditIndex;
FillGrid();
}
protected void gvCourseDetails_RowCancelingEdit(object sender,
GridViewCancelEditEventArgs e)
{
gvCourseDetails.EditIndex = -1;
FillGrid();
}

protected void gvCourseDetails_RowUpdating(object sender,

GridViewUpdateEventArgs e)
{
int i = e.RowIndex;
CourseId = int.Parse(gvCourseDetails.DataKeys[i].Value.ToString());
DropDownList ddl =
(DropDownList)this.gvCourseDetails.Rows[i].FindControl("ddlCourseStatus")
;

126
 CourseStatus = ddl.SelectedItem.ToString();
b = helpdeskclass.updatecourse(CourseId, CourseStatus);
if (b)
{
gvCourseDetails.EditIndex = -1;
FillGrid();
}

}
}

8.2 Testing Apporach

Software Testing Techniques:

Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, designing and coding.

INTRODUCTION
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. In fact,
testing is the one step in the software engineering process that could be
viewed as destructive rather than constructive.

A strategy for software testing integrates software test case design

methods into a well-planned series of steps that result in the successful
construction of software. Testing is the set of activities that can be planned
in advance and conducted systematically. The underlying motivation of
program testing is to affirm software quality with methods that can
economically and effectively apply to both strategic to both large and small-
scale systems.
STRATEGIC APPROACH TO SOFTWARE TESTING
The software engineering process can be viewed as a spiral. Initially
system engineering defines the role of software and leads to software
requirement analysis where the information domain, functions, behavior,

127
performance, constraints and validation criteria for software are established.
Moving inward along the spiral, we come to design and finally to coding. To
develop computer software we spiral in along streamlines that decrease the
level of abstraction on each turn.
A strategy for software testing may also be viewed in the context of
the spiral. Unit testing begins at the vertex of the spiral and concentrates on
each unit of the software as implemented in source code. Testing progress
by moving outward along the spiral to integration testing, where the focus is
on the design and the construction of the software architecture. Talking
another turn on outward on the spiral we encounter validation testing where
requirements established as part of software requirements analysis are
validated against the software that has been constructed. Finally we arrive
at system testing, where the software and other system elements are tested
as a whole.

UNIT TESTING

MODULE TESTING

Component Testing
SUB-SYSTEM TESING

SYSTEM TESTING
Integration Testing

128
ACCEPTANCE TESTING
User Testing
8.3. UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software

design, the module. The unit testing we have is white box oriented and some
modules the steps are conducted in parallel.

1. WHITE BOX TESTING

This type of testing ensures that
 All independent paths have been exercised at least once
 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational
bounds
 All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each
form .we have created independently to verify that Data flow is correct, All
conditions are exercised to check their validity, All loops are executed on
their boundaries.
2. BASIC PATH TESTING
Established technique of flow graph with Cyclomatic complexity was used to
derive test cases for all the functions. The main steps in deriving test cases
were:
Use the design of the code and draw correspondent flow graph.
Determine the Cyclomatic complexity of resultant flow graph, using formula:
V(G)=E-N+2 or
V(G)=P+1 or
V(G)=Number Of Regions
Where V(G) is Cyclomatic complexity,
E is the number of edges,
N is the number of flow graph nodes,
P is the number of predicate nodes.
Determine the basis of set of linearly independent paths.

3. CONDITIONAL TESTING

129
In this part of the testing each of the conditions were tested to both true and
false aspects. And all the resulting paths were tested. So that each path that
may be generate on particular condition is traced to uncover any possible
errors.
4. DATA FLOW TESTING
This type of testing selects the path of the program according to the location
of definition and use of variables. This kind of testing was used only when
some local variable were declared. The definition-use chain method was
used in this type of testing. These were particularly useful in nested
statements.
5. LOOP TESTING
In this type of testing all the loops are tested to all the limits possible.
The following exercise was adopted for all loops:
All the loops were tested at their limits, just above them and just below
them.
All the loops were skipped at least once.
For nested loops test the inner most loop first and then work outwards.
For concatenated loops the values of dependent loops were set with the
help of connected loop.
Unstructured loops were resolved into nested loops or concatenated loops
and tested as above.
Each unit has been separately tested by the development team itself
and all the input have been validated.
8.4 INTEGRATION TESTING

Testing is done for each module. After testing all the modules, the
modules are integrated and testing of the final system is done with the test
data, specially designed to show that the system will operate successfully in
all its aspects conditions. Thus the system testing is a confirmation that all is
correct and an opportunity to show the user that the system works.

The purpose of integration testing is to verify functional, performance

and reliability requirements placed on major design items. These "design
items", i.e. assemblages (or groups of units), are exercised through their
interfaces using black box testing, success and error cases being simulated

130
via appropriate parameter and data inputs. Simulated usage of shared data
areas and inter-process communication is tested and individual subsystems
are exercised through their input interface.

Test cases are constructed to test that all components within

assemblages interact correctly, for example across procedure calls or
process activations, and this is done after testing individual modules, i.e.
unit testing.

The overall idea is a "building block" approach, in which verified

assemblages are added to a verified base which is then used to support the
integration testing of further assemblages.

131
 SYSTEM SECURITY

9.1 INTRODUCTION

The protection of computer based resources that includes hardware,

software, data, procedures and people against unauthorized use or natural
Disaster is known as System Security.
System Security can be divided into four related issues:
 Security
 Integrity
 Privacy
 Confidentiality
SYSTEM SECURITY refers to the technical innovations and procedures
applied to the hardware and operation systems to protect against deliberate
or accidental damage from a defined threat.
DATA SECURITY is the protection of data from loss, disclosure,
modification and destruction.
SYSTEM INTEGRITY refers to the power functioning of hardware and
programs, appropriate physical security and safety against external threats
such as eavesdropping and wiretapping.
PRIVACY defines the rights of the user or organizations to determine what
information they are willing to share with or accept from others and how the
organization can be protected against unwelcome, unfair or excessive
dissemination of information about it.
CONFIDENTIALITY is a special status given to sensitive information in a
database to minimize the possible invasion of privacy. It is an attribute of
information that characterizes its need for protection.
9.2 SECURITY SOFTWARE
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 system employees two types of checks and controls:

132
CLIENT SIDE VALIDATION
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:
 VBScript in used to ensure those required fields are filled with suitable
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.
 Tab-indexes are set according to the need and taking into account the
ease of user while working with the system.

SERVER SIDE VALIDATION

Some checks cannot be applied at client side. Server side checks are
necessary to save the system from failing and intimating the user that some
invalid operation has been performed or the performed operation is
restricted. Some of the server side checks imposed is:
 Server side constraint has been imposed to check for the validity of
primary key and foreign key. A primary key value cannot be duplicated.
Any attempt to duplicate the primary value results into a message
intimating the user about those values through the forms using foreign
key can be updated only of the existing foreign key values.

 User is intimating through appropriate messages about the successful

operations or exceptions occurring at server side.

 Various Access Control Mechanisms have been built so that one user may
not agitate upon another. 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 o the
server side.

 Using server side validation, constraints on several restricted operations

are imposed.

133
CONCLUSIONS

134
 6. CONCLUSION

The project titled as STUDENT HELP DESK was deeply studied and
analyzed to design the code and implement with various testing methods
was done under the guidance of the experienced project guide. The solution
developed is free from all the bugs and executable with all different modules
to the utmost satisfaction of the client. All the current requirements and
possibilities have been taken care during the project time. We feel that the
solution provided now will suit to all the needs of various clients in the same
industry but also we don’t rule the possibilities of further upgrading of this
solution with the new and advance technologies and further additional
requirements of the clients.

The documentation and the project report is finally prepared to be referred

as user manual for further effective results of this software solution

FUTURE ENHANCEMENTS

6.1 FUTURE SCOPE OF PROJECT

We are providing Pocket Pc Communication to Browse the Student

information from anywhere by using the Smart Devices which are used in
the future

135
 BIBLIOGRAPHY

6.2 BIBLIOGRAPHY

SOFTWARE ENGINEERING
By Roger.S. Pressman

SQL FOR PROFESSIONALS

By Jain

ASP.Net Professional
By Wrox Publications

MSDN 2002

136
By Microsoft

137