Intranet Mailing in Virtual Office

SESSION- 2017-18
PROJECT REPORT
ON
INTRANET MAILING IN VIRTUAL OFFICE
BY
Faiz khan(1504031)
Under Guidance of
Dr. Mazhar Khaliq Mr. Chandra Bhushan Verma

Internal Supervisor External Supervisor
(Head of Department Project Manager
Computer Science/ (Analyze Infotech)
Information Technology)
In Partial Fulfillment of the requirements for the award of the degree

Bachelor of Computer Science (BCA)
AKNOWLEDGEMENT
I would like to thank my project guide Dr. Mazhar Khaliq for his valuable
guidance and advice inspired us greatly to work in this project. His willingness to
motivate us contributed tremendously to our project.
Besides, I would like to thank the authority of “ Khwaja Moinuddin Chishti

Urdu, Arabi-Farsi University,Lucknow” for providing me with a good
environment and facilities to complete this project.
In addition WE express gratitude to all the faculty member for the guidance and
support rendered to us throughout my academic career as a student in the
University.
Also I would like to take the opportunity to thank my family members for giving
me full support, without whose help the completion of this project report was not
possible.
FAIZ KHAN
(1504031)
INDEX
1. Title of the Project
2. Introduction
3. Modules
4. Project scope
5. Objective
6. Literature survey
7. Requirement Analysis
8. Introduction Of ASP.Net
9. Introduction of Microsoft Visual Studio
10. Introduction of Microsoft SQL Server
11. Introduction of HTML
12. Introduction of C#
13. Preliminary Investigation
14. Software Engineering Paradigm
15. S/W & H/W Requirement
16. System Design
17. 0 level D.F.D
18. 1 level D.F.D
19. E-R Diagram

20. Data Structure
21. Table of Information
22. Interface Design
23. Coding
24. Testing
25. GANT chart
26. PERT chart
27. Error Handling
28. Validation Check
29. Future scope
30. Bibliography
Project
On
INTRANET MAILING IN VIRTUAL
OFFICE
INTRODUCTION
The ‘VIRTUAL OFFICE’ is an Enterprise Intranet Application that automates and
improves procedures within organizations. It is a useful technology for delineating
the steps that must be taken, the dependencies that must be enforced, and the
approvals that must be obtained during the completion of projects. It keeps track
the information about the employees and also it keeps track of the task assigned to
each employee. The super users of the system are the ‘ADMIN’ and the
‘EMPLOYEES’ of the different departments allocated by the admin in an
organization or company.
The ‘VIRTUAL OFFICE’ mainly consists of eight modules Administrative

module, Login module, Bulletin board, E-forum, Task management module,
Project management module, Address book, Documents library and lastly Logout.
In the administrative module administrator the admin may be the owner of the site,
he can create a new employee and can assign a password to them. Login module
consists of Login Registration, Changing password, Password Reminder. Where
actually a new user can register and the existing user can login with user id and
password.
E-forum is discussion software allows people from within a corporation to

exchange work and ideas. Included in the software are links to other intranet
resources, so that from within a discussion, people can link out to a Web page on
the Internet or intranet, or can even link into intranet databases.
Project management module gives employees task status reports. We can

assign a task to an employee, can view status of all tasks and also can view today’s
report of all tasks. Address book module mainly maintains information about all
employees addresses where we can view addresses of all the employees. Document
library module contains the list of documents available in document library and it
also allows posting documents.
Project Modules
MODULES
The Proposed system has following main modules-
Module Description
The ‘VIRTUAL OFFICE’ mainly consists of eight modules
 Administrative Module
 Login module
 Bulletin board
 E-forum
 Project management module
 Address book
 Documents library and lastly Logout
Administrative Module
In the administrative module administrator the admin may be the owner of the site,
he can create a new employee and can assign a password to them.
Login module
Login module consists of Login Registration, Changing password, Password

Reminder. Where actually a new user can register and the existing user can login
with user id and password.
Bulletin Board
The Bulletin board is an important module where all the employees can see the
articles which were putted on notice board. Not only they can view they can also
post their own articles. It just acts like notice board where one can get all the
information about the activities which were going on in all departments. A bulletin
board (pin board, pin board or notice board in British English) is a place where
people can leave public messages, for example, to advertise things to buy or sell,
announce events, or provide information. Bulletin boards are often made of a
material such as cork to facilitate addition and removal of messages or it can be
placed on the computer so people can leave and erase messages for other people to
read and see.
Bulletin boards are particularly prevalent at universities. Many sport dozens, if not
hundreds or thousands of public bulletin boards, used for everything from
advertisements by extracurricular groups and local shops to official notices.
Dormitory corridors, well-trafficked hallways, lobbies, and freestanding kiosks
often have cork boards attached to facilitate the posting of notices. At some
universities, lampposts, bollards, trees, and walls often become impromptu
posturing sites in areas where official boards are sparse in number.
E-Forum
E-forum is discussion software allows people from within a corporation to

exchange work and ideas. Included in the software are links to other intranet
resources, so that from within a discussion, people can link out to a Web page on
the Internet or intranet, or can even link into intranet databases. Forum software
packages are widely available on the Internet. One significant difference between
forums and electronic mailing lists is that mailing lists automatically deliver new
messages to the subscriber, while forums require the member to visit the website
and check for new posts. Because members may miss replies in threads they are
interested in, many modern forums offer an "e-mail notification" feature, whereby
members can choose to be notified of new posts in a thread, and web feeds that
allow members to see a summary of the new posts using aggregator software. The
main difference between newsgroups and forums is that additional software, a
newsreader, is required to participate in newsgroups. Visiting and participating in
forums normally requires no additional software beyond the web browser.
Project Management Module
Project management module gives employees task status reports. We can assign a
task to an employee, can view status of all tasks and also can view today’s report of
all tasks. We can allocate the project tasks to various employees in the office.
Project manager can view the employees work details like how many hours have
been completed.
Documents Library
Document library module contains the list of documents available in document

library and it also allows posting documents. Fields to fill out when uploading a
document To upload a document, click the "Upload Document" link on any Virtual
Office web
Page. Fill out the fields as completely as possible. Remember, the information you
Provide about the document is used to allow other users (or even yourself) to
search For and find the document later:
1. Document Title - a brief document name.
2. Document Description - a brief description of the contents of the document.
3. Owner - the user who is currently uploading this document. This field is filled
in automatically by the Virtual Office, which recognizes each user? NOTE: If this
User is not you, you should log out and log in again as yourself.
4. Category - the document category that best fits the document you are uploading.
Document categories are used simply to facilitate searching by dividing the

Documents contained in the Virtual Office into logical groups. Only the Virtual
Office administrator can add or edit the list of document categories.
5. File - click the button to locate the file on your local computer that you wish to
Upload. Filenames should always include a proper 3-letter extension, or users will
have problems trying to download the file. Rename suspicious files before
uploading them to the Virtual Office.
6. Who may view (download) this file - the list of groups you would like to have
access to this file. By default, a document will be accessible to all groups, meaning
that any other user can download the file. You can restrict download of the file to
one or more groups by selecting only those groups from the list. Select and
unselect multiple groups by holding down the "Control" key as you click on each
selection.
7. Who may replace or delete this file - the list of groups you would like to have
the ability to edit or replace this file. By default, a document will be accessible to
"(all groups)", meaning that any other user can edit the file. You can restrict edit
ability of the file to one or more groups by selecting only those groups from the
list. Select and unselect multiple groups by holding down the "Control" key as you
click on each
Project Scope
PROJECT SCOPE
VIRTUAL OFFICE is an Enterprise Intranet Application that automates and

improves procedures within organizations. It is a useful technology for delineating
the steps that must be taken, the dependencies that must be enforced, and the
approvals that must be obtained during the completion of projects.
It keeps track the information about the employees and also it keeps track of the
task assigned to each employee. The super users of the system are the ‘ADMIN’
and the ‘EMPLOYEES’ of the different departments allocated by the admin in an
organization or company.
Objective
OBJECTIVE
Objective of the project is to develop an Intra net Mailing application that can
facilitate a communication system between members of a department. Members
can group chat between them and send email with attachment that can be
downloaded. The Application starts with a login page, which is an html file where
the user can
Login to the company’s website where he can access his account details, he can do
his
Work of doing project tasks there, where he can have an access to the company’s
Database with some constraints basing on his designation.
There is link in the page for the Registration of New user and another link for the
forget password for the employees who have forgot their password. After entering
the user details there is an Authentication of the user can be done using login page.
After the login session has been completed he can access to the home page where
all the tasks regarding the employees like view task status, project status and
Bulletin board, E-forum. After doing his work the logout details of the employee
will be stored in the database where we can access those details for further use.
Administration
Administration processes are simplified allowing more time for management of
resources. This project information will assist management in ensuring that
projects underway within the organization are strategically aligned to the business
and that the important projects are receiving the priority required. It also allows
management to check that the project is being managed effectively.There are many
benefits for an organization that opts to follow a standardized Process or method
when investigating, initiating and managing projects. Some of these benefits are:
• It provides a consistent approach to projects in an organization
• The project success rate is increased, ultimately saving costs
• It raises the skill of project managers in the organization
• A common knowledge base is created reducing project risks.
User role
 Employee can login with his id and password.

 He can view his details and can modify if any changes needed. This is called
as “Employee Details”
 He can view the “Documents” which are needed for his project.
 He can view the “Announcements” which are given by the Administrator.
 If he has any problem, he can create a “Forum” which can solve by the other
employees. If he know he can also give solution to the others problem in
Forum.
 He must update the current “Status” of the project and modifications done
on that day.
The primary objective of the virtual office is to fully automate the conventional
office. Connecting Employees to the company site through online, the secondary
objectives (and benefits) are as follows
 Seeking a low-risk alternative to renting a conventional office;

 Testing a new product or service idea;
 Downsizing from a conventional office;
 Migrating from using post-office box;
 Seeking to establish a business presence in the provider's country or city;
 Seeking a business address within an expensive location, for corporate
image purpose;
 Seeking a business address as its registered business address for complying
to government regulation;
 Seeking supportive business services such as answering services;
 Seeking a proxy for collection of mails and parcels
Project specification
The Portal Administrator role would typically be allocated to an individual

working in the project office. If your organization does not have a project office, it
should be someone who is involved in the overall prioritization, administration and
management of projects and who has authority in these areas.
Virtual office contains a documentation repository per project and a general

repository of project management templates that can be used by the project
managers and team members. The repository enables all team members to upload
specific documentation relating to the project i.e. project plans, minutes of
meetings, specification documentation, training documentation, agreements with
suppliers etc.
This facility enables the easy sharing of documentation by team members and also
assists in ensuring that the latest version is always centrally available to the team
members. It avoids the unnecessary emailing of large documents to several team
members and the risk that documentation could be mislaid. Up-to-date, relevant
documentation is a critical requirement for a successful project.
Literature Survey
LITERATURE SURVEY
The Virtual office is being character to decrease the wastage of time for the
employee. Employee can interact through online for doing his regular works
which will be done at regular conventional office.
Today’s world is computer world because most of work is doing with the help of
computer. Dependency on computer is behind the few reasons. We cannot easily
manage to store large number of data or information single handily. If we will be
need some information or data in urgency then we cannot manage in manually
these works are very difficult if we cannot use computer.
The cost of using project portal is based on the number of users requiring access to
the portal with annual and monthly payment options available.
Costs are also dependant on:
• Implementation assistance required
• Amount of disk space required
• System administration services
• Hosting requirements (on-site hosting is available)
• Customization requirements
• Support requirements
This project is started towards systematically automating all the work that is done
manually at present. Their aim is to focus following aspects:
 The main objective is to automate non computer environment

 To save manpower.
 It will speed the processing of data and transaction.
 It will provide all the error reporting and handling features, so that the user is
