Chapter 1 INTRODUCTIONdocshare02.docshare.tips/files/8493/84938047.pdf• Over 6,500 employees...

Chapter 1

INTRODUCTION

1

INTRODUCTION

“Connecting Mail” is a mailing based project designed and implemented to serve the purpose of sending and receiving mails over the internet effectively.

The project deals with e-mails which can be sent, received, read and stored easily. One can compose an e-mail on the ‘COMPOSE MAIL’ page, send it to any other member of the website, and the mail gets stored in the ‘SENT ITEM’ page automatically. The site provides the facility to attach any file along with mail, and send it to the destination. Mails receives are as well stored in the ‘INBOX’ page and can be read or deleted any time. The deleted mails are automatically moved to the ‘TRASH’ where they can be permanently deleted.

‘CONNECTING MAIL’ is also enhanced with an additional feature of ‘GROUP CHATTING’, i.e. all users currently online can chat in a common chat room and sent Instant messages.

1.1BENEFITS FOR USING CONNECTING MAIL

• SEARCH:-

Search instantly within connecting mail to find the exact message you want. You can use connecting mail search the same way you did use Google Search, by entering a word (or multiple words) that appears anywhere within the message you want to locate. If you are looking for a message that contains the word shopping, simply type shopping in the search field and press SEARCH MAIL. Your result will be displayed with your search terms highlighted in yellow.

2

• CHAT:-

With just one click, you can chat in CONNECTING MAIL. Connecting mail chat lets you send and receive instant messages with friends, family and colleagues using chat network. Exchange quick notes and emoticons with anyone on the network using Connecting Mail.

• SECURE:-

Just like blank websites, connecting mails uses HTTPS encryption to keep your mail secure

• SPACE:-

Over 7578.340558 MBs of free storage space and tons more to enhance if you need it.

• FREE:-

The complete use of website is free .

3

4

1.2CMC

“In a free enterprise, the community is not just another stakeholder in the business, but is in fact the very purpose of its existence. - Jamsetji Tata

CMC Limited is a leading systems engineering and integration company in India, offering application design, development, testing services and asset-based solutions in niche segments through turnkey projects of national importance. CMC has also been expanding its service presence in international markets offering off-shoring advantages and delivering value through service level-based and project scope-based deliveries.

Since its inception on December 26, 1975, CMC has been a frontrunner in providing IT solutions and services. CMC was the first ever enterprise in India to set up a countrywide data network called INDONET - a computer network providing access to major cities in India, way back in 1985.

A subsidiary of Tata Consultancy Services Limited (TCS Ltd), one of the world's leading information technology consulting, services and business process outsourcing organizations, CMC Limited is a part of the US$70 billion Tata Group, India's best known business conglomerate.

Today, CMC Limited, an ISO 9001:2000, certified and CMMI Level V accredited organization, is positioned as a premier IT solutions provider in the fast growing and competitive IT market. We execute large and complex turnkey projects, and have built, managed and supported our customers' IT systems across the value chain infrastructure, applications and business processes.

A few highlights of our business

• Over 6,500 employees spread across India, USA, UK, Europe, MEA & APAC• 2,000+ experts in technologies & domain for Application Development Practice• 700 strong skilled force in Embedded Systems • 11 Development Centers across India and USA• Experience in setting up large ODCs up to 300+ team

CMC has 18 offices in major Indian cities and over 150 service locations. We have a sizable resource pool of engineers trained in diverse technologies, with vast domain knowledge and varied skill sets.

5

http://www.tcs.com/

We conduct significant research into emerging technologies and competence areas at our state-of-the-art, ISO 9001 certified R&D Centre in Hyderabad, India. This gives us an edge in complex, high technology projects.

CMC over the years has followed a multi-dimensional approach to support its growth and expansion in becoming a global player.

Together with Tata Consultancy Services Limited (TCS Ltd), our strategic partner, we are working to target the global market with additional offerings that leverage our combined strengths and enable us to follow common best practices.

CMC's wholly owned subsidiary, CMC Americas Inc, was acquired in 1991 and formerly called Baton Rouge International (BRI), before being renamed in 2003. With 9 offices in USA and servicing customers across the country, it drives CMC's thrust towards globalization and business development in USA.

In addition to the following, CMC Americas Inc also maintains offices in Austin, TX; Los Angeles, CA; Sunnyvale, CA; Atlanta, Georgia; Baton Rouge, LA; Novi, MI; Edison, NJ; Reston, VA and Burlington, MA.

CMC Informatics UK is the branch office of CMC Limited in the United Kingdom and covers the territories of UK, Ireland and Europe. The office is based in the historic city of Guildford in Surrey, one of richest counties in the UK.

CMC's products for transport, law enforcement, banking and insurance verticals, and services in embedded technologies, IT Consultancy and Infrastructure Development Management and Outsourcing are offered through this office. The London Underground Limited (LUL), Forth Ports and TRW are a few of our well known clients.

CMC Dubai is the branch office of CMC in West Asia and serves as a front end for CMC's thrust towards globalization, especially in terms of business development in the Middle East and Africa.

The Dubai office handles large projects for important clients like the National Bank of Bahrain and Syrian Railways. In Africa, the Tanzania Police is also handled from this office.

6

http://www.tcs.com/

Since its incorporation in 1975, CMC has an enviable record of successfully building IT solutions for massive and complex infrastructure and market projects.

Take, for instance, just three of the many major projects undertaken by us:

• A passenger ticketing and reservations system for Indian Railways, which runs 6,000 passenger trains carrying over 10 million passengers a day, on a 90,000-km railway network covering around 8,000 railway stations.

• A cargo handling system is a comprehensive online real time cargo handling system to integrate all complex and varied activities of container terminals. This system has been implemented for several Indian and International ports.

• An online transaction processing system for the Bombay Stock Exchange, which handles millions of securities trading transactions every day.

1.2.1 End-to-end solutions capability

We manage turnkey projects, and have built, managed and supported our customers' IT systems across the value chain — infrastructure, applications and business processes. That is because our capabilities span the entire IT spectrum: IT architecture; hardware; software (including systems and application software, development or implementation, maintenance, and frameworks); network consulting; and IT-enabled processing services.

This is how we work:

• Our Customer Services (CS) unit designs and builds the IT infrastructure and network.

• Our Systems Integration (SI) unit develops applications and integrates them across diverse hardware and software platforms.

• Our IT-Enabled Services (ITES) unit manages developed applications and digitization activities.

• Our Education and Training unit provides IT education and training to users.

1.2.2 Strong customer relationships

CMC's customer orientation and service culture lead to enduring bonds with clients. Our distinct value proposition and service culture, coupled with our track record of successful service delivery, are reflected in our long-standing customer relationships with dominant players in key infrastructure, services and government sectors.

Our customers include some of the biggest organizations in India: Reserve Bank of India, Indian Railways, Indian Oil Corporation Limited, Bharat Petroleum Corporation Limited, Oil and Natural Gas Corporation Limited, United Western Bank, Bank of India and Bank of Baroda.

The trust reposed in us by our clients is reflected in our growing revenues from operations such as post-implementation maintenance and support activities.

7

http://www.cmcltd.com/investor_centre/financial_summary.shtml

http://www.cmcltd.com/about_us/clients.shtml

http://www.cmcltd.com/industry_practices/index.shtml

http://www.cmcltd.com/case_studies/bolt.shtml

1.2.3 Strong service delivery chain

In the domestic market, we have established an extensive services network penetrating the remotest geographical locations. This gives us an unmatched advantage in servicing customers with an all-India presence, such as the railways, banks, government entities and other organizations with countrywide operations.

1.2.4 Growth strategies

CMC's growth strategy focuses on capitalizing on its unique skill sets and leveraging the synergies with TCS and other Tata group companies, for growth in revenue and profitability of our operations.

We will continue to focus on consolidating our dominant position in India, while expanding our reach globally.

1.3 What is ASP.NET?

ASP.NET is a service scripting technology that enables scripts (embedded in web pages ) to be executed by an Internet server.

• ASP.NET is a Microsoft Technology

• ASP stands for Active Server pages

• ASP.NET is a program that runs inside IIS

• IIS (Internet Information Services) is Microsoft’s Internet server

• IIS comes as a free component with Windows servers

• IIs is also a part of Windows 2000 and XP Professional

1.3.1 What is ADO?

• ADO stands for Active-X Data Objects

8

• ADO is a Microsoft Active-X component

• ADO is a programming interface to access data in a database

• ADO is automatically installed with Microsoft IIs

1.3.2 What is SQL?

• SQL stands for Structured Query Language

• SQL lets you access and manipulate databases

• SQL is an ANSI(American National Standards Institute) standard

1.3.3 Features of .NET

• Rich Functionality out of the box:

.NET framework provides a rich set of functionality out of the box. It contains hundreds of classes that provide variety of functionality ready to use in your applications. This means that as a developer you need not go into low level details of many operations such as file IO, network communications and so on.

• Easy development of web applications :

ASP.NET is a technology available on .NET platform for developing dynamic and data driver’s web applications. ASP.NET provides an event driven programming model (similar to Visual Basic 6) that simplify development of web pages (now called as web forms) with complex user interface. ASP.NET server controls provide advanced user interface elements (like calendar and grids) that save lot of coding from programmer’s side.

• OOPs Support:

The advantages of Object Oriented programming are well known. .NET provides a fully object oriented environment. The philosophy of .NET is – “Object is mother of all”. Languages like Visual Basic .NET now support many of the OO features that were lacking traditionally. Even primitive types like integer and characters can be treated as objects something not available even in OO languages like C++.

• Multi-Language Support:

9

Generally enterprises have varying skill sets. For example, a company might have people with skills in Visual Basic, C++, and Java etc. it is an experience that whenever a new language or environment is invented existing skills are outdated. This naturally increases cost of training and learning curve. .NET provides something attractive in this area. It supports multiple languages. This means that you have skills in C++, you need not throw them but just mould them to suit NET environment .

Currently four languages are available right of the box. Namely- Visual Basic.NET, C# (pronounced as C-sharp), Jscript.NET and managed C++(a dialect of Visual C++). There are many vendors that are working on developing language compilers for other languages (20+ language compilers are already available). The beauty of multi language support lies in the fact that even though the syntax of each language in different, the basic capabilities of each language remain at par with one another.

• Multi-Device Support:

Modern life style is increasingly embracing mobile and wireless devices such as PDAs, mobiles and handheld PCs….NET provides promising platform for programming such devices. .NET Compact Framework and Mobile Internet Toolkit are step ahead in this direction.

• Automatic Memory Management:

While developing applications developers had to develop an eye on system resources like memory. Memory leaks were major reason in failure of applications. .NET takes worry away from developer by handling memory on its own. The garbage collector takes care of freeing unused objects at appropriate intervals.

1.4 SYSTEM ANALYSIS

1.4.1 Why is System Analysis Necessary?

During system analysis some activities are carried out, such as problem definition, design, and implementation.

Before designing the actual system/project, you should know,

10

1. What is the problem?

2. How to solve it?

3. What are the technical factors required?

4. What are its features and limitations?

If a system is designed without considering above activities then the system will not work properly to the satisfaction of user requirement. So system analysis is necessary to design perfect and accurate system, which satisfies the user requirement.

1.4.2 Role of system analyst:

System analysis is central to the whole of system development. It includes gathering the necessary data and developing plans for new system. This is not an easy task because many people need to be satisfied and many conflicts resolved.

The system analyst is the person who guides the analysis, design and implementation and maintenance of a given system. In performing these four tasks, the analyst must always match the information system objectives with the goals of organization.

• System analyst must determine the requirements of a new system so that during analysis they can discuss with users how to design a new system that meets the requirements.

• System analyst has to provide different solutions to the problem, to satisfy user requirements.

• The system analyst must be able to find out the details about the system itself. To do this, the analyst will have to look at such things as forms (input, output formats), data used by the organization.

11

• System analyst must also be able to work in environment that has considerable ambiguity and uncertainty.

• System analyst must also be creative and imaginative in producing new solutions to meet user requirements.

1.4.2.1 The multifaceted role of the analyst:

The analyst plays his role in many characters. These various roles played by him are:

• Change agent

• Monitor

• Architect

• Psychologist

• Sales person

• Motivation

• Politician

1.4.2.2 Change agent:

The analyst is called as change agent because sometimes he changes the entire policy of industry or organization to improve overall working as well as profit of the organization. The change is brought implementing new software based computer system. In order to make this change successful the analyst should give user as much participation as possible while designing the system.

1.4.2.3 Investigator and Monitor:

12

The analyst finds out why user is not satisfied with the not present system he is using. What are the drawbacks of pitfall in the present system, that user wants to remove by replacing it with new system.

The analyst also monitors the activities going on while designing a new system. The activities to be monitored include successful completion of programs with respect to time, cost and quality.

1.4.2.4 Architect:

System analysts are like architects. He must work with user to identify the goals and shapes of new system. Architect first prepares a plan and according to that plan he develops a building. A system analyst also creates several plans and develops or builds system according to that plan.

1.4.2.5 Psychologist:

Analyst plans the role of psychologist in the way he/she reaches people interprets their behavior and draws conclusion from their interactions.

1.4.2.6 Sales person:

The analyst works as a sales person by giving oral presentation of the system at each stage of development. The analyst should be very good in communication and in putting his ideas before the user. Also he should be able to clarify the issues raised by the user at the time of presentation.

1.4.2.7 Motivator:

