ABSTRACT

This system facilitates mailing among users of an Intranet. Nowa-days organizations are growing fast and are increasing in size also. So these organizations are divided into departments. In the fast growing world the information is needed as fast as possible. This can be accomplished by passing the information quickly. Quick passing of mails is not possible in manual systems. This is because the information is passed through persons of one department to another department. This leads to the inconsistency and delay in delivering information. So we need a system which is both quick and accurate. This can be achieved by developing a web-based Secure Mailing System.

INDRODUCTION

Project objective
The objective of this project is to manage mails in an office such that compose mails read mails, and also remove the mails from the inbox of a particular user in that office. The user log in by use his username and password. The user can see his inward mails, local mails etc. The user can easily remove the inbox mail directly from the inbox by clicking the remove button. The software has been developed using the most powerful and secured backend MySQL and the most widely accepted front end tool asp.net with HTML coding behind.

Features of the system
This system will be performing the following tasks: (a) The system will provide an interface to the user for login his page. (b) User can read their inward mails sending by the others. (c) User can send mails to the other user. (d) User can see the files that not completed officially. (e) User can send/replay messages

SCOPE AND PURPOSE

Scope
This product has great future scope. Secure mailing system software developed on and for the Windows and later versions environments and Linux OS. This project also provides security with the use of Login-id and Password, so that any unauthorized users can not use your account. The only Authorized that will have proper access authority can access the software.

Purpose
The purpose of this software is to build a mail system that allows the people to communicate in an efficient manner. Also they can send mails to different users in an office. The functions included in the software are send mails, view the inward mails, view the local mails etc. Also the user have an opportunity to remove the mails from the inbox.

SYSTEM ANALYSIS AND PLANNING

System analysis or study is an important phase of any system development process. It is the process of gathering and interpreting the facts, diagnosing the problems and using that information recommend improvement to the existing system. The system analyst plays the role of an interrogator and dwells deep into the working of the present system. The system is viewed as a whole and the inputs of the system are identified. The outputs are traced through the various processing that the inputs phase through.

Purpose
The purpose of this software is to build a mail system that allows the people to communicate in an efficient manner. Also they can send mails to different users in an office. The functions included in the software are send mails, view the inward mails, view the local mails etc. Also the user have an opportunity to remove the mails from the inbox.

FEASIBILITY STUDY Feasibility

Feasibility is the determination of whether or not a project is worth doing. The process followed in making this determination is called Feasibility study. Once it has been determined that a project is feasible, the system analyst can go ahead and prepare the project specification which finalizes the project requirements.

Technical Feasibility
Technical feasibility study was done to ensure that the work can be completed with the current equipments, existing software technology and available person.
4

Technical needs of a system mainly includes:(a) Facility to produce outputs in a given system (b) Response time under certain conditions. (c) Providing security. (d) Facility to communicate data to distant location.

Functional Feasibility
This is done to ensure whether the system is feasible with the end user. It includes the Graphical User Interface and automatic data retrieval from the database. The software is functionally feasible.

Time Feasibility
The stipulated time for the development of the project is four Months and it can be finished within that span of time. Hence the system is feasible in terms of time.

Financial Feasibility
The software product, which is to be developed, is financially feasible. The cost required for the maintenance of the software is also realizable.

Operational Feasibility
This is mainly related to human organization and political aspects. The points to be considered are:(a) What changes will be brought in the system? (b) What organization structures are distributed? (c) What new skills will be required?

Overview
The main objective of this system is to improve the capability of the current system. The system is to provide the following advantages: Computerized mail management in an office. Make the proposed system completely user friendly and menu driven. Reduce repetitive manual work Provides backup and accuracy. Provides efficient storage for all the details. Informative guidance to the user

IMPEMENTATION ISSUES

HTML
Hyper Text Markup Language (HTML) is the main markup language for displaying web pages and other information that can be displayed in a web browser. HTML is written in the form of HTML elements consisting of tags enclosed in angle brackets (like <html>), within the web page content. HTML tags most commonly come in pairs like <h1> and </h1>, although some tags, known as empty elements, are unpaired, for example <img>. The first tag in a pair is the start tag, the second tag is the end tag (they are also called opening tags and closing tags). In between these tags web designers can add text, tags, comments and other types of text-based content. The purpose of a web browser is to read HTML documents and compose them into visible or audible web pages. The browser does not display the HTML tags, but uses the tags to interpret the content of the page. HTML elements form the building blocks of all websites. HTML allows images and objects to be embedded and can be used to create interactive forms. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It can embed scripts in languages such as JavaScript which affect the behavior of HTML webpages. Web browsers can also refer to Cascading Style Sheets (CSS) to define the appearance and layout of text and other material. The W3C, maintainer of both the HTML and the CSS standards, encourages the use of CSS over explicitly presentational HTML markup.

.NET
INTRODUCTION TO .NET Framework
The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:

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

To provide a code-execution environment that minimizes software deployment and versioning conflicts.

To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semitrusted third party.

To

provide

code-execution

environment

that

eliminates

the

performance problems of scripted or interpreted environments.

To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Webbased applications.

To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.

For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime
8

