See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/375059394

Mall Management System

Thesis · May 2013

DOI: 10.13140/RG.2.2.35772.41601

CITATIONS READS
0 6,600

2 authors, including:

Devharsh Trivedi
Bowie State University
61 PUBLICATIONS 37 CITATIONS

SEE PROFILE

All content following this page was uploaded by Devharsh Trivedi on 28 October 2023.

The user has requested enhancement of the downloaded file.

 A Project Report On

Mall Management System

Submitted in Partial Fulfillment of
The Degree of

Bachelor of Engineering
In
Computer Engineering

Prepared By

Shivam Patel
(090120107041)

Devharsh Trivedi
(090120107059)

Guided By

Prof. Kalpana Mudaliar

DEPARTMENT OF
COMPUTER ENGINEERING
APRIL-MAY 2013

GANDHINAGAR INSTITUTE OF TECHNOLOGY,

MOTI-BHOYAN, GANDHINAGAR
 CERTIFICATE

This is to certify that this work of Industrial Defined Project entitled “Mall Management

System” represents the bonafide work of Shivam Patel, 090120107041 for the partial

fulfillment of the degree of Bachelor of Engineering in Computer Engineering at the

Department of Computer Engineering, Gandhinagar Institute of Technology, Moti-Bhoyan,

Gandhinagar, Gujarat, during the academic year 2012-13 and his work is satisfactory.

Internal Guide, External Guide,

Prof. Kalpana Mudaliar Mr. Sagar Makwana
Asst. Prof., Senior Developer,
Computer Engineering Department Virtual Height IT Solutions

Prof. Rahul Vaghela

Head of Department,
Department of CE-IT
 CERTIFICATE

This is to certify that this work of Industrial Defined Project entitled “Mall Management

System” represents the bonafide work of Devharsh Trivedi, 090120107059 for the partial

fulfillment of the degree of Bachelor of Engineering in Computer Engineering at the

Department of Computer Engineering, Gandhinagar Institute of Technology, Moti-Bhoyan,

Gandhinagar, Gujarat, during the academic year 2012-13 and his work is satisfactory.

Internal Guide, External Guide,

Prof. Kalpana Mudaliar Mr. Sagar Makwana
Asst. Prof., Senior Developer,
Computer Engineering Department Virtual Height IT
Solutions

Prof. Rahul Vaghela

Head of Department,
Department of CE-IT
 ABSTRACT

Current systems emphasis on online shopping by a customer from a mall, where as our
system will provide a common platform for owner and keeper. This system is totally different
from shopping mall management system. Mall Management System emphasis on the
communication and interaction between Mall owners and Shopkeepers in the Mall. Mall
management system will be very effective for fast, easy and efficient communication between
a mall owner and a shopkeeper.

Purpose of making this website is to provide more facilities to mall owners to get efficient
business communication with shop keepers. Mall management is a well formulated concept in
developed countries which are more matured markets.

Mall management largely encompasses several activities that go into the maintenance of the
mall. This covers facilities management functions, operation management, marketing
management, accounts management and customer service. It is basically a combination of
services that factor in people, place, processes and technology in a particular building.
Professional mall management results in the best possible utilization of resources available.

Mall management begins with taking care of issues such as positioning, tenant mix,
infrastructure facilities, the kind of environment required and finance management, which is
the most crucial part of all. It also takes care of issues like positioning, zoning that include
tenant mix and placement within mall, promotions and marketing.

I
 ACKNOWLEDGEMENT

We would like to acknowledge the contribution of certain distinguished people, without their
support and guidance this project work would not have been completed.

We take this opportunity to express our sincere thanks and deep sense of gratitude to our
project guide Prof. Kalpana Mudaliar, Asst. Prof., Computer Engineering, GIT, for her
guidance and moral support during the course of preparation of this project report. We really
thank her from the rock bottom of our heart for always being there with her extreme
knowledge and kind nature.

We take this opportunity to thank all our friends and colleagues who started our out on the
topic and provided extremely useful review feedback and for their all-time support and help in
each and every aspect of the course of our project preparation. We are grateful to our college
Gandhinagar Institute of Technology, Gandhinagar for providing us all required stuff and good
working environment.

We feel a deep sense of gratitude for our Director, Dr. N.M.Bhatt who formed part of our
vision and taught us the good things that really matter in life.

Acknowledgements and thanks are also extended to all the authors whose articles have been
referred to for the completion of this report.

Shivam Patel (090120107041)

Devharsh Trivedi (090120107059)

II
 LIST OF FIGURES

Figure No. Description Page No.

2.1 Chart of Effects and Probability 16
2.2 Incremental Model 17
3.1 E-R Diagram 19
3.2.1 DFD Level 0 20
3.2.2 DFD Level 1 Admin 21
3.2.3 DFD Level 1 Mall Owner 22
3.2.4 DFD Level 1 Shop Keeper 23
3.2.5 DFD Level 1 Customer 23
3.3 Use case Diagram 24
3.4 Sequence Diagram 25
3.5.1 Admin Activity Diagram 26
3.5.2 Mall Owner Activity Diagram 27
3.5.3 Shopkeeper Activity Diagram 28
3.5.4 Customer Activity Diagram 29
5.1 Incremental Life Cycle Model 62
5.2 Data Access Layer 67
5.3 Business Logic Layer 68

III
 LIST OF TABLES

Table No. Description Page No.

1.1 Project Profile 2

2.1 Timeline Chart 11
2.2 Risk Identification 16
4.1 Country 30
4.2 State 30
4.3 City 30
4.4 Admin_db 30
4.5 Mall_owner_db 31
4.6 Shop_keeper_db 31
4.7 Category 32
4.8 Cleantable 32
4.9 Safetable 32
4.10 Sectable 33
4.11 Db_new_msg 33
4.12 regkeydata 33
4.13 db_event 33
4.14 db_contactMessage 34
5.1 General 63
5.2 Presentation Layer 63
5.3 Input Validation 64
5.4 Data Access 64
5.5 Catching 64

IV
5.6 State Management 64
5.7 Exception Handling 64
5.8 Configuration 65
6.1 Testing Plan 70

V
 SYMBOLS AND ABBREVIATIONS

MMS: Mall Management System

DFD: Data Flow Diagram

SRS: System Requirements Specification

DB: Database

Admin: Administrator

MO: Mall Owner

SK: Shop Keeper

ASP: Active Server Page

VS: Visual Studio

