Table of Contents

Abstract
INTRODUCTION
System Requirement
Overview of a Software Specification Document (SRS)
Business Requirement Document
System Design
Implementation
Testing
Use case diagram
E-R Diagram
Database
Snapshots
Coding

ABSTRACT
E solution works as single application as client server system as web based
system and as distribution database system. E Solution Is front end on ASP.NET
and Back end on sql server 2008.E solution is web site where register user post
a technical question and get its solution on its register id.Or E solution is a path
where any technical question problem share with many member and who knows
solution of this problem post solution. You will be able to work with remote outlets
and warehouses in united integer even without reliable connection between
them.
Every user name and password must be entered in this dialog box, and then
every user to be allocated with the required Lists and Forms access according to
their job responsibilities.
Once you are familiar with the E solution System and have worked through the
tutorial, you are ready to create your own database and then add your own data
based upon how your organization does its business.

Analysis of system's objectives: - In this phase each objective has been

analyzed, and a planning to implement the system has been made.
Planning to implement the system: - In this phase system has been design to
implement the Inventory Control.
Testing and debugging: - In this phase the whole system has been tested on
personal web server, and debugging has been completed.
Deploying and maintaining the system: - This one is the final phase of Inventory
Control, which has to be implemented.

1. INTRODUCTION
(a) Project introduction:Purpose of this Document:This document contains a description for E-Solution system. This document will
contain the functional requirements of the project and how the developers will
enhance the project to achieve all the objectives. The SRS will serve as a guide
for the client and the developers.

(b) Project Description:E-Solution works as single application as client server system as web based
system and as distribution database system. You will be able to work with remote
outlets and warehouses in united integer even without reliable connection
between them.
Every user name and password must be entered in this dialog box, and then
every user to be allocated with the required Lists and Forms access according to
their job responsibilities.
Once you are familiar with the this System and have worked through the tutorial,
you are ready to create your own database and then add your own data based
upon how your organization does its business.

(c) About Organization:The primary objective of the E-Solution is:

To provide the best education, which will enable young men/women to build
their careers as professional managers & technocrats?

To equip them with up-to-date knowledge to develop managerial skills and

aptitudes, to instill business ethics and with competent performance as
managers & technocrats.

To provide a broader socioeconomic scope against which a particular

managerial problem can be assessed. The emphasis shall be on decisionmaking process with reference to the Indian and International situation.

To development of managerial expertise for implementation of business

aspects.

To introduce basic tools and concepts for analysis and other functional areas
of Question Answring and Knowledge as well to develop special skills and
knowledge aptitude required in global environment

System Requirement
1. SoftwareRequirements

--WindowsXp
--VisualStudio2008
-- VisualStudioDevelopmentServer
--SQLServer2005(Asdatabaseserver)
--Web Browser (Internet explorer )

2. HardwareRequirements

--512MBRAM
--Resolution1024*768(forbettervisualization)

List

of

Software

tools

1)Visual Studio 2008:- This will be used for maintaining the database of our
system.

2)

IE

(Internet

Explorer)/Mozilla:

To

navigate

all

web

pages.

3) Visual Studio Development Server: - This will be used for launching and
running

the

system.

4) C#:- To create dynamic web pages and to enable connectivity with the
database.

Overview of a Software Specification Document (SRS)

1.

INTRODUCTION
States the goals and objectives of the software, describing it in the context of the
computer-based system.
User Requirements :These include the functional requirements of the user. What according to the user should
be the essential features of the project? What facilities and features must be included in
the project for their benefit and what not? Based upon the analysis the following user
requirements can be enlisted:
6

1. Login facility.
2. Download E-books.
4. Question and answring.
5. Rules and regulation.
6. Registration form.

System Requirements:This includes the system hardware and software requirements and other technical
requirements.
A. Other General Requirements:1. A person should be able to click on a button or link to be taken to the specific
application. The first page of the application should provide the user (admin and
employee only) with the options of log-in. Then user is provided with his/her option
page. The page through which the user enter customer details should allow saving of
personal details like name, contact number, address etc. The page for account opening
is then provided and an account number is auto-generated.
2. The Students information saves into the database.
3. The cancel button should take the user back to the home page (first page)