to enable Web Forms applications and XML Web services, both of which are discussed later in this topic.

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

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

FEATURES OF THE COMMON LANGUAGE RUNTIME

The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin (such as the Internet, enterprise network, or local computer). This means
9

that a managed component might or might not be able to perform fileaccess operations, registry-access operations, or other sensitive functions, even if it is being used in the same active application.

.NET FRAMEWORK CLASS LIBRARY

The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of the .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework. For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET Framework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the class library includes types that support a variety of specialized development scenarios. For example, you can use the .NET

10

Framework to develop the following types of applications and services:

Console applications. Scripted or hosted applications. Windows GUI applications (Windows Forms). ASP.NET applications. XML Web services. Windows services. For example, the Windows Forms classes are a comprehensive set

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

CLIENT APPLICATION DEVELOPMENT

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

Another kind of client application is the traditional ActiveX control (now replaced by the managed Windows Forms control) deployed over the
11

Internet as a Web page. This application is much like other client applications: it is executed natively, has access to local resources, and includes graphical elements.

ASP.NET Server Application Development

Server-side applications in the managed world are implemented through runtime hosts. Unmanaged applications host the common language runtime, which allows your custom managed code to control the behavior of the server. This model provides you with all the features of the common language runtime and class library while gaining the performance and scalability of the host server. The following illustration shows a basic network schema with managed code running in different server environments. Servers such as IIS and SQL Server can perform standard operations while your application logic executes through the managed code. SERVER-SIDE MANAGED CODE

ASP.NET is the hosting environment that enables developers to use the .NET Framework to target Web-based applications. However, ASP.NET is more than just a runtime host; it is a complete architecture for developing Web sites and Internet-distributed objects using managed code. Both Web Forms and XML Web services use IIS and ASP.NET as the publishing

12

mechanism for applications, and both have a collection of supporting classes in the .NET Framework.

LANGUAGE SUPPORT The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual Basic, and JScript.

WHAT IS ASP.NET WEB FORMS? The ASP.NET Web Forms page framework is a scalable common language runtime programming model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing pages), the ASP.NET Web Forms framework has been specifically designed to address a number of key deficiencies in the previous model. In particular, it provides: The ability to create and use reusable UI controls that can encapsulate common functionality and thus reduce the amount of code that a page developer has to write. The ability for developers to cleanly structure their page logic in an orderly fashion (not "spaghetti code"). The ability for development tools to provide strong WYSIWYG design support for pages (existing ASP code is opaque to tools).

13

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

CODE-BEHIND WEB FORMS

ASP.NET supports two methods of authoring dynamic pages. The first is the method shown in the preceding samples, where the page code is physically declared within the originating .aspx file. An alternative approach--known as the code-behind method--enables the page code to be more cleanly separated from the HTML content into an entirely separate file. INTRODUCTION TO ASP.NET SERVER CONTROLS In addition to (or instead of) using <% %> code blocks to program dynamic content, ASP.NET page developers can use ASP.NET server controls to program Web pages. Server controls are declared within an .aspx file using custom tags or intrinsic HTML tags that contain a runat="server" attributes value. Intrinsic HTML tags are handled by one of the controls in the System.Web.UI.HtmlControls namespace. Any tag that doesn't explicitly
14

map

to

one

of

the

controls

is

assigned

the

type

of

System.Web.UI.HtmlControls.HtmlGenericControl.

Server controls automatically maintain any client-entered values between round trips to the server. This control state is not stored on the server (it is instead stored within an <input type="hidden"> form field that is roundtripped between requests). Note also that no client-side script is required.

In addition to supporting standard HTML input controls, ASP.NET enables developers to utilize richer custom controls on their pages. For example, the following sample demonstrates how the <asp: ad rotator> control can be used to dynamically display rotating ads on a page.

1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI. 2. ASP.NET Web Forms pages can target any browser client (there are no script library or cookie requirements). 3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages. 4. ASP.NET server controls provide an easy way to encapsulate common functionality. 5. ASP.NET ships with 45 built-in server controls. Developers can also use controls built by third parties. 6. ASP.NET server controls can automatically project both uplevel and downlevel HTML. 7. ASP.NET templates provide an easy way to customize the look and feel of list server controls.
15

8. ASP.NET validation controls provide an easy way to do declarative client or server data validation.

C#.NET ADO.NET OVERVIEW ADO.NET is an evolution of the ADO data access model that directly addresses user requirements for developing scalable applications. It was designed specifically for the web with scalability, statelessness, and XML in mind.

ADO.NET uses some ADO objects, such as the Connection and Command objects, and also introduces new objects. Key new ADO.NET objects include the DataSet, DataReader, and DataAdapter.

The important distinction between this evolved stage of ADO.NET and previous data architectures is that there exists an object -- the DataSet -that is separate and distinct from any data stores. Because of that, the DataSet functions as a standalone entity. You can think of the DataSet as an always disconnected recordset that knows nothing about the source or destination of the data it contains. Inside a DataSet, much like in a database, there are tables, columns, relationships, constraints, views, and so forth.

The following sections will introduce you to some objects that have evolved, and some that are new. These objects are:
16

Connections. For connection to and managing transactions against a database.