E-R: Entity-Relation

sec: Security

cle: Cleaning

CLR: Common Language Runtime

SQL: Structured Query Language

T-SQL: Transact-SQL

IIS: Internet Information Server

API: Application Program Interface

DOM: Document Object Model

RDBMS: Relational Database Management System

TDS: Tabular DataStream

SOAP: Simple Object Access Protocol

VI
 CONTENTS

Abstract I
Acknowledgement II
List of Figures III
List of Tables IV
Symbols and Abbreviations VI
Contents VII
Chapter : 1 INTRODUCTION
1.1 Organization Profile 1
1.2 Project Detail 2
1.3 Purpose 2
1.4 Scope 2
1.5 Objective 2
1.6 Technology and Literature Review 4
Chapter : 2 ABOUT THE SYSTEM
2.1 System Requirement Specification 7
2.2 Feasibility Study 11
2.3 Project Planning 11
Chapter : 3 ANALYSIS
3.1 E-R Diagram 19
3.2 Data Flow Diagram 20
3.3 Use Case Diagram 24
3.4 Sequence Diagram 25
3.5 Activity Diagram 26
Chapter : 4 DESIGN
4.1 Data Dictionary 30
4.2 Application Navigation 34
4.3 User Interface 35

VII
Chapter : 5 IMPLEMENTATION
5.1 Implementation Environment 61
5.2 Security Feature 63
5.3 Coding Standard 63
5.4 Store Procedure 65
5.5 Data Access Layer 66
5.6 Business Logic Layer 67
Chapter : 6 TESTING
6.1 Testing Plan 70
6.2 Testing Strategies 71
6.3 Testing Methods 71
Chapter : 7 CONCLUSION AND FUTURE WORK
7.1 Conclusion 72
7.2 Future Enhancement 72
References 73

VIII
Mall Management System Introduction

Chapter 1.
INTRODUCTION

1.1 Organization Profile

About VHIS

Virtual Height is committed to helping our clients develop and enhance their business
offerings through our range of technology and design services m order to provide a
foundation for business excellence.

Our Mission

We aspire to be No. 1 in the website development, domain registration and hosting, web
designing, recruiting held, globally, by providing the best of talents, skins and abilities
available in the world to our valuable clients.

Our Services

 Website Hosting
 Domain Registration
 Website Designing
 Website Development
 Placement Consultancy
 Software Development
 Freelance Project

1
Mall Management System Introduction

1.2 Project Detail

1.2.1 Project Definition

Mall Management System emphasis on the communication and interaction between Mall owners and
Shopkeepers in the Mall. Mall management system will be very effective for fast, easy and efficient
communication between a mall owner and a shopkeeper.

1.2.2 Project Profile

[Table 1.1 Project Profile]

Project title Mall Management System

Group ID GIT_CE_12_25
Project Guide Prof. Kalpana Mudaliar
Company Guide Mr. Sagar Makwana
Start Date 01/08/2012
End Date(Tentative) April 2013

1.3 Purpose

Purpose of making this website is to provide more facilities to mall owners to get efficient
business communication with shop keepers. Mall management is a well formulated concept in
developed countries which are more matured markets.

1.4 Scope

 The system should be able to run on any system regardless of the operating system or
hardware; within reason.
 User Friendliness is the main focus.
 Ensuring minimal down-time due to the critical nature of the system.
 Long term maintenance and diagnostics coverage.

1.5 Objective
Features:

 Security Management
 Safety Management
 Marketing Management
 Event and Notification Management

2
Mall Management System Introduction

Benefits:

o Increase efficiency
o Manage relationships
o Faster communication
o Reduced workload
o Ease of management

3
Mall Management System Introduction

1.6 Technology and Literature Review

 Technology: ASP.NET
1. Languages to be used: C#
2. Database Server: Microsoft SQL Server 2008
3. Web Server: IIS 6.0 or Higher

 ASP.NET AJAX is a set of extensions to ASP.NET developed by Microsoft for

implementing Ajax functionality. It is released under the Microsoft Public
License.
 AJAX stands for Asynchronous JavaScript and XML is a group of interrelated
web development techniques used on the client-side to create interactive web
applications.
 With Ajax, web applications can retrieve data from the server asynchronously in
the background without interfering with the display and behaviour of the existing
page.
 The use of Ajax techniques has led to an increase in interactive or dynamic
interfaces on web pages. Data are usually retrieved using the XML HttpRequest
object. Despite the name, the use of XML is not actually required, nor do the
requests need to be asynchronous.

 Microsoft Ajax Library

The Microsoft Ajax Library is a JavaScript library that provides the features for the
client portion of the ASP.NET AJAX framework.

 Components. The library provides an infrastructure to build either visual or non-

visual JavaScript components. A global JavaScript object – Sys. Application – is
responsible for managing the lifecycle of client components.
 JavaScript extensions – An enhanced type system is introduced to emulate object-
oriented constructs such as namespaces, classes and interfaces; and to perform
reflection on client types.
 Abstraction API – Common operations on the DOM (retrieving elements, setting
styles and other manipulations) are automatically translated by the library into
browser-specific calls.
 Ajax – A set of client components is provided to handle Ajax requests and web-
service calls.
 Application Services – The library allows accessing the ASP.NET Membership,
Authentication, Roles and Profile services from the client side.
 Recently, new features have been announced as part of the ASP.NET AJAX 4.0
release:
 Template Engine – Allows displaying data on the client side by using HTML
templates and a custom binding notation. This approach avoids performing page
rendering on the server side.

4
Mall Management System Introduction

 Declarative instantiation of client components – Allows registration, instantiation

and configuration of client components using markup code, without writing any
imperative JavaScript code.

 About C#
 C# (pronounced C Sharp) is a multi-paradigm programming language that
encompasses functional, imperative, generic, object-oriented (class-based), and
component-oriented programming disciplines.
 C# is one of the programming languages supported by the .NET Framework's
Common Language Runtime.
 C# is intended to be a simple, modern, general-purpose, object-oriented
programming language. Its development team is led by Anders Hejlsberg, the
designer of Borland's Object Pascal language.
 It has an object-oriented syntax based on C++ and is heavily influenced by Java. It
was initially named Cool, which stood for "C-like Object Oriented Language."
However, in July 2000, when Microsoft made the project public, the name of the
programming language was given as C#.

 Why Asp.Net?
 Since 1995, Microsoft has been constantly working to shift its focus from window
