Final WebMart Documentation

8/2/2019 Final WebMart Documentation

1/159

C2006 Final Project Implementation Phase IV

WebMart Proposal

Table of Contents

1. Introduction 22. Current System 2

2.1. Membership Procedures 2

2.2. Order Procedures 22.3. Feedback 32.4. Marketing 3

3. Basic Problems and Limitations 4

4. Proposal of new system 64.1. Membership Procedures 6

4.2. Order Procedures 64.3. Feedback 74.4. Marketing 74.5. Online Help 74.6. Easy Searching 7

5. Benefits 8

6. Hardware and Software Specifications 106.1. Hardware Requirements 106.2. Software Requirements 10

7. Cost/Benefit Analysis 11

1


2/159


1. Introduction

WebMart is a large super market with only one branch in Pakistan Lahore. A recently

developed shopping mart has over 200 members, providing them with extra facilities and

concessions on products. Other than members, there are normal customers who buy

products but their information is not required by the system. Their aim is to develop theirbranches in major cities of Pakistan and supply their products and facilities to the

customers. WebMart also supply products throughout the country. All the operations of the

system are performed manually.

2. Current System

All the operations and procedures are performed manually. Functions performed for

membership are listed below.

2.1 Membership procedures:

2.1.1Customer Registration:Customer requests for a membership to the receptionist. The customer is provided

with a membership form, requiring the customer to provide his personal

information like name, phone number, address etc.

2.1.2Acceptance of agreement and policies:Detailed terms, rules, policies and conditions of the system and achieving a

membership are stated in the form. The customer fills the form giving his personalinformation, signs the contract and hand it over to the receptionist.

2.1.3Issuing Membership Card:After the membership process is complete, the customer is issued a membership

card. Members are provided with different services and concession/discount on

products.

2.2 Order Procedures:

The system also supplies their product throughout the country. This is only for the

members. Procedures for placing an order are listed below.

2.2.1Order Placement:The member places an order via phone providing the operator his member id, name

and address.

2.2.2Members data Confirmation:The operator searches for the member id and confirms the data related to the

member id.

2


3/159


2.2.3Stock Availability:On confirmation, the operator informs the member about the products and their cost

and amount currently available in stock.

2.2.4Notification of estimate time delivery:

On the members approval, the order is successfully placed and the member isnotified the estimate delivery time on the provided address.

2.2.5Shipment:The order is then forwarded to the suppliers department.

2.2.6Notification of Successful Delivery:

When the order is received by the member, the supplier issues a notification of asuccessful delivery to the shopping mall.

2.3 Feedback:

Feedback is obtained from customers and members to check whether the system

has fulfilled the services being promised, and what can the system do to improvetheir own services. Quality and price assurance, and whether the service was

provided on time.

2.4 Marketing:

WebMart is responsible for the promotion of all the products and services beingprovided. Advertisement is done on newspapers only to aware the members and

other customers of the new products and special packages being offered.

3


4/159


3. Basic Problems and Limitations

3.1 Limited scope:In the manual system the scope is limited to certain geographical boundaries.

3.2 Wastage of Resources:A huge amount of resource like papers, inks, registers, pens, shelves, utilities are

required to be present. A large percentage of these resources are mishandled and

wasted.

3.3 Time consumption:Manual Data Entry, data retrieval, marketing and other processes takes a hugeamount of time.

3.4 To err is Human:

The whole systems processes are being carried on fully through human interactionso a number of human errors occur during fulfillment of tasks.

3.5 Loss of information:The information gathering process is not very secure and efficient in manual

systems therefore there are dangers of information loss during storage process.

3.6 Service updates issues:Company may be interested in adding more services, but notifying customers andmembers takes a huge amount of time.

3.7 Scattered data:All the data is scattered, there is no proper ordering of data and no proper datakeeping mechanism.

3.8 Data Integrity issue:The major concern is data integrity. No proper secure data entry rules are defined.

Data security is at high risks in manual system.

3.9 Transaction security issues:Transaction are being carried out through human interaction, this makes transaction

vulnerable and slow. Insecure transaction processing shakes customers satisfaction

and trust.

3.10Data Backup Issues:Its really a very hard to backup all the data manually as it will take ages to

complete backup process.

4


5/159


3.11 Physical presence:The customer has to be physically present in offices while availing the services.

Customer finds it very much hectic to visit the offices again and again. This wastestime and creates tension in customers mind.

3.12 Dependency on employees:The major processes are fully dependent on employees so the trustworthiness

issue rises.

5


6/159


4. Proposal of the new system

New proposed system is a web based application which will provide services, information

and facilities to customers and members at their own home. This system will cope up with

all the problems and limitations faced in the current system, and will provide some

additional features as well.

4.1 Membership procedures:

4.1.1Customer Registration:Customer will be able to apply for membership online. Their physical presence is not

required. The customer is required to provide his personal information like name,phone number, address etc.

4.1.1.1Acceptance of agreement and policies:As in manual form, detailed terms, rules, policies and conditions of the system and

achieving a membership are stated in this electronic form as well. The customer fillsthe form giving his personal information, and accepts the terms.

4.1.1.2Validation:The information given will be validated automatically. Further validation relating

policies will be completed within 2 to three days.

4.1.1.3Issuing Membership Card:

On successful validation, the customer will be issued a membership card id andpassword to access online membership facilities. He will be required to take the

membership card id by visiting personally or requesting for a home delivery with some

expenses.

4.2 Order Procedures:

The website will provide the customers and members a detailed information of all the

products in the shopping mall that can be home delivered. But members can only order

them.

4.2.1Members Login Confirmation:Member enters his designated card id and password. When login procedure is

successfully completed, he is able to make orders. On any error the user is notified andis required to enter the above described values correctly.

4.2.2Add to Cart:Members can surf the site, add their desired products in their cart.

4.2.3View Cart:

They can view their cart showing a list of items they selected, cost of each item, stock

6


7/159


availability, total cost, and net cost after discount.

4.2.4Order Placement:On members approval the order is successfully placed.

4.2.5Notification of estimate time delivery:The member is notified the estimate delivery time on the provided address.

4.3 Feedback:

Customers can send their feedback, comments online and tips to improve the

companys services. Some multiple choice questions are asked as well.

4.4 Marketing:

The will now have a new media for promotion and marketing of all the products and

services being provided. Advertisement to aware the members and other customers ofthe new products and special packages being offered will be done easily and will be

cheaper and moreover animated than newspaper.

4.5 Online Help:

The visitor can acquire help and ask queries relating business terms and procedures, by

chatting online using java applet.

4.6 Easy Searching:

Customers will be able to search easily by entering desired product name, and searchresults will be displayed.

7


8/159


5. Benefits

5.1 Web Presence:Business organization cant think of surviving in the market without jumping into

IT field. System proposed will provide WebMart with the web presence to avail the

facilities of IT and Internet community.

5.2 Global Access and scope:Due to web presence, the scope of the company will be unlimited. People all overthe world can access the web portal and gather information required.

5.3 Market Penetration:WebMart will be able to penetrate into the related markets through electronic

marketing. This will increase the no. of customers approaching the company.

5.4 Efficient usage of Resources:In computerized system the resources will be well organized and limited. Peopleusing the resources will be well trained so there will be an efficient and better usageof available resources.

5.5 Efficient time management:Most of the processes will be computerized and will be very fast. There time

calculations for all processes will be done; this will result into accurate time

planning.

5.6 Less Human errors:

Due to minimum human interaction with the system there will be lesser chances oferror due to human lapse.

5.7 Accurate information:The information updating process will be much faster and accurate than the manualinformation generation. Information generated through automated processes will be

more accurate and precise.

5.8 Up-to-date Information:Customers always require the current information about the services being

provided. The web portal will display all the current information about products so

that customers can be better informed.

5.9 Centralized data:All the data of the organization will be centralized. This will provide the facility of

easy access of whole organizations data.

8


9/159


