A Mini Project Testimony On

MESSAGE BASED SYSTEM IMPLEMENTATION

BY Aditya Kandukuri (05361A0501) Madhav Reddy (05361A0578) David Tejaswi (05361A0512) Giridhar Kumar (05361A0516)

Dept. of Compuer Science Engineering,

Jaya Prakash Narayan College of Engineering,
Dharmapur, Mahabubnagar.

CERTIFICATE

This is to endorse that Aditya Kandukuri bearing Roll No: 05361A0501 of III/IV Bachelor of Technology in Computer Science Engineering have been successfully completed the mini project on “Message Based System” during the period 15th May 08 to June 08.

Internal Guide.

Head of the Dept.

External Examiner.

Acknowledgement
It is a pleasure for us to add a few heartfelt words for the people who were Part of

this project in numerous ways, people who gave unending support right from the stage the idea was conceived.

We would like to thank our PARENTS, Dr S.Subhash Kulkarni, and principal, who helped us in getting an opportunity to do a project.

We will always be thankful to Prof. P.V.S.Srinivas, Head of the Computer Science Department, for his kind consideration and encouragement in carrying out this project successfully.

We also thankful to Haritha Asst. Prof. who helped us in getting an opportunity to do a project in Message Based System and also those who have helped us in gathering information about the project.

ABSTRACT

ABSTRACT
This project deals with the Mailing System. This project is having different modules like new User creation form named it as a Sign Up form and already existing user can logged into the Mailing System named it as a Sign In form. As organizations are divided into departments.

Quick passing of mails is not possible in load manual systems. Because in manual systems the mails are passed through persons from one department to another. But it takes much time and risk also. This leads the inconsistency of information. So we need a system that is both quick and accurate. This can be achieved by mailing system.

Intranet mailing system sends the mails spontaneously without requiring the parties be available at the same instant. Furthermore mails can be sending more people at the same time. It also leaves a written copy of the sending mails that can fill away. This is much cheaper than the manual system. Although electronic mail can be viewed as just a special case of the file transfer.

The ultimate senders and receivers are always people, not Machines. This fact has resulted in electronic mail systems being constructed as two distinct, but closer related parts: One providing for the human interface composition, editing and reading mail and one for transforming mail i.e means managing mailing lists and providing notification delivery.

Contents
Page No 1. Introduction • Project Profile • Organization profile 2. Project Analysis • Present system • Proposed System • Software Requirement Specification • Feasibility Study 3. Design and Implementation • Project Modules • Data Dictionary • E-R Diagrams • UML Diagrams • Hardware and Software Specifications 4. Life Cycle Model 5. System Environment 6. System Testing 7. Screens 8. Coding 9. Conclusion • Future Scope • Bibliography 02 03 04 05 05 06 07 10 11 13 18 22 25 35 36 39 52 57 71 84 84 85

INTRODUCTION
Project Specification about Intranet:
This project deals with the Mailing System. This project is having different modules like new User creation form named it as a Sign Up form and already existing user can logged into the Mailing System named it as a Sign In form.

PRESENT SYSTEM:
Present System is manually providing services to employees of departments of an Organization. Employees have to go departments to know some particular information. Sometimes information is passed by manually between departments. This manual system will take time to pass the information and sometimes it causes loss of information also. There by causing loss of employee time also. Thus the present system stated is Time taking, Security less, Cost Consuming.

NEED FOR NEW SYSTEM:
Now-a-days the organizations are growing fast and are increasing in size also. So these organizations are divided into departments. In the fast growing world the information is need as fast as possible. This can be accomplished by passing the information quickly. Quick passing of mails is not possible in load manual systems. Because in manual systems the mails are passed through persons from one department to another. But it takes mush time and risk also. This can be achieved by mailing system. Intranet mailing system sends the mails spontaneously with out requiring the parties be available at the same instant. Furthermore mails can be sending more people at the same time. It also leaves a written copy

of the sending mails that can file away. This is much cheaper than the manual system. Although electronic mail can be viewed as just a special case of the file transfer. The ultimate senders and receivers are always people, not Machines.

Organization Profile:
AXEND LABS was found in 1994, AXEND LABS is organized as three strategic Business units catering to Software Development, Software Services and Data managements and training areas. The company is steered by a highly motivated team of technologists with solid software development experience. The company is steered by a high performing and young Board of Directors all of who have an average software industry experience of 8 years. The management is result oriented, which is achieved by consensus. Key issues are brainstormed and an optimal solution ensured. All the business functions, the strategic business units and related

responsibilities are shared among the Directors thus ensuring smooth and efficient business process. AXEND LABS is leading provider of client/server solutions for small to medium corporations. For existing client/server installations Inforise offer solutions that are web-centric in tune with the changing needs of corporation. So to say, at this very moment you need your existing client server solution to support web integration. Inforise start with understanding your information needs to provide you a combination of tailor-made off-site and on-site solutions instantly leveraging the advantages of the Internet. Inforise client server and web bridging solutions help you to get incrementally migrate to the new network centric computing paradigm. AXEND LABS implemented mini client server applications for a variety of business processors and developed software libraries for finance, inventory, sales orders, purchases, manufacturing, human resources, and production process in an enterprise.

PROJECT ANALYSIS
PRESENT SYSTEM:
Presenting Intranet Mailing System is manually providing services to employees of departments of an Organization. Employees have to go departments to know some particular information. Sometimes information is passed by manually between departments .This manual system will take time to pass the information and sometimes it causes lost of information also. This causes lost of employee time also.

NEED FOR NEW SYSTEM:
Now-a-days the organizations are growing rapidly and are increasing in size also. So there organizations are divided into departments. In the fast growing world the information is need as fast as possible. This can be accomplished by passing the information quickly. Quick passing of mails is not possible in load manual systems. Because in manual systems the mails are passed through persons from one department to another. But it takes mush time and risk also .This leads the inconsistency of information. So we need a system which is both quick and accurate. This can be achieved by mailing system.

Electronic mailing system sends the mails spontaneously with out requiring the parties be available at the same instant. Furthermore mails can be sent to more people at the same time. It also leaves a written copy of the sending mails that can file away. It much cheaper than the manual system. Although electronic mail can be viewed as just a special case of the file transfer. The ultimate senders and receivers are always people, not Machines. This

fact has resulted in electronic mail systems being constructed as two distinct, but closer related parts: One providing for the human interface composition, editing and reading mail and one for transforming mail i.e. means managing mailing lists and providing notification delivery.