Software Project Constraints

Compatibility
IMS software should run compatibly (i.e. under the same operating
system, database and networking capabilities) with the other
subsystems software it works together with.
It should allow an Administrator to enroll new users and give them
access rights required by their duties.
Reliability and Availability
It should permit 1 hour per day for maintenance and backup
activities with minimal disruption to users.
Any failure should cause no more than 10-minute downtime,
with the average not exceding 2 minutes.

 Backup should spot-tested to ensure they are reliable.

Performance
It should allow up to 10 users to logon simultaneously
and receive an average response time not exceeding 3
seconds.
Parts received should be in the recorded in the system
in no more than 2 hours, with the average under 30
minutes.

2.

INFORMATION DESCRIPTION
Detailed description of the problem the software must
solve
Information content, relationships, flow and structure
Hardware, software and human

interfaces are

described for external system elements and internal

software functione

Business requirement documents

1. SIGN UP IN E-SOLUTION :E-Solution web site provide signup facility for new user and get all information
according to database and store in database.
In signup block user input value likes user name, password,email address,lat
name, first name and contact no. etc
Storage in database table in sign up table according to user value.
And its future use for admin and user self if he wants to change own profile.
In signup block user input value likes user name, password,email address,lat
name, first name and contact no. etc

2. FACILITIES :E solution works as single application as client server system as web based
system and as distribution database system. E Solution Is front end on
ASP.NET and Back end on sql server 2008.E solution is web site where
register user post a technical question and get its solution on its register
id.Or E solution is a path where any technical question problem share with
many member and who knows solution of this problem post solution. You will
be able to work with remote outlets and warehouses in united integer even
without reliable connection between them.
Every user name and password must be entered in this dialog box, and then
every user to be allocated with the required Lists and Forms access according
to their job responsibilities.
Once you are familiar with the E solution System and have worked through
the tutorial, you are ready to create your own database and then add your
own data based upon how your organization does its business.

Analysis of system's objectives: - In this phase each objective has been

analyzed, and a planning to implement the system has been made.
Planning to implement the system: - In this phase system has been design to
implement the Inventory Control.
Testing and debugging: - In this phase the whole system has been tested on
personal web server, and debugging has been completed.
Deploying and maintaining the system: - This one is the final phase of
Inventory Control, which has to be implemented.
E solution site provide facility like if user and member have any problem and
have any query then he ask and update his question and all about answer
gives by experts and multiple answer gives by multiple member and thats not
done all other facility like get any university result and other latest result and
get e-books and any time done question and answering.

Incompleteness
The system extensibility can be enhanced additionally by allowing a participant to
attend only part of the meeting.
It should ideally belong to one of the locations preferred by as many important
participants as possible.

The amount of interaction among participants should be kept minimal.

Ambiguous
An approval should be accurately monitored, especially when it is held virtually.
Here, nomad city will then be important to consider.
Difference between potential requester and approving authority.

Clarification of criteria for expanding date range.

Misclassified

To make them confident about the reliability of the communications.

Physical constraints should not be broken.

Missing

Missing Login and Logout requirements.

Redundancy
Make requester aware of what is going on and Keep participants informed about
status and final outcome.
The five stages in scope management:
Initiation, scope planning, scope definition, scope verification and scope change control.

10

I. Initiation - committing the organization to begin the next phase of the project.
II. Scope Planning - developing a written scope statement as the basis for future project
decisions.
III. Scope Definition - subdividing the major project deliverables into smaller and more
manageable components.
IV. Scope Verification - formalizing acceptance of the project scope.

System Design
The most creative and challenging phase of the system life cycle is system
design the term design describes a final system and the process by
which it is developed is refers to the technical specification that will be
applied in implementing the candidate system. It also includes the
construction of programs and programs testing. The key question here is
how should the problem be solved. The first step is to determined how
the output is to be produced and in what format.
1) Before, starting for actual coding, it is highly important to understand what we are
going to create and what it should look like?
For this purpose Flow Charts, Use Case Diagram, Class Diagram, State Transition
Diagram, etc, were made. It gave an idea of how data and information will flow in the
system and interconnection between web forms, interaction among the actors of the
system.
2) The requirement specifications from first phase are studied in this phase and
system design is prepared.
3) System Design helps in specifying hardware and system requirements and also
helps in defining overall system architecture.
4) The system design specifications serve as input for the next phase of the model.

