Report

Intranet Web Mail System 1
Abstract:
1. Introduction
1.1. Introduction to project
1.2. Why web based claim processing system?
1.3. Overview of project
2. System Analysis
2.1. Initial Investigation
2.2. Purpose of System
2.3. Present System
2.4. Disadvantages of present system
3. Proposed System
3.1. Object of proposed system
3.2. Advantages of Proposed System
3.3. Feasibility Analysis
4. Requirement
4.1. Hardware Requirement
4.2. Software Requirement
5. System Designs
5.1 Introduction
5.1.1 System Design
5.1.2 Logical Design
5.2. DFD (Data Flow Diagram)
5.3. ER-Diagram
5.4. Tables
6. Developing Tools
6.1. Front End
6.2. Back End
7. Coding & Testing
8. Snap shots & Screen shots
9. Feature enhancement
10. Conclusion
11. Reference
Abstract:
The project entitled INTRANET WEB MAIL SYSTEM is to
provide an efficient inter and intra department communication facility in the organization.
It consists of the modules Administrator, Registered User Login, Mail Box Module, and
Address Module. New User Signup form validates whether the user-id already exists and
also validation is done for all the fields in the form. Registered User login is also aptly
validated for the user-id, and password. The user must have an account to use the mailing
facilities provided by the system.
INTRANET WEB MAIL SYSTEM consists of inbox, composes,

address book, sent item, delete item, draft, spam, calendar, search mail and create folder
and Logout etc. Whatever the user needs he/she can just select the necessary option.
Inbox shows the number of mails and their status, that is whether it is new or read.
Compose allows us to send the message and also it has the facility to save the sent
messages as draft. Deleted item shows the emails can be deleted in the database. Address
book is used to store the important address. Calendar has the facility to add events and
add tasks and search events. Remainder can be set for adding events of particular dates.
Logout allows him/her to quit the service of the system.
Problem Statement:
The registered users should be able to login to the mail box and
manage the mail box. The administrator should be able to manage access and
authorizations of the users. New users should be able to register and create their account.
1.In
1.1 1
The project entitled INTRANET WEB MAIL SYSTEM is to
provide an efficient inter and intra department communication facility in the
organization. It consists of the modules Administrator, Registered User
Login, Mail Box Module, and Address Module. New User Signup form
validates whether the user-id already exists and also validation is done for all
the fields in the form. Registered User login is also aptly validated for the
user-id, and password. The user must have an account to use the mailing
facilities provided by the system.
INTRANET WEB MAIL SYSTEM consists of inbox, composes,

address book, sent item, delete item, draft, spam, calendar, search mail and
create folder and Logout etc. Whatever the user needs he/she can just select
the necessary option. Inbox shows the number of mails and their status, that
is whether it is new or read. Compose allows us to send the message and also
it has the facility to save the sent messages as draft. Deleted item shows the
emails can be deleted in the database. Address book is used to store the
important address. Calendar has the facility to add events and add tasks and
search events. Remainder can be set for adding events of particular

dates. Logout allows him/her to quit the service of the system.
The motivation behind this project is to create an indexing structure
that optimizes cluster related queries for use in all kind of databases. Modern
multimedia databases typically offer the ability to query sound files based on
proximity to a given sound file. The measure of distance used is often
Euclidean distance within some small feature space of the sound files, or may
be a more complicated notion of distance based on more computationally
expensive comparisons between sound files.
However, the notion of distance used is almost always predefined, and

independent of the data. Yet knowing how a given data point relates to other
data points in the database can often yield insight into what data points should
be considered similar. In many circumstances, it is advantageous to report
points in the same cluster as being closer than points in other clusters, even if
some points in other clusters.
Computationally expensive data mining operations allow users to

classify data into clusters. However, these operations require several passes
through data, and Classifications can be made obsolete when data is inserted,
deleted, or modified.
We would prefer if the greatest possible degree of intermediate results

were retained with the database, so that future clustering operations could
take advantage of computations performed by earlier clustering operations.
As a response to these needs, we developed two indexing schemes that
facilitate cluster based queries. Even though the original idea for this project
was related to indexing large databases of sounds, the indexing

schemes that we developed are appropriate for indexing any other kind of
data provided that the appropriate features are extracted.
Keyword and advanced search features allow users to search the entire
database or look for information in specific categories which meet their
specified criteria. Advanced search features provide additional criteria
features. Easy navigation provides users with quick access to browse ads
within categories and jump to any other category throughout the site.
In this project took care of adding the documents of each sections like,
doc files, txt files, jpg files, gip files, MPEG files, bmp files, etc, also took
care that only the user who register to our site will be permitted to add the
documents.
In today's modern, sophisticated and fast world, online classifieds have

become a medium of communication among the internet users. On one end it
is informative and on the other end it is convenient and cost effective. In this
scenario, the online classified websites have occupied one among the top
ranking sites on the intranet due to its vast popularity among the users.
1.2 WHY ??
Finding information
Staff have consistently told us that it is complex and time consuming to find
University-wide information they need to complete administrative tasks.
All staff-focused information is on the general website, mixed in with

content for students, visitors, external partners and our many other
audiences. It has grown organically over a long period, leading to a site
overflowing with information that is grouped by organisational structure
rather than by the topics staff would logically look for.
Information is presented in many different ways and the language used is

often technical or heavy in jargon. By reviewing and reorganising this
content in a discrete staff-focused intranet, it will be easier to find
information and complete tasks, giving staff more time to focus on their
core work.
The inclusion of staff information on the website also makes it confusing for
our other web visitors. The Universitys website has millions of visitors each
month and is an important communication tool for our organisation. In 2011
a web strategy project defined a road map for the future development of
the University website, the first step of which was to move the staff
information out into an intranet. This will free the website up to focus on the
other audiences.
Communication and community development