Commands. For issuing SQL commands against a database. DataReaders. For reading a forward-only stream of data records from a SQL Server data source.

DataSets. For storing, Remoting and programming against flat data, XML data and relational data.

DataAdapters. For pushing data into a DataSet, and reconciling data against a database.

When dealing with connections to a database, there are two different options: SQL Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider (System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider. These are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data Provider is used to talk to any OLE DB provider (as it uses OLE DB underneath).

Connections: Connections are used to 'talk to' databases, and are represented by provider-specific classes such as SqlConnection. Commands travel over connections and resultsets are returned in the form of streams which can be read by a DataReader object, or pushed into a DataSet object.

17

Commands:

Commands contain the information that is submitted to a database, and are represented by provider-specific classes such as SqlCommand. A command can be a stored procedure call, an UPDATE statement, or a statement that returns results. You can also use input and output parameters, and return values as part of your command syntax. The example below shows how to issue an INSERT statement against the Northwind database.

DataReaders:

The DataReader object is somewhat synonymous with a read-only/forwardonly cursor over data. The DataReader API supports flat as well as hierarchical data. A DataReader object is returned after executing a command against a database. The format of the returned DataReader object is different from a recordset. For example, you might use the DataReader to show the results of a search list in a web page.

18

SQL SERVER

A database management, or DBMS, gives the user access to their data and helps them transform the data into information. Such database management systems include dBase, paradox, IMS, SQL Server and SQL Server. These systems allow users to create, update and extract

information from their database. A database is a structured collection of data. Data refers to the

characteristics of people, things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields relating to a particular person, thing or event are bundled together to form a single complete unit of data, called a record (it can also be referred to as raw or an occurrence). Each record is made up of a number of fields. No two fields in a record can have the same field name. During an SQL Server Database design project, the analysis of your business needs identifies all the fields or attributes of interest. If your

business needs change over time, you define any additional fields or change the definition of existing fields.

SQL SERVER TABLES SQL Server stores records relating to each other in a table. Different tables are created for the various groups of information. Related tables are grouped together to form a database.

19

PRIMARY KEY Every table in SQL Server has a field or a combination of fields that uniquely identifies each record in the table. The Unique identifier is called the Primary Key, or simply the Key. The primary key provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify, locate and refer to one particular record in the database.

RELATIONAL DATABASE Sometimes all the information of interest to a business operation can be stored in one table. SQL Server makes it very easy to link the data in multiple tables. Matching an employee to the department in which they work is one example. This is what makes SQL Server a relational

database management system, or RDBMS. It stores data in two or more tables and enables you to define relationships between the table and enables you to define relationships between the tables.

FOREIGN KEY When a field is one table matches the primary key of another field is referred to as a foreign key. A foreign key is a field or a group of fields in one table whose values match those of the primary key of another table.

20

REFERENTIAL INTEGRITY Not only does SQL Server allow you to link multiple tables, it also maintains consistency between them. Ensuring that the data among related tables is correctly matched is referred to as maintaining referential integrity.

DATA ABSTRACTION A major purpose of a database system is to provide users with an abstract view of the data. This system hides certain details of how the data is stored and maintained. Data abstraction is divided into three levels.

Physical level:

This is the lowest level of abstraction at which one

describes how the data are actually stored.

Conceptual Level: At this level of database abstraction all the attributed and what data are actually stored is described and entries and relationship among them.

View level: This is the highest level of abstraction at which one describes only part of the database.

21

ADVANTAGES OF RDBMS

Redundancy can be avoided Inconsistency can be eliminated Data can be Shared Standards can be enforced Security restrictions ca be applied Integrity can be maintained Conflicting requirements can be balanced Data independence can be achieved.

DISADVANTAGES OF DBMS A significant disadvantage of the DBMS system is cost. In addition to the cost of purchasing of developing the software, the hardware has to be upgraded to allow for the extensive programs and the workspace required for their execution and storage. While centralization reduces duplication, the lack of duplication requires that the database be adequately backed up so that in case of failure the data can be recovered.

22

ENTERPRISE WIDE DATA SHARING The unrivaled portability and connectivity of the SQL SERVER DBMS enables all the systems in the organization to be linked into a singular, integrated computing resource.

PORTABILITY SQL SERVER is fully portable to more than 80 distinct hardware and operating systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms. This portability gives complete

freedom to choose the database sever platform that meets the system requirements.

OPEN SYSTEMS SQL SERVER offers a leading implementation of industry standard SQL. SQL Servers open architecture integrates SQL SERVER and non SQL SERVER DBMS with industries most comprehensive collection of tools, application, and third party software products SQL Servers Open architecture provides transparent access to data from other relational database and even non-relational database.

DISTRIBUTED DATA SHARING SQL Servers networking and distributed database capabilities to access data stored on remote server with the same ease as if the information was
23

stored on a single local computer. A single SQL statement can access data at multiple sites. You can store data where system requirements such as performance, security or availability dictate.

UNMATCHED PERFORMANCE The most advanced architecture in the industry allows the SQL SERVER DBMS to deliver unmatched performance.

SOPHISTICATED CONCURRENCY CONTROL Real World applications demand access to critical data. With most

database Systems application becomes contention bound which performance is limited not by the CPU power or by disk I/O, but user waiting on one another for data access. SQL Server employs full, unrestricted row-level locking and contention free queries to minimize and in many cases entirely eliminates contention wait times.

NO I/O BOTTLENECKS SQL Servers fast commit groups commit and deferred write technologies dramatically reduce disk I/O bottlenecks. While some database write whole data block to disk at commit time, SQL Server commits transactions with at most sequential log file on disk at commit time, On high throughput systems, one sequential writes typically group commit multiple

transactions. Data read by the transaction remains as shared memory so

24

that other transactions may access that data without reading it again from disk. Since fast commits write all data necessary to the recovery to the log file, modified blocks are written back to the database independently of the transaction commit, when written from memory to disk.

25

SYSTEM REQUIREMENTS SPECIFICATIONS

System requirements are expressed in a software requirement document. The Software requirement specification (SRS) is the official statement of what is required of the system developers. This requirement document includes the requirements definition and the requirement specification. The software requirement document is not a design document. It should set out what the system should do without specifying how it should be done. The requirement set out in this document is complete and consistent. The software specification document satisfies the following:1 It specifies the external system behaviors. 2 It specifies constraints on the implementation. 3 It is easy to change. 4 It serves as reference tool for system maintainers. 5 It record forethought about the life cycle of the system. 6 It characterizes acceptable response to undesired events.

Performance Requirements:
In order to maintain an acceptable speed at maximum number of uploads allowed from a particular customer will be any number of users can access the system at any time. Also connections to the servers will be based on the criteria of attributes of the user like his location, and server will be working whole 24X 7 times.

Non Functional Requirements:

Following Non-functional requirements will be there in the Insurance on internet: i). Secure access of confidential data (customers details). ii). 24 X 7 availability. iii). Better component design to get better performance at peak time.
26

