Final Report

INDEX
CONTENT PAGE NO.

1. Organizational Profile
1.1 History
1.2 Activities
1.3 Organizational structure
1.4 Objectives
2. Proposed System
2.1 Objectives
2.2 Project Definition
2.2.1 Features Of Project
2.3 Project Scope
2.4 Project Platform
2.4.1 Motive of Platform
2.4.2 Advantages Of ASP.NET
2.4.3 Features Of ASP.NET
2.5 Project Summary.
3. Project Manual
3.1 Project Abstract
3.2 Timeline Chart
4.System Analysis
4.1 Problem Definition
4.2 Fact Finding Techniques
4.3 Requirement Analysis
4.4 Feasibility Study
4.4.1Introduction
4.4.2 Operational Feasibility
4.4.3 Technical Feasibility
4.4.4 schedule Feasibility
4.4.5 Economical feasibility
4.4.6 Implementation Feasibility
5.System Design
1
5.1 Software Design Principle
5.2 System flow Diagram
5.3 Data Flow Diagram
5.3.1 context level data flow diagram
5.3.2 first level data flow diagram
5.3.3 second level data flow diagram
5.4 Use case Diagram
5.5 Relationship Diagram
5.6 Sequence Diagram
5.7 Data dictionary
6.Software Development
6.1 H/W & S/W Requirement
6.1.1 H/W requirement
6.1.2 S/W requirement
6.2 User Interface
7. Testing
7.1 S/W Testing
7.1.1 statistical testing
7.1.2 defect testing
7.1.3.1 Black box testing
7.1.3.2 White box testing
7.1.3.3 performance Testing
7.1.3.4 Interface Testing
7.2 Test Cases
8. S/W Implementation
8.1ASP.NET Concept
8.1.1 ASP.NET Framework
8.1.2 What Is ASP.NET?
8.1.3 Features Of ASP.NET.
8.1.4 Advantages Of ASP.NET
8.2 SQL Server 2000.
8.2.1 About SQL server 2000
2
8.2.2 Features Of SQL Server 2000
8.2.3 Advantages Of SQL Server 2000
9.Maintainance
9.1 Introduction
9.1.1 Corrective Maintenance
9.1.2 Adaptive Maintenance
9.1.3 Perfective Maintenance
9.1.4 Preventive Maintenance
10.Conclusion 1. Organizational Profile
10.1 Advantages
10.2 Limitations
10.3 Future Enhancement
11. User Manual
12. Screen Layout
12.1 snapshots
13.BIBLIOGRAPHY
History
Activities
Organizational Structure
Objectives
3
INTRODUCTION OF ORGANIZATION
ABOUT ONGC HAZIRA PLANT:-
1.1 History
4
ONGC’s march towards success from a small beginning in 1956 to one of the largest Exploration
& Production (E&P) company at global levels today,has its relationship with the last man of
the remotest village in many parts of this country.
Hazira Plant, the largest gas-processing complex in the country is designed to process 41
MMSCMD sour natural gas & associated sour condensate. With the commissioning of gas based
LPG Plant (5MMSCMD) in December 1987, the processing capacity build-up was
commissioned in four phases, namely Phase-1, Phase-2, Phase-3, Phase-3A in sept.1988,
October 1990, October 1996 and October 1997 respectively. Kerosene Recovery Unit for value
addition was commissioned in January 1998. The complex, sprawling over an area of approx.
705 hectares is the mother plant for almost all industries at Hazira and enroute HBJ pipeline.
Health, Safety and Environment is the foremost concern with elaborate provision using latest
concept and gadgets for safety, effluent treatment plants and 30% of total land is kept under flora
& fauna.
The state-of-the-art process facilities developed at Hazira Plant and its role in overall national
economy makes it a jewel in the crown of ONGC. The plant has kept pace with the latest
developments in the world to upgrade the technology and safe working practices.
1.2 Activities
Gas Terminal: The sour gas and

condensate received from offshore in a
multiphase flow are separated by gravity
into two streams viz. gas and liquid as a
first step. For this, the fluids coming from
offshore trunk pipelines are routed
through a set of Pressure Reduction
Control system. Then through the cyclone separator the fluids are distributed to Slug Catchers
5
for separation of gas and liquid. The sour gas separated is taken out from top riser pipes to Gas
Sweetening Units and the sour liquid thus collected is routed to Condensate Fractionation Units.
Gas Sweetening Unit: The purpose is to

remove lethal H2S from sour gas. Sour Gas from
Slug Catcher is distributed to different GSU trains,
which comes in counter-current contact with lean
amine solution in Absorption Column. The sweet
gas leaves from the top of the column with 4 ppm
H2S which is routed to GDU/LPG units. The rich
amine enters the regenerator column for regenerating and re-circulation in the system. Acid gas,
liberated from top of the regenerator column during recycling of MDEA forms feed for Sulphur
Recovery Unit.
Gas Dehydration Unit:
The unit aims at removal of water vapors from sweetened gas from GSU. The sweet gas comes
in counter-current contact with lean Tri-Ethylene Glycol (TEG) solution in Absorption column.
The dry gas liberated from top of the Absorber forms feed for Dew Point Depression Unit. The
rich TEG (containing water vapors) is sent to Reboiler & Regenerator to remove moisture. The
regenerated TEG is continuously recycled and reused in the system.
Dew Point Depression Unit:
The purpose is to remove hydrocarbon condensate from the sweetened and dehydrated gas by
chilling to avoid hydrate formation in the long distance H-B-J pipeline. The feed gas from GDU
trains is chilled to about (-)5 deg.C in a chiller with the help of propane refrigerant in closed
circulation cycle. The cooled gas condensate is pumped to LPG Plant for distillation. This treated
gas is then sent to GAIL for onward transmission to H-B-J pipeline and partly to local
consumers.
Condensate Fractionation Unit:
This unit aims at removal of H2S and recovery of LPG and

NGL from the sour hydrocarbon condensate separated in the
6
Slug Catcher. The liquid from Slug Catcher is distributed into stripper columns of various CFU
trains. The liquid from stripper bottom is fed to LPG column of recovery of LPG from the top
and NGL from the bottom. The LPG is sent to Caustic wash unit for removal of H 2S. The NGL
forms the feed for KRU.
Caustic Wash Unit:
The LPG from CFU contains up to 20 ppm H 2S which has to be removed to les than the
permissible limit of 4 ppm in CWU before it is sent for storage in Horton spheres. The LPG is
passed through the Absorber (containing caustic solution) and sand filter to wash and remove
H2S. Make-up caustic lye is added for maintaining the quality of solution.
Kerosene Recovery Unit:
NGL produced from CFU is given value addition in KRU by way of producing aromatic rich
naphtha (ARN), superior kerosene oil (SKO), heavy cut (HC) and/or high-speed diesel (HSD).
The hot NGL is fed to Naphtha Column for distillation from where Naphtha is recovered as a top
product. The bottom stream is fed to the kerosene column through the gas fired furnace for
further fractionation. Kerosene / ATF is recovered from top of the kerosene column and
HSD/Heavy Cut is recovered from the bottom. A suitable chemical additive is added in ATF to
maintain electrical conductivity, and storage stabilizer for HSD before these products are sent to
storage.
1.3 Objectives
• Optimize production of hydrocarbons.
• Self-reliance in technology.
• Promoting indigenous effort in Oil & Gas related equipment, material and services.
7
• Assist in conservation of hydrocarbons, more efficient use of energy and development of
alternate source of energy.
• Environment protection.
• Generate adequate resources for reinvestment.
• Develop scientifically oriented and technically competent human resource through

motivation and training.
1.4 Organizational Structure
8
2. Proposed System
Objective
Project Definition
Project Scope
Project Platform
Project Summary
9
2.1 Objective
The main objective of this project is to develop a system (website) through which the
employee of ONGC who are living in colony can do complain and communication with
each other.
• To send complain online through this website.
• To store information about complain.
• To maintain stored information.
• Display the information when user wants.
• To send email to other person through this website.
• To receive the email from other person from this website.
2.2 Project Definition
Online Complain Management & E-mail System, using asp.net, C#.
2.2.1 Features of Project
User does the following Things:
• User can send the complain.

• User can check the status of the complain.
• User can send the mail.
• User can read the mail.
• User can send reply of particular mail.
• User can forward the mail to particular user.
• User can also have facility to send attachment along with its mail.
• User login and logout.
Escalator does the Following Things:

• Check all complains done by user.
• Changes the status of complain.
• Send mail to other escalator.
• Escalate login and logout.
10
Administrator does the Following Things:
• Create and maintain Employee Record.

• Maintain User.
• Create and maintain login record of employee.

• Administer login and logout.
2.3 Project Scope
The main objective of this project is to develop a system (website) through which the employee
of ONGC who are living in colony can do complain and communication with each other.
2.4 Project Platform
Once we confirmed with the definition and got an idea of the software we were required to
develop, we were looking forward to the capabilities of ASP.NET that could be exploited in our
software. we found wide range of facilities provided by ASP.NET that would be of great help
while we progressed further with the project.
2.4.1 Motive of Platform
ASP.NET is a new & powerful server-side technology for creating dynamic web pages. It
comes complete with a wide range of predefined controls ready for you to use, saving your time
& making you more productive. It also relies on a module attached to the web server. However,
the ASP.NET module which is a physical files called aspnet_isapi.dll doesn’t do all of the work
itself; it passes some on to the .NET Framework to do the processing for it.
ASP.NET allows you to use a far greater selection of full programming languages & also allows
you to utilize to the full the rich potential of the .NET Framework. It helps you to create faster,
more reliable dynamic web pages with any of the programming languages supported by the
.NET Framework.
Within your application ASP.NET allows you to customize pages for a particular user, keep
track of user’s details as they move through a website & store information about them in a
database of self-describing XML file. You can alter the layout of pages at the click of the button,
add & remove files from your machines & even draw on the logic of other applications without
having to download them first.
Technically speaking, aspnet_isapi.dll module parses the contents of the ASPX file- it breaks
them down into separate commands in order to establish the overall structure of our code.
11
Having done this, it arranges the commands within a pre-defined class definition- not necessarily
together & not necessarily in the order in which we wrote them. That class is then used to define
a special ASP.NET Page object, & one of the tasks this object then performs is to generate a
stream of HTML, that can be sent back to IIS, & from here, back to the client.
2.4.2 Advantages of ASP.NET