In the absence of an intranet, there is a heavy reliance on email as the
primary method to communicate with staff. While news is published on,
and linked from, the Staff and Careers web page, an intranet would provide
greater scope for publishing important notices, targeted staff-related news
and more in-depth articles, giving these communications a higher profile
and increasing readership and engagement. It could also provide a space
for more social communication, contributing to developing the University
community and culture.
Collaboration
Increased cross-organisational collaboration is an important strategic
objective for the University. There is a genuine will to facilitate greater
working relationships between academic disciplines as well as
administrative departments, to make better use of our expertise in
achieving our goals, from research outcomes to cost savings. There is a
need to define what is meant by collaboration, at a University-wide and
project or local level, and what the intranet can do to support this.
Leadership
While most faculties have some form of intranet, staff in faculties have told
us that it would be very useful to have greater guidance on what makes a
good intranet. This would include what features it should have, what
content it should contain, how it should be structured, how it should be
managed on an ongoing basis and what platform it should use. A
University-wide intranet should provide this model, and should also have
the capability for faculties to develop their own subsets of the main intranet
where they can include local information and collaborative spaces.
1.3. Overview of project:

The project Intranet web mail system is a complete solution for
Organization without paper. The motivation behind this project is to
create an indexing structure that optimizes cluster related queries for
use in all kind of databases. Modern multimedia databases typically
offer the ability to query sound files based on proximity to a given
sound file. The measure of distance used is often Euclidean distance
within some small feature space of the sound files, or may be a more
complicated notion of distance based on more computationally
expensive comparisons between sound files.
However, the notion of distance used is almost always

predefined, and independent of the data. Yet knowing how a given data
point relates to other data points in the database can often yield insight
into what data points should be considered similar. In many
circumstances, it is advantageous to report points in the same cluster as
being closer than points in other clusters, even if some points in other
clusters.
Considering a music database, the user can make title related
queries or singer related queries but he or she may also need to look for
music entries of a certain (unknown) category. Computationally
expensive data mining operations allow users to classify data into
clusters. However, these operations require several passes through data,
and Classifications can be made obsolete when data is inserted, deleted,
or modified. Furthermore, any computation performed by traditional
clustering algorithms is lost as soon as additional records are inserted
into the database.
We would prefer if the greatest possible degree of intermediate
results were retained with the database, so that future clustering
operations could take advantage of computations performed by earlier
clustering operations. As a response to these needs, we developed two
indexing schemes that facilitate cluster based queries. Even though the
original idea for this project was related to indexing large databases of
sounds, the indexing schemes that we developed are appropriate for
indexing any other kind of data provided that the appropriate features
are extracted.
Its users can capture patient demographics, schedule
appointments, perform billing tasks, and generate reports using it. In
the manual system lot of manpower is wasted to keep track of the
different transactions and documents. Existing system is time
consuming and difficult to use. In order to overcome these limitations
we find the solution that is Intranet web mail system .
With the Intranet web mail system , this application can minimize
administrative bureaucracy while maximizing the Organization value.
It saves the time to manage documents and spend more of their time
for other work, and less time on the administration and management
that comes with a successful practice. This software is easy to set-up
and in just a few days you can reap the benefits of a paperless
management system.
2.System Analysis:
2.1. Initial Investigation

The investigation is one way of handling this project. The
objective is to determine whether the request is valid and feasible before a
recommendation is reached to do nothing, improve or modify the existing
system, build a new one. The user request identifies the need for change and
authorises the initial investigation . it may undergo several modifications
before it becomes a written commitment.
Once the request is approved the following activities are

carried out: Background investigation, fact- finding and analysis,
presentation of results- called project proposal.
Background Analysis:
once the project is initiated, the analyst begins to learn about the
setting, the exesting system , and the physical processes related to the revised
system. For example , it is important to structure of the bank, who runes it;
who reports to whom in the safe deposit area; the relationship between safe
deposit and the teller line, accounting , accounting and customer service and
the nature, frequency, and level between safe deposit staff and these
departments.
Fact-finding:
After obtaining this background knowledge, the analyst begins to collect
data on the existing system output, input, and costs. The tool used in data
collection are:
1. Review of written documents
2. On-site observation
3. Interviews.
4. Questionnaires.
2.2 Proposed System:

In case of the proposed system all the facilities provided are
the same as in case of the existing system but the proposed system provides all the
functionalities. Electronic mailing system sends the mails spontaneously without
requiring the parties available at same instant. Proposed System is implemented in
order to deliver the most effective and efficient system to the users. The time
consuming is less as it is online. It is proposed to make the system extremely user
friendly with well- designed screens and limited inputs. It is also proposed to include
the list of value boxes and grid structures in the screen to make data retrieval very
easy and convenient.
2.3. Present System:

Present system is manual. In the manual system
lot of manpower is wasted to keep track of the different
transactions. Existing system is time consuming and difficult to
use. This manual system will take time to pass the information
and sometime it causes lost of information .This causes lost of
employee time also. There is no central database from where
one can get different statistical data at one place.
In case of the proposed system all the facilities provided are the
same as in case of the existing system but the proposed system provides all
the functionalities without the use of papers and in a single directory. This
system is developed and implemented to do the activities very quickly and
easily. Hence it is simpler and efficient.
Proposed System is implemented in order to deliver the
most effective and efficient system for the Organization. The time
consuming is less as it is online. The system is flexible enough to modify
easily. It is user friendly and attractive for users. It overcomes the major
drawbacks of existing system. But the stretch of Internet is global. Internet
users can view the document of even different countries and the can do what
they wish. Another superiority of online classifieds over the printed media
classified document is the low cost nature of the online classifieds. There are
lots of free websites, which provide the facility of posting or uploading
classified document free of cost. You may post as many classified document
of you wish absolutely free.
There also some paid classified websites with better

