INVENTORY SYSTEM MC1804 Software Project Development Lab Anna University lab manual download

INVENTORY SYSTEM MC1804 Software Project Development Lab Anna University lab manual download

INVENTORY SYSTEM

Problem Statement

The stock inventory control system is the systematic recording of all the transactions that take place during the purchase of goods. Previously, all these details were entered manually. So it was difficult to refer to all the transaction information later.

In order to overcome these difficulties a computerized form to record the transactions is necessary. Thus the stock inventory control system is designed and implemented. The stock inventory control system will interface with the purchasing, customer order entry, ordering for goods, purchasing register, customer details, pay money, damage, exchange, invoice, sales register and database. The inventory control system will be invoked for the following functions.

·         Customer will purchase goods from the inventory manager.

·         Goods are returned to the supplier for various reasons.

 Purchasing

 When an order from a customer arrives, inventory manager asks the customer to enter the details about the products like product id, product name, quantity etc.

Customer order entry.

When an order is to be placed by the customer, the customer gives the order to the sales person. The sales person checks the availability of the goods from the inventory database.

Damage

The inventory manager informs the supplier about the damage of goods. The supplier will check for the damaged goods. If the goods are damaged, supplier will exchange for the new goods. 

Exchange

           

The goods that have been delivered by the supplier is checked for the damage by the inventory manager. If the goods are damaged then it is subjected for exchange with the supplier. The supplier then replaces the damaged goods by the new goods. The inventory database is updated with the replaced goods.

Ordering goods

 The customer purchases the goods from the inventory manager. The inventory manager check for the availability of goods, if the goods is not available inventory manager can order goods from the supplier.

Invoice

The invoices for all the transactions between the customer, inventory manager and supplier are issued.

Pay money

The customer will pay the money for the goods that has been purchased.

Mode of payment

The customer will pay the amount in the form of cash or cheque or credit card.

Purchasing register

This register will contain purchasing details of the inventory manager from the supplier.

Database

For each and every transaction the database has to be updated.

Sales register

           

This register will contain the sales details of the sales that have taken place with the customer.

Documentation

Use Case Specification: EXCHANGE

Brief Description

The Exchange use-case specifies the importance of damaged stocks that need to be changed and includes the expired dates stocks also. The client who received the stocks from the particular supplier verifies for the valid goods .If any product found to be damaged or expired then it can be exchanged without conditions.

 

Flow of Events

Basic Flow

1.      Both the proprietor and the supplier initiate the use case. The proprietor opens the main form and the exchange option is clicked.

2.      The product name, product number, quantity and value is entered in the exchange form and submitted.

3.      This information is passed and the details are stored in the stock database.

4.      The information pertaining to the exchange of goods is forwarded to the corresponding supplier.

5.      If the supplier possess the stocks requested for exchange then stocks are delivered else the money is returned or refunded.

  

 Alternative Flows

·         Sales basis

The Exchange may also include certain products whose sale does not prove profitable.

In that case the client may request for an alternative good for that product value or get the same product manufactured by a different company.

This request can either be accepted or rejected by the supplier.

·         Damaged Stock

If the delivered goods are found to be damaged or expired then the stocks are   forwarded to the corresponding supplier to exchange items and replace or refund the value of the products dispatched.

Special Requirements

None

Preconditions

Delivery of products

After products are delivered the products are verified to check for any damaged stocks. If the products are found damaged then it is forwarded to exchange.

Payment of that product is also a condition.

 

Post Conditions

Replacement of goods

The immediate effect of Exchange is Replacement of the requested goods.

Supplier satisfies the needs of the clients of replacing the damaged, expired stocks.

Extension Points

None

Use Case Specification: INVOICE

Brief Description

The invoice includes the placement of orders and the delivery of goods to the clients by the supplier, on the demand of entire or partial payment. This also includes Product description, quantity, and rate per unit and total value along with taxes if any. The clients also mention the delivery dates to the supplier.

