Emall

Project Id: 05 E-Mall Management System

E-Mall Management
System


A
PROJECT REPORT ON
E-MALL MANAGEMENT SYSTEM

For the partial Fulfillment of the
Requirements for the award of degree in
DIPLOMA OF ENGINEERING
IN
INFORMATION TECHNOLOGY

Submitted By:

Project Id: 05

Singh Akanksha D.
096140316016
Prajapati Dipal A.
096140316077

DEPARTMENT OF INFORMATION TECHNOLOGY
GOVERNMENT POLYTECHNIC FOR GIRLS, AHMEDABAD.

INTERNAL GUIDE: EXTERNAL GUIDE:
Abhilasha Shrivastav Mitul Shah
Information Technology Sai Management & Education services
Government Polytechnic for Girls Ahmedabad, www.smesindia.com

GPG(I.T.) I


A
PROJECT REPORT ON
E-MALL MANEGMENT SYSTEM

For the partial Fulfillment of the
Requirements for the award of degree in
DIPLOMA OF ENGINEERING
IN
INFORMATION TECHNOLOGY

Submitted By:
Singh Akanksha D.
096140316016
Prajapati Dipal A.
096140316077

DEPARTMENT OF INFORMATION TECHNOLOGY
GOVERNMENT POLYTECHNIC FOR GIRLS , AHMEDABAD.

GPG(I.T.) II


Certificate

This is to certify that Ms. Akanksha D. Singh and Ms. Dipal A. Prajapati having
Enrolment No: 096140316016 and 096140316077 respectively. has completed Part-I IDP Project
work. Having title “E-Mall Management System”. They have undergone the process of shodh
yatra, literature survey and problem definition. They are supposed to carry out the residue IDP Part-II
work on same problem during Semester-VI for the final fulfillment of the IDP work which is
prerequisite to complete Diploma Engineering.

Date:

Guide – IDP Head of Department

Abhilasha Shrivastav Harsha Chauhan

ACADEMIC YEAR: 2011-2012

GPG(I.T.) III


Certificate

This is to certify that Ms. Akanksha D. Singh and Ms. Dipal A. Prajapati having
Enrolment No: 096140316016 and 096140316077 respectively has completed Part-II IDP Project
work. Having title “E-Mall Management System”. They have undergone the process of shodhyatra
literature survey and problem definition. They have completed their project within a given time limit.

Date:

Guide – IDP Head of Department

Abhilasha Shrivastav Harsha Chauhan

ACADEMIC YEAR: 2011-2012

GPG(I.T.) IV


PREFACE

As a part of this diploma 6th semester, students have to undergo a project. This particular project
allows a student to implement what she has learned within the four walls of classroom. It is here
that the caliber of the student is tested to find her flexibility for rigorous tasks assigned to her in
future.
This report that were submitting intends to highlight our versatility in sub staining the pulls and
pressure of day to day professional life put to perspectives the fact that we are capable enough to
deliver whenever a challenge is thrown to us.

GPG(I.T.) VI


Acknowledgements

Inevitably all those who made contribution and facilitate in the completion of a project report, we
would like to express our gratitude to them I would like to take this opportunity to express our
appreciation and a deep sense of being thankful to our Head Of I.T Department Mrs. Harsha
Chauhan and Mrs. Abhilasha Shrivastav who help for project.

I am thankful to the staff of department of Information Technology for their encouragement
and help, without which I could not have been able to complete the project in such a short period.

Thanking You
Singh Akanksha D.
Prajapati Dipal A.

GPG(I.T.) VII


Abstract
The E-Mall Management System is a web based application intended for online retailers. The
main objective of this application is to make it interactive and its ease of use. It would make
searching, viewing and selection of a product easier. It contains a sophisticated search engine for
users to search for products specific to their needs. The search engine provides an easy and
convenient way to search for products where a user can Search for a product interactively and the
search engine would refine the products available based on the user‘s input. The user can then
view the complete specification of each product. They can also view the product reviews and
also write their own reviews. The application also provides a drag and drop feature so that a user
can add a product to the shopping cart by dragging the item in to the shopping cart. The main
emphasis lies in providing a user-friendly search engine for effectively showing the desired
results and its drag and drop behavior.

GPG(I.T.) VIII


INDEX

SR_NO CHAPTER PAGE NO

Chapter 1 Introduction……………………………………………………. 1
1.1 Project summary……………………………………………….. 2
1.2 Purpose: goals & objectives…………………………………… 2
1.3 Project Scope……………………………………....................... 3
1.4 Technologies and literature review of past work/system……… 4

Chapter 2 Project Management…………………………………………… 12
2.1 Project planning and scheduling………………………………. 13
2.1.1 Project development approach………………………………… 13
2.1.2 Project plan including milestone, deliverables, roles, responsibilities 14
and dependencies……………………………...
2.1.3 Schedule Representation……………………………………… 15
2.2 Risk management……………………………………………… 15
2.2.1 Risk identification……………………………………………... 16
2.2.2 Risk analysis…………………………………………………… 17
2.2.3 Risk planning………………………………………………….. 18
2.3 Estimation…………………………………………………….. 19
2.3.1 Effort estimation………………………………………………. 19
2.3.2 Cost analysis…………………………………………………… 20

Chapter 3 System Requirement Study…………………………………….. 22
3.1 User characteristics……………………………………………. 23
3.2 Hardware and software requirement………………………….. 23
3.3 Constraints…………………………………………………….. 24

Chapter 4 System Analysis………………………………………………... 26
4.1 Study of current system………………………………………... 27
4.2 Problem and weakness of current system……………………... 27
4.3 Requirements of new system………………………………….. 27
4.4 Feasibility study……………………………………………….. 33
4.5 Requirements validation………………………………………. 34
4.6 Function of system…………………………………………….. 35
4.6.1 Use case diagram………………………………………………. 35
4.7 Data modeling…………………………………………………. 37

GPG(I.T.) IX


4.7.1 E-R diagram…………………………………………………… 38
4.7.2 System activity diagram………………………………………. 39
4.7.3 Data dictionary………………………………………………… 42
4.8 Functional and behavioral modeling…………………………... 48
4.8.1 Data flow diagram……………………………………………... 48
4.8.3 Control Flow Diagram 55
4.9 Main modules of new system………………………………….. 56
4.10 Selection of hardware and software and justification…………. 56

Chapter 5 Testing…………………………………………………………… 58
5.1 Testing Plan……………………………………………………….. 59
5.2 Testing strategy…………………………………………………… 59
5.3 Testing Methods…………………………………………………... 59
5.4 Test Cases………………………………………………………… 60

Chapter 6 Screen Shots……………………………………………………… 62

Chapter 7 Limitation & Future Enhancement…………………………….. 88

Chapter 8 Conclusion and Discussion……………………………….......... 90

GPG(I.T.) X

SAI MANAGEMENT & EDUCATIONAL SERVICES