The analyst work as a motivator after the system is implemented. It is the responsibility of the analyst to motivate the user to use the new system. It is directly dependent how much user participation is given in the project design and how much efforts are taken to train the user that the user can be motivated to use the new system.

13

1.4.2.8 Politician:

A politician should be a good diplomat, should have proper good control on his party members and should have good influence on the people. It is true for becoming a successful system analyst. While designing a new system, the analyst should not only think about the technical side but also keeping good relations, good control and good influences on the people with and around him.

1.5 DESIGN SPECIFICATIONS & REQUIREMENT

• Software & Hardware Specification:

Specification must reflect the actual application to be handled by the system and include system objective, flowchart, input-output requirement, file structure and cost.

• Reliability:

Software reliability brings up the concept of modularity. A package with a high degree of modularity has the capacity to operate in many machine configurations and perhaps across manufacture product lines.

This software with high potential can work or can be operated in P1 based configuration computers.

• Functionality:

14

It is a definition of the facilities, performance and other factors that the user requires in the finished product.

This software provides the facility of having the complete infrastructure of the house, etc. the performance of the software includes the flexibility of the software.

• Flexibility:

One feature of the flexibility is adaptability, which is of the ease of extending the product. In the field of flexibility, the software covers all factors to be considered. For Example: knowing the astrological sign, KUA number, and etc. of a particular person.

• Usability:

The points to be considered while thinking of usability are portability and understandability. While designing this software, we always try to make it more portable, should not consume more space as well. As we are using HTML as a front-end, which is very user friendly, so it scores full marks in understanding?

• Security:

Security control and access of software or data file should be maintained in this software.

• Capacity:

The software, when under development should be developed in such a way that the number of files, data elements, etc. and size of each of them should be considered. It should not affect the users system, so that he/she can make up gradations or degradations in the system hardware or software.

• Performance:

The language, in which the package is developed, should be well known or say should be aware to the programmers. The operating system may also affect its performance. These both factors are important for consideration. This software should be economical for buying and should be user friendly.

15

In my project, we have considered all above factors and developed such a project that can run in all environments but may be supported by Apache server.

1.5.1 HARDWARE REQUIREMENTS:-

• Min. 16MB RAM.

• Min. 1MB of Display Card.

• Min. 100MB free space on the Hard Disk.

• At least Color Monitors.

1.5.2 SOFTWARE REQUIREMENTS:-

• C# (ASP.NET)

• My SQL

• Minimum Windows 98 and above

16

1.6 Use case

17

View Report

Feedback

Admin

Draft

Register

Login / Logout

Create Profile

View Profile

Forget password

Query

Chat

Trash

Sent Items

Compose mail

1.7 FUNCTIONAL REQUIREMENTS:

18

View Report

Feedback

Admin

Draft

Register

Login / Logout

Create Profile

View Profile

Forget password

Query

Chat

Trash

Sent Items

Compose mail

UserSearch

The Functional Requirement document (also called Functional Specifications or Functional Requirement Specifications), defines the capabilities and functions that a system must be able to perform successfully.

Functional Requirements should include-

• User can login.

• User can browse the inbox.

• User can store mails.

• User can chat with friends.

• User can delete any mails.

• User can search any mails.

• User can give feedback.

• User can ask query.

Email is a relatively simple method of conveying information between multiple parties, and is often used as the basis for conveying business decisions. The relatively quick organizational take up of email as a means of organizational policies for managing email or the application of systems to give effect to email management policies and strategies.

Typically, organizational executives represent their requirements for managing email in terms that are high –level contextual statements of intent, such as “ we need a system to manage our email ”. Because of the diversity of product options, it is incumbent upon the ECM project champion to help organizations better understand their more detailed requirements for managing email.

A requirements analysis and definition effort is typically required to determine the most appropriate business solution option/s that are fit for the organizational needs. The ensuing requirements specification will be a baseline for determining a representative list of technology products that might support the business solution option/s. Both the organization and the prospective vendors will then have a clearer understanding of the requirements for “managing email”.

The first effort may be to develop an email management policy. Many organizations have such policies, but often provide rules relating to use of email for business and private

19

purposes, the nature of content that can/cannot be circulated, relationships to organizational harassment policies, etc. .These policies often do not provide (adequate) guidelines for the “management” of email.

Email management policies often provide classification system to help business users understand the types of emails that are to be managed within an ECM solution and those that do not need to be captured. Email management policies also describe the retention and disposal rules that apply to emails within organizations. Classification examples are:-

Business emails- these emails represent a business transaction or decision that needs to be captured as a record.

Transient emails- these emails may relate to business, but are not viewed as being vital records, and generally would not represent a risk if not captured in ECM solution.

Private emails- these emails (if allowed within organizational usage constraints) might not be captured in the ECM solution.

These classifications are not prescriptive, but indicative, as the requirements may vary between organizations and jurisdictions. While such policies provide generic business rules for managing email, the context also needs to be looked at from a business perspective, to determine the degree of risk exposure posed by the current methods of using email for business transactions/decisions. This analysis needs to take into account, not only business process requirements, but also legal and regulatory considerations.

The ECM practitioner might pose a simple question such as “which business emails do we need to manage, why, and what are the priorities?”.The first part of the question is to help establish focus, and the second is to help analyze the business rationale, and the third is to help establish the priority areas for deploying a solution. During the development of the business strategy for giving effect to the email policy, the practitioner will need to consider the various technology solution options that are available for managing emails.

Some of the technology solution options are:

Direct capture/email archive- these solutions capture all- or a defined set of-emails (and messages) that are received by, and generated within, organizations. These have a range of capabilities, including the ability to categorize by content provide search options, and apply retention/disposal rules.

End-user capture- the end-user captures specific emails that are to be stored in the ECM repository. The ECM solution may support the classification and retention/disposal rules.

20

Customized option- organizations might generate emails from line-of-business (LOB) systems to customers and/or service providers. There may be requirement to integrate LOB systems with an ECM solution to capture these emails as a record.

Some vendors offer a range of products, and often a diversity of functional options. The pre-requisites to the development and specification of functional requirements for managing email within an enterprise are viewed as (a) the development and publication of an email management policy, and (b) a clear definition of the business strategy for implementing email management.

1.8 NON FUCTIONAL REQUIREMENTS:

A non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture.

1.8.1 Software System Attributes

Usability: The links provided for each form. The user is facilitated to view and make entries in the forms. Validations are provided in each field to avoid inconsistent or invalid entry in the databases. Some forms consists Hyper Links, which provides further details. Reports screen contains text boxes and drop down lists, so that reports can be produced.

Security: Application will allow only valid users to access the system. Access to any application resource will depend upon user’s designation. There are two types of users namely Administrator and Student. Security is based upon the individual user ID and Password.

Maintainability: The installation and operation manual of examination management system will be provided to the user.

Availability: System will be available around the clock except for the time required for the backup of data.

Portability: The application is developed in ASP.NET. It would be portable to other operating system provided .NET Framework is available for the OS. As the database is

21

made in DB2, porting the database to another database server would require some development effort.

Acceptance Criteria

The software should meet the functional requirement and perform the functionality effectively and efficiently.

• A user-friendly interface with proper menus.

• Data transfer should be accurate and within a reasonable amount of time keeping in mind the network traffic.

• The system should not allow entry of duplicate key values.

• System should have the ability to generate transactional Logs to avoid any accidental loss of data.

• Log file should also be generated.

1.8.2 Security and Reliability Requirements

• Security

The information should be Secure; there should not be any kind of malfunctioning. All the results, details of Exams taken and Questions and stored securely in the system. System Information will not be changed by any person rather than the management.

• Reliability

System should be reliable. It should keep secure all the information regarding to particular Student, Faculty, Questions and Results. It should work effectively in tremendous rush. The system must give the perfect calculation and perfect results in kind of damn situation. The particular result must be listed in to the particular user only; there should not be any kind of data integrity or other problem between Administrator, Faculty and Student.

• Flexibility

System is working easily on the Intranet with the username and password of the user. The Institute has given the rights to the staff and the students to use the system with their

22

username. The system can also work on other kind of technology with the little modification. System should be quite flexible to install and maintain.

• Efficiency

System should be efficient enough to meet all kinds of requirements as required by the Administrator, Faculty and Student. The system should not hang or lose its efficiency in any kind of worse conditions. It should provide the correct output in all manners.

• User Friendliness

System should be user friendly, so that any user can access the system.

1.9 FEASIBILITY STUDY

1.9.1 Introduction:

A feasibility analysis involves a detailed assessment of the need, value and practicality of a proposed enterprise, such as systems development. The process of designing and implementing Record-keeping systems has sufficient accountability and resource implications for an organization. Feasibility analysis will help you make inform and transparent decision at crucial points during the developmental process with a particular course of action.

1.9.2 Cost effectiveness:

The cost encompasses both designing and installing the system. It includes user training, updating the physical facilities & documenting. System Performance criteria are evaluated against the cost of each system to determine which system is likely to be most cost effective and also meets the performance requirements. Cost are most easily determine when the receipts if the systems are tangible and measurable. An additional factor to consider is the cost of the study design and requirements.

Each candidate system’s performance is evaluated against the system performance requirements set prior to the feasibility study. Whatever the criteria, there has to be as close a match as practicable, although trade-off are often necessary to select the best system. In

23

weight system performance each candidate system is weighted by it performance and cost data by applying a rating figure. Then candidate system with the highest total score is selected. The procedure for weighing candidate system is simple:

a. Assign a weighing factor to each evaluation criterion based on the criteria’s effect on the success of the system.

b. Assign a quantitative rating to each criterion qualitative rating.c. Multiply the weight assigned to each category by the relative rating to determine

the score.d. Sum the score column for each candidate system.

There are two types of analysis:

1. Benefit-Cost –Analysis(BCA) It is a systematic, quantitative method of assigning the life cycle-cost and benefits of completing alternative approaches. This includes which one of the alternatives is best.

2. Cost Effectiveness Analysis (CEA) It is a simplified BCA, which can be done when either the either the benefits or the cost are the same for all alternatives. The analysis is greatly simplified because the best alternative is either the one with the most benefits (when the costs are the same for al alternatives) or the one with the lowest cost (when the benefits are the same for all alternatives).

1.9.3 Information sources:

To find out the information about our project is called Information gathering. It is an art and science. The approach and manner in which the information is gathered required person with sensitivity, common science and knowledge of what and when to gather and channels to use in the secure the information. The methodology and tools for information gathering required training and the experience and training is required.

The phases for information gathering while system analysis is:

1. Familiarity with the present system through the available information such as procedure manuals, documents and their flow, interviews with staff and on side observation.

24

2. Definition of the decision-making is associated with managing the system. Conducting interviews clarifies the decision point and how decisions are made in user area.

3. Once decision points are defined, a series of interviews conducted define the information requirement of user. The information is analyzed and document.

1.9.4 Kind of information:

Before one document where to go for information or what tools to use, the first requirement is to figure out what information to gather. Much of information we need to analyze relates to the organization in general the user staff and workflow.

1.9.5 Categories of informatin

• Information about organization:

25