based platforms to the internet. As the result, Microsoft introduced ASP (Active
server page) in November 1996.
 ASP offered the efficiency of ISAPI applications along with a new level of
simplicity that made it easy to understand and use.
 Unlike ASP, ASP.NET uses the Common Language Runtime (CLR) provided by
the .NET framework. This CLR manages execution of the code we write.
 ASP.NET code is a compiled CLR code instead of interpreted code (ASP). CLR
also allows objects written in different languages to interact with each other. The
CLR makes development of Web applications simple.

 Advantages Using ASP.NET

 ASP.NET drastically reduces the amount of code required to build large
applications
 ASP.NET makes development simpler and easier to maintain with an event-driven,
server-side programming model.
 ASP.NET pages are easy to write and maintain because the source code and
HTML are together.
 The source code is executed on the server. The pages have lots of power and
flexibility by this approach.
 The source code is compiled the first time the page is requested. Execution is fast
as the Web Server compiles the page the first time it is requested. The server saves
the compiled version page for use next time the page is requested.

5
Mall Management System Introduction

 The HTML produced by the ASP.NET page is sent back to the browser. The
application source code you write is not sent and is not easily stolen.
 ASP.NET validates information (validation controls) entered by the user without
writing a single line code.
 ASP.NET easily works with ADO.NET using data-binding and page formatting
features.

 SQL Server
 Microsoft SQL Server is a relational database management system (RDBMS)
produced by Microsoft. Its primary query languages are T-SQL, Entity-SQL and
ANSI SQL.
 SQL Server included native support for managing XML data, in addition to
relational data. For this purpose, it defined an xml data type that could be used
either as a data type in database columns or as literals in queries. XML columns
can be associated with XSD schemas; XML data being stored is verified against
the schema. XML is converted to an internal binary data type before being stored
in the database. Specialized indexing methods were made available for XML data.
XML data is queried using XQuery; SQL Server 2008 added some extensions to
the T-SQL language to allow embedding XQuery queries in T-SQL.
 In addition, it also defines a new extension to XQuery, called XML DML that
allows query-based modifications to XML data.
 SQL Server 2008 also allows a database server to be exposed over web services
using TDS packets encapsulated within SOAP (protocol) requests. When the data
is accessed over web services, results are returned as XML.
 For relational data, T-SQL has been augmented with error handling features and
support for recursive queries. SQL Server 2008 has also been enhanced with new
indexing algorithms and better error recovery systems.
 Data pages are check summed for better error resiliency, and optimistic
concurrency support has been added for better performance.
 Permissions and access control have been made more granular and the query
processor handles concurrent execution of queries in a more efficient way.
 Partitions on tables and indexes are supported natively, so scaling out a database
onto a cluster is easier.
 SQL CLR was introduced with SQL Server 2008 to let it integrate with the .NET
Framework.

6
Mall Management System About The System

Chapter 2.
ABOUT THE SYSTEM

2.1 System Requirement Specification

1.Introduction

1.1 Purpose:

Purpose of making this system is to provide more facilities to mall owners to get efficient
business communication with shop keepers. Mall management is a well formulated concept in
developed countries which are more matured markets.

Mall management largely encompasses several activities that go into the maintenance of the
mall. This covers facilities management functions, operation management, marketing
management, accounts management and customer service. It is basically a combination of
services that factor in people, place, processes and technology in a particular building.
Professional mall management results in the best possible utilization of resources available.

Mall management begins with taking care of issues such as positioning, tenant mix,
infrastructure facilities, the kind of environment required and finance management, which is
the most crucial part of all. It also takes care of issues like positioning, zoning that include
tenant mix and placement within mall, promotions and marketing.

1.2 Scope:

 The system should be able to run on any system regardless of the operating system or
hardware; within reason.
 User Friendliness is the main focus.
 Ensuring minimal down-time due to the critical nature of the system.
 Long term maintenance and diagnostics coverage.
 Increase efficiency.
 Manage Relationship.

2.General description

2.1 Product perspective:

This system is totally self contained and works relatively as efficient as other
packages related to the subject. It provides simple database rather than complex ones
for high requirements and it provides good and easy graphical user interface to both
new, naive as well as experienced users of the computers.

7
Mall Management System About The System

2.2 Product functions:

 User Registration
 Select service like mall owner or shopkeepers
 Mall owner gives key to shopkeepers of different shops
 Mall Owner can check latest update of event, payment, notification of different mall
 Shopkeepers can do online transactions of all shops
 Shopkeepers can access the different shops at one place by using keys

2.3 User Characteristic:

The Mall owners who will be using our product will have a basic familiarity with personal
computers and a working knowledge of systems with graphical user interfaces. The Mall
owners are not assumed to have any understanding of networking or file transfer methods. The
only specific information the Owner and keeper are required to have is the name of the server
they wish to connect to, a login name, and a password if the remote server‘s security
configuration demands it.

3.System Features:-

1. Admin:
a. Registration/ Login(Admin can create another admin)
-Here admin should have one option that he can create another admin and allocate
different rights to that person regarding website operations.
b. Admin can define schemes for shopkeepers
-Admin can define schemes for shopkeepers so they can attract to more invest.
c. Admin should have his own email panel and address book to mail every one
-By using his own email panel admin can mail any one added to his address book on
website.
d. Admin can Add/Modify Terms and condition
-Admin can add terms and condition as well he can change them and delete them.
e. Admin can view all feedbacks and Enquires.
-Admin can view all feedback and enquires and also can replay them at a time by
email.
f. Admin can add contact details.
-In cases of opening a new mall and defining any new schemes admin can add or delete
and modify the contact information.

2. Shopkeepers:
a. User can apply only after login
-if user is not login he will not able to show all details on website.
b. User can see all details of their shop
-user is available to see details only after login
c. User can see advertisement policy of mall.
-user can see all advertisement details of malls.

8
Mall Management System About The System

3.Mall Owners:

a. User can apply only after login

-if user is not login he will not able to show all details on website.
b. User can see all details of their malls
-user is available to see details only after login.
c. User can post advertisement on the website
-user can also post advertisement of shopkeeper shops.
d. User can maintain all the details of their all malls
-user can also maintain all the details of all shops in all malls.
e. User can set advertisement policy
-user can handle terms and condition of advertisement policy.

4. Specific Requirements:-

4.1External Interface Requirements:-

4.1.1. User Interfaces :-

