Complete Mailing System - MCA

1. ABSTRACT

           The project titled “complete mailing system” is a web application. This application is implemented is ASP.Net and SQL server. The design of the project mainly aimed at, to provide a platform for the effective communication between the users to users, and companies etc.            

           

            The aim is to develop object oriented Graphical User Interface application to the Complete Maling System.

            To give a user friendly, fully GUI application to the Complete Maling System. The objective of the system is easily send Information from one to another user and maintain all about employees ID’s in dynamic format and get any required information within fraction of seconds

 4.3 DATA FLOW DIAGRAM

            Graphical description of a system data and how the processor transforms the data is known as data flow diagrams.

           

            Data Flow Diagrams (DFD) are used for documenting the findings in data flow analysis. They graphically show the relation between processes a data. The transformation of data from input to output, through processes, may be described logically and independently of the physical components associated with the system. DFD’S quite easy to read and understand. There are two alternate but equivalent symbol sets.

There are four simple notations to complete a DFD

1. Data flow
2. Transform process
3. Data store
4. External entity

Advantages of DFD

·        These are simple notations, which are easily understood by users and those involved in the system.

·        Users can be involved in the study of DFD for more accuracy.            

·        Users can examine charts.

·        Avoiding mistakes early may prevent systems failure.

·        A circle represents a process or transforms that is applied to data or control.

·        An arrow represents flow of one or more data items or Data objects. All arrows on the Data flow diagram should be labeled.

     

            It is important to note that the diagram supplies no explicit indication of the sequence of the prosing, prouder or sequence may be implementation is generally delayed until software design.

The basic notations used to create a DFD are illustrated   in below figure:

External Entity

A procedure or consumer of information that resides  outside  the  bounds  of  the  system  to  be  modeled.      

 

Process

            A transfer of information (a function) that resides within the   bounds of the system to be modeled.

 

Data Objects

      The arrowhead indicates the direction of data flow.

 

Data Store

      A repository of data that is to be store for Use by one or more processes; may be as simple as Simple as a buffer or quick or as sophistic coated as a relational database. A rectangle is used to represents an internal entity or (Sink / Source) i.e.

 

0-LEVEL DATA FLOW DIAGRAM

Management System on Complete Mailing System

 

                  

               INPUT                                                         OUTPUT

CONTEXT LEVEL DATA FLOW DIAGRAM

                                     

                                                                                 Home Mail

                                                                                                      Register

                                                                                                      Inbox

                                                                                                      Sent box

                                                                                                      Trash

4.4 HARDWARE AND SOFTWARE REQUIREMENTS

  

Introduction

            Software requirements specify software and hardware requirement tools, that develop this application.

Hardware requirements

·        Processor                     :Pentium 4

·        Main memory               : 512MB + RAM

·        Hard disk drive : 80 GB

·        Mouse                          : Scroll

·        Keyboard                     : 102/103/104/ Multimedia

·        CD-Drive                     : Recommended

·        Monitor                        : 15 Preferably color Monitor

Software requirements

• Operating System                  :  Windows XP
• Front-End                               : Asp. NET

Back-End                                : SQL server

4.6 TABLE DESIGN

DATA BASE

Table name: Login

Column Name	Datatype	Length
Username	varchar	50
Password	varchar	50

Table name: Register

Column Name	Datatype	Length
Username	varchar	50
User Middle name	varchar	50
User Last name	varchar	50
Gender	varchar	50
Date of Birth	varchar	50
Address	varchar	50
City	varchar	50
Qualification	varchar	50
Phone Number	varchar	50
Register Date	varchar	50
Email ID	varchar	50
Password	varchar	50
Conform Password	varchar	50
Login ID	varchar	50

Table name: Inbox

Column Name	Datatype	Length
User Name	varchar	50
From User	varchar	50
Received Date	varchar	50
Subject	varchar	50
Particular	varchar	50

Table name: Sent

Column Name	Datatype	Length
User Name	varchar	50
To Login ID	varchar	50
To Subject	varchar	50
To Particular	varchar	50
Date & Time	varchar	50

                                              

Table name: Trash

Column Name	Datatype	Length
User Name	varchar	50
To Login ID	varchar	50
To Subject	varchar	50
To Particular	varchar	50
Date & Time	varchar	50

               

5. SYSTEM IMPLEMENTATION

5.1 MICROSOFT VISUAL Studio.NET

An overview of the Visual Studio.net Framework

            Unless you have been living under a rock for the past year, you must have heard of .net (“dot net”) by now.  What is .net?  Is it a new operating environment?  Is it a new language?  Is it a new way of developing distributed applications?  The answer is “Yes”: .net is all of these things and more.

            The .net world was created by Microsoft to allow users to have access to their information, files, or programs anywhere, anytime, and on any platform or device. When Microsoft introduced the first Windows operating system, it took application development and system design to a new level: multi-tasking.  With each new version of Windows, multi-tasking has been driven more towards distributed processing and .net is the next step. 

            Visual Studio.net has an entirely new, object-oriented framework.  In this paper I will introduce you to some of features in Visual Studio.Net, however, I will focus mostly on Asp.net.net and draw some comparisons to its predecessor VB 6.   The reader of this paper will not be able to start developing code in Asp.net.net after reading, but should have a high-level view of the changes in Asp.net.net and how they differ from previous versions.

As shown in Figure 1, Asp.net sits at the top of the framework (along with the other languages in Visual Studio.net).  Below that is the Common Language Specification (CLS).  This specification is a set of rules that govern the minimum language features that must be supported to ensure that a language will interoperate with other CLS-compliant components and tools.  As long as a language conforms to the CLS, it is guaranteed to work with the CLR.  In this way, when third-party compilers target the .net framework, as long as they conform to the CLS, the code is guaranteed to work.

            You might also notice that VB is now and “equal” or peer of C++, C# and any other language that is .net compliant.  Asp.net.net shares the same variable types, arrays, user-defined types, classes, graphical forms, visual controls and interfaces as these other languages.