PROPOSED SYSTEM:
The proposed system contains all the features of the mailing system as with the Internet. Such as Inbox, Compose, Address Book, Password Change, New user Registration. The proposed system can be used all around the organization by interconnecting all the terminals in LAN. Here all these features will be visible only for the registered users (or) employees of the organization.

ADVANTAGES WITH THE PROPOSED SYSTEM:
The user of Intranet Mailing System is given a unique login id and must give the correct password. It gives total security for us. So unauthorized user can't allow to see our messages. Even if the user forgets his/her password reminding facility by which the user can recollect the password and log into the system.

The main advantage of the Intra mail system is its security feature allowing only registered users to access the system and preventing any hackers, unauthorized users.

As the access for the MBSI is only restricted to the people registered within the organization itself and information is transferred with in the organization itself, and all this transformation will be up to some limit so the data transformation will be fast.

SOFTWARE REQUIREMENT SPECIFICATION:
Software Requirements Specification plays an important role in creating quality software solutions. Specification is basically a representation process. Requirements are represented in a manner that ultimately leads to successful software implementation.

Requirements may be specified in a variety of ways. However there are some guidelines worth following: • • • Representation format and content should be relevant to the problem Information contained within the specification should be nested Diagrams and other notational forms should be restricted in number and consistent in use. • Representations should be revisable.

REQUIREMENT PHASE
The requirement phase basically consists of three activities: • • • Requirement Analysis Requirement Specification Requirement Validation

REQUIREMENT ANALYSIS:
Requirement Analysis is a software engineering task that bridges the gap between system level software allocation and software design. It provides the system engineer to specify software function and performance indicate software’s interface with the other system elements and establish constraints that software must meet. The basic aim of this stage is to obtain a clear picture of the needs and requirements of the end-user and also the organization. Analysis involves interaction between the clients and the analysis. Usually analysts research a problem from any questions asked and reading existing documents. The analysts have to uncover the real needs of the user even if they don’t

know them clearly. During analysis it is essential that a complete and consistent set of specifications emerge for the system. Here it is essential to resolve the contradictions that could emerge from information got from various parties. This is essential to ensure that the final specifications are consistent. It may be divided into 5 areas of effort. • • • • • Problem recognition Evaluation and synthesis Modeling Specification Review Each Requirement analysis method has a unique point of view. However all analysis methods are related by a set of operational principles. They are • The information domain of the problem must be represented and understood. • The functions that the software is to perform must be defined. • The behavior of the software as a consequence of external events must be defined. • The models that depict information function and behavior must be partitioned in a hierarchical or layered fashion. • The analysis process must move from essential information to implementation detail.

REQUIREMENTS SPECIFICATION:
Software Requirements Specification plays an important role in creating quality software solutions. Requirements are represented in a manner that ultimately leads to successful software implementation. Requirements may be specified in a variety of ways. guidelines worth following: • • • Representation format and content should be relevant to the problem Information contained within the specification should be nested Diagrams and other notational forms should be restricted in number and However there are some

consistent in use.

Representations should be revisable.

FEASIBILITY STUDY:
Software Requirements Specification plays an important role in creating quality software solutions. Specification is basically a representation process. Requirements are represented in a manner that ultimately leads to successful software implementation. Requirements may be specified in a variety of ways. However there are some guidelines worth following: • • • Representation format and content should be relevant to the problem Information contained within the specification should be nested Diagrams and other notational forms should be restricted in number and consistent in use.

PROJECT FEASIBILITY:
In preliminary Investigation we got the result that the electronic mailing system is feasible. This includes three aspects: TECHNICAL FEASIBILITY: Technical Feasibility is nothing but implementing the project with existing technology. Electronic mailing system is technically feasible. ECONOMICALLY FEASIBLE: Economic Feasibility means the cost of understanding project should less cost than the existing system. Electronic mailing system is economically feasible, because it reduces the expenses in the system. OPERATIONAL FEASIBILITY: Operational Feasibility means the project should be supported by users. It should not cause any problems to users after implementing. Electronic mail was fully supported by users. So, Electronic mailing System is operationally feasible.

DESIGN AND IMPLEMENTATION
System design is the process of planning a new system to complement or altogether replace old systems. System design can be defined to have three different activities in it. They are • • • External Design Architectural design Detailed Design

Architectural design and detailed design collectively called as internal design.

EXTERNAL DESIGN:
External design of a software involves conceiving, planning and specify the external observably characteristics of the software products. External design includes user report format, external data sources and data links. This design begins during analyze phase and continuous to the design phase. The external design gives the actual data flow from one system to other system. It also shows the relation of the current system to outside the world. It shows what the inputs, outputs are. Here the external design is conveyed to the user by using the browser. The external design also includes user responses, report format, data source and data links. Errors are easily traced out during the external design. Once external design in completed a more detailed explanation of the parts identified, as part of external design will lead to easy understanding of the internal working of the system. Avoiding errors in the external design will not lead to the hard failures during the time interval design.

INTERNAL DESIGN:
Internal design activities are actually constituted in two different activities. • • Architectural Design Detailed Design

Internal design involves planning, specifying the internal structure and processing details of the software product. Architectural design is concerned with the refining conceptual view of the system, identifying internal processing, functions, decomposing, high level functions into sub overall performance of the software products. Use of objects in the "Electronic Mail Service" leaves you with a more comfortable programming technique. Designing of an object for each identified entity results in reducing, repetitive coding and increases efficiency.

PROJECT MODULES
The Intranet Mailing System is applicable to this fast growing world where every qualified person is in urgent need of job, they join places, working at odd times The organization have shift systems and it becomes difficult for an employee of one shift to communicate with another employee on a different shift. In these circumstances the Intranet Mailing System proves its worth, if the organization has an Intranet Mailing facility available to all its employees then each employee can register himself and send mails to any other registered employee and thus making the communication easier No necessity of paying money for the mailing facility(i.e. free of cost). The mails that the employees send reach the destination with less time than internet. Although the intranet Mailing System works in a similar fashion as that of an Intranet Mailing System, there is no need to get an Internet connection for our mailing system. The various branches of the organization can be connected to a single host server and then an employee of within organization can only use this facility. In one branch can send a message to anemployee of another branch through the server.

INTRANET MAILING SYSTEM DESCRIPTION
This project deals with the Mailing System. This project is having different modules like new User creation form named it as a Sign-Up form and already existing user can logged into the Mailing System named it as a Sign In form. This was submitted with two modules given below Sign up Option. Sign in Option.