The software provides good graphical interface for the front end of the database and a
good informative interface for the rear end. The system users are:

 The Mall Owners as system administrators.

 Shopkeepers as normal users.

4.1.1.1. System Administrators

The administrator log on to the system by inserting administrator name and password.
Administrator can do any transaction as well as editing all details inside the database such as
adding, editing, deleting a new user as well as adding, editing, deleting a new item.

4.1.1.2. System Users

The users have to enter the user name and password and click on ‘Login’ button. If user makes
any mistake the system will ask for the correct username and password until he enters the
correct one. When the user wants to do any transaction user has to click on the menu icon on
the main menu. Then the transaction window will open.

4.1.1.3. Hardware Interfaces

 Mall Owners main computer

 Other PCs

4.1.1.4. Software Interfaces

9
Mall Management System About The System

 System will interact with the system database to record all transaction data.

4.2. Communication Interfaces :-

 Local intranet and internet protocols.

 Supports all HTTP, SMTPS and POP3 services

4.3. Performance Requirements :-

 Good working pc with all the requirements as stated in the hardware interfaces
 Works for medium size information databases
 Should not be overloaded
 The response time for menu changes will not be more than 3 seconds.
 The time taken to update the database or to get information from the database will not
be more than 2 seconds.

4.4. Design Constraints:-

 The browser should support .NET

 The browser should be at least Netscape navigator v 4.0 or internet explorer
 .NET programming environment has been used for secure transactions and protection
from viruses, worms, and other threats like hacking of passwords by hackers.
 While designing this product fault tolerance and standard compliance are kept in
mind.
 Error messages will be displayed at the time of detection of input error and the
system errors

5.Non Functional Requirements:-

5.1 Hardware Requirements:

 The processor should be at least Dual Core or above

 The processor speed should be greater than 400Mhz
 Ram should be or greater than 128 MB.

5.2 Software Requirements

 Operating System :Windows XP,Vista,7,Mac OS

 Technology :ASP.NET
 Programming Language :C#
 Database :Microsoft SQL 2008
 Browser :Mozilla Firefox, Google Chrome, IE, Opera, Safari

10
Mall Management System About The System

2.2 Feasibility Study

 Operational Feasibility:
System besides being simple should also be user friendly. Any user can easily access
the website and all materials, messages, post, chat and all other facilities and if any user
has even smallest problem then he can report to the admin and he will surely get result
very immediately.

 Economic Feasibility:
This System is developed using new technology so there is requirement of new
software or development tools. With the speed provided by the new system, greater
volumes of transactions can be easily dealt with, which will increase the profit.

 Technical Feasibility:
The social networking website is developed using asp.net with framework 4.0 and SQL
server 2008 which give access large amount of data in simple and secure manner and
give output faster.

2.3 Project Planning

2.2.1. Timeline Chart

 SCHEDULE

[Table 2.1 Timeline Chart]

August:
No. Tasks Weekend 1 Weekend 2 Weekend 3 Weekend 4

1 Decide project
name and
functionality
2 Discuss project
functionality with
internal guide
3 Requirement
Gathering and
Specifications

September:
No. Tasks Weekend 1 Weekend 2 Weekend 3 Weekend4
1 Requirement
Gathering and
Specifications

11
Mall Management System About The System

2 Data flow
diagram

3 UML Diagram

October:
No. Tasks Weekend 1 Weekend 2 Weekend 3 Weekend 4
1
UML Diagram

2
Data Dictionary
related to project

November:
No. Tasks Weekend 1 Weekend 2 Weekend 3 Weekend 4
1
Data Dictionary
related to project

2
General page and
about it
3 Master Page

December:
No. Tasks Weekend 1 Weekend 2 Weekend 3 Weekend 4
1. Registration, Login
page, Profile page

2. Design Post and

12
Mall Management System About The System

Message page

3. Design Admin and

Customer module

4. Design of Mall-
Owner and
Shopkeeper module

January:
No. Tasks Week 1 Week 2 Week 3 Week 4
1. Code about
Registration, Post
and Messages.

2. Code about Mall-

Owner and
Shopkeeper module

3. Code about Admin

and Customer
module

February and March:

No. Tasks Week 1 Week 2 Week 3 Week 4 Week 5
1. Testing of all
modules

13
Mall Management System About The System

2.2.2. Risk Management

Simplest and possibly best definition of risk is “the possibility of loss injury,
disadvantage or destruction.
Risks are of many types:
1. Programmatic risk
2. Schedule risk
3. Cost risk
4. Technical risk
5. Supportability risk

Risk management is the sum of all proactive management directed activities

within a program.

 Risk Identification
The purpose of this topic is to identify the risks involved in project. Here we will
consider all the possible risks that can affect the project. All such risks are involved
below. Due to some technical or managerial reason the project might not be able to
meet its requirement up to ultimate data given. This risk exists in almost all the
projects. Technology being used might not be able to meet the expectation. This
can occur when the design of some processes cannot be implemented in the chosen
programming language.

Developer inexperience is also one of the risks which will be considered. This
might happen if the person who chooses for one particular task has no experience
in doing similar work. Constant turnover might happen. The possibility of the risk
is hard to gauge. If developer turnover is high then there will be a very high
negative impact on the project. This also delay the project as new people will first
have to understand what is happening and the flow of the module. Database crash is
one of the technical risks that will be considered. This risk will be prioritized first.

 Risk Analysis
Risk analysis is a systematic approach for describing and/or calculating risk.
During risk analysis process, each identified risk is considered in term and a
judgment made about the probability and the seriousness of the risk.

14
Mall Management System About The System

[Table 2.2 Risk Identification]

NO Risks Probability Effects

1 Change into the technology for development Very Low insignificant

2 Design of project is not satisfied to the Low Tolerable
customer
3 Reductions in project budget due to financial Very low Tolerable
problem
4 Changes to the requirements which require Very low Serious
major design rework as proposed
5 The database used in system cannot process Very low Serious
as many transaction per second as expected
6 Unauthenticated Access of the secure data Very low Catastrophic
7 The time require to develop the software is Very low Serious
under estimated
8 Misunderstanding the nature of the Low Tolerable
environment

9 The size of project is increased. High Tolerable

10 The code generated is inefficient Low Insignificant

11 Traffic on the website is increased. Very Low Tolerable

12 Browser compatibility problem Moderate Tolerable