Implementation:Once the system was tested, the implementation phase started. The term
implementation has different meanings, ranging from the conversion of a basic
application to a complete replacement of a computer system. Implementation is

11

the process of converting a new or a revised system design into an operational

one.
Implementation includes the activities that take place to convert the older system
to the newer one. The new system may be totally new or replacing an existing
system. In either case, proper implementation is essential to provide a reliable
system to meet organizational requirements. System implementation describes
how the different parts of the system are interacting with each other to give us a
feasible software solution.

a. Environment: Project Develop Under Microsoft Environment(Microsoft XP

SP2,MS Visual Studio, MS Sql Server 2005)

b. Coding Style: Two Tier Architecture

c. Coding Techniques: C# using Classes
1) On receiving system design documents, the work is divided in modules/units and
actual coding is started.
a. As, we were a team of four, so, first teams were divided in two, and
further work was divided among each team.
b. Each one designed there part of web forms.
c. Which were later on integrated in next phase. The system is first
developed in small programs called units, which are integrated in the next
phase.
2) Each unit is developed and tested for its functionality; this is referred to as Unit
Testing. Unit testing mainly verifies if the modules/units meet their specifications.

Project Scope:

Login page is provided for the user-admine/everyone.

Then Option page will come once user is logged on.

Account opening page is provided once users details are entered.

12

Users ID are automatically generated.

The login page comes first which take input as username and password.
The username and password is right otherwise it gives error and page is not
executed.

The verification is on the basis of availability of account no and the status of

account with user E-mail address. It means the transaction is performed only
when this data is already in the database.

Users By users we refer to the students who wants to know his account
details according to specific fields.
Administrator - By Administrator we refer to the A-Pro Personnel who
have administrative privileges for the website.

Features
Rich Functionality out of the box

.NET framework provides a rich set of functionality out of the box. It contains
hundreds of classes that provide variety of functionality ready to use in your
applications. This means that as a developer you need not go into low level
details of many operations such as file IO, network communication and so on.

Easy development of web applications

ASP.NET is a technology available on .NET platform for developing dynamic and