Web Services

            Web Services provide a Web-enabled user interface with tools that include various HTML controls and Web controls.  Forms creating using Web Services are the same as forms created for a Windows application.  The code behind a Web form is the same as the code behind a Windows form.  The markup language that is used by Web forms is still there, but the Web form applications generate it for you.

User Interface

            At the same level as Web Services is the User Interface.  The User Interface is where Windows forms live.  It also provides code for drawing to the screen, printing, rendering text and displaying images.

Data and XML

            Both Web Services and the User Interface sit on top of the Data and XML block.  As you will learn later in this paper, XML (or extensible markup language) plays just as important of a role as data.  XML is used to provide a text view of data that can be shared between services on the same PC or passed through a firewall to a web server across the country using SOAP (more on SOAP a little later).

Base Class Library

            The base class library (BCL) is underneath the Data and XML block.  This area is the origin for the base class of all .net programs.  Everything in Asp.net.net is an object, and all objects originate from a class named System.  The BCL also provides collections, localization, text objects, interoperability with non-.net code and ActiveX controls and a variety of other services.

The Common Language Runtime

            At the base of the .net framework is the common language runtime (CLR).  Much like the Java Virtual Machine, the CLR is needed to make .net code run on any machine.

The CLR is a set of resources that any .net program can take advantage of, from any .net-supported language.  All languages will be more equal in capability than they ever have before.

            The CLR includes support for the BCL, where the architecture for controls and forms actually live.  It is also responsible for managing threads and exceptions (replacing the Err object in Visual studio).  Garbage collection is also handled by the CLR.

            The CLR takes code generated by VB and converts it to the native language of the current platform.  Through this conversion, the magic of multi platform execution is achieved.  Now VB programmers can write code in VB syntax and the CLR is responsible for converting it to any platform that can run the CLR.  The programmer is removed several layers from the hardware and doesn’t really need to know what platform his/her code is running on.

            One additional service of the CLR is handling bad code.  You have probably heard stories of rogue code that overran buffers and trashed a machine, killing all other programs along with it.  By design, this cannot happen with code written in Asp.net.net.

 

System Namespace

            The System namespace includes all classes that represent the base data types used by all Asp.net.net applications.  In .net, all of the base data types are Object, Byte, Char, Array, and so on.  Many of these correspond to the data type in classic VB.

            In addition to the base data types, the System namespace contain nearly 100 classes that provide functionality ranging from hand exceptions and forming delegates to dealing with the core run-time concepts such as application domains and the automatic memory manager.  The System namespace also contains 25 second-level namespaces, listed in Table 1.  Looking at these, you can see how the namespace convention logically separates functionality.

Table 1 – Secondary namespaces in the System Namespace

Namespaces	Description
System.CodeDom	Contains classes that can be used to represent the elements and structure of a source code document.
System.Collections	Contains interfaces and classes that define various collections of objects, such as lists, queues, arrays, hash tables and dictionaries.
System.ComponentModel	Provides classes that are used to implement and license components.
System.Configuration	Provides classes that give system run times, administrative tools, applications and other consumers of configuration information access to configuration information.
System.Data	Consists mostly of classes that constitute the Microsoft ADO.net architecture.
System.Diagnostics	Provides classes to debug applications and trace the execution of code.
Ssytem.DirectoryServices	Provides access to Active Directory from manage code.
System.Drawing	Provides access to the GDI+ basic graphics functionality.
System.EnterpriseServices	Provides transaction-processing functionality.
System.Globalization	Provides localization information on elements such as the current culture, formatting, data, and time for specific locales.
System.IO	Provides types that allow synchronous and asynchronous reading from and writing to data streams and files.
System.Management	Provides classes for manager of system object and events.
System.Messaging	Provides classes to connect to message queues on the network, send messages to queues and receive or “peek” messages from queues.
System.Net	Provides a simple programming interface to many of the protocols found on the network today.
System.Reflection	Contains classes and interfaces that provide a managed view of types, methods and fields, with the ability to dynamically create and invoke types.
System.Resources	Provides management of resources, such as a resource that contains culture-specific information.
System.Runtime	Provides infrastructure services,
System.Security	Provides the underlying structure of the .net framework security system, including interfaces, attributes, exceptions and base classes for permissions.
System.ServiceProcess	Provides classes to install and run services (non-interface executables).
System.Text	Contains classes representing ASCII, Unicode, UTF-7 and UTF-8 character encoding; abstract base classes for converting blocks of characters to and from blocks of bytes; a helper class that manipulates and formats String objects without creating intermediate instances of String.
System.Threading	Provides class and interfaces that enable multithreaded programming.
System.Timers	Provides two components that raise an event on an interval or more complex schedule.
System.Web	Supplies classes and interfaces that enable browser-server communication.
System.Windows.Forms	Contains classes for creating Windows-based applications and classes for many controls that can be added to forms.
System.Xml	Contains XML classes that provide standards-based support for processing XML.

                      One of the biggest improvements with .net, in my opinion, is the new common IDE.  As you can see in Figure 3, the IDE contains a little of all the

different classic Visual Studio languages.  There is an output window similar to the one in C++, the properties window similar to the one in VB; but best of all are the “slide-in” capabilities of the different explorer windows.

            There is now a server explorer that slides-in from the left side of the IDE.  This explorer allows the developer to have access to operating services, data connections, and best of all, SQL server.  I cannot tell you how many times I’ve wished that I could change a stored procedure or table design without having to load SQL Enterprise Manager to do so.  With the .net IDE, all of the tools are found right in the same application.  With the use of the “thumb-tack”, you can minimize explorers to gain more space for your code window if needed.