moderation quality, which provide you the facility of posting your own
classified documents in exchange of some money. But the cost of publishing
classified document in a print media seems to be greater. There you have to
pay in cost per column basis. So the expanse rises. The online classified
websites also providing more space to write the docs and the fonts are bigger
and more readable in websites than the print
2.4. Disadvantages of present system:

1. In purposed system manpower is wasted to keep track of the
transactions.
2. It is time consuming as compared to the proposed system.
3. Very difficult to maintain all the information manually.
4. There is no security on the incoming and outgoing transactions.
5. No backup of inboxes for respective users.
3.Proposed System:
3.1. Object of proposed system
Our Application Mainly Deals with Many Tasks

Login / Sign out
Uploading the files/photos
Displaying all Details of employees
Insertion of new Employee/Claim
Searching the documents by keywords or search by category wise.
Action for the claims
Edit the Employee/Claim.
Delete the Employee/Claim.
Editing personal informations
Deleting particular users etc
3.2. Advantages of Proposed System
1. Using this project we can have all document Information and

the Organization Information.
2. Through this software we can search Documents and also
number of users using this and also Admin able to see how many
users and how many in the managers are using this.
3. To create well structured database for the WCPS System.
4. To create user-friendly interface, simple to learn and easy to
use.
5. Secure access control and prevents misuse by unauthorized
users.
6. Fully validated to ensure correct and error free Document
entry.
7. Human intervention can be reduced.
8. Time consumption is less.
9. In today's modern, sophisticated and fast world, online
classifieds have become a medium of communication among the
internet users. On one end it is informative and on the other end it
is convenient and cost effective. In this scenario, the online
classified websites have occupied one among the top ranking sites
on internet due to its vast popularity among the users.
10. The downfall of the classified section of print media started
after the introduction of television and radio. After the
introduction of Internet it seems the classified websites are
becoming the front-runner in the field of classified advertisements.
11. Now the online aspect of classified documents is highly
praised around the entire globe. This is because of some important
advantages like the global nature of Internet, availability of more
space to write advertisements properly, better keyword based
search option and the user friendliness of the classified websites.
12. Fully automated administrator's interface. The most extensive
admin features of any other system available.
13. Find all documents to edit or delete based on user name or
user email address in the document maintenance admin area.
14. Easily edit or delete admin directly from the user interface by
going to the documents detail pages.
15. Extensive category administration. Easily add, edit or delete
new categories for your system via the browser based category
maintenance tools. Link your new category with an existing
"variable definition file" which defines the data fields available to
your new category. You may also create your own new definition
file containing only the data fields you wish to make available for
that category.
16. System customization is all completed via browser based
tools. Customize the appearance or any other feature of your
system by editing the design configuration file.
3.3 Feasibility Analysis :

Feasibility study consists of activities which determine the
existence of scope of developing an information system to the
organization. This study should be done throughout the life cycle.
Feasibility study starts from the preliminary investigation phase. At this
stage the main work load, the greatest upheaval and the major impact
on the existing system shifts to the user department.
The new system may be totally new, replacing an existing manual
or automated system or it may be a major modification to an

existing system. Proper implementation is essential to provide a reliable
system to meet the organization requirements. Successful
implementation may not guarantee improvement in the organization
using the new system, but improper installation will prevent it.
The process of putting the developed system in actual use is
called system implementation. This includes all those activities that
take place to convert from the old system to the new system. The
system can implement only after thorough testing is done and if it is
found to be working according to the specifications. The system
personnel check the feasibility of the system.
The most crucial stage is achieving a new successful system and
giving confidence on the new system for the user that it will work
efficiently and effectively.
It involves careful planning, investigation of the current system

and its constraints on implementation, design of methods to achieve the
changeover. The more complex the system being implemented, the
more involved will be the system analysis and the design effort required
for implementation. There are many issues involved feasibility study as
followed.
Technical feasibility
Operational feasibility
Economical feasibility
Legal feasibility
>Technical feasibility: is concerned with the availability

ofhardware and software required for the development of the system.
>Operational feasibility: is the is all about problems that may

arise during operations other issues related to operational feasibility are
information, response time, accuracy, security, services and efficiency.
>Economic feasibility:is the measure of cost effectiveness of the
project. i.e. judging whether the possible benefit of solving the problem
is worthwhile or not. Legal feasibility studies issues arising out of the
need to the development of the system.
> Legal feasibility : plays a major role in formulating contracts

between vendors and users. If the ownership of the code is not given to
the user, it will be difficult to install it without proper permission to
other systems.
4.REQUIREMENTS
3.1 Hardware Requirements:

Disk capacity : 80 GB Hard disk
Operating System : XP/Vista
RAM Capacity : 2 GB
Processor : Pentium IV or above
4.1 SOFTWARE REQUIREMENT

SPECIFICATION
Purpose
The purpose of SRS document is to describe the requirements
needed to develop Intranet Web Mail System software application. This document will
provide a general description of the product, product perspective, and general constraint.
It will also provide specific requirement and functional needs for this project such as
interface, functional and performance requirements.
Scope:
It gives total security for us
An unauthorized user can't allowed to see our messages
Intra mail system is it's security feature allowing only registered users to
access the system and preventing any hackers, unauthorized users
Definition, Acronyms and Abbreviation
SRS: Software Requirement Specification
Developers Responsibilities Overview

The developer is responsible for:
1. Designing the Intranet Web Mail System
2. Implementing the System
3. Testing the System
4. Installing the system.
5. Maintaining the system.
6. Explaining the working of the System to the Users
7. Demonstrating the working of the System to the Users
General Description
Product Perspective
1. The product is a DOT NET application. It will therefore require the
Presence of DOT NET environment only on the server not on the
Client machine
2. Software products are software systems delivered to the customers

