e billing system in mall megha

8/19/2019 e Billing System in Mall Megha

1/24

PROJECT REPORT

ON

E-BILLING SYSTEM IN MALL

SUBMITTED BY

NAME,

SUBMITTED TO SIKKIM MANIPAL UNIVERSITY IN THE PARTIAL FULFILLMENT OF THE

REQUIREMENT FOR THE AWARD OF MBA IN PROJECT MANAGEMENT

LEARNING CENTRE -

ADDRESS----------

CENTRE CODE -


2/24

ACKNOWLEDGEMENT

I offer my gratitude to those ho ha!e s"e#t their "re$ious time% i#terest a#d $o#ti#ued e#$ourageme#t through the study

a#d for the $om"&etio# of my "ro'e$t(

I ou&d &i)e to tha#)s to our "ro'e$t guide for their e#$ourageme#t a#d su""ort throughout the $ourse of our "ro'e$t(

Last *ut #ot the &east% I e+"ress my gratitude to a&& those ho dire$t&y , i#dire$t&y dire$t me for su$$essfu& $om"&etio# of the "ro'e$t(

Name

Rid


3/24

-ONA.IDE CERTI.ICATE/

IT I0 Certified that this "ro'e$t re"ort tit&ed 1 2 is the *o#a3fide or) of NAME % ho4s Registratio# id is

555555555 a#d $arried out the "ro'e$t or) u#der my $om"&ete su"er!isio#(

sig#ature of fa$u&ty head sig#ature of a$ademi$ desig#ati 65555555555555555557

655555555555555555557


4/24

CONTENTS

Sl No. Subject

1. Pro'e$t Tit&e

2. I#trodu$tio#

3. O*'e$ti!e

4. 0ystem A#a&ysis

5. .easi*i&ity 0tudy

6. 08W E#gi#eeri#g Paradigm A""&ied

7. 08W a#d 98W Re:uireme#t 0"e$ifi$atio#

8. 0ystem Desig# 6D.D a#d ERD7

9. Codi#g

10. Code Effi$ie#$y

11. O"timi;atio# of Code

12.


5/24