Asp.net

            ASP.NET is a managed framework that facilitates building server-side applications based on HTTP, HTML, XML and SOAP. To .NET developers, ASP.NET is a platform that provides one-stop shopping for all application development that requires the processing of HTTP requests.       

            Asp .NET provides the easiest, most productive language and tool for rapidly building Windows and Web applications. Asp.NET comes with enhanced visual designers, increased web application performance, and a powerful integrated development environment (IDE). It also supports creation of applications for wireless, Internet-enabled hand-held devices web application etc. The following are the features of Asp.Net are all about server-side features. Client-side control and interaction is possible but requires manual coding from the developer. This means that pure ASP applications often require frequent server roundtrips, and this in turn often compromises performance.

Building Web-based Applications

            With Asp.net .NET we can create Web applications using the shared Web Forms Designer and the familiar "drag and drop" feature. You can double-click and write code to respond to events. Asp.net .NET 2003 comes with an enhanced HTML Editor for working with complex Web pages. We can also use IntelliSense technology and tag completion, or choose the WYSIWYG editor for visual authoring of interactive Web applications.

Simplified Deployment

            With Asp.net .NET we can build applications more rapidly and deploy and maintain them with efficiency. Asp.net .NET 2003 and .NET Framework 1.1 makes "DLL Hell" a thing of the past. Side-by-side versioning enables multiple versions of the same component to live safely on the same machine so that applications can use a specific version of a component. XCOPY-deployment and Web auto-download of Windows-based applications combine the simplicity of Web page deployment and maintenance with the power of rich, responsive Windows-based applications.

Powerful, Flexible, Simplified Data Access

You can tackle any data access scenario easily with ADO.NET and ADO data access. The flexibility of ADO.NET enables data binding to any database, as well as classes, collections, and arrays, and provides true XML representation of data. Seamless access to ADO enables simple data access for connected data binding scenarios. Using ADO.NET, Asp.net .NET can gain high-speed access to MS SQL Server, Oracle, DB2, Microsoft Access, and more.

Improved Coding

            You can code faster and more effectively. A multitude of enhancements to the code editor, including enhanced IntelliSense, smart listing of code for greater readability and a background compiler for real-time notification of syntax errors transforms into a rapid application development (RAD) coding machine.

Direct Access to the Platform

            Asp.net developers can have full access to the capabilities available in .NET Framework 1.1. Developers can easily program system services including the event log, performance counters and file system. The new Windows Service project template enables to build real Microsoft Windows NT Services. Programming against Windows Services and creating new Windows Services is not available in Asp.net .NET Standard, it requires Visual Studio 2003 Professional, or higher.             

Full Object-Oriented Constructs

            You can create reusable, enterprise-class code using full object-oriented constructs. Language features include full implementation inheritance, encapsulation, and polymorphism. Structured exception handling provides a global error handler and eliminates spaghetti code.

XML Web Services

            XML Web services enable you to call components running on any platform using open Internet protocols. Working with XML Web services is easier where enhancements simplify the discovery and consumption of XML Web services that are located within any firewall. XML Web services can be built as easily as you would build any class in Asp.net.  The XML Web service project template builds all underlying Web service infrastructure.

Mobile Applications

            Asp.net .NET 2003 and the .NET Framework 1.1 offer integrated support for developing mobile Web applications for more than 200 Internet-enabled mobile devices.

            These new features give developers a single, mobile Web interface and programming model to support a broad range of Web devices, including WML 1.1 for WAP—enabled cellular phones, compact HTML (cHTML) for i-Mode phones, and HTML for Pocket PC, handheld devices, and pagers. Please note, Pocket PC programming is not available in Asp.net .NET Standard, it requires Visual Studio 2003 Professional, or higher.

COM Interoperability

            You can maintain your existing code without the need to recode. COM interoperability enables you to leverage your existing code assets and offers seamless bi-directional communication between Asp.net 6.0 and Asp.net .NET applications.

Reuse Existing Investments

            You can reuse all your existing ActiveX Controls. Windows Forms in Asp.net .NET 2003 provide a robust container for existing ActiveX controls. In addition, full support for existing ADO code and data binding enable a smooth transition to Asp.net .NET 2005.

Upgrade Wizard

            You upgrade your code to receive all of the benefits of Asp.net .NET 2005. The Asp.net .NET Upgrade Wizard, available in Asp.net .NET 2005 Standard Edition, and higher, upgrades up to 95 percent of existing Asp.net code and forms to Asp.net .NET with new support for Web classes and User Controls.

Source: Microsoft
Session and Application variables

l        Session variables

–        Hashtable-style collection of name-value pairs

–        Remembered until the client closes the browser (or the session timeout expires – default 20 minutes)

–        Only for one client

–        Session[“ValidUser”] = true

l      Application variables

–        Hashtable-style collection of name-value pairs

–        Always remembered

–        For all clients

–        Application[“NumClients”] = NumClients + 1

final note :

            Asp.net is a type-safe language (you can only access a variable through the type associated with that variable).  We should be used to using Option Explicit in C# code to require variable declaration, but Asp.net has a new directive called Option Strict.  This new directive prevents you from trying to overwrite data with a different data type and should always be included at the top of your class and form code.

The System.Object Class

            The System.Object class is much like the Object class in Java.  The System. Object class is the super class of all classes the in .net framework—it’s the only class in .net that does not inherit from any other object type.  All objects must either explicitly or implicitly declare support for exactly one or the other object type.  In .net it is impossible to use a class that does not inherit from System. Object. 

            There are six methods inherited by all classes that come from the System.Object class, see Table 3 below.