iv). Flexible service based architecture will be highly desirable for future extension Non functional requirements define system properties and constraints It arise through user needs, because of budget constraints or organizational policies, or due to the external factors such as safety regulations, privacy registration and so on. Various other Non-functional requirements are: 1. Security 2. Reliability 3. Maintainability 4. Portability 5. Extensibility 6. Reusability 7. Application Affinity/Compatibility 8. Resource Utilization

External Interface Requirements:

User Interface:
User of the system will be provided with the Graphical user interface, there is no command line interface for any functions of the product. The user will get two pages Login page followed by Password

Software Interface:
Software required to make working of product is:1. Operating System: Windows XP/vista/7 or later version Linux which supports networking.
2. Database- SQL Server 2005

OS

3. Front end- ASP.NET, C#.NET

27

4. Reporting- Crystal Report 5. MS Office 2003- Documentation

Hardware Interface
P4 Processor (3.2 GHz) 512 MB RAM CRT Monitor Printer Keyboard Mouse CPU

Communication Interfaces
The two parties should be connected through either by LAN or WAN for the communication. Communication channels Receiver, Sender

28

General Constraints, Assumptions, Dependencies, Guidelines:

General Constraints
The interface will be in English only. The system is working for single server. There is no maintainability or backup so availability will get affected. The system is a single user system. GUI features available.

Assumptions and Dependencies

The product does require back-end database server SQLSERVER for storing the username and password for different types of user of the system as well as various databases regarding various insurance information.

Assumptions:
User must be trained for basic computer functionalities. User must have the basic knowledge of English The system must be able to respond to database software within reasonable time.

Front-end (user interaction):

The product will require a computer with an application program or with any other application program and an communication channel.

29

 The speed of the communication channel (if any) must be, at a minimum 28.8 kbps in order to support message transfer in reasonable time.

30

SYSTEM DESIGN SPECIFICATION

Systems design is the process 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 with the disciplines of systems analysis , systems architecture and systems engineering.

Unified Modeling Languages

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

Goals of UML The primary goals in the design of the UML were: 1.Provide users with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models.
31

2.Provide extensibility and specialization mechanisms to extend the core concepts. 3.Be independent of particular programming languages and development processes. 4.Provide a formal basis for understanding the modeling language. 5.Encourage the growth of the OO tools market.

The Unified Modeling Languages encompasses a number of models. Use Case Diagram Class Diagram Sequence Diagram Collaboration Diagram Use case Diagram Use Case diagrams show the various activities the users can perform on the system. The System is something that performs a function. They model the dynamic aspects of the system. It provides a users perspective of the system. Actor: An actor is a user of the system playing a particular role. Use case: Use case is a particular activity a user can do on the system. Relationship: Relationships are simply illustrated with a line connecting actors to use cases.

32

Class Diagram A class diagram describes the types of objects in the system and the various kinds of static relationships that exist among them i.e., A graphical representation of a static view on declarative static elements. A class is the description of a set of objects having similar attributes, operations, relationships and behavior. Sequence Diagram A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Chart. Sequence diagrams are sometimes called event diagrams, event scenarios, and timing diagrams