Sign Up Option: This module deals with the sign up process. This module is having the facilities for creating new account in this Intranet Mailing System. This feature is provided by clicking signup option and it displays fill up form. In sign up form the new user can fill all the details of the new user. This form will takes all the details about the user. This will loads the information like Username, User Password. Confirm Password, the Age of the user, Sex, in which city user is living, the state belongs to the user, City, Pin code, Nation. This form contains some optional fields and some are compulsory fields. After entering the details in to the form the user can select the option provided on the sign up form. The option is Register. When the user clicks on the 'Register' button, Mailing System checks whether the user name exists or not. If the user name is already present in the database system the corresponding dialog box will be given to the user and this process will be repeated until the user is entered new username which does not exist on the database. If not it will checks further fields. If any one or more than one compulsory field is empty it gives the message to the user that the corresponding field is empty. If he enters values in all compulsory fields then the mailing system checks whether the user is entered the same values in the fields User Password and Confirm Password. If he entered same values the form will be submitted otherwise the system will gives the corresponding alert message to the user. Sign ln Option: If the user is already contains an account in this system, this form permit to enter in to this mailing system. Now he can use all the facilities provided by this Mailing System. A valid accountant can access these facilities by entering the two options provided by the logging screen, if not he can create the new* user account by using the facility of the Sign In form. By entering the Username and Password of the user presses the Sign in button. If the username & password are correct then system gives the permission to logon in to the Mailing system. This checking at the database side is compulsory for the purpose of authentication. Only a valid user can access the facilities provided by this present Intranet Mailing System. In this fashion this form is providing some sort of security.

If the Username & Password are valid, now the user is successful enough to logging on to the system, two frames are displayed. Left-hand side frame displays the user menu and the right hand side menu displays the information about how many mails he received. By clicking this, the user Inbox will be displayed. User Menu: Provides a way to give any commands to the mail server. The options include in the menu are Compose Sent Messages Options Inbox Addresses Logout

Compose Screen: This screen is obtained when the user selects the compose option from the mail folder. The fields in this screen are: To: Here the primary receiver's address is to be entered Subject: Here the primary receiver's address is to be entered. CC: Here the address of the receiver is typed where the same copy of the mail has to be sending. BCC: Here the address of the receiver is typed where the same copy of the mail has to be sending and receiver can receive only one copy separately It won't show all the different addresses Mail text to be sent: This is the text area where the actual mail data has to be sent. Send: This is a button, used to send the mail Inbox: If the user selects this option on the user menu the corresponding inbox of the user will be displayed. To read the different mails one option is provided as a subject By clicking on the subject place the corresponding mail will be displayed. Sent Messages: Using these options user can select different messages which are all ready sent earlier. This is for the purpose to know which message is sent to whom. Addresses: By clicking this option one more screen will be displayed on the right hand side of the frame that screen is Address screen This screen can be used to create to add new addresses to the database system. Here various listings of addresses with the name and there nick name. Here we have various options. Delete: Can be selected to delete the current address.

Add: It will generate a new form to add a new address to the list with name of the address holder and the nickname. After clicking this Add option provided on the Address Screen one more form will be displayed having following options Name: Here name of the address holder is to be entered. Nick Name: Here nick name of the address holder is to be entered. Mail Id: Here Mail id of the address holder is to be entered. Address: Here the actual address that is to be stored is entered. Add: When clicked add button this address adds to the current screen. Options: By selecting options menu one more screen will be displayed, the screen in Change Password Screen. It contains following providers' Old Password Here the old password has to be typed; it is useful to check whether the user is an authenticated user to change the password. Change Password: Here the new password that is to be replaced with the old password is entered. Confirm: Here the user has to enter the same password that is entered in the new field to confirm the change of password. Change: This button is to be clicked to actually change the old password to the new password. Logout: By clicking this option the login session of the user will expire. If you want to reenter in to the site one more option is to be provided, if u want sign out completely one more option is provided to sign out completely that is to logout the use completely from the site

Advantages:
The user of Intranet Mailing System is given a unique login id and must give the correct password. It gives total security for us. So, unauthorized users can be prevented to see our messages. Even if the user forgets his/her password reminding facility by which the user can recollect the password and log into the system. The advantage of the Intra mail system is its security feature allowing only registered users to access the system and preventing any hackers, unauthorized users.

DATA DICTIONARY:
TABLE NAME: NEW_USERS_DETAILS Description: This table contains the details of the new users. CONSTRAINTS: All fields are NOT NULL. DATATYPE&SIZE VARCHAR(20) VARCHAR(IO) VARCHAR(IO) NUMBER(3) VARCHAR(I) VARCHAR(20) NUMBER(6) VARCHAR(20) DESCRIPTION Username User Password Pwd for confirmation User Age User Sex User City User Pin code User Nation

FIELDNAME USERNAME USERPWD CON_PWD USER_AGE USER_SEX USER_CITY USER__PIN USER_NATION

TABLENAME: INBOX_DETAILS

Description: This table stores the information of all the new mails that are received by the different users. This table containing the fields like from which the mail is coming from, whom he is sending mail, when he is sending the mail and what is the message

FIELDNAME SOURCE DESTINATION SUBJECT DATE MESSAGE

DATATYPE&SIZE VARCHAR(20) VARCHAR(20) VARCHAR(10) DATE VARCHAR(1500)

DESCRIPTION Whom is sending the mail To whom data is sending what is the subject On which date the mail is sending Message

TABLENAME:

USER_ADDRESS_DETAILS

Description: This table stores the addresses of the user friends

FIELDNAME USER_NAME FR_NAME FR_N_NAME FR_MAILID FR_ADDRESS

DATATYPE & SIZE VARCHAR(20) VARCHAR(20) VARCHAR(IO) VARCHAR(25) VARCHAR(IOO)

DESCRIPTION User Name Friend Name Friend Nick Name Friend E-mail ID Friend Address

TABLENAME: SENT_MESSAGE

Description: This table stores the information of all the new mails that are send by the users. This table containing the fields like from which the mail is coming from, whom he is sending mail, when he is sending the mail and what is the message.

FIELDNAME SOURCE DESTINATION SUBJECT DATE MESSAGE

DATATYPE & SIZE VARCHAR(20) VARCHAR(20) VARCHAR(10) DATE VARCHAR(1500)

DESCRIPTION Whom is sending the mail To whom data is sending what is the subject On which date the mail is sending Message

E-R DIAGRAMS:

USER INBOX DETAILS:

USER_AGE USER_CITY CON_PWD

USER_SEX USER_PINCOD

USER_AGE

USER_PWD NEW_USER_DETAILS

USER_NAME

INBOX_DETAILS

DESTINATION SUBJECT DATES

MESSAGE

USER ADDRESS DETAILS:

USER_AGE USER_CITY CON_PWD

USER_SEX USER_PINCOD

USER_AGE

USER_PWD NEW_USER_DETAILS

USER_NAME

USER_ADDRESS_DETAILS

FR_NAME FR_N_NAME FR_MAILID

FR_ADDRESS

SENT MESSAGE DETAILS:

SUBJECT

DATES

DESTINATION

MESSAGE

INBOX_DETAILS

SOURCE

SENT_MESSAGE

DESTINATION

MESSAGE

SUBJECT

DATES

UML DIAGRAMS
Introduction
In this chapter author is going to study the Unified Modeling Language (UML) and its attributes. The Author has studied various modeling techniques and has chosen UML is the appropriate modeling technique for the proposed project. The objective of this present chapter is mainly concerned about the design of the proposed system.

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

Goals of UML
The primary goals in the design of the UML were: Provide users with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models. Provide extensibility and specialization mechanisms to extend the core concepts. Be independent of particular programming languages and development processes. Provide a formal basis for understanding the modeling language. Encourage the growth of the OO tools market. Support higher-level development concepts such as collaborations, frameworks, patterns and components.

Integrate best practices.

UML Diagrams
Each UML diagram is designed to let developers and customers view a software system from a different perspective and in varying degrees of abstraction. UML diagrams commonly created in visual modeling tools include

Use Case Diagram The first UML model diagram that was used to carry out the requirements modeling is the USE CASE diagram5. The diagram was very simple and easy in identifying all the processes that was presented in the initial stages of the system.

A use case6 is a description of a system’s behavior from a user’s standpoint. For system developers, this is a valuable tool. Use case can also refer to a collection of related success and failure scenarios that describe actors using a system to support a goal the scenarios refer to the specific actions and interaction between actors and system. The two main components of a use case diagram are use cases and actors.

An actor represents a user or another system that will interact with the system you are modeling. A use case is an external view of the system that represents some action the user might perform in order to complete a task. Use cases are used in almost every project.

USE CASE DIAGRAM OF MBSI:

Inbox

compose

Employee

Password change

Employee

Address book

NEW USER REGISTRATION USE CASE DIAGRAM:

new user registration

administrator

administrator

registration failed

SEQUENCE DIAGRAM:

: Employee

login verify

Inbox

compose

change password

address book

enter login details success

show_messages verify success

send_mail verify sent_message_to_validuser change_password verify

password_updat ed

add_new_address verify

s uccessfully_added_newaddress

SEQUENCE DIAGRAM FOR ADMINISTRATOR:

administrator

login

new user registration

administrator

enter log details success verify

enter new user details verify authorized user

assign usid and pwd valid user

COLLABORATION DIAGRAM:
2 : ve rify 5 : ve rify

1 : e n te r lo g in d e t a ils lo g in 3: s uc c es s : E m p lo y e e

4: s how _m es s ages In b o x 6: s uc c es s

1 2 : p a s sw ord _ u p d ate d 1 3 : a d d _ n e w _ a d d re s s 9 : s e n t _ m e s s a g e _ t o _ va lid u s e r 7 : s e n d _m a il 8 : ve rify 1 5 : s u c c e s s fu lly _ a d d e d _ n e w a d d re s s 1 0 : c h a n g e _ p a s s w o rd 1 1 : ve r if y 1 4 : ve r if y

c om pos e

c hange p a s s w o rd

a d d re s s book

COLLABORATION DIAGRAM FOR ADMINISTRATOR:
2 : v e r i fy

1 : e n t e r lo g d e t a ils lo g in 3: success : ad m in is t ra t o r

6 : a u t h o riz e d u s e r 5 : ve r i fy 4 : e n t e r n e w u s e r d e t a ils

7 : a s s ig n u s id a n d p w d new user r e g i s tr a ti o n 8 : va l i d u s e r a d m ini s t ra t o r

CLASS DIAGRAM:

new login registration new_name : String address : String age : integer Gender : String State : Stirng

inbox sourc e_address : St ring destinat ion_add : St ring Subjec t : St ring received_date : dat e mess age : St ring

compose mail destination_add : String subject : String Bcc_add : String CC_address : String login username : String Password : String

password_change old_pwd : string new_pwd : String confirm_pwd : String

mes s_dis play delete message name : String nick_name : String address : String Email : String sender_add : String message : String subject : String delete_mess : String

address name : String Nick_name : String address : String Email : String

HARDWARE AND SOFTWARE SPECIFICATION:

Working Environment:
Operating platform RDMS Software Browser : : : : windows 98/2000nt/Xp SQL server 2000 Visual Studio .Net 2005 Internet Explorer

Hardware requirement specification:
PROCESSOR SPEED HARD DISK RAM : : : : Pentium 233 MHz 4.2 MB 512 MB

SYSTEM DEVELOPMENT LIFE CYLCE MODEL
System Development is a process consisting of two major steps, System Analysis and Design. It stars when management or some times system development personnel realize that a particular business system needs improvement. System development life cycle method is classically though of as a set of activities that analysis, designers and users carry out to develop and implement an information system. The system Development Life Cycle method is divided into six activities. • • • • • • Preliminary Investigation. Determination of System Requirements. Design of Systems. Developments of Software. System testing. Implementation and Evaluation.

The project Electronic Mail Service has been developed adhering to the above and activities. The total project has been completed by dividing in to the various phases of system development life cycle. A brief description of each phase in the project it as follows

PRELIMINARY INVESTIGATION:
In this phase of the System Development Life Cycle a need was felt for assisting the development Mail service for a company that a single account to be shared by a number of people of that company. This activity was divided into three activities. • • • Request clarification Feasibility Study Request proposal

REQUEST CLARIFICATION:
In Electronic mail service the request were received from a company for sharing a single account. Then the feasibility study on the project was studied. The various feasibility studies performed i.e., Technical feasibility whether existing equipment software was sufficient for completing the project. Economic feasibility determines whether the doing of project is economically beneficial. This seems to be beneficial because the company need not spend any amount on the project trainees because they work at a less amount and only machine time is burden. The outcome of first phase was that the request and the various studies were approved and it was decide for the project if taken up would server the end user. On developing and implementing this software saves a lot of amount and sharing of valuable server space.

SYSTEM REQUIREMENTS:
This is second phase in System Development life cycle. In this phase all the details of the area under investigations are considered. It is termed as Detailed Investigation. Some of the major questions that are normally answered in this phase are as follows: • • • • • What is being done? How it is being done? How frequently does it occur? How great is the volume of transactions of decisions? Does a problem exist?