Table 3 – Inherited Methods from System.Object

Namespaces	Access	Description
Equals	Public	Takes another object as a parameter and returns a Boolean that indicates whether the two objects are equal.
GetHashCode	Public	Returns an integer hash code that represents the object’s value.  This code is usually used as a key when the object is added to a collection.  Two identical objects should generate the same code.
Finalize	Protected	The CLR calls an object’s Finalize method to notify the object that the object is about to be destroyed.  This method really does nothing and is overridden by the class.
MemberwiseClone	Protected	Creates a shallow copy of the object.
GetType	Public	Returns an instance of System.Type, which is used to get information about the object through metadata.
ToString	Public	Returns a string representation of the object.

 

Garbage Collection in Asp.net

            In Visual Studio, when you were finished using an object, you simply set it to nothing and the object would be released.  This is no longer the case with Asp.net.net.  In Asp.net.net, when a variable loses scope, the CLR destroys the object and removes it from the stack automatically for you.

ASP.NET Overview and Features

—        ASP.NET provides services to allow the creation, deployment, and execution of
Web Applications and Web Services

—        Web Applications are built using Web Forms

—        Web Forms are designed to make building
web-based applications as easy as building Visual Basic applications

—        Built on .NET Framework: any .NET programming language can be used (C#, Visual Basic)

—        Complete object model

—        Separation of code and UI

—        Maintains page state

—        Session management

—       Caching, Debugging, Extensibility

Asp.NET Features:

—        True object Oriented Programming

—        ASPX, ASP – side by side

—        Simplified programming model

—        Simplified deployment

—        Better performance

—        Caching

—        Security

—        Powerful controls

—        Simplified browser support

—        Simplified form validation

—        Code behind pages

—        More powerful data access

—        Web services

—        Better session management

—        Simplified browser support

—        Simplified form validation

—        Code behind pages

—        More powerful data access

—        Web services

—        Better session management

—        Microsoft. Net Framework

—        Common Language runtime

—        .NET Framework Class Library

—        Client Application Development

—        Front End Used

—       Language Support

—       Multithreading

Webpage.aspx  Example

—        When the form is processed on the server, the run at attribute is removed.

—        Only those elements marked in the ASPX file with runat="server" are modified or replaced in the generated XHTML.

Webpage.aspx  Example
Creating an ASP.NET Web Application using Visual Studio

Step 1: Creating the Web Application Project

—        Select File > New Web Site... and choose ASP.NET Web Site in the Templates pane.

—        Select File System from the drop-down list closest to Location.

—        Set the Language drop-down list to Visual C#, and click OK.

Webpage.aspx  Example

—        An ASPX file (i.e., Web Form) named Default.aspx is created for each new project.

—        Visual Web Developer creates a code-behind file named Default.aspx.cs.

—        The View Designer button opens the Web Form in Design mode.

—        The Copy Web Site button allows you to copy the project’s files to another location, such as a remote web server.

—        Finally, the ASP.NET Configuration button takes you
to the Web Site Administration Tool.

—        Look at Toolbox displayed in the IDE when the project loads.

Standard and Data list of web controls

Editing the Webpage.aspx

—        When the project loads for the first time, the Web Forms Designer displays the auto generated ASPX file in Source mode.

—        Design mode indicates the XHTML element where the cursor is currently located.

—        You can also view both the markup and the web-page design at the same time by using Split mode

—        Right click the ASPX file in the Solution Explorer
and select View Code to open the code-behind file.

Renaming the Webpage.aspx

Renaming the ASPX File

—        Right click the ASPX file in the Solution Explorer and select Rename.

—        Enter the new file name Webpage.aspx and press Enter. Both the ASPX file and the code-behind file are updated.

Renaming the Class in the Code-Behind File and Updating the ASPX File

—                    Visual Studio’s refactoring tool, which automatically updates      the existing references to this class in the rest of the project to        reflect this change.

—                    Right click the class name in the partial class’s declaration and    select Refactor > Rename… to open the Rename      dialog.

Webpage.aspx  Example

Changing the Title of the Page

—        We change the page’s title from the default Untitled Page to A Simple Web Form Example.

—        Open the ASPX file in Source mode and modify the text between the <title> tags.

—        Alternatively, you can modify the Web Form’s Title property in the Properties window.

—        To view the Web Form’s properties, select DOCUMENT from the drop-down list in the Properties window.

Designing the Page

—        To add controls to the page, you can drag and drop them from the Toolbox onto the Web Form in Design mode.

—        Like the Web Form itself, each control is an object that has properties, methods and events.

—        You can type text directly on a Web Form at the cursor location or insert XHTML elements using menu commands.

—        The positions of controls and other elements are relative to the Web Form’s upper-left corner. This type of layout is known as relative positioning.

—        An alternate type of layout is known as absolute positioning, in which controls are located exactly where they are dropped on the Web Form.

—        You can enable absolute positioning in Design mode in the HTML Designer > CSS Styling node of the Options dialog.

—        Absolute positioning is discouraged, because pages designed in this manner may not render correctly in different browsers or on computers with different screen resolutions and font sizes.

Running Webpage.aspx Example

Running the Program

—     You can view the Web Form several ways.

—     You can select Debug > Start Without Debugging, which runs the application by opening it in a browser window.

—     To debug your application, you can select Debug > Start Debugging. You cannot debug a web application unless debugging is explicitly enabled by the web.config file.

—     To view a specific ASPX file, you can right click either the Web Forms Designer or the ASPX file name and select View In Browser.

—     Finally, you can run your application by opening a browser window and typing the web page’s URL in the Address field.

Introduction to ODBC

            The ODBC interface provides an interface between applications and an underlying data base in such a way, that the application code does not depend on the underlying data base.

ODBC

            When writing a new application, which relies on heavy database usage, the coder has to select his preferred database - should it be a free one, such as MySQL or PostgreSQL or a commercial solution, such as Oracle or MsSQL. However, if at some point he decides to switch to another database solution, he will have to edit the whole code, in order to make the application Compatible with the new type of database.

   In order to prevent this, ODBC was created.

ODBC history

            ODBC, standing for Open DataBase Connectivity, represents a standard database access method working as SQL API software. It was developed back in 1992 with the sole purpose of facilitating the work with database management systems (DBMS). It was created by the Microsoft corporation and is since then included in every copy of Microsoft Windows. In 1995 the ODBC was included in the SQL Standard, which played a great role in making ODBC more popular. Today, there are versions for almost any operating system currently used.

 

How ODBC works

ODBC was intended to enable developers' access to any data through any application, regardless of the DBMS used for managing that data. ODBC boasts platform independence since it has been purposefully designed in a way that makes it distinct from database systems, programming languages and operating systems. Facilitating the data access from an application to a database management system through ODBC is done through a specific mechanism. A common ODBC implementation contains one or more applications, a core ODBC 'Driver Manager' library, and one or more database drivers. The Driver Manager's role is to interpret the data queries coming from an application by using the DBMS-specific details contained in database drivers. The latter represent a middle layer inserted between an application and the DBMS in use. This way, the application's data queries are translated into commands that can easily be read by the DBMS. A basic requirement for an ODBC implementation to be run is that both the application and the DBMS be ODBC-compliant. In other words, the application must be able to issue ODBC commands and the DBMS must be capable of responding to them.

   Thanks to its modular nature ODBC gives developers a great freedom in creating the separate components of an ODBC implementation. Thus, a programmer can write applications that use standard features without needing to worry about the type of DBMS used for administering the database that the application tries to access.

   Likewise, the only thing the database driver programmers need to keep in mind during the development process is how to attach their database driver to the 'Driver Manager' library. The result is that currently there are hundreds of ODBC drivers created for a large variety of data sources.
Thanks to the long period of existence and the fruitful efforts of its team of developers, ODBC now offers access to a much wider range of data sources than any other database access method available today. It has turned into a universal data access standard, working with a great variety of operating systems and providing access to even non-relational data, including text and XML files.

Data Readers

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

   

Data Set 

          The Data Set object is similar to the ADO Record set object, but more powerful, and with one other important distinction: the Data Set is always disconnected. The Data Set object represents a cache of data, with database-like structures such as tables, columns, relationships, and constraints. However, though a Data Set can and does behave much like a database, it is important to remember that Data Set objects do not interact directly with database, or other source data. This allows the developer to work with a programming model that is always consistent, regardless of where the source data resides. Data coming from a database, an XML file, form code, or user input can all be placed into Data Set objects. Then, as changes are made to the Data Set they can be tracked and verified before updating the source data.

Data Adapter (ODBC/SQL)

           The Data Adapter object works as a bridge between the Data Set and the source data. Using the provider-specific Sql Data Adapter (along with its associated SQLCommand.A and SqlConnection) can increase overall performance when working with a Microsoft SQL server databases.

            The Data Adapter object uses commands to update the data source after changes have been made to the Data Set. Using the Fill method of the Data Adapter Calls the SELECT command; using the Update method calls the INSERT, UPDATE or DELETES command for each change row. You can explicitly set these commands in order to control the statements used at runtime to resolve changes, including the use of stored procedures

5.2 INTRODUCTION TO SQL SERVER 7.0

            In the 1980’s Microsoft and Sybase teamed up to create SQL server. After release of version 6.5 Microsoft and Sybase separated and SQL server made its progress into the competitive market. SQL server 6.5, the Earlier version mainly focused on Database Design implementation. The latest version (7.0) is a significant version.

            SQL Server is an SQL- Complaint RDBMS. SQL-Complaint means it uses the ANSI version of structured query language. Most modern RDBMS products have their own dialect of SQL

For EX: Oracle Has PL/SQL

            SQL Server supports SQL-92 standards. IT uses a version of SQL called Transact SQL.

            Client-Server means that SQL server is designed to store Data in central location (the server) and Deliver it on demand to numerous other locations (the Clients). SQL server is also a Relational Database Management System.

Relational Features of SQL server;

Ø      Information gathering

Ø       Unique of rows.

Ø      Systematic treatment of nulls values.

Ø      Guaranteed access.

Ø     High level Update, Insert, Delete.

Query fundamentals:

            Once the data is entered in SQL Server Database, you need to have a way to retrieve it, to change it, to add or insert new data or to delete existing data. So a query is a request for data stored in a SQL Server tables. Basically it is a special demand from the user for data Retrieval   , Modification, or Deletion. Query is fired by the user and is processed by SQL Server.

Enterprise Manager

            SQL Server Enterprise manager is a graphical tool that allows easy configuration and management of Microsoft SQL-Server objects. Enterprise manager can be found in SQL-Server 7 Program grope.

SQL Server Enterprise Manager can also be used to:

• Manage Logins. Permissions and users
• Create database.
• Take Backups of database and transaction logs.
• Manage tables.

Query Analyzer

Queries are processed in two steps:

INTERPRETS - First the queries are checked the syntax.

EXECUTE - Then the processing takes place.

SQL Server Tables

 SQL Server stores records relating to each other in a table. Different tables are grouped together to form a database.

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 simple 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 tables 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.

Referential Integrity

Not only does SQL Server allow you to link multiple tables, it also maintains consistency between them. Ensuring that the data among relater 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.

5.3 SOURCE CODE

Public Class Form2

    Dim i As Integer

    Dim j As Integer

    Dim k As Integer

      Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button4.Click

        If Button4.Text = "&New" Then

            Button4.Text = "&Save"

            T1.Text = String.Empty

            T2.Text = String.Empty

            DTP1.Text = String.Empty

            ComboBox1.Text = String.Empty

            T3.Text = String.Empty

            T4.Text = String.Empty

            CB4.Text = String.Empty

            T6.Text = String.Empty

            Cb2.Text = String.Empty

            ComboBox3.Text = String.Empty

            mycon.open()

            cmd_Auto.CommandText = "select *from Auto"

            rd = cmd_Auto.ExecuteReader()

            If rd.HasRows = False Then

                mycon.close()

                Exit Sub

            End If

            T1.Text = rd.GetValue(0)

            T2.Focus()

            mycon.close()

        ElseIf Button4.Text = "&Save" Then

            If T1.Text = String.Empty Or T2.Text = String.Empty Or DTP1.Text = String.Empty Or T3.Text = String.Empty Or T4.Text = String.Empty Or CB4.Text = String.Empty Or T6.Text = String.Empty Or Cb2.Text = String.Empty Or ComboBox3.Text = String.Empty Then

                MsgBox("please enter all data...", MsgBoxStyle.Information, "alert")

            End If

mycon.open()

            cmd_Employeemaster.CommandText = "insert into Employeemaster values(" & Val(T1.Text) & ",'" & T2.Text & "','" & DTP1.Value & "','" & T3.Text & "','" & T4.Text & "','" & Trim(CB4.Text) & "','" & T6.Text & "','" & Cb2.Text & "','" & ComboBox1.Text & "','" & ComboBox3.Text & "')"

            cmd_Employeemaster.ExecuteNonQuery()

            cmd_Auto.CommandText = "update Auto set Emp_code=" & Val(T1.Text) & " +1"

            cmd_Auto.ExecuteNonQuery()

            MsgBox("record saved..", MsgBoxStyle.Information, "alert")

            Button4.Text = "&New"

            mycon.close()

        End If

End Sub

Private Sub Form2_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

        i = 1

        For k = 1 To 20

            For j = 1 To 12

              Cb2.Items.Add((Str(k) + "years") + (Str(j) + "months"))

            Next j

        Next k

    End Sub

End Class

6. TESTING

            Testing is an operation of the software real or simulated inputs to demonstrate that the product satisfies its requirements and, if it does not, to identify the specified difference between expected and actual result. There varied levels of software test, ranging from unit or element testing through integration testing, performance testing, up to software system and acceptance tests.

Testing Level

            Software testing is a usually don e at several levels. They are commonly referred to as testing, integration testing and system testing.

Unit Testing

            The objective of the unit testing is to verify that individual units the smallest compliable components, such as java classes function correctly. Unit testing is usually done by programmers.Unit testing is a also called component testing. However component testing is some times considered to be a level of testing above unit testing. This may be the case with a system that contains individually testable component that are composed of multiple units.

Integrated Testing

            The objective of integration testing is to test the integration of and communication between components. Additionally, it may include testing the integration of subsystem or communication with external system. Integration testing may be done by the programmer, but it may also be done by the build caption, or the team lead, the project manager, or even a configuration management group.

On some projects, integration testing may be divided into two levels: Assembly testing and system integration testing. During assembly testing, the integration of the software components is tested.

System Testing

The objective of the system testing is to find defects that are attributable to the behaviors of the system as a whole, rather than the behavior of individual components, and to test that the software  function as complete system. This level of testing is different from integration testing in that the tests are concerned with the entire system, not just integration between components. Other than the system functionality and behavior, system testing includes testing configuration, throughput security, resource, utilization, and performance.

Test design

            Just as the components of a system must be designed, test for a system must be designed. Two common methods of test design are black box and white box testing. After the tests are implemented, though, the design method may not be evident.

       

Black Box Testing

            Black box testing focuses designing test that view components as opaque. The implementation details of the components are not know (or, at least, are ignored), and only externally observable behavior or functionality is tested. Other terms for black box testing are functionality testing and behavior testing.

            However, Behavioral testing and black box testing are slightly different. Even though both view components have black boxes, behavioral testing also knowledge of the implementation details of components to be used in test design necessary.

White Box

            White box testing focuses on designing test that view components as transparent. The implementation details of the components are known, and that knowledge is used in the test design and creation of test data. Other terms for white box testing are structural testing and clear box testing.

                    

 

7. PROJECT LEGACY

7.1 Future Enhancement

            The software that is been designed is mainly aimed at working LAN & Internet connection through send, receiving information and simplifying the maintenances of the information stored in the database . In the manual system employee record were made manually and internet through, where both Employee and the administrator had to keep in touch with the administrator office for employee information all details like login, password, address, phone number, sending information date etc. But this system enables the Complete Mailing System as the Employees all record will help for transactions to communicate with other for companies etc.

              

            Of accessing the external object attributes since the request of the system is from the user and the Project fulfills all the requirements to the satisfaction level it is feasible and is ready to implement and use.

            The project is perfect to the described constraints and needs no further modification but since change may evolve as user requirement change these is a scope for improvement of the software.

7.2 Conclusion

            This software, which had been developed, is aimed to accomplish almost all requirements in this respect. In this fast pace world, people just can’t find enough time to manually deal with a large quantity of information. This software precedes speedy approach to the management of information. Using software , which has been designed, users can easily navigate through various stored profile of companies as well as employees.

            The developed system has to a good extent succeeded in rectifying the problems that are present in the existing system. Reports generated with live data have been proved to be informative. The system can be further enhanced to accommodate a host of features that are currently involved in the system.

         

            The newly developed system consumes less processing time and reduces the repetitive work was carried on earlier, hence increases the productivity and user friendly and any end user can get familiarized with its usage.

8. Bibliography

The following books were referred during the analysis and execution phase of the project

             Microsoft Asp.net .NET Step by Step

       By Michael Halvorson

         

             Microsoft Asp.net .NET Deluxe Learning Edition

             By Michael Halvorson

        

           Beginning VB>NET (2^nd Edition)

             By Richard Blair ET all

         

            SQL SERVER 7.0

            By Levi tin

ORACLE 8 THE COMPLETE REFERENCE

By Oracle Press

SOFTWARE ENGINEERING

By Roger. S. Pressman

SQL FOR PROFESSIONALS

By Jain

MSDN 2003

By Microsoft

 

2. INTRODUCTION

            The project titled “complete mailing system” is a web application. This application is implemented is ASP.Net and SQL server. The design of the project mainly aimed at, to provide a platform for the effective communication between the users to users, and companies etc..

            This “complete mailing system” is a bridging gap between to users to user and companies. In the some of the area some activities are being carried out through manually, since it is advertisement process. To overcome this software, “complete mailing system” provides us to mailing and processing of matching users to users versus companies and also provides some additional beneficial features. This software is developed with the purpose of mailing process. It propose to maintain a complete listing of all users, their personal and academic information, email id taken up by them, the number of email ids taken up by company, their employee, and information about the company, finally the type of “complete mailing system”  taken by company.

            This software may be to maintain a complete data of email ids and mails can be applicable to any company those who are coming to maintain their emails and products. The database is being managed by maintaining the information, month or year wise and email id wise in the following manner by dividing each feature into different fields.

3. SYSTEM ANALYSIS

3.1 INTRODUCTION

            System is an orderly grouping of inter dependent components linked together according to a plan to achieve a specific objectives. System Analysis is concerned with investigating, analyzing, designing, implementing, and evaluating the system.

            The process of developing a computer based information system is a step by step approach. It begins to logical design and gradually moves to physical design.

General Requirements are: -

1.      The new system should be cost effective.

2.      To augment management, improve productivity and services.

3.      To enhance User/System interface.

4.      To improve information quality and usability.

5.      To upgrade system’s reliability, availability, flexibility and growth potential.

3.2 PROBLEM DEFINITION

            The main problems we are considering here is that the records are maintaining currently in the organization manually and sending through person’s and internet through we are making the application such that those records can maintained in computer are systematic send information and receiving information with appropriate information and protected manner.

            The manual maintenance all employee information may damage the records and so on. If this record storing techniques are changed then those records can be accessed easily for administrator like sending information, receiving information and deleting information etc, with saving time, send accurate information of particular employee ID’s such system is this.

            The “complete mailing system” application is automated version of Intranet management of existing system.

3.3 EXISTING SYSTEM

            The study of existing system is important before thinking of proposed system. At present in some company they are working on manually, we encounter some problems, like send information and receiving information etc, and we feel that some mistakes are to be done, like no internet, verification etc.

            The organization is done manual work in Local Building. But nowadays the manual system is more tedious to get the information about transactions & to maintain the records about employee’s ID’s information to various sections in the Mailing System.

            The study of existing system is necessary before proposing the new system. In existing system of organization, the information is transaction manually in register. These records related to the Employee details, Leave details, transactions and also information related to employees ID’s is maintained. In this Request, Order, Sending request and Receiving information, transactions are also maintained.

            Maintaining manual records of employee ID’s and send information is time consuming and difficult. To prepare the Employee information reports, Leave detail reports, employee ID’s reports, Receiving information, send information reports and transactions sending report one need to go through all the record books and list out the corresponding reports, which is a time consuming and effortful process, it may lead to some error.

            To minimize these problems, it is necessary to develop a new system. So, the development of new web based system in “Complete Mailing System” which is user friendly application which overcomes most of the limitations of existing system.

Draw Backs of Existing System

The following are the drawbacks of the existing manual System.

a)     Time Delay: In the existing system, information related to all transactions is stored in different registers. Since all the transactions are stored in different registers it takes lot of time to prepare different reports.