Collaboration Diagram A Collaboration diagram is very similar to a Sequence diagram in the purpose it achieves; in other words, it shows the dynamic interaction of the objects in a system. A distinguishing feature of a Collaboration diagram is that it shows the objects and their association with other objects in the system apart from how they interact with each other. The association between objects is not represented in a Sequence diagram. A Collaboration diagram is easily represented by modeling objects in a system and representing the associations between the objects as links. The interaction between the objects is denoted by arrows.

33

DATA FLOW DIAGRAMS Data flow diagrams (DFD) was first developed by LARRY CONSTANTINE as way representing system requirements in a graphical form; this lead to modular design. A DFD describes what data flow (logical) rather than how they are processed, so it does not depend on hardware, software, data structure or file organization. It is also known as bubble chart. A Data Flow Diagrams is a structured analysis and design tool that can be used for flowcharting in place of, or in association with, information-oriented and process-oriented systems flowcharts. A DFD is a network that describes the flow of data and the processes that change, or transform, data throughout a system. This network is constructed by using a set of symbols that do not imply a physical implementation. It 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 phase that functionality decomposes the requirement specifications down to the lowest level of detail. The symbols used to prepare DFD do not imply a physical implementation, a DFD can be considered to an abstract of the logic of an informationoriented or a process-oriented system flow-chart. For these reasons DFDs are often referred to as logical data flow diagrams.

The four basic symbols used to construct data flow diagrams are shown below: A rectangle represents a data source or destination.

A directed line represents the flow of data that is data stream.

34

An enclosed figure, usually a circle or an oval bubble, represent a process that transforms data streams.

An open-ended rectangle represents data storage.

These are symbols that represent data flows, data sources, data transformations and data storage. The points at which data are transformed are represented by enclosed figures, usually circles, which are called nodes. The principle processes that take place at nodes are 1. combining data streams 2. splitting data streams 3. modifying data streams.

35

DataFlow Diagram

1. Request for Registration. 2. Login. 3. Send Mail. 4. Add topic detail.

1. Login 2. Check mail Details.

3. View Details

5 View Detail 6 Update Details User Administrator

Secure Mail System

1. Confirmation of Login 1. Confirmation of registration.

2. Confirmation of details

2. Confirmation of mail Details. 3. View Details

0-Level Dataflow Diagram

36

Request for registration

Store User Details

Login System

Registration System

DB1 Login Details Re tri ev e de tai ls

Confirmation of registration

Request For Login Login System

Store Details

Login request User Administrator

Login verification msg

Login Verify Confir matio n msg

Request For Login Send Mail Mail System User Stor Mail Receive Mail D2 Mail details 37

Confirmation Details

DB System Details 1. Add topic details 2. View Details 3 Update Details View System Details Receive Confirmatio n Administrator Reta riev e Store information

User

Confirmation Deatils

View Details

1-Level Data Flow Diagram

38

DATABASE DESIGN
NORMALISATION
A normalization is a collection of interrelated data stored with a minimum of redundancy to serve many application .The database design is used to group data into a tables and mininmize 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 cost.

Normalization is a 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 the various types of anomalies and inconsistencies are not introduced into the database.

39

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 relations is said to be in third normal form if and if it is in second normal form and every non-key attribute is non transitively depend on the primary key.

40

CODING

41