warned and made aware of any foreseen errors. Thus it will reduce the error
rate.
 It will provide various ways through which we generate various types of
report.
 It will provide best security features such as provisions of passwords.
Requirement
Analysis
Requirement Analysis
Requirements analysis in systems engineering and software engineering,
encompasses those tasks that go into determining the needs or conditions to meet
for a new or altered product or project, taking account of the possibly
conflicting requirements of the various stakeholders, analyzing, documenting,
validating and managing software or system requirements. Requirements analysis
is critical to the success of a systems or software project. The requirements should
be documented, actionable, measurable, testable, traceable, related to identified
business needs or opportunities, and defined to a level of detail sufficient for
system design.
Conceptually, requirements analysis includes three types of activities
 Eliciting requirements :(e.g. the project charter or definition), business process

documentation, and stakeholder interviews. This is sometimes also called
requirements gathering.
 Analyzing requirements: determining whether the stated requirements are clear,
complete, consistent and unambiguous, and resolving any apparent conflicts.
 Recording requirements: Requirements may be documented in various forms,

usually including a summary list and may include natural-language
documents, use cases, user stories, or process specifications.
Requirements analysis can be a long and tiring process during which many delicate
psychological skills are involved. New systems change the environment and
relationships between people, so it is important to identify all the stakeholders, take
into account all their needs and ensure they understand the implications of the new
systems. Analysts can employ several techniques to elicit the requirements from
the customer. These may include the development of scenarios (represented as user
stories in agile methods), the identification of use cases, the use of workplace
observation or ethnography, holding interviews, or focus groups (more aptly
named in this context as requirements workshops, or requirements review sessions)
and creating requirements lists. Prototyping may be used to develop an example
system that can be demonstrated to stakeholders. Where necessary, the analyst will
employ a combination of these methods to establish the exact requirements of the
stakeholders, so that a system that meets the business needs is produced.
Requirements quality can be improved through these and other methods
 Visualization. Using tools that promote better understanding of the desired end-
product such as visualization and simulation.
 Consistent use of templates. Producing a consistent set of models and templates
to document the requirements.
 Documenting dependencies. Documenting dependencies and interrelationships

among requirements, as well as any assumptions and congregations.
As the existing system increases the paper work and record maintenance tedious
there is a need of new system which makes the record maintenance easy that is the
common requirement the college attendance management system. So the
completion of this project can successfully eliminate the existing problems with the
present system.
SYSTEM ARCHITECTURE
The application will follow three-tier architecture. In three-tier architecture

application will run the traditional client/server model but from the web server.
The client only displays the GUI and data but has no part in producing results.
Three-tier architecture will contain the following tiers
Client/Presentation Tier: This tier includes all the HTML content or forms to be
displayed on the client browser. It is the form which provides the user interface to
end user. Programmer uses this tier to get or set the data back and forth.
Business Logic Layer: In the Business logic tier, the actual processing of the data
and the logic behind the implementation of the application will be present. This tier
can contain a class, which can be used to write the functions, and also works as a
mediator between the presentation tier and data tiers.
Data Tier: Data Tier contains methods and classes that deal with passing and
storing data to the data Storage Layer. Queries or stored procedures are used to
access the data from the database or to perform any operation to the database. It
stores the data passed by the presentation tier.
DEFINATIONS,ACRONYMS & ABBREVATIONS

 HTML: Hypertext Markup Language is a markup language used to
design static web pages.
 Asp: Active server pages is used to develop web application
 IIS: Internet Information Service is a web server to run web application
 VS :Visual Studio is application where we can develop application by

using this IDE
 HTTP: Hypertext Transfer Protocol is a transaction oriented client/server

protocol between web browser & a Web Server.
 HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure

socket layer).
 TCP/IP: Transmission Control Protocol/Internet Ptotocol
 Control Protocol/Internet Protocol, the suite of communication protocols

used to connect hosts on the Internet. TCP/IP uses several protocols, the
two main ones being TCP and IP.
TECHNOLOGIES
• .Net Framework: Application Architecture
• SQL server: Database
• Visual Studio 2012: Development Tool
• IIS: Web Server
• MS Visio: Design Too

Preliminary
Investigation
Preliminary Investigation
If the project is approved for preliminary investigation, an analyst from the IT
department is assigned to perform preliminary investigation. The analyst might be
part of the organization or from a contracted software development company. His
or her purpose is to identify clearly the nature and scope of the problems,
opportunities of improvement, and define specific solutions.Plagued by a scarcity
of resources and difficult delivery dates. It is both necessary and prudent to
evaluate the feasibility of the project at the earliest possible time. Months or years
of effort, Money loss and untold professional embarrassment can be averted I few
better understand the project at its study time. This type of study determines if an
application can and should be developed. Once it has been determining that,
application is feasible. After that analyst can go ahead and prepares the project
specification, which finalizes project requirements. Feasibility studies are
undertaken within tight time constraints. The developed system is started after
considering the main three types of feasibilities that are discussed below:-
Technical Feasibility As we know the technical feasibility is concerned with

specifying equipment and software that will successfully satisfy the user
requirement. The technical needs of the system may vary considerably, but might
include:
Facility to produce outputs of advertisements, shopping and mailing in the given

time for ease of use.
Response time under certain condition is minimal.
Ability to process a certain volume of transaction at a particular speed.

Facility to communicate data to distinct location.
In examining the technical feasibility, configuration of the system is given more

importance than the actual make of hardware. The configuration should give the
complete picture about the system’s requirements- how many workstations are
required, how these units are interconnected so that they could operate and
communicate smoothly.
Economical Feasibility: Economic analysis is the most frequently used

technique for evaluating the effectiveness of the proposed system. More commonly
known as cost/benefits analysis, the procedure is to determine the benefits and
savings that are expected from the purposed system and compared with costs. If
benefits outweigh cost, a decision is taken to design and implement the system.
Otherwise, further justification or alternative of the proposed system will have to
be made if it has a chance of being approved. This is an ongoing effort that
improves in accuracy at each phase of the system life cycle. The analysis part also
clears the doubt of economic problems which could be possible in developing the
system. As already mentioned that the company has to just pay the developed
software cost and not other investment is needed at the time of implementation of
the new system as the preliminary requirements already exist in the company.
Operational Feasibility: Proposed projects are beneficial only if they can be

turned into information system that will meet the financial management
requirements of the business/organization. This test of feasibility asks if the system
will work when it developed and installed. Are there major barriers to
implementation?
Some of the important questions that are useful to test the operational feasibility of
a project are given below:
Is there sufficient support for the project from the implementation? From user? If
the present system is well liked and used to the extent that persons will not be able
to see reasons for change, there may be resistance.
Are current business methods acceptable to the user? If they are not, user may
welcome a change that will bring about a more operational and useful system
Have the user been involved in the planning and development of the project? If
they are involved at the earliest stage of project development, the chances of
resistance can be possibly reduced.
Will the proposed system cause harm? Will it produce poorer result in any case or
area?
Will the performance of staff member fall down after implementation? Issue that
appears to be quite minor at the early stage can grow into major problem after
implementation
Therefore, it is always advisable to consider operational aspects carefully.
The system is developed keeping in mind that it should be user friendly and easy to
operate hence the system is operational feasible.
INTRODUCTION OF
ASP.NET
ASP.NET
ASP.NET is an open-source[2] server-side web application framework designed
for web development to produce dynamic web pages. It was developed
by Microsoft to allow programmers to build dynamic web sites, web applications
and web services.
It was first released in January 2002 with version 1.0 of the .NET Framework, and
is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is
built on the Common Language Runtime (CLR), allowing programmers to write
ASP.NET code using any supported .NET language. The
ASP.NET SOAP extension framework allows ASP.NET components to process
SOAP messages.
ASP.NET's successor is ASP.NET Core. It is a re-implementation of ASP.NET as a
modular web framework, together with other frameworks like Entity Framework.
The new framework uses the new open-source .NET Compiler
Platform (codename "Roslyn") and is cross platform. ASP.NET MVC, ASP.NET
Web API, and ASP.NET Web Pages (a platform using only Razor pages) have
merged into a unified MVC 6.[3]
ASP.NET is a web development platform, which provides a programming

model, a comprehensive software infrastructure and various services required to
build up robust web applications for PC as well as mobile devices. ASP.NET works
on top of the HTTP protocol, and uses the HTTP commands and policies to set a
browser-to-server bilateral communication and cooperation. ASP.NET is a part of
Microsoft .Net platform. ASP.NET applications are compiled codes, written using
the extensible and reusable components or objects present in .Net framework.
These codes can use the entire hierarchy of classes in .Net framework.
ASP.NET application codes can be written in any of the following languages:

 C#
 Visual Basic.Net
 Jscript
 J#