COMPANY PROFILE
It Is Our Pleasure to introduce you to SMES (Sai Management & Educational Services) as an IT
and Management Solution Provider. The company commenced its operation on date & year of
commencement with a vision to provide IT and Management Solution in the country, starting
from Ahmedabad.
SMES is an established provider of IT Training in areas of Computer Hardware, Networking,
Software Programming, Multimedia, ERP, SEO, and Software Testing. SMES is the fastest
growing company in the field of Information Technology Training, based in Gujarat (INDIA).
The company was launched by well experienced IT Professionals from the industry, with an
exposure to the other important and necessary functional areas like Marketing, Administration,
Manpower Management and Quality Control
The proprietors of the company were the first to successfully run HIGH END courses like ERP,
VLSI, SEO, and SOFTWARE TESTING.
Today, SMES has 3 centers in Gujarat and is imparting training in the latest areas of Computer
Hardware, Networking, Software Programming, Multimedia, ERP, SEO and Software Testing.
The company has well furnished centers, strong technical and non technical (administration and
Marketing) team and runs professionally. The company has already applied for ISO Certification
which it will get very soon.
As one of the fastest growing System Integrators In the industry, SMES strives to provide
products and services that meet customers‘ evolving needs- we provide.
We are in corporate training and development in IT business software like ERP, manufacturing
inventory, sales and distribution software as well as HR solution software.
Corporate Training-
IT Industry,
Service Industry
(Telecallers, Call center, BPO)
Software consultation and designing –―Our Quality Policy is to meet our customer requirements
by delivering high quality software solutions on time with in budgets.‖
Insurance, Banks

GPG(IT) XI

Web Management and portal management

Website development and designing in advance environment like animation flash etc.
Web related Services, Software Development & also developing Medium and Small Websites,
Hosting for Small and Corporate Clients.
ERP system-Designing and providing training and for
School management software for and online web based school support system,
Textile - software for manufacturing, trading, inventory, finance and HR
Software for NGO operation, prospects and planning
Software support system for Military administration, HR and research.
Specially designed estimation portal for civil engineering useful for AMC, Nagarpalika‘s, MES,
GEB, GHB, and other construction public sector.
Academic Support system for final year technical and management students
Offering live projects, training in advance software and placement processes for student of
following category.
BCA, MCA,
MscIT,
BE (IT), (Comp), (EC.),
Mechatronics, Students
Diploma,
MBA students (Capacity, building, Talent profiling)
Talent profiling for students, professional, seeks for job as well talent profile activity for existing
employees of organization for re-structuring change management and diversification activity.
Human resources providing technically qualified, trained and experienced manpower in all areas
and human capital management in IT industry, service industry, call center, BPO, KPO

Our commitment to serve quality has leaded us to win customers from various business fields
and to provide maximum customer satisfaction by prompt, regular, and timely after-sales Service
support.

GPG(IT) XII

SMES is supported by CORE TEAM to meet all objectives. Our technical team comprises of
well-qualified engineers who not only have knowledge of all products but also capable to
understand customer‘s Specific requirements.

OUR Valued Customer

NIRMA Limited
BAKERI Urban Development Pvt Ltd.
ISBM – Managers and Telecallers staff training
IBMR (Institute Of Business Management & Research)
DA – IICT (Dhirubhai Ambani Institute of Information & Communication Technology) HR,
Oracle, JAVA and other hi-tech software
Aditya Infotech
Pioneer Infotech
PCPL
SICS
Sysnapse Infotech
And many more….

Development
Our Exclusive Development Division focuses on equipping itself in the emerging technologies to
offer best in bread technical solutions for our clients. We have over the period of time acquired
expertise in the following areas: Microsoft .NET, PHP, SharePoint, MS CRM, Java, J2EE,
Struts, spring, Hibernate to name a few.

Consulting
At Prelude, Guiding clients through the difficult solution search process is what we do best.
Customer Satisfaction means most to us and we term it our top priority. While Customers are
spending Millions of Dollars towards research and development of software, most of them find it
tough in getting the right partner in delivering qualified quality people to them. With Prelude one

GPG(IT) XIII

Can be rest assured that the spending will be more than it‘s worth. We will provide the talent you
need to achieve success. We are part of your team. We deliver the best. Finding the right people
has always been like searching ―needle out of haystack‖ which we are good at.
Prelude has always been investing substantially on building resources and maintains one of the
most extensive and diverse talent pools in the industry. We screen thousands of prospective
candidates on your behalf. We carefully match your detailed spectrum of technical attributes
with those that our candidates possess. In our effort to target the specific expertise you require,
we assess experience, availability and attitude. In the end, we only submit better candidates that
closely match your requirements. We never waste your time.

GPG(IT) XIV

Project Id: 05 Introduction

1.0 INTRODUCTION

1.1 Project Summary

 STUDY OF CURRENT SYSTEM
After studying current system we find that current system has less facility and it takes
much time to perform the operation. Current system cannot provide the central data
storage and storage and it leads to the data redundancy. Current system is not also real-
time so it takes much human hours to perform the task.

 PROBLEM AND WEAKNESS OF CURRENT SYSTEM

The E-mall Management System application enables vendors to set up online shops, customers to
browse through the shops, and a system administrator to approve and reject requests for new
shops and maintain lists of shop categories.

Also on the agenda is designing an online shopping site to manage the products in the shop and
also help customers purchase them online without having to visit the shop physically.

Our online shopping mall will use the internet as the sole method for selling goods to its
consumers. The consumer will be in complete control of his/her shopping experience by using the
―unique storefront‖ concept. Shopping will be highly personalized and the mall will provide
lower prices than most competitors. This, in brief, is a description of our product which will
showcase a complete shopping experience in a small package.

1.2 PURPOSE: GOALS & OBJECTIVES:-

 GOALS :

 This project envisages bridging the gap between the seller, the retailer and the customer.

 The ―E-Mall Management System‖ web application is intended to provide complete
solutions to not only administrator and vendors but also to the customers through a single
get way using the internet as the sole medium. It will enable vendors to setup online
shops, customer to browse through the shop and purchase them online without having to
visit the shop physically. The administration module will enable a system administrator to
approve and reject requests for new shops and maintain various lists of shop category.

GPG(I.T.) 2


 Simplicity of design, execution and operation is main goal of this unique mall.
Additionally, the efficiency of this online business over other existing, similar ventures
and traditional brick-and-mortar shops is a hallmark of our E-Mall Management System.

 OBJECTIVES

Today the internet and its boom have created a new economic scenario that not only stresses on
the classical concept of the ―product‖ but also on the modern concept of ―service‖. It is this level
of service that dictates whether a commercial venture will succeed or not in the market. To
provide a high accessibility of service we will design the online shopping website, so that
potential customers need not go to a physical shop to buy products or services. They just need to
online to complete their purchases. Unlike the prevailing ―brick and mortar‖ shops which have
physical existence, we will operate solely from cyberspace.

Most current systems have a physical foundation that is the root cause to quite a number of
problems. By maintaining multiple store fronts, itself being an expensive proposition, store prices
are forced to rise. Thus, by using our product, our clients‘ competitors are at a disadvantage
because their costs are significantly higher than our costs, allowing our clients to sell the same
goods at a lower price. As people become more accustomed to using the internet, they view
ordering products and services online as a time-saving and cost-saving experience, which is the
very essence of our online shopping system.

Shopping has long been considered a recreational activity by many. Shopping online is no
exception. The goal of this application is to develop a web based interface for online retailers. The
system would be easy to use and hence make the shopping experience pleasant for the users. The
objective of this application is:
 to use web based interface where users can search for products, view a