Information about organization`s policies, goals, objectives and structure explain the kinds of environment that introduce the computerized system. Policies are translated into rules and procedures for achieving the goal are set a organization for achieving the goal. After policies and set, a organization is organized to meet these goals.

• Information about User Staff:

Another kind of information for analysis is knowledge about people who run the present system their job functions and information requirements, the relationship of job with existing system and interpersonal network that hold the user group together.

• Information about Work Flow

Work flow focuses on what happens to data through various points in a system. This can show by a data flow diagram or a system flowchart and direction from source to destination. In contrast, the system flowchart represents physical system.

1.9.6 Time Feasibility

As you study about what is mean by feasibility study, the Time Feasibility is the sub point of it. It means the study of time period, which is required for the system. Using this time feasibility analyst will design a proper life cycle it is mentioned that at which time the system will be ready to use. This Time Feasibility will be sent at the initial stage of system.

The CBS time period should match the system life cycle.

26

The system life cycle ends when the system is terminated or is replaced by a system that has significant differences in processing, operational capabilities, resource requirement, or system outputs. Significant differences are a very subject term, and some organization, while others may be that the change must be over 30% to be significant.

1.9.7 Software & hardware availability:

When you design a system at that stage there are some requirements for the systems, for that you should study on your system. While studying you determine what are the requirements for your system. There are two types of requirements software & hardware requirements. For example in the database the same amount of RAM for graphics card is called Hardware requirements.

Steps in the feasibility analysis:

• Form a project team and appoint a project leader:

The concept behind the project team is that future system users should be involved in its design and implementation. Their knowledge and experience in the operation area are essential to the success of the system. For small projects, the analyst and an assistant usually suffice; however, more complex studies require a project team. The team consists of analysis and user staff-enough collective expertise to devise a solution to the problem. Even many times, an outside consultant and an information specialist join the team until the job is completed. Projects are planned to occupy a specific time period, ranging from several weeks to months. The senior system analyst is appointed as project leader.

• Prepare system flowcharts:

Information oriented charts and dataflow diagram prepared in the initial investigation are reviewed at this time. The charts bring up the importance of the output, input and dataflow among key points in the existing system. All other flowcharts needed for detailed evaluation are completed at this point.

27

• Enumerate potential candidate system:

This step identifies the candidate system that is capable of producing the outputs include in the generalized flowcharts. This requires a transformation from logical to physical system models. Another aspect of this consideration of the hardware that can handle total system requirements.

• Describe and identify characteristics of candidate system:

From the candidate system considered, the team begins a preliminary evaluation in an attempt to reduce them to a manageable number. The information along with additional data available through the vendor highlights the positive and negative features of the system. The constraints unique to each system are also specified.

• Determine and evaluate performance and cost-effectiveness of each candidate system:

Each candidate system performance is evaluated against the system performance requirements set prior to the feasibility study. Whatever the criteria, there has to be as close a match as practicable, although trade-off are often necessary to select the best system.

The cost encompasses both designing and installing the system. It includes user training, updating the physical facilities & documenting. System performance criteria are evaluated against the cost of each system to determine which system is likely to be the most cost effective and also meets the performance requirements. Cost are most easily determine when the receipt if the systems are tangible and measurable. An additional factor is the cost of the study and requirement.

28

29

Chapter 2

SYSTEM DESIGN

30

2.1 SDLC (System Development Life Cycle)

A structured sequence of phases for implementing an information system is system design life cycle of that system. The various steps involved in the system design life cycle are as follows:-

Reorganization of need (preliminary survey/initial investigation):-

The steps involve about outlining the problem and understanding what are the present methods of solving the problems, which are designing the system. It includes preliminary survey/initial investigation as well.

Feasibility study:

(Evaluation of existing system and procedure analysis of alternative candidate systems cost estimation)

The feasibility study is a formal proposal for a new system. Before the project is to begin, the project is studied to determine what exactly the user wants depending upon the result of initial investigation. The survey is expanded to more detailed study.

Feasibility study can be understood by giving the answer/solution of these their requirements:-

Q. What are the user’s demonstrable needs and how does a candidate system meet them?

Answer:-

Our new system covers all the basic of the user for e.g. , as mentioned earlier that our database is MS SQL SERVER, which does not have limitation to store data. And one of the major advantages of new system is that it avoids redundancy means there is no repetition of the data.

Q. What resources are available for given candidate system? Is the problem worth solving?

31

Answer:-

In the existing system the opera or has to learn all the operation of the commands. Whichever is coming in light while operating a particular form then one help called tool tip will come if the mouse point comes on corresponding fields of particular form.

Q. What is the likely impact of the candidate system on the organization? How will do if fit within the organizations master M.I.S. plan:-

Answer:-

The new system is well fitted in the office working condition, because it covers all basic needs of the user working in the office. It is less tedious and less time consuming.

System analysis:-

Analysis is a detailed study of various operations performed by the system and the relationship within and outside of the system that is it includes finding out in more detailed what the system problem are the different new changes the user wants.

System design:-

The system design is most creative and challenging phase of the system design life cycle. Analyst phase is used to design the logical model of the system and system design the physical model of the system:

In these phase system designer designs:-

Output:- Output design means that what should be the format presentation of the result. First of all for designing of various forms to be present which is the front end of our software.

Input:- In input design stage, which is the part of the system design stage the system analyst has to decide what inputs are required for the system and prepare input format to give input to the system according to the requirement.

2.2 DATA FLOW DIAGRAM

32

The project dictionary contains an entry for each DFD developed during analysis. Thus there is a context diagram. A top level DFD and detailed diagram for all top level functions and their components. Each DFD has a unique number and can be reference by that number.

DFD is a graphic representation of system that shows data flow to, frame and within the system, processing functions that change data in some manner and the storage this data. DFD are nothing but more than network of a related system functions (processing of data) that indicate from where information (data) is received (inputs) and to where it is send (outputs). It is also called as bubble charges.

DFD’s are more detailed than content diagram. DFD’s are used to despite specifics data flows (movement of inform) from both the physical view point (How it is done ) and the logical view point (what is done).

DFD use a number of symbols to represent system. Most data flow modeling methods use four kinds of symbols these symbols are used to represent four kinds of system components.

1. Process

2. Data stores

3. Data flows

4. External entities

33

Function Database

Input/Output Flow

DATA FLOW DIAGRAM

0 LEVEL DFD:

Fig.2.2.1 Context Level DFD for Connecting Mail

34

1-LEVEL DFD:

Fig.2.2.2 1-Level DFD for Connecting Mail

35

2-LEVEL DFD:

1. MEMBER LOGIN

Fig.2.2.3.1 2-Level DFD for Connecting Mail

36

2. QUERY

Fig.2.2.3.1 2-Level DFD for Connecting Mail

37

2.3DESCRIPTION OF MODULE

• LOGIN: This module allows the user to browse the website after login.

• FEEDBACK: This module allows the user to give the feedback about the website.

• QUERY: This module allows the user to ask any query related to the website from the administration.

• SENT ITEMS: This module allows the user to check for those mails that are sent.

• DRAFT: This module allows the user to save the mail.

• SEARCH: This module allows the user to search any mail.

• RECEIVE MAIL: This module allows the user to check the received mail.

• TRASH: This module allows the user to delete any mail.

• ATTACHMENT: This module allows the user to attach any file (i.e text, picture, music and movie) in a mail.

• FORGET PASSWORD: This module allows the user to retrieve the password by giving the security answer of the questions.

• PROFILE: This module allows the user to give their personal information in the profile.

• SETTING: This module allows the user to change the setting of the profile or to delete the account.

• NEW USER: This module allows the user to become the member of the website by registering.

38

2.4 DATABASE DESIGN

Database design is a complex subject, no matter how easy some people think it is. This section only scratches the surface, but it is a good scratch

A properly design database is a model of a business or something in the real world. Like their physical model counterparts, data models enable you to get answers about the facts that make up the objects being modeled. It`s the question that need answer that determine which facts need to be stored in the model.

In the relational model, data is organized in the tables that have the following characteristics: everywhere records has the same number facts; every field contains the same type of facts in each record; there is only one entry for each fact; no records are exactly the same; the other of the records and fields is not important.

Database design is the process of producing a detailed data model of a database. This logical data model contains all the needed logical and physical choices and physical storage parameters needed to generate a design in a DATA DEFINITION LANGUAGE, which can then be used to create a database. A fully attributed data model contains detailed attributes for each entity.

The term database design can be used to describe many different parts of the design of an overall database structure used to store the data. In the relational model these are the tables and views. In an object database the entities and relationships map directly to object classes and named relationships. However, the term database design could also be used to apply to the overall process of designing, not just the base structures, but also form and queries used as part of the overall database application within the database system (DBMS).

The process of doing database design generally consists of a number of steps which will be carried out by the database designer. Usually, the designer must:

Determine the relationship between different data elements.

Superimpose a logical structure upon the data on the basis of these relationships good database design.

39

ADMIN TABLE DEFINITION

ADMIN TABLE DATA

LOGIN TABLE DEFINITON

LOGIN TABLE DATA

40

MEMBER TABLE DEFINITION

MEMBER TABLE DATA

41

DRAFT TABLE DEFINITON

DRAFT TABLE DATA

FEEDBACK TABLE DEFINITON

42

FEEDBACK TABLE DATA

IMAGE TABLE DEFINITON

43

IMAGE TABLE DATA

INBOX TABLE DEFINITON

44

INBOX TABLE DEFINITON

OUTBOX TABLE DEFINITION

45

OUTBOX TABLE DATA

PROFILE TABLE DEFINITON

46

PROFILE TABLE DATA

47

QUERY TABLE DEFINITON

QUERY TABLE DATA

48

2.5 E-R DIAGRAM

49

1

50

LOGIN

Access

ADMIN MEMBER

View

FEEDBACK

Reply

QUERY

Provides

Edit

IMAGE

Store

DRAFT

Manages

INBOX

OUTBOX

PROFILE

uname

password

uname

password

S_no

password

sa

sq

email

uname

Confirm password

ID

feedback

S_no

salutation

name

Email_id

Phone_no

citycountry

address

Write_here

S_no

sender

rec

datesubje

ctbody attachm

entstatus

draft

S_no

sender

rec

date

subject

body attachment

status

draft

S_no

sender

rec

date

subject

body

attachment

status

draft

S_no

image

uname

button

S_no

emailid

dob

imgid

Phone

lastname

firstname

address

1 1

1

M

1

N

11

11

N

N

N

N

1

N1

N

N

2.6 PROGRAM SPECIFICATION

After the broad stages or modules for a system have been define did this necessary to move preparation of detailed programming specification. The programs or modules are defined according to the functions they perform, not by the size of the program. The breakdown of programs into smaller modules makes it easier to debug a system and modify it. Program specification must be developed from each module, which involve program name, purpose for the program, owner of the project and general information about the program.

The program development process include three important stages namely program design, program coding and program testing. All three stages contribute to the production of high quality program. In this chapter the techniques used for any designing any program coding testing has been discussed.

Program design is the foundation for a good program and is therefore an important part of the program development cycle. Before coding a program should be well conceived and all aspects of the program design should be consider in details.

Program design is a basically concern with the development of a strategy to be used in writing a program development cycle. Before coding a program, the program should be well conceived and all aspects of the program design should be considered in a detail.

• Program analysis

• Outlining program structure

• Algorithm development

• Selection of control structure

51

2.6.1 PROBLEM ANALYSIS:-

Before we are thinking of solution procedure to problem we must fully understand the nature of the problem and what we want to the program to do. Without the complementation the definition of the problem at hand program design might turn into a hit is miss approach. We must carefully decide following at this stage:

What kind of data will go in?

What kinds of outputs are needed?

What are the constraints and condition under which program has to operate?

2.6.2 ALGORITHM DEVELOPMENT:-

After we decided a solution an overall outline of the program, the next step is to work out the detail definition, step by step procedure known as algorithm for each function. The most common method of describing an algorithm is the use of flowcharts. The other method is write what is known by pseudo code. The flowcharts present the algorithm pictorially while the pseudo code describes the solution steps in logical order. Either method’s involves concept of logical and creativity.

Since algorithm is key factor for developing an effective program, we should devote enough attention to this step. A problem might have different approaches to the solution. For example there are mane- sorting techniques available to sort a list. Similarly there are many of the finding area under the curves. We must consider all approaches and select the one, which is simple to follow, take less execution and procedures with the required accuracy.

52

2.6.3 CONTROL STRUCTURE

A complex solution procedure may involve large number of control statements to direct the flow of execution. In such indiscriminate use of control statement such as go to may lead to understand and incomprehensible program. It has demonstrated that any algorithm can be structure denotes three basic control structure namely, sequence structure, selection structure and looping structures.

As well design program would provide the following benefits:

1. Coding is easy and error free.

2. Testing is simple

3. Maintenance is easy

4. Good documentation is possible.

5. Cost estimates can be made more accurately

6. Progress of coding may be control more precisely

2.6.4 PROGRAM CODING

The algorithm developed in the previous section must be translated into a set of instruction that a computer can understand. The major emphasis in coding should be simplicity and clarity. A program written by has to read by other later. Therefore it should be readable and simple to understand. Complex logic and tricky coding should be avoided. The element of coding style include internal document, construction of statements, generally of the program and input/output formats.

Use one statement per line.

Use proper indentation when selection and looping structure are implemented.

Avoid heavy nesting of loops, preferable not more than three levels.

53

Use simple conditions test, if necessary break complicated condition into simple condition.

2.6.5 INPUT/OUTPUT FORMATS:-

INPUT/OUTPUT FORMAT should be simple and acceptable to users. A number of guideline should be considered during coding:-

• Keep format simple

• Use end of indicators rather than the user require specifying the number of items.

• Label all interactive input reports

• Label all output reports

• Use output messages when the output contains some peculiar result

SUMMARY

This chapter should provide use with details of program design, analyses, algorithm development, and program coding statement, constructional, internal documentation and different input/output formats which are of importance, enough to be considered before developing any program

54

Chapter 3

DEVELOPMENT

&

IMPLEMENTATION

55

3.1 INPUT & OUTPUT CONSIDERATION:

Welcome to “CONNECTING MAIL- A MAILING WEBSITE”

The CONNECTING MAIL website handles the daily mail basis. It uses C#-ASP.NET as a front end & MS SQL SERVER as a back end

Electronic mail, commonly called email or e-mail, is a method of exchanging digital messages from an author to one or more recipients. Modern email operates across the internet or author computer networks. Some early emails systems required that the author and the recipient both be online at the same time, instant messaging. Today`s email system are based on a store-and-forward model. Emails servers accept, forward, deliver and store messages. Neither the user nor their computers are required to be online simultaneously; they need connect one briefly, typically to an email server, for as it takes to send or receive messages.

An email message consists of three components, the messages envelope, the message header, and the message body. The message header contains control information, including, minimally an originator`s email address and one or more recipient addresses. Usually descriptive information is also added such as a subject header field and a message submission date/time stamp. Originally a text only (7-bit ASCII) communication medium, emails was extended to carry multi-media content attachment, a process standardized in RFC 2045

56

3.2 SCREENSHOTS

OUTPUT SCREEN

1. When user enter the username and password INBOX page will be displayed

57

2. When the user wants to save the mail, the mail will be saved in DRAFT PAGE.

58

3. When the mail is send, DONE will be written on the button.

59

4. Send mails will be displayed in the SENT ITEMS PAGE

60

5. The mail which is send to the receiver will be shown in her INBOX

61

6. When the mails are deleted.

62

7. Query is submitted

63

8. Feedback submitted

64

9. Chat

65

10.Profile

66

11.Setting

67

12.When the new user becomes the member of the website, he can continue.

68

13.Output screen of admin login

Admin can proceed further

69

14.Admin give reply to the query of the user

70

15.Admin can view the feedback result

71

INPUT SCREEN

16.User fills the field of the login page.