with the documentation, which describes how to install and use the
system.
Product Functions
1. There are two types of users
i. Administrators
ii. Authorized (Registered) Users
2. Admin has authority to create new user, update or delete existing user.
3. It also has permission to view all users mailbox, send new mail, and delete
existing mails and other mailbox management functions
4. Have the access to the System through proper combination of the user id &
password and can access desired pages and forms
5. In Mail Box Module the registered user can check number of mails and send
messages through compose mail
6. The user can search emails and add events and tasks and also edit or delete
personal information and facility to create folders
7. Reminder can be set for adding events of particular dates
8. In Address Module the registered user can add or edit or delete contacts in the
system. It helps to store important contacts in the system
User Characteristics
In general the users must have knowledge of operating
Windows environment based application software packages. Basic computer knowledge
of using keyboard, mouse, and common windows environment are required user
characteristics.
Assumptions and Dependencies

i. It is assumed that user has basic knowledge of computer operations including
input and output handling.
ii. Care is taken so that even a wise can easily operate the system and obtain
the services provided by it.
Specific Requirements Inputs and Outputs

The user logs into the system and operates as the instruction is
specified and logs out when work is completed.
Functional Requirements
The functional requirements for a system describe the
functionality or services that the system should provide. This may deal with questions like
how the user will login to the system and how the system should behave in particular
situations.
External Interface Requirements

User Interface
Every user should be comfortable of working with computer
and net browsing. He must have basic knowledge of English too.
Software Interface:
The main software interfaces used in the system are forms,
menus and buttons. In case of errors, appropriate message will be displayed on the web
form.
Performance Requirements:
The proposed application needs to fulfill the requirements of all
users and produce accurate results. It should be reliable.
Software Requirements:
i. Technology : .Net
ii. Front End : C#, Dot net framework 2.0, ASP.Net
iii. Back End : MS SQL Server 2005
Security Requirements:
Only the authorized users are allowed to use the system by
supplying appropriate login credentials.
5.System Designs:
1.Introduction:
5.1.1SYSTEM DESIGN:
The object oriented analysis and design of any problem consist of
building a model of non application domain and then adding implementations details to it
during the design of the system. This approach is known us OMT(Object Modeling
Technique) which is four stages,
o Analysis
o System design
o Object design
o Implementation design
Analysis:
The results are object and dynamic and functional model.
System design:
The results are a structured of the basic architecture of the system
along with the high level strategy decisions.
Object design:
This phase produces a design documents, consisting of detailed

objects static, dynamic and functional models.
Implementation design:
This activity produces reusable, exendible and robust code.
5.1 Context diagram
Admin
Display the
Intranet Login screen
Web Mail based on
System the login
User
Data base
Software design is a process through which requirements

are translated in to a representation of software. Initially the
representation depicts a holistic view of software. Subsequent
refinement leads to a design representation that is very close to source
code.
Since we are following an Object oriented Design
technique, the next step towards the development is to identify the
classes and their relationships. A class is a description of an object type.
Instances of classes are known as Objects. UML also provides tools for
designing the system. Class diagrams enable us to establish relationship
among various classes of the system. Before proceeding on to develop
class diagrams, the next step is to identify the potential classes in the
system. Some of the basic tips in identifying the classes are:
Analyzing the requirement statement.
Use Cases.
Application experts.
Studying the system.
By following these simple rules during the initial

process of analyzing, several classes get formulated. These classes are
referred to as candidate classes and they represent the possible classes
in a given system. It is not essential to incorporate all the identified
candidate classes; some of them may also be dropped and are called
unfit candidate classes.
A class icon is a rectangle with three sections in it. Horizontal

lines across the rectangle divide the sections. The first section is where
the class name is mentioned. In the second section the attributes or data
members of the class and in the third section the methods or functions
of the class are mentioned. A class diagram thus takes the form.
In DFD the cardinality or multiplicity can be expressed at the ends of
the association at the class where it is applicable. Whenever there is no
mention of the cardinality then one is considered.
With the help of DFD, we designed the class diagram of our system,
which looks like the following. The cardinality among the relationship is
also mentioned.
Based on the user requirements and the detailed analysis of a new
system, the new system must be designed. This is the phase of system
designing. It is a most crucial phase in the development of a system.
Normally, the design proceeds in two stages:
Preliminary or general design
Structure or detailed design
Preliminary or general design:

In the preliminary or general design, the features of the new system
are specified. The costs of implementing these features and the benefits to be
derived are estimated. If the project is still considered to be feasible, we
move to the detailed design stage.
Structure or Detailed design:

In the detailed design stage, computer oriented work begins in earnest.
At this stage, the design of the system becomes more structured. Structure
design is a blue print of a computer system solution to a given problem
having the same components and inter-relationship among the same
components as the original problem. Input, output and processing
specifications are drawn up in detail. In the design stage, the programming
language and the platform in which the new system will run are also decided.
5.1.1 Logical Design:
The steps to be followed during physical design are given below:

Designing physical files and database-describes how data will be stored
and accessed in secondary computer memory and how the quality of
data will be ensured.
Design system and program structure-describes the various programs

and program modules that correspond data flow diagram and other
documentation developed in earlier phases of lifecycle.
Designing distributed processing strategies describes how your

systems will make data and processing available to users on computer
networks within the capabilities of existing computer networks.
Depicts various step involved in physical design.

5.2 Data Flow Diagram:

The DFD is a graphical technique that depicts the information flow and
the transforms that are applies as data move from input to the output .The DFD is also
known as Bubble Chart or Data Flow Graphs or Context diagram.
DFD Of Administrator Module