complete description of the products and order the products.

their needs. The search engine would list a set of products based on the search term and the
user can further filter the list based on various parameters.
 An AJAX enabled website with the latest AJAX controls giving attractive and interactive look
to the web pages and prevents the annoying post backs.
 Drag and Drop feature which would allow the users to add a product to or remove a product
from the shopping cart by dragging the product in to the shopping cart or out of the shopping
cart.
 A user can view the complete specification of the product along with various images and also
view the customer reviews of the product. They can also write their own reviews.

1.3 SCOPE:-

 Secure registration and profile management facilities for Customers

GPG(I.T.) 3


 Browsing through the e-Mall to see the items that are there in each category of
products like Apparel, Kitchen accessories, Bath accessories, Food items etc.

 Adequate searching mechanisms for easy and quick access to particular products
and services.

 Creating a Shopping cart so that customers can shop ‗n‘ no. of items and checkout
finally with the entire shopping carts.

 Regular updates to registered customers of the OSM about new arrivals.

 Uploading ‗Most Purchased‘ Items in each category of products in the Shop like
Apparel, Kitchen accessories, Bath accessories, Food items etc.

 Strategic data and graphs for Administrators and Shop owners about the items that
are popular in each category and age group.

 Maintaining database of regular customers of different needs.

 Shop employees are responsible for internal affairs like processing orders, assure
home delivery and getting customer's delivery-time feedback.

 Feedback mechanism, so that customers can give feedback for the product or
service which they have purchased. Also facility rating of individual products by
relevant customers. Also feedback can be given on the performance of particular
vendors and the entire mall as well.

 Adequate payment mechanism and gateway for all popular credit cards, cheques
and other relevant payment options, as available from time to time.

1.4 TECHNOLOGIES AND LITERATURE:-

 Introduction of .NET
.Net is just a one platform on which you can create any application. Microsoft‘s .NET
initiative is broad-based and very grand. It includes the .NET Framework, which encompasses the
languages and execution platform, plus extensive class libraries, providing rich built-in
functionality.

Besides the core .NET Framework, the .NET initiative includes protocols (such as the Simple
Object Access Protocol, commonly known as SOAP) to provide a new level of software
integration over the Internet, via a standard known as Web Services.

GPG(I.T.) 4


Tools like designers, wizards, debuggers, and profilers, and since the object models are at the
runtime level, such tools can be designed to work across all languages that use the CLR. It is
expected that third parties will produce a host of such tools.

 An Overview of the .NET Framework
First and foremost, .NET is a framework that covers all the layers of software
development above the operating system level. It provides the richest level of integration among
presentation technologies, component technologies, and data technologies ever seen on a
Microsoft, or perhaps any, platform

Second, the entire architecture has been created to make it as easy to develop Internet
applications as it is to develop for the desktop.

The .NET Framework actually ―wraps‖ the operating system, insulating software
developed with .NET from most operating system specifics such as file handling and memory
allocation. This prepares for a possible future in which the software developed for .NET is
portable to a wide variety of hardware and operating system foundations.

Fig: Net Framework
The major components of the Microsoft .NET Framework are shown in Figure 1.2. The
framework starts all the way down at the memory management and component loading level and
goes all the way up to multiple ways of rendering user and program interfaces. In between, there
are layers that provide just about any system-level capability that a developer would need.

The Common Language Runtime
We are all familiar with runtimes—they go back further than DOS languages. However, the
common language runtime (CLR) is as advanced over traditional runtimes as a machine gun is
over a musket. Figure 1-2 shows a quick diagrammatic summary of the major pieces of the CLR.
GPG(I.T.) 5


The Intermediate Language
All the .NET languages are compiled into another lower-level language before the code is
executed. This lower-level language is the MSIL (Microsoft Intermediate Language), or just IL.
The CLR, the engine of .NET, uses only IL code. Because all .NET languages are designed based
on IL, they all have profound similarities. This is the reason that the C# and VB .NET languages
provide essentially the same features and performance. In fact, the languages are so compatible
that a web page written with C# can use a VB .NET component in the same way it uses a C#
component, and vice versa.

Fig: Language Compilations in. NET

GPG(I.T.) 6


For the most part, .NET developers don‘t need to think about how the CLS works, even though
they rely on it every day. Figure 1-5 shows how the .NET languages are compiled to IL. Every
EXE or DLL file that you build with a .NET language contains IL code. This is the file you
deploy to other computers

The CLR runs only IL code, which means it, has no idea which .NET language you
originally used. Notice, however, that the CLR actually performs another compilation step—it
takes the IL code and transforms it to native machine language code that‘s appropriate for the
current platform. This step occurs when the application is launched, just before the code is
actually executed. In an ASP.NET application, these machine-specific files are cached while the
web application is running so they can be reused, ensuring optimum performance.

 The .NET Class Library
 The .NET class library is a giant repository of classes that provide prefabricated
functionality for everything from reading an XML file to sending an e-mail message.
 If you‘ve had any exposure to Java, you may already be familiar with the idea of a class
library. However, the .NET class library is more ambitious and comprehensive than just
about any other programming framework.

 Any .NET language can use the .NET class library‘s features by interacting with the right
objects. This helps encourage consistency among different .NET Languages and removes
the need to install numerous components on your computer or web server. Some parts of
the class library include features you‘ll never need to use in web applications (such as the
classes used to create desktop applications with the Windows interface).

 Other parts of the class library are targeted directly at web development, such as those
used for web services and web pages. Still more classes can be used in various
programming scenarios and aren‘t specific to web or Windows development. These
include the base set of classes that define common variable types and the classes for data
access, to name just a few.

GPG(I.T.) 7


Fig: .Net Framework Class Library

 Features of Asp.Net

i. Data Control
Data access in ASP.NET 2.0 can be accomplished completely declaratively (no code) using the new
data-bound and data source controls. There are new data source controls to represent different data
back ends such as SQL database, business objects, and XML, and there are new data-bound controls
for rendering common UI for data, such as grid view, details view, and form view.

ii. Navigation Controls
Navigation controls provide common UI for navigating between pages in your site, such as tree
view, menu, and sitemap path. These controls use the site navigation service in ASP.NET 2.0 to
retrieve the custom structure you have defined for your site.

iii.Login Controls
The new login controls provide the building blocks to add authentication and authorization-based
UI to your site, such as login forms, create user forms, password retrieval, and custom UI for
logged in users or roles. These controls use the built-in membership and role services in
ASP.NET 2.0 to interact with the user and role information defined for your site.

iv. Web Part Controls
Web parts are an exciting new family of controls that enable you to add rich, personalized content
and layout to your site, as well as the ability to edit that content and layout direct from your
GPG(I.T.) 8


application pages. These controls rely on the personalization services in ASP.NET 2.0 to provide
a unique experience for each user in your application.

v. Master Pages
This feature provides the ability to define common structure and interface elements for your site,
such as a page header, footer, or navigation bar, in a common location called a "master page", to
be shared by many pages in your site. In one simple place you can control the look, feel, and
much of functionality for an entire Web site. This improves the maintainability of your site and
avoids unnecessary duplication of code for shared site structure or behavior.