In this project the user’s requirements and the constraints were studied thoroughly. Some of the constraints which are very important are up to date maintenance I .e.

keeping mails are individual from other securely, information of each person, password were kept securely.

DESIGN OF SYSTEM:
This is third phase of system Development life cycle. The design of this “electronic mail service” produces how the next step of the system being implemented. This phase is also called as logical design. In Electronic Mail Service the design processes was started by identifying the various ways of keeping security, sharing of resources, and using process time so as to reduce on processor from some housekeeping tasks i.e. for each time downloading of page was reduced, in this phase clear examination of validations to be made, data to be send to our electronic mail server, and which data to processed, command to executed, which data to be stored, which data to be send to other mail servers was clearly identified, in this phase individual data items and various functions to be performed by that object of the class the design specifications swear portrayed in the form of flow charts, tables and other methods. This was then carried to development stage.

DEVELOPMENT OF SOFTWARE:
This is fourth phase of system development lifecycle. During this phase software developers may install (or modify and then install) purchased software or may write new custom designated programs. The choice depends on the cost of each of option, the time available to write software the personnel required developing software, the resources available for developing etc. In Electronic Mail Service consisting all the facts like personnel, tools available, complexity involved and also cost considered, it was decided to develop software in house by using Java for starring mails was done in normal files. Communication between client and server was done through TCP/IP which is reliable for communication. New classes were written for each and documentation was made for further enhancements.

SYSTEM ENVIRONMENT
MICROSOFT .NET FRAMEWORK The .Net frame work is a new computing platform that simplifies application development in the highly distributed environment of the internet. The .NET frame work is designed to fulfill the following objectives: • To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but internet distributed, or executed remotely. • To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted party. • To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments. • To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications. • To build all communications 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. 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, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as managed code. The class library, the other main component of the.NET Framework, is a comprehensive, object-oriented collection of reusable types that you can use to develop

application ranging from traditional command line or graphical user interface (GUI) applications to applications to latest innovations provide by Windows applications. The .net Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can be exploit both managed and unmanaged features. For example, ASP .NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP .NET works directly with the runtime enable Web forms applications and XML Web services, both of which are discussed later in this topic. Internet explorer is an example of an unmanaged application that hosts the runtime. Using Internet Explorer to host the runtime enables you to embed managed components or windows forms controls in HTML documents. Hosting the runtime in this way makes managed mobile code possible, but with significant improvement that only managed code can offer, such as semi-trusted execution and secure isolated file storage. The following illustration shows the relationship of the common language runtime and the class library to your application and to the overall system. The illustration also shows how managed code operates within a larger architecture. FEATURES OF THE COMMON LANGUAGE RUNTIME: The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common runtime. Language compilers that target the .NET Framework makes the features of the .NET Framework available to existing code written in that language, greatly easing the migration process for existing application. While the runtime is designed for the software of the future, it also supports of today and yesterday. Interoperability between managed and unmanaged code enables developers to use necessary COM components and DLLs. The runtime is designed to enhance the performance. Although the common language runtime provides many standards runtime service, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Meanwhile, the memory manager removes the possibilities of fragmented memory and increases memory locality-of-reference to further increase performance.

Finally the run time can be hosted by high performance, server’s side applications such as Microsoft SQL Server and internet information services (IIS). This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry’s best enterprise servers that supports runtime hosting. .NET FRAMEWORK CLASS LIBRARY: The .NET Framework class library is a collection of usable types that integrate with the common language runtime the class library is object oriented providing types from which your managed codes can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework. For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework. In addition to these common tasks, the class library type that supports a variety of specialized development scenarios. For example, you can use the .NET Framework to develop the following types if applications and services. • • • • • • Console applications scripted or hosted applications windows GUI applications(Windows forms) ASP .NET applications XML Web services Windows services. For example, the windows forms classes are a comprehensive set of reusable types that vastly simplify Windows GUI development. If you write an ASP .NET web form application, you can use the web forms classes.

CLIENT APPLICATION DEVELOPMENT: Client applications are the closest to a traditional style of application in windows based programming. These are the types of applications that display windows or forms on the

desktop, enabling a user to perform a task. Client applications include applications such as word processors and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they likely access local resources such as the file system and peripherals such as printers. Another kind of client applications is the traditional ActiveX control (now replaced by the managed Windows Forms control) deployed over the internet as a web page. This application is much like other client applications: it is executed natively, has access to local resources, and includes graphical elements.

ACTIVEX DATA OBJECTS
ADO .NET OVERVIEW ADO .NET is an evolution of the ADO data access model that directly addresses user requirements for developing scalable applications. It was designed specifically for the web with scalability, statelessness, and XML in mind. ADO .NET uses some ADO objects, such as the Connection and Command objects, and also introduces new objects. Key new ADO .NET objects include the Data Set, Data Reader, and Data Adapter. The important distinction between this evolved stage of ADO .NET and previous data architectures is that there exists an object--the Dataset--that is separated and distinct from any data stores. Because of that, the Dataset functions as a standalone entity. You can think of the Dataset as an always disconnected record set that knows nothing about the source or destination of the data it contains. Inside a Dataset, much like in a database, there are tables, columns, relationships, constraints, views, and so forth. A Data Adapter is the object that connects to the database to fill the Dataset. Then, it connects back to the database to update the data there, based in operations performed while the Dataset held the data. In the past, data processing has been primarily connection based. Now, in an effort to make multi tired apps more efficient, data processing is truing to a message based