Flow of Events

Basic Flow

1.      The Supplier is the initiator of the use case. He issues the invoice to the proprietor. The proprietor maintains a separate form to save details pertaining to different invoices issued by different suppliers.

2.      The Goods-Receipts form is completed by entering product number, product name, quantity, price per unit and total value details then it is produced to the proprietor.

3.       The proprietor saves details about the invoice in his system.

4.      After the delivery of goods the proprietor makes payment.

5.       The stock database receives information and database gets updated.    

Alternative Flows

Style of Pay on delivery  

·         The Payment on delivery may be partial or may be entire amount by cash.

·         The Payment may also be based on the delivery of products.

·         If the products are partially delivered then payment of entire bill can be settled later that is partial bill is settled.

·         It can also be on credit basis.

Special Requirements

None.

Preconditions

Orders

Orders need to be placed to produce an invoice to a client by the supplier.

The product requirement, quantities are explicitly defined to value the requirement and produce invoice to deliver.

Post Conditions

Delivery

The Products are delivered to the client requested for service.

The supplier receives the amount specified from his client on delivery

Extension Points

None.

Use Case Specification: Stock Database

Brief Description

The Stock database is maintained by the proprietor in order to keep track of the stocks in hand, orders placed that is the purchase, sales and maintenance of the minimum level, maximum level and the reorder level of the stocks.

 

Flow of Events

Basic Flow

1.      The Proprietor is the initiator who maintains the stocks database. He clicks the stock database option in the main form.

2.      He enters the product name, number, quantity, value per unit etc. in the form.

3.      Save the details to the form.

4.      A message is passed to the form stating the database is updated.

Alternative Flows

Sales basis

The Exchange may also include certain products whose sale does not prove profitable. In that case the client may request for an alternative good for that product value or get the same product manufactured by a different company. This request can either be accepted or rejected by the supplier.

Damaged Stock

If the delivered goods are found to be damaged or expired then the stocks are   forwarded to the corresponding supplier to exchange items and replace or refund the value of the products dispatched.

Special Requirements

No special requirements

Preconditions

Delivery of products

After products are delivered the products are verified to check for any damaged stocks. If the products are found damaged then it is forwarded to exchange.

Payment of that product is also a condition.

Post Conditions

Replacement of goods

The immediate effect of Exchange is Replacement of the requested goods.

Supplier satisfies the needs of the clients of replacing the damaged, expired stocks.

Extension Points

None

Use Case Specification: Purchase Registry

Brief Description

The Purchase registry includes the information about orders placed, quantity ordered, and supplier taking the particular order. This also includes the date of delivery and total value of order placed with price per unit.

Flow of Events

Basic Flow

1.      The Proprietor is the initiator for maintenance of the database. He clicks the stock option from the main form.

2.      He furnishes details in the form like supplier name, product name, product number, order number, quantity, date of order etc. and clicks the submit button or add button.

3.      This information is sent to the database.

4.      The database gets updated and retrieves information after confirmation message is sent to the order form about the updated details.

5.       The order details are forwarded to the Transaction manager to handle purchase orders effectively.

6.      The Transaction manager then forwards the order to the prior supplier.

7.      The supplier registers the orders.

8.      An invoice is sent to the proprietor as a mark of order registration and specifies value of products ordered. 

Alternative Flows

None

Special Requirements

None

Preconditions

Stocks have reached below the minimum level or there are no stocks for sale and hence orders are placed.

Post Conditions

The Stocks are delivered on demand of payment of product value and optimum levels of stocks are maintained in the shop.

Extension Points

None

Use Case Specification: Payment

Brief Description

The Payment refers to the billing of products purchased by the customers from the shopping center. The payment involves the price of the goods and any discount allowed. The   proprietor has to produce a bill to the customer inclusive of taxes to the customer on demand of payment of the products purchased.    

Flow of Events