vi. Themes and Skins
The themes and skins features in ASP.NET 2.0 allow for easy customization of your site's look-
and-feel. You can define style information in a common location called a "theme", and apply that
style information globally to pages or controls in your site. Master Pages improves the
maintainability of your site and avoid unnecessary duplication of code for shared styles.

vii. Personalization
Using the new personalization services in ASP.NET 2.0 you can easily create customized
experiences within Web applications. The Profile object enables developers to easily build
strongly-typed, sticky data stores for user accounts and build highly customized, relationship
based experiences. At the same time, a developer can leverage Web Parts and the personalization
service to enable Website visitors to completely control the layout and behavior of the site, with
the knowledge that the site is completely customized for them. Personalization scenarios are now
easier to build than ever before and require significantly less code and effort to implement.

viii. Localization
Enabling globalization and localization in Web sites today is difficult, requiring large amounts of
custom code and resources.ASP.NET 2.0 and Visual Studio 2005 provide tools and infrastructure
to easily build Localizable sites including the ability to auto-detect incoming locale's and display
the appropriate locale based UI. Visual Studio 2005 includes built-in tools to dynamically
generate resource files and localization references. Together, building localized applications
becomes a simple and integrated part of the development experience

ix. Back End - Microsoft SQL Server 2005
SQL Server 2005 provides vast range of new features and a lot of improvements, which SQL
Server 2000 aspirants were always looking for. With SQL Server 2005, users and information
technology (IT) professionals across your organization will benefit from reduced application
downtime, increased scalability and performance, and tight yet flexible security controls. SQL
Server 2005 also includes many new and improved capabilities to help make your IT staff more
productive.

x. Manageability
SQL Server 2005 makes it simpler and easier to deploy, manage, and optimize enterprise data and
analytical applications. As an enterprise data management platform, it provides a single
management console that enables data administrators anywhere in your organization to monitor,
manage, and tune all of the databases and associated services across your enterprise. It provides
GPG(I.T.) 9


an extensible management infrastructure that can be easily programmed using SQL Management
Objects, enabling users to customize and extend their management environment and independent
software vendors (ISVs) to build additional tools and functionality to further extend the
capabilities that come out of the box.

xi. Fast Recovery

SQL Server 2005 improves the availability of SQL Server databases with a new and faster
recovery option. Users can reconnect to a recovering database after the transaction log has been
rolled forward. Earlier versions of SQL Server required users to wait until incomplete transactions
had rolled back, even if the users did not need to access the affected parts of the database.

xii. Replication

Replication is designed to increase data availability by distributing the data across multiple
database servers. Availability is increased by allowing applications to scale out the SQL Server
read workload across databases. SQL Server 2005 offers enhanced replication using a new peer-
to-peer model that provides a new topology in which databases can be synchronized transitionally
with any identical peer database.

xiii. Scalability

Scalability advancements such as table partitioning, snapshot isolation and 64-bit support will
enable you to build and deploy your most demanding applications using SQL Server 2005. The
partitioning of large tables and indexes significantly enhances query performance against very
large databases.

xiv. Table and Index Partitioning

Table and index partitioning eases the management of large databases by facilitating the
management of the database in smaller, more manageable chunks. While the concept of
partitioning data across tables, databases, and servers is not new to the world of databases, SQL
Server 2005 provides a new capability for the partitioning of tables across file groups in a
database. Horizontal partitioning allows for the division of a table into smaller groupings based on
a partitioning scheme. Table partitioning is designed for very large databases, from hundreds of
gigabytes to terabytes and beyond.

xv. Security

SQL Server 2005 makes significant enhancements to the security model of the database platform,
with the intention of providing more precise and flexible control to enable tighter security of the
data. A considerable investment has been made in a number of features to provide a high level of
security for your enterprise data including the following:

 Enforcing policies for SQL Server login passwords in the authentication space.

GPG(I.T.) 10


 Providing for more granularities in terms of specifying permissions at various scopes is the
authorization space.
 Allowing for the separation of owners and schemas in the security management space.

xvi. Authorization

A new security model in SQL Server 2005 allows administrators to manage permissions at a
granular level and at a designated scope, making management of permissions easier as well as
ensuring that the principle of least privileges is upheld. SQL Server 2005 lets you specify a
context under which statements in a module execute. This feature also acts as an excellent
mechanism for granular permission management.

xvii. Authentication

SQL Server 2005 clustering supports Kerberos authentication against a SQL Server 2005 virtual
server. Administrators can specify Microsoft Windows-style policies on standard logins so that a
consistent policy is applied across all accounts in the domain.

xviii. Expand Language and Support

Because the common language runtime (CLR) is hosted in the database engine, developers can
choose from a variety of familiar languages to develop database applications, including Transact-
SQL, Microsoft Visual Basic .NET, and Microsoft Visual C# .NET. Additionally, CLR hosting
provides developers with increased flexibility with user-defined types and functions. The CLR
also provides opportunities to use non-Microsoft code for rapid database application
development.

xix. XML Support

Advancements such as the native XML data type and XQuery help organizations seamlessly
connect internal and external systems. SQL Server 2005 supports both relational and XML data
natively, so enterprises can store, manage, and analyze data in the format that best suits their
needs. Support for existing and emerging open standards such as Hypertext Transfer Protocol
(HTTP), XML, Simple Object Access Protocol (SOAP), XQuery, and XML Schema definition
language (XSD) also facilitate communication across extended enterprise systems.

REVIEW OF PAST WORK/SYSTEM

Online stores must describe products for sale with text, photos, and multimedia files, whereas in a
physical retail store, the actual product and the manufacturer's packaging will be available for
direct inspection (which might involve a test drive, fitting, or other experimentation).

GPG(I.T.) 11


Some online stores provide or link to supplemental product information, such as instructions,
safety procedures, demonstrations, or manufacturer specifications. Some provide background
information, advice, or how-to guides designed to help consumers decide which product to buy.
Some stores even allow customers to comment or rate their items. There are also dedicated review
sites that host user reviews for different products. Reviews and now blog gives customers the
option of shopping cheaper organize purchases from all over the world without having to depend
on local retailers.
There are large numbers of commercial Online Shopping websites offering large number of
products tailored to meet the shopping interests of large number of customers. These online
marketplaces have thousands of products listed under various categories.

The basic problems with the existing systems are the non-interactive environment they provide to
the users. The use of traditional user interfaces which make continuous post backs to the server;
each post back makes a call to the server, gets the response and then refreshes the entire web form
to display the result. This scenario adds an extra trade off causing a delay in displaying the results.

A search engine that would display the results without allowing the users to further filter the
results based on various parameters. Uses of traditional and non user friendly interfaces are hard
to use.

So we have decided to make E-mall which provides services not only to Administrator of mall but
also to the shop-owner and customers join with the mall.

GPG(I.T.) 12

Project Id: 05 Project Management

2.0 PROJECT MANAGEMENT

2.1 PROJECT PLANNING AND SCHEDULING

2.1.1 Project Development Approach

The activities we followed for this project is listed below:

 Planning the work or objectives
 Analysis & Design of objectives
 Assessing and controlling risk (or Risk Management)
 Estimating resources
 Allocation of resources
 Organizing the work
 Database Designing
 Form Design