5.10 Fast data entry and Retrieval:Data entry process will be rapid as there will be no need of writing etc. all the

inputs will be provided to the computer which will store them into the database.Similarly data retrieval process will fasten up because there will be no searching up

from registers etc.

5.11 Swift Backup of data:In computerized database system the backup taking is very fast process all a person

has to do is running some simple wizard. Automatic processes will backup all thedata.

5.12 E-marketing:WebMart can also do its E-marketing by placing ads on different websites this will

increase the customer numbers and also affects directly the income of the company.

5.13 Secure and fast transactions:Money Transactions will be done online which will remove the threats of cash inhand risks. Also by online transactions the transaction process will be completed

within moments.

5.14 No physical presence of customers:Customers and suppliers will be interacting online with company. They need not tovisit WebMart.

5.15 Professional Aptitude:The new system will create professional aptitude within organization. The abilities

of the organizations will be used to move in a progressive direction.

5.16 Cut-Short of Employees:The computerized system is the automated system which will perform a huge

number of tasks by itself. The employees who are performing these tasks in thepresent system will not be required more. WebMart will be able to cut-short these

employees and save their budget.

5.17 Income growth:Some major factors (cut-short of employees, efficient transaction processing, and

increase in customers) will play a major role in growth of companys income.

9


10/159


6. Hardware and Software Specifications

6.1 Hardware Requirements:

Server

Coaxial cableWork stations

Hard discs

HubsScanners

Monitors

RAMUPS

Printers

6.2 Software Requirements:

Operating system (Windows XP/2000)Internet explorer 6.0 or higher

SQL Server/Microsoft Access

Java Runtime Environment (for java applets)

Macromedia Flash Player 6 or higher.

10


11/159


7. Cost/Benefit Analysis

7.1 Estimation of Profitability

Following is the estimation of profit earning within one business year.

Source Existing

Figures

Future Expected Profitability

Employees Salaries 2,15,000 1,40,000 75,000

IT Department Expenses NILL 60,000 - 60,000

Marketing Expenses 25,000 15,000 10,000

Utility Charges 50,000 35,000 15,000

Income from Customers 4,00,000 6,40,000 2,40,000

Total 2,80,000

7.2 Recovery Period Assessment

Total Estimated Cost = 1,05,389

Estimated Income in a year = 2,80,000

Net Profit in a year = 1,74,611

% of Cost w.r.t. Income year = (105389/280000)*100 = 37.64 %Break even Period = 37.64 % of Time period

Time Period = 12 months

Break-even Period = (37.64/100)*12= 4.5168 months i.e. 135 days approximately

11


12/159


WebMart Analysis

Table of Contents

8. INTRODUCTION 139. REQUIREMENT MODELING 14

Fact Findings 14

Result of Fact Finding 18

Input process and outputs 19

Basic Problems and Limitations 20

Project Scope and Constraints 21

10. DATA AND PROCESS MODELING 22Data Flow Diagram 22

Data Dictionary 27

11. SYSTEM REQUIREMENT SPECIFICATION 36

12. APPENDIX 37

12


13/159


8. INTORDUCTION





customers. WebMart also supply products throughout the country. All the operations of the

system are performed manually.

INTRODUCTION TO THE ANALYSIS PHASE

It is the second phase of System Development Life Cycle, required to learn about the

system request of WebMart. The overall objective of the analysis phase is to understand the

proposed project, ensure that it will support business requirements, and build a solidfoundation for the system design phase. The four steps involved in the analysis phase are:

Requirement modeling

This will include fact findings to describe the current system and define

requirements of the new system. Then categorize the system requirements intoinputs, outputs, processes, performance and controls.

Data and Process modeling

A graphical representation of the new proposed system, to show how processes

transform data into useful information. This will include DFD (Data FlowDiagram), data dictionary and process description.

System Requirements Specification

This is the output of the analysis phase and will further on is used in the System

Design phase. It will describe some main points and functions that the new the

proposed system should perform.

13


14/159


9. REQUIREMENT MODELING

Requirement modeling involves investigation and fact findings to describe the current

system and define the requirements of the new system. Some works we will perform are:

Fact Findings

Result of Fact Findings

Basic Problems and Limitations

Fact Findings

Fact findings will be done to investigate the currents system and identify user requirements.

Some fact finding techniques used are:

Interview

Document Review Observation

Interview :

Few main people to interview are:

Manager of the Company

Receptionists

Manager of Feedback Department

Manager of the Company

Justification of Interviewing the Companys Manager

Interview was conducted due to the following reasons:

To get information about the current system flow.

To get the future plans from the top management.

To get such information from top management which are unknown to low level

people.

To know what are the long term goals and objectives set by the top management forthe organization.

Receptionists

Receptionists are one who is linked to day to day work. They are responsible for handling

major business operations. They have direct contact and interaction with the customers.They know in detail what are the preferences and demands of the customers. Interviewing

14


15/159


from them helped in gathering small pieces of information related to small operations being

performed and the customers point of view indirectly.

Justification for Interviewing the Receptionist


To know how the customers are being handled when they visit for first time.

To know what information must be provided to the customer for membership.

To know what information is required from the customer for the membership.

To know what procedures are done in recording customers information into

registers.

To know how a membership card is issued.

To know what information is required from the member for placing an order.

To know what steps are taken in order to make a successful order placement.

Manager of Feedback Department

Customer feedback management is responsible for:

Approaching such customers who have availed services.

Getting time from them for feedback process.

Providing the customers with the feedback forms.

Collecting feedback forms back from the customers.

Analyzing the feedback forms and ranking the suppliers.

Justification of Interviewing Feedback Departments Manager


Manager is the head of department and can guide more effectively towards thehappenings in the department.

To obtain certain important questions and factors that the department want from the

customer in order to grade the companys business operations.

To further obtain questions that the department wants to ask the customer relating

the new system, in order to grade this new system as well.

15


16/159


Document Review:

Some of the documents being reviewed are:

Membership Form

Membership Card Order Receipt

Feedback Form

Members Information Register

Membership Form

Membership form is a document which is provided to customer when he/she is interested in

becoming a member of WebMart. In it customer has to introduce himself for his interests

and also getting membership, provide his personal information. Further detailed terms,rules, policies and conditions of the system and achieving a membership are stated in the

form.

Justification of gathering Membership Form

Following are the major reasons for gathering Membership Form:

It will tell us about the data elements and other information of the customer that the

organization is interested in storing it.

It will describe about what are the requirements from the customer to become amember.

It will describe about the agreement and issues between the customer and the

organization.

It will describe how the customer enters the information in a filled form.

It will help in designing computerized forms.

Membership Card

On successful completion of the membership process, the customer is issued a membership

card. The card holds some information relating the member

Justification of gathering Membership Card

Following are the main reasons for gathering Membership Card:

It will describe what information the organization wants the member to know inorder to interact with the system.

It will inform about customers general information to be presented on card.

It will be helpful in computerizing the card preparation system.

16


17/159


Order Receipt

An Order Receipt is generated when a customer or a member places an order. It contains

information about the order placed, further information relating product order and somemore information if the customer is a member.

Justification of gathering Order Receipt

Following are the main reasons for gathering Order Receipt:

It will describe the data elements used in the process of a successful order

placement. It will be helpful in creating a computerized order receipt.

Feedback Form

The company has taken feedback from customers and members in Feedback Form to knowhow their company is performing. The customers/members write their comments and

answer to questions with addition to their brief description.

Justification of gathering Feedback Form

Following are the main reasons for gathering Feedback Form:

It will describe the data elements that the organization asks from the customers.

It will be helpful in developing an electronic feedback form.

It will describe in detail, the response of customers on certain important factors thatare of interest to our proposed system.

Members Information Register

The company is not yet computerized and is storing members information on registers.

Some of the data elements that were stored in the Membership form are written on

registers.

Justification of reviewing Members Information Register

It will describe the data elements required by the organization to retrieve quickly