PROJECT CODING
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class account : System.Web.UI.Page { connct c = new connct(); protected void Page_Load(object sender, EventArgs e) { if (!Page.IsPostBack) { Button1.Enabled = true; Label9.Visible = false; Button2.Enabled = false; } } protected void Button2_Click(object sender, EventArgs e) { chktext(); if (Label9.Text == "continue") { fill(); } else
42

{ Label9.Visible = true; } } public void fill() { string dob = "" + ddl_date.Text + "/" + ddl_mon.Text + "/" + ddl_year.Text + ""; c.con.Open(); string abc = "insert into user_det(u_id,u_fname,u_lname,u_pass,u_dob,u_gen,u_pcode,u_a dd,u_cno,u_dttm,u_block) values('" + txt_eid.Text + "','" + txt_fname.Text + "','" + txt_lname.Text + "','" + txt_pwd.Text + "','" + dob + "','" + RadioButtonList1.Text + "','" + txt_postal.Text + "','" + txt_add.Text + "','" + txt_cno.Text + "','" + System.DateTime.Now + "','n')"; SqlCommand cmd = new SqlCommand(abc, c.con); cmd.ExecuteNonQuery(); c.con.Close(); Session["uid"] = txt_eid.Text; Session["uname"] = txt_fname.Text; Response.Redirect("ulogmain.aspx"); } public void chktext() { if (Label9.Text != "") { Label9.Text = ""; } if (txt_pwd.Text == "") { ViewState["text"] = "Fill the Password"; goto done; } if (txt_fname.Text == "") { ViewState["text"] = "Fill the First Name"; goto done; }
43

if (txt_lname.Text == "") { ViewState["text"] = "Fill the Last Name"; goto done; } if (txt_add.Text == "") { ViewState["text"] = "Fill the Address"; goto done; } if (txt_cno.Text == "") { ViewState["text"] = "Fill the Contact No."; goto done; } if (ddl_date.Text == "n") { ViewState["text"] = "Select the Date"; goto done; } if (ddl_mon.Text == "n") { ViewState["text"] = "Select the Month"; goto done; } if (ddl_year.Text == "n") { ViewState["text"] = "Select the Year"; goto done; } if (RadioButtonList1.Text == "") { ViewState["text"] = "Select the Gender"; goto done; } if (txt_postal.Text == "") { ViewState["text"] = "Fill the Postal Code"; goto done;
44

} if (txt_ver.Text == "") { ViewState["text"] = "Fill the Verification Code"; goto done; } if (txt_ver.Text != "dedl") { ViewState["text"] = "Fill the Correct Postal Code"; goto done; } if (Label9.Text == "") { ViewState["text"] = "continue"; } done: Label9.Visible = true; Label9.Text = ViewState["text"].ToString(); } protected void Button1_Click(object sender, EventArgs e) { if (txt_eid.Text == "") { Label9.Visible = true; Label9.Text = "Please enter ur Email ID"; } else { chkid(); } } public void chkid() { c.con.Open(); string abc = "select u_id from user_det"; SqlCommand cmd = new SqlCommand(abc, c.con); SqlDataReader dr = cmd.ExecuteReader();
45

if (dr.Read()) { Label9.Text = "Continue....!!"; if (txt_eid.Text == dr["u_id"].ToString()) { Label9.Visible = true; Label9.Text = "Email ID Already Exists...!!"; Button1.Enabled = true; Button2.Enabled = false; txt_eid.ReadOnly = false; } else { Label9.Visible = true; Label9.Text = "Continue ....!!"; Button1.Enabled = false; Button2.Enabled = true; txt_eid.ReadOnly = true; while (dr.Read()) { if (txt_eid.Text == dr["u_id"].ToString()) { Label9.Visible = true; Label9.Text = "Email ID Already Exists...!!"; Button1.Enabled = true; Button2.Enabled = false; txt_eid.ReadOnly = false; goto done; } else { Label9.Visible = true; Label9.Text = "Continue ....!!"; Button1.Enabled = false; Button2.Enabled = true; txt_eid.ReadOnly = true;
46

} } } done: Label9.Visible = true; Label9.Text = ViewState["text"].ToString(); } else { Label9.Visible = true; Label9.Text = "Continue ....!!"; Button2.Enabled = true; txt_eid.ReadOnly = true; } c.con.Close(); } }

//

Admin:
public partial class adminlog : System.Web.UI.Page { connct c = new connct(); protected void Page_Load(object sender, EventArgs e) { if (Session["uid"] == null) { Response.Redirect("login.aspx?log=n"); } if (Session["uid"].ToString() != "Admin") { Response.Redirect("login.aspx?log=n"); } if (Request.QueryString["ud"] == "n") { Button1.Enabled = false; GridView1.Visible = false; Button1.Visible = false;
47

Label3.Visible = true; Label3.Text = "Please Select the user to Block/Unblock"; } if (!Page.IsPostBack) { Button1.Enabled = false; GridView1.Visible = false; Button1.Visible = false; Label3.Visible = false; } } public void gd() { } protected void GridView1_RowDataBound(object sender, GridViewRowEventArgs e) { if (e.Row.RowType == DataControlRowType.DataRow) { e.Row.Cells[1].Text = e.Row.Cells[1].Text + "@secure.com"; } } protected void Button1_Click(object sender, EventArgs e) { ck(); } public void ck() { StringBuilder str = new StringBuilder(); int a = 0; string quid = ""; int s = 0; for (int i = 0; i < GridView1.Rows.Count; i++) { GridViewRow row = GridView1.Rows[i]; bool isChecked = ((CheckBox)row.FindControl("chk")).Checked; Response.Write(isChecked);
48

if (isChecked) { s = Convert.ToInt32(((TextBox)row.FindControl("txt")).Text); if (a == 0) quid += s; else quid += "," + s; a = a + 1; } } if (Button1.Text == "Block") { if (quid == "") { string ab = "n"; Response.Redirect("adminlog.aspx?ud=" + ab); } else Response.Redirect("logchng.aspx?ubid=" + quid); } if (Button1.Text == "Unblock") { if (quid == "") { string ab = "n"; Response.Redirect("adminlog.aspx?ud=" + ab); } else { string a12 = "logchng.aspx?unbid=" + quid.ToString(); Response.Redirect(a12.ToString()); } } } protected void Button2_Click(object sender, EventArgs e) {
49

Label3.Visible = false; Button1.Visible = true; Button1.Text = "Unblock"; Button1.Enabled = true; Button3.Enabled = false; c.con.Open(); GridView1.Visible = true; string str = "select * from user_det where u_block='y' order by u_dttm desc"; SqlDataAdapter ad = new SqlDataAdapter(str, c.con); DataSet ds = new DataSet(); ad.Fill(ds); GridView1.DataSource = ds; GridView1.DataBind(); c.con.Close(); } protected void Button3_Click(object sender, EventArgs e) { Label3.Visible = false; Button1.Visible = true; Button1.Text = "Block"; Button1.Enabled = true; Button2.Enabled = false; GridView1.Visible = true; c.con.Open(); string str = "select * from user_det where u_block='n' order by u_dttm desc"; SqlDataAdapter ad = new SqlDataAdapter(str, c.con); DataSet ds = new DataSet(); ad.Fill(ds); GridView1.DataSource = ds; GridView1.DataBind(); c.con.Close(); } }