LOGIN FORM : this form is used for typing the user name and password by using the keyboard as well as by using interface.

72

17. User can compose the mails.

73

18. User can fill the profile page.

74

19. User can ask query.

75

20. User can give feedback.

76

21. User can change the setting

77

22. New user can be created.

78

23.Chat

79

24. Admin login

Click here for admin

80

25.Only admin can login

81

26.Admin can view queries of the member

82

27.Admin can view feedback of the members

83

28.Forget password

84

3.3 CODING

85

ADMIN PAGES

Source code of adminlogin.aspx

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="adminlogin.aspx.cs" Inherits="adminlogin" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title>Untitled Page</title> <style type="text/css"> #side { height: 627px; width: 799px; } </style></head><body> <form id="form1" runat="server"> <div id="Div1" runat="server" style="background-image: url('images/star.jpg');"> <div id="side">

<br /> <br /> <br /> <br /><br />                                                                         <asp:Label ID="Label1" runat="server" Text="ADMIN LOGIN" Font-Bold="True" Font-Names="Comic Sans MS" Font-Size="XX-Large" ForeColor="Yellow"></asp:Label> <br /> <br /> <br /> <br />                                     <asp:Label ID="Label2" runat="server" Font-Names="Comic Sans MS" Font-Size="Larger" ForeColor="Aqua" Text="USERNAME"></asp:Label>

86

                  <asp:TextBox ID="txt_adname" runat="server"></asp:TextBox> <br /> <br />                                   <br />                                       <asp:Label ID="Label3" runat="server" Font-Names="Comic Sans MS" Font-Size="Larger" ForeColor="#66FFFF" Text="PASSWORD"></asp:Label>               <asp:TextBox ID="txt_adpass" runat="server" TextMode="Password"></asp:TextBox> <br /> <br /> <br />                                                                                         <asp:Button ID="btn_adlogin" runat="server" onclick="btn_adlogin_Click" Text="LOGIN" /> <br /> <br /> <br />                                                                     <asp:Label ID="lbl_admsg" runat="server"></asp:Label>          </div> </div> </form></body></html>

87

Source code of adminMasterpage.master

<%@ Master Language="C#" AutoEventWireup="true" CodeFile="adminMasterPage.master.cs" Inherits="adminMasterPage" %>


<html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title>Untitled Page</title> <link rel="stylesheet" type="text/css" href="style.css" /><script type="text/javascript" src="clockp.js"></script><script type="text/javascript" src="clockh.js"></script> <script type="text/javascript" src="jquery.min.js"></script><script type="text/javascript" src="ddaccordion.js"></script><script type="text/javascript">ddaccordion.init({

headerclass: "submenuheader", //Shared CSS class name of headers group

contentclass: "submenu", //Shared CSS class name of contents grouprevealtype: "click", //Reveal content when user clicks or

onmouseover the header? Valid value: "click", "clickgo", or "mouseover"mouseoverdelay: 200, //if revealtype="mouseover", set delay in

milliseconds before header expands onMouseovercollapseprev: true, //Collapse previous content (so only one open

at any time)? true/false defaultexpanded: [], //index of content(s) open by default

[index1, index2, etc] [] denotes no contentonemustopen: false, //Specify whether at least one header should

be open always (so never all headers closed)animatedefault: false, //Should contents open by default be

animated into view?persiststate: true, //persist state of opened contents within

browser session?toggleclass: ["", ""], //Two CSS classes to be applied to the

header when it's collapsed and expanded, respectively ["class1", "class2"]

togglehtml: ["suffix", "<img src='images/plus.gif' class='statusicon' />", "<img src='images/minus.gif' class='statusicon' />"], //Additional HTML added to the header when it's collapsed and expanded, respectively ["position", "html1", "html2"] (see docs)

animatespeed: "fast", //speed of animation: integer in milliseconds (ie: 200), or keywords "fast", "normal", or "slow"

oninit:function(headers, expandedindices){ //custom code to run when headers have initalized

//do nothing},onopenclose:function(header, index, state, isuseractivated){

//custom code to run whenever a header is opened or closed//do nothing

}})</script>

<script type="text/javascript" src="jconfirmaction.jquery.js"></script>

88

<script type="text/javascript">

$(document).ready(function() {$('.ask').jConfirmAction();

});

</script>

<script language="javascript" type="text/javascript" src="niceforms.js"></script><link rel="stylesheet" type="text/css" media="all" href="niceforms-default.css" /> <style type="text/css"> .search_submit { height: 24px; width: 28px; } </style></head><body> <form id="form1" runat="server"> <div style="height: 135px"> <div id="main_container">

<div class="header"> <div class="logo"><a href="#"><img src="images/logo.gif" alt="" title="" border="0" /></a></div> <div class="right_header" style="font-style:italic; font-size:medium; color:Aqua; height: 15px;">Welcome ,<asp:Label ID="Label1" runat="server"></asp:Label> <a href="profile.aspx">PROFILE</a>

<asp:LinkButton ID="LinkButton1" runat="server" onclick="LinkButton1_Click">LOGOUT</asp:LinkButton> <%-- <asp:LoginStatus ID="LoginStatus1" runat="server" LogoutPageUrl="~/login.aspx" Font-Size="Medium" ForeColor="Aqua" LoginText="LOGIN" LogoutText="LOGOUT" />--%> </div> <div id="clock_a"></div> </div> <div class="main_content"> <div class="menu"> <ul> <li><a class="current" href="#">HOME</a></li> <li><a href="#">About Us</a>   </li>

89

<li><a href="#">Edit</a>  <ul> <li><a href="setting.aspx" title="">Setting</a></li> </ul>  </li> <li><a class="current" href="query.aspx">QUERY</a></li> <li><a class="current" href="feedback.aspx">FEEDBACK</a></li> </ul> </div> <div class="center_content"> <div class="left_content"> <div class="sidebar_search" style="float:left"> <input type="text" name="" class="search_input" value="search keyword" onclick="this.value=''" />     <a id="A1" href="search.aspx" runat="server"><img src="images/search.png" style="height: 33px; width: 35px"/></a> </div> <br /><br /><br /><br /> <div class="sidebarmenu"> <a class="menuitem" href="inbox.aspx">INBOX</a> <a class="menuitem" href="composemail.aspx">COMPOSE MAIL</a> <a class="menuitem" href="draft.aspx">DRAFT</a> <a class="menuitem" href="trash.aspx">TRASH</a> <a class="menuitem" href="sentitems.aspx">SENT MAILS</a> <a class="menuitem" href="chat.aspx" >CHAT</a> </div> </div> <div class="right_content"> <br /> <span class="bt_green_lft">

90

<asp:ContentPlaceHolder id="ContentPlaceHolder1" runat="server"> </asp:ContentPlaceHolder> </span> </div> </div>  </div>  </div>

<br /> <br /> <br /> </div> </form></body></html>

Source code of adminreport.aspx

<%@ Page Language="C#" MasterPageFile="~/adminMasterPage.master" AutoEventWireup="true" CodeFile="adminreport.aspx.cs" Inherits="adminreport" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <br /> <br /> <br /> <asp:DropDownList ID="DropDownList1" runat="server"> <asp:ListItem>VIEW QUERY</asp:ListItem> <asp:ListItem>VIEW FEEDBACK</asp:ListItem> </asp:DropDownList> <br /><br /><br /> <asp:Button ID="BTN_REPORT" runat="server" Text="CLICK HERE TO PROCEED FURTHER" Height="30px" BackColor="Aqua" Font-Bold="False" Font-Names="Comic Sans MS" onclick="BTN_REPORT_Click" /> <br /> <br />

91

<br /></asp:Content>

Source code of adminreply.aspx

<%@ Page Language="C#" MasterPageFile="~/adminMasterPage.master" AutoEventWireup="true" CodeFile="adminreply.aspx.cs" Inherits="adminreply" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <div style="text-align:left"> <br /><br /> <br /> <br />     <asp:Label ID="LblQuery" runat="server" Text="QUERY :" Font-Size="Medium" Font-Bold="False" Font-Names="Comic Sans MS" ForeColor="#FFFF66"></asp:Label><br />     <br />    <asp:Label ID="LblQuestion" runat="server" Font-Bold="False" Font-Size="Medium" Font-Names="Comic Sans MS" ForeColor="#FFFF66"></asp:Label> <br /> <br /> <br /><br />      <asp:Label ID="LblReply" runat="server" Text="Reply :" Font-Size="Medium" Font-Bold="False" Font-Names="Comic Sans MS" ForeColor="#FFFF66"></asp:Label> <br /> <br />     <asp:TextBox ID="TxtReply" runat="server" Font-Bold="True" Font-Size="Medium" TextMode="MultiLine"></asp:TextBox> <br /><br /> <br /> <br /> <br />     <asp:Button ID="BtnReply" runat="server" Text="SEND REPLY" onclick="BtnReply_Click" Font-Bold="False" BackColor="Yellow" Height="34px" Width="132px" />                       <asp:Button ID="BtnBack" runat="server" Font-Bold="False"

92

onclick="BtnBack_Click" Text="Back" Width="69px" BackColor="Yellow" Height="35px" /> <br /> <br /> <br />     <asp:Label ID="LblSend" runat="server" Font-Bold="False" Font-Size="Medium" ForeColor="#FFCCFF" Font-Names="Comic Sans MS"></asp:Label><br /><br /><br /> </div></asp:Content>

Source code of viewfeedback.aspx

<%@ Page Language="C#" MasterPageFile="~/adminMasterPage.master" AutoEventWireup="true" CodeFile="viewfeedback.aspx.cs" Inherits="viewfeedback" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <asp:Button ID="BtnResults" runat="server" Text="FEEDBACK RESULTS" onclick="BtnResults_Click" Font-Bold="False" Font-Names="Comic Sans MS" BackColor="Yellow" Font-Size="Medium" Height="41px" Width="262px" /> <br /> <br /> <asp:Label ID="LblResults" runat="server" BackColor="#FFCCFF" Font-Bold="False" Font-Names="Comic Sans MS" Font-Size="X-Large" ForeColor="#003399"></asp:Label><br /><br /> <br /> <br /> <asp:Label ID="Lblexcellent" runat="server" Font-Bold="False" Font-Size="Larger" Font-Names="Comic Sans MS" ForeColor="#00FFCC"></asp:Label><br /><br /><br /> <asp:Label ID="Lblverygood" runat="server" Font-Bold="False" Font-Size="Larger" Font-Names="Comic Sans MS" ForeColor="#00FFCC"></asp:Label><br /><br /><br /> <asp:Label ID="Lblgood" runat="server" Font-Bold="False" Font-Size="Larger" Font-Names="Comic Sans MS" ForeColor="#00FFCC"></asp:Label><br /><br /><br /> <asp:Label ID="Lblaverage" runat="server" Font-Bold="False" Font-Size="Larger" Font-Names="Comic Sans MS" ForeColor="#00FFCC"></asp:Label><br /><br /><br /> <asp:Label ID="Lblbad" runat="server" Font-Bold="False" Font-Size="Larger" Font-Names="Comic Sans MS" ForeColor="#00FFCC"></asp:Label><br /><br />

93

<br /> <br /> <br /> <br /> <asp:Button ID="BtnBack" runat="server" Text="Back" Font-Bold="False" onclick="BtnBack_Click" Width="106px" BackColor="#FFFF66" Font-Names="Comic Sans MS" Font-Size="Medium" /></asp:Content>

Source code of viewquery.aspx

<%@ Page Language="C#" MasterPageFile="~/adminMasterPage.master" AutoEventWireup="true" CodeFile="viewquery.aspx.cs" Inherits="viewquery" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <div><asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False" BackColor="#FFFF99" Height="264px" Width="555px"> <Columns> <asp:TemplateField HeaderText="S.No"> <ItemTemplate> <asp:HiddenField ID="HdnEmail" runat="server" Value='<%#Eval("email_id") %>' /> <asp:Label ID="LblS_NO" runat="server" Text='<%#Eval("s_no") %>'> </asp:Label> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="Queries"> <ItemTemplate> <asp:Label ID="LblWriteHere" runat="server" Text='<%#Eval("write_here") %>'> </asp:Label> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="Answer To Queries"> <ItemTemplate> <asp:CheckBox ID="chkeachrow" runat="server" AutoPostBack="true" oncheckedchanged="chkeachrow_CheckedChanged" /> </ItemTemplate> </asp:TemplateField> </Columns> </asp:GridView>

94

<br /> <br /> <br /> <br />                                                                                             <asp:Button ID="BtnBack" runat="server" Font-Bold="False" onclick="BtnBack_Click" Text="Back" Width="78px" BackColor="#00CCFF" EnableViewState="False" Font-Size="Medium" Height="33px" /><br /><br /><br /> </div> </asp:Content>

MEMBER PAGES

Source code of Msterpage.master

<%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs" Inherits="MasterPage" %>


<html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title>Untitled Page</title> <link rel="stylesheet" type="text/css" href="style.css" /><script type="text/javascript" src="clockp.js"></script><script type="text/javascript" src="clockh.js"></script> <script type="text/javascript" src="jquery.min.js"></script><script type="text/javascript" src="ddaccordion.js"></script><script type="text/javascript">ddaccordion.init({



onmouseover the header? Valid value: "click", "clickgo", or "mouseover"

95

mouseoverdelay: 200, //if revealtype="mouseover", set delay in milliseconds before header expands onMouseover

collapseprev: true, //Collapse previous content (so only one open at any time)? true/false

defaultexpanded: [], //index of content(s) open by default [index1, index2, etc] [] denotes no content

onemustopen: false, //Specify whether at least one header should be open always (so never all headers closed)

animatedefault: false, //Should contents open by default be animated into view?

persiststate: true, //persist state of opened contents within browser session?

toggleclass: ["", ""], //Two CSS classes to be applied to the header when it's collapsed and expanded, respectively ["class1", "class2"]






}})</script>