for placing order.

17


18/159


Observation:

Observation is a technique in which the Analyst acts as a third party. Watches and testsevery function and process personally.

Justification of doing Observation:

Major benefits obtained using this technique:

Processes and activities are monitored closely and all the information required was

recorded directly.

Analyst gets a chance to understand the functions and note information regardingthem from his point of view also.

Provides a firm base to information gathered earlier.

Helps in noting down such information that was missed in earlier stages.

Cross checking the information gathered in the earlier stages of analysis.

Result of Fact Finding

Some important information gathered in performing these fact findings are:

The company is performing all their business functions manually.

The company has mainly three role playing entities namely Receptionist, Delivery

department and Feedback department.

The interactions of all the departments are mainly with the Receptionist.

The center point where major business operations are performed and forwarded is

the Reception. Customers visit the Reception in order to have a new Membership.

Customer has to revisit the Reception in order to see if he has become a member.

Customers call the Reception for making delivery order.

Customer has to visit the Reception for submitting his feedback.

There is a lot of crowd in front of the Reception thus making it very difficult for

customers to interact with the company.

The membership process is slow.

The ordering process is slow.

18


19/159


Inputs process and outputs

The three main processes found are:

MEMBERSHIP FORMINPUT PROCESS OUTPUT

Filled Membership form

with Personal Information ofthe Customer

Receive and store members

information

Provide the customer with a

Membership Card

MEMBERS ORDERINPUT PROCESS OUTPUT

Items to order from

customer

Check stock level of items

ordered

Prepare order receipt

Get delivery time estimation

from Delivery Department

Update members

information

Notify stock level to the

customer

Provide order receipt tocustomer

Notify successful orderplacement to customer

Forward order list to theDelivery department

Notify estimate deliverytime to customer

MEMBERS FEEDBACKINPUT PROCESS OUTPUTFeedback from the customer Update members

informationForward feedback toFeedback Department

19


20/159


Basic Problems and Limitations

Limited scope:In the manual system the scope is limited to certain geographical boundaries.

Wastage of Resources:A huge amount of resource like papers, inks, registers, pens, shelves, utilities are

required to be present. A large percentage of these resources are mishandled and

wasted.

Time consumption:Manual Data Entry, data retrieval, marketing and other processes takes a hugeamount of time.

To err is Human:

The whole systems processes are being carried on fully through human interactionso a number of human errors occur during fulfillment of tasks.

Loss of information:The information gathering process is not very secure and efficient in manual

systems therefore there are dangers of information loss during storage process.

Service updates issues:Company may be interested in adding more services, but notifying customers andmembers takes a huge amount of time.

Scattered data:All the data is scattered, there is no proper ordering of data and no proper datakeeping mechanism.

Data Integrity issue:The major concern is data integrity. No proper secure data entry rules are defined.

Data security is at high risks in manual system.

Transaction security issues:Transaction are being carried out through human interaction, this makes transaction

vulnerable and slow. Insecure transaction processing shakes customers satisfaction

and trust.

Data Backup Issues:Its really a very hard to backup all the data manually as it will take ages to

complete backup process.

20


21/159


Physical presence:The customer has to be physically present in offices while availing the services.

Customer finds it very much hectic to visit the offices again and again. This wastestime and creates tension in customers mind.

Dependency on employees:The major processes are fully dependent on employees so the trustworthiness issue

rises.

Project Scope and Constraints

Project Scope

The main processes and business functions that are to be implemented within the boundary

of the proposed system are:

All process relating new Membership

All process relating Order placement

Interact with Delivery Department

Save customer information which is of importance to the Feedback Department.

Save complete customer details.

Present and Mandatory Constrains

Some of the main conditions and requirements that the system must satisfy or the outcomesthat a system must achieve are as follows:

The system must perform the Membership process quickly.

The system must automatically interact with the Customer and should require

minimum manual work.

The system must perform the Order process quickly.

The system must provide any information required by the customer.

The system must provide facilities to the Members.

The system must integrate and handle information properly and accurately.

21


22/159


10. DATA AND PROCESS MODELING

This modeling is used to develop a logical model of the new proposed system and

document the system requirements. The technique we used for graphical representation of

the new system is Data Flow Diagram (DFD). The new system is mostly related in

handling members functions and operations. The tasks that will be completed in thismodeling are:

Data Flow Diagram

Data Dictionary

Data Flow Diagram (DFD)

The symbols used for creating Data flow diagram are Gane and Sarson symbols. Further

diagrams that are created are:

Context Level

Diagram 0

Diagram 1

Diagram 4

22


23/159

Member

0

WEBMART

Online

Shopping

System

Deliver

Departm

Members

Feedback

Department


Context Level DFD

Request for new Membership

Membership Form

Submit Membership Form

Notify errors

Notify successful Membership

Provide Membership ID and password

Request Member LoginNotify login errors

Notify successful login

Request item search

Send search result Forward order listRequest Items to Order Estimate delivery time

Notify stock availability Notify successful delivery

Notify successful order placement

Provide Order Receipt

Notify Estimate delivery time

Send Feedback

Forward Members Feedback

23


24/159

Member

Deliver

Departm

Members

Feedback

Department

2

Members

Login

3

Search

Engine

4

Members

OnlineOrder

5

Online

Customer

Feedback

Members

Members

Products

1

New

Member

Registration


Diagram 0 DFD

Request for new Membership Insert new Member

Membership FormSubmit Membership Form

Notify errorsNotify successful Membership

Provide Membership ID & password

Request Member Login

Notify login errors Verify Login data

Notify successful login Permission status

Request item search Forward search query

Search result Search result

Request Items to Order Check items cost

Notify stock availability Items cost

Notify successful order placement Check stock level

Provide Order Receipt Stock level

Notify Estimate delivery time Forward order list

Estimate delivery time

Send Feedback Notify successful delivery

Update Members data

Update Members data


24


25/159

Member

1.1

Member s

Form

1.2Form

Verification

1.3

Save Form

1.4

ID &

password

Generator

Members


Diagram 1 DFD



Forward form for verification

Notify errors

Forward form for saving


Provide Membership ID & password Insert new Member

Request ID & password

25


26/159

Member

4.1

Stock

Availability

4.2

PrepareOrder

Receipt

4.3

Finalize

Order

Products

Members Deliver

Departm


Diagram 4 DFD

Request Items to Order Check stock level

Notify stock availability Stock level

Items to order

Provide Order Receipt Check Items cost

Items cost

Order list


Notify estimate delivery time

Update Members data

Forward order listEstimate delivery time

Notify successful delivery

26


27/159


Data Dictionary

27


28/159


Data Flow Description

LABEL : Check Items cost ALTERNATE NAME : Check Product cost

ORIGIN : Prepare Order Receipt(process) DESTINATION : Products(data store)

VOLUME AND FREQUENCY :

DESCRIPTION : cost of each item ordered from product database to generate Order Receipt

LABEL : Check Stock level ALTERNATE NAME :

ORIGIN : Stock Availability(process) DESTINATION : Products(data store)


DESCRIPTION :

LABEL : Estimate delivery time ALTERNATE NAME :

ORIGIN : Delivery Department(entity) DESTINATION : Finalize Order(process)


DESCRIPTION : Calculated delivery time for the related order list

LABEL : Forward form for saving ALTERNATE NAME :

ORIGIN : Form Verification(process) DESTINATION : Save Form(process)


DESCRIPTION : Forward a verified membership form for saving

LABEL : Forward form for verification ALTERNATE NAME :

ORIGIN : Members Form(process) DESTINATION : Form Verification(process)


DESCRIPTION : Send form received from Member from data verification and validation

LABEL : Forward Members Feedback ALTERNATE NAME :