New users Users

details
User information
Login Forgot
Password
Valid User
Administrator
Manage Manage Change Manag

Inbox User Passwor e
d Contac
ts
View/add/ed View/add/edit Change View/add/

it/delete /delete user Settings edit/delet
inbox e contacts
Messages User Users Contacts

DFD Of Registered User Module
Users
New users
details
User information Forgot
Login
Password
Messages Valid User
User
Delete Inbox
d Items
Registered Option
User s
Sent
Items Folders
Spa Create/Delet
m e/Rename /
Searc MoveFolder
Drafts Calenda Conta
h
Compos r cts
Mail
e
Mail
Folder
Add Add Searc
Event Tasks h
Messages Event Add/Edit/
Messages Delete/Vie
w
Contacts
Event
Contacts
5.3 ER-Diagram:
Entity Relationship diagrams depicts data in its rest state-data
stores. An entity is anything real or abstract, which we want to store
data. Most entities correspond to persons, objects, events or locations. It
is represented by relationship symbol, which is a decision box.
Data Relationships:
An entity is a person, place, thing, or event for which data is
collected.
A relationship is a logical link between entities based on how they
interact.
An entity-relationship diagram (ERD) is a graphical model of
the information system that depicts the relationship among system
entities.
Types of Entity
An entity is anything that can be described by data. All business
system captures and store data about various entities and this falls into
four classes. These are persons, objects, locations and events.
The following are the well-defined entities in E-PAY SLIP
AUTOMATION requests for adding, deleting, editing and
authentication
Types of Relationships (Cardinality)
One-to-One (1:1) - This implies a relation between one or more

entities. This is for every occurrence of the first entity there can only be
one related occurrence of the second entity and vice-versa.
One-to-Many (1: M or M: 1) - For one occurrence of one

entity, there can exit many related occurrences of a second entity and
vice-versa. This means that one entity has two or more entities related
to it.
Many-to-Many (M: M)
For one occurrence of first entity, there can exit many related
occurrences of a second entity, and vice-versa and for all occurrences of
the second entity there can exit many occurrences of the first entity.
ER diagram:
DETAILED DESIGN
Introduction
The detailed design mainly focuses on the internal design of the
module or how the specification of the module can satisfy. Detailed design essentially
expands the system design to contain a more detailed description of the processing logic
and data structure so that the design is sufficiently complete for coding. The detailed
design part consists of the program description that explains briefly about the modules.
6.2 Module Design

There will be two levels of users:
1. Administrator (Full Control)
2. Authorized (Registered) Users
Administrator (Full Control) User:

This is the system administrative level which will be able to
change any application settings, as well as maintaining user profiles. Have the
authorization to utilize and access all the features of the system.
Authorized (Registered) Users:
Have the access to the System through proper combination of

the user id & password and can access desired pages and forms.
The project comprises of following modules.

1. Admin Module
2. Login Module
3. Mail Box Module
4. Address Module
Admin Module
Admin has authority to create new user, update or delete
existing user. It also has permission to view all users mailbox, send new mail, and delete
existing mails and other mailbox management functions.
The different functionality provided were:
Manage Inbox
Admin can view or add or edit or delete the inbox that are set to particular
existing registered users.
Manage Users
Admin can view or edit or delete or add the users that are set for respective
inboxes.
Change Password
Admin has authority to change the password of existing user.
Manage Contacts
Admin can view or add or edit or delete the contacts that are set for respective
inboxes.
Login Module
The module is the one, which allows only authorized people
to access the Application. Any person who needs an access to the application is needed to
login in the first step. The user needs to provide his or her login ID and the password. The
password is checked against the one stored in the database. If both the ID and Password
are valid then the user is given access to the application, else he/she is denied from it.
Mail Box Module
Inbox - Displays the number of emails, email contents, status (open or

read)
Compose - Allows to compose email and send to the recipients
Deleted item - Shows the emails can be deleted in the database.
Drafts Saves the copy of the email in this folder which are not sent
Sent Items - Shows the sent email items
Calendar The calendar clearly displays all dates, events, tasks and issues
relating to a specific team. It provides automatic reminders about
important dates.It also has the facility to search events.
Search Mail Allows to search mails
Folder Preferences It has facility to create , delete , rename and move
folders for storing important mails in particular folder
Spam It can store large description of mails
Options It has the facility to edit the personal information
Logout - Log off from the email system
Address Module
The module is the one, which displays the information about

the contacts which can be added in the respective users. It has the facility to add / view
/edit / update contacts in the system.
6.3 Use Case Diagrams

A use-case diagram is a graph of actors, a set of use cases enclosed
by a system boundary, communication association between the actors and the use cases,
and generalization among the use cases
Manage Inbox
Send and Receive Messages
Draft
Admin
Spam
Registered User
Manage Contacts
Folders
Options
Calendar (Add Event/Task)
Manage User
Change Password
5.4 Database Design Table:
Descriptions about the Tables created in the database.
1. Table: tbl_user
Column Name Data Type Allow Nulls

emailID varchar(50) Primary Key
(Auto Increment)
Name varchar(25) Null
Password varchar(20) Null
DOB datetime Null
Gender varchar(10) Null
Country varchar(25) Null
Sque varchar(50) Null
Sans varchar(50) Null
2. Table: tbl_contacts

contID Int Primary Key
(Auto Increment)
contName varchar(50) Null
contEmail varchar(50) Null
contDesig Varchar(20) Null
contPhone int Null
3. Table: tbl_usercontacts