Introduction Of
Microsoft
Visual Studio
Microsoft Visual Studio
Microsoft Visual Studio is an integrated development environment(IDE)
from Microsoft. It is used to develop computer programs, as well as web sites, web
apps, web services and mobile apps. Visual Studio uses Microsoft software
development platforms such as Windows API, Windows Forms, Windows
Presentation Foundation, Windows Store and Microsoft Silver light. It can produce
both native code and managed code.
Visual Studio includes a code editor supporting IntelliSense (the code

completion component) as well as code refactoring. The integrated debugger works
both as a source-level debugger and a machine-level debugger. Other built-in tools
include a code profiler, forms designer for building GUI applications, web
designer, class designer, and database schema designer. It accepts plug-ins that
enhance the functionality at almost every level—including adding support
for source control systems (like Subversion) and adding new toolsets like editors
and visual designers for domain-specific languages or toolsets for other aspects of
the software development lifecycle (like the Team Foundation Server client: Team
Explorer).
Visual Studio supports 36 different programming languages and allows the code
editor and debugger to support (to varying degrees) nearly any programming
language, provided a language-specific service exists. Built-in languages
include C,[6] C++, C++/CLI, Visual Basic .NET, C#, F#,
[7]
JavaScript, TypeScript, XML, XSLT, HTML and CSS. Support for other
languages such as Python,[8] Ruby, Node.js, and among others is available
via plug-ins. Java (and J#) were supported in the past.
The most basic edition of Visual Studio, the Community edition, is available free
of charge.
Introduction Of
Microsoft
SQL Server
Microsoft SQL Server
Microsoft SQL Server is a relational database management system developed

by Microsoft. As a database server, it is a software product with the primary
function of storing and retrieving data as requested by other software applications
—which may run either on the same computer or on another computer across a
network (including the Internet).
Microsoft markets at least a dozen different editions of Microsoft SQL Server,

aimed at different audiences and for workloads ranging from small single-machine
applications to large Internet-facing applications with many concurrent users.
Introduction of
HTML
HTML
Hypertext Markup Language (HTML) is the standard markup language for
creating web pages and web applications. With Cascading Style Sheets (CSS) and
JavaScript it forms a triad of cornerstone technologies for the World Wide Web.
Web browsers receive HTML documents from a web server or from local storage
and render them into multimedia web pages. HTML describes the structure of a
web page semantically and originally included cues for the appearance of the
document. HTML can embed programs written in a scripting language such as
JavaScript which affect the behavior and content of web pages. Inclusion of CSS
defines the look and layout of content. The World Wide Web Consortium (W3C),
maintainer of both the HTML and the CSS standards, has encouraged the use of
CSS over explicit presentational HTML since 1997.
 HTML stands for Hyper Text Markup Language

 HTML describes the structure of Web pages using markup
 HTML elements are the building blocks of HTML pages
 HTML elements are represented by tags
 HTML tags label pieces of content such as "heading", "paragraph", "table",

and so on
 Browsers do not display the HTML tags, but use them to render the content
of the page
Example
<!DOCTYPE html>
<html>
<head>
<title>Page Title</title>
</head>
<body>
<h1>My First Heading</h1>

<p>My first paragraph.</p>
</body>
</html>
Example Explained
 The <!DOCTYPE html> declaration defines this document to be HTML5

 The <html> element is the root element of an HTML page
 The <head> element contains meta information about the document
 The <title> element specifies a title for the document
 The <body> element contains the visible page content

 The <h1> element defines a large heading
 The <p> element defines a paragraph
Introduction of
C#
C#
C# is a general object-oriented programming (OOP) language for networking and

Web development. C# is specified as a common language infrastructure (CLI)
language.
In January 1999, Dutch software engineer Anders Hejlsberg formed a team to

develop C# as a complement to Microsoft’s NET framework. Initially, C# was
developed as C-Like Object Oriented Language (Cool). The actual name was
changed to avert potential trademark issues. In January 2000, NET was released as
C#. Its NET framework promotes multiple Web technologies.
The term is sometimes spelled as C Sharp or C-Sharp.
C# is a modern, general-purpose, object-oriented programming language

developed by Microsoft and approved by European Computer Manufacturers
Association (ECMA) and International Standards Organization (ISO). C# was
developed by Anders Hejlsberg and his team during the development of .Net
Framework. C# is designed for Common Language Infrastructure (CLI), which
consists of the executable code and runtime environment that allows use of various
high-level languages on different computer platforms and architectures. The
following reasons make C# a widely used professional language: It is a modern,
general-purpose programming language
 It is object oriented
. It is component oriented.
 It is easy to learn.
 It is a tructured language.
 It produces efficient programs.
 It can be compiled on a variety of computer platforms.
 It is a part of .Net Framework.

Strong Programming Features of C#
C# Although C# constructs closely follow traditional high-level languages, C and

C++ and being an object-oriented programming language. It has strong
resemblance with Java, it has numerous strong programming features that make it
endearing to a number of programmers worldwide. Following is the list of few
important features of C#:
Boolean Condition
 Automatic Garbage Collection
 Standard Library
 Assembly Versioning
 Properties and Event
 Delegates and Events Management
 Easy-to-use Generics
 Indexers Conditional Compilation
 Simple Multithreading
 LINQ and Lambda Expressions
 Integration with Windows

MAIN FEATURES OF C#
1. SIMPLE
1. Pointers are missing in C#.

2. Unsafe operations such as direct memory manipulation are not allowed.
3. In C# there is no usage of "::" or "->" operators.
4. Since it's on .NET, it inherits the features of automatic memory management

and garbage collection.
5. Varying ranges of the primitive types like Integer,Floats etc.
6. Integer values of 0 and 1 are no longer accepted as boolean values. Boolean

values are pure true or false values in C# so no more errors of "="operator
and "=="operator.
7. "==" is used for comparison operation and "=" is used for assignment
operation.
2. MODERN
1. C# has been based according to the current trend and is very powerful and
simple for building interoperable ,scable, robust applications.
2. C# includes built in support to turn any component into a web service that
can be invoked over the internet from any application running on any
platform.
3. OBJECT ORIENTED
1. C# supports Data Encapsulation, inheritance, polymorphism, interfaces.

2. (int,float, double) are not objects in java but C# has introduces
structures(structs) which enable the primitive types to become objects.
int i=1;
string a=i Tostring(); //conversion (or) Boxing
4. TYPE SAFE
1. In C# we cannot perform unsafe casts like convert double to a boolean.

2. Value types (priitive types) are initialized to zeros and reference types
(objects and classes) are initialized to null by the compiler automatically.
3. arrays are zero base indexed and are bound checked.
4. Overflow of types can be checked.
5. INTEROPERABILITY
1. C# includes native support for the COM and windows based applications.
2. Allowing restriced use of native pointers.
3. Users no longer have to explicityly implement the unknown and other COM
interfacers, those features are built in.
4. C# allows the users to use pointers as unsafe code blocks to manipulate your
old code.
5. Components from VB NET and other managed code languages and directlyt
be used in C#.
6. SCALABLE AND UPDATEABLE
1. .NET has introduced assemblies which are self describing by means of their
manifest. manifest establishes the assembly identity, version, culture and
digital signature etc. Assemblies need not to be register anywhere.
2. To scale our application we delete the old files and updating them with new
ones. No registering of dynamic linking library.
3. Updating software components is an error prone task. Revisions made to the

code. can effect the existing program C# support versioning in the language.
Native support for interfaces and method overriding enable complex frame
works to be developed and evolved over time.
THE .NET FRAMEWORK:

The .Net framework is a revolutionary platform that helps you to write the
following types of applications:
 Windows applications
 Web applications
 Web services
 The .Net framework applications are multi-platform applications.
The framework has been designed in such a way that it can be used from any of
the following languages: C#, C++, Visual Basic, Jscript, COBOL, etc. All these
languages can access the framework as well as communicate with each other.
The .Net framework consists of an enormous library of codes used by the client
languages such as C#. Following are some of the components of the .Net
framework:
 Common Language Runtime (CLR)
 The .Net Framework Class Library
 Common Language Specification
 Common Type System
 Metadata and Assemblies

 Windows Forms
 ASP.Net and ASP.Net AJAX
 ADO.Net Windows Workflow Foundation (WF)
 Windows Presentation Foundation
 Windows Communication Foundation (WCF)
 LINQ
Software Engineering
Paradigm
Software Engineering Paradigm
Software is more than just a program code. A program is an executable code,
which serves some computational purpose. Software is considered to be collection
of executable programming code, associated libraries and documentations.
Software, when made for a specific requirement is called software product.
Engineering on the other hand, is all about developing products, using well-
defined, scientific principles and methods. Software engineering is an
engineering branch associated with development of software product using well-
defined scientific principles, methods and procedures. The outcome of software
engineering is an efficient and reliable software product.
The software engineering paradigm which is also referred to as a software process

model or Software Development Life Cycle (SDLC) model is the development
strategy that encompasses the process, methods and tools. SDLC describes the
period of time that starts with the software system being conceptualized and ends
with the software system been discarded after usage.
The objectives of the use of software engineering paradigms include:

The software development process becomes a structured process.
Determine the order of states involved in software development and evolution, and
to establish the transitions criteria for the next stage.
The software engineering paradigm provides the guidance to the software engineer.
A paradigm specifies the particular approach or philosophy for designing, building

and maintaining software. Each paradigm has its own advantages and
disadvantages which make some paradigm more suitable to be used in developing
a given software system in a given situation than another.
The techniques, tools procedures and methods in developing software systems are
heavily dependent on the selected paradigm.
There are common software process tasks, phases and activities that are modeled
by software models. They are heavily affected by selected software paradigms.
These tasks, phases and activities include:
Requirements Engineering: Software specification and functional requirements

obtained from the user.
Requirements Analysis and Modeling Architectural Engineering, implementation

and Design: Production of the software system as a product
Software Testing and Validation: Activity that assures that customer specifications
are met
System Delivery.
Software Evolution and Upgrading: System modification to meet continuing

customer needs
System Documenting Maintenance

Software Paradigms
Software paradigms refer to the methods and steps, which are taken while
designing the software. There are many methods proposed and are in work today,
but we need to see where in the software engineering these paradigms stand.
These can be combined into various categories, though each of them is contained
in one another:
Programming paradigm is a subset of Software design paradigm which is further a

subset of Software development paradigm.
Software Development Paradigm
This Paradigm is known as software engineering paradigms where all the
engineering concepts pertaining to the development of software are applied. It
includes various researches and requirement gathering which helps the software
product to build. It consists of –
 Requirement gathering
 Software design
 Programming
Software Design Paradigm

This paradigm is a part of Software Development and includes –
 Design
 Maintenance
 Programming
Programming Paradigm
This paradigm is related closely to programming aspect of software development.
This includes
 Coding
 Testing
 Integration
Need of Software Engineering
The need of software engineering arises because of higher rate of change in user
requirements and environment on which the software is working.
 Large software - It is easier to build a wall than to a house or building,

likewise, as the size of software become large engineering has to step to give
it a scientific process.
 Scalability- If the software process were not based on scientific and
engineering concepts, it would be easier to re-create new software than to
scale an existing one.
 Cost- As hardware industry has shown its skills and huge manufacturing has
lower down he price of computer and electronic hardware. But the cost of
software remains high if proper process is not adapted.
 Dynamic Nature- The always growing and adapting nature of software

hugely depends upon the environment in which user works. If the nature of
software is always changing, new enhancements need to be done in the
existing one. This is where software engineering plays a good role.
 Quality Management- Better process of software development provides

better and quality software product.
Development Model
The waterfall model is a sequential design process, used in software development

processes, in which progress is seen as flowing steadily downwards (like
a waterfall) through the phases of conception, initiation, analysis, design,
construction, testing, production/ implementation and maintenance. The waterfall
development model originates in the manufacturing and construction industries:
highly structured physical environments in which after-the-fact changes are
prohibitively costly, if not impossible. Since no formal software development
methodologies existed at the time, this hardware-oriented model was simply
adapted for software development.
The first known presentation describing use of similar phases in software

engineering was held by Herbert D. Benington at Symposium on advanced
programming methods for digital computers on 29 June 1956. This presentation
was about the development of software for SAGE. In 1983 the paper was
republished with a foreword by Benington pointing out that the process was not in
fact performed in a strict top-down fashion, but depended on a prototype.
The first formal description of the waterfall model is often cited as a 1970 article
by Winston W. Royce, although Royce did not use the term waterfall in that article.
Royce presented this model as an example of a flawed, non-working model; which
is how the term is generally used in writing about software development—to
describe a critical view of a commonly used software development practice.
The earliest use of the term "waterfall" may have been a 1976 paper by Bell and
Thayer.
In 1985, the United States Department of Defense captured this approach in DOD-
STD-2167A, their standards for working with software development contractors,
which stated that "the contractor shall implement a software development cycle
that includes the following six phases: Preliminary Design, Detailed Design,
Coding and Unit Testing, Integration, and Testing".
In Royce's original waterfall model, the following phases are followed in order:
1. System and software requirements: captured in a product requirements
document
2. Analysis: resulting in models, schema, and business rules
3. Design: resulting in the software architecture
4. Coding: the development, proving, and integration of software
5. Testing: the systematic discovery and debugging of defects
6. Operations: the installation, migration, support, and maintenance of complete

systems
S/W & H/W
Requirement
S/W & H/W Requirement
Developer Side:
Operating System Windows 7
Application System IIS 5.4
Database SQL Server 2012
Programming ASP.Net with C#
language
Development IDE Visual Studio 2012
Client Side:
Operating System Any
Web Browser Any
Server side:
Operating system Any
Application Server IIS 5.1
Hardware Interface:
Developer side:
Processor RAM Disk Space
Intel p4 or 2 GB
equivalent 512MB
Client Side:
Intel p4 or 512MB 1 GB
equivalent
Server Side:
Server 2 GB As per the Size
Environment of the required
Data base
Capable Hardware
Communication Interface:
 Client on internet will be using HTTP/HTTPS protocol

 Client on internet will be using TCP/IP protocols
Constraints:
 GUI is only in English.

 Login and Password is used for identification of Admin,Employee,Client
and there is no facility for guest.
 This System is working for single server.
 There is no Maintainability of backup so availability will get effected.
 Limited to HTTP/HTTPS
Software design
Data Flow diagram
(DFD)
SYSTEM DESIGN
Systems design is the process or art of defining the architecture, components,

modules, interfaces, and data for a system to satisfy specified requirements. One
could see it as the application of systems theory to product development. There is
some overlap and synergy with the disciplines of systems analysis, systems
architecture and systems engineering.
DATA FLOW DIAGRAMS:, 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 top-level diagram is often called a “context
diagram”.
A data flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system, modelling its process aspects. A DFD is often used
as a preliminary step to create an overview of the system without going into great
detail, which can later be elaborated.[2] DFDs can also be used for
the visualization of data processing (structured design).
A DFD shows what kind of information will be input to and output from the
system, how the data will advance through the system, and where the data will be
stored. It does not show information about process timing or whether processes
will operate in sequence or in parallel, unlike a traditional
structured flowchart which focuses on control flow, or a UML activity workflow
diagram, which presents both control and data flows as a unified model.
Context Diagram: It contains a single process, but it plays a very important

role in studying the current system. The context diagram defines the system that
will be studied in the sense that it determines the boundaries. Anything that is not
inside the process identified in the context diagram will not be part of the system
study. It represents the entire software element as a single bubble with input and
output data indicated by incoming and outgoing arrows respectively.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. Data move in a specific direction from an origin to a
destination.
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
Symbols Elementary references
Process that transforms data flow
Data Flow
Source or Destination of data
Data Store
Constructing a DFD:
Several rules of thumb are used in drawing DFD’S:

1. Process should be named and numbered for an easy interface. 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.
Salient features of DFD’S:

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

DFD’s are of two types
(a) Physical DFD

(b) Logical DFD
1. Physical DFD:
Structured analysis states that the current system should be first understand
correctly. The physical DFD is the model of the current system and is used to
ensure that the current system has been clearly understood. Physical DFDs shows
actual devices, departments, and people etc., involved in the current system
2. Logical DFD:
Logical DFDs are the model of the proposed system. They clearly should show the
requirements on which the new system should be built. Later during design activity
this is taken as the basis for drawing the system’s structure charts.
Rules Governing the DFD’S:
Process
1. No process can have only outputs.
2. No process can have only inputs. If an object has only inputs than it must be
a sink.
3. A process has a verb phrase level.
Data Store
1. Data cannot move directly from one data store to another data store, a
process must move data.
2. Data cannot move directly from an outside source to a data store, a process,
which retrieves, must move data from the source and place the data into data
store.
3. A data store has a noun phrase level.
Level 0:
Intranet
Mailing
NOTICE
USER UserInfo Notice Info
Mail Info Chat Info

CHAT
MAIL
Level1:
ER Diagram
ER DIAGRAMS
In software engineering, an entity–relationship model (ER model) is a data

model for describing the data or information aspects of a business domain or its
process requirements, in an abstract way that lends itself to ultimately being
implemented in a database such as a relational database. The main components of
ER models are entities (things) and the relationships that can exist among them.
Entity–relationship modeling was developed by Peter Chen and published in a

1976 paper. However, variants of the idea existed previously and have been
devised subsequently such as super type and subtype data entities and
commonality relationships.
An entity–relationship model is a systematic way of describing and defining a

business process. The process is modeled as components (entities) that are linked
with each other by relationships that express the dependencies and requirements
between them, such as: one building may be divided into zero or more apartments,
but one apartment can only be located in one building. Entities may have various
properties (attributes) that characterize them. Diagrams created to represent these
entities, attributes, and relationships graphically are called entity–relationship
diagrams.
An ER model is typically implemented as a database. In the case of a relational

database, which stores data in tables, every row of each table represents one
instance of an entity. Some data fields in these tables point to indexes in other
tables; such pointers represent the relationships.
An entity–relationship model (ER model for short) describes interrelated things

of interest in a specific domain of knowledge. A basic ER model is composed of
entity types (which classify the things of interest) and specifies relationships that
can exist between instances of those entity types.
Database design
DATABASE DESIGN
NORMALIZATION A Database is a collection of interrelated data stored with a

minimum of redundancy to serve many applications. The database design is used
to group data into a number of tables and minimizes the artificiality embedded in
using separate files. The tables are organized to:
 Reduced duplication of data.

 Simplify functions like adding, deleting, modifying data etc..,
 Retrieving data
 Clarity and ease of use
 More information at low cos
Normalization is built around the concept of normal forms. A relation is said to be
in a particular normal form if it satisfies a certain specified set of constraints on the
kind of functional dependencies that could be associated with the relation. The
normal forms are used to ensure that various types of anomalies and
inconsistencies are not introduced into the database.
First Normal Form: A relation R is in first normal form if and only if all
underlying domains contained atomic values only
Second Normal Form: A relation R is said to be in second normal form if and

only if it is in first normal form and every non-key attribute is fully dependent on
the primary key.
Third Normal Form: A relation R is said to be in third normal form if and only if
it is in second normal form and every non key attribute is non transitively depend
on the primary key.
Chat
Column name Data type Description(Allow

Null)
Id Int Primary key
Sender varchar(50) Not Null

Receiver varchar(50) Not Null
Email varchar(50) Not Null

Message varchar(100) Not Null
Messagestatus varchar(50)
Mail

Null)
Id Int Primary key
Sender varchar(50) Not Null