• Better language support
• Programmable Controls
• Event-driven Programming
• XML-based components
• User authentication, with accounts and roles
• Higher Scalability
• Increased performance – Complied code
• Easier configuration and deployment
• Not fully ASP compatible
• ASP.Net used the new ADO.Net
• Data Grid control that can act as a Data set Control
• Objects on a web page expose events that can be processed by ASP.Net
code.
2.4.3 Feature of ASP.NET
There are many benefits of ASP .NET that makes it one of the most powerful tools
available for developing web applications. Here are some benefits.
• Developer Productivity:-
ASP .NET helps the developers to deliver real world web applications in record time.
• Easy Programming Model

• Flexible Language Options
• Great Tool Support
• Rich Class Framework
• Improved Performance and Scalability:-

ASP .NET serves users with the same hardware.
• Compiled Execution
• Rich Output Caching
12
• Enhanced Reliability:-
ASP .NET ensures that application is always available to users.
• Memory Leak, Deadlock and Crash Protection.

• Easy Deployment:-
ASP .NET takes the pain out of deploying server applications.
• “No touch” application deployment

• Dynamic update of running application
• Easy Migration Path
• New Application Models:-

ASP .NET extends application’s reach to new customers and partners.
• XML web services

• Mobile Web Device Support
• ASP to ASP .NET:-

The Migration from ASP to ASP.NET is painless and because of the new programming
model. To understand AS .NET’s features, it helps to understand ASP’s limitations.
• Scripting limitations:-
In ASP application rely on VBScript, developers usually need to add separately
developed components, which add a new layer of complexity. In ASP .NET, web pages
are designed in a modern .NET language, not a scripting language.
• No application structure:-
ASP code is inserted directly into a web page along with HTML mark up. The resulting
tangle has nothing in common with today’s modern, object-oriented languages. As a
result, web form code can rarely be reused or modified without hours of effort.
• State limitation:-
One of ASP’s strongest features is its integrated session state facility. However, session
state is useless in scenario where a web site is hosted by several separate web servers.
ASP .NET corrects this problem by allowing state to be stored in a central repository:
either a separate process or a database that all servers can access.
• Database Management System (DBMS):-
DBMS can be defined as a collection of interrelated data and a set of programs to access,
modify and maintain the data. This collect of data is called Database. To put it simply, a
database is just an organized collection of information – with emphasis on organized.
• Desirable Database Characteristics:-
13
There are many ideas about what a database is and what it should do. Microsoft SQL
Server has all characteristics, which are given below:
 Sufficient Capacity:-
A database’s primary function is to storage large amounts of information. A company
wants to keep historical (archival) data will require even more storage space. The need
for storage capacity is growing rapidly, and databases provide for structured storage.
 Adequate Security:-
Enterprise data is valuable and must be stored safely. That means protection of the stored
data not only from malicious or careless human activities, but also from hardware failures
and natural disasters.
 Multi-user Environment:-
The information stored in a database must be accessible to many users simultaneously at
different levels of security and no matter what, the data must stay consistent. Also,
certain groups of users may be allowed modify several pieces of information, browse
other parts of it, and be prevented from even viewing yet another part.
 Effectiveness:-
Users need quick access to the data they want. The response to someone’s querying the
database must be fast, preferably instantaneous.
 Scalability:-
Databases must be flexible and easily adaptable to changing needs. That primarily
means that the internal structure of database objects should be easily modified with
minimum impact on other objects and processes.
 User-friendliness:-
Databases are not just programmers and technical personnel. Non-technical users
constitute the majority of all database users nowadays. Accountants, managers,
salespeople, doctors, customer service representatives – for all these and many more
people, interaction with databases are integral part of their work. That means data must
14
be easy to manipulate. Of course, most users will access it through a graphical user
interface with a predefined set of screens and limited functionality, but ad hoc database
queries and reports become more and more popular, especially among sophisticated,
computer-literate users.
2.5 Project Summary

Project Title:-
“Online Complain Management & E-mail System”
Front-End Tool:-
ASP.NET 2.0 with C#
Back-End Tools:-
Microsoft Access 2007,
SQL server 2000.
Documentation Tools:-
Microsoft Office XP
Project Duration:-
4 Months (From 15th January 2010 to 7th May 2010)
External Project Guide:-

Mr. Irshad Ahmad, manager (programming), ONGC, Hazira Plant, Surat
Internal Project Guide:-

Mr.M.K.Patel, lecturer, CE Department, L.C.I.T, Bhandu.
Organization:-
Oil and Natural Gas Corporation Limited, Hazira Plant, Surat
Project Team:-
15
Consist of two members,
8th semester student of B.E.C.E
North Gujarat University.
3. Project Management
Project Abstract
Timeline Chart
16
3.1 Project Abstract
• Definition:-
“Online Complain Management & E-mail System”
Register Complain and Send & Receive Email is the main function of this application. In
this Application, employee of ONGC who are living in colony can Register complain
Our Application provides online availability to register complain as per requirement of

employee. Employees can also check the status of complain. They can do email to others
and receive email from others. They can also attach file to their email.
In Our Application we provide facility like send and receive mail from others. Escalators
who solve complain has a facility so they can change the status of particular complain
online. There are three levels of complain. If complain is solved by level one’s escalator
then they send a massage of completion of complain to the next level of escalator. If
complain is not solved by escalator of level one then they forward complain to next level
and same for the third.
In this application user can send and receive mail from others. They can answer the mail
they receive. They can attach file to the mail and send to others. They can check all mails
from inbox.
17
3.2 TimeLine Chart
When creating a software project scheduling, the planner begins with a set of tasks. If automated
tools are used, the work breakdown is input as a task network. Effort, duration and start date are
then input for each task. In addition, tasks may be assigned to specific individuals.
All projects tasks are listed in the left hand column. The horizontal bars indicate the duration of
each task. When multiple bars occur at the same time on the calendar, task concurrency is
implied. The diamonds indicate milestones, which indicate the place where our project reach.
TASK MONTH1 MONTH2 MONTH3 MONTH4
1.1 Identify needs &

benefits
Identify needs & project
constraints
Establish project statement
Milestone: Project scope

defined
1.2 Assess Risks

Project risks
Technical risks
1.3 Define desired

input/output/control
Personal profile
Conformation of registration
18
Selection of services
Define the budget for each

Service
Total estimate
Confirmation of payment
1.4 Research
For database management
For Client/Server Software
For form designing
Milestone: Technologies
identified
1.5 Define the function

and behavior
Static pages about information
Forms for personal profile
Form for registration
Forms for selection of services &

its budget
Forms for estimates & payment
Review OCI definition
Revise OCI as required
Milestone: OCI definition

complete
1.6 Merger of software

elements
Milestone: Software Combined
WORK TASK PLANNED ACTUAL PLANNED ACTUAL
19
START START COMPLETE COMPLETE
1.1 Identify needs & benefits
Identify needs & project constraints M1,D1 M1,D1 M1,D3 M1,D3
Establish project statement M1,D4 M1,D4 M1,D7 M1,D7
Milestone: Project scope defined
1.2 Assess risks
Project risks M1,D8 M1,D8 M1,D15 M1,D15
Technical risks M1,D8 M1,D8 M1,D15 M1,D15
1.3 Define desired input/output/control
Insertion of data M1,D16 M1,D20 M1,D20 M1,D20
Output of the service M1,D21 M1,D21 M1,D23 M1,D23
Selection of services M1,D24 M1,D24 M1,D27 M1,D27
Define the budget for each service M1,D27 M1,D27 M1,D31 M1,D31
Total estimate M2,D1 M2,D1 M2,D4 M2,D4
Confirmation of payment M2,D5 M2,D5 M2,D7 M2,D7
1.4 Research
For database management M1,D8 M1,D8 M1,D15 M1,D15
For Client/Server Software M1,D8 M1,D8 M1,D15 M1,D15
For form designing M1,D12 M1,D12 M1,D15 M1,D15
Milestone: Technologies identified
1.5 Define the function & behavior
Static pages about information M1,D8 M1,D8 M1,D15 M1,D15
Forms for Insertion M1,D21 M1,D21 M1,D23 M1,D23
Form for services M1,D24 M1,D24 M1,D27 M1,D27
Forms for selection of services & its M1,D27 M1,D27 M2,D7 M2,D7
Budget
Forms for estimates & payment M2,D1 M2,D1 M2,D11 M2,D11