To handle the risks we have prioritized it. The damaging risks can be handled first and then
most likely risks. Since the risk related to the schedule slippage arise primarily due to the
intangible nature of the software, so I had to do the visibility of software requirements
documentation and reviewing the relevant documents during the developments. Every phase
can be broken into the reasonably sized tasks and milestones can be scheduled for these tasks.
In this process each identified risk is considered in turn and a judgment made about the
probability and the seriousness of the risk.
1. The probability of the risk might be assessed as very low, low, moderate, high
or very high.
2. The effects of the risk might be assessed as catastrophic, serious, tolerable or
insignificant.

 Chart of Risk Management

Chart Represents The Risk management Probability vs. Effects. There are various
probabilities like very low, high, moderate, and high and related effects are given in to
the percentage

15
Mall Management System About The System

Chart of Probability Vs. Effects is shown as below:

Probability and Effects

30%

25%

20% Effects
Catastrophic
15%
Serious
10% Tolerable
Insignificant
5%

0%
Very Low Low Moderate High
Probability

[Figure 2.1 Chart of Effects and Probability]

2.2.3. Model Specification

 Incremental Model

The Incremental Model combines elements of the linear sequential model with the iterative
philosophy of prototyping.

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.

For example, word processing software developed using the incremental paradigm might
deliver basic file management, editing and document production functions in the first
increment; more sophisticated editing and document production capabilities in the second
increment; spelling and grammar checking in the third increment; and advanced page
layout capability in the fourth increment. It should be noted that the process flow for any
increment can incorporate the prototyping paradigm.

16
Mall Management System About The System

[Figure 2.2 Incremental Model]

17
Mall Management System About The System

 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.

 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.

18
Mall Management System Analysis

Chapter 3.
ANALYSIS

3.1 E-R Diagram

Fig 3.1. E-R Diagram

19
Mall Management System Analysis

3.2 Data Flow Diagram

Fig 3.2.1 DFD Level 0

20
Mall Management System Analysis

Fig.3.2.2 DFD Level 1 Admin

21
Mall Management System Analysis

Fig. 3.2.3 DFD Level 1 Mall-Owner

22
Mall Management System Analysis

Fig. 3.2.4 DFD Level 1 Shopkeeper

Fig. 3.2.5 DFD Level 1 Customer

23
Mall Management System Analysis

3.3 Use Case Diagram

Fig. 3.3 Use Case Diagram

24
Mall Management System Analysis

3.4 Sequence Diagram

Fig. 3.4 Sequence Diagram

25
Mall Management System Analysis

3.5 Activity Diagram

Fig. 3.5.1 Admin Activity Diagram

26
Mall Management System Analysis

Fig. 3.5.2 Mall-Owner Activity Diagram

27
Mall Management System Analysis

Fig.3.5.3 Shopkeeper Activity Diagram

28
Mall Management System Analysis

Fig.3.5.4 Customer Activity Diagram

29
Mall Management System Design

Chapter 4.
DESIGN

4.1 Data Dictionary

Table 4.1 - Country

No Name Type Constraint Description

1. intglcode int Primary key Identifier
2. Country_name Varchar(50) Name of country

Table 4.2 - State

No Name Type Constraint Description

1. intglcode int Primary key Identifier
2. State_name Varchar(50) Name of state
3. Fk_country int Foreign key Identifier of
country

Table 4.3 - City

No Name Type Constraint Description

1. intglcode int Primary key Identifier
2. City_name Varchar(50) Name of city
3. Fk_state int Foreign key Identifier of
state

Table 4.4 - admin_db

No Name Type Constraint Description

1. intglcode int Primary key identifier
2. username Varchar(50) Not null Admin
username
3. password Varchar(50) Not null Admin
password
4. role Varchar(50) Not null Admin role

30
Mall Management System Design

Table 4.5 - mall_owner_db

No Name Type Constraint Description

1. intglcode int Primary key identifier
2. Uname Varchar(50) Not null username
3. DOB datetime Date of birth
4. email Varchar(50) Email address
5. address Varchar(50) Resident address
6. phone Number(10) Contact no
7. Mall_name Varchar(50) Not null Mall name
8. Mall_address Varchar(MAX) Mall address
9. estd datetime Date established
10. area Decimal(18,2) Mall area
11. shops Decimal(10,0) Total shops
12. Timing_from Varchar(50) Starting from
13. Timing_to Varchar(50) Closing to
14. guards Decimal(10,0) No of guards
15. Sec_eqp int Security
equipments
16. cleaners Decimal(10,0) No of cleaners
17. Clean_eqp int Cleaning
equipments
18. holdings Decimal(10,0) No of holdings
19. banners Decimal(10,0) No of banners
20. leds Decimal(10,0) No of LEDs
21. Park_area Decimal(18,2) Parking area
22. Safe_eqp int Safety
equipments
23. Mall_manager Varchar(50) Mall manager
24. Mall_phone Decimal(10,0) Mall phone
25. Mall_email Varchar(50) Mall email
26. username Varchar(50) Not null username
27. password Varchar(50) Not null password
28. status Varchar(50) Default: status
deactivated

Table 4.6 - shop_keeper_db

No Name Type Constraint Description

1. Intglcode Int Primary key Identifier
2. Oid Int Not null Identifier of
mall owner
3. Regkey Varchar(50) Registration key
4. Cost Decimal(10,0) Cost
5. Rent Decimal(10,0) Rent

31
Mall Management System Design

6. Maintenance Decimal(10,0) Maintenance

7. Mall_name Varchar(50) Not null Mall name
8. Sid Int Not null Identifier of
shop keeper
9. Shop_name Varchar(50) Not null Shop name
10. Shop_estd Datetime Shop established
11. Category Int Shop category
12. Shop_area Decimal(18,0) Shop area
13. Shop_mail Varchar(50) Shop email
14. Shop_contact Decimal(10,0) Shop contact no
15. Shop_website Varchar(50) Shop website
16. Timing_to Varchar(50) Starting from
17. Timing_from Varchar(50) Closing to
18. Username Varchar(50) Not null Username
19. Password Varchar(50) Not null Password
20. Status Varchar(50) Default: Status
deactivated

Table 4.7 - category

No Name Type Constraint Description

1. intglcode Int Primary key Identifier
2. category Varchar(50) Not null Shop category

Table 4.8 - cleanTable

No Name Type Constraint Description

1. intglcode Int Primary key Identifier
2. Clean_eqp Varchar(50) Not null Cleaning
equipments

