The developer is responsible for development of the underlying database structure which shall serve as an online shop. The developer shall also be responsible for development of both the customer and the businessman interface for the online shop which shall both make use of the underlying database structure.
The developer will also train the user to use the interface and show sample data entry and deletion. The database must then be built by the client. 2 Chapter 2 General Description 2. 1 Product Perspective Relationship with other products and principal interfaces The interface will be in 2 basic parts 1 .The businessman interface for data deletion,entry and the management of the policy set. The above encompasses all shopkeeper functions such as changing the item information, managing the dispatch time-table et al 2.
The customers interface for buying goods and querying. This shall also include a bulletin board which shall serve as a platform for selling goods,and by extension thereby,auctions. The interface will provide for an easy search so that the customer will be able to locate the product of his choice easily.The data items in the shop will be organized in semantics units called rooms which hold similar products.
The rooms are themselves have child rooms , a parent room and data items in the room . We are using a tree destructive for the same. Both of the above interfaces shall make changes to the same underlying database structure which in totality shall constitute an online shop. 2. 2 Product Functions Overview 1 . Enable customer to buy online.
2. Enable customer to easily browse through the products 3. Needle customer to search allowing customers to post queries and discuss products and sell through us. Low the businessman to manage the shop inventory.
Allow the businessman to view rapes depicting previous sales etc. Allow the businessman to change the look and fell of the site with ease. Allow the shopkeeper to view did rent con gyration options and update them. This information is used for calculating discounts et al. These users have to be registered. 3.
2. 8 Entity Users Field user id user name address email credit card no Join date Varitype Domain Constraint Description integer primary key An identity err acting as primary key parch(20) not null User Name parch(100) not null Address of user parch(40) Email Address integer not null Credit Card Number date not null date of registering parch(20) registered or unregistered I Nils .NET y contacts all ten users,ton registered Ana unregistered.I en type AT user is stored in the Varitype led. 3.
2. 9 Entity Dispatch table Field Dispatch id user id Item id Quantity Priority Domain Constraint Description integer primary key An identity err acting as primary key integer not null I-KID of the user who places order integer not null This is the id of the item being ordered integer not null This gives the quantity of the item ordered integer not null This is the priority of the order placed This is the anal storage unit for the transition information about a deal.When a user on arms to a particular deal, an entry is made in this table to signify the same. This entry is later processed for anal dispatch after the time for tentative changes has expired. During this period the user can take cancel his order if he intends to.
This period can again be varied depending upon the urgency of the order placed. Thus it acts as a buy err to store the transaction details. A thread polls this table after a species deed time to check for any update if required.It may be that the buy err period for a particular item order has expired and it can thus be sent for anal delivery. 18 3.
2. 0 Entity Mode of payment Field Domain Constraint Description MOP id integer discriminator An identity err acting as Dispatch id integer not null This indicates the primary key of the strong entity Amount oat not null This gives the amount per MOP per Dispatch This table represents a weak entity with the dispatch table as the strong entity.This stores the mode of payment used by a particular transaction. 3. 2.
11 Entity policy set Field Domain Constraint Description coy type parch(20) primary key the name of the policy type egg. Dispatch NFG star parch(20) not null this shall be a string in CNN form which shall contain conditions entailing the This entity contains the policies in a CNN form corresponding to each policy type,which shall be computed from the input received from appropriate interface. . 2. 12 Entity shopping basket Field user id item id quantity Domain Constraint Description integer foreign key references users User old integer foreign key references item Item old integer not null Gives the quantity of the item in the basket This acts as a buy err for each customer session wherein all the items selected for buying shall be put into the basket.