<script type="text/javascript" src="jconfirmaction.jquery.js"></script><script type="text/javascript">


});

</script>

<script language="javascript" type="text/javascript" src="niceforms.js"></script><link rel="stylesheet" type="text/css" media="all" href="niceforms-default.css" /> <style type="text/css"> .search_submit { height: 24px; width: 28px; } </style></head><body> <form id="form1" runat="server"> <div style="height: 135px"> 

96

<div id="main_container">

<div class="header"> <div class="logo"><a href="#"><img src="images/logo.gif" alt="" title="" border="0" /></a></div> <div class="right_header" style="font-style:italic; font-size:medium; color:Aqua; height: 15px;">Welcome ,<asp:Label ID="Label1" runat="server"></asp:Label> <a href="profile.aspx">PROFILE</a>

<asp:LinkButton ID="LinkButton1" runat="server" onclick="LinkButton1_Click">LOGOUT</asp:LinkButton> <%-- <asp:LoginStatus ID="LoginStatus1" runat="server" LogoutPageUrl="~/login.aspx" Font-Size="Medium" ForeColor="Aqua" LoginText="LOGIN" LogoutText="LOGOUT" />--%> </div> <div id="clock_a"></div> </div> <div class="main_content"> <div class="menu"> <ul> <li><a class="current" href="#">HOME</a></li> <li><a class="current" href="#">About Us</a>   </li> <li><a href="#">Edit</a>  <ul> <li><a href="setting.aspx" title="">Setting</a></li> </ul>  </li> <li><a class="current" href="query.aspx">QUERY</a></li> <li><a class="current" href="feedback.aspx">FEEDBACK</a></li> </ul> </div> <div class="center_content"> <div class="left_content"> <div class="sidebar_search" style="float:left"> <input type="text" name="" class="search_input" value="search keyword" onclick="this.value=''" />

97

<a href="search.aspx" runat="server"><img src="images/search.png" style="height: 33px; width: 35px"/></a> </div> <br /><br /><br /><br /> <div class="sidebarmenu"> <a class="menuitem" href="inbox.aspx">INBOX</a> <a class="menuitem" href="composemail.aspx">COMPOSE MAIL</a> <a class="menuitem" href="draft.aspx">DRAFT</a> <a class="menuitem" href="trash.aspx">TRASH</a> <a class="menuitem" href="sentitems.aspx">SENT MAILS</a> <a class="menuitem" href="chat.aspx" >CHAT</a> <%--<div class="submenu"> <ul> <li><a href="#">Sidebar submenu</a></li> <li><a href="#">Sidebar submenu</a></li> <li><a href="#">Sidebar submenu</a></li> <li><a href="#">Sidebar submenu</a></li> </ul> </div>--%> </div> </div> <div class="right_content"> <br /> <span class="bt_green_lft"> <asp:ContentPlaceHolder ID="ContentPlaceHolder1" runat="server"> </asp:ContentPlaceHolder> </span> </div> </div>  </div>  </div>

<br /> <br /> <br /> </div> </form>

98

</body></html>

Source code of login.aspx

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="login.aspx.cs" Inherits="login" %>


<html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title>Untitled Page</title> <link rel="stylesheet" type="text/css" href="style.css" /><script type="text/javascript" src="jquery.min.js"></script><script type="text/javascript" src="ddaccordion.js"></script><script type="text/javascript">ddaccordion.init({
















99

}})</script>



});

</script>

<script language="javascript" type="text/javascript" src="niceforms.js"></script><link rel="stylesheet" type="text/css" media="all" href="niceforms-default.css" />

</head><body> <form id="form1" runat="server"> <div> 

<br />                                                     <br /> <div id="Div1" runat="server" style="float:right; height: 99px;"> <img id="Img1" runat="server" src="~/images/animated119.gif" style="height: 99px" /> </div> <br /> <br /> <br /> <br /> <div> <center style="height: 156px">          <br /> <br /> <br /> <br />                                                          &nbs

100

p;                                                                                                                                                        <a href="newuser.aspx"><font color="yellow"face="comic sans ms" size="large" style="font-size: x-large">CREATE ACCOUNT ??? </font></a> <br />                                                                                                                                                                                                             <a href="forgetpassword.aspx"><font color="yellow"face="comic sans ms" size="large" style="font-size: x-large">Forget Password?</font></a>     <br /> <br /> </center> </div> <div style="height: 241px; width: 704px"> <%--<asp:Login ID="Login1" runat="server" onloggedin="BTN_SUBMIT_Click" > <LayoutTemplate> --%>                                                  &nb

101

sp;                        <asp:Label ID="lblheading" runat="server" BackColor="Yellow" Font-Bold="True" Font-Names="Comic Sans MS" Font-Size="X-Large" Height="34px" style="margin-left: 0px" Text=" LOG IN" Width="149px"></asp:Label> <br /> <br /> <br />                                                  <asp:Label ID="LBL_UNAME" runat="server" Font-Names="Comic Sans MS" Font-Size="X-Large" ForeColor="White" Text="USERNAME : "></asp:Label>              <asp:TextBox ID="UserName" runat="server" Height="32px" Width="147px"></asp:TextBox>       <asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server" ControlToValidate="UserName" ErrorMessage="ENTER USER NAME" Font-Names="Comic Sans MS" Font-Size="Small" ForeColor="#66FF66"></asp:RequiredFieldValidator> <br /> <br /> <br />                                                  <asp:Label ID="LBL_PASSWORD" runat="server" Font-Names="Comic Sans MS" Font-Size="X-Large" ForeColor="White" Text="PASSWORD :"></asp:Label>                <asp:TextBox ID="Password" runat="server" TextMode="Password" Height="31px" Width="144px"></asp:TextBox>       <asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server" ControlToValidate="Password" ErrorMessage="ENTER PASSWORD" Font-Names="Comic Sans MS" Font-Size="Small" ForeColor="#66FF66"></asp:RequiredFieldValidator> <br /> <br />

102

   <br />                                                                                                                   <asp:Button ID="loginbutton" runat="server" Text="LOG IN" CommandName="Login" Height="36px" ValidationGroup="Login1" Width="87px" onclick="loginbutton_Click" />                    <asp:Label ID="LBL_MSG" runat="server" Font-Names="Comic Sans MS" Font-Size="Medium" ForeColor="Aqua"></asp:Label> <br /> <%--</LayoutTemplate> </asp:Login> --%> </div>             <img src="images/Download-Link-Arrow1.gif" style="margin-top: 5px; height: 104px;" />       <asp:Label ID="Label1" runat="server" Font-Bold="True" Font-Names="Comic Sans MS" Font-Size="XX-Large" ForeColor="#FFFF66" Text="FOR ADMIN LOGIN CLICK BELOW"></asp:Label> <br /> <br />                                      <a href="adminlogin.aspx"> <img src="images/download.jpg" style="width: 131px; height: 140px" /></a>    <br /> <br /> <br /> <br /> <div class="footer_login"> <div class="left_footer_login">IN ADMIN PANEL | Powered by wered by <a href="http://indeziner.com">INDEZINER</a></div>

103

<div class="right_footer_login"><a href="http://indeziner.com"><img src="images/indeziner_logo.gif" alt="" title="" border="0" /></a></div> </div>

 </div> </form></body></html>

Source code of newuser.aspx

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="newuser.aspx.cs" Inherits="newuser" %>














104





}})</script>



});

</script>


</head><body background="images/back1.jpg"> <form id="form1" runat="server"> <div style="height: 770px; width: 1121px;">                                                               <br /> <br /> <br /> <br />                                                           <asp:Label ID="Label1" runat="server" Font-Bold="True" Font-Names="Comic Sans MS" Font-Size="Large" ForeColor="#66FF33" Text="NEW USER CAN REGISTER HERE"></asp:Label> <br /> <br />

105

<asp:Label ID="LBLUSER" runat="server" Font-Names="Comic Sans MS" Font-Size="Medium" ForeColor="Yellow" Text="USER NAME"></asp:Label>                                         <asp:TextBox ID="TXT_USERNAME" runat="server" Font-Size="Medium" Height="28px" Width="187px"></asp:TextBox> <asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server" ControlToValidate="TXT_USERNAME" ErrorMessage="Please enter username !" Font-Names="Comic Sans MS" ForeColor="#66FFFF" SetFocusOnError="True"></asp:RequiredFieldValidator> <br /> <br />                <asp:Label ID="LBL_PASS" runat="server" Font-Names="Comic Sans MS" Font-Size="Medium" ForeColor="Yellow" Text="PASSWORD"></asp:Label>                                           <asp:TextBox ID="TXT_PASS" runat="server" Font-Size="Medium" Height="29px" TextMode="Password" Width="183px"></asp:TextBox> <asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server" ControlToValidate="TXT_PASS" ErrorMessage="Please fill the password" Font-Names="Comic Sans MS" ForeColor="#66FFFF" SetFocusOnError="True"></asp:RequiredFieldValidator> <br /> <br />               <asp:Label ID="LBL_CONFIRMPASS" runat="server" Font-Names="Comic Sans MS" Font-Size="Medium" ForeColor="Yellow" Text="CONFIRM PASSWORD"></asp:Label>               <asp:TextBox ID="TXT_CONFIRMPASS" runat="server" Font-Size="Medium" Height="26px" TextMode="Password" Width="184px"></asp:TextBox> <asp:CompareValidator ID="CompareValidator1" runat="server" ControlToCompare="TXT_PASS" ControlToValidate="TXT_CONFIRMPASS"

106

ErrorMessage="Password should match !!" Font-Names="Comic Sans MS" ForeColor="#66FFFF" SetFocusOnError="True"></asp:CompareValidator> <br /> <br />                <asp:Label ID="LBL_EMAILID" runat="server" Font-Names="Comic Sans MS" Font-Size="Medium" ForeColor="Yellow" Text="EMAIL ID"></asp:Label>                                               <asp:TextBox ID="TXT_EMAILID" runat="server" Font-Size="Medium" Height="27px" Width="184px"></asp:TextBox>      <asp:Label ID="Label2" runat="server" Font-Names="Comic Sans MS" Font-Size="Large" ForeColor="Yellow" Text="@vmail.com"></asp:Label>      <asp:Button ID="BTN_CHECK" runat="server" BackColor="Yellow" Font-Bold="True" Font-Names="Comic Sans MS" Height="28px" onclick="BTN_CHECK_Click" Text="CHECK THE AVAILABILITY" Width="208px" /> <br />                                                                                         <asp:RequiredFieldValidator ID="RequiredFieldValidator3" runat="server" ControlToValidate="TXT_EMAILID" ErrorMessage="Please mention your correct id." Font-Names="Comic Sans MS" ForeColor="#66FFFF" SetFocusOnError="True"></asp:RequiredFieldValidator> <asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server" ControlToValidate="TXT_EMAILID" ErrorMessage="Mention your id in a form [email protected]" Font-Names="Comic Sans MS" ForeColor="#66FFFF" SetFocusOnError="True" ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*"></asp:RegularExpressionValidator> <br />                                   &nb

107

sp;                                                                                                                                           <br />                                                                                         <asp:Label ID="lbl_show" runat="server" Font-Names="Comic Sans MS" Font-Size="Medium" ForeColor="White"></asp:Label> <br /> <br />            <br />               <asp:Label ID="LBL_SQ" runat="server" Font-Names="Comic Sans MS" Font-Size="Medium" ForeColor="Yellow" Text="SECURITY QUESTION"></asp:Label>              <asp:DropDownList ID="DDL_SQ" runat="server" Font-Names="Comic Sans MS" Font-Size="Small" Height="34px" Width="236px" > <asp:ListItem>---SELECT A QUESTION---</asp:ListItem> <asp:ListItem>What town you were born in?</asp:ListItem> <asp:ListItem>what is your best cartoon character?</asp:ListItem> <asp:ListItem>What was your favourite food as a child?</asp:ListItem> <asp:ListItem>who is your favourite author?</asp:ListItem> </asp:DropDownList> <asp:RequiredFieldValidator ID="RequiredFieldValidator4" runat="server" ControlToValidate="DDL_SQ" ErrorMessage="Select a question" Font-Names="Comic Sans MS" ForeColor="#66FFFF" SetFocusOnError="True"></asp:RequiredFieldValidator> <br />

108

<br />                <asp:Label ID="LBL_SA" runat="server" Font-Names="Comic Sans MS" Font-Size="Medium" ForeColor="Yellow" Text="SECURITY ANSWER"></asp:Label>                   <asp:TextBox ID="TXT_SA" runat="server" Font-Size="Medium" Height="29px" Width="183px"></asp:TextBox> <asp:RequiredFieldValidator ID="RequiredFieldValidator5" runat="server" ControlToValidate="TXT_SA" ErrorMessage="You must mention the answer" Font-Names="Comic Sans MS" ForeColor="#66FFFF" SetFocusOnError="True"></asp:RequiredFieldValidator> <br /> <br /> <br /> <br /> <br />                                     <asp:Button ID="BTN_SUBMIT" runat="server" BackColor="Yellow" Font-Names="Comic Sans MS" Font-Size="Medium" onclick="BTN_SUBMIT_Click" Text="SUBMIT" />                         <asp:Button ID="BTN_RESET" runat="server" BackColor="Yellow" Font-Names="Comic Sans MS" Font-Size="Medium" onclick="BTN_RESET_Click" Text="RESET" />                     <asp:Button ID="BTN_CANCIL" runat="server" BackColor="Yellow" Font-Names="Comic Sans MS" Font-Size="Medium" onclick="BTN_CANCIL_Click" Text="CANCIL" /> <br /> <br /> <br />