Table 4.9 - safeTable

No Name Type Constraint Description

1. intglcode Int Primary key Identifier
2. Safe_eqp Varchar(50) Not null Cleaning
equipments

32
Mall Management System Design

Table 4.10 - secTable

No Name Type Constraint Description

1. intglcode Int Primary key Identifier
2. Sec_eqp Varchar(50) Not null Cleaning
equipments

Table 4.11- db_new_msg

No. Name Type Constraint Description

1. intglcode Int Primary key Identifier
2. Msg_from Int Not null Id of sender
3. senderName Varchar(50) Not null Name of sender
4. senderProfile Varchar(50) Not null Profile type of
sender
5. Msg_to Int Not null Receiver ID
6. receiverName Varchar(50) Not null Receiver Name
7. receiverProfile Varchar(50) Not null Receiver Profile
8. Subject Varchar(50) Subject of
Message
9. Message Varchar(MAX) Not null Message
10. Status Varchar(50) Not null Read/Unread

Table 4.12-regkeydata

No. Name Type Constraint Description

1. intglcode Int Primary key Identifier
2. Oid Int Mallowner ID
3. Regkey Varchar(50) Registration
Key
4. Status Varchar(50) Active/Deactive

Table 4.13-db_event

No. Name Type Constraint Description

1. intglcode Int Primary key Identifier
2. Photoname Varchar(50) Not null Photoname
3. Photopath Varchar(MAX) Not null Photopath
4. Generatedby Varchar(50) Not null Owner/Keeper
5. Event_name Varchar(50) Not null Name of Event
6. Event_details Varchar(MAX) Not null Details of Event
7. Event_venue Varchar(MAX) Not null Venue of Event
8. Event_startdate Varchar(50) Not null Starting Date
9. Event_enddate Varchar(50) Not null Ending Date

33
Mall Management System Design

Table 4.14-db_contactMessage

No. Name Type Constraint Description

1. intglcode Int Primary key Identifier
2. firstName Char(25) Not null First name
3. lastName Char(25) Not null Last Name
4. Companyname Varchar(50) Company Name
5. Email Varchar(50) Not null Email ID
6. Website Varchar(50) Website URL
7. Message Varchar(MAX) Not null Message
8. Status Char(7) Read/Unread

4.2 Application Navigation

Easy in maintaining information: As new information is being added to and released from
their respective courses every year, it will be highly user friendly to track and maintain the
records of all users.

User satisfaction: The system is such that is stands up to the user expectations like easy and
faster retrieval of information.

Safety: The system will be accessible by only the authorized users. As information being
the most crucial for the organization, then the safety of information is importation.

Highly accurate: Resources being used by the system will be compatible with the latest
technologies available in the market, as proposed system uses highly technically compatible
resources, there will be very less wear and tear.

Less time consuming: work carried out by the Mall owner and Shopkeeper at various
stages will be less time consuming.

34
Mall Management System Design

4.3 User Interface

Admin:

Admin Registration Form:

35
Mall Management System Design

Add Category:

Add Country:

36
Mall Management System Design

Add State:

Add City:

37
Mall Management System Design

Change Password:

Abstract details of Mall Owner:

38
Mall Management System Design

Genrate Registration Key:

Admin Send Message:

39
Mall Management System Design

Admin Feedback Message:

40
Mall Management System Design

Add Equipments:

41
Mall Management System Design

Mallowner:

Welcome Page:

42
Mall Management System Design

Mallowner Profile:

43
Mall Management System Design

Shopkeeper Details:

44
Mall Management System Design

Genrate Event:

45
Mall Management System Design

Send Message:

46
Mall Management System Design

Process Data:

47
Mall Management System Design

Shopkeeper:

Welcome Page:

48
Mall Management System Design

View Message:

49
Mall Management System Design

Send Message:

50
Mall Management System Design

Create Event:

51
Mall Management System Design

Customer:

Fig. 1 - Homepage

Fig. 2 – About us: Project developers

Fig. 3 – About us: Mall Management System

Fig. 4 – Contact us: Message Form

Fig. 5 – Contact us: Email details

Fig. 6 – Advertise with us

Fig. 7 – Privacy Policy

Fig. 8 – Webpage translation in other languages

52
Mall Management System Design

53
Mall Management System Design

54
Mall Management System Design

55
Mall Management System Design

56
Mall Management System Design

57
Mall Management System Design

58
Mall Management System Design

59
Mall Management System Design

60
Mall Management System Implementation

Chapter 5.
Implementation

5.1 Implementation Environment

5.1.1 Design & Implementation Constrain

Software Development Life Cycle

Incremental Model:

 The incremental model applies linear sequences in a staggered fashion as

calendar time progresses. Each linear sequence produces a deliverable
“increment” of the software. For example, word-processing software developed
using the incremental paradigm might deliver basic file management, editing,
and document production functions in the first increment; more sophisticated
editing and document production capabilities in the second increment; spelling
and grammar checking in the third increment; and advanced page layout
capability in the fourth increment. It should be noted that the process flow for
any increment can incorporate the prototyping paradigm.

 When an incremental model is used, the first increment is often a core product.
That is, basic requirements are addressed, but many supplementary features
(some known, others unknown) remain undelivered.

 The core product is used by the customer (Or undergoes detailed review). 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.

61
Mall Management System Implementation

 The incremental process model, like prototyping and other evolutionary 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.

 Incremental development is particularly useful when staffing is unavailable for a

complete implementation by the business deadline that has been established for the
Project. Early increments can be implemented with fewer people. If the core product is
well received, then additional staff (if required) can be added to implement the next
increment. In addition, increments can be planned to manage technical risks.

 For example, a major system might require the availability of new hardware that is
under development and whose delivery date is uncertain. It might be possible to plan
early increments in a way that avoids the use of this hardware, thereby enabling partial
functionality to be delivered to end-users without inordinate delay.

Advantages:
 Generates working software quickly and early during the software life cycle
 More flexible - less costly to change scope and requirements.
 Easier to test and debug during a smaller iteration.
 Easier to manage risk because risky pieces are identified and handled during its
iteration

62
Mall Management System Implementation

Disadvantage:
 Each phase of an iteration is rigid and do not overlap each other.
 Problems may arise pertaining to system architecture because not all requirements are
gathered up front for the entire software life cycle.

5.2 Security Feature