approach that revolves around chunks of information. At the center of this approach is the Data Adapter, which provides a bridge to retrieve and save data between a Dataset and its source data store. It accomplishes this by means of requests to the appropriate SQL commands made against the data store. The XML based Dataset objects provides a consistent programming model that works with all models of data storage: flat, relational, and hierarchical. It does this by having no ‘knowledge; of the source of its data, and by representing the data within the Dataset is, it is manipulated through the same set of standards APIs exposed through the Dataset and its subordinate objects. While the Dataset has no knowledge of the source of its data, the managed provider has detailed and specific information. The OLEDB and SQL server .NET Data Providers (System.Data.OleDb and System.Data.Sqlclient) that are part of the .NET Framework provider four basic objects: the command, connection, Data Reader and Data Adapter. In the remaining sections of this document, well walk through each part of the Dataset and the OLE DB/SQL Server .NET Data Providers explaining what they are, and how to program against them. The following sections will introduce you some objects that have evolved, and some that are new. These objects are: Connections. For connection to and transaction against database. Commands. For issuing SQL commands against a database. Data Readers. For reading a forward-only stream of data records from a SQL server data source. Datasets. For storing, removing and programming against flat data, XML data and relational data. Data Adapters. For publishing data into a dataset, and reconciling data against a database. When dealing with connections to a database, there are two different options: SQL server .NET Data Provider (System.Data.Sqlclient) and OLE DB .NET Data Provider (System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider. These

are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data Provider is used to talk to any OLE DB Provider (as it uses OLE DB underneath). CONNECTIONS Connections are used to ‘talk to’ databases, and are represented by provide-specific classes such SQLConnections. Commands travel over connections and result sets are returned in the format of streams which can be read by a DataReader objects, or pushed into a Dataset objects. COMMANDS Commands contain the information that us submitted to a database, and are represented by provider classes such as SQLCommand. A command can be a stored procedure call, an UPDATYE statement, or a statement that returns results. You can also use input and output parameters, and return values as part of your command syntax. The example below shows how to issue an INSERT statement against the North wide database. DATA READERS The Data Reader object is somewhat synonymous with a read-only/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 from a record set. For example, you might use the Data Reader to show the results of a search list in a web page. DATA SETS AND DATA ADAPTERS DATA SETS The DataSet object is similar to the ADO Record set object, but more powerful, and with one other important distinction: the DataSet is always disconnected. The DataSet object represents a cache of data, with database-like structure such as tables, columns, relationships and constrains. However, through a DataSet can and does behave much like a database, it is important to remember that dataset objects do not interact directly with databases, 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, from code, or user input can all be placed into Dataset objects. Then, as changes are made to the Dataset they can be tracked

and verified before updating the source data. The Get Changes method of the Dataset object actually creates a second Dataset that contains only the changes to the data. This Dataset is then used by a Data Adapter to update the original data source. The Dataset has many XML characteristics, including the ability to produce and consume XML data and XML schemas. XML schemas can be used to describe schemas interchanged via Web Services. In fact, a Dataset with a schema can actually be compiled for type safety and statement completion. DATA ADAPTERS The Data Adapter object works as a bridge between the Dataset and the source data. Using the provider-specific SqlDataAdapter (along with its associated SQLCommand and SqlConnection) can increase overall performance when working with a Microsoft SQL Server databases. For other OLE DB-supported databases, you would use the OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection objects. The Data Adapter object uses commands to update the data source after changes have been made to the Dataset. Using the fill method of the Data Adapter calls the SELECT command; using the Update method calls the INSERT, UPDATEOR DELETE commands for each changed 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. For ad-hoc scenarios, a CommandBuilder object can generate these at run-time based upon a select statement. However this run-time generation requires an extra round trip to the server in the order to gather required metadata. So explicitly providing the INSERTING, UPDATEING, DELETEINTG commands at design time will result in better run-time performance.ADO.NET was created with n-Tier, stateless and XML in the forefront. Two new objects, the dataset and data adapter, are provided for these scenarios. Ado.Net can used to get data from a stream, or store data in catch for updates. There is a lot more information about Ado.Net in the documentation. Remember, you can execute a command directly against the database in order to do inserts, update, deletes. You don’t needs to first put data into a dataset in order to insert update, deletes. Also, you can use a dataset to bind to the data, move through the data, move through the data, and navigate data relationships.

SQL SERVER
A data base management, or DBMS, gives the user access to their data helps them transform the data into information. Such as management system includes dbase, paradox, and IMS, SQL and SQL server. These systems allow users to create update and extract from their database. A database is a structured collection of data. Data refers to the characteristics of people, things and events; SQL server stores each data in its own fields. In SQL server the fields relating to particular person, thing or event are bundled together to form a single complete unit of data, called a record (it can also be referred to as a row or an occurrence). Each record is made up of a number of fields .no two fields in a record can have the same field. During a SQL server database design project the analysis of your business needs identifies all the fields or attributes of interest .if your business needs change over time, you define any additional fields or change the definition of existing fields. SQL server tables SQL server stores records relating to each other in a table. Different tables are created for the various groups of information. Related tables are grouped together to form a database. PRIMARY KEY Every table in SQL server has a field or a combination of fields that uniquely identifies each record in table. The unique identifier is called the primary key, or simply the key. The primary key provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify, locate and refer to one particular record in the database. RELATIONAL DATABASE Sometimes all the information of interest to business operation can be stored in one table. SQLServer 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 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 related tables is correctly matched is referred to as maintaining referential integrity. DATA ABSTRACTION A major purpose of database system is to provide users with an abstract view of the data. This system hides certain details of how 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 attributed and what data are actually stored is described and relationship among them VIEW LEVEL: This is the highest level of abstraction at which one describes only part of the database. ADVANTAGES OF RDBMS Redundancy can be avoided. Inconsistency can be eliminated. Data can be shared. Standards can be enforced. Security restrictions can be applied. Integrity can be maintained. Conflicting requirements can be balanced. Data independence can be achieved.

DISADVANTAGES OF DBMS A significant disadvantage of the DBMS System is cost. In addition to the cost of purchasing of developing the software, the hardware has to be upgrade to allow for the extensive programs and the workspace required for their execution and storage. While centralization reduces duplication requires that the database be adequately backed up so that in case of failure the data can be recovered. Features of SQL SERVER (RDBMS) SQL Server is one of the leading database management system (DBMS) because it is the only Database that that meets the uncompromising requirements of today’s most demanding information systems. From complex decision support system (DSS) to the most rigorous online transaction processing (OLTP) application, even application that require simultaneous DSS and OLTP access to the same critical data, SQL Server leads the industry in both performance and capability SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched performance, continuous and support for every database. SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed for online transaction processing and for handling large database application. SQL SERVER with transaction processing option offers two features which contribute to very high level of transaction processing throughput, which are Enterprise Wide Data Sharing The unrivaled portability and connectivity of the SQL server DBMS enables all the systems in the organization to be linked into a single, integrated computing resource. Portability SQL SERVER is fully portable to more 80 distinct hardware and operating systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms.This portability gives complete freedom to choose the database server platforms that meet the system requirements. Open System SQL SERVER offers a leading implementation of industry-standard SQL. SQL Server’s open architecture integrates SQL SERVER and non-SQL SERVER DBMS with

industry’s most comprehensive collection of tools,

application, and third party software

products SQL Server’s open architecture provides transparent to data from other relational database and even non-relational database. Distributed Data Sharing SQL Server’s networking and distributed database capabilities to access data stored on remote server with the same ease as if the information was stored on a single local computer. A single SQL statement can access data multiple sites. You can store data where system requirements such as performance, security or availability dictate. Unmatched Performance The most advanced architecture in the industry allows SQL SEVER DBMS to deliver unmatched performance. Sophisticated Concurrency Control Real world applications demand access to critical data. With most database Systems applications becomes “connection bound”- which performance is limited not by the CPU power or by disk I/O, but user waiting on one another contention free queries to minimize and in many cases entirely eliminates contention waits times. No I/O Bottlenecks SQL Server’s fast commit groups commit and deferred write technologies dramatically reduce disk I/O bottlenecks. While some database write whole data block to disk at commit time, SQL SERVER commits transactions with at most sequential log file on disk at commit time, On high throughput systems, one sequential log file on disk at commit multiple transactions. Testing is the process of confirming that a program or system does what it is proposed off, Testing is the only way to assure the quality of s/w and it is an umbrella activity rather that a separate phase. This is an activity to be performed in parallel with the s/w efforts and one that consists of its own phase of analysis, design, implementation, execution and maintenance.

SYSTEM TESTING
This is the fifth phase of system development life cycle. This is the most important phase of any system development life cycle. During this phase the system is used experimentally to ensure the software does not fail i.e. it will run according to the specifications and in the way users expect? In Electronic mail Service the system was tested firstly by using test data and then by using the various details, special test data was used for testing, to find whether any deviations from the equipped behavior. Implementation & Evaluation: This is the sixth phase of system development life cycle. During this phase the system is implemented and evaluated, implementations is the process of having system personnel check out and put new equipment in to use train users, install the new applications, and construct any five of data needed to use it. Evaluation of the system is performed to identity the strengths and weakness. The actual evaluation can occur along any of the following dimensions. Operational Evaluation: Assessment of the manner in which the system functions including easy of use, response, suitability of information formats, overall reliability and level of utilization. Organizational Impact: Identification & measurement of benefit to organization in such areas as financial concerns, operational efficiency & competitive impact. Includes impact on the internal and external flows User Manager Assessment: Evaluation of the attitudes of the seniors and managers with the organizations as well as the end users.

TESTING STRATEGY:
Unit Testing: This testing method considers a module as single unit and checks the unit at interfaces and communities with other modules rather than getting into details at statement level. Here the module will be treated as BLACKBOX, which will take some inputs and generate output. Integration Testing: Here all the pre-tested individual modules will be assembled to create a larger system and tests are carried out at system level to make sure that all modules are working in synchronous with each other. This testing methodology helps in making sure that all modules which are running perfectly when checked individually and are also running cohesion with other modules. For this testing we create test-cases to check all modules once and then a generated test combination of test paths throughout the system to make sure that no path is making its way into chaos. Validation Testing: Testing is major quality control measure employed during software development. Its basic function is to detect errors. Sub functions when combined may not produce than it is desired. Global data structures can represent the problems. Integrated testing is a systematic technique for constructing the program structure while conducting the tests. To uncover errors that are associated with interfacing the objective is to make test modules and built a program structure that has detected by design. In a non-incremental integration all the modules are combined in advance and the program is tested as a whole. Here error will appear in an endless loop function. In incremental testing the program is constructed and tested in small segments where the errors are isolated and corrected. Different incremental integration strategies are Top-Down integration Bottom-Up integration Regression integration

Testing means quality test. Testing is a process of executing a program with the intent of finding error. A good test case is one that has a high probability of finding an as yet undiscovered error. It is important to keep this statement in a mind as testing is being conducted. Any engineering product can be tested in one of the two ways. Knowing the specific function that a product has been designed to perform, test can be conducted that demonstrates each function is fully operational. This approach is called ‘BLACK BOX TEXTING’. Knowing the internal working of the product, test can be conducted to ensure that “all gears mesh”, that is, that internal operation of the product performs according to specification and all internal components have been adequately exercised. This approach is called “WHITE BOX TESTING”. These approaches provide a mechanism that can help to ensure the completeness of tests and provide the highest likelihood for uncovering errors in s/w. The goals of verification and validation are to access and improve the quality of work products generated during development and modification of s/w. These are 2 types of verification namely. Validation is the process of evaluating s/w at the end of s/w development process. Quality assurance is a planned and systematic pattern of action necessary to provide adequate confirms to the technical requirement. Walkthroughs are sessions where the material being examined is presented by a review and evaluated by a team of reviewers. Inspection involves assessing the s/w life cycle and improving the quality of work products. Life-cycle verification is the process of determining the degree to which the work products of a given phase of the development cycle fulfill the specification established during prior phases. High quality can be achieved through testing of source code alone. Although a program should be totally free of errors, this seldom the case for large s/w products. There are 3 major categories of s/w error. • • • Requirement errors Design errors Implementation errors Quality assurance defines the objective of the project and reviews the overall activities so that the errors are corrected early in the development process. During analysis

and design, an s/w verification plan and acceptance test plan is prepared. The verification plan describes the methods to be used in verifying that the requirements are satisfied by the design documents and that the source is consistent with the requirements specification and design documents. The acceptance test plan includes test cases, outcomes and capabilities demonstrated by each test case. Following completion of the verification plan and acceptance plan, an s/w verification review is held to evaluate the adequacy of the plans.

ONLINE TESTING
A system is tested for online responses, volume of transactions, stress, recovery from failure and usability. System testing involves two kinds of activities-integration testing and acceptance testing. ACCEPTANCE TESTING: It involves planning and execution of functional tests and stress tests in order to demonstrate that the implemented system satisfies its requirements. Tools to special importance during acceptance testing include: • Testing COVERAGE ANALYZER-RECORDS THE CONTROL PATHS FOLLOWED FOR EACH TEST USER. • TRIMING ANALYZER-also calls a profiler, reports the time spent in various regions of the code are areas to concentrate on to improve system performance. • Coding standards-static analyzer and standard checkers are used to insert code for deviations from standard and guidelines. ALPHA and BETA TESTING: If s/w is developed as product to be used by many customers, it is impractical to perform formal acceptance test with each one. So, one most developers use Alpha and Beta testing to uncover that only the end user seems able to find. Alpha testing is conducted by the customer in the presence of many project leaders and recorded the errors and usage problems what they faced. Beta testing is conducted at customer site by the end users of the s/w, the customer recorded that encountered during beta testing and sent those problems to us regular intervals. Then we made the modification and released to the entire customer base. fwv

Screens
Login Page:

Registration Page:

Registration Success:

Login Success:

Inbox:

Compose:

Message Sent Successfully:

Change security code:

Address details:

Logout:

CODING
Code for registration form:
using System; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; public partial class reg : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection("server=pgsystem4;integrated security=true;database=project"); con.Open(); string gender; Session["uid"] = TextBox1.Text; string uid=TextBox1.Text; string fname=TextBox2.Text; string lname=TextBox3.Text; string pwd=TextBox4.Text; string cpwd=TextBox5.Text; if(RadioButton1.Checked) gender=RadioButton1.Text; else gender=RadioButton2.Text; string alternate=TextBox6.Text; string qualification = DropDownList1.SelectedItem.ToString(); string address=TextBox7.Text; string country=DropDownList1.SelectedItem.ToString(); string query = "insert into users values('" + uid + "','" + fname + "','" + lname + "','" + pwd + "','" + cpwd + "','" + gender + "','" + alternate + "','" + qualification + "','" + address + "','" + country + "')"; SqlCommand cmd = new SqlCommand(query,con); int red = cmd.ExecuteNonQuery(); if (red == 1&&CheckBox1.Checked==true) } { Response.Redirect("congrats.aspx"); else { Response.Redirect("failure.aspx"); } } }