Receiver varchar(50) Not Null
Subject varchar(500) Not Null

Attachement varchar(50)
Messagestatus varchar(50) Not Null
Date varchar(50) Not Null
Time varchar(8) Not Null
Body varchar(1000) Not Null
NewsInfo

Null)
Sno Int Primary key
Identity Column
News varchar(500) Not Null
Register
Null)
Id Int Primary key
Identity Column
Password varchar(50) Not Null
Name varchar(50) Not Null
Email varchar(50) Not Null
Dob varchar(50) Not Null
City varchar(50)
Gender varchar(50)
Photo varchar(50)
PROJECT
SCREENSHOT
INTERFACE DESIGN
Snap shot
Home
Registration
User Home
About us
Chat
Inbox
SentMail
Sent Mail
Admin Panel:
Admin Home
Edit Member
Sent Mail (Admin)
Design Page Coding
DESIGN PAGE CODING
Registration Page
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"

AutoEventWireup="true" CodeFile="registration.aspx.cs"
Inherits="registration" EnableEventValidation="false"%>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<style type="text/css">
.auto-style1 {
width: 281%;
align-self:center;
margin-left: 147px;
}
.auto-style2 {
}
.auto-style3 {
width: 168px;
}
.auto-style4 {
width: 168px;
height: 47px;
}
.auto-style5 {
height: 47px;
}
</style>
</asp:Content>
<asp:Content ID="Content2" runat="server"

contentplaceholderid="ContentPlaceHolder1">
<center>   <table class="auto-style1">
<tr>
<td class="auto-style3" style="color: #FF0000">
<asp:Label ID="Label1" runat="server" Text="Username"
Font-Bold="True" Font-Names="Times New Roman" Font-Size="Medium"
ForeColor="#6600FF"></asp:Label>* </td>
<td>
            &
nbsp;
<asp:TextBox ID="TextBox1" runat="server" style="border-
radius:10px" BorderStyle="Groove" Height="35px"
Width="305px"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1"
runat="server" ErrorMessage="*" Font-Bold="True" ForeColor="#CC0000"
ControlToValidate="TextBox1"
EnableClientScript="False"></asp:RequiredFieldValidator>
<br />
<br />
</td>
</tr>
<tr>
<td class="auto-style3" style="color: #FF0000"><asp:Label
ID="Label2" runat="server" Text="Password" Font-Bold="True" Font-
Names="Times New Roman" Font-Size="Medium"
<td>
            &
nbsp;        <asp:TextBox
ID="TextBox2" runat="server" style="border-radius:10px"
BorderStyle="Groove" Height="35px" Width="305px"></asp:TextBox>
<br />
<br />
</td>
</tr>
<tr>
ID="Label8" runat="server" Text="Confirm Password" Font-Bold="True" Font-
ForeColor="#6600FF"></asp:Label></td>
<td class="auto-style5">
            &
nbsp;        <asp:TextBox
<asp:CompareValidator ID="CompareValidator1"
ControlToCompare="TextBox2" ControlToValidate="TextBox6"
EnableClientScript="False"></asp:CompareValidator>
<br />
</td>
</tr>
<tr>
ID="Label3" runat="server" Text="Gender" Font-Bold="True" Font-
<td>
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
<asp:RadioButtonList ID="RadioButtonList1" runat="server"
RepeatDirection="Horizontal" Font-Bold="True" Font-Names="Times New
Roman" Font-Size="Medium" ForeColor="#6600FF" Height="21px" Width="223px"
style="margin-left: 143px"><asp:ListItem>Male</asp:ListItem>
<asp:ListItem>Female</asp:ListItem></asp:RadioButtonList>
<br />
</td>
</tr>
<tr>
ID="Label4" runat="server" Text="Email-id" Font-Bold="True" Font-
<td>
            &
nbsp;       <asp:TextBox ID="TextBox3"
runat="server" style="border-radius:10px" BorderStyle="Groove"
Height="35px" Width="305px"></asp:TextBox>
<br />
<br />
</td>
</tr>
<tr>
ID="Label5" runat="server" Text="D.O.B" Font-Bold="True" Font-
<td>
            &
nbsp;       <asp:TextBox ID="TextBox4"
runat="server" style="border-radius:10px" BorderStyle="Groove"
<br />
<br />
</td>
</tr>
<tr>
ID="Label6" runat="server" Text="Home-Town" Font-Bold="True" Font-
<td>
            &
nbsp;        <asp:TextBox
<br />
<br />
</td>
</tr>
<tr>
ID="Label7" runat="server" Text="Upload-Photo" Font-Bold="True" Font-
<td>
            &