The Process Paradigm we used for our project is Incremental Model.

 The Incremental Software Process 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. In incremental model first increment is called core product. In core product basic
requirements are added but some unknown supplementary features remains undelivered. This
core product is used by customer to evolutes the system and next increment is planned to
develop.

During first increment analysis phase, customer and developers specifies as many requirements
as possible and prepare documentation. Now a first version of product with minimal and
essential feature is launched to market. Based on the feedback and experience with this version,
list of additional features are added. This process is repeated following the delivery of each
increment, until the complete product is produced.

With this approach first model may be available within few weeks or months. In this model, less
cost and time is required to develop first increment called core product. Less risk is occurred to
develop the smaller systems represented by the increments. Incremental funding is allowed,
means only one or two increments might be funded when the program starts. It can results in
better testing, because testing each increment is likely to be easier than testing entire system. The
feedback providing at each increment is useful for determining the final requirement of system.

GPG(I.T.) 13


It is more suitable where sufficient staff is not available. Once a core product is well received
than future and further remaining increment can be implemented by adding additional staff. This
model is also used when requirements cannot or will not be well specified.

System/information Increment 1
engineering
Delivery of 1st increment
Analysis Design Code Test

Increment 2
Delivery of 2nd increment

Increment 3

Delivery of 3rd increment

Increment 4
Delivery of
4th
increment

Calendar Time

Fig: The Incremental Process Model

2.1.2 Project Plan

In this project, we went through Module Wise Completion. First we did analysis of first module;
we went through all the requirements for first module that is Admin Module. By this analysis we
decided field of all the tables of Admin Module. Then we started Database Design. After
competing it we started with the design of all forms of this module. Then we did coding and
finally validations and testing of forms that we made.

After completing the first module we started the same procedure for the Member Module. After
that we completed User Module.
Between this we did settings forms e.g. Change theme, change background color of the main
screen etc. There was continuously interaction with the client that was very beneficial for us.

GPG(I.T.) 14


When we completed whole project we started testing the whole project for final verification.
Then we started documentation of our project. Finally, we completed the project with client‘s
satisfaction.
2.1.3 Schedule Representation

Id Task Name Start Finish Duratio July- Sep-Oct Nov- Jan- Feb- Mar-Apr
n Aug 2011 Dec Feb Mar 2012
2011 2011 2012 2012

1 Study user 5/7/11 28/8/11 8w
Requirements
and
Understood the
project detail

2 Requirement 1/9/11 28/10/1 8w
Analysis 1

3 DB Design 4/11/1 29/12/1 8w
1 1
4 Coding 11/1/1 22/2/12 5w
2
5 Testing 25/2/1 21/3/12 7.5w
2
6 Documentation 22/3/1 30/4/12 8w
2

Fig: Time-line chart of E-Mall Management System

2.2 RISK MANAGEMENT

Risk management is the area that tries to ensure that the impact of risks on cost, quality and
schedule is reduced. Risk management can consider as dealing with the possibility and actual
occurrence of those events that are not regular or commonly expected that is they are
probabilistic. So risk management begins where a normal project management ends.

Risk management has to deal with identifying the undesirable events that occurs, the
probability of their occurring, and the loss if any undesirable event is occurs. Once this is known
then strategies can be formulated for either reducing the probability of the risk or reducing the
effect of the risk. Risk management involves several important steps, each of which is illustrated
in given figure.

GPG(I.T.) 15


Risk Identification

Risk Assessment Risk Analysis

Risk Prioritization
Risk Management
Activities Risk Mitigation

Risk Control Risk Monitoring

Risk Management
Planning

Fig: Risk Management Activities

Steps in the risk management process

Establishing the context involves
1. Planning the remainder of the process.
2. Mapping out the following: the scope of the exercise, the identity and objectives of
stakeholders, and the basis upon which risks will be evaluated.
3. Defining a framework for the process and an agenda for identification.
4. Developing an analysis of risk involved in the process.

2.2.1 Risk Identification

Risk Identification is the first step in risk assessment which identifies all the different risk for
a particular project. The objective of the risk team is to first of all identify the application
oriented, non-environmental risks associated with the application system. By identifying known
and predictable risks, the project manager takes a first step towards avoiding them when possible
and controlling them when necessary.

There are two types of risk: Generic risk and product-specific risk. Generic risks are potential
threat of every software project. Product specific risks can be identified only by those with a
clear understanding of the technology, the people and the environment that is specific to the
software that is to be built.

Risk identification can be facilitated with the help of a checklist of common possible
risk areas of software projects or by examining the contents of organizational database of
previously identified risk. Other methods are surveys, meeting and brainstorming, and
reviews of plans, process and work product.

GPG(I.T.) 16


2.2.2 Risk Analysis

Once risks have been identified, they must then be assessed as to their potential severity of
loss and to the probability of occurrence. Regardless of the prevention techniques employed,
possible threats that could arise inside or outside the organization need to be assessed.
Regardless of the type of threat, the goals of business recovery planning are to ensure the safety
of customers, employees and other personnel during and following a disaster.

The relative probability of a disaster occurring should be determined. Here by the first risk
can occur because of the less of communication with all branches of Apollo for requirement
fulfillment .for example, the company may not have interacted with the branch of Apollo in
U.S.A. and that branch needs some additional functionality of the software.

If by mistake any person threat Administrator password then he can change the data in
software and can leak information. Same thing occurs if the wrong user is authorized.

The software may be in problem by natural threat e.g. internal flooding, external flooding,
internal fire, external fire etc.

 Disaster Prevention

Because a goal of business recovery planning is to ensure the safety of personnel and assets
during and following a disaster, a critical aspect of the risk analysis process is to identify the
preparedness and preventive measures in place at any point in time. Once the potential areas of
high exposure to the organization are identified, additional preventative measures can be
considered for implementation.

Disaster prevention and preparedness begins at the top of an organization. The attitude of
senior management toward security and prevention should permeate the entire organization.
Therefore, management‘s support of disaster planning can focus attention on good security and
prevention techniques and better prepare the organization for the unwelcome and unwanted.

Disaster prevention techniques include two categories:

 Procedural prevention

Procedural prevention relates to activities performed on a day-to-day, month-to-month, or
annual basis, relating to security and recovery. Procedural prevention begins with assigning
responsibility for overall security of the organization to an individual with adequate competence
and authority to meet the challenges. The objective of procedural prevention is to define
activities necessary to prevent various types of disasters and ensure that these activities are
performed regularly.

GPG(I.T.) 17


 Physical prevention

Physical prevention and preparedness for disaster begins when a site is constructed. It
includes special requirements for building construction, as well as fire protection for various
equipment components. Special considerations include: computer area, fire detection and
extinguishing systems, record(s) protection, air conditioning, heating and ventilation, electrical
supply and UPS systems, emergency procedures.

2.2.3 Risk Planning

Once risks have been identified and assessed, all techniques to manage the risk fall into one or
more of these four major categories:

 Tolerate (retention)
 Treat (mitigation)
 Terminate (elimination)
 Transfer (buying insurance)

Ideal use of these strategies may not be possible. Some of them may involve trade-offs that are
not acceptable to the organization or person making the risk management decisions

 Risk avoidance