20
Review OCI definition M2,D8 M2,D8 M2,D15 M2,D15
Revise OCI as required M2,D11 M2,D11 M2,D18 M2,D18
Milestone: OCI definition complete
1.6 Merger of software elements M1,D1 M1,D1 M3,D30 M3,D30
Milestone: Software Combined M2,D19 M2,D19 M2,D26 M2,D26
1.7 Feasibility check
Technical Feasibility M2,D27 M2,D27 M3,D7 M3,D7
Business Feasibility M2,D27 M2,D27 M3,D3 M3,D3
Milestone: Feasibility assessed
1.8 Make quick estimate of size M3,D8 M3,D8 M3,D12 M3,D12
1.9 Testing & Evaluation M3,D13 M3,D13 M3,D23 M3,D23
1.10 Review the product for changes M3,D24 M3,D24 M3,D31 M3,D31
1.11 Documentation M1,D1 M4,D30 M4,D30 M4,D30
21
4. System Analysis
Problem Definition
Fact Finding Technique
Requirement analysis
Feasibility Study
Process Model
22
4.1 Problem Definition
“Online Complain Management & Email System” using Asp.net (c#) and Microsoft Access
2007.
4.2 Fact Finding Techniques
For getting more information about requirements and for better understanding of problem
definition, we use some fact finding techniques.
• Questionnaire:-
To better understand our project, at first we asked many questions to our guide as
well as to many peoples. From that we got much useful information, and many
key ideas to make our project.
• Information Sources:-
Main sources of information are:
 Use of the system.
 Forms and document used in the organization.
 Procedure manuals and rulebooks, which specify how various

activities, are carried out in the organization.
 Various reports used in the organization.
 Computer programs of existing systems.
4.3 Requirement Analysis

23
The description of the services and the constraints are the requirements of the system
and the processes involved in the requirement engineering are:
 Finding out
 Analyzing
 Documenting and
 Checking these services and constraints
Requirements
definition and
specification
Requiremen
t validation
Domain
understandin Prioritization
g
Process
Entry Requirement Analysis Process
Requirements Conflict
collection Resolution
Requiremen
t
Figure: - Requirement Analysis Process
The process activities are explained as:
Domain Understanding:-
Analysis must develop their understanding of the application domain. We spent some
initial time for the domain understanding, like using the existing forms, understanding the
business processes of the client and finding out the ways of optimizing the operations.
24
In order to understand company’s domain, multiple visits to different company’s sites
were made in order to understand the method of showing their own information on
Internet and understanding the core activities.
• Requirement Collection:-
Over a period of time, questionnaires and one-to-one interviews have proven to be the
best methods for requirement collection.
Following the same approach, the functional specification was prepared based on many
meetings with the Project Guide.
• Classification:-
Requirements are classified as follows:
The main requirements are
 User requirements
 System requirement
Above requirements can be further classified as below.
 Functional requirements
 Non-functional requirements
 Domain Requirements

• Conflict Resolution:-
Here, requirement conflicts are handled so that users can distinguish themselves. Like
some facility may not be used by other user, there must not be any objection from other
users.
• Prioritization:-
Basically map navigation facilities and query results are shown such that user can easily
extract the necessary information.
We developed our project step by step. Our major goal was to develop system for
dynamic scaling. So first we developed module user Blog module then we developed
module for Administrator. So we give priority to our work.
• Requirements Validation:-
25
Requirements validation is concerned with showing that the requirements actually define
the system that customer wants. If this validation is inadequate, errors in the requirements
will be propagated to the system design and implementation.
There are several aspects of the requirements that must be checked:
 Validity:
A user may think that a system is needed to perform certain functions.
However, further thought and analysis may identify additional or different
functions that are required.
 Consistency: Any one requirement should not conflict with any other.
 Completeness: The definition should include all functions and constraints

intended by the system user.
4.4 Feasibility Study
4.4.1 Introduction
One of the main meanings of the feasibility is possibility. Checking of the different criteria for
success is included in feasibility study section. These criteria’s are cost, time, efficiency etc. all
these factors play an important role in achieving objective of the system. That means the system
should be such it gives optimum performance at minimum cost, time and requirements.
A feasibility study is a short, focused study, which aims to answer number of questions:
 Does the system contribute to the overall objectives of the Organization?

 Can the system be implemented using current technology and within given cost
and schedule constraints?
 Can the system be integrated with systems which are already in place?
4.4.2 Operational Feasibility
Operational feasibility measures how well the solution will work in the organization and how
will end-user & management feels about system. Proposed system is helpful for the users. It will
allow them to query them to get the appropriate and adequate information.
26
On studying the operational feasibility of the project, the following conclusions could be derived:
 Developed system will provide the adequate throughput and all necessary
Sid files and Shape files to end-users according to their query.
 It will provide efficient and cost-effective access to up-to-date data.
 If it can be installed within suitable environment, system will do
operations under environment of limited resources.
Thus, it is operationally feasible to develop the proposed system.
4.4.3 Technical Feasibility
Technical feasibility tries to answer the following questions to make the software feasible to
develop.
 The software or tools necessary for building or running the application are
easily available or not?
 The compatibility amongst software exists or not?
 Are developers aware of these technologies?
 What about the alternatives of these chosen technologies?
Factors Considered
 Here we have to consider those tools that are available and the ones that
will be required for developing the project.
 After considering the data processing requirements and the degree of

scalability required by the organization, we have decided to use
ASP.NET as the front end development tool and Microsoft access as the
back end database or the system.
 To support 3-tier structure for efficient service delivery throughout the

organization, an Application Server and a Database Server will be
required.
4.4.4 Schedule Feasibility
Projects are initiated with specific deadline. we need to evaluate whether the deadlines are
mandatory or desirable. Time is the one of the critical factor in the development of any system
but this kind of feasibility is hardly perfect in any system.
27
we have been asked to complete the project within the working days of the organization having
period of 4 months approximately. So we have managed to complete the project before given
deadline. In the project management Chapter we elaborate our ideas to develop the system
within the given period. Please refer to that section for through idea.
Hence, it is feasible to develop a system in predetermined time interval.
4.4.5 Economical Feasibility
Economical Feasibility addresses to the following issues:
 Is the organization having the suitable budget to develop the proposed system?
 How much profit can be earned from the system by an organization?
 Would it be cost-effective to develop the system or it is worthwhile to remain
with current system?
we would like to answer for the above question, as given below:
 As development tools and software are free of cost, there isn’t any burden
of buying them.
 The organization doesn’t having its own software, so it is certainly
required for them.
 The profit will be remarkable according to us as far as customer is
concerned.
So, here we do not need to invest extra funds to develop the system. Thus, it is
economical feasible to the organization.
4.4.6 Implementation Feasibility
Under the study of implementation feasibility, we’ve got to draw the finger to the certain issues,
like:
 Is it possible to install the software within the given environment?
28
 Will organization management and users support for the installation of the
software?
 Will proposed system cause any harm to the operation of the organization?
Operationally, this system can be installed and it can work according to its functionalities. The
management has already approved this software to be developed and it won’t cause any harm to
user’s operation or day-to-day activities.
4.5 Process Model
The Incremental model combines elements of linear sequential model with the iterative
Philosophy of prototyping. The incremental model applies linear sequences in a staggered times
as calendar time progresses.
• Justification for Incremental Model:-
To solve the problem we need the incremental model because in the incremental model We have
the at the first we can’t perform the whole analysis so we have to decompose then in to various
module and for each module we have to perform the analysis design coding and At the end
testing so we thought this strategy will good work. So we decided to use increment model
because each time here the correction can be possible example if first time there may be some
error in analysis then it can be solved in the second increment so to solve. In this problem this
model may work perfectly so we used this model.
• Incremental Model:-
The Incremental Model combines elements of the linear sequential model with the iterative
philosophy of prototyping. The incremental model applies linear sequences in a staged fashion as
calendar time progresses.
Each linear sequence produces a deliverable “increment” of the software. It should be noted that
the process flow for any increment could incorporate the prototyping paradigm.
29
When an incremental model is used, the first increment is often a core product. That is, basic
requirements are addressed, but many supplementary features remain undelivered. The core
product is used by the customer. As a result of use and/or evaluation, a plan is developed for the
next increment. The plan addresses the modification of the core product to better meet the needs
of the customer and the delivery of additional features and functionality. This process is repeated
following the delivery of each increment, until the complete product is produced.
System/Information
Engineering
Increment 1
Delivery of
Analys Design Code Test 1st
is increment
Increment 2
Delivery of
Analys Design Code Test 2nd
is increment
Increment 3
Delivery of
Analys Design Code Test 3rd
is increment
Increment 4
Delivery of
Analys Code Test
Design 4th
is
increment
Time
30
The Incremental process model, like prototyping and other evolution approaches, is iterative in
nature. But unlike prototyping, the incremental model focuses on the delivery of an operational
product with each increment. Early increments are stripped down versions of the final product,
but they do provide capability that serves the user and also provide a platform for evaluation by
the user.
The reason for choosing it as process model for this project is that, since all the requirements are
available at initial stage we can relay on this model for the further step by step implementations
and also the project includes leveling. Therefore, after the complete implementation of 1 st level,
5. model.
we can go for the next easily using this System Design
Software Design Principle
System Flow Diagram
Data Flow Diagram
Use Case Diagram
E-R Diagram
Sequence Diagram
Data Dictionary
31
5.1 System Design Principle
• Introduction:-
System design is a process of preparing of input process and the result detail procedure.
After gathering the facts through various techniques such as questionnaires, interviews,
analysis of documents and observation into all existing system and recording these
collected information in the proper format using DFD’s decision table, flowcharts etc.
The next step is to define the system in terms of user requirements. This is referred to as
logical design and then converted into physical design.
• Logical Design:-
The logical design contains the following information:
 Specification about input data. The source of input data the document from which
it will be derived and the process of data preparation from the documents.
 Specification about output reports the data contains in the reports, its formats and
frequency of generation of report.
 Specification about data to be stored permanently in the system and its format.
32
 Specifications about edit correction, backup procedures and data security
arrangement. Specification about implementation plans. Brief information about
current logical and physical system.
 Brief information about the benefit of the new system, its constraints and required
resources to implement it.
Physical design of system:-

Once the agreements are reached between the user and about the logical design of the
system, the system analysis can start with the physical design of the system. Physical
design of the system means the designing the computer part of the information system.
The physical design of the computer system involves the following aspects.
Stored Data:-
Physical storage of data is on the secondary storage device like floppy disk, hard disk and
Magnetic tapes. The data is stored in the database. A database is a collection of tables.
Table is collection data items organized in the terms of collection of rows. Table contains
the stable information about the entities. When row is added or deleted from a table, table
affected, is said to be updating of table.
In online transaction processing system, the table is updated as soon as transaction occurs
but in a batch processing system table will be updated after transaction performed.
Input and output:-

The major step is the system design is the preparation of input data format and the design
of output repots. The input design is the process of designing the input data in a
computer-based format.
While designing the input, try to produce the cost effective method and to make sure that
it is acceptable to the user and also the accuracy of data is to be achieved because if the
input data entered is not correct, the output will be not correct.
33
When the management accepts the input/output design proposal, the next step to follow is
the design of computer procedures. The analyst has to specify to programmer, the
input/output and processing details that are needed to the design the specifying the
computer procedures. These tools are flowcharts, data flow diagrams etc.
5.2 System flow Diagram
Online Complain Management & Email System
Employee Admi Escalator
Logi Logi Logi

n n n
Vali Vali A Vali

d d d
Home Permission denied Home
Register Check Compose Sent Mail Inbox Address Book Change

Complain Status of Mail Setting
Complain
34
View the sent View the
Insert Send Mail Which received Mail C
View
complain Mail to Mail to which Mail
the
other compose to sends to other
to status our account user
Escalator of
Address Book View Address Book
Display Msg
Insert Change
Address Address Book
Reply Msg Forward Msg contents
Sign out
Admin Insert Insert

Manage Employee Login
Change Detail
Detail Email
Password
Delete
ADD Login
User ADD Employee Send any Detail
Record information
to user
Sign out
Receive Compose Sent Inbox Address Book Change

Complain Mail Mail Setting
35
C
View the
Solve/Forwa Send View the sent received Mail
rd Received Mail to Mail Which which Mail
complain other Mail to sends to other View Address Book
Address Book
compose to user
our account
Insert Change
Address Address Book
Display Msg contents
Reply Msg Forward Msg
Sign out
Change
Password User
Information Group Add Group View Group
Registration User
Update User Add group Insert User in Edit/delete

Information Group User in Group
Sign out
5.3 Data Flow Diagram
36
One of the tools of Structured Analysis is the data flow diagram. A Data Flow Diagram is a
graphical representation of the System. The analyst can use Data Flow Diagram to explain his
understanding about the System.
• Application:-
 Data flow models are an intuitive way of showing how data is processed by a
system.
 At analysis level analyst should be used to model the way in which data is
processed in the existing system.
 Data flow models are used to show how data flows through a sequence of
processing steps.
• Description:-
 A graphical tool used to describe and analyze the movement of data through a
system manual or automated including the process store of data and delays in the
system.
 The transformation of data from input to output through processes may be
described logically and independently of the physical component associated with
system.
 The data transformation at each step before moving on to the next stage. These
processing steps or transformation are programs function when data flow
diagrams are used to document a software design.
 The Symbols that are used in the data flow diagram carry the following meaning:
The Following figure shows the basic symbols used in Data-Flow Diagram:
1. Data Flow: Following symbols is used to show data flow. The data flow is the packet of
data.
37
2. Processes: People, procedures or devices that use or produce data.
3. Source or Destination of Data: These are the entities, which interact with the system
from outside its boundaries.
4. Data Store: Here data are stored or referenced by a process in the system.
5.3.1 Context Level Data Flow Diagram
38
Admin
User Account
Maintenance
0
Online
Complain and E Mail Employee
Email
Employee Solved
Send Mail/Complain Management
Complain
& Receive Mail System
Solve complain &

Send/Receive Mail
Escalate
5.3.2 First level Data Flow Diagram

Address_Book
Add Address 0.12 Add Address

Address
Book
View Complainer
0.11 Send/Forward
Mail_Detail Outbox Mail 39
0.5
Complain
0.10 Send/Forward Mail Info Mgt.
Compos
e
Send/Forward Mail
View Enter
Read
Send/Forward Complain
0.9 Mail 0.6
0.8 Mail Read Inbox Complain
Status of
Mail Status
Complain
Mgt. Info
User
Enter Complain
ID
Enter User 0.7

Info Registratio
Escalator Employee
n
Enter Uid, Pwd and

Role
Read_Mail
User1
0.2
0.1 User 0.4 Send
Logi Account Mail
n Mgt.
User Info Entry
Enter Uid, Pwd and Massage Info

Role Entry
Employee_Detail
0.3
Admin Employe
Employee Info Entry
e Info
Enter Uid, Pwd and Mgt.
Role
5.3.3 Second Level Data Flow Diagram
40
Login:-
Admin Enter Uid, Pwd

User1
0.1.1 Retrieve user info

Employee Enter Uid, Pwd
Login
Escalator Enter Uid, Pwd
User Account Mgt.:-

Access
Admin User Info
0.2.1 Retrieve
Display User Info
User Info
User1
0.2.2
Add/Update/Delete
Validate/
User Info Process
User Info
41
Employee Info Entry Mgt.:-
Access
Admin Employee Info
0.3.1
Retrieve
Display Employee Info
Employe
e Info
Employee_Detail
0.3.2
Add/Update/Delete Validate/
Employee Info Process
Employe
e Info
Send Mail to all Users:-
Admin Read_Mail
0.4.1
Validate/
Send Mail to
Process
all Users
Mail Info
42
Complain Info Entry:-
Employee Complainer
0.5.1
Enter Validate/
Complain Process
Mail Info
Complain Status Info:-

Access
Employee Status Info
0.6.1 Retrieve
Display Status Info
User Info
Retrieve Complainer
Escalator Info
Escalate_Detail
43
New User Registration Info:-
Employee Escalate
0.7.1
Validate/
Enter Process Enter
Registration Info Registration Info
New
User Info
User
Update Complain Status Info:-

Access
Escalate Employee Info
0.8.1
Retrieve
Display Employee Info
Status
Info
Complainer
0.8.2
Update Validate/
Complain status Process
Status
Info
44
Read Mail From Inbox:-
Employee Escalate
0.9.1
Enter Enter
Display
Registration Info Registration Info
Mail Info
Retrieve
Mail Info
Read_Mail
Send/Forward Mail (Compose Mail):-
Employee Escalate
0.10.1
Enter Validate/ Enter
Process Mail Info
Mail Info
Mail Info
Mail_Detail
45
View Mail From Outbox:-
Employee Escalate
0.11.1
Access Access
Display
Mail Info Mail Info
Mail Info
Retrieve
Mail Info
Mail_Detail
Address Book Info:-
Employee Escalate
0.7.1
Validate
Enter friend Address Enter friend
Address Info Address Info
Book
Info
Address_Book
46
5.4 Use Case Diagram
Login
EMPLOY
EE
Manage User
Registration
Entry Add/Update/Del
of new User ete User Info
Register
Complain Use Mail facility
Entry of Send
Compose
Complain Mail to all Users
Mail Send Manage
Mail to Other User Employee Info
ADMIN
Inbox Add/Update/delete
ESCALATOR
Employee Info
View Received
Mail Change
Address Book Password
Add Mail
Address Update
Password
Change Setting
Update
entered Info about
User
Online Complain Management & Email

System – Use Case Diagram
47
5.5 Relation Ship Diagram
48
5.6 Sequence Diagram
Login:-
User
: : Login
: User1
Login Checker
1. Enter Username,
Password
2. Submit Details
3. Get Login Details
and Password
4. Check Login
5. Error or Success
Massage
49
User Account Detail:-
: User :
Admin Detail : Controller User1
Form
1. Enter User
Details 2. Submit the
details
3. Add or Update
the details
4. Successful
added or
updated
5. Enter User code
to be deleted 6. Submit the

User-code 7. Delete details
8. Successful
deletion
50
Employee Details:-
: Employee
:
Admin Detail : Controller Employe
Form e _Detail
1. Enter Employee 2. Submit the

Details details
3. Add or Update
the details
4. Successful
added or
updated
5. Enter Employee
code
6. Submit the
to be deleted Employee-code 7. Delete details
8. Successful
deletion
Send Mail to All Users:-
: Read
: Mail Detail _Detail
Admin : Controller
Form
1. Enter Mail Details
details
3. Add or Update
the details
4. Successful
Mail Send
51
Complain Details:-
: Complain :
Detail Complain
Employee : Controller
er
Form
1. Enter Complain
details
3. Add the details
4. Successful
added or
updated
Complain Status Info:-
:
: Complain ID Complain
Detail : Controller er
Employee
Form Details
1. Enter Complain
2. Submit the
id Details
details
3. Get Status
details
4. Successful
Retrieve
52
Registration Detail:-
: Registration
Employe : User
Detail
e or : Controller Details
Escalate Form
1. Enter
registration 2. Submit the
Details details
3. Add or Update
registration
details
4. Successful
Registration
53
Complain Status change Detail:-
:
: Status Detail Complain
Escalate er
Form : Controller
Details
1. Enter Status
2. Submit the
Details
details
3. Update
Status details
4. Successful Update
54
5.7 Data Dictionary
Data dictionary is repository of data about the system.
Data dictionary is an integer component of structured analysis, since data flow diagrams
by themselves do not fully describe the subject under investigation. Data dictionary
provides the additional information about the system. It is description of all the data used
in the system.
There are 11 tables in our database shown as below:
Table Name: User

Description: This table contains basic information about user
Field Name Data Type Length Validation
UserID varchar 50 Primary key
UserName varchar 50 Not null
First Name varchar 50 Not null
MiddleName varchar 50 Not null
LastName varchar 50 Not null
Address varchar 255 Not null
Range /not
PhoneNo varchar 10 null
ALTEmail varchar 100 Not null
Security varchar 255 Compare

question
55
validator
Compare
Security
answer varchar 50 validator
Table Name: User1

Description: This table contains user password and user security fields.
UserID varchar 50 Primary key
FirstName varchar 50 Not null
Address varchar 255 Not null
PhoneNo varchar 10 Invalid
ALTEmail varchar 100 Not null
Table Name: Group_Master

Description: This table contains group detail.
Groupid int 4 Primary Key
GroupName varchar 50
56
Table Name: Group_User
Description: This table contains information about user contact.
Groupid int 4 Foreign key
GroupName varchar 50
ID int 4
Table Name: Address_Book

Description: This table contains .information about user contact.
UserID varchar 50 Foreign key
FirstName varchar 50 Not null
EmailID varchar 100 Invalid
PhoneNo varchar 10 Invalid
ContactGroup varchar 50
ContctUsername varchar 50
Table Name: Mail_Detail

Description: This table contains information about mail.
Field Name Data Type Leng Validation
th
Primary
UserID varchar 50 Key
MailTo varchar 100
MailFrom varchar 100
57
Cc varchar 100
Bcc varchar 100
Subject varchar 50
Attachment varchar 100
Message text 16
MailDateTim
e smalldatetime 4
MailSize int 4
Table Name: Mail_Detail

Description: This table contains information about mail sent by user.
Field Name Data Type Leng Validation
th
Primary
UserID varchar 50 Key
MailTo varchar 100
MailFrom varchar 100
Cc varchar 100
Bcc varchar 100
Subject varchar 50
Attachment varchar 100
Message text 16
MailDateTim
e smalldatetime 4
MailSize int 4
Table Name: User_Mail

Description: This table contains information about user mail.
58
UserID Varchar 50 Foreign Key
MailID Varchar 50
MailTo Varchar 100
MailFrom Varchar 100
MailRead Varchar 255
MailType Varchar 100
Table Name: Escalate_Detail

Description: This table contains information about Escalate.
escalateid varchar(50) 50 Primary Key
complainid int 4 Foreign Key
escalatedto varchar(50) 50
escalatedate smalldatetime 4
status varchar(50) 50
Table Name: Employee

Description: This table contains information about Employee.
employeeid Varchar 50 Primary Key
name Varchar 50 Foreign Key
address Varchar 255
contactno Varchar 10
birthdate smalldatetime 4
gender Varchar 50
59
mstatus Varchar 50
joindate smalldatetime 4
designation Varchar 50
department varchar 50
Table Name: Complainer

Description: This table contains information about complain.
Field Name6. Software

Data Type Development
Length Validation
complainid int Foreign Key
employeeid Varchar 50
location Varchar 50
complain Varchar 100

detail
dateofcomplai smalldatetime 4
n
ipaddofpc Varchar 50
status varchar 50
Table Name: Complain Detail
Description: This table contains information about complain detail.
Employee id Varchar 5 Primary key

0
H/w &
location S/W requirement
Varchar 5
0
User Interface
complain Varchar 10
detail 0
dateofcompl smalldatetime
ain 4
ipaddofpc Varchar 5
0
60
status varchar 5
0
61
6.1 Hardware and Software Requirement
6.1.1 Hardware Requirement
To get better performance, for our project minimum hardware requirements are as under:
C.P.U : Pentium IV processor
RAM : 256 MB
Hard Disk : 40 GB HDD, Local Area Network (Well Configured)
6.1.2 Software Requirement
To get better performance, for our project minimum software requirements are as under:
Operating System: Microsoft Window XP Service Pack 2
Software Tools: ASP.NET 2.0
Internet Information Service (IIS)
Internet Explorer 6.0 or higher.
Database Tools: Microsoft Access 2003/2007 ,SQL server 2000.
62
6.2 User Interface
Online Complain Management & Email System provides easy user interface. It tries to avoid
ambiguity in interface as much as possible. Also it uses capability of Microsoft operating system
for better user interface. It uses internet explorer to provide good user interface.
63
7. Testing
Software Testing
Test Cases
7.1 Software Testing

64
Involves executing an implementation of the software with test data and examining the outputs
of the software and its operational behavior to check that it is performing as required.
7.1.1 Statistical Testing
Statistical Testing is used to test the program’s performance and reliability and to check how it
works under operational conditions. Tests are designed to reflect the actual user inputs and their
frequency.
The stages involved in the static analysis for this system are follows.
• Control flow analysis:-

 We found many functions which are unreachable during execution, then
for solving this problem we put some extra conditions to make that code
reachable.
 We also found some unconditional branches into loops.
• Data use analysis:-

 We found variables that are used before initialization, Some Variables are
declared but never used, some of them are assigned twice but never used
between assignments, etc.
• Interface analysis:-
 Parameter type mismatches
 Parameter number mismatches
 Non-usage of the results of functions
 Uncalled functions and procedures
65
• Storage management faults:-
 Mails not Stored in Resources
 Out of Bound ->Program’s non-volatile memory
7.1.2 Defect Testing
Intended to find inconsistencies between a program and its specification. These

inconsistencies are usually due to program faults or defects.
7.1.2.1 Black-Box Testing
Black-box testing, also called behavioral testing, focuses on the functional requirements
of the software black-box testing is not an alternative to white-box testing.
Black-box testing attempts to find errors in the following Categories:
 Incorrect or missing function.

 Interface errors.
 Errors in fetching external data.
 Behavior or performance errors.
 Initialization and termination error.
Black-box testing is implementing on our project through test each and every
independent aspx file. For dependent files, we check the dependency and interface after
integrating all the files. For behavior or performance testing we first made demo give it to
our project guide and some employees to use and check performance.
7.1.2.2 White-Box Testing 66

White-box testing, sometimes called glass-box testing, is a test case design that uses the
control structure described as part of component-level design to derive test cases.
As per our project, we have used white Box Testing Model because independent paths of
aspx files and loops are the cornerstones of the vast majority of all algorithms
implemented in the software. There are five different classes of the loops, which can be
defined as follows.
 Simple Loops.
 Nested Loops.
 Concatenated Loops.
 Unstructured Loops.
 Continuous Loops.
As per our project, we have used Simple Loops. The Concatenated loops can be tested
with the different aspx files of the project; all are independent of each other.
7.1.2.3 Performance Testing
Performance testing is designed to test the runtime performance of the system within the
context of the system. These tests were performed as module level as well as system
level. Individual modules were tested for required performance. The performance of the
system was satisfactory. E.g. checking of processing time, operation response time etc.
67
7.1.2.4 Interface Testing
Interface testing is integral part of Integration testing. Therefore we checked for the
 Interface misuse
 Interface misunderstanding
We examined the code to be tested and explicitly list each call to an external component. In
the system, standards tests for GUIs have been performed, which are as follows.
 All menu functions and sub-functions were verified for correctness.

 Validations for all inputs were done.
 Each menu functions were tested, whether it invokes the corresponding
functionality properly.
 All required fields are not left blank.
 All button menus are properly working or not.
 If some buttons are not used in some cases, then making these buttons de-
sensitive.
 Testing Screen display with scrolling window.
 Testing the behavior of drop list input, because new base is created
according to drop list input.
 The position and related labels for all controls were checked.
 Grouping information is displayed appropriately.
 Whether the system prompts the user with appropriate message as and
when invalid information is entered.
68
7.2 Test Cases
Test Case: 1
Test Case ID: Test Case for Login

Section – 1 Section – 2
(Before Execution) (After Execution)
Purpose: Execution History:

Verify user’s login When user enters his Id, password and role,
system checks validity of inputs against
values stored in the database.
Pre Conditions: Results:

Every users must have user id, password (1) If inputs are valid then it displays
the “successful login” message.
(2) If inputs are invalid then it displays
“error message”.
Inputs: If Fail the Possible Reason:
User id, password User has entered invalid Id or password
69
Expected Outputs: Any Other Observation: --
(1) Successful Login
(2) Error Message
Post Conditions: Any Suggestion:

(1) If login is successful then user is If user fails then user may try with valid Id
logged on into the system or password.
(2) If login is not successful then user

will not allowed m.
Test Case: 2
Test Case ID: Test Case for add Employee record

Addition of new record in employee The system request that the admin to enter
database. the employee information, once the admin
provides requested information the
employee is added to the database and
appropriate message is displayed.

Admin must log on to the system before (1) If inputs are valid then it displays the
entry. “employee added successfully” message.
70

Employee id, name, address, contact no, Admin has entered some invalid data.
birthdate.

(1) Addition successfully
(2) Error Message
Post Conditions: Any Suggestion: --

(1) If test case is successful the
employee information is added into
database.
(2) Otherwise error message will be
displayed.
Test Case: 3
Test Case ID: Test Case for delete Employee record

Deletion of record from employee The system request that the admin to enter
database. the employee id, the system retrieve and
display the employee information. The
admin performs deletion. The system
deletes the record from the database.

entry. “employee deleted successfully” message.
71

Employee id Employee with specified id does not exist
in database.

(1) Deletion successfully
(2) Error Message

(1) If test case is successful the If fails, Admin can try with the other id or
employee information is deleted from cancel the operation.
database.
displayed.
Test Case: 4
Test Case ID: Test Case for update employee record

Updation of record in employee database. The system request that the admin to enter
the employee id, the system retrieve and
display the employee information. The data
entry admin makes desired changes. After
updating, system updates employee record
with updated information.

(1) If inputs are valid then it displays the
72
Admin must log on to the system before “employee updated successfully” message.
entry.

Employee id Employee with specified id does not exist
in database.

(1) Updation successfully
(2) Error Message

(1) If test case is successful the If fails, admin can try with the other id or
employee information is updated into cancel the operation.
database.
displayed.
Test Case: 5
Test Case ID: Test Case for delete registered user record

Deletion of record from user database. The system request that the admin to enter
the user name, the system retrieve and
display the user information. The admin
performs deletion. The system deletes the
record from the database.

entry. “user deleted successfully” message.
73

User name User with specified name does not exist in
database.

(1) Deletion successfully
(2) Error Message

(1) If test case is successful the user If fails, admin can try with the other user
information is deleted from database. name or cancel the operation.
displayed.
Test Case: 6
Test Case ID: Test Case for send mail to all user

Send mail to all users in database. The system request that the admin to enter
the mail information, once the admin
provides requested information the mail is
send to all user in database and appropriate
message is displayed.

entry. “mail sent successfully” message.
74

User mail id, subject, message. Admin has entered some invalid data.

(1) Sent mail successfully
(2) Error Message

(1) If test case is successful the mail is
send to all users in database.
displayed.
Test Case: 7
Test Case ID: Test Case for add complain record

Addition of new record in complain The system request that the employee to
database. enter the complain detail information, once
the employee provides requested
information the complain is added to the
database and appropriate message is
displayed.

75
Employee must log on to the system before “complain added successfully” message.
entry.

Employee id, location, complain detail. Employee has entered some invalid data.

(2) Error Message

(1) If test case is successful the
complain is added into database.
displayed.
Test Case: 8
Test Case ID: Test Case for view mail from inbox

View mail from mail database. The system request that the user to enter
the user id and pwd information, once the
user provides requested information the
mail is viewed to user from database and

User must log on to the system before (1) If inputs are valid then it displays the
entry.
76
“view mail successfully” message.

User mail id, password. User has entered some invalid data.

(1) View mail successfully
(2) Error Message

viewed to user from database.
displayed.
Test Case: 9
Test Case ID: Test Case for compose mail

Compose mail from mail database. The system request that the user to enter
the mail id, subject and message
information, once the user provides
requested information the mail is sent to
user from database and appropriate

77
User must log on to the system before
entry.
“send mail successfully” message.

User mail id, subject, message. User has entered some invalid data.

(1) Sent mail successfully
(2) Error Message

sent to user from database.
displayed.
Test Case: 10
Test Case ID: Test Case for view sent mail

View mail from sent database. The system request that the user to enter
the user id, pwd information, once the user
provides requested information the mail is
viewed to user from database and

78
User must log on to the system before
entry.
“view sent mail successfully” message.

User’s user id, password. User has entered some invalid data.

(1) View mail successfully
(2) Error Message

viewed to user from database.
displayed.
Test Case: 11
Test Case ID: Test Case for add address record

Addition of new record in address The system request that the user to enter
database. the address information, once the operator
provides requested information the address
is added to the database and appropriate
79

User must log on to the system before (1) If inputs are valid then it displays the
entry. “user added successfully” message.

Subject firstname, lastname, mailid. User has entered some invalid data.
Expected Outputs:
8. Software Implementation
Any Other Observation: --
(2) Error Message

(1) If test case is successful the address
information is added into database.
displayed.
ASP.NET Concepts
Ms SQL Server 2000
80
8.1 ASP.NET Concepts
81
8.1.1 ASP.NET Framework
Since 1995, Microsoft has been constantly making efforts to shift focus from the Windows
-based platforms to the Internet. Microsoft introduced Active Server Pages (ASP) as an
endeavor toward Internet programming. However, writing ASP script, an interpreted script,
was a traditional way of programming as compared to the existing structured object-oriented
programming. Moreover, it was very difficult to debug and maintain the unstructured ASP
code. Definitely, you could combine the code written in structured object-oriented
languages, such as Visual Basic, with ASP code. However, you could combine the VB code
only as a component. Moreover, the software integration for the Web development was quite
complicated and required an understanding of a host of technologies and integration issues
on the part of the developers. Therefore, an architecture was needed that would allow the
development of Web applications in a more structured and consistent manner.
Recently, Microsoft introduced the .NET Framework with a vision for developers to Create
globally distributed software with Internet functionality and interoperability. The.NET
Framework includes multiple languages, class libraries, and a common execution platform.
In addition, the .NET Framework includes protocols that allow developers to integrate
software over the Internet and the .NET Enterprise Servers, such as SQL Server 2000,
Commerce Server 2000, and BizTalk Server. Thus, the .NET Framework provides the
richest built-in functionality for software integration ever provided by any platform. Also,
with the .NET Framework, developing the Internet applications is as easy as developing
desktop applications.
82
The .NET Framework frees the software developer from most of the operating system
specifics, such as memory management and file handling, because the .NET Framework
covers all the layers of software development above the operating system. Figure describes
the different components of the .NET Framework.
The top layer represents user and program interfaces, and includes Windows Forms, Web
Forms, Web Services, and Application Services. Windows Forms provide a Win32-based
user interface. Web Forms provide a Web-based user interface. Web Services are the most
revolutionary program interfaces because they allow programs to communicate over the
Internet. The Internet-based program interfaces, which include Web Forms and Web
Services, are implemented by ASP.NET, which is a built-in component of the .NET
Framework.
The middle layer represents the .NET Framework classes, which are universally available
across multiple languages. The usage of these classes is consistent across all languages
included in the .NET Framework.
The base layer represents the common execution platform called the Common Language
Runtime (CLR). This is the most important component of the .NET Framework. The
CLR provides support for multiple languages and allows cross language inheritance. For
example, you can inherit a class written in Visual Basic from a class written in Visual C++.
83
Thus, with .NET, the choice of a programming language simply depends on the user's
choice. With .NET, it is possible to create applications by using multiple languages. The
multiple-language support is possible because the CLR provides a common system of data
types. In addition, the CLR performs the memory management and monitors the complete
life cycle of objects, while it tracks objects and handles garbage collection.
Visual Studio .NET (VS.NET) is the first release of the products based on the .NET
Framework. It includes Visual Basic, Visual C++, and C#. VS.NET provides a common
Integrated Development Environment (IDE) for all languages. Therefore, developers always
work in a consistent environment irrespective of the language they use.
With that basic understanding of the .NET Framework, you are ready to look at the basic
features of ASP.NET.
8.1.2 What is ASP.NET?
ASP.NET, the next version of ASP, is a programming framework that is used to create
enterprise-class Web applications. The enterprise-class Web applications are accessible on a
global basis, leading to efficient information management. However, the advantages that
ASP.NET offers make it more than just the next version of ASP.
ASP.NET is integrated with Visual Studio .NET, which provides a GUI designer, a rich
toolbox, and a fully integrated debugger. This allows the development of applications in a
What You See is What You Get (WYSIWYG) manner. Therefore, creating ASP.NET
applications is much simpler.
84
Unlike the ASP runtime, ASP.NET uses the Common Language Runtime (CLR) provided by
the .NET Framework. The CLR is the .NET runtime, which manages the execution of code.
The CLR allows the objects, which are created in different languages, to interact with each
other and hence removes the language barrier. CLR thus makes Web application
In addition to simplifying the designing of Web applications, the .NET CLR offers many
advantages. Some of these advantages are listed as follows
Improved performance:-
The ASP.NET code is a compiled CLR code instead of an interpreted code. The CLR
provides just-in-time compilation, native optimization, and caching. Here, it is important to
note that compilation is a two-stage process in the .NET Framework. First, the code is
compiled into the Microsoft Intermediate Language (MSIL). Then, at the execution time, the
MSIL is compiled into native code. Only the portions of the code that are actually needed
will be compiled into native code. This is called Just in Time compilation. These features
lead to an overall improved performance of ASP.NET applications.
Flexibility:-
The entire .NET class library can be accessed by ASP.NET applications. You can use the
language that best applies to the type of functionality you want to implement, because
ASP.NET is language independent.
Configuration settings:-
The application-level configuration settings are stored in an Extensible Markup Language

(XML) format. The XML format is a hierarchical text format, which is easy to read and
write. This format makes it easy to apply new settings to applications without the aid of any
local administration tools.
85
Security:-
ASP.NET applications are secure and use a set of default authorization and authentication
schemes. However, you can modify these schemes according to the security needs of an
application.
ASP.NET combines unprecedented developer productivity with performance, reliability, and

deployment.
Easy Programming Model:-
ASP.Net makes building real world Web applications dramatically easier. ASP.Net server
controls enable an HTML-like style of declarative programming that let you build great
pages with far less code than with classic ASP. Displaying data, validating user input, and
uploading files are all amazingly easy. Best of all, ASP.Net pages work in all browsers --
including Netscape, Mozilla Firefox and Internet Explorer.
Flexible Language Options:-
ASP.Net lets you leverage your current programming language skills. Unlike classic ASP,
which supports only interpreted VBScript and JScript, ASP.Net now supports more than
25 .Net languages (including built-in support for VB.Net, C#, and JScript.Net -- no tool
required), giving you unprecedented flexibility in your choice of language.
Great Tool Support:-
You can harness the full power of ASP.Net using any text editor -- even Notepad! But
Visual Studio 2005 adds the productivity of Visual Basic-style development to the Web.
Now you can visually design ASP.Net Web Forms using familiar drag-drop-double-click
techniques, and enjoy full-fledged code support including statement completion and color-
86
coding. VS.Net also provides integrated support for debugging and deploying ASP.Net Web
applications. The Professional versions of Visual Studio 2005 deliver life-cycle features to
help organizations plan, analyze, design, build, test, and coordinate teams that develop
ASP.Net Web applications. These include UML class modeling, database modeling
(conceptual, logical, and physical models), testing tools (functional, performance and
scalability), and enterprise frameworks and templates, all available within the integrated
Visual Studio .Net environment.
Rich Class Framework:-
Application features that used to be hard to implement, or required a 3rd-party component,

can now be added in just a few lines of code using the .Net Framework. The .Net
Framework offers over 4500 classes that encapsulate rich functionality like XML, data
access, file upload, regular expressions, image generation, performance monitoring and
logging, transactions, message queuing, SMTP mail, and much more.
Compiled Execution:-
ASP.Net is much faster than classic ASP, while preserving the "just hit save" update model
of ASP. However, no explicit compile step is required! ASP.Net will automatically detect
any changes, dynamically compile the files if needed, and store the compiled results to reuse
for subsequent requests. Dynamic compilation ensures that your application is always up to
date, and compiled execution makes it fast.
Rich output Caching:-
ASP.Net output caching can dramatically improve the performance and scalability of your
application. When output caching is enabled on a page, ASP.Net executes the page just
once, and saves the result in memory in addition to sending it to the user. When another
user requests the same page, ASP.Net serves the cached result from memory without re-
executing the page. Output caching is configurable, and can be used to cache individual
87
regions or an entire page. Output caching can dramatically improve the performance of
data-driven pages by eliminating the need to query the database on every request.
Web-Farm Session State:-
ASP.Net session state lets you share session data user-specific state values across all
machines in your Web farm. Now a user can hit different servers in the web farm over
multiple requests and still have full access to her session. And since business components
created with the .Net Framework are free-threaded, you no longer need to worry about
thread affinity.
8.1.3 Features of ASP.NET
Scripting Limitations:-
Asp application relies on VBscript, which suffers from a number of limitations. To

overcome these problems, developers usually need to add separately developed components,
which add a new layer of complexity. In ASP.Net, web pages are designed in modern .Net
language, not a scripting language.
Headaches with development and configuration:-
Because of the way COM and ASP work, you can’t easily update the components your web
site uses. Often, you need to manually stop and restart the server, which just isn’t practical
on a live web server. Changing configuration option can be just as ugly. ASP.Net introduces
a slew of new features to allow web sites to be dynamically updated and reconfigured.
88
• No application structure:-
ASP code is inserted directly into a web page along with HTML markup. The resulting
tangle has nothing in common with today’s modern, object-oriented languages. As a
result, web form code can rarely be reused or modified without hours of effort.
• State limitations: -
One of Asp’s strongest features is its integrated session state facility. However, session
state is useless in scenario where several separate web server host a web site. In this
scenario, a client might access server A and essentially abandoned. ASP.Net corrects this
problem by allowing state to be stored in a central repository; either a separate process or
a database that all severs can access.
8.1.4 Advantages of ASP.NET
 Better language support

 Programmable Controls
 Event-driven Programming
 XML-based components
 User authentication, with accounts and roles
 Higher Scalability
 Increased performance – Complied code
 Easier configuration and deployment
 Not fully ASP compatible
 ASP.Net used the new ADO.Net
 Data Grid control that can act as a Data set Control
 Objects on a web page expose events that can be processed by ASP.Net
code.
89
8.2 SQl Server 2000
8.2.1 About SQl Server 2000
The database component of Microsoft SQL Server 2000 is a Structured Query Language
(SQL)–based, scalable, relational database with integrated Extensible Markup Language
(XML) support for Internet applications. Each of the following terms describes a
fundamental part of the architecture of the SQL Server 2000 database component:
Database:-
A database is similar to a data file in that it is a storage place for data. Like a data file, a
database does not present information directly to a user; the user runs an application that
accesses data from the database and presents it to the user in an understandable format.
Database systems are more powerful than data files in that data is more highly organized. In
a well-designed database, there are no duplicate pieces of data that the user or application
must update at the same time. Related pieces of data are grouped together in a single
structure or record, and relationships can be defined between these structures and records.
When working with data files, an application must be coded to work with the specific
structure of each data file. In contrast, a database contains a catalog that applications use to
90
determine how data is organized. Generic database applications can use the catalog to
present users with data from different databases dynamically, without being tied to a
specific data format.
A database typically has two main parts: first, the files holding the physical database and
second, the database management system (DBMS) software that applications use to access
data. The DBMS is responsible for enforcing the database structure, including:
• Maintaining relationships between data in the database.

• Ensuring that data is stored correctly and that the rules defining data relationships
are not violated.
• Recovering all data to a point of known consistency in case of system failures.
• Relational Database:-
Although there are different ways to organize data in a database, relational databases are one
of the most effective. Relational database systems are an application of mathematical set
theory to the problem of effectively organizing data. In a relational database, data is
collected into tables (called relations in relational theory).
A table represents some class of objects that are important to an organization. For example,
a company may have a database with a table for employees, another table for customers, and
another for stores. Each table is built of columns and rows (called attributes and tuples in
relational theory). Each column represents some attribute of the object represented by the
table. For example, an Employee table would typically have columns for attributes such as
first name, last name, employee ID, department, pay grade, and job title. Each row
91
represents an instance of the object represented by the table. For example, one row in the
Employee table represents the employee who has employee ID 12345.
When organizing data into tables, you can usually find many different ways to define tables.
Relational database theory defines a process called normalization, which ensures that the set
of tables you define will organize your data effectively.
• Scalable:-
SQL Server 2000 supports having a wide range of users access it at the same time. An
instance of SQL Server 2000 includes the files that make up a set of databases and a copy of
the DBMS software. Applications running on separate computers use a SQL Server 2000
communications component to transmit commands over a network to the SQL Server 2000
instance. When an application connects to an instance of SQL Server 2000, it can reference
any of the databases in that instance that the user is authorized to access. The
communication component also allows communication between an instance of SQL Server
000 and an application running on the same computer. You can run multiple instances of
SQL Server 2000 on a single computer.
SQL Server 2000 is designed to support the traffic of the largest Web sites or enterprise data
processing systems. Instances of SQL Server 2000 running on large, multiprocessor servers
are capable of supporting connections to thousands of users at the same time. The data in
SQL Server tables can be partitioned across multiple servers, so that several multiprocessor
computers can cooperate to support the database processing requirements of extremely large
systems. These groups of database servers are called federations.
Although SQL Server 2000 is designed to work as the data storage engine for thousands of
92
concurrent users who connect over a network, it is also capable of working as a stand-alone
database directly on the same computer as an application. The scalability and ease-of-use
features of SQL Server 2000 allow it to work efficiently on a single computer without
consuming too many resources or requiring administrative work by the stand-alone user.
The same features allow SQL Server 2000 to dynamically acquire the resources required to
support thousands of users, while minimizing database administration and tuning. The SQL
Server 2000 relational database engine dynamically tunes itself to acquire or free the
appropriate computer resources required to support a varying load of users accessing an
instance of SQL Server 2000 at any specific time. The SQL Server 2000 relational database
engine has features to prevent the logical problems that occur if a user tries to read or
modify data currently used by others.
• Structured Query Language:-
To work with data in a database, you have to use a set of commands and statements
(language) defined by the DBMS software. Several different languages can be used with
relational databases; the most common is SQL. The American National Standards Institute
(ANSI) and the International Standards Organization (ISO) define software standards,
including standards for the SQL language. SQL Server 2000 supports the Entry Level of
SQL-92, the SQL standard published by ANSI and ISO in 1992. The dialect of SQL
supported by Microsoft SQL Server is called Transact-SQL (T-SQL). T-SQL is the primary
language used by Microsoft SQL Server applications.
93
Database Architecture:-
Microsoft SQL Server 2000 data is stored in databases. The data in a database is organized
into the logical components visible to users. A database is also physically implemented as
two or more files on disk.
When using a database, you work primarily with the logical components such as tables,
views, procedures, and users. The physical implementation of files is largely transparent.
Typically, only the database administrator needs to work with the physical implementation.
Each instance of SQL Server has four system databases (master, model, tempdb, and msdb)
and one or more user databases. Some organizations have only one user database, containing
all the data for their organization. Some organizations have different databases for each
group in their organization, and sometimes a database used by a single application. For
example, an organization could have one database for sales, one for payroll, one for a
document management application, and so on. Sometimes an application uses only one
database; other applications may access several databases.
It is not necessary to run multiple copies of the SQL Server database engine to allow
multiple users to access the databases on a server. An instance of the SQL Server Standard
or Enterprise Edition is capable of handling thousands of users working in multiple
databases at the same time. Each instance of SQL Server makes all databases in the instance
available to all users that connect to the instance, subject to the defined security
permissions.
When connecting to an instance of SQL Server, your connection is associated with a
particular database on the server. This database is called the current database. You are
94
usually connected to a database defined as your default database by the system
administrator, although you can use connection options in the database APIs to specify
another database. You can switch from one database to another using either the Transact-
SQL USE database name statement, or an API function that changes your current database
context.
SQL Server 2000 allows you to detach databases from an instance of SQL Server, then
reattach them to another instance, or even attach the database back to the same instance. If
you have a SQL Server database file, you can tell SQL Server when you connect to attach
that database file with a specific database name.
8.2.2 Features of SQl Server 2000
The overwhelming majority of databases used on computer systems are relational databases.
Also, server databases such as relational databases on mainframe or minicomputer systems
support the use of Structured Query Language (SQL), as well as proprietary tools for accessing
data.
Two key features of a server database become important because of the client access to data. The
first feature provides a single point of access to the data in the database. The second feature
divides processing and manipulation between the client and server systems.
SQL Server provides several tools that help you manage the system and its databases and tables. You can
use these tools to
95
 Perform the administration of the databases
 Control access to data in the databases
 Control the manipulation of data in the databases
8.2.3 Advantages of SQl Server 2000
 Ease of installation, deployment, and use

SQL Server includes a set of administrative and development tools that improve your
ability to install, deploy, manage, and use SQL Server across several sites.
 Scalability
The same database engine can be used across platforms ranging from laptop computers
running Microsoft Windows® 95/98 to large, multiprocessor servers running Microsoft
Windows NT®, Enterprise Edition.
 Data warehousing
SQL Server includes tools for extracting and analyzing summary data for online
analytical processing (OLAP). SQL Server also includes tools for visually designing
databases and analyzing data using English-based questions.
96
9. Maintenance
Introduction
97
9.1 Introduction
Once you develop a project a duty is not completed. Sometimes the application is unstable. It
still works, but every time a change is attempted, unexpected and serious side effects occur. Yet
the application must continue to evolve.
The maintenance of the existing software can account for over 60 percent of all effort expended
by a development organization, and the percentage continues to rise as more software is
produced. You may ask why so much maintenance is required and why so much effort is
expended. we will try to provide the answer:
“Much of the software we depend on today is on average 10 to 15 years old. Even when these
programs were created using the best design and coding techniques known at the time, they were
created when program size and storage space were principle concerns. They were then migrated
to new platforms, adjusted for changes in machine and operating system technology and
enhanced to meet new user needs--all without enough regard to overall architecture.
The result is the poorly designed structures, poor coding, poor logic and poor documentation of
the software systems we are now called on to keep running…”
98
The ubiquitous nature of change underlies all software work. Change is inevitable when
computer-based systems are built; therefore, we must develop mechanism for evaluating,
controlling and making modifications.
Software Maintenance is, of course, far more than “fixing mistakes”. We may define
maintenance by describing four activities that are undertaken after a program is released for use.
We have defined four different activities as under:
1. Corrective maintenance
2. Adaptive maintenance
3. Perfective maintenance
4. Preventive maintenance
9.1.1 Corrective Maintenance
Even with the best quality assurance activities, it is likely that the customer will uncover defects
in the software. Corrective maintenance changes the software to correct defects.
9.1.2 Adaptive Maintenance
Over time, the original environment (e.g., CPU, operating system, business rules, external
product characteristics) for which the software was developed is likely to change. Adaptive
maintenance results in modification to the software to accommodate to its external environment.
9.1.3 Perfective Maintenance
As software is used, the customer/user will recognize additional functions that will provide
benefit. Perfective maintenance extends the software beyond its functional requirements.
9.1.4 Preventive Maintenance

99
Computer software deteriorates due to change, and because of this, preventive maintenance
must be conducted to enable the software to serve the needs of its end users. In essence,
preventive maintenance makes changes to computer programs so that they can be more easily
corrected, adapted, and enhanced.
10. Conclusion
Advantages
Limitation
Future Enhancement
100
The module developed by us is very handy, user friendly and efficient. It is a very stable, less
costly and has a lot of features like:
 Efficiently works like other web site on internet

 Fast to access
 Easy for modify and add into database
 Highly sophisticated and user friendly.
The application made by us is perfectly suited to implement all these features.
In Online Complain Management & Email System, register Complain by employee and
managing mails of users is one of the important jobs at hand. This system also provides facility
to create groups. For creation of group is the authority of a user. He can add, delete and modify
the group and group users also.
Administrator can handle user. He can delete user when miss use this site and send the mails to
user. Administrator can handle IPaddress which pc to use this website. Administrator can also
handle Employee’s records and user account’s record.
All users have the email facility. User can send and receive mail. He can add personal details of
his friend in to address book, and can send email to him from address book.
101
10.1 Advantages
 Easy for Installation and maintenance.

 Easy to use for all users.
 Easy to maintain whole system through one user.
 There no need to special servers.
 There is no limitation of user.
 Fast to access.
 Easy for modify and add into database.
 Highly sophisticated and user friendly system.
10.2 Limitations
Though we tried our best but due to some reasons like time duration, this software has some
limitations.
 From this website employee can’t update complain.

 In this website we can’t give the Bulk an Spam Email facility to the user
 The size of the mailbox is dependent on the server in which this website (system)
is stored.
 This site is not actually place in the web space so we are not get mail from other
site other than this.
10.3 Future Enhancement
 One can stop some mail from which you do not want to come in the your Mail
(Block Mails from other)
102
 You can get mail like business advertisement and other in Bulk folder.
 Provide updating of complain to employee.
 Provide chatting facility.
 Provide voice chatting facility.
 Provide group chat facility.
11. User Manual
Users Manual
103
11.1 Users Manual
Perform Following Step to install the intranet mail server
1. Copy Web Setup Folder from CD Drive.
2. Run Setup.Exe and provide necessary information as setup needs.

Before you start Setup be sure that,
a. Your IIS (Internet Information Services is Well Configured.

b. .Net Framework (version 2.0) is already installed.
c. Local Area Network is Well Configured.
d. Sql server 2000 is already installed.
3. When user starts the application, user found login screen on the desktop. After
entering userid and password user get a welcome screen and user can compose mail,
check mail.
104
12. Screen Layouts
Snap Shot
105
106
Snap Shot: 1
• This is the Very first page of the website.
• It contains the link to the Login Page and Registration Page.
107
Snap Shot: 2
• This is the registration page.
• New user can register and get mail id from this page.
108
Snap Shot: 3
• This is admin Login page.
• From this admin can login int system.
Snap Shot: 4
109
• This is the employee detail page.
• From this page employee record is added into database.
Snap Shot: 5
• This is the employee detail page.
• From this page employee record is invalid into database
110
Snap Shot: 6
• This is the email page of admin.
• From this page admin can send mail to all users who are registered.
111
Snap Shot: 7
• This is the page to change password.
• From this page admin can change password and set new password.
112
Snap Shot: 8
• This is the Admin Complain detail page.
• No. of complain solved by the particular department.
113
Snap Shot: 9
• No. of complain solved by the particular Electrical department.
114
Snap Shot: 10
• No. of complain solved by the Civil department.
115
Snap Shot: 11
• This is the Escalator Home Page.
• Escalator can see complain record and recent complain.
116
Snap Shot: 12
• This is the Escalator Recent complain Page.
• Escalator can see recently added complain record .
117
Snap Shot: 13
• This is the Escalator complain record Page.
• Escalator can see all added complain record .
118
Snap Shot: 14
• This is the Escalator compose mail Page.
• Escalator send a mail to employee .
119
Snap Shot: 15
• This is the home page.
• This page displays the username who is logged in.
120
Snap Shot: 16
• This is the complain register page.
• From this page employee who is logged in can insert complain.
121
Snap Shot: 17
• This is the inbox page.
• From this page user can see all mails.
• User can delete the mail.
122
Snap Shot: 18
• This is the compose mail page.
• From this page user can send mail to other user.
• User can attach file to mail and send it to other user who are login.
123
Snap Shot: 19
• This is the outbox page.
• From this page user can see the mail which user sent to other user.
124
Snap Shot: 20
• This is the view complain page.
• From this page Escalate can see all complain done by employee.
125
Snap Shot: 21
• This is the home page for address book.
• From this page user can view addresses from address book.
• User can add new address in address book.
126
Snap Shot: 22
• This is the address book page .
• From this page user can add other user’s mailid into address book.
127
Snap Shot: 23
• This is the view address book page .
• From this page user can view addresses from address book.
• User can edit and delete addresses.
128
Snap Shot: 24
• This is the home page for change setting.
• From this page user can change password and user information.
• User can add group and view group.
• User can add group user.
129
Snap Shot: 25
• This is the home page for change password.
• From this page user can change password.
130
Snap Shot: 26
• This is the add group page.
• From this page user can add new group.
131
Snap Shot: 27
• This is the add group user page.
• From this page user can add new user in the group.
132
Snap Shot: 28
• This is the view group user page.
• From this page user can view all users of group.
• User can edit and delete group user.
133
13. Bibliography
Bibliography
13.1 Bibliography
134
Beginning ASP.NET in C# 2005 for Novice to Professional
• By Matthew MacDonald
ASP.NET 2.0 All-in-One Desk Reference For Dummies

• By Doug Lowe, Jeff Cogswell, and Ken Cox
Sams Teach Yourself ASP.NET 2.0 in 24 Hours

• By Scott Mitchell
MSDN Help
www.google.com
http://www.microsoft.com
135

Final Report

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Final Report

Caricato da

Copyright:

Formati disponibili

INDEX

CONTENT PAGE NO.

ABOUT ONGC HAZIRA PLANT:-

Gas Terminal: The sour gas and

Gas Sweetening Unit: The purpose is to

Gas Dehydration Unit:

Dew Point Depression Unit:

Condensate Fractionation Unit:

This unit aims at removal of H2S and recovery of LPG and

Caustic Wash Unit:

Kerosene Recovery Unit:

• Optimize production of hydrocarbons.

• Generate adequate resources for reinvestment.

• Develop scientifically oriented and technically competent human resource through

1.4 Organizational Structure

• To send complain online through this website.

• To store information about complain.

• To maintain stored information.

• Display the information when user wants.

• To send email to other person through this website.

• To receive the email from other person from this website.

2.2 Project Definition

Online Complain Management & E-mail System, using asp.net, C#.

2.2.1 Features of Project

User does the following Things:

• User can send the complain.

Escalator does the Following Things:

• Create and maintain Employee Record.

• Create and maintain login record of employee.

2.4 Project Platform

2.4.1 Motive of Platform

2.4.2 Advantages of ASP.NET

2.4.3 Feature of ASP.NET

• Easy Programming Model

• Improved Performance and Scalability:-

• Memory Leak, Deadlock and Crash Protection.

• “No touch” application deployment

• Easy Migration Path

• New Application Models:-

• XML web services

• ASP to ASP .NET:-

• Desirable Database Characteristics:-

2.5 Project Summary

External Project Guide:-

Internal Project Guide:-

“Online Complain Management & E-mail System”

Our Application provides online availability to register complain as per requirement of

TASK MONTH1 MONTH2 MONTH3 MONTH4

1.1 Identify needs &

Establish project statement

Milestone: Project scope

1.2 Assess Risks

1.3 Define desired

Define the budget for each

For Client/Server Software

For form designing

1.5 Define the function

Forms for personal profile

Form for registration

Forms for selection of services &

Forms for estimates & payment

Review OCI definition