ORIGIN : Online Customer Feedback DESTINATION : Customer Feedback Department(entity


DESCRIPTION : Forward online members feedback to the Feedback department

LABEL : Forward order list ALTERNATE NAME :

ORIGIN : Finalize Order(process) DESTINATION : Delivery Department(entity)


DESCRIPTION :

LABEL : Forward search query ALTERNATE NAME :ORIGIN : Search Engine(process) DESTINATION : Products(data store)


DESCRIPTION :

LABEL : Insert new Member ALTERNATE NAME :

ORIGIN : Save Form DESTINATION : Members(data store)


28


29/159


DESCRIPTION :

LABEL : Items to order ALTERNATE NAME :

ORIGIN : Stock Availability(process) DESTINATION : Prepare Order Receipt(process)


DESCRIPTION :

LABEL : Items cost ALTERNATE NAME : Check Product cost

ORIGIN : Products(data store) DESTINATION : Prepare Order Receipt(process)



LABEL : Membership Form ALTERNATE NAME :

ORIGIN : Members Form(process) DESTINATION : Member(entity)


DESCRIPTION :

LABEL : Notify errors ALTERNATE NAME :

ORIGIN : Form Verification(process) DESTINATION : Entity(entity)


DESCRIPTION :

LABEL : Notify Estimate delivery time ALTERNATE NAME :

ORIGIN : Finalize Order(process) DESTINATION : Member(entity)


DESCRIPTION :

LABEL : Notify login errors ALTERNATE NAME :

ORIGIN : Members Login(process) DESTINATION : Member(entity)


DESCRIPTION :

LABEL : Notify stock availability ALTERNATE NAME :

ORIGIN : Stock Availability(process) DESTINATION : Member(entity)


DESCRIPTION :

LABEL : Notify successful delivery ALTERNATE NAME :ORIGIN : Delivery Department(entity) DESTINATION : Finalize Order(process)


DESCRIPTION :

LABEL : Notify successful login ALTERNATE NAME :



29


30/159


DESCRIPTION :

LABEL : Notify successful Membership ALTERNATE NAME :

ORIGIN : Save Form(process) DESTINATION : Member(entity)

VOLUME AND FREQUENCY :DESCRIPTION :

LABEL : Notify successful order placement ALTERNATE NAME :



DESCRIPTION :

LABEL : Order list ALTERNATE NAME :

ORIGIN : Prepare Order Receipt(process) DESTINATION : Finalize Order(process)


DESCRIPTION :

LABEL : Permission status ALTERNATE NAME :

ORIGIN : Members(data store) DESTINATION : Members Login(process)


DESCRIPTION :

LABEL : Provide Membership ID & password ALTERNATE NAME :

ORIGIN : ID & password Generator(process) DESTINATION : Member(entity),Save Form(proc


DESCRIPTION :

LABEL : Provide Order Receipt ALTERNATE NAME :

ORIGIN : Prepare Order Receipt(process) DESTINATION : Member(entity)


DESCRIPTION :

LABEL : Request for new Membership ALTERNATE NAME :

ORIGIN : Member(entity) DESTINATION : Members Form(process)


DESCRIPTION :

LABEL : Request ID & password ALTERNATE NAME :

ORIGIN : Save Form(process) DESTINATION : ID & password Generator(process)


DESCRIPTION :

LABEL : Request item search ALTERNATE NAME :

ORIGIN : Member(entity) DESTINATION : Search Engine(process)

30


31/159



DESCRIPTION :

LABEL : Request Items to Order ALTERNATE NAME :ORIGIN : Member(entity) DESTINATION : Stock Availability(process)


DESCRIPTION :

LABEL : Request Member Login ALTERNATE NAME :

ORIGIN : Member(entity) DESTINATION : Members Login(process)


DESCRIPTION :

LABEL : Search result ALTERNATE NAME :

ORIGIN : Product(data store) DESTINATION : Search Engine(process), Member(entityVOLUME AND FREQUENCY :

DESCRIPTION :

LABEL : Send Feedback ALTERNATE NAME :

ORIGIN : Member(entity) DESTINATION : Online Customer Feedback(process)


DESCRIPTION :

LABEL : Stock level ALTERNATE NAME :

ORIGIN : Products(data store) DESTINATION : Stock Availability(process)


DESCRIPTION :

LABEL : Submit Membership Form ALTERNATE NAME :



DESCRIPTION :

LABEL : Update Members data ALTERNATE NAME :

ORIGIN : Finalize Order, Online Customer Feedback DESTINATION : Members(data store)


LABEL : Verify Login data ALTERNATE NAME :

ORIGIN : Members Login DESTINATION : Members(data store)


DESCRIPTION :

31


32/159


Data Store Description

LABEL : Members ALTERNATE NAME :

ATTRIBUTES : Insert new Member, Permission status, Update Members data, Verify Login data


LABEL : Products ALTERNATE NAME :

ATTRIBUTES : Check Items cost, Check stock level, Forward search query, Items cost, Search result

Stock level


DESCRIPTION :

External Entity Description

LABEL : Customer Feedback Department ALTERNATE NAME :

INPUT DATA FLOWS : Forward customer feedback

OUTPUT DATA FLOWS :

DESCRIPTION :

LABEL : Delivery Department ALTERNATE NAME :

INPUT DATA FLOWS : Forward order list

OUTPUT DATA FLOWS : Estimate delivery time, Notify successful delivery

DESCRIPTION :

LABEL : Member ALTERNATE NAME :

INPUT DATA FLOWS : Membership Form, Notify errors, Notify estimate delivery time, Notify logi

errors, Notify stock availability, Notify successful login, Notify successful Membership, Notify

successful order placement, Provide Membership ID & password, Provide Order Receipt, Search result

OUTPUT DATA FLOWS : Request for new Membership, Request item search, Request items to ord

Request Members Login, Send Feedback, Submit Membership

DESCRIPTION :

32


33/159


Process Description

PROCESS NUMBER : 1 LABEL : New Member Registration ALTERNATE NAME :

INPUT DATA FLOWS :

OUTPUT DATA FLOWS :PROCESS DESCRIPTION

DESCRIPTION :

PROCESS NUMBER : 1.1 LABEL : Members Form ALTERNATE NAME :

INPUT DATA FLOWS : Request for new Membership, Submit Membership Form

OUTPUT DATA FLOWS : Membership Form

PROCESS DESCRIPTION GET request FROM Member

SEND Membership Form TO Member

GET Submitted form FROM MemberSEND form TO PROCESS 1.2

DESCRIPTION :

PROCESS NUMBER : 1.2 LABEL : Form Verification ALTERNATE NAME :

INPUT DATA FLOWS : Forward form for verification

OUTPUT DATA FLOWS : Forward form for saving, Notify errors

PROCESS DESCRIPTION GET form FROM PROCESS 1.1IF errors in form THEN

SEND error notification TO Member

ELSESEND form TO PROCESS 1.3

DESCRIPTION :

PROCESS NUMBER : 1.3 LABEL : Save Form ALTERNATE NAME :

INPUT DATA FLOWS : Provide Membership ID & password

OUTPUT DATA FLOWS : Insert new Member, Notify successful Membership

PROCESS DESCRIPTION GET form FROM PROCESS 1.2GET membership ID & password FROM PROCESS 1.4

INSERT new Member INTO Members database

SEND successful membership notification TO Member

DESCRIPTION :

PROCESS NUMBER :1.4

LABEL :ID & password Generator

ALTERNATE NAME :INPUT DATA FLOWS : Provide ID & password

OUTPUT DATA FLOWS : Provide Membership ID & password

PROCESS DESCRIPTION GET request FROM PROCESS 1.3

SEND Membership ID & password TO PROCESS 1.3

SEND Membership ID & password TO Member

DESCRIPTION :

33


34/159


PROCESS NUMBER : 2 LABEL : Members Login ALTERNATE NAME :

INPUT DATA FLOWS : Request Members Login

OUTPUT DATA FLOWS : Notify login errors, Notify successful login

PROCESS DESCRIPTION GET login request FROM MemberSEND login data for verification TO Members database

GET permission status FROM Members databaseIF permission status IS allowed THEN

SEND successful login notification

ELSE

SEND login error notification

DESCRIPTION :

PROCESS NUMBER : 3 LABEL : Search Engine ALTERNATE NAME :

INPUT DATA FLOWS : Request item search, Search result

OUTPUT DATA FLOWS : Forward search query, Search resultPROCESS DESCRIPTION GET search request FROM Member

SEND search query TO Products databaseGET search result FROM Products database

SEND search result TO Member

DESCRIPTION :


INPUT DATA FLOWS :

OUTPUT DATA FLOWS :

PROCESS DESCRIPTION

DESCRIPTION :

PROCESS NUMBER : 4.1 LABEL : Stock Availability ALTERNATE NAME :

INPUT DATA FLOWS : Request Items to order, Stock level

OUTPUT DATA FLOWS : Check stock level, Items to order, Notify stock availability

PROCESS DESCRIPTION GET order request FROM MemberSEND stock level request TO Products database

GET stock level FROM Products database

SEND stock availability notification TO MemberSEND items to order TO PROCESS 4.2

DESCRIPTION :

PROCESS NUMBER : 4.2 LABEL : Prepare Order Receipt ALTERNATE NAME :

INPUT DATA FLOWS : Items cost, Items to order

OUTPUT DATA FLOWS : Check Items cost, Order list, Provide Order Receipt

PROCESS DESCRIPTION GET items to order FROM PROCESS 4.1SEND items cost request TO Products database

GET items cost FROM Products database

34


35/159


SEND Order Receipt TO Member

SEND order list TO PROCESS 4.3

DESCRIPTION :

PROCESS NUMBER : 4.3 LABEL : Finalize Order ALTERNATE NAME :INPUT DATA FLOWS : Estimate delivery time, Order list, Notify successful delivery

OUTPUT DATA FLOWS : Forward order list, Notify estimate delivery time, Notify successful order

placement, Update Members data

PROCESS DESCRIPTION GET order list FROM PROCESS 4.2

SEND order list TO Delivery Department

GET estimate delivery time FROM Delivery DepartmentSEND successful order placement notification TO Member

SEND estimate delivery time notification TO Member

UPDATE Members database WHERE member is one who orderedGET successful delivery notification FROM Delivery Department

UPDATE Members database WHERE member is one who orderedDESCRIPTION :

PROCESS NUMBER : 5 LABEL : Online Customer Feedback ALTERNATE NAME :

INPUT DATA FLOWS : Send Feedback

OUTPUT DATA FLOWS : Forward Members Feedback

PROCESS DESCRIPTION GET feedback FROM Member

SEND feedback TO Feedback Department

UPDATE Members database WHERE member is one who sent

DESCRIPTION :

35


36/159


11. SYSTEM REQUIREMENT SPECIFICATION

Some of the requirements that the new system should fulfill:

Provide the company with a web presence.

Provide Membership Form online.

Validate the data elements in the form automatically.

Save new members record in the database.

Notify the Customer his successful membership.

Provide him Membership ID and password in order to avail online facilities.

Provide customers an easy and attractive interface to search and surf all productsoffered online.

Provide a search option for customers to easily find what they are interested in.

Provide brief description and information for each product.

Provide Members login/logout facility.

Notify member if login information is incorrect. Show members information and additional option when a member logs in

successfully.

Provide members to easily order items.

Update members data on successful order placement.

Provide Feedback Form to customers.

Update members data after successful feedback submission.

Provide a platform and media for the company to advertise.

Provide a media for the company to introduce themselves.

Provide a media for the company to inform their special offers and schemes to their

members and viewers of the website.

36


37/159


12. APPENDIX

Interviews Conducted:

Name: Mr. Zeeshan Mahmood

Age: 37

Experience: Working for 1 year in WebMart.

Designation: Manager of the Company

Q1: How many branches WebMart has?

WebMart is a newly developed system and has only one branch in Lahore.

Q2: Has the company any computerized System?

Company doesnt have any computerized system working.

Q3: What are the major departments of Organization?

There are four major departments.

Reception

Delivery Department

Customer Feedback Department

Marketing Department

Q4: Are the departments inter-connected?

Delivery and Feedback departments are interconnected to the reception, whereas Marketingdepartment is working independently.

Q5: How are accounts being handled?

Departments control their accounts within them. Account reports are generated and sent ohigh level management.

Q6: What is the mode of payment?

Payments of all kind are done through cash, on delivery payment

Q7: How the forms and other documents supplied to customers?

Customer has to personally obtain it from the Reception.

Q8: Where are all the data of the organizations being stored?

All the data is stored and retrieved manually in registers. Carbon copy of Membership formand Order Receipt is stored.

Q9: How customers approach the organization?

37


38/159


Customers have to visit the company to register themselves and after registration they can

avail services.

38


39/159


Name: Mr. Ali Khan

Age: 33

Experience: Working for 1 year

Designation: Receptionist

Q1: How the customer approaches for new Membership?Customer approaches either by phone or by visiting the Reception himself.

Q2: Who gathers information from the customer?

Receptionists are assigned to gather information from the customers

Q3: How the information is stored?

Information is stored into registers by the Receptionists.

Q4: How different documents and forms are provided to customers?

Documents and forms are provided to customers from the Reception.

Q5: Are there any registration charges?

There arent any registration charges.

Q6: How the contracts are done with customers and the legal issues are handled?

Special contracts are formed addressing all legal issues and every aspect needed to beaddressed. These contracts are to be signed by the customer.

Q7: In how much time registration process completes?

Registration process normally completes in a 3 days.

Q8: When does the member card issued to customers?

Member cards are issued to customers after 2 days of completion of registration

Q9: Which basic information membership card contains?

Membership cards contain introduction of customers and Membership ID.

Q10: What benefits a registered customer gets over non registered customers?

Registered users enjoy special packages and schemes. These packages offer low rates and

gift products etc. The main benefit of member over customer is he can place order onphone and products are delivered to his address.

Q11: How is the Order process carried out?

Member places order on phone giving his information. On verification the member is

notified about the stock availability. The Receptionist prepares the order receipt and

calculates the amount. The Receptionist then forwards the order list to the Deliverydepartment and then inform the customer about the estimate delivery time.

39


40/159


Name: Ms. Ayesha Raza

Age: 33

Experience: Working with the company for 1 year.

Designation: Manger of Feedback Departments

Q1: How the customers are approached by the management?Management approaches such customers who have availed the services. A form is posted

to the customers. This form asks them about the quality of the service they got, timings of

service provision or product bought.

Q2: Why the feedback is gathered by the management?

Feedback is gathered from the customers to grade the business operations. This helps in

providing better facilities to the customers.

Q3: How the feedback form are provided to customers and collected back?

Feedback forms are posted to the customers. Customers have to personally submit it to the

Receptionist.

40


41/159


WebMart Design

Table of Contents

13. INTRODUCTION TO THE NEW SYSTEM 42Context Level DFD 43

Diagram 0 DFD 44

Diagram 1 DFD 45

Diagram 4 DFD 46

14. INTRODUCTION TO THE DESIGN PHASE 47

15. DATA DESIGN 48Unresolved ERD 48

Mapping of ERD 49

16. USER INTERFACE DESIGN 50

17. SYSTEM ARCHITECTURE 59Presentation Tier 59Business Logic Tier 60

Database Tier 60

Why 3-Tier Architecture? 61

Hardware and Software Selection 61

18. DATA DICTIONARY 62Data Flow Description 63

Data Store Description 67

External Entity Description 67

Process Description 68

Data Structures 71Data Elements 72

41


42/159


13. INTRODUCTION TO THE NEW SYSTEM





customers. WebMart also supply products throughout the country.

The technique we used for graphical representation of the new system is Data FlowDiagram (DFD). The new system is mostly related in handling members functions and

operations.

Data Flow Diagram (DFD)

The symbols used for creating Data flow diagram are Gane and Sarson symbols. Furtherdiagrams that are created are:

Context Level

Diagram 0

Diagram 1

Diagram 4

42


43/159

Member

0

WEBMART

Online

Shopping

System

Deliver

Departm

Members

Feedback

Department


Context Level DFD


Membership Form

Submit Membership Form

Notify errors


Provide Membership ID and password

Request Member LoginNotify login errors

Notify successful login

Request item search

Send search result Forward order listRequest Items to Order Estimate delivery time

Notify stock availability Notify successful delivery


Provide Order Receipt

Notify Estimate delivery time

Send Feedback


43


44/159

Member

Deliver

Departm

Members

Feedback

Department

2

Members

Login

3

Search

Engine

4

Members

OnlineOrder

5

Online

Customer

Feedback

Members

Members

Products

1

New

Member

Registration


Diagram 0 DFD

Request for new Membership Insert new Member


Notify errorsNotify successful Membership

Provide Membership ID & password

Request Member Login

Notify login errors Verify Login data

Notify successful login Permission status

Request item search Forward search query

Search result Search result

Request Items to Order Check items cost

Notify stock availability Items cost

Notify successful order placement Check stock level

Provide Order Receipt Stock level

Notify Estimate delivery time Forward order list

Estimate delivery time

Send Feedback Notify successful delivery

Update Members data

Update Members data


44


45/159

Member

1.1

Member s

Form

1.2Form

Verification

1.3

Save Form

1.4

ID &

password

Generator

Members


Diagram 1 DFD



Forward form for verification

Notify errors

Forward form for saving


Provide Membership ID & password Insert new Member

Request ID & password

45


46/159

Member

4.1

Stock

Availability

4.2

PrepareOrder

Receipt

4.3

Finalize

Order

Products

Members Deliver

Departm


Diagram 4 DFD

Request Items to Order Check stock level

Notify stock availability Stock level

Items to order

Provide Order Receipt Check Items cost

Items cost

Order list


Notify estimate delivery time

Update Members data

Forward order listEstimate delivery time

Notify successful delivery

46


47/159


14. INTRODUCTION TO THE DESIGN PHASE

In the previous phase, the logical model of the system was developed. In the design phase

the physical model of the new system will be developed that will meet the specification

described in the system requirement document. System design phase includes:

Data Design

In the previous phase logical design of the information system was built using

DFDs. In this part of the design phase, physical design and plan of the system will

be developed for data organization, storage and retrieval.

User Interface Design

This includes the layout of the interface showing users interaction with the

computer.

System Architecture

System architecture translates the logical design of an information system into aphysical structure that includes hardware, software, network support and processing

method.

47


48/159

MEMBER ORDER

LOGIN

ITEM

FURNITURE

TABLES

FEEDBACK

VENDOR

ELECTRONICS

COMPUTERSPRINTER

INK JETB&W

LASERCOLOR

LASER

PCLAPTOPS

DESKTOPS

MONITORCRT

LCD

COMPUTER

OFFICE

BOOKSRELIGIOUS

SCIENCE & IT

VENDOR

FEEDBACK

OTHER


15. DATA DESIGN

This step involves the development of a physical design for data organization, storage and

retrieval. This task will be completed using Entity Relationship Diagram (ERD). The

ERDs included are

Unresolved ERD

Mapping of ER Model

Unresolved ERD:

Belongs to Places

Sends Placed by

Perform Consists of

Performed by Belongs to

Of

Of

48


49/159

MEMBERSPk * MemberId

* NIC* MemberName

* Address* Discounto Phoneo Mobile

o Email

ORDERSPk * OrderNo* OrderDate

Fk oMemberId

LOGINSFk * MemberId

* LoginDate* LoginTime ITEMS ORDERED

PkFk * OrderNoPkFk * ItemId

* Quantity

* PriceAtSale* DiscountAtSale

VENDORSPk * VendorId

* VendorName

ITEMSPk * ItemId

* ItemName

* PriceFk * VendorId

oDescription

Fk o PcIdFk o MonitorIdFk o PrinterId

Fk o TvIdFk o AcIdFk o BookId

Fk o FurnitureId

PCSPk * PcId

* PcType

* ProcessorType

* ProcessorSpeedo RAMo HardDisk

o IncludedDriveo Videoo OperatingSystemo ScreenSize

PRINTERSPk * PrinterId

* PrinterType* PagesPerMinute

MONITORSPk * MonitorId

* MonitorType* DiagonalSize

* Resolution

BOOKSPk * BookId

* Author*

BookCategoryo Edition

FURNITURESPk * FurnitureId

* FurnitureType* Finish


Mapping of ER Model:

1 m

1

mm 1

m

1

1 1

1 1 m

1

1 1

1 1

1 1

49


50/159


16. USER INTERFACE DESIGN

Few interface sketch shown are for the followings

Home Page

Membership Form

Members Profile

Shopping Cart

Members Order

Products

50


51/159

Companys Logo Banners and other options

Main Navigation Bar

Home Page Information and Pictures Advertisement

Products Navigation

Bar


HOME PAGE

51


52/159


Main Navigation Bar

Products Navigation MEMBERSHIP FORM

Bar


MEMBERSHIP FORM

52


53/159


Main Navigation Bar

MEMBERS PROFILE

Products Navigation Members Information and Options

Bar


MEMBERS PROFILE

53


54/159


Main Navigation Bar

SHOPPING CART

Items Detail

Products NavigationBar

Other options for items in the cart


SHOPPING CART

54


55/159


Main Navigation Bar

MEMBERS ORDER

Order Details

Products Navigation

Bar

Other viewing options


MEMBERS ORDER

55


56/159


Main Navigation Bar

PRODUCTS

Items costItems brief description

Products Navigation

Bar

Other related options and information.

Items Picture


PRODUCTS

56


57/159


17. SYSTEM ARCHITURE

The 3-tier architecture design includes:

Presentation tier

Business logic tier

Database tier

Presentation Tier:

The presentation tier is the top most tier of 3-tier architectural design. It represents thedynamic creation of display code (HTML) that is sent to the user's browser. It

communicates with the other tiers by way of outputting the results to the client tier

(browser) and all other tiers by calling custom tags, calling database stored procedure,calling web services, etc. This layer acts as glue that holds the entire application together. It

binds all of the tiers and ensures that the client sees what was requested in the browser.

57


58/159


Business Logic Tier:

Business logic in PKS is located on the Internet Information Services (IIS).The business

logic tier represents the core functionality of your application. It performs low-level code

and number crunching. It contains and executes the rules that run the application. The

business logic tier acts as the Web Logic Layer between Browser and the Database. Thebusiness logic functionality of this tier is broken into three parts:

Get and send data to the database tier.

Get and receive data from the presentation tier.

Perform necessary calculations and/or data manipulations.

The business logic tier gets data from the database tier and manipulates it according to theneeds of the presentation tier. The business logic tier also takes data provided by the

presentation tier and manipulates it to the needs of the database tier. With .NET, the most

complex logic performed by this tier is now the calculation and manipulation of data (in C#

or Managed C++) to handle business logic.

Database Tier:

Database tier is the final tier of the 3-tier architectural design. The data tier contains thedatabase. It might also include data access procedures. The database can be placed in a

single location or it can be distributed, if required. The database layer takes care of

persistency. An object from the object layer can write itself to one or more tables. In the

database layer you'll find things like database, connection, table, SQL and result set.

58


59/159


Why 3-Tier Architecture?

Now a days3-tier architecture is considered to be the most suitable architecture for large,

Web-based enterprise applications. The partitioning of the application enables rapid design

and development of the system which is not present in the 2-tier architecture.

Advantages of 3-tier Architecture:

Clear separation of user-interface-control and data presentation from application-

logic. Through this separation more clients are able to have access to a wide variety

of server applications. The two main advantages for client-applications are clear:quicker development through the reuse of pre-built business-logic components and

a shorter test phase, because the server-components have already been tested.

Re-definition of the storage strategy wont influence the clients. RDBMS offer a

certain independence from storage details for the clients. However, cases likechanging table attributes make it necessary to adapt the clients application.

Dynamic load balancing: if bottlenecks in terms of performance occur, the server

process can be moved to other servers at runtime.

Change management: of course its easy - and faster - to exchange a component on

the server than to furnish numerous PCs with new program versions.

It is relatively simple to use wrapping techniques in 3-tier architecture. Asimplementation changes are transparent from the viewpoint of the object's client, a

forward strategy can be developed to replace legacy system smoothly.

Low bandwidth network

Business logic sits on a small number (maybe just one) of centralized machines.

Reusability of business logic is greater for the presentation layer,

Migration to new graphical environments is faster,

Hardware and Software Selection:

Hardware: Server

Coaxial cable

Client PCs for employees

Hub

Printer

Scanner

Software: Microsoft Access/SQL Server

Internet Explorer

Windows Advance Server

59


60/159


18. DATA DICTIONARY

This data dictionary has documented the following:

Data Flows Description

Data Stores Description


Process Description

Data Structures

Data Elements

60


61/159


Data Flow Description

LABEL : Check Items cost ALTERNATE NAME : Check Product cost

ORIGIN : Prepare Order Receipt(process) DESTINATION : Products(data store)



LABEL : Check Stock level ALTERNATE NAME :

ORIGIN : Stock Availability(process) DESTINATION : Products(data store)


DESCRIPTION :

LABEL : Estimate delivery time ALTERNATE NAME :

ORIGIN : Delivery Department(entity) DESTINATION : Finalize Order(process)


DESCRIPTION : Calculated delivery time for the related order list

LABEL : Forward form for saving ALTERNATE NAME :

ORIGIN : Form Verification(process) DESTINATION : Save Form(process)


DESCRIPTION : Forward a verified membership form for saving

LABEL : Forward form for verification ALTERNATE NAME :

ORIGIN : Members Form(process) DESTINATION : Form Verification(process)


DESCRIPTION : Send form received from Member from data verification and validation

LABEL : Forward Members Feedback ALTERNATE NAME :

ORIGIN : Online Customer Feedback DESTINATION : Customer Feedback Department(entity


DESCRIPTION : Forward online members feedback to the Feedback department

LABEL : Forward order list ALTERNATE NAME :

ORIGIN : Finalize Order(process) DESTINATION : Delivery Department(entity)


DESCRIPTION :

LABEL : Forward search query ALTERNATE NAME :ORIGIN : Search Engine(process) DESTINATION : Products(data store)


DESCRIPTION :

LABEL : Insert new Member ALTERNATE NAME :

ORIGIN : Save Form DESTINATION : Members(data store)


61


62/159


DESCRIPTION :

LABEL : Items to order ALTERNATE NAME :

ORIGIN : Stock Availability(process) DESTINATION : Prepare Order Receipt(process)


DESCRIPTION :

LABEL : Items cost ALTERNATE NAME : Check Product cost

ORIGIN : Products(data store) DESTINATION : Prepare Order Receipt(process)



LABEL : Membership Form ALTERNATE NAME :

ORIGIN : Members Form(process) DESTINATION : Member(entity)


DESCRIPTION :

LABEL : Notify errors ALTERNATE NAME :

ORIGIN : Form Verification(process) DESTINATION : Entity(entity)


DESCRIPTION :

LABEL : Notify Estimate delivery time ALTERNATE NAME :



DESCRIPTION :

LABEL : Notify login errors ALTERNATE NAME :



DESCRIPTION :

LABEL : Notify stock availability ALTERNATE NAME :

ORIGIN : Stock Availability(process) DESTINATION : Member(entity)


DESCRIPTION :

LABEL : Notify successful delivery ALTERNATE NAME :ORIGIN : Delivery Department(entity) DESTINATION : Finalize Order(process)


DESCRIPTION :

LABEL : Notify successful login ALTERNATE NAME :



62


63/159


DESCRIPTION :

LABEL : Notify successful Membership ALTERNATE NAME :

ORIGIN : Save Form(process) DESTINATION : Member(entity)


LABEL : Notify successful order placement ALTERNATE NAME :



DESCRIPTION :

LABEL : Order list ALTERNATE NAME :

ORIGIN : Prepare Order Receipt(process) DESTINATION : Finalize Order(process)


DESCRIPTION :

LABEL : Permission status ALTERNATE NAME :

ORIGIN : Members(data store) DESTINATION : Members Login(process)


DESCRIPTION :

LABEL : Provide Membership ID & password ALTERNATE NAME :

ORIGIN : ID & password Generator(process) DESTINATION : Member(entity),Save Form(proc


DESCRIPTION :

LABEL : Provide Order Receipt ALTERNATE NAME :

ORIGIN : Prepare Order Receipt(process) DESTINATION : Member(entity)


DESCRIPTION :

LABEL : Request for new Membership ALTERNATE NAME :



DESCRIPTION :

LABEL : Request ID & password ALTERNATE NAME :

ORIGIN : Save Form(process) DESTINATION : ID & password Generator(process)


DESCRIPTION :

LABEL : Request item search ALTERNATE NAME :

ORIGIN : Member(entity) DESTINATION : Search Engine(process)

63


64/159



DESCRIPTION :

LABEL : Request Items to Order ALTERNATE NAME :ORIGIN : Member(entity) DESTINATION : Stock Availability(process)


DESCRIPTION :

LABEL : Request Member Login ALTERNATE NAME :

ORIGIN : Member(entity) DESTINATION : Members Login(process)


DESCRIPTION :

LABEL : Search result ALTERNATE NAME :

ORIGIN : Product(data store) DESTINATION : Search Engine(process), Member(entityVOLUME AND FREQUENCY :

DESCRIPTION :

LABEL : Send Feedback ALTERNATE NAME :

ORIGIN : Member(entity) DESTINATION : Online Customer Feedback(process)


DESCRIPTION :

LABEL : Stock level ALTERNATE NAME :

ORIGIN : Products(data store) DESTINATION : Stock Availability(process)


DESCRIPTION :

LABEL : Submit Membership Form ALTERNATE NAME :



DESCRIPTION :

LABEL : Update Members data ALTERNATE NAME :

ORIGIN : Finalize Order, Online Customer Feedback DESTINATION : Members(data store)


LABEL : Verify Login data ALTERNATE NAME :

ORIGIN : Members Login DESTINATION : Members(data store)


DESCRIPTION :

64


65/159


Data Store Description

LABEL : Members ALTERNATE NAME :



LABEL : Products ALTERNATE NAME :


Stock level


DESCRIPTION :


LABEL : Customer Feedback Department ALTERNATE NAME :

INPUT DATA FLOWS : Forward customer feedback

OUTPUT DATA FLOWS :

DESCRIPTION :

LABEL : Delivery Department ALTERNATE NAME :

INPUT DATA FLOWS : Forward order list

OUTPUT DATA FLOWS : Estimate delivery time, Notify successful delivery

DESCRIPTION :

LABEL : Member ALTERNATE NAME :

INPUT DATA FLOWS : Membership Form, Notify errors, Notify estimate delivery time, Notify logi

errors, Notify stock availability, Notify successful login, Notify successful Membership, Notify

successful order placement, Provide Membership ID & password, Provide Order Receipt, Search result

OUTPUT DATA FLOWS : Request for new Membership, Request item search, Request items to ord

Request Members Login, Send Feedback, Submit Membership

DESCRIPTION :

65


66/159


Process Description

PROCESS NUMBER : 1 LABEL : New Member Registration ALTERNATE NAME :

INPUT DATA FLOWS :

OUTPUT DATA FLOWS :PROCESS DESCRIPTION

DESCRIPTION :

PROCESS NUMBER : 1.1 LABEL : Members Form ALTERNATE NAME :

INPUT DATA FLOWS : Request for new Membership, Submit Membership Form

OUTPUT DATA FLOWS : Membership Form

PROCESS DESCRIPTION GET request FROM Member

SEND Membership Form TO Member

GET Submitted form FROM MemberSEND form TO PROCESS 1.2

DESCRIPTION :

PROCESS NUMBER : 1.2 LABEL : Form Verification ALTERNATE NAME :

INPUT DATA FLOWS : Forward form for verification

OUTPUT DATA FLOWS : Forward form for saving, Notify errors

PROCESS DESCRIPTION GET form FROM PROCESS 1.1IF errors in form THEN

SEND error notification TO Member

ELSESEND form TO PROCESS 1.3

DESCRIPTION :

PROCESS NUMBER : 1.3 LABEL : Save Form ALTERNATE NAME :

INPUT DATA FLOWS : Provide Membership ID & password

OUTPUT DATA FLOWS : Insert new Member, Notify successful Membership

PROCESS DESCRIPTION GET form FROM PROCESS 1.2GET membership ID & password FROM PROCESS 1.4

INSERT new Member INTO Members database

SEND successful membership notification TO Member

DESCRIPTION :

PROCESS NUMBER :1.4

LABEL :ID & password Generator

ALTERNATE NAME :INPUT DATA FLOWS : Provide ID & password

OUTPUT DATA FLOWS : Provide Membership ID & password

PROCESS DESCRIPTION GET request FROM PROCESS 1.3

SEND Membership ID & password TO PROCESS 1.3

SEND Membership ID & password TO Member

DESCRIPTION :

66


67/159


PROCESS NUMBER : 2 LABEL : Members Login ALTERNATE NAME :

INPUT DATA FLOWS : Request Members Login

OUTPUT DATA FLOWS : Notify login errors, Notify successful login

PROCESS DESCRIPTION GET login request FROM MemberSEND login data for verification TO Members database

GET permission status FROM Members databaseIF permission status IS allowed THEN

SEND successful login notification

ELSE

SEND login error notification

DESCRIPTION :


INPUT DATA FLOWS : Request item search, Search result

OUTPUT DATA FLOWS : Forward search query, Search resultPROCESS DESCRIPTION GET search request FROM Member

SEND search query TO Products databaseGET search result FROM Products database

SEND search result TO Member

DESCRIPTION :


INPUT DATA FLOWS :

OUTPUT DATA FLOWS :

PROCESS DESCRIPTION

DESCRIPTION :

PROCESS NUMBER : 4.1 LABEL : Stock Availability ALTERNATE NAME :

INPUT DATA FLOWS : Request Items to order, Stock level

OUTPUT DATA FLOWS : Check stock level, Items to order, Notify stock availability

PROCESS DESCRIPTION GET order request FROM MemberSEND stock level request TO Products database

GET stock level FROM Products database

SEND stock availability notification TO MemberSEND items to order TO PROCESS 4.2

DESCRIPTION :

PROCESS NUMBER : 4.2 LABEL : Prepare Order Receipt ALTERNATE NAME :

INPUT DATA FLOWS : Items cost, Items to order

OUTPUT DATA FLOWS : Check Items cost, Order list, Provide Order Receipt

PROCESS DESCRIPTION GET items to order FROM PROCESS 4.1SEND items cost request TO Products database

GET items cost FROM Products database

67


68/159


SEND Order Receipt TO Member

SEND order list TO PROCESS 4.3

DESCRIPTION :

PROCESS NUMBER : 4.3 LABEL : Finalize Order ALTERNATE NAME :INPUT DATA FLOWS : Estimate delivery time, Order list, Notify successful delivery

OUTPUT DATA FLOWS : Forward order list, Notify estimate delivery time, Notify successful order

placement, Update Members data

PROCESS DESCRIPTION GET order list FROM PROCESS 4.2

SEND order list TO Delivery Department

GET estimate delivery time FROM Delivery DepartmentSEND successful order placement notification TO Member

SEND estimate delivery time notification TO Member

UPDATE Members database WHERE member is one who orderedGET successful delivery notification FROM Delivery Department

UPDATE Members database WHERE member is one who orderedDESCRIPTION :

PROCESS NUMBER : 5 LABEL : Online Customer Feedback ALTERNATE NAME :

INPUT DATA FLOWS : Send Feedback

OUTPUT DATA FLOWS : Forward Members Feedback

PROCESS DESCRIPTION GET feedback FROM Member

SEND feedback TO Feedback Department

UPDATE Members database WHERE member is one who sent

DESCRIPTION :

68


69/159


Data Structures

LABEL : ACS ALTERNATE NAME :

ATTRIBUTES : AcId, AcType, BTU

DESCRIPTION :

LABEL : BOOKS ALTERNATE NAME :

ATTRIBUTES : BookId, Author, BookCategory, Edition

DESCRIPTION :

LABEL : FEEDBACKS ALTERNATE NAME :


DESCRIPTION :

LABEL : FURNITURES ALTERNATE NAME :


DESCRIPTION :

LABEL : ITEMS ALTERNATE NAME :


DESCRIPTION :

LABEL : ITEMS ORDERED ALTERNATE NAME :


DESCRIPTION :

LABEL : LOGINS ALTERNATE NAME :ATTRIBUTES : Insert new Member, Permission status, Update Members data, Verify Login data

DESCRIPTION :

LABEL : MONITORS ALTERNATE NAME :


DESCRIPTION :

LABEL : ORDERS ALTERNATE NAME :


DESCRIPTION :

LABEL : PCS ALTERNATE NAME :


DESCRIPTION :

LABEL : PRINTERS ALTERNATE NAME :


Stock level

69


70/159


DESCRIPTION :

LABEL : TVS ALTERNATE NAME :


DESCRIPTION :

LABEL : VENDORS ALTERNATE NAME :


Stock level

DESCRIPTION :

Data Elements:

LABEL : AcId ALIAS : acid

TYPE & LENGTH : DEFAULT VALUE : NoneACCEPTABLE VALUE : SOURCE : ACS (data structure)

DESCRIPTION :

LABEL :AcType ALIAS : actype

TYPE & LENGTH : DEFAULT VALUE : None

ACCEPTABLE VALUE : SOURCE : ACS (data structure)

DESCRIPTION :

LABEL : Address ALIAS : addr


ACCEPTABLE VALUE : SOURCE : MEMBERS (data structure)

DESCRIPTION :

LABEL : Author ALIAS : author


ACCEPTABLE VALUE : SOURCE : BOOKS (data structure)

DESCRIPTION :

LABEL : BookCategory ALIAS : bcat


ACCEPTABLE VALUE : SOURCE : BOOKS (data structure)DESCRIPTION :

LABEL : BookId ALIAS : bid



DESCRIPTION :

70


71/159


LABEL : BTU ALIAS : btu


ACCEPTABLE VALUE : SOURCE : ACS (data structure)

DESCRIPTION :

LABEL : Color ALIAS : color


ACCEPTABLE VALUE : SOURCE : TVS (data structure)

DESCRIPTION :

LABEL : Description ALIAS : descrip


ACCEPTABLE VALUE : SOURCE : ITEMS (data structure)

DESCRIPTION :

LABEL : DiagonalSize ALIAS : dsizeTYPE & LENGTH : DEFAULT VALUE : None

ACCEPTABLE VALUE : SOURCE : MONITORS (data structure)

DESCRIPTION :

LABEL : Discount ALIAS : discount


ACCEPTABLE VALUE : SOURCE : MEMBERS (data structure)

DESCRIPTION :

LABEL : DiscountAtSale ALIAS : das


ACCEPTABLE VALUE : SOURCE : ITEMS ORDERED (data structure)

DESCRIPTION :

LABEL : Edition ALIAS : edition



DESCRIPTION :

LABEL : Email ALIAS : email

TYPE & LENGTH : DEFAULT VALUE : NoneACCEPTABLE VALUE : SOURCE : MEMBERS (data stru