It includes not performing an activity that could carry risk. An example would be not buying
a property or business in order to not take on the liability that comes with it. Another would be
not flying in order to not take the risk that the airplanes was to be hijacked. Avoidance may seem
the answer to all risks, but avoiding risks also means losing out on the potential gain that
accepting (retaining) the risk may have allowed. Not entering a business to avoid the risk of loss
also avoids the possibility of earning profits.

 Risk reduction

It involves the methods that reduce the severity of loss. Examples include sprinklers designed
to put out a fire to reduce the risk of loss by fire. This method may cause a greater loss by water
damage and therefore may not be suitable. Halon fire suppression systems may mitigate that risk,
but the cost may be prohibitive as a strategy. Modern software development methodologies
reduce risk by developing and delivering software incrementally. Early methodologies suffered
from the fact that they only delivered software in the final phase of development; any problems
encountered in earlier phases meant costly rework and often jeopardized the whole project. By
developing in iterations, software projects can limit effort wasted to a single iteration. A current
trend in software development, spearheaded by the Extreme Programming community, is to

GPG(I.T.) 18


reduce the size of iterations to the smallest size possible, sometimes as little as one week is
allocated to an iteration.

 Risk retention

It involves accepting the loss when it occurs. True self insurance falls in this category. Risk
retention is a viable strategy for small risks where the cost of insuring against the risk would be
greater over time than the total losses sustained. All risks that are not avoided or transferred are
retained by default. This includes risks that are so large or catastrophic that they either cannot be
insured against or the premiums would be infeasible. War is an example since most property and
risks are not insured against war, so the loss attributed by war is retained by the insured. Also
any amounts of potential loss (risk) over the amount insured are retained risk. This may also be
acceptable if the chance of a very large loss is small or if the cost to insure for greater coverage
amounts is so great it would hinder the goals of the organization too much.

 Risk transfer

It means causing another party to accept the risk, typically by contract or by hedging.
Insurance is one type of risk transfer that uses contracts. Other times it may involve contract
language that transfers a risk to another party without the payment of an insurance premium.
Liability among construction or other contractors is very often transferred this way. On the other
hand, taking offsetting positions in derivatives is typically how firms use hedging to financially
manage risk. Some ways of managing risk fall into multiple categories. Risk retention pools are
technically retaining the risk for the group, but spreading it over the whole group involves
transfer among individual members of the group. This is different from traditional insurance, in
that no premium is exchanged between members of the group up front, but instead losses are
assessed to all members of the group.

The planning by which the risks cannot occur is:
 Interact with all branches.
 Authorize carefully and creating new safe security system for that.
 Make new security for natural threats

2.3 ESTIMATION

2.3.1 Effort Estimation

Today software is the most expensive element of virtually all computer-based systems. For
complex, custom systems, a large cost estimation error can make the difference between profit
and loss. Cost overrun can be disastrous for the developer.

Too many variables-human, technical, environmental, political-can affect the ultimate cost of
software and effort applied to develop it. However, software project estimation can be
transformed from a black art to a series of systematic steps that provide estimates with
acceptable risk.
GPG(I.T.) 19


To achieve reliable cost and effort estimates, a number of options arise:
1.Delay estimation until late in the project.
2.Base estimates on similar projects that have already been completed.
3.Use relatively simply decomposition techniques to generate project cost and effort.
4.Use one or more empirical models for software cost and effort estimation.

 The COCOMO Model

Like all estimation models for software, the COCOMO models require sizing information.
Three different sizing options are available as part of the model hierarchy: object points, function
points, and lines of source code.

Like functions points, the object point is indirect software that is computed using counts of
the number of
(1) Screens (at the user interface),
(2) Reports,
(3) Components likely to be required to build the application.

Once complexity is determined, the number of screens, reports, and components are
weighted according to Table above. The object point count is then determined by multiplying the
original number of object instances by the weighting factor in table above and summing to obtain
a total object point count. When component based development or general software reuse is to be
applied, the percent of reuse (%reuse) is estimated and the object point count is adjusted:

NOP = (object points) X [(100 - %reuse) / 100]

Where NOP is defined as new object points. To derive an estimate of effort based on the
computed NOP value, a ―productivity rate‖ must be derived. Table below presents the
productivity rate

PROD=NOP / person-month
For different levels of developer experience and development environment maturity. Once the
productivity rate has been determined, an estimate of project effort can be derived as

Estimated effort = NOP/PROD

2.3.2 COST ANALYSIS

Cost-benefit analysis is a term that refers both to:

 A formal discipline used to help appraise, or assess, the case for a project or proposal, which
itself is a process known as project appraisal and
 An informal approach to making decisions of any kind.
GPG(I.T.) 20


WHAT IS COST ANALYSIS?