nbsp;      <asp:FileUpload ID="FileUpload1"
runat="server" Height="35px" Width="305px" />
ControlToValidate="FileUpload1"
<br />
<br />
</td>
</tr>
<tr>
<td class="auto-style2" colspan="2">
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;
<br />
            &
nbsp;
<asp:Button ID="Button1" runat="server" Text="Register"
BackColor="Blue" Font-Bold="True" Font-Size="Medium" ForeColor="#99FF99"
OnClick="Button1_Click" Height="36px" Width="100px" style="border-
radius:10px"/>
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$ ConnectionStrings:ConnectionString %>"
SelectCommand="SELECT * FROM [register]"></asp:SqlDataSource>
</td>
</tr>
</table>
</center>
</asp:Content>

</asp:Content>
Page
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"

AutoEventWireup="true" CodeFile="login.aspx.cs" Inherits="login"
EnableEventValidation="false" %>

.auto-style1 {
width: 688px;
}
.auto-style4 {}
</style>
<script type="text/javascript">
function makeobject() {
var p;
try {
p = new XMLHttpRequest();
}
catch (e) {
try {
p = new ActiveXObject("Msxml2.HttpRequest");
}
catch (e) {
try {
p = new
ActiveXObject("Microsoft.HttpRequest");
}
catch (e) {
alert("your browser does not support Ajax");
}
}
}
return p;
}
function loadUser() {
var a = document.getElementById("TextBox1").value;
var b = document.getElementById("TextBox2").value;
var r = makeobject();
var s = Math.random();
r.onreadystatechange = function () {
if (r.readyState == 4) {
alert(r.responseText);
}
}
if (a == "")
{
alert("shbdhbj");
}
else if(b=="")
{
alert("jhcfj");
}
else if(a==b)
{
alert("vgh");
}
else
{
r.open("post", "loginUser.aspx?t=" + s + "&uname=" + a +
"&pass=" + b);
r.send();
}
}
</script>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder2"
Runat="Server">
</asp:Content>
Runat="Server">

<br />
<table style="width: 638px; height: 260px;">

<tr>
<asp:Panel ID="Panel1" runat="server" Height="289px">
<asp:Image ID="Image3" runat="server" Height="301px"
ImageUrl="~/images3/log.PNG" Width="258px" />
</asp:Panel>
<br />
<br />
</td>
<asp:Panel ID="Panel2" runat="server"
ForeColor="#F30C2F">
<br />
<br />
<asp:Label ID="Label1" runat="server" Font-
Bold="True" Font-Names="Times New Roman" Font-Size="Medium"
ForeColor="#6600FF" Text="Email-id"></asp:Label>
*
<asp:TextBox ID="TextBox1" runat="server"
BorderStyle="Groove" Height="35px" style="border-radius: 10px"
<asp:RequiredFieldValidator
ID="RequiredFieldValidator1" runat="server" ErrorMessage="plz enter
email" Font-Bold="True" ForeColor="Blue" ControlToValidate="TextBox1"
<br />
<br />
<br />
<asp:Label ID="Label2" runat="server" Font-
ForeColor="#6600FF" Text="Password"></asp:Label>
*
BorderStyle="Groove" Height="35px" style="border-radius: 10px"
Width="305px" TextMode="Password"></asp:TextBox>
ID="RequiredFieldValidator2" runat="server" ErrorMessage="plz enter
correct password" Font-Bold="True" ForeColor="Blue"
<br />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;
<br />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;

<asp:Button ID="Button2" runat="server"
OnClick="Button2_Click" Text="Login" Width="79px" />
<br />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;      <asp:HyperLink ID="HyperLink1"
runat="server">Forget Password</asp:HyperLink>
   <asp:HyperLink ID="HyperLink2"
runat="server" NavigateUrl="~/registration.aspx">Create an
Account</asp:HyperLink>
<br />
<br />
<br />
            &
nbsp;
<br />
<br />
<br />
<br />
<br />
<br />
<br />
</asp:Panel>
<br />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
</td>
</tr>
</table>
</asp:Content>
Home Page
<%@ Page Title="" Language="C#" MasterPageFile="~/mainMasterPage.master"

AutoEventWireup="true" CodeFile="home.aspx.cs" Inherits="home"
EnableEventValidation="false"%>

</asp:Content>

<p>
            &
nbsp;
ImageUrl="~/images3/User-icon.png" Width="186px" />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
ImageUrl="~/images3/images5.jpg" Width="186px" />
</p>
<p>

<asp:ImageButton ID="ImageButton1" runat="server" Height="81px"
ImageUrl="~/images3/AD1.png" OnClick="ImageButton1_Click"
Width="245px" />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
<asp:ImageButton ID="ImageButton2" runat="server" Height="81px"
ImageUrl="~/images3/US1.png" OnClick="ImageButton2_Click"
Width="245px" />
</p>
</asp:Content>
Aboutus Page

AutoEventWireup="true" CodeFile="aboutus.aspx.cs" Inherits="aboutus" %>

#art-main, table
{
font-family: "Century Gothic",Arial, Helvetica, Sans-Serif;
font-style: normal;
font-weight: normal;
font-size: 12px;
text-align: justify;
width: 598px;
}
.auto-style1 {
height: 40px;
width: 803px;
}
.auto-style2 {
height: 200px;
width: 803px;
}
</style>
</asp:Content>
Runat="Server">
<table>
<tr>
<td style="vertical-align: top; font-family: calibri; font-
size: medium; color: #2E566C; text-align: justify;" class="auto-style1">
Intranet Mailing System is a web based applicationwhich
provides facility to the members or employees connected within a LAN
(Local Area Network) to communicate and exchange file and
folders among them.<br />
</td>
</tr>
<tr>
<br />
In Intranet Mailing Facility as per its name
it provides facility to mail the members connected
within a local area
network, here one can share any kind of attachement and
subject to other
employee by providing specific mail id of receiver mail.
</td>
</tr>
<tr>
<br />
In this Local area netwok mailing
system one could   not get egistered by
himself/herself
employees working in a same
Local area netwok are provided
their ID & password by
administrator so that they could gain the facility
provided by application.</td>
</tr>
<tr>
<br />
In Intranet Mailing System facility of communication is
been provide by one on
one chatting   facility where
inbox and sent item are
also available to have your chatting
history.</td>
</tr>
<tr>
</td>
</tr>
<tr>
<table style="width:100%;">
<tr>
<td>
<asp:Image ID="Image1" runat="server"
Height="200px"
ImageUrl="~/images3/internet-
intranet.jpg" Width="200px" />
</td>
<td>
</td>
<td>
<asp:Image ID="Image2" runat="server"
Height="200px"
ImageUrl="~/images3/internet-
intranet.jpg" Width="200px" />
</td>
</tr>
</table>
</td>
</tr>
</table>
</asp:Content>
Chat Page

AutoEventWireup="true" CodeFile="Chat.aspx.cs" Inherits="Chat"
EnableEventValidation="false"%>

.auto-style1 {
width: 100%;
}
.auto-style2 {
height: 303px;
}
</style>
</asp:Content>
Runat="Server">


    <table class="auto-style1"
style="border: thick groove #800080">
<tr>
<td colspan="2" style="border: thick groove #800080;
font-size: medium; font-weight: bold; font-style: normal; font-family:
'Times New Roman', Times, serif; color: #800000; background-color:
#FF6699;">
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           You are
chatting too:
<asp:Label ID="Label1" runat="server" Text="Label"></asp:Label>
</td>
</tr>
<tr>
<td class="auto-style2" style="background-color:
#FF6699">
<asp:Panel ID="Panel1" runat="server" Width="228px">
<asp:GridView ID="GridViewmember" runat="server"
AllowPaging="True" BackColor="#FF99CC" BorderStyle="Groove">
<Columns>
<asp:TemplateField ShowHeader="False">
<ItemTemplate>
<asp:LinkButton ID="LinkButton1"
runat="server" CausesValidation="False" CommandName="Select"
OnClick="LinkButton1_Click" Text="Chat"></asp:LinkButton>
</ItemTemplate>
</asp:TemplateField>
</Columns>
</asp:GridView>
</asp:Panel>
</td>
<asp:Panel ID="Panel2" runat="server" Visible="False"
BackColor="#CC33FF" Width="581px">
<br />
<asp:GridView ID="GridView4" runat="server">
</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource1"
runat="server" ConnectionString="<%$ ConnectionStrings:ConnectionString
%>" SelectCommand="SELECT [message], [date], [time], [sender] FROM
[chat]"></asp:SqlDataSource>
<br />
<br />
<br />
TextMode="MultiLine" Width="291px" Height="58px"></asp:TextBox>
BackColor="Blue" Font-Bold="True" Font-Size="Large" ForeColor="#66FF99"
OnClick="Button1_Click" Text="Send" Width="68px" />
</asp:Panel>
</td>
</tr>
<tr>
<td style="background-color: #FF6699"> </td>
<td style="background-color: #FF6699">
<br />
<asp:Panel ID="Panel3" runat="server">
</asp:Panel>
<br />
<br />
<br />
<br />
</td>
</tr>
</table>
</asp:Content>
Mail Page

AutoEventWireup="true" CodeFile="mail.aspx.cs" Inherits="mail"

.auto-style1 {
width: 100%;
margin-left: 168px;
}
.auto-style2 {
}
.auto-style3 {
width: 177px;
}
.auto-style4 {
width: 177px;
height: 48px;
}
.auto-style5 {
height: 48px;
}
</style>
</asp:Content>
Runat="Server">
<p>

<table class="auto-style1">
<tr>
<asp:Label ID="Label6" runat="server" Text="To" Font-
ForeColor="#6600FF"></asp:Label>
</td>
            &
nbsp;           &n
bsp;
style="border-radius:10px" BorderStyle="Groove" Height="36px"
ID="RequiredFieldValidator4" runat="server" ErrorMessage="*"
ControlToValidate="TextBox1" ForeColor="#FF3300"
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label7" runat="server" Text="Subject"
</td>
<td>
            &
nbsp;           &n
bsp;
style="border-radius:10px" BorderStyle="Groove" Height="35px"
ControlToValidate="TextBox2" EnableClientScript="False"
ForeColor="#FF3300"></asp:RequiredFieldValidator>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label8" runat="server" Text="Body"
</td>
<td>
            &
nbsp;           &n
bsp;
TextMode="MultiLine" style="border-radius:10px" BorderStyle="Groove"
ControlToValidate="TextBox3" EnableClientScript="False"
ForeColor="#FF3300"></asp:RequiredFieldValidator>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label9" runat="server" Text="Attach"
</td>
<td>
            &
nbsp;           &n
bsp;
<asp:FileUpload ID="FileUpload1" runat="server" />
<br />
<br />
</td>
</tr>
<tr>
<td class="auto-style2" colspan="2">
            &
nbsp;           &n
bsp;
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;
Text="Send" OnClick="Button1_Click" Style="border-radius:10px" />
<asp:Label ID="Label10" runat="server" Text="Label"
Visible="False"></asp:Label>
<br />
</td>
</tr>
</table>
</p>
</asp:Content>
Inbox Page