Forgot
public partial class forgot : System.Web.UI.Page
50

{ connct c = new connct(); protected void Page_Load(object sender, EventArgs e) { if (!Page.IsPostBack) { Label1.Visible = false; txt_eid.Visible = false; RequiredFieldValidator1.Visible = false; Button1.Enabled = false; Label3.Visible = false; } } protected void RadioButtonList1_SelectedIndexChanged(object sender, EventArgs e) { string str = RadioButtonList1.SelectedValue; if (str == "y") { Label1.Visible = true; txt_eid.Visible = true; RequiredFieldValidator1.Visible = true; Button1.Enabled = true; Label3.Visible = true; } if (str == "n") { Label3.Visible = false; Label1.Visible = false; txt_eid.Visible = false; RequiredFieldValidator1.Visible = false; Button1.Enabled = true; } } protected void Button1_Click(object sender, EventArgs e) { chktext();

51

string dmy= "" + ddl_date.Text + "/" + ddl_mon.SelectedValue + "/" + ddl_year.Text + ""; if (Label5.Text == "y") { if (txt_eid.Visible == true) { ViewState["str123"] = "select * from user_det where u_id='" + txt_eid.Text + "' and u_pcode='" + txt_postal.Text + "' and u_dob='" + dmy + "'"; fill(); } if (txt_eid.Visible == false) { ViewState ["str123"] = "select * from user_det where u_pcode='" + txt_postal.Text + "' and u_dob='" + dmy + "'"; fill(); } } else { Label5.Visible = true; } } public void fill() { c.con.Open(); SqlCommand cmd = new SqlCommand(ViewState["str123"].ToString(), c.con); SqlDataReader dr = cmd.ExecuteReader(); if (dr.Read()) { Label5.Visible = true; Label5.Text = "Your ID is :-" + dr["u_id"].ToString() + "@secure.com ....&.... Password is :-" + dr["u_pass"].ToString() + ""; } else {
52

Label5.Visible = true; Label5.Text = "Sorry your details is not valid we can't provide you ID/Password..!!"; } dr.Close(); c.con.Close(); } public void chktext() { if (Label5.Text != "") { Label5.Text = ""; } if (ddl_date.Text == "n") { ViewState["text"] = "Select the Date"; goto done; } if (ddl_mon.Text == "n") { ViewState["text"] = "Select the Month"; goto done; } if (ddl_year.Text == "n") { ViewState["text"] = "Select the Year"; goto done; } if (ViewState["text"] == null) { ViewState["text"] = "y"; } done: Label5.Visible = true; Label5.Text = ViewState["text"].ToString(); } }

Login
53

public partial class login : System.Web.UI.Page { connct c = new connct(); protected void Page_Load(object sender, EventArgs e) { if (!Page.IsPostBack) { Label4.Visible = false; } if (Request.QueryString["log"] != null) { Label4.Visible = true; Label4.Text = "Please Login into your account"; } } protected void Button1_Click(object sender, EventArgs e) { if (txt_uname.Text == "admin" && txt_pass.Text == "a") { Session["uid"] = "Admin"; Response.Redirect("adminlog.aspx"); } else { c.con.Open(); string abc = "select * from user_det where u_id='" + txt_uname.Text + "' and u_pass='" + txt_pass.Text + "'"; SqlCommand cmd = new SqlCommand(abc, c.con); SqlDataReader dr = cmd.ExecuteReader(); if (dr.Read()) { if (dr["u_block"].ToString() == "y") { ViewState["per"] = "No Permission...Please Contact to administrator"; goto done; }
54

if (dr["u_block"].ToString() == "n") { Session["uid"] = txt_uname.Text; Session["uname"] = dr["u_fname"].ToString(); Response.Redirect("ulogmain.aspx"); } done: Label4.Visible = true; Label4.Text = ViewState["per"].ToString(); } else { Label4.Visible = true; Label4.Text = "Please enter correct ID & Password"; } dr.Close(); c.con.Close(); } } } Log out public partial class logout : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { Session["uname"] = null; Session["uid"] = null; Response.Redirect("about.aspx"); } }