109

</div> </form> </body></html>

Source code of profile.aspx

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="profile.aspx.cs" Inherits="security_profile" %>














110





}})</script>



});

</script>


<style type="text/css"> .style3 { width: 52px; } .style4 { height: 32px; width: 52px; } .style5 { height: 23px; width: 52px; } .style6 { height: 122px; width: 52px; } .style7 { height: 26px; width: 52px; } </style></head><body> <form id="form1" runat="server"> <div >

111

<table border="0" cellpadding="0" cellspacing="0" style="left: 41px; width: 782px; position: absolute; top: -6px; height: 44px;"> <tr> <td colspan="3" style="height: 24px; text-align: center"> <asp:ValidationSummary ID="ValidationSummary1" runat="server" ShowMessageBox="True" ShowSummary="False" Style="left: 17px; position: absolute; top: 7px" /> <br /> <br /> <br /> <asp:Label ID="Label2" runat="server" Forecolor="Yellow" Height="26px" Style="left: 301px; position: absolute; top: 30px; right: 343px;" Text="Label" Width="138px"></asp:Label>                                                                                                              <a href="inbox.aspx"><img id="Img1" runat="server" src="~/images/home.jpg" style="height: 40px; width: 42px"/></a></tr> <tr> <td colspan="3" style="height: 24px">                                                                       <span style="font-size: 16pt"><strong> <span style="font-size: 24pt; color: #ffff00">ENTER DETAIL                 </span></strong> </span>      <span style="font-size: 16pt; color: #00ffff; background-color: #3300cc;"></span></td> </tr> <tr style="color: #0000cc; font-weight: bold;"> <td style="width: 175px"> <span style=""> <span style="color: Aqua; width: 100%; font-style:italic"> FIRST NAME</span></span></td>

112

<td style="width: 50px; color: #000000;"> <asp:TextBox ID="TxtUName" runat="server"></asp:TextBox> <br /> </td> <td style="font-weight: bold; color: #0000cc" class="style3"> <asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server" ControlToValidate="TxtUName" ErrorMessage="Plz Enter your first name " Width="25px">*</asp:RequiredFieldValidator></td> </tr> <tr style="font-weight: bold; color:Aqua; font-style:italic"> <td style="width: 175px; height: 32px"> <span style="width: 100%"> <br />    LAST NAME</span></td> <td style="width: 50px; height: 32px"> <br /> <asp:TextBox ID="TxtLNAME" runat="server"></asp:TextBox></td> <td style="color: #0000cc; " class="style4"> <asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server" ControlToValidate="TxtLNAME" ErrorMessage="Plz Enter your last name " Width="25px">*</asp:RequiredFieldValidator> <br /> </td> </tr> <br /><br /> <tr> <td style="width: 175px; height: 32px;"> <strong><span style="color:Aqua; font-style:italic; width: 100%;"> ADDRESS</span></strong></td> <td style="width: 50px; height: 32px;"> <asp:TextBox ID="TxtAddress" runat="server"></asp:TextBox> <br /> </td> <td class="style4"> <asp:RequiredFieldValidator ID="RequiredFieldValidator4" runat="server" ControlToValidate="TxtAddress" ErrorMessage="Enter ur address" Width="17px">*</asp:RequiredFieldValidator> <br /> <br /> <br /> </td> </tr> <tr> <td style="width: 175px"> <span style="color: #000000"> <span style="color:Aqua; font-style:italic">

113

<strong style="width: 100%"> PHONE</strong></span></span></td> <td style="width: 50px; color: #000000;"> <asp:TextBox ID="TxtPhone" runat="server"></asp:TextBox>    <br /> </td> <td class="style3"> <asp:RequiredFieldValidator ID="RequiredFieldValidator5" runat="server" ControlToValidate="TxtPhone" ErrorMessage="plz enter phone no">*</asp:RequiredFieldValidator> <asp:RequiredFieldValidator ID="RequiredFieldValidator11" runat="server" ControlToValidate="DropDownList2" ErrorMessage="Plz Select the DOB">*</asp:RequiredFieldValidator> <asp:RequiredFieldValidator ID="RequiredFieldValidator12" runat="server" ControlToValidate="DropDownList3" ErrorMessage="Plz Select the DOB">*</asp:RequiredFieldValidator> <br /> <br /> <br /> </td> </tr> <tr style="color: #000000"> <td style="width: 175px; height: 23px;"> <span style="color: #000000"> <strong><span style="color:Aqua; font-style:italic; width: 100%;"> EMAIL ID</span></strong></span></td> <td style="width: 50px; height: 23px; color: #000000;"> <asp:TextBox ID="TxtEmailId" runat="server"></asp:TextBox>    <div style="z-index: 101; left: 268px; width: 378px; position: absolute; top: 391px; height: 32px"> <asp:DropDownList ID="DropDownList1" runat="server" Width="97px"> </asp:DropDownList> <asp:DropDownList ID="DropDownList2" runat="server" Height="22px" Width="89px"> </asp:DropDownList>   <asp:DropDownList ID="DropDownList3" runat="server" Height="22px" Width="96px" AutoPostBack="True" OnSelectedIndexChanged="DropDownList3_SelectedIndexChanged"> </asp:DropDownList>    <asp:RequiredFieldValidator ID="RequiredFieldValidator9" runat="server" ControlToValidate="DropDownList1" ErrorMessage="Plz Select the DOB">*</asp:RequiredFieldValidator>

114

</div> </td> <td class="style5"> <strong><span style="color: #0000cc"> </span></strong><asp:RequiredFieldValidator ID="RequiredFieldValidator3" runat="server" ControlToValidate="TxtEmailId" ErrorMessage="Enter Emial ID" Width="20px">*</asp:RequiredFieldValidator> <asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server" ControlToValidate="TxtEmailId" ErrorMessage="Invalid Email ID" ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*" Width="16px">*</asp:RegularExpressionValidator></td> </tr> <tr> <td colspan="3" style="height: 35px"> <strong>  <span style="color:Aqua; font-style:italic; width: 100%;">        <asp:Label ID="Label1" runat="server" Font-Bold="True" Style="left: 43px; position: absolute; top: 392px" Text="DOB:" Width="65px" Forecolor="Aqua"></asp:Label>             </span></strong></td> </tr> <tr style="font-weight: bold; color: #0000cc"> <td colspan="3" style="height: 140px">           <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <span style="color:Aqua; font-style:italic; width: 100%;">YOU HAVE ENTERED    :</span>       <asp:TextBox ID="TxtEnterdDOB" runat="server"></asp:TextBox> </td> </tr> <tr> <td style="width: 175px; height: 122px;">           <strong> <span style="color:Aqua; font-style:italic; width: 100%;">ATTACH IMAGE

115

</span></strong></td> <td style="width: 100%; height: 122%;"> <asp:FileUpload ID="FileUpload1" runat="server" />    <asp:Button ID="Button1" runat="server" Text="Attach" Width="79px" OnClick="Button1_Click" ValidationGroup="a" /> <br />       <br /> <asp:LinkButton ID="LinkButton1" runat="server" Forecolor="aqua" OnClick="LinkButton1_Click" ValidationGroup="a" Width="159px">CHANGE IMAGE</asp:LinkButton></td> <td class="style6"> <asp:Image ID="Image1" runat="server" Height="159px" Width="251px" BorderStyle="Inset" /></td> </tr> <tr> <td style="width: 75%; height: 0%;"> </td> <td style="width: 50%; height: 26%;"> <br /> <br /> <asp:Button ID="Button2" runat="server" OnClick="Button2_Click" Text="SUBMIT" Width="66px" BorderColor="Olive" BorderStyle="Inset" /> <asp:Button ID="Button3" runat="server" Text="CLEAR" Width="65px" OnClick="Button3_Click" BorderColor="Olive" BorderStyle="Inset" /><br /> <br />   </td> <td class="style7"> </td> </tr> </table> </div> </form></body></html>

Source code of inbox.aspx

116

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="inbox.aspx.cs" Inherits="security_inbox" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="false" onrowcommand="GridView1_RowCommand1" Height="235px" Width="522px" BackColor="#FFFF99"> <Columns> <asp:TemplateField> <ItemTemplate> <asp:CheckBox ID="Chk" runat="server" /> <asp:HiddenField ID="HiddenField1" runat="server" Value='<%#Eval("s_no") %>' /> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="sender"> <ItemTemplate> <%#Eval("sender") %> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="subject"> <ItemTemplate> <asp:LinkButton ID="lnkSub" runat="server" Text='<%#Eval("subject") %>' CommandName="view" CommandArgument='<%#Eval("s_no") %>'></asp:LinkButton> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="attachment"> <ItemTemplate> <%#Eval("attachment") %> </ItemTemplate> </asp:TemplateField> </Columns> </asp:GridView><center><asp:Button ID="Button1" runat="server" Text="delete" onclick="Button1_Click" /></center>

</asp:Content>

Source code of sentitems.aspx

117

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="sentitems.aspx.cs" Inherits="security_sentitems" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="false" onrowcommand="GridView1_RowCommand" Height="298px" Width="612px" BackColor="#FFFF99"> <Columns> <asp:TemplateField> <ItemTemplate> <asp:CheckBox ID="Chk" runat="server" /> <asp:HiddenField ID="HiddenField1" runat="server" Value='<%#Eval("s_no") %>'/> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="sent to"> <ItemTemplate> <%#Eval("rec") %> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="subject"> <ItemTemplate> <asp:LinkButton ID="linkbutton" runat="server" Text='<%#Eval("subject") %>' CommandName="view1" CommandArgument='<%#Eval("s_no") %>'></asp:LinkButton> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="attachment"> <ItemTemplate> <%#Eval("attachment") %> </ItemTemplate> </asp:TemplateField> </Columns> </asp:GridView> <center> <asp:Button ID="Button1" runat="server" Text="delete" onclick="Button1_Click" /> </center></asp:Content>

Source code of composemail.aspx

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="composemail.aspx.cs" Inherits="security_composemail" Title="Untitled Page" %>

118

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <font color="aqua" size=4 face="comic sans ms">To :</font>                        : <asp:TextBox ID="TextBox1" runat="server" ></asp:TextBox> <br /> <font color="aqua" size=4 face="comic sans ms">Subject :</font>            <asp:TextBox ID="TextBox2" runat="server"></asp:TextBox> <br /> <font color="aqua" size=4 face="comic sans ms">Attachment:</font>   <asp:FileUpload ID="FileUpload1" runat="server" /> <br /> <br /> <font color="aqua" size=4 face="comic sans ms">Body :</font><br />        <asp:TextBox ID="TextBox3" runat="server" Height="213px" Width="286px"></asp:TextBox> <p>          <asp:Button ID="Button1" runat="server" Text="send" onclick="Button1_Click" BackColor="Aqua" Font-Bold="True" Font-Names="Comic Sans MS" Height="28px" Width="50px" />             <asp:Button ID="Button3" runat="server" Text="save" onclick="Button3_Click" BackColor="Aqua" Font-Bold="True" Font-Names="Comic Sans MS" Height="28px" Width="54px" />             <asp:Button ID="Button2" runat="server" Text="cancel" onclick="Button2_Click" BackColor="Aqua" Font-Bold="True" Font-Names="Comic Sans MS" /> </p></asp:Content>

Source code of draft.aspx

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="draft.aspx.cs" Inherits="security_draft" Title="Untitled Page" %>

119

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="false" onrowcommand="GridView1_RowCommand" BackColor="#FFFF99" Height="290px" Width="510px"> <Columns> <asp:TemplateField> <ItemTemplate> <asp:CheckBox ID="Chk" runat="server" /> <asp:HiddenField ID="HiddenField1" runat="server" Value='<%#Eval("s_no") %>' /> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="sender"> <ItemTemplate> <%#Eval("sender") %> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="subject"> <ItemTemplate> <asp:LinkButton ID="lnkSub" runat="server" Text='<%#Eval("subject") %>' CommandName="view" CommandArgument='<%#Eval("s_no") %>'></asp:LinkButton> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="attachment"> <ItemTemplate> <%#Eval("attachment") %> </ItemTemplate> </asp:TemplateField> </Columns> </asp:GridView> <asp:Button ID="Button1" runat="server" Text="delete" onclick="Button1_Click" /></asp:Content>

Source code of trash.aspx

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="trash.aspx.cs" Inherits="security_trash" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">

120