b)     Redundancy: As the information passes through different registers, each register is consolidated and sent to next register. So the same information is being tabulated at each register, which involves lot of complication and duplication in work, thus it causes redundancy.

c)      Accuracy: Since the same data is compiled at different sections, the Possibility of tabulating data wrongly increases. Also if the data is more, Validations become difficult. This may result in loss of accuracy of data.

d)     Information Retrieval: As the information is stored in the particular Format, it can only be retrieved in the same format. But if it is to be retrieve in different format, it is not possible.

e)     Storage Media: In the existing system, data transaction being stored on too long registers it is very difficult to refer after some time.

f)       Reports: At the various reports are tabulated manually.  They are not such Attractive and require more time and delayed reports.

g)     Enquiry: Enquiry for different level of information is much more difficult. On line enquiry of data is not possible

h)    Calculation problem: In transaction all records are calculating suddenly is difficult and some mistakes also taking place.

i)       Maintenance problem: Employee’s ID’s records like leave details and information, are maintaining manually is very difficult.

3.4 PROPOSED SYSTEM

            The Advancing computer technology has more features, which gives a lot of advance facilities. My computer application “Complete Mailing System” is used to maintain the information of different Employee’s ID’s transactions in the Mailing System. As the Employee details maintains particular employee ID’s information and all these activities are carried out by using computer technology.

            Thus the use of “Complete Mailing System” makes easy to send information, receiving information and maintain details of all employees ID’s what the information sending, when sending information and receiving the information, what the information removing etc, all details accessing in this application.

