INTRODUCTION OF SHOPPING MART

The SHOPPING MART Web site is the application that provides customers
with online shopping. Through a Web browser, a customer can browse the catalog, place
items to purchase into a virtual shopping cart, create and sign in to a user account, and
purchase the shopping cart contents by placing an order with a credit card.

The Application is a working demonstration of how to use blueprints principles in a

real application design. This document is an online guide to the design and the
implementation of the application Enterprise Applications with web technology.

Each release of the application maintains consistent design features such as separating
logic and presentation, using web component for control and web pages for presentation,
using business components, and so on. high-level design features, this document goes deeper
into the implementation details of the current application release.

This document is provided as an online-only resource so that it may be continually

extended and updated. This document begins with a description of the separate applications
that the sample application comprises, describes the modular structure of the EMAT
application, and provides an in-depth description of several pieces of the modules.

• Each FUTURE FASHION module has different requirements from the others. This
section describes the requirements, design, and implementation of each module.
• Control module—the control module dispatches requests to business logic, controls
screen flow, coordinates component interactions, and activates user sign on and registration.
The control module is implemented by the WAF and application-specific WAF extensions.
• Shopping cart module—the shopping cart tracks the items a user has selected for
purchase
• Sign on module—the sign on module requires a user to sign on before accessing
certain screens, and manages the sign on process
• Messaging module—the messaging module asynchronously transmits purchase orders
from the pet store to the OPC
• Catalog module—the catalog module provides a page-based view of the catalog based
on user search criteria
• Customer module—the customer module represents customer information: addresses,
credit cards, contact information, and so on
 TOOLS, PLATFORM & LANGUAGE TO BE USED

TOOLS:

 FRONT-END : ASP.NET(With C# 3.5)

 BACK-END : SQL SERVER 2005

HARDWARE AND SOFTWARE ENVIRONMENT

HARDWARE ENVIRONMENT:

 PROCESSOR : P-IV(1.80 GHZ)

 RAM : 128 MB
 STORAGE CAPACITY : 40 GB

SOFTWARE ENVIRONMENT:

 OPERATING SYSTEM : WINDOW SERVER 2000

 RDBMS : SQL SERVER 2005
 SOFTWARE TOOL : VISUAL STUDIO 2008
 FEASIBILITY STUDY

A feasibility study is conducted to select the best system that meets performance
requirement. This entails an identification description, an evaluation of candidate system and
the selection of best system for he job. The system required performance is defined by a
statement of constraints, the identification of specific system objective and a description of
outputs.
The key consideration in feasibility analysis are :

1. Economic Feasibility:
2. Technical Feasibility:
3. Operational Feasibility:

It looks at the financial aspects of the project. It determines whether the

management has enough resources and budget to invest in the proposed system and the
estimated time for the recovery of cost incurred. The personal cost like salaries of employees
hired are also nominal, because working in this system need not required a highly qualified
professional. The operating-environment costs are marginal. The less time involved also
helped in its economical feasibility. It was observed that the organization has already using
computers for other purpose, so that there is no additional cost to be incurred for adding this
system to its computer. The computers in the organization are highly sophisticated and don’t
needs extra components to load the software. Hence the organization can implement the new
system without any additional expenditure. Hence, it is economically feasible
Economic Feasibility: Economic analysis is the most frequently used method for evaluating

the effectiveness of a candidate system. More determine the benefits and the saving that are

expressed from a candidate system and compare them costs. If benefits outweigh costs.

Otherwise, further justification or alterations in the proposed system will have to be made if it

is to have a chance of being approved. This is an ongoing effort that improves in accuracy at

each phase of the system life cycle.

Technical Feasibility: Technical feasibility center around the existing computer system

hardware etc. and to what extent it can support the proposed addition. For example, if the
current computer is operating at 80% capacity - an arbitrary ceiling – then running another

application could over load the system or require additional hardware. This involves financial

consideration to accommodate technical enhancements. If the budget is a serious constraint

then the project is judged not feasible.

Operational Feasibility: It is common knowledge that computer installations have some

thing to do with turnover, transfers, retraining and changes in employee job status. Therefore,

it is understandable that the introduction of a candidate system requites special efforts to

educate, sell, and train the staff on new ways of conducting business.
 SYSTEM DEVELOPMENT METHODOLOGY

1. Initiation Phase

The initiation of a system (or project) begins when a business need or opportunity is
identified. A Project Manager should be appointed to manage the project. This business need
is documented in a Concept Proposal. After the Concept Proposal is approved, the System
Concept Development Phase begins.

2. System Concept Development Phase

Once a business need is approved, the approaches for accomplishing the concept are
reviewed for feasibility and appropriateness. The Systems Boundary Document
identifies the scope of the system and requires Senior Official approval and funding
before beginning the Planning Phase.

3. Planning Phase

The concept is further developed to describe how the business will operate once the approved
system is implemented, and to assess how the system will impact employee and customer
privacy. To ensure the products and /or services provide the required capability on-time and
within budget, project resources, activities, schedules, tools, and reviews are defined.
Additionally, security certification and accreditation activities begin with the identification of
system security requirements and the completion of a high level vulnerability assessment.

4. Requirements Analysis

Phase Functional user requirements are formally defined and delineate the requirements in
terms of data, system performance, security, and maintainability requirements for the system.
All requirements are defined to a level of detail sufficient for systems design to proceed. All
requirements need to be measurable and testable and relate to the business need or
opportunity identified in the Initiation Phase.
5. Design Phase

The physical characteristics of the system are designed during this phase. The operating
environment is established, major subsystems and their inputs and outputs are defined, and
processes are allocated to resources. Everything requiring user input or approval must be
documented and reviewed by the user. The physical characteristics of the system are
specified and a detailed design is prepared. Subsystems identified during design are used to
create a detailed structure of the system. Each subsystem is partitioned into one or more
design units or modules. Detailed logic specifications are prepared for each software module.

6. Development Phase

The detailed specifications produced during the design phase are translated into hardware,
communications, and executable software. Software shall be unit tested, integrated, and
retested in a systematic manner. Hardware is assembled and tested.

7. Integration and Test Phase

The various components of the system are integrated and systematically tested. The user tests
the system to ensure that the functional requirements, as defined in the functional
requirements document, are satisfied by the developed or modified system. Prior to installing
and operating the system in a production environment, the system must undergo certification
and accreditation activities.

8. Implementation Phase
The system or system modifications are installed and made operational in a production
environment. The phase is initiated after the system has been tested and accepted by the .
This phase continues until the system is operating in production in accordance with the
defined user requirements.
 FUTURE SCOPE
On the basis of the work done in dissertation entitled “Music Online”, the following
conclusions emerge from the development.

1. This project has achieved the objective of replacing/augmenting the conventional

system of arranging manpower as could be conducted by a typical telecom dept.
2. The development of this package has been achieved by using C#.NET, which is very
conductive to develop the package with regard to time and specific need to the user.
3. This package is highly user friendly, required an optimal minimal input from user
while providing highly relevant and focused outputs.
4. Fully automated, avoiding human intervention. Hence it provides a very rapid cost
effective alternative to the conventional manual operation/procedures; the visual
outputs are more reliable than the audio forms of manual communication.
5. The system can further extended as per user and administrative requirements to
encompass other aspects of connection management for telecom dept.
 LIMITATIONS

 This project does not Edit the date of connection or store the date
of transfer in case of connection transfer.
 System date for the project is like as backbone for the human, i.e.
proposed system is depends on system date so it must be correct.
 Cannot be connected to the Internet.
 There are some inherent problems like time, finance etc. to
elaborate further study.