Code for login page:
using System; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; public partial class _Default : System.Web.UI.Page { SqlConnection con=null; protected void Button2_Click(object sender, EventArgs e) { TextBox1.Text = " "; TextBox2.Text = " "; } protected void Button1_Click(object sender, EventArgs e) string query = "select * from users where uid='" + TextBox1.Text + "' and pwd='" + TextBox2.Text + "'"; { con = new SqlConnection("server=pgsystem4;integrated security=true;database=project"); con.Open(); SqlCommand cmd = new SqlCommand(query, con); SqlDataReader rd = cmd.ExecuteReader(); bool b = rd.Read(); if (b) Response.Redirect("success.aspx"); else Response.Redirect("failure.aspx"); con.Close(); } protected void LinkButton1_Click(object sender, EventArgs e) { Response.Redirect("reg.aspx"); } protected void LinkButton1_Click1(object sender, EventArgs e) { Response.Redirect("reg.aspx"); } protected void TextBox1_TextChanged(object sender, EventArgs e) { } protected void Calendar1_SelectionChanged(object sender, EventArgs e) { } }

Code for Compose mail
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; public partial class compose : System.Web.UI.Page { SqlConnection con = new SqlConnection("server=pgsystem4;integrated security=true;database=project"); SqlCommand cmd; SqlCommand cmd1; protected void Page_Load(object sender, EventArgs e) { TextBox4.Text = System.DateTime.Now.ToShortDateString(); } protected void Button1_Click(object sender, EventArgs e) { cmd = new SqlCommand("insert into composemail values('" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "')", con); con.Open(); cmd.ExecuteNonQuery(); con.Close(); cmd1 = new SqlCommand("insert into inbox values('" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "')", con); con.Open(); cmd1.ExecuteNonQuery(); con.Close(); Response.Redirect("composesuccess.aspx"); } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("inbox.aspx"); } }