Features of Proposed System

• Doesn't use any paper (good for the environment).
• User friendly messages are given when necessary.
• Working Particular LAN (Local area network) connection and internet connection also.
• No limit on how short or how long the message should be (it would seem ridiculous to send a one line letter to someone in the post, but on email this is acceptable).
• Can attach large documents and other files with a click of a button (and without using up resources like paper).
• What the information sending, when sending, remove the information and receiving all information available in this application.

Advantages of Proposed System

• Less time consuming.
• Quick delivery and reply of messages.
• Work LAN connection and Internet connection also.
• Convenient.
• Reduced register work.
• Manpower reduced.
• Record maintenances easy.
• Provides security mechanism.
• Less prone to errors.
• Computerized reports.

Disadvantages of Proposed System

• Being graphics based, a GUI (Graphic User Interface) runs slowly than a text based system. However, with the power and speed of modern computers this is not the problem it once was.
• Less hand-writing practice.
• Can be bad for your eyes if you spend too long sending e-mails on your computer.
• User has to open email website or email program to read the message. If you do not login and read the message can remain unread for ever. 
• Email attachments can bring virus into your computer if not scanned by network or virus program on your computer. 
• Can provide an easy way to spread viruses to computers.
• The foremost short coming of .NET platform is that it is still the propriety of Microsoft. It is more coupled with the Microsoft Windows operating system and is implemented only on Microsoft Windows successfully.
• The managed .Net applications are somewhat slower to start and run than the traditional Win32 applications.