Basic Flow

1.      The Proprietor clicks the Customer bill option from the inventory software main form

2.      The Customer bill generation form is opened.

3.      The entry to the various fields like customer name, product number, quantity, price and total value is entered by the proprietor.

4.       After generating the bill to the customer, the prior products and its sold value is updated in stock and sales databases respectively.

5.      The bill is generated to the customer and a copy is saved for updating databases on payment. There can be no credit system on payment in this inventory software

Special Requirements

None

 

Preconditions

The customers purchase their necessary products from the shop. On generation of bills to the products from the billing section customers need to pay to obtain their purchased product.

Post Conditions

Generation of bills induces payment and customers are requested to obtain their purchase products from the Delivery section.

Extension Points

None

Use Case Specification: Sales Registry

Brief Description

The sales registry includes the movement of stocks with respect to the direct consumers. The sale includes the price per unit and the total value. The sales will project the product’s outflow and the stocks in hand value to calculate the profit.

Flow of Events

Basic Flow

1. The Proprietor is the initiator of the use-case. He clicks the customer bill form and enters the prior information in various fields of the form.
2. If discounts are allowed then prior price has to be deducted from the MRP of the product before generating the bill.
3. Generates the bill in the form and forwards to the printer to print the form.
4. The customer obtains the bill on payment and products are issued.
5. The informations about the sold goods from the customer bill generated are passed to the sales registry.
6. The various fields in the register are completed and information is passed to update stock database.
7. The stock database is updated and values are stored. A message is passed to the sales form informing the updation of the stocks database.    

Alternative Flows

There are no alternative flows for this use case.

Special Requirements

There are no special requirements pertaining to sales.

Preconditions

The products are purchased and kept for sales. The product and its utility value and price value is Precondition for sales.

 

Post Conditions

The profit of the shop is the major outcome of the sales.

Extension Points

The extension point to the sales registry is the Discount.

The Discount may be due to festive offers or for the disposal of the old stocks.  

Name of extension point

Discount is the only extension point

Use Case Specification: <Stock database>

 

Brief Description

The Stock database is maintained by the proprietor in order to keep track of the stocks in hand, orders placed that is the purchase, sales and maintenance of the minimum level, maximum level and the reorder level of the stocks.

Flow of Events

Basic Flow

1.      The Proprietor is the initiator who maintains the stocks database. He clicks the stock database option in the main form.

2.      He enters the product name, number, quantity, value per unit etc. in the form.

3.      Save the details to the form.

4.      A message is passed to the form stating the database is updated.

Alternative Flows

None.

Special Requirements

None

Preconditions

1. The stocks are purchased first either on a wholesale market or from factory outlets.
2. Stocks are fixed to have minimum level and maximum level and are maintained.

 

Post Conditions

The stocks are purchased and delivered according to the orders placed.

Reorder level is fixed to maintain the inventory of the shop.

 

Extension Points

None

Use Case Specification: <Supplier database>

Brief Description

The database includes the information pertaining to the different kinds of supplier their address, stocks needed from them, stocks delivered, date of delivery, exchange, and the proprietor of the shop maintains receipts. They keep of the track of orders placed to the different suppliers.

Flow of Events

Basic Flow

1.      The Proprietor is the initiator of the use case. The proprietor clicks supplier form to open from the main page.

2.      He enters the details in the form like supplier name, phone no., address, product, invoice no, delivery date etc. 

3.      Submits to the database.

4.      The database gets updated and values are stored.

5.      A message is passed to the form “database updated”.

Alternative Flows

No alternative flows exist.

 

Special Requirements

No Special requirements.

Preconditions

The Proprietor needs to be a client of one or more suppliers to obtain stocks than to manufacture by himself the necessary products for his shop.

Post Conditions

The Proprietor will contain all necessary details about the supplier whom he has given orders and track information about his orders and delivery of the same.

Extension Points

There are no extension points for the use case.