mailing system doc

Upload: pandu-pandu

Post on 03-Apr-2018

219 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/28/2019 Mailing System DOC

    1/81

    INTRODUCTION

    1

  • 7/28/2019 Mailing System DOC

    2/81

    Mailing system is a very useful application that is used for the communication purposes

    of educational institutions. The application is developed using ASP.Net and C#, with sql server

    as the back end. There are two modules in this application. They are users and administrators.

    The administrators have full access to the application i.e. the administrator can access all of the

    modules in the application, while the users have restricted access that is they can use only some

    of the modules.

    The purpose of this project is to create an application for a university. So that

    communication among different departments is possible. The proposed system is to create a

    mailing system such that each user (Employee of the university) will have access to the

    application according to their roles, create their own mail-ids and can use this id to

    communicate with other users in the university.

    This project comprises of two modules:

    1. Administrator module.

    2. User module.

    1. Administrator Module:

    This application deals with database maintenance and differentiating users

    according to their roles, the administrator has privileges to delete any user at any point of time.

    2. User module:

    In this module, the users (Employee of the university) will create own mail-ids

    and can have all mailing facilities.

    Each module in their application consists of their own authentication and can view/enter

    the details as when required. This application also deals with the security in order to make the

    application secured. It uses the authentication techniques to provide role-based security. In order

    to make the database consistent, necessary steps are taken while creating the database. The

    exception handling techniques are used to provide code based security to prevent the application

    from abnormal termination.

    2

  • 7/28/2019 Mailing System DOC

    3/81

    SYSTEM SPECIFICATIONS

    2.1 HARDWARE DESCRIPTION

    3

  • 7/28/2019 Mailing System DOC

    4/81

    The selection of hardware is very important in the existence and proper working of any

    software. When selecting hardware, the size and requirements are also important.

    The proposed System is developed on:

    Processor : INTEL core2duo

    RAM : 1GB

    Hard Disk Drive : 160GB

    2.2 SOFTWARE DESCRIPTION

    Operating System

    (i) For Server : Windows Server 2003

    (ii) For Client : Windows xp

    Framework : .Net Framework

    Back- End : MS SQL SERVER

    IDE : Microsoft Visual studio

    Web Technology : ASP.NET

    Web Server : IIS

    Language : C# .NET

    Project will be done in ASP. NET with C# as front end and SQL Server 2005 as back end.

    Microsoft .NET is framework that connects information, people, systems and devices. It spans

    clients, servers and developer tools and consists of:

    The .NET Framework programming model that enables developers to build Web-

    based applications which expose their functionality programmatically over a

    network using standard protocols such as HTTP.

    4

  • 7/28/2019 Mailing System DOC

    5/81

    Developer tools such as Microsoft Visual Studio .NET, which provide a rapid

    application integrated development environment for programming with the .NET

    Framework.

    Client software such as Windows XP, Windows CE and Microsoft Office XP that

    helps developers deliver a deep and compelling user experience across a family of

    devices and existing products.

    The .NET Framework is the programming model of the .NET environment for building,

    deploying and running Web- based applications, smart client applications and XML Web

    services. It manages much of the plumbing, enabling developers to focus on writing the business

    logic code for their applications. The .NET Framework includes the common language runtime

    and class libraries.

    5

  • 7/28/2019 Mailing System DOC

    6/81

    ORGANIZATIONAL

    PROFILE

    Krishna University largely caters to the higher educational needs of people in Krishna

    District in particular and Andhra Pradesh in general. Krishna district was one of the oldest

    British administered areas of Andhra Pradesh. It was formerly called Masulapatnam district, and

    in1859 when the then Guntur district was delinked, certain taluks, thereof, were added to this,

    which was renamed as Krishna district, after the mighty river Krishna. This district is endowed

    6

  • 7/28/2019 Mailing System DOC

    7/81

    with a rich variety of soils, and occupies an important place in agriculture. This district is also

    known for the availability of mineral sources like Chromites, Diamonds, Iron ore, Limestone,

    Mica and Sulphur. This district has a geographical area of 8727 Sq Mt with a population of

    around 42 lakhs. This District is endowed with one of the largest fresh water lakes called Kolleru

    Lake.

    Krishna University is established in a great historic coastal town called Machilipatnam,

    which are the head quartos of Krishna district of Andhra Pradesh. Machilipatnam is a city and a

    special grade municipality in Krishna district in Indian state of Andhra Pradesh

    Krishna University is presently located at Andhra Jateeya kalasala, a famous first grade

    college in Machilipatnam. The university will function from the academic year 2008-09 in the

    academic blocks of A.J Kalasala Campus allotted for this purpose.

    7

  • 7/28/2019 Mailing System DOC

    8/81

    SYSTEM ANALYSIS

    4.1 DEFINITION

    System Analysis is the detailed study of the various operations performed by the system

    and their relationships within and outside the system. Analysis is the process of breaking

    something into its parts so that the whole may be understood. System analysis is concerned with

    becoming aware of the problem, identifying the relevant and most decisional variables, analyzing

    8

  • 7/28/2019 Mailing System DOC

    9/81

    and synthesizing the various factors and determining an optimal or at least a satisfactory

    solution. During this a problem is identified, alternate system solutions are studied and

    recommendations are made about committing the resources used to design the system

    4.2 PROPOSED SYSTEM

    Mailing System is aimed at developing a web-based and central process system for

    communication purposes in Educational institutions. Some features of this system will be storing

    mails, replies to the mails, composing mails, sending attachments, etc.

    4.3 ADVANTAGES

    Speed: As the application is developed on Local Net, the messages are delivered

    instantly resulting fast communication.

    Easy to prioritize: Since the mails have subject lines, it is easy to prioritize them and

    ignore unwanted mails.

    Reliable and secure: Constant efforts are being taken to improve the security in

    electronic mails. Thus making it one of the secured ways of communication.

    Informal and conversational: The language used in e-mails is generally simple and thus

    makes the communication informal. Sending and receiving e-mails takes less time, so it can be

    used as a tool for interaction.

    4.4 FEASIBILTY STUDY

    A feasibility analysis usually involves a through assessment of the operational (need),

    financial and technical aspects of a proposal. Feasibility study is the test of the system proposal

    made to identify whether the user needs may be satisfied using the current software and

    hardware technologies, whether the system will be cost effective from a business point of view

    and whether it can be developed with the given budgetary constraints. A feasibility study should

    9

  • 7/28/2019 Mailing System DOC

    10/81

    be relatively cheap and done at the earliest possible time. Depending on the study, the decision is

    made whether to go ahead with a more detailed analysis.

    When a new project is proposed, it normally goes through feasibility assessment.

    Feasibility study is carried out to determine whether the proposed system is possible to develop

    with available resources and what should be the cost consideration. Facts considered in the

    feasibility analysis were.

    Technical Feasibility

    Economic Feasibility

    Behavioral Feasibility

    4.4.1 Technical Feasibility

    Technical feasibility includes whether the technology is available in the market for

    development and its availability. The assessment of technical feasibility must be based on an

    outline design of system requirements in terms of input, output, files, programs and procedures.

    This can be qualified in terms of volumes of data, trends, frequency of updating, cycles of

    activity etc, in order to give an introduction of technical system. Considering our project if is

    technically feasible. Internal Management System with its emphasis on a more strategic decision

    making is fast gaining ground as a popular outsourced function.

    4.4.2 Economical Feasibility

    This feasibility study present tangible and intangible benefits from the prefect by

    comparing the development and operational cost. The technique of cost benefit analysis is often

    used as a basis for assessing economic feasibility. This system needs some more initial

    investment than the existing system, but it can be justifiable that it will improve quality of

    service.

    10

  • 7/28/2019 Mailing System DOC

    11/81

    Thus feasibility study should center along the following points:

    Improvement resulting over the existing method in terms of accuracy, timeliness.

    Cost comparison

    Estimate on the life expectancy of the hardware

    Overall objective

    Our project is economically feasible. It does not require much cost to be involved in the overall

    process. The overall objectives are in easing out the requirement processes.

    4.4.3 Behavioral/ Operational Feasibility

    This analysis involves how it will work when it is installed and the assessment of

    political and managerial environment in which it is implemented. People are inherently resistant

    to change and computers have been known to facilitate change. The new proposed system is very

    much useful to the useful to the users and there for it will accept broad audience from around the

    world.

    11

  • 7/28/2019 Mailing System DOC

    12/81

    SYSTEM DESIGN

    5.1 DEFINITION

    The most creative and challenging face of the system development is System Design. It

    provides the understanding and procedural details necessary for implementing the systemrecommended in the feasibility study. Design goes through the logical and physical stages of

    development.

    In designing a new system, the system analyst must have a clear understanding of the

    objectives, which the design is aiming to fulfill. The first step is to determine how the output is to

    12

  • 7/28/2019 Mailing System DOC

    13/81

    be produced and in what format. Second, input data and master files have to be designed to meet

    the requirements of the proposed output. The operational phases are handled through program

    construction and testing.

    Design of a system can be defined as a process of applying various techniques and

    principles for the purpose of defining a device, a process or a system in sufficient detail to permit

    its physical realization. Thus system design is a solution to how to approach to the creation of

    a new system. Thus important phase provides the understanding and the procedural details

    necessary for implementing the system recommended in the feasibility study. The design step

    provides a data design, architectural design, and a procedural design.

    5.2 OUTPUT DESIGN

    In the output design, the emphasis is on producing a hard copy of the information

    requested or displaying the output on the CRT screen in a predetermined format. Two of the

    most output media today are printers and the screen. Most users now access their reports from a

    hard copy or screen display. Computers output is the most important and direct source of

    information to the user, efficient, logical, output design should improve the systems relations

    with the user and help in decision-making.

    As the outputs are the most important source of information to the user, better design

    should improve the systems relation and also should help in decision-making. The output

    devices capability, print capability, print capability, response time requirements etc should also

    be considered form design elaborates the way output is presented and layout available for

    capturing information. Its very helpful to produce the clear, accurate and speedy information for

    end users.

    5.3 INPUT DESIGN

    In the input design, user-oriented inputs are converted into a computer based system

    format. It also includes determining the record media, method of input, speed of capture and

    entry on to the screen. Online data entry accepts commands and data through a keyboard. The

    13

  • 7/28/2019 Mailing System DOC

    14/81

    major approach to input design is the menu and the prompt design. In each alternative, the users

    options are predefined. The data flow diagram indicates logical data flow, data stores, source and

    destination. Input data are collected and organized into a group of similar data. Once identified

    input media are selected for processing.

    In this software, importance is given to develop Graphical User Interface (GUI), which is

    an important factor in developing efficient and user-friendly software. For inputting user data,

    attractive forms are designed. User can also select desired options from the menu, which

    provides all possible facilities.

    Also the important input format is designed in such a way that accidental errors are

    avoided. The user has to input only just the minimum data required, which also helps in avoiding

    the errors that the users may make. Accurate designing of the input format is very important in

    developing efficient software. The goal or input design is to make entry as easy, logical and free

    from errors.

    5.4 SOFTWARE DESIGN

    It is a process of planning the new or modified system. Analysis specifies what a

    new or modified system does. Design specifies how to accomplish the same. Design is

    essentially a bridge between requirement specification and the final solution satisfying the

    requirements. Design of a system is essentially a blue print or a solution for the system.

    The design process for a software system has two levels. At first level the focus is

    on depending in which modules are needed for the system, the specification of these modules

    and how the modules should be interconnected. This is what is called system designing of top

    level design. In the second level, the internal design of the modules, or how the specification of

    the module can be satisfied is described upon. This design level is often called detailed design or

    logic design.

    14

  • 7/28/2019 Mailing System DOC

    15/81

    The first level produces system design, which defines the components needed for

    the system, and how the components interact with each other. It focus is on depending on in

    which that modules are needed for the system, the specification of these modules and how the

    module should be interconnected.

    5.4.1Introduction to UML

    Unified Modeling Language is the one of the most exciting tools in the world of

    system development today. Because UML enables system builders to create blue prints that

    capture their visions in a standard, easy to understand way and communicate them to others.

    The UML is brain child of Grady Brooch, James Rumbaugh and Ivar Jacobson.

    The UML is a language for

    Visualizing

    Specifying

    Constructing

    Documenting

    These are the artifacts of a software-intensive system. The abbreviation for UML

    is Unified Modeling Language and is being brought of a designed to make sure that the existing

    ER Diagrams which do not serve the purpose will be replaced by this UML Diagrams where in

    these language as its own set of Diagrams.

    Some of the Diagrams that help for the Diagrammatic Approach for the Object

    Oriented Software Engineering are:

    Class Diagrams

    Use Case Diagrams

    Sequence Diagrams

    State Chart Diagrams

    Activity Diagrams

    15

  • 7/28/2019 Mailing System DOC

    16/81

    Using the above mentioned diagrams we can show the entire system regarding the

    working of the system or the flow of control and sequence of flow the state of the system and the

    activities involved in the system.

    5.4.2 Components of the UML:

    The UML consists of a number of graphical elements that combine to form

    diagrams. Because its a language, the UML has rules for combining these elements. The

    purpose of the diagrams to present multiple views of the system, and this set of multiple views is

    called a Model. A UML Model of a system is something like a scale model of a building. UML

    model describes what a system is supposed to do. It doesnt tell how to implement the system.

    The following are the main nine component Diagrams of UML:

    5.4.3 Class Diagram:

    A Class is a category or group of things that has similar attributes and common

    behavior. A Rectangle is the icon that represents the class it is divided into three areas. The upper

    most area contains the name, the middle area contains the attributes and the lowest areas show

    the operations. Class diagrams provides the representation that developers work from. Class

    diagrams help on the analysis side, too.

    5.4.4 Object Diagram:

    An object is an instance of a class- A specific thing that has specific values of the

    attributes and behavior. A Rectangle is the icon that represents the object diagram but the name

    is underlined. The name of the specific instance is on the left side of the colon, and the name of

    the class is on the right side of the colon .

    5.4.5 Use-Case Diagram:

    A Use-Case is a description of a systems behavior from a users stand point. For

    system developer this is a valuable tool: its a tried-and-true technique for gathering system

    requirements from a users point of view. That is important if the goal is to build a system that

    16

  • 7/28/2019 Mailing System DOC

    17/81

    real people can use. A little stick figure is used to identify an actor the ellipse represents use-

    case.

    5.4.6 State Diagram:

    At any given time, an object is in particular state. One way to characterize change

    in a system is to say that its objects change the state in response to events and to time. The UML

    State Diagram captures these kinds of changes it presents the states an object can be in along

    with the transitions between the states, and shows the starting point and end point of a sequence

    of state changes.

    A Rounded Rectangle represents a state, along with the solid line and arrow head

    that represents a transition. The arrow head points to the state being transition into. The solid

    circle symbolizes starting point and the bulls eye that symbolizes the end point.

    5.4.7 Sequence Diagrams:

    In a functioning system objects interacts with one another and these interactions

    occur over time. The UML Sequence Diagrams shows the time based dynamics of the

    interaction. The sequence diagrams consist of objects represented in the usualway-as named

    rectangles (If the name underlined), messages represented as solid line arrows and time

    represented as a vertical progression.

    5.4.8 Activity Diagrams:

    The state diagram shows the states of an object and represents activities as arrows

    connecting the states. The Activity Diagram highlights the activities. Each activity is represented

    by a rounded rectangle-narrower and more oval-shaped than the state icon. An arrow represents

    the transition from the one activity to the next. The activity diagram has a starting point

    represented by filled-in circle, and an end point represented by bulls eye.

    5.4.9 Collaboration Diagram:

    17

  • 7/28/2019 Mailing System DOC

    18/81

    An object diagram shows the objects and their relationships with one another. A

    collaboration Diagram is an extension of the object diagram. In addition to the associations

    among objects, the collaboration diagram shows the messages the objects and each other.

    5.5 Use cases:

    Use case Model:

    The functional model, represented in UML with use case diagrams,

    describes the functionality of the system from the users point of view. Use cases are

    used during requirements elicitation and analysis to represent the functionality of the

    system. A use case describes a function provided by the system that yields a visible result

    for an actor. An actor describes any entity that interacts with the system. An actor can be human

    or an external system. In this proposed system actors are Administrator, Manager, Technical

    person and Customer.

    USE CASE DIAGRAMS:

    UML provides the use case diagram to facilitate the process of requirements

    gathering. The Use case diagram models the interactions between the systems external clients

    and the use cases of the system.

    18

    USE-CASE DIAGRAM

  • 7/28/2019 Mailing System DOC

    19/81

    19

    Registratio

    n

    Login

    Inbox

    Reply

    Compose

    Mail

    Sent

    Mail

    Use

    r

    Settings

    Sign Out

  • 7/28/2019 Mailing System DOC

    20/81

    CLASS DIAGRAM:

    20

    Login

    Inbox

    Compose Mail

    Users

    Profile

    Sign Out

    Administrator

  • 7/28/2019 Mailing System DOC

    21/81

    The object model, represented in UML with Class diagrams, Describes the

    structure of system in terms of objects, attributes, associations.

    The UML enables us to model the classes in a system and their relationships via class

    diagrams. In a class diagram, each class is modeled as a rectangle. This rectangle can be divided into

    three parts. The top part contains the name of the class. The middle part contains the classs attributes.

    The bottom contains the classs operations. The UML defines object diagrams which are similar to class

    diagrams except that they model objects and links-links are relationships between objects. Object

    diagrams present a snapshot of the structure while the system is running this provides information about

    which objects are participating in the system at a specific point in time.

    21

  • 7/28/2019 Mailing System DOC

    22/81

    INBOX

    Public SqlConnection con

    Public DataSet ds

    Public SqlCommand cmd

    Page_Load(object sender, EventArgs e)

    c1_CheckedChanged(object sender, EventArgs e)

    GridView1_RowDeleting(object sender, GridViewDeleteEventArgs e)

    22

    LOGIN

    Public SqlConnection con

    Public SqlCommand cmd

    Public int i

    Button3_Click(object sender, EventArgs e)

    Button2_Click(object sender, EventArgs e)

    LinkButton1_Click(object sender, EventArgs e)

    Page_Load(object sender, EventArgs e)

  • 7/28/2019 Mailing System DOC

    23/81

    Linkbutton1_Command(object sender, CommandEventArgs e)

    Linkbutton10_Command(object sender, CommandEventArgs e)

    GridView1_PageIndexChanging(object sender,

    GridViewPageEventArgs e)

    LinkButton4_Click(object sender, EventArgs e)

    ADMIN_LOGIN

    Protected Page_Load(object sender, EventArgs e)

    Protected Button1_Click(object sender, EventArgs e)

    Protected Button2_Click(object sender, EventArgs e)

    REGISTRATION

    Public string g

    Public SqlConnection con

    Public SqlCommand cmd

    Protected Button1_Click(object sender, EventArgs e)

    Protected DropDownList1_SelectedIndexChanged(object

    sender, EventArgs e)

    Protected DropDownList3_SelectedIndexChanged(object

    sender, EventArgs e)

    Protected Page_Load(object sender, EventArgs e)

    Protected Button3_Click(object sender, EventArgs e)

    Protected Button2_Click(object sender, EventArgs e)

    23

  • 7/28/2019 Mailing System DOC

    24/81

    INBOX

    Public SqlConnection con

    Public DataSet ds

    Public SqlCommand cmd

    Protected Page_Load(object sender, EventArgs e)

    Protected c1_CheckedChanged(object sender, EventArgs e)

    Protected GridView1_RowDeleting(object sender,

    GridViewDeleteEventArgs e)

    Protected Linkbutton1_Command(object sender,

    CommandEventArgs e)

    Protected Linkbutton10_Command(object sender,

    CommandEventArgs e)

    Protected GridView1_PageIndexChanging(object sender,

    GridViewPageEventArgs e)

    Protected LinkButton4_Click(object sender, EventArgs e)

    ADMIN_INBOX

    Public SqlConnection con

    Public SqlDataAdapter da

    public DataSet ds

    24

  • 7/28/2019 Mailing System DOC

    25/81

    Protected Page_Load(object sender, EventArgs e)

    ADMIN_COMPOSE_MAIL

    Public SqlConnection con

    Public SqlCommand cmd

    Protected Button1_Click(object sender, EventArgs e)

    COMPOSE_MAIL

    Public SqlConnection con

    Public SqlCommand cmd

    Protected LinkButton3_Click(object sender, EventArgs e)

    Protected Button1_Click(object sender, EventArgs e)

    Protected Button3_Click(object sender, EventArgs e)

    SENT_MAIL

    Public SqlConnection con

    Public SqlCommand cmd

    Public SqlDataReader dr

    Public DataSet ds

    Protected Page_Load(object sender, EventArgs e)

    25

  • 7/28/2019 Mailing System DOC

    26/81

    FEED

    Public SqlConnection con

    Pulic SqlCommand cmd

    Protected Page_Load(object sender, EventArgs e)

    Protected Button1_Click(object sender, EventArgs e)

    Protected Button2_Click(object sender, EventArgs e)

    Protected LinkButton1_Click(object sender, EventArgs e)

    MESSAGE

    Protected Page_Load(object sender, EventArgs e)

    Protected LinkButton3_Click(object sender, EventArgs e)

    REPLY

    Public SqlConnection con

    Public SqlCommand cmd

    Public SqlDataAdapter da

    Protected Button1_Click(object sender, EventArgs e)

    Protected Button1_Click(object sender, EventArgs e)

    26

  • 7/28/2019 Mailing System DOC

    27/81

    VIEWPROFILE

    Public SqlConnection con

    Public SqlCommand cmd

    Public DataSet ds

    Public SqlDataAdapter da

    Protected Page_Load(object sender, EventArgs e)

    PASSWORD_RECOVERY

    Public SqlConnection con

    Public SqlCommand cmd

    Public SqlDataReader dr

    Public string ans, pwd

    Protected Button2_Click(object sender, EventArgs e)

    Protected Button3_Click(object sender, EventArgs e)

    27

  • 7/28/2019 Mailing System DOC

    28/81

    SETTINGS

    Public SqlConnection con

    Public SqlCommand cmd

    Public SqlDataReader dr

    Public DataSet ds

    Protected LinkButton3_Click(object sender, EventArgs e)

    Protected Button1_Click(object sender, EventArgs e)

    Protected LinkButton4_Click(object sender, EventArgs e)

    ADMIN_INBOX

    Public SqlConnection con

    Public SqlDataAdapter da

    public DataSet ds

    Protected Page_Load(object sender, EventArgs e)

    USER_S_PROFILE

    Public SqlConnection con

    Public SqlCommand cmd

    Public DataSet ds

    Protected Page_Load(object sender, EventArgs e)

    Protected GridView1_RowDeleting(object sender,

    GridViewDeleteEventArgs e)

    28

  • 7/28/2019 Mailing System DOC

    29/81

    ADMIN_COMPOSE_MAIL

    Public SqlConnection con

    Public SqlCommand cmd

    Protected Button1_Click(object sender, EventArgs e)

    ADMINMESSAGE

    Protected Page_Load(object sender, EventArgs e)

    Protected LinkButton3_Click(object sender, EventArgs e)

    Protected Button1_Click(object sender, EventArgs e)

    ADMINREPLY

    Public SqlConnection con

    Public SqlCommand cmd

    Public SqlDataAdapter da

    public DataSet ds

    Protected Page_Load(object sender, EventArgs e)

    Protected Button1_Click(object sender, EventArgs e)

    29

  • 7/28/2019 Mailing System DOC

    30/81

    SEQUENCE DIAGRAM

    Sequence diagrams describe behavior as a sequence of messages exchanges among se

    toff objects. The sequence diagrams consists of objects represented in the usual way as named

    rectangles with underlined, messages represented as solid-line arrows and time represented as

    a vertical progress.

    D:DatabaseU:user w:Website

    1. Login

    4.Displays the Inbox page

    5. Compose mail

    6. Sending message

    7. Change the Info & Update

    10. Sign out

    8. Store s the mail details

    9.Stored

    3.Invalid UserId & Pwd

    2. Checking the login details

    figure: User Login

    30

  • 7/28/2019 Mailing System DOC

    31/81

    DATABASE

    SPECIFICATION

    Table: Members

    31

  • 7/28/2019 Mailing System DOC

    32/81

    Field Name Data Type Size Constraints

    First Name Varchar 50

    Last Name Varchar 50

    UserID Varchar 50 Primary Key

    Password Varchar 50

    DOB Varchar 50

    Department Varchar 50

    Designation Varchar 100

    Gender Varchar 50

    Mobile No Bigint

    Telephone No Bigint 50

    Address Varchar 300

    Security Question Varchar 50

    Answer Varchar 50

    Type Varchar 50

    Table: Mails

    32

  • 7/28/2019 Mailing System DOC

    33/81

    Table : admin

    Field Name Data Type Size

    FromMail Varchar 50

    Mailto Varchar 50

    Subject Varchar 50

    BodyOfTheMessage Varchar 50

    33

    Field Name Data Type Size

    From mail Varchar 50

    MailTo Varchar 50

    Subject Varchar 50

    BodyOfTheMessage Varchar 600

    Cc Varchar 50

    Bcc Varchar 50

    FileName Varchar 50

  • 7/28/2019 Mailing System DOC

    34/81

    :

    IMPLEMENTATION

    34

  • 7/28/2019 Mailing System DOC

    35/81

    Webpage design code for Login:

    .style1{

    width: 100%;

    }.style2

    {

    color: #FF3300;

    font-weight: bold;}

    .style3

    {width: 205px;

    }

    WELCOME TO UNIVERSITY MAILING

    UserID shoudnot be Empty

    35

  • 7/28/2019 Mailing System DOC

    36/81

    Enter

    the Password

    Forgot

    36

  • 7/28/2019 Mailing System DOC

    37/81

    Password

    37

  • 7/28/2019 Mailing System DOC

    38/81

    Webpage design code for Inbox:

    .style4

    {height: 341px;

    }


    Delete

    All

    FROM MAIL

    MAIL TO

    38

  • 7/28/2019 Mailing System DOC

    39/81

    SUBJECT

    ATTACHMENTS


    Any

    Feedback

    39

  • 7/28/2019 Mailing System DOC

    40/81

    Webpage design code for Admin Inbox :

    FROM MAIL

    MAIL TO

    SUBJECT

    40

  • 7/28/2019 Mailing System DOC

    41/81

    ATTACHMENTS

    Webpage Server code for Login:

    41

  • 7/28/2019 Mailing System DOC

    42/81

    using System;

    using System.Collections;

    using System.Configuration;using System.Data;

    using System.Linq;

    using System.Web;using System.Web.Security;

    using System.Web.UI;

    using System.Web.UI.HtmlControls;using System.Web.UI.WebControls;

    using System.Web.UI.WebControls.WebParts;

    using System.Xml.Linq;

    using System.Data.SqlClient;public partial class Login : System.Web.UI.Page

    {

    int i;

    protected void Button3_Click(object sender, EventArgs e){

    SqlConnectioncon=newSqlConnection(ConfigurationManager.Con

    nectionStrings["con"].ToString());

    SqlCommand cmd = new SqlCommand();cmd.Connection = con;

    cmd.CommandText = "select count(*) from Members where UserID='" + TextBox3.Text

    +Label4.Text + "' and Password='" + TextBox2.Text + "'";

    con.Open();int i = Convert.ToInt32(cmd.ExecuteScalar());

    if (i == 0)

    {Label3.Text = "Invalid User Id/Password";

    }

    else{

    FormsAuthentication.Authenticate(TextBox3.Text, TextBox2.Text);

    FormsAuthentication.GetAuthCookie(TextBox3.Text, CheckBox3.Checked);

    Session["uid"] = TextBox3.Text + Label4 .Text ;Session["pwd"] = TextBox2.Text;

    Response.Redirect("Inbox.aspx");

    }con.Close();

    cmd.Dispose();

    }

    protected void Button2_Click(object sender, EventArgs e)

    {

    TextBox3.Text = "";

    42

  • 7/28/2019 Mailing System DOC

    43/81

    TextBox2.Text = "";

    }

    protected void LinkButton1_Click(object sender, EventArgs e){

    Response.Redirect("Password Recovery.aspx");

    }

    protected void Page_Load(object sender, EventArgs e)

    {TextBox3.Focus();

    }

    }

    Webpage Server code for Inbox:

    using System;using System.Collections;

    43

  • 7/28/2019 Mailing System DOC

    44/81

    using System.Configuration;

    using System.Data;

    using System.Linq;using System.Web;

    using System.Web.Security;

    using System.Web.UI;using System.Web.UI.HtmlControls;

    using System.Web.UI.WebControls;

    using System.Web.UI.WebControls.WebParts;using System.Xml.Linq;

    using System.Data.SqlClient;

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

    {SqlConnectioncon=newSqlConnection(ConfigurationManager.ConnectionStrings["c

    on"].ToString());

    DataSet ds = new DataSet();

    SqlCommand cmd = new SqlCommand();protected void Page_Load(object sender, EventArgs e)

    {

    SqlCommand cmd = new SqlCommand("select count(*) from Mails where MailTo='" +

    Session["uid"] + "' and status='U'", con);con.Open();

    int i = Convert .ToInt32 ( cmd.ExecuteScalar());

    Menu Menu3 = (Menu)Master.FindControl("Menu2");

    Menu3.Items[1].Text = "Inbox(" + i.ToString() + ")";con.Close();

    cmd.Dispose();

    if (Page.IsPostBack == false)

    {

    con.Open();SqlDataAdapterda=newSqlDataAdapter("selectFromMail,MailTo,Subject,Filena

    me,Status from Mails where Mailto='" + Session["uid"] + "'", con);

    DataSet ds = new DataSet();

    da.Fill(ds, "hi");GridView1.DataSource = ds.Tables[0];

    GridView1.DataBind();

    con.Close();int d = 0;

    for (d = 0; d < GridView1.Rows.Count; d++)

    {GridViewRow R = GridView1.Rows[d];

    if (ds.Tables["hi"].Rows[d][4].ToString() == "U")

    {

    R.BackColor = System.Drawing.Color.BlueViolet ;

    44

  • 7/28/2019 Mailing System DOC

    45/81

    }

    else

    {R.BackColor = System.Drawing.Color.White ;

    }

    }}

    }

    protected void c1_CheckedChanged(object sender, EventArgs e){

    GridViewRow r = GridView1.HeaderRow;

    CheckBox c1 = (CheckBox)r.Cells[1].Controls[1];

    if (c1.Checked == true){

    foreach (GridViewRow R in GridView1.Rows)

    {

    CheckBox c2 = (CheckBox)R.FindControl("c2");c2.Checked = true;

    }}

    else if (c1.Checked == false)

    {foreach (GridViewRow R in GridView1.Rows)

    {

    CheckBox c2 = (CheckBox)R.FindControl("c2");

    c2.Checked = false;}

    }

    }protected void GridView1_RowDeleting(object sender, GridViewDeleteEventArgs e)

    {

    GridViewRow r = GridView1.Rows[e.RowIndex];LinkButton lfrom = (LinkButton)r.Cells[4].Controls[0];

    string s = lfrom.Text;

    SqlCommand cmd = new SqlCommand("delete from Mails where Subject='" + s +

    "'",con );con.Open();

    cmd.ExecuteNonQuery();

    con.Close();SqlDataAdapterda=newSqlDataAdapter("select

    FromMail,MailTo,Subject,Filename,Status from Mails where Mailto='" + Session["uid"] + "'",

    con);DataSet ds = new DataSet();

    da.Fill(ds, "chaitu");

    GridView1.DataSource = ds.Tables[0];

    GridView1.DataBind();

    45

  • 7/28/2019 Mailing System DOC

    46/81

    }

    protected void Linkbutton1_Command(object sender, CommandEventArgs e)

    {

    string sub = e.CommandArgument.ToString();

    string comd = "update mails set status='R' where Subject='" + sub + "'";SqlCommand cmd = new SqlCommand(comd, con);

    con.Open();

    cmd.ExecuteNonQuery();con.Close();

    SqlDataAdapter da = new SqlDataAdapter("select BodyOfTheMEssage from Mails where

    Subject='" + sub + "'", con);

    DataSet dx = new DataSet();da.Fill(dx, "body");

    string body = dx.Tables[0].Rows[0][0].ToString();

    Response.Redirect("Message.aspx?sub=" + body);

    }protected void Linkbutton10_Command(object sender, CommandEventArgs e)

    {if (e.CommandArgument.ToString() == "No Attachments")

    {

    }

    else

    {

    string attach = e.CommandArgument.ToString();Response.WriteFile("~/upload/" + e.CommandArgument.ToString());

    }

    }protected void GridView1_PageIndexChanging(object sender, GridViewPageEventArgs e)

    {

    GridView1.PageIndex = e.NewPageIndex;SqlDataAdapterda=new SqlDataAdapter("select FromMail,MailTo,Subject,Filename,Status

    from Mails where Mailto='" + Session["uid"] + "'", con);

    DataSet ds = new DataSet();

    da.Fill(ds, "chaitu");GridView1.DataSource = ds.Tables[0];

    GridView1.DataBind();

    }protected void LinkButton1_Click(object sender, EventArgs e)

    {

    Response.Redirect("Feed.aspx");}

    protected void LinkButton3_Click(object sender, EventArgs e)

    {

    46

  • 7/28/2019 Mailing System DOC

    47/81

  • 7/28/2019 Mailing System DOC

    48/81

    using System.Web;

    using System.Web.Security;

    using System.Web.UI;using System.Web.UI.HtmlControls;

    using System.Web.UI.WebControls;

    using System.Web.UI.WebControls.WebParts;using System.Xml.Linq;

    using System.Data.SqlClient;

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

    {

    SqlConnectioncon=newSqlConnection(ConfigurationManager.ConnectionStrings["con

    "].ToString());SqlDataAdapter da;

    protected void Page_Load(object sender, EventArgs e)

    { con.Open();

    SqlDataAdapter da = new SqlDataAdapter("select * from admin", con);DataSet ds = new DataSet();

    da.Fill(ds, "hi");

    GridView1.DataSource = ds.Tables[0];GridView1.DataBind();

    con.Close();

    if (Page.IsPostBack == false)

    {con.Open();

    da = new SqlDataAdapter("select * from admin where Mailto='" + Session["uid"] + "'",

    con);

    da.Fill(ds, "hi");

    GridView1.DataSource = ds.Tables[0];GridView1.DataBind();

    con.Close();

    int d = 0;

    for (d = 0; d < GridView1.Rows.Count; d++){

    GridViewRow R = GridView1.Rows[d];

    if (ds.Tables["hi"].Rows[d][4].ToString() == "U"){

    R.BackColor = System.Drawing.Color.BlueViolet;

    }else

    {

    R.BackColor = System.Drawing.Color.White;

    }

    48

  • 7/28/2019 Mailing System DOC

    49/81

    }

    }

    }protected void GridView1_PageIndexChanging(object sender, GridViewPageEventArgs e)

    {

    GridView1.PageIndex = e.NewPageIndex;SqlDataAdapter da = new SqlDataAdapter("select * from admin",con );

    DataSet ds = new DataSet();

    da.Fill(ds, "chaitu");GridView1.DataSource = ds.Tables[0];

    GridView1.DataBind();

    }protected void c1_CheckedChanged(object sender, EventArgs e)

    {

    GridViewRow r = GridView1.HeaderRow;

    CheckBox c1 = (CheckBox)r.Cells[1].Controls[1];if (c1.Checked == true)

    {foreach (GridViewRow R in GridView1.Rows)

    {

    CheckBox c2 = (CheckBox)R.FindControl("c2");c2.Checked = true;

    }

    }

    else if (c1.Checked == false){

    foreach (GridViewRow R in GridView1.Rows)

    {CheckBox c2 = (CheckBox)R.FindControl("c2");

    c2.Checked = false;

    }}

    }

    protected void GridView1_RowDeleting(object sender, GridViewDeleteEventArgs e)

    {GridViewRow r = GridView1.Rows[e.RowIndex];

    string s = r.Cells[1].Text;

    string command = "delete from admin where Frommail='" + s + "'" ;command = command + "delete from admin where Frommail='" + s + "'";

    SqlCommand cmd = new SqlCommand();

    cmd.Connection = con;cmd.CommandText = command;

    con.Open();

    cmd.ExecuteNonQuery();

    con.Close();

    49

  • 7/28/2019 Mailing System DOC

    50/81

    SqlDataAdapter da = new SqlDataAdapter("select * from admin ", con);

    DataSet ds = new DataSet();

    da.Fill(ds, "chaitu");GridView1.DataSource = ds.Tables[0];

    GridView1.DataBind();

    }protected void Linkbutton1_Command(object sender, CommandEventArgs e)

    {

    string sub = e.CommandArgument.ToString();

    string comd = "update admin set status='R' where Subject='" + sub + "'";

    SqlCommand cmd = new SqlCommand(comd, con);

    con.Open();cmd.ExecuteNonQuery();

    con.Close();

    SqlDataAdapter da = new SqlDataAdapter("select BodyOfTheMEssage from admin where

    Subject='" + sub + "'", con);DataSet dx = new DataSet();

    da.Fill(dx, "body");string body = dx.Tables[0].Rows[0][0].ToString();

    SqlDataAdapter da1=new SqlDataAdapter ("select Frommail from Admin where

    Subject='"+sub +"'",con);da1.Fill (dx,"admin");

    Session ["admin"]=dx.Tables ["admin"].Rows [0][0].ToString ();

    Response.Redirect("adminmessage.aspx?sub=" + body);

    }protected void Linkbutton10_Command(object sender, CommandEventArgs e)

    {

    if (e.CommandArgument.ToString() == "No Attachments"){

    }else

    {

    string attach = e.CommandArgument.ToString();

    Response.WriteFile("~/upload/" + e.CommandArgument.ToString());}

    }

    protected void LinkButton4_Click(object sender, EventArgs e)

    {

    Response.Redirect("Feed.aspx");}

    protected void LinkButton3_Click(object sender, EventArgs e)

    {

    50

  • 7/28/2019 Mailing System DOC

    51/81

    SqlCommand cmd = new SqlCommand("delete from Mails where MailTo='" +

    Session["uid"] + "' ", con);

    con.Open();cmd.ExecuteNonQuery();

    con.Close();

    SqlDataAdapter da = new SqlDataAdapter("select * from mails where MailTo='" +Session["uid"] + "'", con);

    DataSet ds = new DataSet();

    da.Fill(ds, "chaitu");GridView1.DataSource = ds.Tables[0];

    GridView1.DataBind();

    }

    protected void GridView1_SelectedIndexChanged(object sender, EventArgs e)

    {

    }}

    51

  • 7/28/2019 Mailing System DOC

    52/81

    TESTING

    Testing is a process to show the correctness of the program. Testing is needed to show

    completeness, improve the quality of the software and to provide the maintenance aid. Some

    testing standards are therefore necessary reduce the testing costs and operation time. Testing

    software extends throughout the coding phase and it represents the ultimate review of

    configurations, design and coding. Based on the way the software reacts to these testing, we can

    decide whether the configuration that has been built is study or not. All components of an

    application are tested, as the failure to do so many results in a series of bugs after the software

    put to use.

    52

  • 7/28/2019 Mailing System DOC

    53/81

    8.1 Black box Testing

    Black box testing, also called behavioral testing, focuses on the functional requirements of

    software. This testing approach enables the software engineer to derive the input conditions that

    will fully exercise all requirements for a program. Black box testing attempts to find the errors

    like

    Incorrect or missing functions

    Interface errors

    Errors in data structures or external database access

    Behavior or performance errors

    Initialization and termination errors

    In Black box testing software is exercised over a full range of inputs and outputs are observed for

    correctness.

    8.2 White box Testing

    White box testing is also called Glass box testing is a test case design control; structure of

    the procedural design to derive test cases using White box testing method, the software engineer

    can derive the test cases that guarantee that all independent paths within the module have been

    exercised at least once. Exercise all logic decisions on their true or false sides. Execute all loops

    at their boundaries and within their operational bounds. Exercise internal data structure to ensure

    their validity.

    8.3 Software Testing Strategies

    Testing involves

    Unit testing

    Integration testing

    Acceptance testing

    53

  • 7/28/2019 Mailing System DOC

    54/81

    The first level of test is unit testing. The purpose of unit testing is to ensure that each

    program is fully tested.

    The second step is integration testing. In this individual program units or programs are

    integrated and tested as a complete system to ensure that the software requirements are met.

    Acceptance Testing involves planning and the execution of various types of tests in order

    to demonstrate that the implemented software system satisfies the requirements. Finally our

    project meets the requirements after going through all the levels of testing.

    54

  • 7/28/2019 Mailing System DOC

    55/81

    DEMONSTRATION

    Home Page

    55

  • 7/28/2019 Mailing System DOC

    56/81

    Login Page

    56

  • 7/28/2019 Mailing System DOC

    57/81

    Admin Login

    57

  • 7/28/2019 Mailing System DOC

    58/81

    Registration page

    58

  • 7/28/2019 Mailing System DOC

    59/81

    About Us page

    59

  • 7/28/2019 Mailing System DOC

    60/81

    Contact us page

    60

  • 7/28/2019 Mailing System DOC

    61/81

    Inbox page

    61

  • 7/28/2019 Mailing System DOC

    62/81

    ComposeMail

    62

  • 7/28/2019 Mailing System DOC

    63/81

    SentMail

    63

  • 7/28/2019 Mailing System DOC

    64/81

    Settings page

    64

  • 7/28/2019 Mailing System DOC

    65/81

    Admin Inbox page

    65

  • 7/28/2019 Mailing System DOC

    66/81

    AdminComposepage

    66

  • 7/28/2019 Mailing System DOC

    67/81

    Users profile (Administrator)

    67

  • 7/28/2019 Mailing System DOC

    68/81

    View profile

    68

  • 7/28/2019 Mailing System DOC

    69/81

    69

  • 7/28/2019 Mailing System DOC

    70/81

    CONCLUSION

    70

  • 7/28/2019 Mailing System DOC

    71/81

    The Mailing System was developed with an aim of making the communication faster

    among different departments in bigger institutions. It meets the needs of several facilities not

    only passing messages but also sending larger files from one location to another through a local

    area network, thus by resulting time saving and accuracy.

    71

  • 7/28/2019 Mailing System DOC

    72/81

    APPENDIX

    72

  • 7/28/2019 Mailing System DOC

    73/81

    MICROSOFT VISUAL STUDIO

    Microsoft Visual Studio is Microsofts flagship software development product for

    computer programmers. It centers on an integrated distribution environment which has

    programmers create stand alone, and web services that run on any platforms supported by

    Microsofts .Net Framework (for all versions after 6). Supported platforms include Microsoft

    windows, servers and workstations, Pocket PC, Smart Phones and World Wide Web browsers

    not the Java Virtual Machine that all other java tools target.

    VISUAL STUDIO 2008

    The most important language added in this version was the introduction of generics,

    which are similar in many aspects to C++ templates. This potentially increases the number of

    bugs caught at compile- time instead of run- time by encouraging the use of strict type checking

    in areas where it was not possible before, C++ also got a similar upgrade with the addition of C+

    +/CLI which is slated to replace the use of Managed C++. Other new features of Visual Studio

    2005 include the Development Designer which allows application designs to be validated

    before deployments, an improved environment for web publishing when combined with

    ASP.NET 2.0 and load testing to see application performance under various sorts of user loads.

    Visual Studio 2008 also added extensive 64- bit support. While the development environment

    itself only available as a 32- bit application, visual C++ 2008 supports compiling for

    (x64AMD64 and EM64T) as well as IA- 64 (Itanium). The platforms SDK include 64- bit and

    64-bit versions of the libraries.

    73

  • 7/28/2019 Mailing System DOC

    74/81

    NET FRAMEWORK SDK

    The .NET framework is an integral windows component that supports building and

    running the next generation of applications and XML web services. The key component of the

    .NET frame work are the common language run time and the . NET frame work class library,

    which includes ADO.NET, ASP.NET and windows forms. The .NET framework provides a

    managed execution environment simplified development and deployment and integration with a

    wide variety of programming languages.

    This framework is made up of the following parts:

    The common language runtime(CLR)

    The base class libraries.

    Rich client user interface using windows forms

    RAD for the internet using web forms

    OVERVIEW OF THE .NET FRAME WORK

    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 following objectives:

    To provide a consistent object oriented programming environment whether object

    code is stored and executed locally but internet- distributed or executed remotely.

    To provide a code execution environment that minimizes software deployment

    and versioning conflicts.

    To provide a code execution environment that guarantees safe execution of code,

    including code created by an unknown or semi trusted third party.

    74

  • 7/28/2019 Mailing System DOC

    75/81

    To provide a code execution environment that eliminates the performance

    problem of scripted or interpreted environments.

    To make the developer experience consistent across widely types of application, such as

    windows based applications and web based applications.

    To build all communication on industry standards to ensure that code based on the .NET

    framework can integrate with any other code.

    The .NET framework has two main components: the common language runtime and

    the .Net framework class library. The common language runtime is the foundation of the .NET

    framework. You can think of the runtime as an agent that manages code at execution time, and

    remoting while also enforcing strict type safely and other forms of code accuracy that ensure

    security and robustness in fact the concept of code management is a fundamental principle of the

    runtime.

    Code that targets the runtime is known as managed code, while code that does not

    target the runtime is known as un managed code. The class library, the other main component of

    the .NET frameworks is a comprehensive, object-oriented collection reusable types that you can

    use to develop applications ranging from traditional command line or graphical user interface

    (FGUI) applications to application base d on the latest innovations provided by ASP.NET, such

    as web forms and XML web services.

    The .NET framework can be hosted by unmanaged component that load the common

    language runtime into their processes and initiate the execution of managed code. ASP.NET

    works directly with the runtime to enable ASP.NET application and XML web services, both of

    which are discussed later in this topic, Internet explorer is an example of unmanaged application

    that hosts the runtime (in the form of a MIME type extension). Using internet explorer to the

    host runtime enables you to embed managed components or windows forms controls in HTML

    documents. Hosting the runtime in this way makes mobile code 9similar to Microsoft Active Xr

    controls) possible, but with significant improvement that only managed code can offer, such as

    semi-trusted execution and secure isolated file storage.

    75

  • 7/28/2019 Mailing System DOC

    76/81

    The following illustration shows the relationship of the common language runtime and

    the class library to your application and to the overall system. The illustration also shows how

    managed code operated with in a larger architecture.

    We can use the .NET framework to develop the following types of application and services:

    Console applications

    Web applications

    XML Web services

    Windows Forms Applications

    COMMON LANGUAGE RUNTIME (CLR)

    The common language runtime (CLR) is responsible for runt-time services such as

    language integration; security enforcement; and memory, process and thread management. In

    addition, it has a roll at development time when features such as life cycle management strong

    type naming, cross-language exception handling, dynamic binding and so on, reduce the amount

    of code that a developer must write to turn the business logic the reusable component. The

    runtime can be hosted by high performance, server-side applications, such a s Microsoft Internet

    Information Services (IIS) for building web applications with ASP.NE and the next release of

    Microsoft SQL Server. This infrastructure enables you to use code managed by the .NET

    framework to write your business logic, while still enjoying the superior performance of the

    industrys best enterprises servers that support runtime hosting.

    76

  • 7/28/2019 Mailing System DOC

    77/81

    ASP.NET

    ASP.NET is a set of Microsoft.NET framework technologies used for building web

    applications and XML Web services. ASP.NET page execute on the server and generate mark

    up such as HTML, WML or XML that is sent to a desktop or mobile browser. ASP.NET pages

    use a compiled, event-driven programming model that improves performance and enables the

    separation of application logic and user interface. Both ASP.NET pages and ASP.NET web

    services files contain server-side (as opposed to client side logic) written in Visual basic .NET,

    C#.NET or any .NET compatible language, Web applications and XML Web Services take

    advantage of the features of the common language runtime, such as type safety, inheritance,

    language, interoperability, versioning, and integrated security.

    IIS

    Microsoft Internet Information S4ervices (IIS; formerly called Server is a set of

    Internet-based services for servers using Microsoft Windows. It is the worlds second most

    popular web server in terms of overall websites. As of September 2007 it served 34.94% of all

    websites and 36.63% of all active websites according to Net craft. The servers currently include

    FTP, SMTP, NNTOP, and HTTP/HTTPS.

    ADO.NET

    ADO.NET provides consistent access to data sources such a Microsoft SQL Server and

    XML, as well as to data sources exposed through OLE DB and ODBC. Data sharing consumer

    applications can use ADO.NET to connect to these data sources and retrieve, manipulate and

    update the data that they contain.ADO.NET separates data access from data manipulation into discrete components that

    can be used separately or in tandem. ADO.NET includes .NET Frame work data providers for

    connecting to a database, executing commands and retrieving results. Those results are either

    processed directly, placed in and ADO.NET Dataset objects in order to be exposed to the used in

    an ad hoc manner, combined with data from multiple sources or remoted between tiers.

    77

  • 7/28/2019 Mailing System DOC

    78/81

    The ADO.NET Dataset object can also be used independently of a .NET Framework data

    provider to manage data local to the application or sourced from XML.

    The ADO.NET classes are found in System.Data.dll and are integrated with the XML

    classes found in System.Xml.dll. When compiling code that uses the System. Data, namespace

    reference both System.Data.dll and System.Xml.dll.

    ADO.NET provided functionality to developers writing managed code similar to the

    functionality provided to native component object model (COM) developers by ActiveX Data

    Objects (ADO).

    ADO.NET COMPONENTS

    There are two components of ADO.NET that you can use to access and manipulate

    data:

    .NET Framework data providers.

    The Dataset

    .NET FRAMEWORK DATA PROVIDERS

    The .NET Framework Data providers are components that have been explicitly

    designed for data manipulation and fast, forward-only, read-only access to data. The connection

    object provides connectivity to a data source. The command object enables access to database

    commands to return data, modify data, run stored procedures and send or retrieve parameter

    information.

    The Data Adapter provides a high-performance stream of data from the data source.

    Finally, the Data Adapter provides the bridge between the Dataset object and the data source.

    The Data Adapter uses command object to execute SQL commands at the data source to both

    load the Dataset with data and reconcile changes made to the data in the Dataset back to the data

    source.

    78

  • 7/28/2019 Mailing System DOC

    79/81

    THE DATASET

    The ADO.NET Dataset is explicitly designed for data access independent of any data

    source. As a result, it can be used with multiple and differing data sources used with XML dataor used to manage data local to the application. The Dataset contains a collection n of one or

    more Data Table objects made up to rows and columns of data as well as primary key, foreign

    key, constraint and relation information about the data in the Data Table objects.

    BENEFITS OF ADO.NET

    ADO.NET offers several advantages over previous versions of ADO and over other

    data access components. These benefits fall into the following categories:

    1. Interoperability

    2. Maintainability

    3. Programmability

    4. Salability

    MICROSOFT DATA ACCSS COMPONENTS (MDAC)

    Microsoft Data Access Components (MDAC) is a collection of core files provided to

    help applications by providing a means of accessing data. MDAC includes core files for Open

    Database Connectivity (ODBC), ActiveX Data Objects (ADO), OLEDB, Network libraries and

    client configuration tool for SQL Server. Depending on your data access strategy, you may need

    to ensure that MDAC is installed on the client computers, the business servers, the Web servers

    or the database servers. MDAC 2.6 or later is required by the .NET Framework and at least

    MDAC 2.7 SP1 is recommended.

    79

  • 7/28/2019 Mailing System DOC

    80/81

    BIBLIOGRAPHY

    Windows programming Vikas Gupta

    80

  • 7/28/2019 Mailing System DOC

    81/81

    ASP. NET Unleashed Stephen Walther

    Visual C#.NET Black Book Steven Holzer

    Professional ASP. NET Web services Alex Homer, Dave Sussman