data driven web applications. ASP.NET provides an event driven programming
model (similar to Visual Basic 6 that simplify development of web pages (now
called as web forms) with complex user interface. ASP.NET server controls
provide advanced user interface elements (like calendar and grids) that save lot
of coding from programmers side.
13

Security

Windows platform was always criticized for poor security mechanisms. Microsoft
has taken great efforts to make .NET platform safe and secure for enterprise
applications. Features such as type safety, code access security and role-based
authentication make overall application more robust and secure

Testing
Overview:
The aim of testing process is to identify all defects in a software product. Testing
is any activity aimed at evaluating the software for quality results it produces and
the quality of results it can handle. Testing is an operation to detect the
differences between the expected (required) result and the actual result.
Testing a program consists of subjecting the program to a test inputs or test
cases and observing if the program behaves as expected. If the program fails to
behave as expected, then the condition under which failures occurs are noted for
later debugging and correction. There are many stages of testing depending on
the complexity of the software.

Levels of Testing:
The basic levels of testing are:1. Unit Testing.
2. Integration Testing.
3. System Testing
4. Acceptance Testing.

14

1 UNIT TESTING:
Unit testing has been under taken when a module has been coded and
successfully reviewed. Unit testing is the testing of different units or modules of
system in isolation. It is programmers responsibility to think of the advantage of
doing unit testing before integration testing is that it makes debugging easier. If
an error is detected when a module is being tested along with several modules, it
would be difficult to determine which module exactly has an error.
In the current system Inventory Management System, unit testing has been
exclusively done after finishing every module.

2 INTEGRATION TESTING:
Once a program or module has been unit tested, the programmer can then work
with integration it with other programs. The primary objective of integration testing
is to test the module interfaces in order to ensure that there are no errors in the
parameter passing, when one module involves another modules. During
integration testing, different, different modules of the system are integrated in a
planned manner i.e. the order in which they are combined to realize the full
system.

3 SYSTEM TESTING:
System testing is actually a series of different test whose primary purpose is to
exercise the computer based system, all work to verify that system elements
have been properly integrated and performed allocated function.
Its focus is to prove that the completed system does what it should. This test is
conducted in a formal manner. The testers use scenario-based system test
scripts that have predicted outputs. The test results are recorded in structured
test logs. The structured test logs and scripts drive the system testing process.

15

System testing activities are intended to prove that the system meets its
objectives. Testing proves that the system meets its requirements. This is not
entirely true unless one considers acceptance testing as a type of a system
testing because the purpose of acceptance testing is to demonstrate that the
system meets the user requirement. Acceptance testing is validation process.
System testing in the strictest sense is a verification process. Regardless of
whether it represents verification or validation. System testing represents an
external view of the system.
This is true because requirements represents the eventual system users of the
system (an external view). Users do not understand nor do they care about how
the system works as long as it is usable. System testing should be approached
from this perspective.
As far as the proposed Hostel Management System is concerned it meets this
requirement.

4 PERFORMANCE TESTING:
Some of the performance testing done for the proposed system are:1. Stress Testing:- Stress testing is done to evaluate system performance
when it is stressed for short periods of tome. Providing a range of
abnormal and even illegal input condition so as to stress the capability
of the software. Input data volume, input data rate, processing time,
utilization of memory etc are tested beyond the designed capacity.
2. Volume Testing:- This testing is done to check whether the data
structures have been designed successfully for extraordinary situation.

16

System Analysis, System Design which we followed during our project

The System analysis and design are two consecutive steps of system development life
cycle (SDLC). System analysis is the first step of SDLC, defined as a management
technique, which helps us in designing a new system or improving an existing system.
There are four basic element in system analysis:
1. Outputs: To determine the outputs of the system, the objectives or goals of the system
should be defined. This is done by extensive investigation process of user requirements.
2. Inputs: On the basis of outputs of the sytem we can determine its inputs. The input for
the system should be checked for accuracy, timeliness, proper format and economy.
3. Files: Files are used to store data.
4. Process: Process are concerned about conversion of input and files into outputs.
The second step of the SDLC is system design. The primary objectives of the design, is to
deliver the requirements as specified in the feasibility report of the system analysis.
System design involves first locial design and then physical construction of the sytem.
The logical design describes the structure and characteristics of feature, like the outputs,
inputs, files, databases and procedures. The physical construction which follows the
logical design, procedure actural program software, files and a working system.
The system design is an iterative process, which involves following five elements:
1. Output design: The starting point of the design process is to the proper knowledge of
system requirement which will be converted in output.
2. Input design: Once the output requirements have been finalized, the next step is to find
out what data needed to produce those outputs.
3. File design: Input data is stored in files in a logical manner. The designer devise the
techniques of storing and retrieving data from files.
4. Procedure design: This step involves specification of how processing will be
performed.
5. Control design: The control design indicates necessary procedures which will ensure
correctness of processing, accuracy of data, timely output etc.
.
Level 1 DFD for Hostel Management System
Here the two Modules deposit and withdrawal have been shown. These modules will be
further referred in Level 2 DFD for Hostel Management system. The deposit and
withdrawal module take customer ID, A/C no and amount to be add (deposit) or
subtract withdrawals input and shows the updated value of Account to the customer. Now
we show the Level 2 DFD for the Bank Management System.

17

In Level 2 DFD of Hostel Management System. A number of modules have been used to
impose different checks. Besides one CMS base data stores have been used,
Hostal wardens: Which keeps information about all the students in the hostel.

Now we prepare Data Dictionary for the Dataflows and Data stores used in the DFD: A
data dictionary is simplislistically, an alphabetic list of names which are included in the
different models of a system. As well as the name, the dictionary should include an
associated description of the named entity and, if the name represents a composite object
there may be a description of the composition of the information such as the data of
creation, the creator & the representation of the entity may also be included depending on
the type of the model which is being developed.
Test strategy for any one of the software modules: Software testing is one of the most
important phase of software development. It is the kernel of design phase. Once source
code has been generated, software must be tested to uncover and correct as many errors
as possible before delivery to customers. Every time the program is executed customer
test it. Thus the program should be tested for finding and removing all errors before it
gets to the customers.
A strategy for software testing integrates software test case design methods into a well
planned series of steps that results in the successful construction of software.
Following are the characteristics software testing strategy:
(i) Testing begins at the component level and works outward towards integration of the
entire computer based system.
(ii) Different testing techniques are important at different points in time.
(iii) Testing is conducted by the developer of the software and independent test groups.
(iv) Testing and debugging are different activities but debugging must be accommodated
in any testing strategy.
(v) Verification and validation are most important testing strategy. Verification refers to
the set of activities that ensures that software correctly implements a specific function.
Validation refers to a different set of activities that ensures that software that has been
built, is traceable to customer requirement.
Verification: Are we building the product right?
Validation: Are we building the right product?

18

Data Flow Diagram

Faculties
Students

Others
E-Solution
Module

data store

Admin

Admin
data store

19

Use case diagrams

login (from usecase)

Maintain Member Info.

(from usecase)

Admin
(from usecase)

Account Generation (from usecase)

Service Provide System

Maintain Solution Info

(from usecase)

20

Databas
e

21

Database Name: E-Solution

Tables:1. Admin

2.Member Details

22

3.News

4.Post Question

5.Reply

6.Sign Up

23

24

Project
Snap
Shots

(1)

Home Page

25

(2)

Login Page

26

(3)Registration Form

(3)

Member Page

27

(5)Contact us

28

(7)Member HomePage

(6)Member Post Page

29

(7)Admin Login

(8)Admin HomePage

(9)Admin News Block

(10)Admin Member Page

30

31

Coding

32

<%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs"

Inherits="MasterPage" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

1.0

Transitional//EN"

<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
<script src="jquery-1.2.6.min.js" type="text/javascript"></script>
<script type="text/javascript">
/***
Simple jQuery Slideshow Script
Released by Jon Raasch (jonraasch.com) under FreeBSD license: free to use or
modify, not responsible for anything, etc. Please link out to me if you like it :)
***/
function slideSwitch() {
var $active = $('#slideshow IMG.active');
if ($active.length == 0) $active = $('#slideshow IMG:last');
// use this to pull the images in the order they appear in the markup
var $next = $active.next().length ? $active.next()
: $('#slideshow IMG:first');
// uncomment the 3 lines below to pull the images in random order
// var $sibs = $active.siblings();
// var rndNum = Math.floor(Math.random() * $sibs.length );
// var $next = $( $sibs[ rndNum ] );
$active.addClass('last-active');
$next.css({ opacity: 0.0 })
.addClass('active')
.animate({ opacity: 1.0 }, 1000, function () {
$active.removeClass('active last-active');
});
}
$(function () {
setInterval("slideSwitch()", 5000);
});
</script>
<style type="text/css">
/*** set the width and height to match your images **/
#slideshow {
position: relative;
height: 190px;
}
#slideshow IMG {
position:absolute;