AutoEventWireup="true" CodeFile="inbox.aspx.cs" Inherits="inbox"

</asp:Content>
Runat="Server">
<asp:GridView ID="GridView1" runat="server" Width="583px"
AllowPaging="True" BackColor="#CC33FF" Font-Bold="True" Font-
Size="Medium" ForeColor="#00FF99">
<Columns>
<asp:CommandField SelectText="View"
ShowSelectButton="True" />
</Columns>
</asp:GridView>
SelectCommand="SELECT * FROM [chat] "></asp:SqlDataSource>
SelectCommand="SELECT [sender], [subject], [body], [time], [date] FROM
[mail] where ([receiver]=@receiver)"></asp:SqlDataSource>
<br />
<br />
</asp:Content>
Admin LogIn
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage21.master"

AutoEventWireup="true" CodeFile="adminlogin.aspx.cs"
Inherits="adminlogin" %>

.auto-style4 {
width: 60%;
height: 200px;
margin-left: 79px;
}
.auto-style6 {
height: 43px;
}
.auto-style8 {
width: 535px;
height: 55px;
}
.auto-style9 {
height: 55px;
}
</style>
</asp:Content>

<p>
<br />
<br />
<br />
ImageUrl="~/images3/fg.jpg" Width="286px" />
<br />
<br />
</p>
</asp:Content>

<tr>
<asp:Label ID="Label1" runat="server" Text="Name" Font-
Bold="True" Font-Size="Medium" ForeColor="#9900CC"></asp:Label>
</td>
            &
nbsp;
<asp:TextBox ID="TextBox1" runat="server" Height="27px"
Width="311px" Style="border-radius:10px"></asp:TextBox>
<br />
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label2" runat="server" Text="Password"
Font-Bold="True" Font-Size="Medium" ForeColor="#9900CC"></asp:Label>
</td>
<asp:TextBox ID="TextBox2" runat="server" Height="27px"
Width="311px" style="border-radius:10px"
TextMode="Password"></asp:TextBox>
<br />
<br />
</td>
</tr>
<tr>
<td class="auto-style6"
colspan="2">          &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;           &n
bsp;
<asp:Button ID="Button1" runat="server" BackColor="Blue"
Font-Bold="True" Font-Size="Medium" ForeColor="#66FFFF" Height="36px"
Text="Login" Width="100px" Style="border-radius:10px"
OnClick="Button1_Click" />
</td>
</tr>
</table>
</asp:Content>
Add Member page

<%@ Page Title="" Language="C#"
MasterPageFile="~/MasterPage2(admin).master" AutoEventWireup="true"
CodeFile="addmember.aspx.cs" Inherits="addmember" %>
<%@ Register assembly="System.Web.DataVisualization, Version=4.0.0.0,

Culture=neutral, PublicKeyToken=31bf3856ad364e35"
namespace="System.Web.UI.DataVisualization.Charting" tagprefix="asp" %>

</asp:Content>

<div>
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;      <strong style="font-size:
large">
            &
nbsp;           &n
bsp;   Update information</strong></div>
<asp:GridView ID="GridView1" runat="server"
AutoGenerateColumns="False" DataKeyNames="id"
DataSourceID="SqlDataSource1"
OnSelectedIndexChanged="GridView1_SelectedIndexChanged" Font-Bold="True"
Font-Size="Medium" ForeColor="#CC33FF" Height="198px" style="margin-left:
0px" AllowPaging="True">
<Columns>
<asp:TemplateField HeaderText="id"
InsertVisible="False" SortExpression="id">
<EditItemTemplate>
<asp:Label ID="Label1"
runat="server" Text='<%# Eval("id") %>'></asp:Label>
</EditItemTemplate>
<ItemTemplate>
<asp:Label ID="Label1"
runat="server" Text='<%# Bind("id") %>'></asp:Label>
</ItemTemplate>
<asp:BoundField DataField="name"
HeaderText="name" SortExpression="name" />
<asp:BoundField DataField="password"
HeaderText="password" SortExpression="password" />
<asp:BoundField DataField="email"
HeaderText="email" SortExpression="email" />
<asp:BoundField DataField="dob"
HeaderText="dob" SortExpression="dob" />
<asp:BoundField DataField="city"
HeaderText="city" SortExpression="city" />
<asp:BoundField DataField="gender"
HeaderText="gender" SortExpression="gender" />
<asp:BoundField DataField="photo"
HeaderText="photo" SortExpression="photo" />
<asp:CommandField HeaderText="Update"
ShowEditButton="True" ShowSelectButton="True" SelectText="" />
<asp:TemplateField HeaderText="Delete"
ShowHeader="False">
<ItemTemplate>
<asp:LinkButton ID="LinkButton1"
runat="server" CausesValidation="False" CommandName="Delete"
OnClick="LinkButton1_Click1" Text="Delete"></asp:LinkButton>
</ItemTemplate>
</Columns>
<EditRowStyle Width="50px" />
<RowStyle Width="80px" />
</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource1"
runat="server" ConnectionString="<%$ ConnectionStrings:ConnectionString
%>" SelectCommand="SELECT * FROM [register]" UpdateCommand="update
register set
name=@name,password=@password,email=@email,dob=@dob,city=@city,gender=@ge
nder,photo=@photo where email=@email"></asp:SqlDataSource>
</asp:Content>
<br />
ImageUrl="~/images3/bg.jpg" style="margin-left: 321px" Width="237px" />
</asp:Content>
Admin addUser page

CodeFile="AdminADDUser.aspx.cs" Inherits="AdminADDUser" %>

.auto-style3 {
width: 95%;
}
.auto-style4 {
width: 695px;
}
.auto-style5 {
width: 307px;
}
.auto-style6 {
width: 307px;
table-layout: auto;
height: 34px;
}
.auto-style7 {
width: 695px;
height: 34px;
}
</style>
</asp:Content>
<div><strong style="font-size:
large">
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;        <br />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;           &n
bsp;
<asp:Label ID="Label9" runat="server" ForeColor="#6600CC"
Text="ADD USER"></asp:Label>
</strong></div>
<br />
<table class="auto-style3" style="align-self:center; margin-left:
291px;">
<tr>
<td class="auto-style5" style="table-layout: auto">
<asp:Label ID="Label1" runat="server" Text="USERNAME"
Font-Bold="True" Font-Size="Medium" ForeColor="#993399"></asp:Label>
</td>
radius: 10px" Height="24px" Width="300px"></asp:TextBox>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label2" runat="server" Text="PASSWORD"
Font-Bold="True" Font-Size="Medium" ForeColor="#993399"></asp:Label>
</td>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label3" runat="server" Text="CONFIRM
PASSWORD" Font-Bold="True" Font-Size="Medium"
ForeColor="#993399"></asp:Label>
</td>
<asp:CompareValidator ID="CompareValidator1"
runat="server" ControlToCompare="TextBox2" ControlToValidate="TextBox3"
ErrorMessage="incorrect password"
EnableClientScript="False"></asp:CompareValidator>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label4" runat="server" Text="EMAIL" Font-
Bold="True" Font-Size="Medium" ForeColor="#993399"></asp:Label>
</td>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label5" runat="server" Text="DOB" Font-
</td>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label6" runat="server" Text="CITY" Font-
</td>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label7" runat="server" Text="GENDER" Font-
</td>
<asp:RadioButtonList ID="RadioButtonList1" runat="server"
RepeatDirection="Horizontal" Font-Bold="True" Font-Size="Medium"
ForeColor="#9900CC">
<asp:ListItem>MALE</asp:ListItem>
<asp:ListItem>FEMALE</asp:ListItem>
</asp:RadioButtonList>
<br />
</td>
</tr>
<tr>
<asp:Label ID="Label8" runat="server" Text="PHOTO" Font-
</td>
<asp:FileUpload ID="FileUpload1" runat="server" Font-
Bold="True" Font-Size="Medium" ForeColor="#9900CC" />
<br />
</td>
</tr>
<tr>
<td class="auto-style5" style="table-layout:
auto"> </td>
OnClick="Button1_Click" Text="SUBMIT" BackColor="Blue" Font-Bold="True"
Font-Size="Medium" ForeColor="White" />
</td>
</tr>
</table></center>
</asp:Content>
Compose Mail Page
CodeFile="ComposeMail.aspx.cs" Inherits="ComposeMail" %>

.auto-style3 {
width: 80%;
margin-left: 275px;
}
.auto-style4 {
height: 76px;
}
.auto-style5 {
height: 76px;
width: 210px;
}
.auto-style6 {
width: 210px;
}
</style>
</asp:Content>
<tr>
<td class="auto-style5" style="font-size: medium; font-
weight: bold; color: #9900CC">subject</td>
            &
nbsp;
<asp:TextBox ID="TextBox2" runat="server" Style="border-
radius:20px" Height="28px" Width="305px"></asp:TextBox>
</td>
</tr>
<tr>
<td style="font-size: medium; font-weight: bold; color:
#9900CC" class="auto-style6">attachment</td>
<td>
            &
nbsp;
<asp:FileUpload ID="FileUpload1" runat="server" Font-
Bold="True" Font-Size="Medium" ForeColor="#9900CC" Height="27px"
Width="286px" />
<br />
<br />
</td>
</tr>
<tr>
<td style="font-size: medium; font-weight: bold; color:
#9900CC" class="auto-style6">
<asp:Label ID="Label1" runat="server"
Text="Message"></asp:Label>
</td>
<td>
            &
nbsp;
<asp:TextBox ID="TextBox1" runat="server" TextMode="MultiLine"
Height="81px" Width="574px" Style="border-radius:20px"></asp:TextBox>
<br />
</td>
</tr>
</table>
<br />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;
<br /> <br /> <br />
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;           &n
bsp;           &nb
sp;           &nbs
p;           &nbsp
;
            &
nbsp;           &n
bsp;
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click"
Text="Send Mail" BackColor="Blue" Font-Bold="True" Font-Size="Medium"
ForeColor="White" style="border-radius:10px" Height="33px"/> <br/> <br
/> <br /> <br />
</asp:Content>
Forget Password Page
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage21.master"

AutoEventWireup="true" CodeFile="forgetpassword.aspx.cs"
Inherits="forgetpassword" %>

</asp:Content>
<p>
<br />
</p>
<p>
</p>
<p>
</p>
</asp:Content>
CS Page
Coding
CS PAGE CODING
LogIn Page
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;
using System.Data;
public partial class login : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button2_Click(object sender, EventArgs e)
{
string a = "";
string b = "";
SqlConnection con = new
SqlConnection(ConfigurationManager.ConnectionStrings["ConnectionString"].
ConnectionString);
SqlCommand cmd = new SqlCommand("select email,password from
register where email=@email and password=@password",con);
cmd.Parameters.AddWithValue("@email", TextBox1.Text);
cmd.Parameters.AddWithValue("@password", TextBox2.Text);
con.Open();
SqlDataReader dr = cmd.ExecuteReader();
while (dr.Read())
{
a = dr[0].ToString();
b = dr[1].ToString();
}
if (a == TextBox1.Text.Trim() && b == TextBox2.Text.Trim())

{
Session["email"] = TextBox1.Text;
Response.Redirect("profile.aspx");
}
else
{
Response.Write("unsuccessful login");
}
}
}
Home Page
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class home : System.Web.UI.Page