3.5 MODULES

Ø      User registration

Ø      Inbox

Ø      Sent

Ø      Search

Ø      Securities

Ø      Trash

User registration

               In this module all employee details are maintained that are personal files, particular employee and leave details allot  for  employees. 

Inbox

            In this module receiving the data like Message, .doc files, pdf files, images etc.  

Sent

            In this module after sending data like Message, .doc files, pdf files, images that data stored in this Sent module.

Search

            In this module search the spelling and important words.

Securities

            In this module lot of securities like password login ID, if you don’t account not opening login etc.

Trash

            In this module we can delete your data like receiving data and sending data etc.

 

3.6 FEASIBILITY ANALYSIS

            The main objective of the feasibility study is to test operational, Technical and economic feasibility of the proposed system. This is done by investing existing system. This stage where everyone will test the feasibility stage contains following factors to access.

Technical Feasibility

          Technical feasibility is one of the important assessments in the system analysis phase.

• Today various types of software & hardware are available consequently, technical feasibility is not a constraint for system development.
• At present the capacity of secondary memory is 80GB, hence memory is not a constraint.
• Accuracy, easy of access, security & reliability ensured.

            From the above technical feasibility is fit for the “Complete Mailing System” system.

Economic Feasibility

            Economic feasibility attempts two ways, the costs developing and implementing a new system, against the benefit that would accrue from having the new system in place. This feasibility study gives the top management economic justification for the new system. This feasibility study gives the economic ability to the Complete Mailing System to be technically fit.

            A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful reference to compare actual costs as the project progresses.

            There could be several of information benefits on account of automation. These could include increased customer satisfaction, improvement in speed work, expending activities, improved accuracy of operations, better documentation and receiving information, sending file record keeping, and faster retrieval information.