usercontactsID Int Primary Key
(Auto Increment)
emailID varchar(255 Null
contID int Foreign Key
4. Table: tbl_event

eventide Int Primary Key
(Auto Increment)
Title varchar(20) Null
Type varchar(25) Null
Description Varchar(3000) Null
Date datetime Null
Location Varchar(20) Null
Sharing Varchar(10) Null
DueDate Datetime Null
Priority Int Null
Status Varchar(25) Null
Comment Varchar(50) Null
Notes Varchar(250) Null
emailID Varchar(150) Foreign Key
5. Table: tbl_messages

msgID Int Primary Key
(Auto Increment)
msgFrom varchar(10) Null
msgTo varchar(50) Null
msgSub Varchar(50) Null
msgCC Varchar(50) Null
msgAttachment Varchar(50) Null
msgDetails Text Null
msgArrivedDate datetime Null
msgSentDate Datetime Null
msgRead bit Null
msgDel bit Null
msgDraft bit Null
msgSpam bit Null
6. Table: tbl_folder

folderID Int Primary Key
(Auto Increment)
folderName varchar(50) Null
Folderin varchar(50) Null
emailID Varchar(50) Foreign Key
6.Developing Tools
Introduction
Implementation is a process of having the systems personnel check out
iles of data needed to use it.
Once installed, applications are often used for many years. However,
both the organisation and users will change and environment will be different over weeks
and months.Therefore, the applications will undoubtedly have to be maintained
modification and changes will be made to the software, files or procedures to meet
emerging user requirements. Since organizations, systems and the business environments
undergo continuous changes , the information system should keep pace. In this sense
implementation is an ongoing process.
To implement this project Intranet Web Mail System we have used

the C#.NET
6.1. Front End:
Active Server Pages is a new technology from Microsoft than enables web server to
process application logic & then deliver standard HTML to the client browser. ASP.NET
is a specification which is used for designing:
i. Web Forms: It is used for designing the web applications which uses HTTP protocols
for sending the request and for receiving the response using the browser.
ii. Web Services: it is a specification to achieve the cross language, cross platform and
cross device integration
Introduction to C#.NET
C# is an integral part of the entire .NET framework. .NET represents

not only a revolution in facilities available for general-purpose Windows programming,
but it will also be the immediate environment seen in .NET code (known as managed
code) when it runs. C# is a genuine object-oriented programming language.
The Microsoft .NET Framework is a software framework that

is available with several Microsoft Windows operating systems. It includes a large library
of coded solutions to prevent common programming problems and a virtual machine that
manages the execution of programs written specifically for the framework. This runtime
environment is known as the Common Language Runtime (CLR). The CLR provides
other important services such as security, memory management, and exception handling.
The class library and the CLR together compose the .NET Framework.
Components of .NET Framework

The .NET Framework consist of Common Language Runtime
(CLR) .NET Framework Class Libraries, known as Base Class Libraries (BCL). The CLR
is at the base is considered as the heart of the .NET Framework. The CLR is a virtual
machine in which all .NET applications and Languages run .NET Framework Class
Libraries include support for everything from file I/O and database I/O to XML and
SOAP. The .NET Framework class libraries are very vast. The BCLs functionality is
available to all languages that use the CLR.
Universal type system called the .NET Common Type System
(CTS). In addition to defining all types, the (CTS) also stipulates the rules that the CLR
follows with regard to applications declaring and using these types. In the world of .NET
and C# everything in the CTS is an object.
It is the engine that drives key functionalities, which include Cross
Languages inheritance, allocation & management of memory, Reference tracking for
object and handle garbage collection. The next generations of standard system service
such as ADO.NET & XML are included in the middle layer. These services are brought
under control of the framework, making them universally available and making their
usage consistence across languages
ASP.NET Windows Forms
Web Web
Control Drawing
Services forms
s s
ASP.Net Application Windows Application

Service Services
. NET Framework Base Classes
ADO.NET XML Threading IO
NET Security Diagnostics ETC..
Common language Run Time
Memory Common Type Life Cycle

Management System Monitoring
ADO.NET
The data access component for the .NET Framework. ADO.NET
is made of a set of classes that are used for connecting to a database. ADO .NET it is able
to create and manage a connection using one of the two connection objects:
SqlConnection: An object that manages a connection to a SQL Server version 7.0 or

later.
OleDbConnection: An object that manages a connection to any data store accessible via
OLE DB.
A typical connection string property might look like the following:
SqlConnection con = new SqlConnection (DataSource=(local); Initial Catalog= database

name; Integrated Security=true);
Opening and Closing Connections
The two primary methods for connections are Open and Close.
The Open method uses the information in the Connection String property to contact the
data source and establish an open connection. The Close method shuts the connection
down.
Methods such as Fill only open and close the connection

automatically if it is not already open. If the connection is open, the methods use it but do
not close it. This gives the flexibility to open and close data commands. In that case, it is
inefficient to have each adapter open and close the connection when we call its Fill
method. Instead of opening the connection, call the Fill method of each adapter, and then
close the connection.
7.4 Implementation of the System:

The request for an operation on the data store and provides the required inputs. For error
encountered in the operation the tool provides the suitable error massage on the screen.
Data Structure:
Con
Provides connection for the SQL server database and of type SqlConnection.
SqlConnection con=new SqlConnection;
Dataset
Provides to retrieve data from the database and store it into the main
memory for further database transaction.
7.4.2 System Calls Used In Programming

Connect ()
Creates a secured connection to the SQL database which then be
used for database transactions like retrieving data and storing the data back in the
database engine. Returns the connection and returns -1 if failed to establish the
connection.
6.2. Back End:
Introduction to SQL Server

SQL Server 2005 (codenamed Yukon), released in October
2005, is the successor to SQL Server 2000. In this substantial upgrade, they've packed the
new database engine full of features. It included native support for managing XML data,
in addition to relational data. For this purpose, it defined an xml data type that could be
used either as a data type in database columns or as literals in queries. XML is converted
to an internal binary data type before being stored in the database. CLR was introduced
with SQL Server 2005 to let it integrate with the .NET Framework.
TEST CASES AND RESULT
Test Case:1 Admin login page

Input : Enter the user name and password, if it matches with the type of the
admin then that particular type of the admin page will be displayed
Otherwise it will not continue
Actual output: Display the admin home page
Result: passed
References: screens 1,3
Test Case:2 New User Registration

Input: Enter the details of the new user with appropriate data types.
Validation is to be done for the each field in the form.
Actual output: One new user record is entered into the data base.
Result: passed
References: screen 2
Test Case 3: Search Mail

Input : If user wants to search mail then enter the word or letter which are in
description of messages
Actual output: Display the list of mails which are available in particular user
Result: passed
Test Case:4 Folder

Input: Enter the folder name and under which folder can be created , deleted
and renamed
Actual output: Display the folders which can be created
Result: passed
Test Case: 5 Personal Information

Input: If user wants to update personal information then user can edit this
data and click on update button.
Actual output: Display the updated personal information
Result: passed
Test Case:6 Add new Event

Input : If user wants to keep remainder of events then user can add the
details of events and it reminds the event of that particular date by sounding
alarm
Actual output: Display the new event can be added and it display the
message and it sounds the alarm
Result: passed
Test Case:7 Add New Contacts

Input: Enter the contact details for storing in the database. Validation is to
be done for each field in the form
Actual output: Display the new contacts can be added and it display the list
of contacts which can be added
Result: passed
7.Coding & Testing

7.1 Coding
The goal of the coding phase is to translate the design of
the system into code in the suitable programming language.
Coding is done in our application keeping in mind some of the
programming standards like a naming conventions and code
indentation with a proper comments in the suitable parts of the
code are followed in this application, so that providing an
update version of the software should be easy and affordable.
7.2 Testing
Testing is a process of operating system or component under

specified conditions, observing or recording the results, and
making an evaluation of some aspect of the system or
component.
Software testing is critical element in software quality
assurance and represents the ultimate review of specification,
design, and coding. The user according to their requirement
does testing of proposed system, which is important other than
testing by developer. The following methods of testing were
carried out to assure the correctness and reliability of proposed
system.
Software testing is a quality assurance function with the
objective of verifying the software design by evaluating the
structural interface and procedure elements. It is actually a
series of different tests whose primary purpose is to fully
exercise the computer based system. Although each test has a
different purpose, all work to verify that all system elements
have been properly integrated and performed allocated
functions.
Testing and Results

Once the source code of the software has been generated,
software must be tested to uncover and correct as many errors
as possible before delivery to the customer. Testing assures the
quality of the software product.
Testing phase involves systematic planning of different

test patterns and test cases to make the product bug-free.
Some of the aspects considered in this phase are internal logic
of the software components, input and output domains,
behavior and performance of the system. During testing, the
system is experimentally used to ensure that the software does
not fail, that is it will run fool-proof according to the way
users expect.
Testing also involves verification and validation (V & V)

of the software product. Verification ensures that we are
building the product right. So verification refers to the set of
activities that run the system with simulated data to ensure that
the software correctly implements a specific function. Where
as validation, which ensures that we are building the right
product, refers to a set of activities of using the software in a
live environment to meet customer needs.
The testing strategies can be broadly divided into two
main categories.
Black box testing is conducted at the interface level. It is
used to demonstrate that the software functions are
operational, input is properly accepted, output is correctly
produced and the software responds positively to the external
environment. Black box testing gives little regard to the
internal logic of the system.
White box testing of software is predicted on close
examination of procedural details. Here, the status of the
program is tested by analyzing the internal logic of the
modules involved.
Testing Strategies
Some of the important testing strategies are as follows:
Unit Testing
It is a white box testing technique, which focuses on
smallest unit of software design the software component or
module. Important control paths have been tested during the
time of coding to uncover errors within the boundary of the
modules. Unit testing ensured that the data properly flows in
and out of the system.
Integration testing
It is a white box testing technique that integrates all the
(unit-tested) modules and examines the software as a whole. It
involves uncovering the errors associated with interfacing of
modules. For example one module can have adverse effect on
another or when they are combined may not produce desired
results. Such errors have been detected and eliminated.
System testing
It is a series of different tests that incorporate all the
system elements like software, hardware, people and
information. Along with the developers, the potential users of
the system fully exercise the newly developed system, to
ensure its expected behavior. All the system elements are
properly put together to meet the desired purpose.
Security testing
This testing technique attempts to verify that proper
security mechanisms are built into the system. Some of the
security features employed in the proposed system are:
Authentication of the user is checked, by verifying the

username and the password while logging into the system.
Unauthorized users are not allowed to access vital information.
Restricted data access is provided to the users depending on

their roles and privileges.
Passwords are stored in an encrypted format.
Database is protected by password and can be accessed only

by DBA.
Validation testing
This black box testing strategy (also known as user
acceptance testing) assures that the software functions in a
manner expected by the user. It validates all the user
requirements. Test data covering all user-defined attributes is
applied in this technique. The proposed system under
consideration has been tested by using this technique and
found to be working satisfactorily. JavaScript technology used
to perform this.
Load Testing
Testing with the intent of determining how well the
product handles competition for system resources. The
competition may come in the form of network traffic, CPU
utilization or memory allocation. The developed system has
successfully passed the load testing.
Functional Testing
This testing refers to the functions that must be

performed after actions or certain events happened. In
Integrated Construction Management System fallowing test
cases are performed to justify that Planning and Stock
Modules are working properly.
8.Snap shots & Screen shots:
USER MANUAL
Screen 1: Login Page
This is our login page. Using user name and password user can
enter into the website. Using this we have provided security to our website. Depending on
their role they will be entered into their respective modules.
Screen 2:New Registration Page

This is our new user page. If the user is not registered to our
website, it will not be permitted to enter into the site. He/she has to register by creating
new user account. Validation is to be done for the necessary field in the form.
Screen 3: Admin Home Page

This is admin module home page. Admin has authority to manage
inbox, user and contacts settings and also to change password settings.
Screen 4:Manage Inbox
Screen 5:Manage Contacts
Screen 6: Inbox Mail

This is the inbox mail where the mails are sent by different users or an
Administrator.
Screen 7: Read Message through Inbox

If user can click this subject link the respected page has been displayed and it can
send reply, reply to all and forward message to different user.
Screen 8: Compose Mail
Screen 9: Save Message in the Draft

Screen 10: Deleted Mails
Displays deleted mails into inbox.
Screen 11: Spam

Displays large description of mails it stored in the spam.
Screen 12: Search Mail

User enters the check word then it searches of those particular users
emails.
Screen 13: Folder Preferences

It can create, delete and rename folders for storing important mails
in that particular folder. Also it has facility to move folder from one folder to other folder.
Screen 14: Options

Displays personal information and folder preferences.
Screen 15: Personal Information

This is a personal information form where user can edit this
information. It displays the updated personal information page.
Screen 16: Calendar

Displays the calendar page for adding new events, tasks and
searching events.
Screen 17: Add New Events

This is a event form where user can add events of that
particular dates. This page displays the new events can be added.
Screen 18: Remainder of Events
Displays the remainder of events of those particular dates. After login
this website it displays the message of event.
Screen 19: View Tasks

Displays the list of tasks that can be added in the system.
Screen 20: Add New Contacts

This is a contacts form where user enters the contacts details.
Screen 21: View Contacts List

Displays the list of contacts that can be added in particular user.
9.FUTURE ENHANCEMENTS:
The webmail system has been developed in a very short period of

time and all efforts have been taken so that the developed system is very efficient in its
execution and use. This system can further be enhanced in terms of user friendliness and
its scope of accessibility. The user friendliness can be enhanced by adding facilities to
segregate read, unread mails separately in the folders, by segregating the mails on daily
and weekly basis, etc. The access to the mailbox can be improved via internet by making
it available outside the organization.
10.CONCLUSION:
The Intranet Web Mail System has been developed to facilitate effective and
instantaneous communication in an organization. It is a web application that helps to
produce inter and intra communication facility in an organization. It provides all the
functionalities required by the users of the organization.
The project was successfully developed and implemented.
Its performance found to be satisfactory. The system was tested with sample data and was
found to be much faster, reliable and user friendly than the existing system. This system is
flexible enough to adapt any changes in it that can occur during maintenance. Any sorts of
enhancements are possible in future.
11.References:
The following references were made for successful
completion of the project, from where a good deal of important
knowledge was acquired and incorporated in the work.
Reference Book:
1.Proffessional ASP.NET 2.0
Wrox Publication
Asp.NET 2.0 with C#
2.C#.NET 2005
Complete Reference
Murachs
Web References:
http://WWW.knowledgetree.com/
http://WWW.Wikipedia.com/
http://WWW.msdn.microsoft.com/
http://WWW.asp.net.com/

Report

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Report

Загружено:

Авторское право:

Доступные форматы

Intranet Web Mail System 1

INTRANET WEB MAIL SYSTEM consists of inbox, composes,

INTRANET WEB MAIL SYSTEM consists of inbox, composes,

search events. Remainder can be set for adding events of particular

However, the notion of distance used is almost always predefined, and

Computationally expensive data mining operations allow users to

We would prefer if the greatest possible degree of intermediate results

was related to indexing large databases of sounds, the indexing

In today's modern, sophisticated and fast world, online classifieds have

All staff-focused information is on the general website, mixed in with

Information is presented in many different ways and the language used is

Communication and community development

1.3. Overview of project:

However, the notion of distance used is almost always

2.1. Initial Investigation

Once the request is approved the following activities are

2.2 Proposed System:

2.3. Present System:

There also some paid classified websites with better

2.4. Disadvantages of present system:

Our Application Mainly Deals with Many Tasks

3.2. Advantages of Proposed System

1. Using this project we can have all document Information and

3.3 Feasibility Analysis :

or automated system or it may be a major modification to an

It involves careful planning, investigation of the current system

>Technical feasibility: is concerned with the availability

>Operational feasibility: is the is all about problems that may

> Legal feasibility : plays a major role in formulating contracts

3.1 Hardware Requirements:

4.1 SOFTWARE REQUIREMENT

Developers Responsibilities Overview

2. Software products are software systems delivered to the customers

Assumptions and Dependencies

Specific Requirements Inputs and Outputs

External Interface Requirements

This phase produces a design documents, consisting of detailed

5.1 Context diagram

Software design is a process through which requirements

By following these simple rules during the initial

A class icon is a rectangle with three sections in it. Horizontal

Preliminary or general design:

Structure or Detailed design:

5.1.1 Logical Design:

The steps to be followed during physical design are given below:

Design system and program structure-describes the various programs

Designing distributed processing strategies describes how your

Depicts various step involved in physical design.

5.2 Data Flow Diagram:

DFD Of Administrator Module

New users Users

Manage Manage Change Manag

View/add/ed View/add/edit Change View/add/

Messages User Users Contacts

DFD Of Registered User Module

Types of Relationships (Cardinality)

One-to-One (1:1) - This implies a relation between one or more

One-to-Many (1: M or M: 1) - For one occurrence of one

6.2 Module Design

Administrator (Full Control) User:

Authorized (Registered) Users:

Have the access to the System through proper combination of

The project comprises of following modules.

Mail Box Module