{
{
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
{
Response.Redirect("adminlogin.aspx");
}
protected void ImageButton2_Click(object sender, ImageClickEventArgs
e)
{
Response.Redirect("login.aspx");
}
}
Registration Page
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class registration : System.Web.UI.Page

{
{
}
{
{
ConnectionString);
try
{
con.Open();
SqlCommand cmd = new SqlCommand("INSERT INTO
register(name,password,email,dob,city,gender,photo) VALUES
(@name,@password,@email,@dob,@city,@gender,@photo)", con);
cmd.Parameters.AddWithValue("@name", TextBox1.Text);
cmd.Parameters.AddWithValue("@password", TextBox2.Text);
cmd.Parameters.AddWithValue("@email", TextBox3.Text);
cmd.Parameters.AddWithValue("@dob", TextBox4.Text);
cmd.Parameters.AddWithValue("@city", TextBox5.Text);
cmd.Parameters.AddWithValue("@gender",
RadioButtonList1.SelectedItem.ToString());
cmd.Parameters.AddWithValue("@photo", "~/photo/" +
FileUpload1.FileName);
string name = FileUpload1.FileName.ToString();

string path = "~/photo/" + name;
FileUpload1.SaveAs(Server.MapPath(path));
cmd.ExecuteNonQuery();
Response.Write("Successfully Register");
TextBox4.Text = "";
TextBox3.Text = "";
TextBox2.Text = "";
TextBox1.Text = "";
TextBox5.Text = "";
}
catch (Exception ex)
{
Response.Write(ex.Message);
Response.Write("Unsucessfull Registration");
}
finally
{
con.Close();
}
}
}
}
Mail Page
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class mail : System.Web.UI.Page

{

{
}
{
Session["receiver"] = TextBox1.Text;
string email = "";
email = Session["email"].ToString();
string name = FileUpload1.FileName.ToString();

string path = "~/photo/" + name;
FileUpload1.SaveAs(Server.MapPath(path));

ConnectionString);
con.Open();
SqlCommand cmd = new SqlCommand("insert into
mail(sender,receiver,subject,attach,date,time,body)values('" + email +
"','" + TextBox1.Text + "','" + TextBox2.Text + "','" + path + "','" +
DateTime.Now.ToShortDateString() + "','" +
DateTime.Now.ToShortTimeString() + "','" + TextBox3.Text + "')", con);
TextBox1.Text = "";
TextBox2.Text = "";
TextBox3.Text = "";
con.Close();
Label10.Visible = true;
}
}
Chat Page
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Chat : System.Web.UI.Page

{
ConnectionString);
SqlCommand cmd = new SqlCommand();
string str = "";
{
str = Session["email"].ToString();
cmd.Connection = con;
gridmember();
}
private void gridmember()

{
SqlCommand cmd = new SqlCommand("SELECT email FROM register WHERE
email != '" + str + "'", con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
da.Fill(dt);
con.Close();
GridViewmember.DataSource = dt;
GridViewmember.DataBind();
}
protected void LinkButton1_Click(object sender, EventArgs e)
{
LinkButton lnkbtn = sender as LinkButton;
GridViewRow gvrow = lnkbtn.NamingContainer as GridViewRow;
string filePath =
GridViewmember.Rows[gvrow.RowIndex].Cells[1].Text;
Label1.Text = filePath;
Panel2.Visible = true;
cmd.CommandText = "SELECT message, date, time FROM chat WHERE

sender ='"+ str +"' AND receiver='"+ Label1.Text +"'";
da.Fill(dt);
con.Close();
GridView4.DataSource = dt;
GridView4 .DataBind();

{
cmd.CommandText = "INSERT INTO chat
(message,sender,receiver,messagestatus,date,time) VALUES
(@message,@sender,@receiver,@messagestatus,@date,@time)";
cmd.Parameters.AddWithValue("@message", TextBox1.Text);
cmd.Parameters.AddWithValue("@sender", str);
cmd.Parameters.AddWithValue("@receiver", Label1.Text);
cmd.Parameters.AddWithValue("@messagestatus", "itrue");
cmd.Parameters.AddWithValue("@date",
DateTime.Now.ToShortDateString());
cmd.Parameters.AddWithValue("@time",
DateTime.Now.ToShortTimeString());
con.Open();
// con.Close();
TextBox1.Text = "";
SqlDataAdapter ad =new SqlDataAdapter ("SELECT message, date,
time FROM chat WHERE sender ='"+ str +"' AND receiver='"+ Label1.Text
+"'", con );
DataSet ds = new DataSet();
ad.Fill(ds);
GridView4.DataSource = ds;
GridView4.DataBind();
con.Close();
}
private void gridinbox()
{
/* SqlCommand cmd = new SqlCommand("SELECT
date,time,subject,receiver,body FROM mail WHERE sender!='" + str + "' ",
con);
da.Fill(dt);
con.Close();
GridView5.DataBind();*/
}
private void gridsentitem()
{
//SqlCommand cmd = new SqlCommand("SELECT
date,time,subject,receiver FROM mail WHERE sender='" + str + "'", con);
//SqlDataAdapter da = new SqlDataAdapter(cmd);
//DataTable dt = new DataTable();
//da.Fill(dt);
//con.Close();
//GridView3.DataSource = dt;
//GridView3.DataBind();

{
/*Panel3.Visible = true;
//gridsentitem();
SqlCommand cmd = new SqlCommand("SELECT
date,time,subject,receiver, body FROM mail WHERE sender='" + str + "'",
con);
da.Fill(dt);
con.Close();
GridView5.DataBind();*/
}
}
Sent Item Page
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class sentitem : System.Web.UI.Page

{

ConnectionString);
SqlCommand cmd = new SqlCommand();
string str = "";
{
str = Session["email"].ToString();
cmd.Connection = con;
}
private void gridinbox()
{
date,time,subject,receiver,body FROM mail WHERE sender!='" + str + "' ",
con);
da.Fill(dt);
con.Close();
}
{
Panel2.Visible = true;
//gridsentitem();
date,time,subject,receiver, body FROM mail WHERE sender='" + str + "'",
con);
da.Fill(dt);
con.Close();
}
}
Admin LogIn
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class adminlogin : System.Web.UI.Page

{
{
}
{
string a = "";
string b = "";
ConnectionString);
SqlCommand cmd = new SqlCommand("select * from login where
name='"+TextBox1.Text+"' and password='"+TextBox2.Text+"'",con);
con.Open();
SqlDataReader dr = cmd.ExecuteReader();
while (dr.Read())
{
a = dr[0].ToString();
b = dr[1].ToString();
}
if (a == TextBox1.Text.Trim() && b == TextBox2.Text.Trim())

{
Session["email"] = TextBox1.Text;
Response.Redirect("ComposeMail.aspx");
}
else
{
Response.Write("unsuccessful login");
}
}
}
Testing
TESTING
Testing is a process, which reveals errors in the program. It is the major quality
measure employed during software development. During testing, the program is
executed with a set of conditions known as test cases and the output is evaluated to
determine whether the program is performing as expected.
In order to make sure that the system does not have errors, the different levels of
testing strategies that are applied at differing phases of software development are:
Levels of Testing:
Testing execute program with the aim to finding error. A good test is one which
uncover a new error with a high degree of probabilities. A successful test is one
which find an error not yet discovered
We have to prepare the test cases to test the software. This is done to check the
complete functionalities of the system----Black Box testing
The internal working of the code, logic, path, loops etc.--- White Box testing
Module1 module2 module3
Units Units Units
i/P integration o/p i/p integration o/P

System Testing: Presentation +business + database
UAT: user acceptance testing
TYPES OF TESTING
Unit Testing
Unit Testing is done on individual modules as they are completed and become
executable. It is confined only to the designer's requirements.
Unit testing refers to tests that verify the functionality of a specific section of code,
usually at the function level. In an object-oriented environment, this is usually at
the class level, and the minimal unit tests include the constructors and destructors.
[23]
These types of tests are usually written by developers as they work on code (white-
box style), to ensure that the specific function is working as expected. One function
might have multiple tests, to catch corner cases or other branches in the code. Unit
testing alone cannot verify the functionality of a piece of software, but rather is
used to ensure that the building blocks of the software work independently from
each other.
Unit testing is a software development process that involves a synchronized
application of a broad spectrum of defect prevention and detection strategies in
order to reduce software development risks, time, and costs. It is performed by the
software developer or engineer during the construction phase of the software
development lifecycle. Unit testing aims to eliminate construction errors before
code is promoted to additional testing; this strategy is intended to increase the
quality of the resulting software as well as the efficiency of the overall
development process.
Depending on the organization's expectations for software development, unit

testing might include static code analysis, data-flow analysis, metrics analysis, peer
code reviews, code coverage analysis and other software testing practices.
Each module can be tested using the following two strategies:
Black Box Testing
In this strategy some test cases are generated as input conditions that fully execute
all functional requirements for the program. This testing has been uses to find
errors in the following categories:
a) Incorrect or missing functions

b) Interface errors
c) Errors in data structure or external database access
d) Performance errors
e) Initialization and termination errors.
In this testing only the output is checked for correctness. The logical flow of the
data is not checked.
White Box testing
In this the test cases are generated on the logic of each module by drawing flow
graphs of that module and logical decisions are tested on all the cases.
It has been uses to generate the test cases in the following cases:
a) Guarantee that all independent paths have been executed.

b) Execute all logical decisions on their true and false sides.
c) Execute all loops at their boundaries and within their operational
bounds.
d) Execute internal data structures to ensure their validity.
Integrating Testing
Integration testing ensures that software and subsystems work together as a whole.
It tests the interface of all the modules to make sure that the modules behave
properly when integrated together.
System Testing
Involves in-house testing of the entire system before delivery to the user. Its aim
is to satisfy the user the system meets all requirements of the client's specifications.
Acceptance Testing
It is a pre-delivery testing in which entire system is tested at client's site on real

world data to find errors.
Validation
The system has been tested and implemented successfully and thus ensured that all
the requirements as listed in the software requirements specification are completely
fulfilled. In case of erroneous input corresponding error messages are displayed.
Compilation Test:
It was a good idea to do our stress testing early on, because it gave us time to fix
some of the unexpected deadlocks and stability problems that only occurred when
components were exposed to very high transaction volumes.
Execution Test:
This program was successfully loaded and executed. Because of good

programming there was no execution error.
Output Test:
The successful output screens are placed in the output screens.
19 PERT CHART
A PERT chart is a project management tools used to schedule, organize, and
coordinate tasks within a project. PERT stands for Program Evaluation Review
Technique. A PERT chart presents a graphic illustration of a project as network
diagram consisting of numbered nodes(either circles or rectangles) representing
events, or milestones in the project linked by labeled vectors (directional lines)
representing tasks in the project. The direction of the arrows on the lines indicates
the sequence of tasks.
Alpha Testing
SRS And Design

Programming Beta Testing
3 5 8 10
10 15 30 10 10
1 2
4 6 7 9 11
3 10 10 10 5
Buy Hardware Writing