The interfaces provided to the firm are web based. Hence security is one of the primary
questions involved. In order to establish privacy of accounts and information, the team has
provided login facilities for the application. This is mainly because any important information
which needs to be given only to the firm remains secured. The username and the password are
stored safely in the database. The password is stored in an encrypted format in the database so
as to enhance the system’s security. Similar kind of mechanism has been provided for the
other interface as well. Hence the issue of security has been resolved using the mechanism of
username and password.

 Authorized owners and keepers will be able to log in to the system.

 Access to the various subsystems will be protected by a user log in screen that requires
a user name and password.

5.3 Coding Standard

General
Table: 5.1 General

No. Standard
1 AJAX programming, controls, and frameworks are not to be used
2 Web site is partitioned into restricted areas (protected using SSL) and public areas

Presentation Layer
Table: 5.2 Presentation Layer

No. Standard
3 Code-behind files are used rather than inline server-side script blocks
4 Code-behind files are not used as a container for Business Logic and/or Data Access
Logic
5 Master Pages are used as a means to create a consistent layout for web applications
6 Commonly used page elements are separated into Web User Controls and/or Web
Custom Controls
7 Web site is fully-functional when JavaScript is disabled in the browser

63
Mall Management System Implementation

Input Validation
Table: 5.3 Input Validations
No. Standard
8 Server-side validation is performed on all user inputs from sources such as HTML
controls, Query String, and Cookies
9 Input from field values are retained when form is redisplayed to the user after input
validation fails

Data Access
Table: 5.4 Data Access
No. Standard
10 Data paging is used for unbounded or long lists of data

Caching
Table: 5.5 Caching
No. Standard
11 Data that is frequently used but changes infrequently is cached using ASP.NET
Caching
12 Pooled resources (e.g. Database connections) are not cached
13 Sensitive data is not cached using ASP.NET caching or Application state

State Management
Table: 5.6 State Management
No. Standard
14 Sensitive information such as passwords and connection strings are not stored in any
client-side state
15 Web site is fully-functional when cookies are disabled in the browser
16 Session State is disabled for web applications and only enabled for individual pages
that require it
17 View State is disabled for web applications and only enabled for individual controls
that require it
18 View State is not enabled for data bound controls such as drop-down lists, check box
lists, grid views, repeaters, etc
19 The Data Grid server control is not used
20 Objects are not stored in the session state
21 Application state is only used for sharing application-wide read-only data for all clients

Exception Handling
Table: 5.7 Exception Handling
No. Standard
22 HTTP error codes are handled using custom error reporting pages
23 Unhandled exceptions are caught using an application-level global error handler

64
Mall Management System Implementation

Configuration
Table: 5.8 Configurations
No. Standard
24 Configurable application settings are stored in the web application's Web.config file
25 Request validation is enabled to prevent scripting attacks
26 Page output buffering is enabled
27 ASP.NET tracing and debugging are disabled
28 Database connection string should be encrypted

5.4 Store Procedure

65
Mall Management System Implementation

5.5 Data Access Layer

 A data access layer (DAL) is a layer of a computer program which provides simplified
access to data stored in persistent storage of some kind, such as an entity-relational
database.

 DAL might return a reference to an object (in terms of object-oriented programming) complete
with its attributes instead of a row of fields from a database table. This allows the client (or
user) modules to be created with a higher level of abstraction. This kind of model could be
implemented by creating a class of data access methods that directly reference a corresponding
set of database stored procedures. Another implementation could potentially retrieve or write
records to or from a file system. The DAL hides this complexity of the underlying data store
from the external world.

 For example, instead of using commands such as insert, delete, and update to access a specific
table in a database, a class and a few stored procedures could be created in the database. The
procedures would be called from a method inside the class, which would return an object
containing the requested values. Or, the insert, delete and update commands could be executed
within simple functions like registeruser or loginuser stored within the data access layer.

 Applications using a data access layer can be either database server dependent or independent.
If the data access layer supports multiple database types, the application becomes able to use
whatever databases the DAL can talk to. In either circumstance, having a data access layer
provides a centralized location for all calls into the database, and thus makes it easier to port
the application to other database systems.
 A Data Access layer can be an important part of a software application. Business applications
almost always need access to data from relational or object databases and the Java platform
offers many techniques for accessing this data, regardless of whether a data access layer is
used.
 Data Access layer concerns with taking the request from the user interface and according to the
logic, this layer provides the necessary data from the database.

66
Mall Management System Implementation

Figure 5.2: Data Access Layer

5.6 Business Logic Layer

 A business logic layer (BLL) is a software engineering practice of compartmentalizing.
The business logic layer is usually one of the tiers in a multitier architecture. It
separates the business logic from other modules, such as the data access layer (DAL)
and user interface (UI).

 The task of the business logic layer is to provide an interface to the business methods
of the system. The business layer applies the facade pattern and is split among different
managers , each one providing functionality needed for a specific module of the
system. Thus there exists one manager for user authorization and one manager for cost
analysis. Common functionality used in these managers are either encapsulated internal
helper-classes or provided by an abstract base class called the BaseManager, from
which every manager derives.

 Within a BLL objects can further be partitioned into business processes (business
activities) and business entities. Business process objects typically implement the

67
Mall Management System Implementation

controller pattern, i.e. they contain no data elements but have methods that orchestrate
interaction among business entities. Business entities typically correspond to entities in
the logical domain model, rather than the physical database model.

 Business Logic Layer concerns with performing the logic on input request from the
interface and pass this logic to the data tier.

 This layer is very important because it has to handle logic of request.

 In our system, the Transaction Module deals with making the business logic.

 Consider the following three tier system which is followed by us.

Figure: 5.3 Business Logic layer

68
Mall Management System Implementation

 The presentation tier

In the presentation layer, the code-behind mechanism for ASP.NET pages and
user controls is a prominent example of a layered design. The mark-up file defines the
look and layout of the web form and the code behind file contains the presentation
logic. It's a clean separation because both the mark-up and the code-behind layers
house specific sets of functionality that benefit from being apart. Designers don't have
to worry about messing up code to make user interface changes and developers don't
have to worry about sifting through the user-interface to update code.

 The data tier

You also see sub-layers in the data tier with database systems. Tables define the
physical storage of data in a database, but stored procedures and views allow you to
manipulate data as it goes into and out of those tables. Say, for example, you need to
demoralize a table and therefore have to change its physical storage structure. If you
access tables directly in the business layer, then you are forced to update your business
tier to account for the changes to the table. If you use a layer of stored procedures and
views to access the data, then you can expose the same logical structure by updating a
view or stored procedure to account for the physical change without having to touch
any code in your business layer.

 The business tier