<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="false" onrowcommand="GridView1_RowCommand" Height="176px" Width="476px"> <Columns> <asp:TemplateField> <ItemTemplate> <asp:CheckBox ID="Chk1" runat="server" /> <asp:HiddenField ID="HiddenField1" runat="server" Value='<%#Eval("m_id") %>' /> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="sender"> <ItemTemplate> <%#Eval("sender") %> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="subject"> <ItemTemplate> <asp:LinkButton ID="lnkSub" runat="server" Text='<%#Eval("subject") %>' CommandName="view" CommandArgument='<%#Eval("m_id") %>'></asp:LinkButton> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="attachment"> <ItemTemplate> <%#Eval("attachment") %> </ItemTemplate> </asp:TemplateField> </Columns> </asp:GridView> <asp:GridView ID="GridView2" runat="server" AutoGenerateColumns="false" onrowcommand="GridView2_RowCommand" Height="206px" Width="476px"> <Columns> <asp:TemplateField> <ItemTemplate> <asp:CheckBox ID="Chk2" runat="server" /> <asp:HiddenField ID="HiddenField2" runat="server" Value='<%#Eval("m_id") %>' /> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="sender"> <ItemTemplate> <%#Eval("sender") %> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="subject">

121

<ItemTemplate> <asp:LinkButton ID="lnkSub2" runat="server" Text='<%#Eval("subject") %>' CommandName="view" CommandArgument='<%#Eval("m_id") %>'></asp:LinkButton> </ItemTemplate> </asp:TemplateField> <asp:TemplateField HeaderText="attachment"> <ItemTemplate> <%#Eval("attachment") %> </ItemTemplate> </asp:TemplateField> </Columns> </asp:GridView> <center> <asp:Button ID="Button1" runat="server" Text="delete" onclick="Button1_Click" /> </center></asp:Content>

Source code of viewmail.aspx

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="viewmail.aspx.cs" Inherits="security_viewmail" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"><asp:Label ID="Label1" runat="server" Text=""></asp:Label></asp:Content>

Source code of afterregister

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="afterregister.aspx.cs" Inherits="security_afterregister" %>


<html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title>Untitled Page</title> <link rel="stylesheet" type="text/css" href="style.css" /><script type="text/javascript" src="jquery.min.js"></script><script type="text/javascript" src="ddaccordion.js"></script><script type="text/javascript">

122

ddaccordion.init({headerclass: "submenuheader", //Shared CSS class name of headers

groupcontentclass: "submenu", //Shared CSS class name of contents grouprevealtype: "click", //Reveal content when user clicks or














}})</script>



});

</script>


</head><body> <form id="form1" runat="server"> <div>

123

<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br />                 <asp:Label ID="lbl_ermsg" runat="server" Font-Names="Comic Sans MS" Font-Size="Larger" ForeColor="#FF99CC" Text="REGISTRATION SUCCESSFULLY COMPLETED !!!!!"></asp:Label> <br /> <br />                                                     <asp:Label ID="Label1" runat="server" Font-Names="Comic Sans MS" Font-Size="Larger" ForeColor="#FF99CC" Text="CLICK HERE TO CONTINUE..."></asp:Label> <br /> <br />                                                                                                                    <br />

124

<asp:Button ID="btn_conti" runat="server" BackColor="#FF99CC" Font-Bold="False" Font-Names="Comic Sans MS" Font-Size="Medium" Height="39px" Text="CONTINUE" Width="133px" onclick="btn_conti_Click" /> <br /> <br /> </div> </form></body></html>

Source code of default.aspx

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="security_Default" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"></asp:Content>

Source code of query.aspx

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="query.aspx.cs" Inherits="query" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <table style="height: 468px; width: 651px"> <tr> <td style="width: 141px; height: 26px" align="right"> <font face="comic sans ms" size=4 color="aqua">SALUTATION :</font></td> <td style="width: 130px; height: 26px" align="left"> <asp:DropDownList ID="DdlSalutation" runat="server" AutoPostBack="True"> <asp:ListItem>Mr</asp:ListItem> <asp:ListItem>Miss</asp:ListItem> <asp:ListItem>Mrs</asp:ListItem> </asp:DropDownList></td> <td style="width: 113px; height: 26px"> </td> <td style="width: 113px; height: 26px"> </td> </tr> <tr>

125

<td style="width:141px; height: 26px;" align="right"> <font face="comic sans ms" size=4 color="aqua">NAME :</font></td> <td style="width:130px ; height: 26px;" align="left"> <asp:TextBox ID="TxtName" runat="server"></asp:TextBox><font color="red"><b>*</b></font></td> <td style="width: 113px; height: 26px;"> <asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server" ControlToValidate="TxtName" ErrorMessage="RequiredFieldValidator">Please Mention Your Name</asp:RequiredFieldValidator></td> <td style="width: 113px; height: 26px"> <asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server" ControlToValidate="TxtEmail" ErrorMessage="RegularExpressionValidator" ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*">Please Enter Correct Email</asp:RegularExpressionValidator></td> </tr> <tr> <td style="width: 141px; height: 21px;" align="right"> <font face="comic sans ms" size=4 color="aqua">EMAIL ID :</font></td> <td style="width: 130px; height: 21px;" align="left"> <asp:TextBox ID="TxtEmail" runat="server" ></asp:TextBox><font color="red"><b>*</b></font> </td> <td style="width: 113px; height: 21px;"> <asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server" ErrorMessage="RequiredFieldValidator" ControlToValidate="TxtEmail">Mention Your Email</asp:RequiredFieldValidator></td> <td style="width: 113px; height: 21px"> </td> </tr> <tr> <td style="width: 141px" align="right"> <font face="comic sans ms" size=4 color="aqua">PHONE NUMBER :</font></td> <td style="width: 130px" align="left"> <asp:TextBox ID="TxtPhone" runat="server"></asp:TextBox></td> <td style="width: 113px"> <font face="comic sans ms" size=3 color="aqua">(With STD-ISD Code)</font></td> <td style="width: 113px"> </td> </tr> <tr> <td style="width: 141px" align="right"> <font face="comic sans ms" size=4 color="aqua">ADRESS :</font></td> <td style="width: 130px" align="left"> <asp:TextBox ID="TxtAddress" runat="server" TextMode="MultiLine"></asp:TextBox><font color="red"><b>*</b></font></td>

126

<td style="width: 113px"> <asp:RequiredFieldValidator ID="RequiredFieldValidator3" runat="server" ControlToValidate="TxtAddress" ErrorMessage="RequiredFieldValidator" Width="61px">Mention the Address</asp:RequiredFieldValidator></td> <td style="width: 113px"> </td> </tr> <tr> <td style="width: 141px" align="right"> <font face="comic sans ms" size=4 color="aqua">CITY :</font></td> <td style="width: 130px" align="left"> <asp:TextBox ID="TxtCity" runat="server"></asp:TextBox><font color="red"><b>*</b></font></td> <td style="width: 113px"> <asp:RequiredFieldValidator ID="RequiredFieldValidator4" runat="server" ControlToValidate="TxtCity" ErrorMessage="RequiredFieldValidator">Mention the City</asp:RequiredFieldValidator></td> <td style="width: 113px"> </td> </tr> <tr> <td style="width: 141px" align="right"> <font face="comic sans ms" size=4 color="aqua">COUNTRY :</font></td> <td style="width: 130px" align=left> <asp:TextBox ID="TxtCountry" runat="server"></asp:TextBox><font color="red"><b>*</b></font></td> <td style="width: 113px"> <asp:RequiredFieldValidator ID="RequiredFieldValidator5" runat="server" ControlToValidate="TxtCountry" ErrorMessage="RequiredFieldValidator">Mention the Country Name</asp:RequiredFieldValidator></td> <td style="width: 113px"> </td> </tr> <tr> <td style="width: 141px" align="right"> <font face="comic sans ms" size=4 color="aqua">WRITE HERE :</font> </td> <td style="width: 130px" align="left"> <asp:TextBox ID="TxtWrite" runat="server" TextMode="MultiLine"></asp:TextBox><font color="red"><b>*</b></font></td> <td style="width: 113px"> <asp:RequiredFieldValidator ID="RequiredFieldValidator7" runat="server" ControlToValidate="TxtWrite" ErrorMessage="RequiredFieldValidator">Mention your Query!</asp:RequiredFieldValidator></td> <td style="width: 113px"> </td> </tr>

127

<tr> <td style="width: 141px" align="right"> </td> <td style="width: 130px" align="left"> </td> <td style="width: 113px"> </td> <td style="width: 113px"> </td> </tr> <tr> <td colspan="3" style="height: 26px">                                                             <asp:Button ID="BtnSubmit" runat="server" Text="Submit" OnClick="BtnSubmit_Click" />                                                <asp:Button ID="BtnReset" runat="server" Text="Reset" onclick="BtnReset_Click" CausesValidation="False" /> </td> <td colspan="1" style="height: 26px"> </td> </tr> <tr> <td colspan="3" style="height: 26px">                                               <br />                                                        <asp:Label ID="Label1" runat="server" Font-Names="Comic Sans MS" Font-Size="Large" ForeColor="Yellow"></asp:Label></td> <td colspan="1" style="height: 26px"> </td> </tr> </table></asp:Content>

128

Source code of feedback.aspx

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="feedback.aspx.cs" Inherits="feedback" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <br /><br /> <br /><font size="4" face="comic sans ms" color="yellow"><b> Thank you for visiting our website. We are always striving to update our website with the latest information to better meet <br />your needs and would appreciate if you could provide us with <br />some feedback about your experience with our website. </b></font> <br /> <br /> <br /> <center> <asp:RadioButtonList ID="RblFeedback" runat="server" AutoPostBack="True" BackColor="#FFFF99" Font-Bold="True" Font-Size="Larger"> <asp:ListItem>EXCELLENT</asp:ListItem> <asp:ListItem>VERY GOOD</asp:ListItem> <asp:ListItem>GOOD</asp:ListItem> <asp:ListItem>AVERAGE</asp:ListItem> <asp:ListItem>BAD</asp:ListItem> </asp:RadioButtonList> <br /><br />

<br /> <asp:Button ID="BtnSubmit" runat="server" onclick="BtnSubmit_Click" Text="Submit" /><br /> <br /> <br /> <asp:Label ID="Label1" runat="server" Font-Bold="True" ForeColor="#66FFFF" Font-Names="Comic Sans MS" Font-Size="Large"></asp:Label> <br /><br />

<br /> </center></asp:Content>

129

Source code of setting.aspx

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="setting.aspx.cs" Inherits="security_setting" %>


















}})</script>

<script type="text/javascript" src="jconfirmaction.jquery.js"></script>

130

<script type="text/javascript">


});

</script>


</head><body> <form id="form1" runat="server"> <div style="height: 710px; width: 726px;"> <br /> <br /> <br />                                         <asp:Label ID="Label2" runat="server" Font-Bold="True" Font-Names="Comic Sans MS" Font-Size="Larger" ForeColor="#CCFF66" Text="EDIT YOUR PROFILE"></asp:Label> <br /> <br /> <br /> <br />              <asp:Label ID="Label3" runat="server" Font-Bold="True" Font-Names="Comic Sans MS" Font-Size="Large" ForeColor="#CCFF99" Text="1. CHANGE YOUR PROFLIE PICTURE"></asp:Label> <br />                    <br />                   <asp:Button ID="Button2" runat="server" onclick="Button2_Click" Text="Click here to change your profile pic" BackColor="#FFFF99" Font-Names="Comic Sans MS" />    <asp:Image ID="Image1" runat="server" Height="162px" Width="215px" />                                                           <br />

131

             <br />                   <asp:FileUpload ID="FileUpload1" runat="server" /> <br />                     <br />                                        <asp:Button ID="Button3" runat="server" onclick="Button3_Click1" Text="Add" Width="75px" BackColor="#FFFF99" Font-Names="Comic Sans MS" /> <br /> <br /> <br /> <br />             <asp:Label ID="Label4" runat="server" Font-Bold="True" Font-Names="Comic Sans MS" Font-Size="Large" ForeColor="#CCFF99" Text="2. DELETE YOUR ACCOUNT"></asp:Label>          <br /> <br /> <br /> <br />                                     <asp:Button ID="Button4" runat="server" BackColor="#FFFF99" Font-Names="Comic Sans MS" Text="DELETE MY ACCOUNT" onclick="Button4_Click" /> </div> </form><p>      </p></body></html>

Source code of search.aspx

<%@ Page Language="C#" MasterPageFile="MasterPage.master" AutoEventWireup="true" CodeFile="search.aspx.cs" Inherits="security_search" Title="Untitled Page" %>

132

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">

<h1>SEARCH RESULT</h1> <asp:GridView ID="GridView1" runat="server" DataSourceID="SqlDataSource1" BackColor="#FFFF99" Height="182px" Width="319px"> </asp:GridView> <asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$ ConnectionStrings:ConnectionString %>" SelectCommand="SELECT [sender], [rec], [date], [subject], [body], [attachment] FROM [outbox]"> </asp:SqlDataSource></asp:Content>

Source code of chat.aspx

<%@ Page Language="C#" MasterPageFile="~/MasterPage.master" AutoEventWireup="true" CodeFile="chat.aspx.cs" Inherits="chat" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <div> <br />                                     <asp:Label ID="Label2" runat="server" Font-Names="Comic Sans MS" Font-Size="Larger" ForeColor="Yellow" Text="WELCOME TO THE CHAT ROOM"></asp:Label> <br /> <br /> <asp:ScriptManager ID="ScriptManager1" runat="server"> </asp:ScriptManager> <asp:UpdatePanel ID="UpdatePanel1" runat="server"> <ContentTemplate> <asp:ListBox ID="ListBox1" runat="server" Height="250px" Width="243px" ></asp:ListBox> <asp:Timer ID="Timer1" runat="server" Interval="2000" OnTick="Timer1_click"> </asp:Timer> </ContentTemplate> </asp:UpdatePanel> <br /> <asp:TextBox ID="TextBox1" runat="server" Height="38px" Width="293px" ></asp:TextBox> <br /> <br />