Manuals User Test
User
Requirement
Installation Training
And Analysis
Gantt chart
Gantt Chart is also known as Time Line Charts. A Gantt Chart can be developed
for the entire project or a separate chart can be developed for each function. A
tabular form is maintained where rows indicate the tasks with milestones and
columns indicate duration (weeks/months). The horizontal bars that spans across
columns indicate duration of the tasks.
January February March April

Requirement
Gathering
Design
Test Cases
Coding
Testing
Build
Error Handling
Error handling in ASP.NET has three aspects:
 Tracing - tracing the program execution at page level or application level.
 Error handling - handling standard errors or custom errors at page level or

application level.
 Debugging - stepping through the program, setting break points to analyze

the code
To understand the concepts, create the following sample application. It has a label
control, a dropdown list, and a link. The dropdown list loads an array list of
famous quotes and the selected quote is shown in the label below. It also has a
hyperlink which has points to a nonexistent link.
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs"

Inherits="errorhandling._Default" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>
Tracing, debugging and error handling
</title>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:Label ID="lblheading" runat="server" Text="Tracing, Debuggin
and Error Handling">
</asp:Label>
<br /> <br />
<asp:DropDownList ID="ddlquotes" runat="server"

AutoPostBack="True" onselectedindexchanged="ddlquotes_SelectedIndexChanged">
</asp:DropDownList>
<br /> <br />
<asp:Label ID="lblquotes" runat="server">

</asp:Label>
<br /> <br />
<asp:HyperLink ID="HyperLink1" runat="server"

NavigateUrl="mylink.htm">Link to:</asp:HyperLink>
</div>
</form>
</body>
</html>
The code behind file:
public partial class _Default : System.Web.UI.Page

{
{
if (!IsPostBack)
{
string[,] quotes =
{
{"Imagination is more important than Knowledge.", "Albert
Einsten"},
{"Assume a virtue, if you have it not" "Shakespeare"},
{"A man cannot be comfortable without his own approval", "Mark
Twain"},
{"Beware the young doctor and the old barber", "Benjamin
Franklin"},
{"Whatever begun in anger ends in shame", "Benjamin Franklin"}
};
for (int i=0; i<quotes.GetLength(0); i++)

ddlquotes.Items.Add(new ListItem(quotes[i,0], quotes[i,1]));
}
}
protected void ddlquotes_SelectedIndexChanged(object sender, EventArgs e)

{
if (ddlquotes.SelectedIndex != -1)
{
lblquotes.Text = String.Format("{0}, Quote: {1}",
ddlquotes.SelectedItem.Text, ddlquotes.SelectedValue);
}
}
}
Error Handling
Although ASP.NET can detect all runtime errors, still some subtle errors may still
be there. Observing the errors by tracing is meant for the developers, not for the
users.
Hence, to intercept such occurrence, you can add error handing settings in the
web.config file of the application. It is application-wide error handling. For
example, you can add the following lines in the web.config file:
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">

<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
</system.web>
<configuration>
The <customErrors> section has the possible attributes:
 Mode : It enables or disables custom error pages. It has the three possible
values:
o On : displays the custom pages.
o Off : displays ASP.NET error pages (yellow pages)
o remoteOnly : It displays custom errors to client, display ASP.NET

errors locally.
 defaultRedirect : It contains the URL of the page to be displayed in case of

unhandled errors.
To put different custom error pages for different type of errors, the <error> sub
tags are used, where different error pages are specified, based on the status code of
the errors.
To implement page level error handling, the Page directive could be modified:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs"

Inherits="errorhandling._Default" Trace ="true" ErrorPage="PageError.htm"
%>
Validation Check
Whenever we have an application that expects user input, then it becomes

important to ensure the validity of the data input by the user. We might have
scenarios when some data is mandatory for the user to enter. There are scenarios
when the user data has to be in some particular format example email ID. There
could be scenarios when we want the data to be in some range example date input.
So for all the above mentioned scenarios, if we take the user input without
validation, then chances are that we will end up having wrong data with us
(perhaps in database). If it is a bad day for us then possibly our application might
also end up behaving in an unexpected manner and even crash on us (like if we try
to convert a non numeric string to int). Worst case scenario, the user will use the
input field to perform SQL injection and cause serious damage to our database. So
it is always a good idea to have validation in place whenever we are taking input
from the user.
Types of Validation
There are two ways we can perform validation:
Client side validation

Server side validation
Client Side Validation
Client side validation
It is something that will happen on users' browser. The validation will occur before
the data gets posted back to server. It is a good idea to have client side validation as
the user gets to know what needs to be changed immediately, i.e., no trips to
servers are made. So from the users' point of view, it gives him fast response and
from the developers' point of view, it saves valuable resources of server.
JavaScript is most widely used to perform client side validation. From decades,
developers have been using JavaScript for client side validation. It is always a
good idea to have knowledge of JavaScript as it gives us full control over client
side validation. Now Microsoft is also embracing jQuery in its current versions so
perhaps JavaScript and/or Jquery should be the right thing to use for client side
validation.
Server Side Validation
Server side validation occurs at server. The benefit of having server side validation
is that if the user somehow bypasses the client side validation (accidentally or
deliberately), then we can catch the problem on the server side. So having server
side validation provides more security and ensures that no invalid data gets
processed by the application.
Server side validation is done by writing our custom logic for validating all the
input. ASP.NET also provides us some controls which will facilitate the server side
validation and provides a framework for the developers to do the same.
Validation Controls in ASP.NET
The validation controls provided bt ASP.NET are:
RequiredFiledValidator –
This validation control will be used when we are mandating the user input for any
particular field. Let's say we have a simple form with name field and we don't want
this to be empty. so what we can do is add a Required Field Validator to the page,
set the ControlToValidate to the ID of the name input field, set the error message
property.
CompareValidator-
This control will compare the value of

its ControlToValidate with ControlToCompare. It uses the comparison operators to
do the same. Now let us say we have a hypothetical scenario where we want the
same name to be entered twice (not so hypothetical if it would be password) then
we can have a CompareValidator in place with the following properties:
RangeValidator-
In scenarios where we want to ensure that the value entered by the user is in some
predefined range, we can use this control.
RegularExpressionValidator-
RegularExpressionValidator comes in handy when we want input data to be in

some specific format. Let us try to do that on our page by asking the user for his
email ID.
CustomValidator-
If with all these validation controls provided by ASP.NET, we still find ourselves a
scenario where we need customized validation behavior, we can use
the CustomValidator Control. Let us try to use this control and perform custom
client side as well as server side validation. What we will do is we will check for '-'
character in user input and reject the input if '-' is present in any field (assuming a
SQL injection attempt). So let us see how can we use CustomValidator for it.
ValidationSummary
- Although we can do all the client side and server side validations ourselves using
JavaScript and server side code, we could find the validation controls provided by
ASP.NET useful in many scenarios. These validation controls give us the
flexibility of validating on client side or server side. We can use
the ValidationGroup,Page.IsValid properties and Page.validate method to have fine
grained control on the validation process.
All these validation have n=been applied in the project.
CONCLUSION & FUTURE SCOPE

Conclusion: The application was tested and implemented successfully. The system
behavior was found to be as expected in the problem definition. By this application
employees in the organization can easily update their day to day work and they can
easily clarify their doubts and get the information what ever he want for example
details of their other employees and can view different documents and Articles
what are available and they can post and update their own Articles and documents
and by this department heads or who are super users get the details of employees
and their daily work progress and status of work assigned and details So by this
The Employees can now use the online system to do their usual work in the office.
Future Scope:
Additional Features like biometric authentication while logging in can be done in

the Project. Biometric techniques like fingerprint recognition, Eyes recognition are
most suitable for project. Facility of video conferencing can be done between
members. A service of messaging on mobile phone can be facilitated so that
updates can be sent on mobile phones.
BIBLIOGRAPHY
 FOR .NET INSTALLATION
www.support.mircosoft.com
 FOR DEPLOYMENT AND PACKING ON SERVER

www.developer.com
www.15seconds.com
 FOR SQL
www.msdn.microsoft.com
 FOR ASP.NET
www.asp.net
www.asptoday.com
www.aspfree.com
 REFERENCE BOOKS
Evangelous Petereous, “C#.NET Black Book”.

Roger S.Pressman, “Software Engineering”.
Jain, “SQL FOR PROFESSIONALS”.
Wrox, “Professional ASP.NET”.

Intranet Mailing in Virtual Office

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Intranet Mailing in Virtual Office

Uploaded by

Copyright:

Available Formats

SESSION- 2017-18

INTRANET MAILING IN VIRTUAL OFFICE

Dr. Mazhar Khaliq Mr. Chandra Bhushan Verma

Computer Science/ (Analyze Infotech)

In Partial Fulfillment of the requirements for the award of the degree

Besides, I would like to thank the authority of “ Khwaja Moinuddin Chishti

1. Title of the Project

9. Introduction of Microsoft Visual Studio

10. Introduction of Microsoft SQL Server

11. Introduction of HTML

13. Preliminary Investigation

14. Software Engineering Paradigm

15. S/W & H/W Requirement

16. System Design

17. 0 level D.F.D

18. 1 level D.F.D

19. E-R Diagram

21. Table of Information

22. Interface Design

25. GANT chart

26. PERT chart

27. Error Handling

28. Validation Check

29. Future scope

The ‘VIRTUAL OFFICE’ mainly consists of eight modules Administrative

E-forum is discussion software allows people from within a corporation to

Project management module gives employees task status reports. We can

The Proposed system has following main modules-

The ‘VIRTUAL OFFICE’ mainly consists of eight modules

 Project management module

 Documents library and lastly Logout

Login module consists of Login Registration, Changing password, Password

E-forum is discussion software allows people from within a corporation to

Project Management Module

Document library module contains the list of documents available in document

2. Document Description - a brief description of the contents of the document.

Document categories are used simply to facilitate searching by dividing the

VIRTUAL OFFICE is an Enterprise Intranet Application that automates and

Database with some constraints basing on his designation.

Administration processes are simplified allowing more time for management of

resources. This project information will assist management in ensuring that

benefits for an organization that opts to follow a standardized Process or method

• It provides a consistent approach to projects in an organization

• The project success rate is increased, ultimately saving costs

• It raises the skill of project managers in the organization

• A common knowledge base is created reducing project risks.

 Employee can login with his id and password.

 Seeking a low-risk alternative to renting a conventional office;

The Portal Administrator role would typically be allocated to an individual

Virtual office contains a documentation repository per project and a general

Costs are also dependant on:

• Implementation assistance required

• Amount of disk space required

• System administration services

• Hosting requirements (on-site hosting is available)

 The main objective is to automate non computer environment

Conceptually, requirements analysis includes three types of activities

 Eliciting requirements :(e.g. the project charter or definition), business process

 Recording requirements: Requirements may be documented in various forms,

 Documenting dependencies. Documenting dependencies and interrelationships

The application will follow three-tier architecture. In three-tier architecture

Three-tier architecture will contain the following tiers

DEFINATIONS,ACRONYMS & ABBREVATIONS

 Asp: Active server pages is used to develop web application