33

top:-1px;
left:-4px;
z-index:8;
opacity:0.0;
width: 1000px;
}
#slideshow IMG.active {
z-index:10;
opacity:1.0;
width: 1000px;
}
#slideshow IMG.last-active {
z-index:9;
}
</style>
<asp:ContentPlaceHolder id="head" runat="server">
</asp:ContentPlaceHolder>
<style type="text/css">
.contener
{
width: 1000px;
height: auto;
margin-right: auto;
margin-left: auto;
}
.left
{
border: thin solid #6666FF;
width: 150px;
float: left;
list-style-type: none;
}
.middle
{
width: 500px;
float: left;
}
.right
{
width: 150px;
float: right;
}
.header
{
width: 800px;
height: 200px;
}
.footer
{
width: 800px;
height: 50px;
clear: both;
}

34

body
{
background-image: url('/Final project/images/bg/das.jpg');
}
.menu
{
width: 150px;
height: auto;
list-style-type: none;
background-color: #FFFFFF;
margin: 0px;
padding: 0px;
}
.menu li
{
width: 100%;
height: 30px;
color: #000000;
}
.menu a
{
text-decoration: none;
color: #CCCCCC;
}
.menu a:hover
{
text-decoration: underline;
}
.menu li:hover
{
background-color: #333300;
color: #000000;
}
.style1
{
color: #000000;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<div class="contener">
<div class="header">
<div id="slideshow">
<img src="images/0.jpg" id="DataList4_img1_0" height="180"
alt="Slideshow Image 1" class="active" />
<img src="images/1.jpg" id="DataList4_img1_1" width="800" height="180"
alt="Slideshow Image 1" />
<img src="images/11.jpg" id="Img1" height="180" alt="Slideshow Image 1"
class="body" />
<img src="images/3.jpg" id="Img2" width="800" height="180" alt="Slideshow
Image 1" />
<img src="images/4.jpg" id="Img3" width="800" height="180" alt="Slideshow
Image 1" />
<img src="images/5.jpg" id="Img4" width="800" height="180" alt="Slideshow
Image 1" />

35

<img src="images/6.jpg" id="Img5" width="800" height="180" alt="Slideshow

Image 1" />
<img src="images/7.jpg" id="Img6" width="800" height="180" alt="Slideshow
Image 1" />
<img src="images/9.jpg" id="Img7" width="800" height="180" alt="Slideshow
Image 1" />
<img src="images/banner.jpg" id="Img8" width="800" height="180"
alt="Slideshow Image 1" />
<img src="images/i1.jpg" id="Img9" width="800" height="180" alt="Slideshow
Image 1" />
<img src="images/images7.jpg" id="Img10" width="800" height="180"
alt="Slideshow Image 1" />
<img src="images/images.jpg" id="Img11" width="800" height="180"
alt="Slideshow Image 1" />
</div>
<div class="contener">
<div class="left">
<ul class="menu">
<li><a href="Default.aspx"><span class="style1">Home</span></a></li>
<li><a href="aboutus.aspx"><span class="style1">About
Us</span></a></li>
<li><a href="Member%20list.aspx"><span class="style1">Member
List</span></a></li>
<li><a href="Login.aspx"><span class="style1">Login</span></a></li>
<li><a href="sign%20up.aspx"><span class="style1">Sign
Up</span></a></li>
<li><a href="contact%20us.aspx"><span class="style1">Contact
Us</span></a></li>
<li><a href="D.aspx"><span class="style1">Q</span></a></li>
<li>Help</li>
</ul>
</div>
<div class="middle">
<asp:ContentPlaceHolder ID="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>
</div>
<div class="right">
<a href="Login.aspx">
<img alt="" src="images/qsubm.jpg"
style="height: 75px; border-width: 0px; margin-left: 0px;" />
</a>
<a href="D.aspx">
<img alt="" src="images/do-you-know-that-pack-of-250.jpg"
style="height: 100px; width: 149px; border-width: 0px" /></a>
<p>
<asp:Calendar ID="Calendar1" runat="server" Height="182px"
style="margin-left: 0px"></asp:Calendar>
</p>
</div>
</div>
<div class="footer">
copyright
</div>
</div>
</form>
</body>

36

</html>

ADMIN HOME
<%@ Page Title="" Language="C#" MasterPageFile="~/Admin/MasterPage.master"
AutoEventWireup="true" CodeFile="Adhome.aspx.cs" Inherits="Admin_Default2" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
</asp:Content>
<asp:Content
ID="Content2"
ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<p>
welcome<asp:Label ID="Label1" runat="server" Text="Label"></asp:Label>
</p>
</asp:Content>
<%@
Page
Title=""
Language="C#"
MasterPageFile="~/MasterPage.master"
AutoEventWireup="true" CodeFile="sign up.aspx.cs" Inherits="sign_up" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
<title></title>
<link rel="stylesheet" type="text/css" media="all" href="jsDatePick_ltr.min.css" />
<script type="text/javascript" src="jquery.1.4.2.js"></script>
<script type="text/javascript" src="jsDatePick.jquery.min.1.3.js"></script>
<script type="text/javascript">
window.onload = function(){
new JsDatePick({
useMode:2,
target:"inputField",
dateFormat:"%d-%M-%Y"
});
};
</script>
<style type="text/css">
.style1
{
width: 400px;
}
.style2
{
height: 32px;
}
.textbox
{
border-color: #999999;
padding: 5px 10px 5px 10px;
border-style: solid;
border-radius: 25px;
-moz-border-radius: 25px;
}
#inputField
{
width: 143px;
}

37

</style>
</asp:Content>
<asp:Content
ID="Content2"
ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<asp:Image ID="Image1" runat="server" ImageUrl="~/images/register.gif" />
<br />
<br />
<table class="style1" align="center">
<tr>
<td>
First Name</td>
<td>
<asp:TextBox ID="fname" runat="server" CssClass="textbox"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server"
ControlToValidate="fname" ErrorMessage="First Name Required"
ForeColor="Red"
SetFocusOnError="True"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Last Name</td>
<td>
<asp:TextBox ID="lname" runat="server" CssClass="textbox"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator3" runat="server"
ControlToValidate="lname" ErrorMessage="Required Last Name"
ForeColor="Red"
SetFocusOnError="True"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
User Name</td>
<td>
<asp:TextBox
ID="txtusername"
runat="server"
CssClass="textbox"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="txtusername" ErrorMessage="User Name Required"
ForeColor="Red" SetFocusOnError="True"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Date of&nbsp; Birth</td>
<td>
<input type="text" size="23" id="inputField" class="textbox" />
</td>
</tr>
<tr>
<td class="style2">
Gender</td>
<td class="style2">
<asp:DropDownList ID="DropDownList1" runat="server" Height="34px"
Width="137px"
style="margin-bottom: 0px" CssClass="textbox">
<asp:ListItem>I AM...</asp:ListItem>
<asp:ListItem>Male</asp:ListItem>

38

<asp:ListItem>Female</asp:ListItem>
<asp:ListItem>Other</asp:ListItem>
<asp:ListItem></asp:ListItem>
</asp:DropDownList>
</td>
</tr>
<tr>
<td>
Mobile No.</td>
<td>
<asp:TextBox ID="mobile" runat="server" CssClass="textbox"></asp:TextBox>
<asp:RegularExpressionValidator ID="RegularExpressionValidator1"
runat="server"
ControlToValidate="mobile" ErrorMessage="Mobile Should be 10 digit"
ForeColor="Red" SetFocusOnError="True"
ValidationExpression="\d{10}"></asp:RegularExpressionValidator>
</td>
</tr>
<tr>
<td>
&nbsp;E-mail address</td>
<td>
<asp:TextBox runat="server" ID="txtEmail" CssClass="textbox"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator4" runat="server"
ControlToValidate="txtEmail" ErrorMessage="Email Required"
ForeColor="Red"></asp:RequiredFieldValidator>
<br />
<asp:RegularExpressionValidator ID="RegularExpressionValidator2"
runat="server"
ControlToValidate="txtEmail" ErrorMessage="Invalid Email address"
ForeColor="Red"
ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+
([-.]\w+)*"></asp:RegularExpressionValidator>
<br />
</td>
</tr>
<tr>
<td align="center" colspan="2">
&nbsp;<asp:Button ID="Button1" runat="server" Text="Submit" Width="142px"
onclick="Button1_Click" />
&nbsp;<br />
<asp:ValidationSummary ID="ValidationSummary1" runat="server"
ShowMessageBox="True" ShowSummary="False" />
</td>
</tr>
</table>
<p>
</p>
</asp:Content>
<%@ Page Title="" Language="C#" MasterPageFile="~/member/Member.master"
AutoEventWireup="true" CodeFile="mhome.aspx.cs" Inherits="member_mhome" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
</asp:Content>
<asp:Content ID="Content2" runat="server"
contentplaceholderid="ContentPlaceHolder1">

39

<p>
Welcome&nbsp;
<asp:Label ID="Label1" runat="server" Text="Label"></asp:Label>
<asp:Image ID="Image1" runat="server" Height="150px" Width="100px" />
</p>
<p>
&nbsp;Letest update
</p>
<p>
&nbsp;</p>
<p>
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$ ConnectionStrings:ConnectionString %>"
SelectCommand="SELECT [Question], [DateOfPost] FROM [PostQuestion]">
</asp:SqlDataSource>
</p>
<p>
&nbsp;</p>
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
BackColor="White" BorderColor="White" BorderStyle="Ridge" BorderWidth="2px"
CellPadding="3" CellSpacing="1" DataSourceID="SqlDataSource1"
GridLines="None">
<Columns>
<asp:BoundField DataField="Question" HeaderText="Question"
SortExpression="Question" />
<asp:BoundField DataField="DateOfPost" HeaderText="DateOfPost"
SortExpression="DateOfPost" />
</Columns>
<FooterStyle BackColor="#C6C3C6" ForeColor="Black" />
<HeaderStyle BackColor="#4A3C8C" Font-Bold="True" ForeColor="#E7E7FF" />
<PagerStyle BackColor="#C6C3C6" ForeColor="Black" HorizontalAlign="Right" />
<RowStyle BackColor="#DEDFDE" ForeColor="Black" />
<SelectedRowStyle BackColor="#9471DE" Font-Bold="True" ForeColor="White"
/>
<SortedAscendingCellStyle BackColor="#F1F1F1" />
<SortedAscendingHeaderStyle BackColor="#594B9C" />
<SortedDescendingCellStyle BackColor="#CAC9C9" />
<SortedDescendingHeaderStyle BackColor="#33276A" />
</asp:GridView>
<p>
&nbsp;</p>
<p>
&nbsp;</p>
<p>
&nbsp;</p>
<p>
&nbsp;</p>
<p>
&nbsp;</p>
<p>
&nbsp;</p>
<p>
&nbsp;</p>
<p>
&nbsp;</p>

40

<p>
&nbsp;</p>
</asp:Content>

<%@ Page Title="" Language="C#" MasterPageFile="~/member/Member.master"

AutoEventWireup="true" CodeFile="msgpost.aspx.cs" Inherits="member_msgpost" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
</asp:Content>
<asp:Content
ID="Content2"
ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<p>
Post your question at here :-</p>
<p><table class="style1">
<tr>
<td>

<asp:TextBox ID="TxtQuestion" runat="server"

TextMode="MultiLine"></asp:TextBox>
</td>
</tr>
<tr>
<td align="justify" colspan="2">
<asp:Button ID="btnpost" runat="server" onclick="btnpost_Click" Text="post"
/>
</td>
</tr>
</table>
<br />
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
onrowcancelingedit="GridView1_RowCancelingEdit"
onrowdeleting="GridView1_RowDeleting" onrowediting="GridView1_RowEditing"
onrowupdating="GridView1_RowUpdating">
<Columns>
<asp:BoundField DataField="Questionid" HeaderText="QuestionId"
ReadOnly="True" />
<asp:BoundField DataField="Question" HeaderText="Question" />

<asp:CommandField ShowEditButton="True" />

<asp:CommandField ShowDeleteButton="True" />

</Columns>
</asp:GridView>
<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</p>
<p>
<br />
</p>
</asp:Content>

41

Conclusio
n
Conclusion

42

We are glad to say that our project E-SOLUTION is a successful project. A

project has no end because we can work for a long time for making it more
versatile however have tried to do our best in this short period of time.
From this project we have learned a lot. It was a great
experience for us. At last we want to thank all the our project leaders staff
members, teachers, friends, and every one who helped and supported us in
completing this project.
By the Gods grace we have completed it and compiled it
successfully.

List of abbreviations
1.DFD
DATA FLOW DIAGRAM
2.ERD
ENTITY RELATIONSHIP DIAGRAM
3.SQLServer
STRUCTURED QUERY LANGUAGE
4.Visual Studio.Net
5.C#

REFERENCES
1.www.google.com
2.www.asp.net
3.www.Books of SQL
4.www.w3school.com

43

44