And of course, this brings us to the topic of business objects and the Data
Access Layer (also known as the DAL), two sub-layers within the business tier. A
business object is a component that encapsulates the data and business processing logic
for a particular business entity. It is not, however, a persistent storage mechanism.
Since business objects cannot store data indefinitely, the business tier relies on the data
tier for long term data storage and retrieval. Thus, your business tier contains logic for
retrieving persistent data from the data tier and placing it into business objects and,
conversely, logic that persists data from business objects into the data tier. This is
called data access logic.

69
Mall Management System Testing

Chapter 6.
TESTING

 Project Testing is the process of executing a program or system with the intent of
finding errors. It involves any activity aimed at evaluating an attribute or capability of a
program or system and determining that it meets its required results.

 Testing can be stated as the process of validating and verifying that a software
program/application/product:

 Meets the requirements that guided its design and development;

 Works as expected; and
 Can be implemented with the same characteristics.

 Testing can be implemented at any time in the development process. However, most of
the test effort traditionally occurs after the requirements have been defined and the
coding process has been completed having been shown that fixing a bug is less
expensive when found earlier in the development process.

6.1 Testing Plan

Table 6.1: Testing Plan

Sr. Type of testing Responsibility Remarks

No.
1 Unit testing Independent code (working Checking whether the code is
in any circumstances) Flexible for further changes
to be made. Will it affect any
other module to any extent or
not. Perform alpha testing to
reduce bugs. N-Unit tool
used.

2 Integration Testing done to check To ensure that running the

Interdependencies of units. Current test affects the
No gaps in data flow. previous code to achieve
each test case. All fixes are
achieved.

3 System System as a whole working

on any environment.

70
Mall Management System Testing

4 Acceptance System should operate in the To ensure no gaps. To

manner expected. End user achieve the overall
maps his initial requirements functionality.
with the system.

6.2 Testing Strategy

 Checked all input systems and all functionality it’s working properly
 The database connections were checked and each time the database connection was opened
it was ensured that the connection was closed within finally block to optimize the database
performance
 Checked the application for login and for login send appropriate errors for each problem in
login
 Database work properly in manner of register
 If user enter wrong information for search he will get such errors
 End user need to directly upload information from excel file to database and its working
properly we have tried it many times and it gives complete information whether data is
updated or entered in database
 Advanced search option with other information is also working properly
 Change in settings also work properly and make updates in database properly

6.3 Testing Methods

 Black box testing which is the first step for testing

 White box testing which is the second step for testing

Black box testing takes an external perspective of the test object to derive test cases.
These tests can be functional or non-functional, though usually functional. The test designer
selects valid and invalid inputs and determines the correct output. There is no knowledge of
the test object's internal structure.

This method of test design is applicable to all levels of software testing: unit,
integration, functional testing, system and acceptance. The higher the level, and hence the
bigger and more complex the box, the more one is forced to use black box testing to simplify.
While this method can uncover unimplemented parts of the specification, one cannot be sure
that all existent paths are tested.

White box testing (a.k.a. clear box testing, glass box testing, transparent box testing,
and translucent box testing or structural testing) uses an internal perspective of the system to
design test cases based on internal structure. It requires programming skills to identify all paths
through the software. The tester chooses test case inputs to exercise paths through the code and
determines the appropriate outputs.

71
Mall Management System Conclusion & Future Work

Chapter 7.
CONCLUSION & FUTURE WORK

7.1 Conclusion
Mall Management System will provide an efficient and effective way for betterment of speed
and quality of financial and social communication between mall owners and shop keepers.
As this is a different and new concept, this system will be successful in market.

 System satisfies all the requirements for which the company developed the system.
 System Provides all the facilities like chatting,send-receive message,view
profile,genrate event,advertisement.
 Non-Users can give their feedback by using social network and also by send
message to admin of the system.
 Only authenticated clients can Login and can view Personal details of Site. So that
unauthorized person cannot misuse it.
 It is easy to operate and user-friendly.

All the objectives that had been charted out in the initial phases were achieved
successfully.

7.2 Future Enhancement

o The next versions of Mall Management System may include Online Shopping, Direct
communication with users for non-users,Payment via PayPal and some more
functionality based on feedbacks received.

72
 REFERENCES

Books:

[1] Matthew MacDonald, "Beginning ASP.NET 3.5 in C# 2008: From Novice to

Professional, Second Edition" Published by Apress 2007.

[2] Herbert Schildt, "C# 2.0 - The Complete Reference, Second Edition" Published by
McGraw-Hill/Osborne 2006.

[3] Ken Cox, "ASP.NET 3.5 For Dummies" Published by Wiley Publishing, Inc. 2008.

[4] John W. Gosney, "ASP Programming For The Absolute Beginner" Published by
Premier
Press, Inc. 2002.

[5] Ian Griffiths and Matthew Adams, ".NET Windows Forms In a Nutshell"
Published by O'Reilly 1999.

[6] A. Keyton Weissinger, "ASP In a Nutshell" Published by O'Reilly 1999.

Websites:

[7] "ASP.NET AJAX Control Toolkit",

http://www.asp.net/ajaxlibrary/AjaxControlToolkitSampleSite/

[8] "ASP.NET Server Controls Tutorials",

http://www.dotnetfunda.com/tutorials/controls/

[9] "ASP.NET, C#.NET, JavaScript, Gridview, SQL Server, Ajax examples",

http://www.aspdotnet-suresh.com/

[10] "Events - ASP.NET Tutorial",

http://asp.net-tutorials.com/basics/events/

[11] "Free asp.net code , vb code , c# code , sample aspx code examples",
http://www.aspxcode.net/

[12] "ASP.NET Queries",

http://stackoverflow.com/questions/tagged/asp.net

[13] "Microsoft Visual Studio C# Help",

http://msdn.microsoft.com/library/vstudio/a72418yk

73
 [14] "ASP.NET Tutorials",
http://www.tutorialspoint.com/asp.net/index.htm

[15] "ASP.NET Tutorial, Help and Source code",

http://asp.net-informations.com/

[16] "ASP.NET Tutorials",

http://www.aspspider.com/tutorials/

[17] "ASP.NET Tutorial",

http://www.w3schools.com/aspnet/default.asp

74

View publication stats