Search
public partial class search : System.Web.UI.Page { connct c = new connct();
55

protected void Page_Load(object sender, EventArgs e) { if (!Page.IsPostBack) { txt_eid.Text = ""; txt_fname.Text = ""; txt_lname.Text = ""; } } protected void Button1_Click(object sender, EventArgs e) { chk(); fillgd(); } public void chk() { if (txt_fname.Text == "" && txt_lname.Text != "" && txt_eid.Text != "") { string str = "select * from user_det where u_lname='" + txt_lname.Text + "' and u_id='" + txt_eid.Text + "'"; ViewState["str"] = str.ToString(); } if (txt_fname.Text != "" && txt_lname.Text == "" && txt_eid.Text != "") { string str = "select * from user_det where u_fname='" + txt_fname.Text + "' and u_id='" + txt_eid.Text + "'"; ViewState["str"] = str.ToString(); } if (txt_fname.Text != "" && txt_lname.Text != "" && txt_eid.Text == "") { string str = "select * from user_det where u_fname='" + txt_fname.Text + "' and u_lname='" + txt_lname.Text + "'"; ViewState["str"] = str.ToString();
56

} if (txt_fname.Text != "" && txt_lname.Text != "" txt_eid.Text != "") { string str = "select * from user_det where u_fname='" + txt_fname.Text + "' and u_lname='" + txt_lname.Text + "' and u_id='" + txt_eid.Text + "'"; ViewState["str"] = str.ToString(); } if (txt_fname.Text == "" && txt_lname.Text == "" txt_eid.Text == "") { string str = "select * from user_det"; ViewState["str"] = str.ToString(); } if (txt_fname.Text != "" && txt_lname.Text == "" txt_eid.Text == "") { string str = "select * from user_det where u_fname='" + txt_fname.Text + "'"; ViewState["str"] = str.ToString(); } if (txt_fname.Text == "" && txt_lname.Text != "" txt_eid.Text == "") { string str = "select * from user_det where u_lname='" + txt_lname.Text + "'"; ViewState["str"] = str.ToString(); } if (txt_fname.Text == "" && txt_lname.Text == "" txt_eid.Text != "") { string str = "select * from user_det where u_id='" + txt_eid.Text + "'"; ViewState["str"] = str.ToString(); } } public void fillgd() {

&&

&&

&&

&&

&&

57

c.con.Open(); string abc = ViewState["str"].ToString(); SqlDataAdapter ad = new SqlDataAdapter(abc, c.con); DataSet ds = new DataSet(); ad.Fill(ds); GridView1.DataSource = ds; GridView1.DataBind(); c.con.Close(); } protected void GridView1_RowDataBound(object sender, GridViewRowEventArgs e) { e.Row.Cells[0].Text = e.Row.Cells[0].Text + "@secure.com"; }

Uaddview
public partial class uadview : System.Web.UI.Page { connct c = new connct(); protected void Page_Load(object sender, EventArgs e) { if (Session["uid"] == null) { Response.Redirect("login.aspx?log=n"); } if (Session["uname"] == null) { Response.Redirect("login.aspx?log=n"); } if (!Page.IsPostBack) { Label1.Visible = false; GridView1.Visible = false;
58

Label2.Visible = false; Label3.Visible = false; RequiredFieldValidator1.Visible = false; TextBox1.Visible = false; Button1.Visible = false; } if (Request.QueryString["dfid"] == null) { Button1.Visible = false; GridView1.Visible = true; gd(); Label2.Visible = false; Label3.Visible = false; RequiredFieldValidator1.Visible = false; TextBox1.Visible = false; Label1.Visible = true; } else { Label1.Visible = false; chk(); Button1.Visible = true; GridView1.Visible = false; Label2.Visible = true; Label2.Text = "Selected Topic is :" + ViewState["topic"].ToString() + "."; Label3.Visible = true; RequiredFieldValidator1.Visible = true; TextBox1.Visible = true; } } public void chk() { c.con.Open(); string str = "select * from df_topic where dft_id=" + Request.QueryString["dfid"]; SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr = cmd.ExecuteReader(); dr.Read();
59

ViewState["topic"] = dr["dft_topic"].ToString(); dr.Close(); c.con.Close(); } public void gd() { c.con.Open(); string str = "select * from df_topic"; SqlDataAdapter ad = new SqlDataAdapter(str, c.con); DataSet ds = new DataSet(); ad.Fill(ds); GridView1.DataSource = ds; GridView1.DataBind(); c.con.Close(); } protected void GridView1_RowDataBound(object sender, GridViewRowEventArgs e) { if (e.Row.RowType == DataControlRowType.DataRow) { e.Row.Cells[2].Text = e.Row.Cells[2].Text + "@secure.com"; e.Row.Cells[1].Text = "<a href=uadview.aspx?dfid=" + e.Row.Cells[0].Text + ">" + e.Row.Cells[1].Text + "</a>".ToString(); } } protected void Button1_Click(object sender, EventArgs e) { c.con.Open(); string comment = TextBox1.Text.Replace("'", "''"); string str = "insert into df_views(dfv_uid,dfv_dft_id,dfv_views,dfv_dttm) values('" + Session["uid"].ToString() + "','" + Request.QueryString["dfid"].ToString() + "','" + comment + "','" + System.DateTime.Now + "')"; SqlCommand cmd = new SqlCommand(str, c.con); cmd.ExecuteNonQuery(); c.con.Close();
60

Button1.Enabled = false; } }

61

SAMPLE SCREEN SHOTS

62

63

64

65

66

67

68

69

70

71

FUTURE SCOPE AND FURTHER ENHANCEMENT

1.

This product can be enhanced for video calling

2.

This product can be enhanced for globalization mailing.

72

BIBLIOGRAPHY

Books which I referred for the reference

The Complete Reference Asp.net by Hanna Beginning Asp Edition, by Harris and Andrew The Complete Reference SQLServer by W.Jason The Complete Reference HTML.

Websites referred:-

www.wikipedia.org www.google.co.in

73