A cost-benefit analysis `is necessary to determine economic feasibility. The Primary objective of
the cost-benefit analysis is to find out whether it is economically worthwhile to invest in the
project. If the return on the investments is good, then the project is considered economically
worthwhile.

Cost-benefit analysis is performed by first listing all the costs associated with the project. Costs
consist of direct costs and indirect costs. Benefits can be broadly classified as tangible benefit
and intangible benefits. Tangible benefits are directly measurable and intangible are not.

The sum of all costs is compared with the sum of all the savings (tangible and intangible). It is
not always easy to assign money value to intangible benefits. It is arrived at by discussion
amongst users of the system.

GPG(I.T.) 21

Chapter 3
System Requirement Study

Project Id: 05 System Requirement Study

3.0 SYSTEM REQUIREMENT STUDY

3.1 User Characteristics
The application identifies three types of users—Mall Administrator, Shop Owner and Mall
Customer—each with different privileges.
(This is only an initial tentative list)

Mall The Mall Administrator is the super user and has complete control over all
Administrator the activities that can be performed. The application notifies the
administrator of all shop creation requests, and the administrator can then
approve or reject them. The administrator also manages the list of available
product categories. The administrator can also view and delete entries in the
guestbook.

Shop Owner Any user can submit a shop creation request through the application. When
the request is approved by the Mall Administrator, the requester is notified,
and from there on is given the role of Shop Owner. The Shop Owner is
responsible for setting up the shop and maintaining it. The job involves
managing the sub-categories of the items in the shop. Also, the shop owner
can add or remove items from his shop. The Shop Owner can view different
reports that give details of the sales and orders specific to his shop. The Shop
Owner can also decide to close shop and remove it from the mall.

Mall Customer A Mall Customer can browse through the shops and choose products to place
in a virtual shopping cart. The shopping cart details can be viewed and items
can be removed from the cart. To proceed with the purchase, the customer is
prompted to login. Also, the customer can modify personal profile
information (such as phone number and shipping address) stored by the
application. The customer can also view the status of any previous orders,
and cancel any order that has not been shipped yet.

3.2 Hardware and Software Specification:

Application will be accessed through a Browser Interface. The interface would be viewed
best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully
compatible with Microsoft Internet Explorer for version 8 and above. No user would be able
to access any part of the application without logging on to the system.

GPG(I.T.) 23


 H/W requirement for Server
 Processor Minimum: Pentium 4 CPU, 2.40 GHz
 Memory RAM: 2 GB
 Hard Disk: 150 GB

 H/W requirement for Clients
 Pentium IV 1.6 GHZ or compatible
 500 MB RAM (minimum) / 256 MB RAM (recommended)
 80GB HDD
 Screen resolution minimum
 Internet connection

 S/W requirement for Server
 Front end: Visual Studio 2008/2005.
 Back end: LINQ Database
 Any web browser(Internet Explorer, Mozilla Firefox etc)
 Toolkit: Ajax Toolkit

 S/W requirement for Clients
 Internet Connection: 150 kbps
 Any Web Browser but user interface shall be compatible to IE6

3.3 Constraints

 Regulatory Policies:

Currently, E-commerce System is running on local Server and is protected by Norton
Antivirus. It can be accessed by all.

 Hardware Limitations:

The only limitation posed is when the disk space is exhausted.

GPG(I.T.) 24


Criticality of the application:

As due to only four months of development of project, there was no time to develop online
biding and C2C application.

GPG(I.T.) 25

Project Id: 05 System Analysis

4.0 SYSTEM ANALYSIS

4.1 STUDY OF CURRENT SYSTEM
The Online Shopping Mall (VSM) application enables vendors to set up online shops,
customers to browse through the shops, and a system administrator to approve and reject request
for new shops and maintain lists of shop categories.

Also on the agenda is designing an online shopping site to manage the items in the shop and
also help customers purchase them online without having to visit the shop physically.

4.2 PROBLEMS AND WEAKNESS OF CURRENT SYSTEM
In current system if we want to buy some products then we have to go to the store and buy a
product this process is time consuming. There is one solution of it. We can buy product online by
seating home using the e-commerce system.

4.3 REQUIREMENTS OF NEW SYSTEM
Requirement for the system tools is whatever you want to create as per your requirement. But
the most common thing in the system is the hardware and software require for that system.
Requirements specification adds further information to the requirements definition.

 User requirements
As the whole organization is going to use the application, the application should serve the
purpose of each person associated with the organization. Depending on the business logic of
each department, the corresponding forms should help the user to automate the processing in
such a way that the physical documents can be easily mapped to forms available in the
application.

GPG(I.T.) 27


As the main focus of the project is on Banking Accounting System the specific focuses is on
saving and share the main requirements of users. As the current physical system involves a
lot of duplication of data, the system should eliminate redundancy in the system and make
the data readily available throughout the organization.

 System requirements
System requirements states which kind of services, functions and facility should be given to
users. We have determined the given requirements:

 The application should use a central database so that the data entered at a given node is
available throughout the organization, depending on the access rights of the user
 The performance of the application should be consistent and should use load-sharing in
order for the application to work smoothly without getting crashed.
● The application should have an interface that can be mapped to the physical documents
that are currently being used by the organization, so that the user does not get confused
between the interface and the physical form in use.
● Concurrent access to the database should be available with great consistency, in order to
serve multiple users simultaneously.

 Functional Requirements
Since this project uses database and control, this needs the retrieval of information from the
database. It needs access of Database from a front end, as asp.net, it provides easy linking to
the database, along with the flexibility required to develop a user-friendly front end.

 Non -Functional Requirements
 Efficiency
The system must provide easy and fast access without consuming more cost.

 Reliability
User should never be surprised by the behavior of the system and it should also provide
meaningful feedback when errors occur so that user can recover from the errors.

GPG(I.T.) 28


 Technical reason.
In other words, the system should not stop functioning if any errors arise.

 Maintenance
The software will be used and maintained by people other than those involved with the
actual development. Hence, it is important that the code be such that there is extreme ease
with which the program can be corrected if an error is encountered.

 User Friendly
The application needs to demonstrate a high level of user-friendliness. This involves
minimal physical or intellectual skill on the part of the end user to operate

 Portability
The application must be easily deployable at numerous locations. System engineering
provides the appropriate mechanism for understanding what the customer wants,
analyzing need, assessing feasibility ,negotiating a reasonable solution, specifying the
solution unambiguously, validating the specification and managing the requirements as
they are transformed into an operational system.
The system requirement engineering process can be described into following distinct steps
o Requirement Analysis
o Requirement specification
o Requirement definition
o Requirement Analysis

In Requirement analysis, we met to the employees. And discussed about their requirements and
the problems they are facing with existing system.
 Fact Finding Technique
 Requirement Engineering
◦ This is concerned with the introductory phases of the software process in which
the requirements for the software are established and specifies in detail for further
development.

GPG(I.T.) 29


◦ Feasibility study
◦ Requirements analysis
◦ Requirements definition
◦ Requirements specification
◦ Feasibility report
◦ System models
◦ Specification of requirements
◦ Specification of requirements
◦ Requirements documents

 Methods of Searching Information

 Interviewing Technique:-
The primary purpose of interviewing is to obtain both quantitative and qualitative data
regarding user requirements, policies, procedures and practices.

 Questionnaires:-
Detailed questionnaires are useful to gather quantitative information. They are no substitutes
for interviews, as questionnaires do not get qualitative information. The shorter a
questionnaire, the higher is the probability of getting replies back quickly.

 Requirement Specification:-
The term specification means ―different things to different people‖. Analysis of data is
describing the system to determine how well it is performing, what requirements must be
met, and strategies for fulfilling them.
Following activities are important and must be performed correctly.

o Analysis of actual data
The data collected during the fact finding study and included in data flow and decision
analysis documentation are examined to determine how well the system is performing and
whether it will.
o Meet the organization‘s demand.
GPG(I.T.) 30


 Preliminary Investigation
Primary investigation must be needed for the better feature of the any type of the project First
of all we must study other websites and after go ahead. Most important thing is which the
way we want to create the project. So we have to find related data. So it keeps our mind that
the primary related data must have with us. With these primary data we can perform well
featured project.

Requirement Analysis

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

Requirement Analysis Process
Requirements definition and specification

Requirement
Validation
Prioritization
Conflict
Resolution
Requirements
Collections
Domain
Understanding
Requirement
Process
Entry

GPG(I.T.) 31


Software Requirement Analysis

The requirements gathering process is intensified and focused specifically on software. Software
requirements analysis encompasses understanding the information domain for the software as
well as required function, performance, behavior and interfacing. Requirements for both the
system and the software are documented and reviewed with the customer.

1. DESIGN
Software design is a multi-step process that focuses on four distinct attributes of a program: data
structure, software architecture, interface representation, and procedural details. The design
process translates requirements into a representation of the software that can be assessed for
quality before code generation begins. The design is documented and becomes part of the
software configuration.
2. CODE GENERATION
The design is translated into a machine – readable form. If design is performed in a detailed
manner, code generation can be accomplished mechanistically.

3. TESTING
The testing process focuses on the logical internals of the software, assuring that all statements
have been tested, and on the functional externals i.e. conducting tests to uncover errors and
ensure that defined input will produce actual results that agree with required results.

4. MAINTENANCE
Software maintenance applies to following phases in the existing program:
a) Change in software due to errors.
b) Change in software because the software must be adapted to accommodate
changes in its external environment.
c) Change in software when the customer requires functional or performance
enhancements.

GPG(I.T.) 32


4.4 FEASIBILITY STUDY

Feasibility study is the study of the system to check whether the system made is feasible
or not. It is very Useful to check whether the system work as per the requirement or not. It is
undertaken to determine the possibility of the probability of developing completely new system.

Need of the feasibility study

 Answer the question whether the new system is to be developed or Not?
 Define the problem and objectives involved.
 Is the cost incurred in the development of the system of the Justified?

Operational feasibility: -

It covers mainly two aspects. It determines that how the proposed system will fit in the
current operation and what if the job retraining and restructuring may be needed at the end of the
implementation of the system. The operational feasibility checks whether user who is going to
use the system as able to work with the software with which the system is coded!
In the system Operation feasibility following are the question to be asked!
 Is there sufficient support for the project?
 Is current method are acceptable to the user?
 Have the user been involved in the planning and development of the system?
 Project is very useful for online system.
 System is very user-friendly.
 Level of security and any other access constrains are high.

Technical feasibility: -
 It determines that work for the project be done with the present equipments and existing
software technology.

GPG(I.T.) 33


 Necessary all things is easily feasible for the project. Necessary technology, documents,
reports are also available. Technical guarantee of accuracy, reliability and security are also
provided.
It asks following question?
 Does necessary technology exists to do what is suggested?
 Do the Proposed equipments have the technical capacity to hold the data
required to use new system?
 Are there technical guarantees of accuracy, reliability ease of access and data security

Economical feasibility: -

It looks the financial aspects of the project. Economic feasibility concerns with the returns of the
investments in the project. It determines whether it is worthwhile to invest money in the
proposed system?
It asks for the following question.
 What is the cost to conduct a full system investigation?
 What is the cost of hardware and software required in the development of the
proposed system?
Estimated cost is fitted in budget. (I.e. cost of software and hardware is feasible to common
person.

4.5 REQUIREMENTS VALIDATIONS:
It means that the developed software is as per requirement or not? Simply stating whatever we
are doing is right or wrong as per requirements? Here we check each and every requirement and
compare with our product and that it satisfies the user need.

GPG(I.T.) 34


4.6 FUNCTIONS OF SYSTEM:-

4.6.1 Use Cases, event trace or scenario
Actors:
An Actor is a role that a user plays with respect to the system. There is only one actor
in above figure i.e. user. There can be many users in the given system, but as far as the system is
concerned, they all play the same role. Actors carry out use cases. A single actor may perform
many use cases; conversely, a use case may have several actors performing it.

Use Case Relationships:
 In addition to the links among actors and use cases, we can show several kinds of relationships
between use cases.
 They include relationship occurs when you have a chunk of behavior that is similar across
more than one use case and you don‘t want to keep copying the description of that behavior.
 You can also use case generalization when you have one use case that is similar to another use
case but does a bit more. In effect, this gives us another way of capturing alternative scenarios.
 A third relationship, which we have shown is called extend. Essentially, this is similar to
generalization but with more rules to it.

GPG(I.T.) 35


Use case diagram of Administrator,Shop owner and Customer

Visit the site

Browse
catalog

New account
creation

Login

Request for
shop

Accept or deny
shop request

View Shop Owner
Deatils Visitor

Send Notification
To Shop Owner

View Product
Deatils

Admin View Suggestion

Change Password

Maintain Product

Recruit Employee

Shop Owner

Send Notification
To Shop Owner

Customer

View Product &
Sales Deatils

Buy Product

View Customer
Deatils

Fig Use case diagram of Administrator, visitor, shop-owner and customer

GPG(I.T.) 36


4.7 DATA MODELING
4.7.1 E-R Diagrams
Data models are tools used in analysis to describe the data requirements and assumptions in the
system from a top-down perspective. They also set the stage for the design of databases later on
in the SDLC.
There are three basic elements in ER models:
 Entities are the "things" about which we seek information.

 Attributes are the data we collect about the entities.

 Relationships provide the structure needed to draw information from multiple entities.

Relationships:-
A Relationship is a diamond that contains its name. It touches one relationship-entity and
optionally some attribute-entity connectors. It is linked with two entities.
Connectors:-
A relationship-entity connection is a line that touches exactly one text label (expressing
cardinality) and two other regions (rectangle or diamond). Cardinality is a text string with values
chosen from the set.
SYMBOL USED IN E-R Model
An entity set is represented as a rectangle.
A diamond represents the relationship among a number of entities, which are connected to the
diamond by lines

. entity

Relation ship

n Relation m
ships

cardinality Relation
entity ships

GPG(I.T.) 37


E R Diagram Add Identity No.
Name

Request id Bank Stat.

Shop
Type
Shop Owner
E mail Id

Contact No.
Visitor Fill Form
Request Id Name
Add

Sex
User_Name
Admin Id Password
Customer
E mail Id

Contact No.
Admin View Request
Notification

Send
View
Shop Owner
Id Request Id

User_Name
Create Shop Owner
Password
Customer Id
Customer
Add
Request Id

User_Name Create
Customer

Password

Send Product Check

Name
Product Id
Department Id
View
Name
Price

Department
Do
Orderlist

View Request
Customer
Suggest Id Id
Shop Id
Request Id Pro, Id
Data Shop Id

Suggest View

Shopping
Purchas Id Cart Id PayMod

Date
Shopping

Fig: E-R Diagram of E-Mall Management System

GPG(I.T.) 38


4.7.2 System Activity or Object Interaction Diagram

1. Activity Diagram of Administrator

Home Admin

Login

Invalid Check

Valid

Change Shop Owner Product Customer
Password Request Details Details

Customer
Suggestion

Notifications

Logout

Fig: Activity Diagram of Administrator

GPG(I.T.) 39


2. Activity Diagram of Shop Owner

Home Shop Owner

Login

Invalid Check

Valid

Change Customer Final Product Forgot Contact
Password Details Billing password us

Customer
Request Bill Product Recovery
receipt Details Email

Log out

Fig: Activity Diagram of Shop Owner

GPG(I.T.) 40


3. Activity Diagram of Customer

Home Customer

Login

Invalid Check

Valid

Forgot
Change Purchase password
Password product

Billing of Suggestion
Shopping Products s
View cart
product and Recovery
its detail Email

Log out

Fig: Activity Diagram of Customer

GPG(I.T.) 41


4.7.3 Data Dictionary:-

1. Login Table
Sr Field Name Data Type Size Constraints
1 Login_Id Int 10 Pk
2 User_Name Varchar 20
3 Password Varchar 30
4 Role_Id Int 4 Fk

2. Role Table
1 Role_Id Int 4 Pk
2 Role_Name Varchar 30

3. Notification Table
1 Notification_Id Int 4 Pk
2 Subject Varchar 30
3 Discription Varchar 30
4 Shop_Owner_Id Int 4 Fk
5 Status Bin 30

4. Bank Account Table
1 Account_Id Int 4 Pk
2 Card_Id Int 4 Fk
3 Card_Number Number 16
4 Sequrity_Code Number 3
5 Amount Money 10

5. Billing Table
1 Bill_Id Varchar 8 Pk
2 Date Datetime 8
3 Total_Price Money 15
4 Billstatus Bit 1

GPG(I.T.) 42

Emall

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Emall

Similar to Emall (20)

Recently uploaded

Recently uploaded (20)

Emall