`

INTRODUCTION

(Problem Analysis)

This project is based on the E-BILLING SYSTEM IN MALL for world Wide. An E-Shopping is a

multifunctional integrated computer based system that allows many activities to be performed in an

electronics mode.

It is done in the HTML, VB Script, Java Script, Active Server Pages (ASP) which is friendly with

MS-SQL as database query language which has also some important features in this Scienecand


6/24

Technology age. It compromises thirteen modules, user can search and retirve any queries related to

any of these modules.

The system is superior to the manual system in that it has speed, realiablity, portability and

flexibility, which has been fulfilled by our project.


7/24

PRELIMINARY INVESTIGATION

The software entitled “MarineParkElectronics.com” is intended to be Internet based system.

1.The main and first objectives of this project are to fulfill the customer need on time.

2.Selling Laptops and other electronics peripherals (such as computer peripherals, webcam etc.).

3.Due to easy and secure accessing of site, multiple users access simultaneously.

4.Ease of product search depending on the brand, configuration and budget range of user.

5.Making laptops available to users at cheapest prices through sale and refurbished goods.

6.User can order the product available at the company online.

7.Preperation of reports like bill and shipment should take less time.

8.The application consists os real time tracking system. By real time tracking systsem the

customer can check the staus of his/her order.

9.Once the order bill is executed it is sent to the customer.

10. A customer becomes a client of the company at the sole concern of the company.


8/24

11. Providing Merchant IF from Verisign gateway for secure online credit card transactions.4.

SYSTEM ANALYSIS

This project is based on the E-BILLING SYSTEM IN MALL for world Wide. An E-Shopping is a

multifunctional integrated computer based system that allows many activities to be performed in an

electronics mode.

It is done in the HTML, VB Script, Java Script, Active Server Pages (ASP) which is friendly with

MS-SQL as database query language which has also some important features in this Scienecand

Technology age. It compromises thirteen modules, user can search and retirve any queries related to

any of these modules.

The system is superior to the manual system in that it has speed, realiablity, portability and

flexibility, which has been fulfilled by our project.

PROCESS DIAGRAM FOR SYSTEM ANALYSIS


9/24

STUDY

CURRENT

SYSTEM

DERIVE

LOGICAL

SYSTEM

NEWSYSTEM

MODEL

USER

STATED

REQUIREMENTS

FEASIBILITY

DOCUMENT

DISCRIPTIVESTATEMENT OF

INFORMATION PROVIDED BY

SYSTEM PROCESSING

RULES

DATADICTIONARY

NEW LOGICAL DATAFLOW

DIAGRAM

CURR ENT PHYSICAL D ATAFLOW

DIAGRAM

CURRENT LOGICAL DATAFLOW

DIAGRAM

4.1.

IDENTIFICATION OF NEED

System developmental process consisting of two major steps of system analysis and design starts

when management or sometime system develop the software entitled “Mpsuperstores.com” is

intended to be Internet based system.

10.The main and first objectives of this project are to fulfill the customer need on time.

11.Selling Laptops and other electronics peripherals (such as computer peripherals, webcam etc.).

12.Due to easy and secure accessing of site, multiple users access simultaneously.

13.Ease of product search depending on the brand, configuration and budget range of user.

14.Making laptops available to users at cheapest prices through sale and refurbished goods.

15.User can order the product available at the company online.

16.Preparation of reports like bill and shipment should take less time.


10/24

17.The application consists os real time tracking system. By real time tracking systsem the

customer can check the status of his/her order.

18.Once the order bill is executed it is sent to the customer.

10. A customer becomes a client of the company at the sole concern of the company.

11. Providing Merchant IF from Verisign gateway for secure online credit card transactions.


11/24

4.2. PRELIMINARY INVESTIGATION

System developmental process consisting of two major steps of system analysis and design

starts when management or sometime system development personnel feel that a new system or an

improvement in the existing system is required. The first step in the system development life cycle is

the preliminary investigation to determine the feasibility of the system. The main purpose of the

preliminary investigation is to evaluate project requests. This investigation is not related with design

phase but it is the collection of details to describe the business system in all respect.

The system is superior to the manual system in that it has speed, reliability, portability and

flexibility, which has been fulfilled by our project. So, our analyst working the preliminary

investigation should accomplish the following objectives:

• Clarify and understand the project request.

• Determine the size of the project.

Assess cost and benefits of alternatives approaches.

• Determine the technical, economical and operational feasibility of alternative

approaches.

Report the finding to management with recommendations outlining the acceptance or rejection of the

proposal.

Conducting the investigation: - The data that analyst collect during preliminary investigation are

gathered through three primary method

1. Reviewing organization documents: - The analyst conducting the the investigation first learn about

the organization involved in, or affected by the project. On this project I with guide are getting some

details by examining organization charts and studying written operating procedures. The procedures

clearly define various important steps involved in receiving, managing and dispensing stock.


12/24

2. On-site observation: - in this method, we are observe the activities of the system directly. Our

purpose of on –site observation is to get as choose as possible to the real system being studied.

During on-site observation, we can see the office environment, work load of the system and the

users, method of work and the facilities provided by organization to the users.

3. Conducting interviews: - after above mentioned two method we are on the point where we know

how the system should operate, but they may not include enough details to allow a decision to be

made about the merits of a system proposal, nor do they present user view about current operations.

Typically, a recruitment cycle goes through the stages of collection of resumes (through referrals, ads

etc.), sorting them, screening of candidates, short-listing, sending an offer and final joining

formalities of candidate. These are the routines and manual tasks that consume most time and

Manpower. The time and effort that goes into this can be broken up:

Sorting incoming resumes and discarding obvious drop-outs: 25-35%

Scheduling the screening process for eligible candidates, intimating them, communication and

ordination with personnel involved in the screening process: 15-20%

Monitoring each candidate through the screening procedure, selecting and rejecting appropria

and sending out appropriate information: 25-35%

Sending offer letters and follow-up of joining formalities, checking whether candidate joins: 10-15


13/24


14/24

5. FEASIBILITY STUDY

Feasibility is the determination of whether or not a project is worth doing. The process followed in mak

this determination is called a feasibility study. Once it has been determined that a project is feasible,

analyst can go ahead and prepare the project specification which finalizes project requirements.

PROCESS DIAGRAM FOR FEASIBILITY ANALYSIS

ANALYZE TO FIND

DEFICIENCES

FIND BROAD

ALTERNATIVE

SOLUTION

EVALUATE

FEASIBILITY OF

ALTERNATES

USER

STATED

REQUIREMENTS

DEFICIENCES IN

CURRENT SYSTEM

PROPOSED FEASIBILITYALTERNATIVES

REVISION BASED ON FEASIBILITY

ALTERNATIVES

CONSTRAINTS ON RESOURCES

WORKING CURRENT SYSTEM USERS CONSESUS

DEFINE AND

QUANTIFY GOALS

Three important tasks of feasibility were studied and are described below: -

5.1. Technical Feasibility

This is concerned with specifying equipment and software that will successfully satisfy the user

requirement. The technical needs of the system may vary considerable, but might include:

• The facility to produce output in a given time.

• Response time under certain volume of tram cation at a particular speed.

• Facility to communicate date to distant location.


15/24

The proposed equipment had the capacity to hold the data required to use the new system. We felt

that system could be upgraded if developed. Also the guarantee of making available accurate, reliable

information & ease of access along with data security can be provided through computerized system.

5.2. Economic Feasibility

Economic analysis is the most frequently used technique for evaluating the effectiveness of a

proposed system. More commonly known as cost/benefits analysis. With the knowledge we have

acquired during studies we knew that the proposed system was technically feasible but this work was

not the end.

Cost of hardware & Software needed was considered. Also various other costs were estimated.

This automation would reduce the cost and also a few costly errors. In the right of various benefits we

estimated that the project is economically feasible.

5.3. Operational Feasibility

It is mainly related to the human organization and political aspects. The points to be considered are:

• What changes will be brought with the system?

• What organizational structures are disturbed?

• What new skill will be required? Do the existing staff members have these skill? If not, can

they be trained in due course of time?

It was established that the proposed automated system should work when it is developed and

installed. No major barriers to implementation were there.


16/24

6. SOFTWARE ENGINEERING PARADIGM APPLIED

In order to transform requirements into a working system, we must satisfy both the customer and the

system builders on development team. The customer understands what the system is to do. At the

same time, the system builders must understand how the system is to work. For this reason, system

design is really a two-part process. First, we produce a system specification that tells the customer

exactly what the system will do. This specification is sometimes called a conceptual system design.

Once the customer approves the conceptual design, we present the system builders with a technical

design that allows them to build the actual hardware and software. This two-part design mirrors the

two parts of requirement description. The conceptual design concentrates on the function of the

system, while the technical design describes the form the system will take.

Various software paradigms are available for developing the project. The most simple and commonly

used paradigm is the Waterfall model, which is also used for the development of this project. This

model is also referred to as Linear Sequential Model. As all activities are performed in a sequential

manner, this model is easy to implement. With the waterfall model, the sequence of activities

performed in a software development project is:requirement analysis, project planning, system design,

detailed design, coding and unit testing, system integration andtesting.

Linear ordering of activities has some important consequences. First, to clearly identify the end of

phase and beginning of the next phase, some clarification mechanism has to be employed at the end

of each phase. This is usually done by some verification and validation means that will ensure that

output of a phase is consistent with its input (which is the output of the previous phase), and that of

the phase is consistent with the overall requirements of the system.

The consequence of the need for certification is that each phase must have some defined output that

can be evaluated and certified. That is, when activities of a phase are completed, there should be

some product that is produced by the phase. And the goal of the product is to produce this product.


17/24

The outputs of earlier phases are often calledwork products(orintermediate products) and are usually

in the form of documents like requirements document or design document.

There are two basic assumptions for justifying the linear ordering of phases in the manner proposed

by the waterfall model:

1.For a successful project resulting in a successful product, all the phases listed in the waterfall

model must be performed anyway. A successful software product is one, which satisfies all the

objectives of the development project. These objectives include satisfying the requirements and

performing the development within time and cost constraints.

2.Any different ordering of the phases will result in a less successful software product. As the

simplicity of waterfall model lies in the linear pattern, it is easier to implement. This is because,

the output of the previous phase is well known before starting next phase.

3.

Re:uireme#ts

A#a&ysis ,Pro'e$t

P&a##i#g

.easi*i&ity

Re"ort

0ystem

.easi*i&ity


18/24

(Figure - Waterfall Model)

The project is fully made keeping in mind the waterfall model paradigm. Each activity involved in the proj

is handled sequentially. Also all phases of the software development life cycle are covered sequentially.

CONCEPTUAL DESIGN:

The conceptual design tells the customer what the system will do. The system is described in

terms of its boundary, entities, attributes, and relationships. In the conceptual designing phase we

have considered the following questions: -

• Where will the data come from?

• What will happen to it in the system?

• What will the system look like to user?

• What choices will user be offered?

• What will the reports and screen look like?

Moreover, the system is described in language that the customer can understand, rather than in

computer jargon and technical terms. For example, the customers of the system had been told

that a menu on display screen will give users access to the system functions as SHOW, NEXT,

PREV, ADD, MODIFY AND DELETE. The system description may even list acceptable user

responses and the actions that may result. However, the customer is not told how the data are

stored in the system or what kind of database management system is used for data manipulation.


19/24

On the time of conceptual design, I have written it in the customer’s language, which does not

contain technical jargon. It describes the functions of the systems and incorporates all

requirements in adequate details.

TECHNICAL DESIGN:

The technical design explains the system to those hardware and software experts who will

implement it. The design describes the hardware configuration, the software needs, the

communication interfaces, the input and output of the system and anything else that translates the

requirements into a solution to the customer’s problem. The design description is a technical picture

of the system specification. Thus we include the following items in the technical design:

The system architecture: a description of the majore hardware components and their

functions.

The system software structure: the hierarchy and function of the software components.

The data: the data structure and data flow.

DESIGN APPROACH:

Modular approach has been taken into consideration. Design is the determination of the

modules and interlobular interfaces that satisfy a specified set of requirements. A design module is a

functional entity with a well-defined set of inputs and outputs. Therefore, each module can be viewed

as a component of the whole system, just as each room is a component of a house. A module is well

defined if all the inputs to the module are essential to the function of the module and all outputs are

produced by some action of the module. Thus if one input will left out, the module could not perform

its full function. There are no unnecessary inputs: every input is used in generating the output.

Finally, the module is well defined only when each output is a result of the functioning of the module

and when no input becomes an output without having the transformed in some way by the module.


20/24

Modularity: Modularity is a characteristic of good system design. Hi level modules give us the

opportunity to view the problem as whole and hide details that may distract us. By being able to

reach down to a lower level for more detail when we want to, modularity provides the flexibility we

need to understand what the system is to do, tarce the flow of data through the system, and target

the pockets of complexity.

Level of Abstraction: Abstraction an information hiding allows us to examine the way in which

modules are related to one another in the overall design the degree to which the modules are

independent of one another is a measure of how good the system design is. Independence is desirable

for two reasons. 1. It is easier to undesratnd how a mosule works if its function is not intrecetly tied

to others. 2. It is much easier to miodify a module if it is independent of others. Often a change in

requirements or in a design decision means that certain modules must be modified. Each change

affects data or function or both. If the modules depend heavily on each other, a change to one module

may mean changes module that are affected by the change.

Coupling:coupling is a measure of how many modules depend oneach other. Two modules are highly

coupled if there is a great deal of dependence between them. Loosely couple modules have no

interconnection at all. Coupling depends on several things

• The refernces made from one module to another.

• The amount of data passed from one module to another.

• The amount of control one module has over the other.

• The degree of complexity in the interface between one module and another.

Thus, coupling really represents a range of dependence, from complete dependence to complete

independence. We want to minimize the dependence among modules for several reasons. First, if an

element is affected by a system action, we always want to know which module causes an effect at a

given time. Second, modularity helps in tracking the cause of the system errors. If an error occurs


21/24

during the performance of particular function independence of modules allows us to isolate the

defective module more easily.

Cohesion:cohesion refers to the internal “glue” with which a module is constructed. The more

cohesive a module, the mpre related are the internal parts of the module to each other and to the

functionality of the module. In other words, a module is cohesive if all elements of the module are

directed towards and essential for performing the same function.

Fan in Fan out: A single module can control several modules. Fan In is a number of modules

controlling a particular module, and Fan out is the number of modules controlled by a module.

Scope of control and effect:Finally we want to be sure that the modules in our design do not affect

other modules over which they have the control. The mosules controlled by the given module are

collectively refered to as the scope of effect. No module should be in scope of effect if it not in scope

control.

Thus in order to make the syetm easier to construct, test, correct, and maintain our goals had been: -

• Low coupling of modules

• High cohesive modules

• Minimal number of modules with high Fan out.

• Scope of effect of a module limited to its scope of control


22/24

SOFTWARE/HARDWARE SPECIFICATION

Hardware Specification

• Pentium III 1.5 Ghz and Above

•

256 MB SDRAM or More• 40 GB HDD

Software Specification

Windows 9x

Internet Information Server

SQL Server 7.0

ASP

HTML

Jscript ,


23/24

Client

Server

Client requests ASP page

Server returns HTML

The Server locates the ASP fle on the hard drive and parses it, removing all ASP scripts an

In ASPClient-Server Modelis implemented. A client computer requests some needed

information from Server computer. The Server returns this information and the client acts on it. The

client is a web browser on the internet. With the internet the server is a particular web server. Aweb

server is a computer that contains all the web pages for a particular web site and has special

software installed to send these web pages to web browsers that request them.

The client can’t tell the difference between an ASP page and a static web page because it

receives just HTML text in both cases. When the web server processes the an ASP page, all the

programmatic code is interpreted on the server-none of it is sent to the client. The web plays a more

active role when an ASP page is requested by the client.


24/24

(Figure – Client/Server Interaction for ASP files)

ASP OBJECT HIERARCHY:

This hierarchy diagram shows the process of creating and serving ASP Pages.

Client Request

Server Res!nse

Ali"#ti!n O$%e"t

Res"o#se

O*'e$t

Re:uest

O*'e$t

Sessi!n O$%e"t

Sessi!n O$%e"t

Res"o#se

O*'e$t

C l i e n t

e billing system in mall megha

Documents