Operational Feasibility

            It centralizes the extent of the proposed system will fulfill the Complete Mailing System requirements. So this is one of the important factor of the feasibility study. The software which I have developing is much easier to operate. And it covers all aspects of the working system and it has considerable improvement than the earlier manual system. To operate this system no much computer knowledge is required and just trained to need to appoint new candidate. The system is so simple & user-friendly that the users can use it easily.   

• Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.

·        Are the current business methods acceptable to the user?  If they are not, Users may welcome a change that will bring about a more operational and useful systems.

·        Have the user been involved in the planning and development of the project? Early involvement reduces the chances of resistance to the system and in General and increases the likelihood of successful project.

4. SYSTEM DESIGN

4.1 INTRODUCTION

            Design is the first step in the development phase of any engineered products or system. It is the technical kernel of software engineering. It is the 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.

           Design is creative process that can be guided and directed, but it can never be reduced to an algorithmic process. The design of a real system is a much different activity then the design of a data processing application.

The following are some guidelines for organizing activities of a software design.

·        Review the requirement specifications.

·        Review and expand the external interfaces.

·        Review and refine data flow diagrams developed during requirement analysis.

·        Identify functional abstraction and data abstractions.

·        Define a visible interface for each and every functional abstraction and data abstraction.

·        Define the modularization criteria to be used.

·        Verify that the resulting system structure satisfies the requirements.

·        Develop interface specifications for the procedures in each module.

·        Conduct the critical design review.

·        Redesign if necessary.

Detailed design was carried out in the following phases:

• Entity Relationship Diagram (ER-Diagram)
• Data Flow Diagram (DFD)

4.2 ENTITY RELATIONSHIP DIAGRAM

            Entity Relationship Diagrams are major data modeling tool and will help organize the data in the project into entities and define the relationships between the entities.

Entity: A data entity is anything real or abstract about which we want to

store data.

Relationship: A data relationship is a natural association that exists between one or more entities. Cardinality defines the number of occurrences of one entity for a single occurrence of the related entity.

Attribute: A data attribute is a characteristic common to all or most instances of a particular entity. An attribute or combination of attributes that uniquely identifies one and only instance of an entity is called a primary key.

Degree of Relationship: Is the number of entities associated with the relationship.

Connectivity and Cardinality: The connectivity of relationship describes the mapping of associated entity instances in the relationship. The different types of cardinality ratios are:

• One to one (1:1)
• One to many(1:N)
• many to one(N:1)
• many to many(M:N)