Code for change password:
using System; using System.Data; using System.Data.SqlClient; using System.Configuration; using System.Collections; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; public partial class change : System.Web.UI.Page { SqlConnection con = new SqlConnection("server=pgsystem4;integrated security=true;database=project"); SqlDataAdapter da; DataSet ds = new DataSet(); protected void Page_Load(object sender, EventArgs e) { Label5.Visible=false; da = new SqlDataAdapter("select * from register", con); } protected void Button1_Click(object sender, EventArgs e) { da.Fill(ds, "register"); for(i=0;i<ds.Tables["register"].Rows.Count;i++) { if (TextBox2.Text != ds.Tables["register"].Rows[i]["uid"].ToString()) { Label5.Visible=true; Label5.Text = "<h2>u entered invalid username/password</h2>"; } else if (TextBox3.Text == "") { Label5.Text = "<h2>enter password</h2>"; } else { da = new SqlDataAdapter("update register set pwd='" + TextBox4.Text + "',cpwd='" + TextBox5.Text + "' where uid like '" + TextBox2.Text + "'", con); da.Fill(ds, "register"); Response.Redirect("update.aspx"); } } } protected void Button3_Click(object sender, EventArgs e) { TextBox2.Text = " "; TextBox3.Text = " "; TextBox4.Text = " "; TextBox5.Text = " "; } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("inbox.aspx"); }}

Code for address details:
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class address : System.Web.UI.Page { SqlConnection con = new SqlConnection("server=pgsystem4;integrated security=true;database=project"); SqlDataAdapter da; DataSet ds = new DataSet(); protected void Page_Load(object sender, EventArgs e) { Label1.Visible = false; //Label1.Text = Session["uid"].ToString(); da = new SqlDataAdapter("select uid,fname,lname,gender,alternate,qualification,address,country from register where uid='"+Label1.Text+"'", con); da.Fill(ds, "register"); //DetailsView1.DataSource = ds.Tables["register"]; DetailsView1.DataBind(); } }

CONCLUSION
All the objectives that had been charted out in the initial phases were achieved successfully. System Features: System satisfies all the requirements for which the company developed the system. System has strong security. System is fully GUI based. It is easy operate and user friendly. Platform includes the inbuilt backup and recovery facility. Working on the project was a good experience. Working together in teams helped us to communicate better. We understand the importance of planning and designing as a part of software development. The concept of peer-reviews helped to rectify the problems as and when they occurred and also helped us to get some valuable suggestions that were incorporated by us. Developing the project has helped us to gain some experienced on real time development procedures.

Future Enhancement:
As the developed system was only a prototype, there will be a lot of room for future improvements. Below is the list of future enhancements, which is expected to be made available in the next version of the system. A backup and recovery procedure can be developed to backup all mission critical information and restore all information automatically in times of system fails. Enhancing the system to support for different languages or make available in different kind of languages. User can choose the type of language, which they preferred. Feedback page to be designed and it will be integrated with the system in next version where users can directly send their feedback on the present system. Author is going to have a deep research on two way send and receive mails from user and system.

Bibliography:
Visual Studio Dot Net 2005 Professional ADO.NET Fundamentals of ASP.NET ASP.NET 2.0 in C# C# 2005 FOR DUMMIES Beginning Visual Basic 2005 Sql server 2005 programming VB 2005 XML Weekend Crash Course HTML and CSS 7th Edition : : : : : : : : : : Wrox Publications Wiley publishing,Inc. Laurence Moroney. Matthew MacDonald. Stephen Randy Davis, Chuck Sphar. Thearon Willis,Bryan Newsome Robert Vieira. Wiley publishing,Inc. Kay Ethier and Alan Houser. Dick Oliver,Michael Morrison.

• • • • • • • • • •