133

<asp:Button ID="Button1" runat="server" Text="SEND" OnClick="Button1_CLick" /><br /><br /><br /></div></asp:Content>

Source code of forgetpassword.aspx

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="forgetpassword.aspx.cs" Inherits="forgetpassword" %>


<html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title>Untitled Page</title></head><body bgcolor="green"> <form id="form1" runat="server"> <div> <center><font color="black" size=5 face="comic sans ms">Forget Password</font></center><br /><br /> <asp:Panel ID="Panel1" runat="server">      <font color="black" face="comic sans ms" size="5">Enter User Name:</font>           <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox> <br /> <br />                                                 <asp:Button ID="Button1" runat="server" Text="Submit" onclick="Button1_Click" /> </asp:Panel> <asp:Panel ID="Panel2" runat="server" Visible="false">                  <asp:Label ID="lblSq" runat="server" Text="Label"></asp:Label> <br /> <br /> <font color="black" size=5 face="comic sans ms">Enter Security Answer:</font>    <asp:TextBox ID="TextBox2" runat="server"></asp:TextBox> <br /> <br />                               &nbs

134

p;                <asp:Button ID="Button2" runat="server" Text="Submit" onclick="Button2_Click" /> <br /> <br />          <asp:Label ID="lblAs" runat="server" Text="Label"></asp:Label> </asp:Panel> </div> </form></body></html>

135

3.4 TESTING

System Testing

A software project needs to be tested for judging its viability and performance. Testing is a most time consuming activity but it is vital to the success of new system. During the development phase, programmers also test their programs but generally systematic testing of the program is lacking. Thus this is necessary for programmers to remove syntax and some logical errors of programs during the development phase. A systematic and organized testing of system is a must to ensure the reliability and accuracy of the system. Thus system testing makes a logical assumption that if all parts of the system are correct, the goal will be successfully achieved. Testing of software is done at various levels

White-Box Testing

White-box testing, sometimes called glass-box testing is a test case design method that uses the control structure of the procedural design to derive test case. Using white-box testing method, the software can be derived test cases that:-

Guarantee that all independent paths within a module have been exercised at least once.

Exercise all logical decisions on their true and false sides.

Exercise all loops at their boundaries and within.

Exercise internal data structure to ensure their validity.

Basic Path Testing

The basic path method enables the test case to derive a logical complexity measure of a procedural design and this measure as a guide for defining a basic set of execution paths. Test cases derived to exercise the basic set are guaranteed to execute every statement in the program at least one time during testing.

Conditional Testing

136

Conditional testing is a test case design method that exceeds the logical conditions contained in a program module. The condition testing method focuses on testing each condition in the program. Condition testing strategies have two advantages, first, measurement of test coverage of a condition is simple: second, and the test coverage of condition in a program provides guidance for the generation of additional tests for the coverage of conditions in a program. Purpose of condition testing is to detect not only the errors in the conditions of a program but also other errors in the program. Branch Testing is the simplest condition testing strategy.

Black-Box Testing

Black-box testing is also called behavioral testing, focuses on the functional requirements of the software. That is, black-box testing enables the software engineer to derive sets of input conditions that will fully exercise all functional requirements for the program. Black box testing is not an alternative to white-box techniques. Rather, it is a complementary approach that is likely to uncover a different class of errors than white-box methods.

Black-box testing attempts to find errors in the following categories:

Incorrect or missing function,

Interface errors,

Errors in data structures or external data base access,

Initialization and termination errors.

Unlike white-box testing, which is performance early in the testing process, Black-box testing tends to applied during later stages of testing. By applying Black-box techniques, we derive a set of test cases that satisfy the following criteria:

1. Test cases that reduce, by a count that is greater than one, the number of additional test cases that must be designed reasonable testing.

2. Test cases that tell us something about the presence or absence of errors, rather than an error associated only with the specific test at hand.

137

UNIT TESTING

Unit testing focuses on verification efforts on the smallest unit of software design – the software components or module. Using the components – level design description as a guide, important control paths are tested to uncover errors within the boundary of the module. The unit test is white-box oriented, and the step can be conducted in parallel for multiple components. The module interface is tested to ensure that information properly flows into and out of the program unit under test. The local data structure is examined to ensure that data stored temporarily maintains its integrity during all steps in an algorithm`s execution. Boundary conditions are tested to ensure that the module operates properly at boundaries established to limit or restrict processing. All independent paths through the control structure are exercised to ensure that all statements in a module have been executed at least once. And finally, all errors handling paths are tested.

Unit testing can be performed from the bottom up, starting with smallest and lowest-level modules and proceeding one at a time. For each module in bottom-up testing a short program is used to execute the module and provides the needed data, so that the module is asked to perform the way when embedded within the larger system.

INTEGARTION TESTING

Integration testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested components and built a program structure that has dictated by design. There are two type of integration testing:

a. Top down testing

b. Bottom up testing

VALIDATION TESTING

Software validation is achieved through a serious of black-box tests that demonstrate conformity with requirements. A test plan outlines the classes of tests to be conducted and a test procedure defines specific test cases. Both the plan and procedure are designed to ensure that all functional requirements are satisfied, all behavioral characteristics are achieved, all performance are attained and human-engineered and other requirement are met.

138

SYSTEM TESTING

System testing is actually a series of different tests whose primary purpose is to fully exercise the computer based system. Although each test has a different purpose, all work to verify that system elements have been properly integrated and perform allocated functions. The purpose of system testing is to consider all the likely variation to which it will be subjected and then push the system to its limits. System testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully activated. Another reason for system testing is its utility as a user-oriented vehicle before implementation.

System testing consists of following steps:

Program testing

String testing

Recovery testing

Security testing

Stress testing

Performance testing

These given testing strategies have been used for the project software. It took a lot of time to test every possible condition for the system and the software can be said “Tested OK” up to a reasonable limit. As any software cannot be 100% free, this software is also not an exception and it is possible to find out errors in the future (at the time of application). These errors will be freed whenever it comes. Thus the new system is tested properly at every stage and user accepts it. All the testing results with test data is given in the input output screen format.

139

TEST CASES

Project/System/Component: Login Control Created By: Deepali Jha

Test Case ID: 01 Creation Date:28/11/11

Feature/Function/Requirement to test: Authentication for username and password if a member enters

Data or Activities Required to Test Expected ResultsUsername=deepali password=deepali

Successful

Username=depali password =DEEPALI

Wrong username and password

Username=deepali password=12345

Wrong password

Username=deep password=diipali

Wrong username and password

NEWUSER.ASPX

REQUIRE FIELD VALIDATOR

Project/System/Component: require field validator Created By: Deepali Jha


Feature/Function/Requirement to test: fields should not be empty

Data or Activities Required to Test

(username)Expected Results

Username= (field left empty) Failure

Username=deepali Success

140

NEWUSER.ASPX


Project/System/Component: Require field validator Created By: Deepali Jha




(email )Expected Results

Email= (field left empty) Failure

[email protected] Success

NEWUSER.ASPX

REGULAR EXPRESSION VALIDATOR

Project/System/Component: regular expression validator Created By: Deepali Jha


Feature/Function/Requirement to test: email


(email )Expected Results

Email= deepali.com Failure

[email protected] Success

141

NEWUSER.ASPX






(password)Expected Results

Password= (field left empty) Failure

Password=deepali Success

NEWUSER.ASPX






(confirm password)Expected Results

Confirm Password= (field left empty) Failure

Confirm Password=deepali Success

142

NEWUSER.ASPX

COMPARE VALIDATOR

Project/System/Component: Compare validator Created By: Deepali Jha


Feature/Function/Requirement to test: fields should be same


(password & confirm password)Expected Results

Password= deepali

Confirm password =dipali

Failure

Password=deepali

Confirm password=deepali

Success

NEWUSER.ASPX






(security questions)Expected Results

Security questions= (field left empty) Failure

Security questions: Type a question for password recovery to be used for

future

Success

143

NEWUSER.ASPX






(security answer)Expected Results

Security answer= (field left empty) Failure

Security answer: Type an answer for password recovery to be used for

future

Success

QUERY.ASPX






(name)Expected Results

Name= (field left empty) Failure

Name= Deepali Success

144

QUERY.ASPX






(email id)Expected Results

Email id= (field left empty) Failure

Email [email protected] Success

QUERY.ASPX

REGULAR EXPRESSION

Project/System/Component: Regular expression validator Created By: Deepali Jha


Feature/Function/Requirement to test: email id


(email id)Expected Results

Email = deepali.com Failure

Email = [email protected] Success

145

QUERY.ASPX






(phone)Expected Results

Phone = (field left empty) Failure

Phone= 98112365410 Success

QUERY.ASPX




Feature/Function/Requirement to test: phone


(Phone)Expected Results

Phone = 9812 Failure

Phone =9811234150 Success

QUERY.ASPX

146






(address)Expected Results

Address = (field left empty) Failure

Address = A-1\16, pitam pura Success

QUERY.ASPX






(city)Expected Results

City = (field left empty) Failure

City =Delhi Success

147

QUERY.ASPX






(country)Expected Results

Country = (field left empty) Failure

Country =India Success

QUERY.ASPX






(write here)Expected Results

Write here= (field left empty) Failure

Write here=how to attach a file Success

PROFILE.ASPX

148






(First name)Expected Results

First Name= (field left empty) Failure

First Name=Deepali Success

PROFILE.ASPX



Test Case ID:20 Creation Date:28/11/11



(Last name)Expected Results

Last Name= (field left empty) Failure

Last Name=Jha Success

PROFILE.ASPX

149






(Address)Expected Results

Address= (field left empty) Failure

Address= A-1\16,pitam pura Success

PROFILE.ASPX






(phone)Expected Results

Phone = (field left empty) Failure


PROFILE.ASPX

150




Feature/Function/Requirement to test: Email


(Phone)Expected Results

Phone = 9812 Failure


PROFILE.ASPX

REQUIRED FIELD VALIDATOR





(Email)Expected Results

Email = (field left empty) Failure


PROFILE.ASPX

151




Feature/Function/Requirement to test: Email


(Email)Expected Results

Email = deep.com Failure


PROFILE.ASPX

REQUIRED FIELD VALIDATOR





(DOB)Expected Results

DOB= (field left empty) Failure

DOB=13 APRIL 1991 Success

152

Chapter 4

FUTURE

DEVELOPMENT

SUMMARY &

CONCLUSION

153

4 .1 FUTURE DEVELOPMENT OF PROJECT

AS PER USERS REQUIREMENT OUR WHOLE PROGRAM IS DESIGNED. WE CAN ADD AN ADDITIONAL CONSTRAINT TO OUR PROJECT. WE ARE ALSO TRYING TO MAKE THIS PROJECT FOR ONLINE USE, SO THAT CUSTOMER CAN USE THE EMAIL FACILITY.

WE ARE FURTHER ENHANCING AND ADDING THE FOLLOWING MODULES:-

CRYSTAL REPORT

4.2 SUMMARY

The project deals with e-mail which can be sent, received, read and stored easily. One can compose an e-mail on the ‘Compose Mail’ page, send it to any other member of the website, and the mail get stored in the ‘Sent Items’ automatically. The site provides the facility to attach any file along with the mail, and send it to the destination. Mails received are as well stored in the ‘Inbox’ and can be read or deleted any time. The deleted mails are automatically moved to the ‘Trash’, where they can be permanently deleted.

“Connecting Mail” is also enhanced with an additional feature of ‘Group Chatting’, i.e. , all users currently online can chat in a common chat room and send Instant Messages.

The product is implemented with help of ASP.NET web application that extensively uses dot net, SQL, SQL SERVER 2005.

154

4 .3 CONCLUSION

Current status of the project:

The project i.e., Connecting Mail has been completed successfully. Various phases (Requirement analysis, high and slow level design, construction, testing) have been completed.

The project has been underlined and is kept in the vision for the correct functioning.

Technical and managerial Lessons Learnt:

I have learnt to work in the team environment with different task provided to different team members. I am developing the project according to software development life cycle. I have read different phases of SDLC. We have learnt how to make SRS.

The outer things I have learnt, how to create friendly interface, how to plan the work and how to work with different components. For completion of project we had to learn the platform independent language, .net that provides interactive user interface. The main advantage of using .net is that, it is platform independent language which makes it to run on any platform without specified Hardware and Software requirement.

As managerial lessons we have learnt to work with patience, how to co-operate with the team members and how to work in team.

155

Chapter 5

BIBLOGRAPHY

156

5.1 BIBLOGRAPHY

This section gives you the name of the books required for the development of the projects.

NAME OF THE BOOKS AUTHOR NAME

1. Visual studio complete reference 6.0 Noel Jecke

2. Programming in Visual Basic Julie Case Bradley

3. Visual Basic 6.0 Wright Brothers

4. Dot Net tutorial for beginners Rashmi Nair

5. Software Engineering R.K. Aggarwal

6. C# E. Balaguruswamy

7. Database Navathe

SOME WEBSITE LINKS ARE AS FOLLOWS:

• http://www.mail.com/

• http://mail2web.com/

• http://yahoomail.com/

• http://gmail.com/

157

http://gmail.com/

http://yahoomail.com/

http://mail2web.com/

http://www.mail.com/

Date post:	15-Oct-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Chapter 1 INTRODUCTIONdocshare02.docshare.tips/files/8493/84938047.pdf• Over 6,500 employees...

Documents