Business Intelligence Network Inventory Management Computer Science Essay

Published:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

This project mainly deals with automating the tasks of maintaining and transacting the goods.In the Business Intelligence Network, inventory management is the key process. This process includes the activities such as maintenance of stock details, maintenance of receipts and items etc. It is a tedious job to maintain all these details manually. Hence we opted to automate the Business Intelligence Network.

Business Intelligence Network automates the tedious job of system. It mainly includes five members.

1. Administrator

2. Sub-Location In-charge

3. Retailer

4. Supplier

5. Customer

Business Intelligence Network System mainly deals with the following processes.

1. Registration of members

2. Ordering items

3. Acquiring items, Receipts

4. Transferring items

5. Selling items and generating bills

6. Generating reports

The Administrator has the privilege to maintain different types of items in the system.He is concerned with registration of Suppliers, Sub-Location In-charges. He maintains the reports of suppliers who are eligible to supply the items. He can send the purchase order to above suppliers when items are required. He is responsible to add receipts when items delivered to the management system. He is also responsible to send the items to sub-location in-charges on demand. He deals with adding of new items and generating reports on items, orders, receipts and stock ctc.

Sub-location In-charge is registered and verified by the administrator. He is responsible to maintain the items for transferring them to Retailers on demand. He can send purchase order to Administrator for getting items that are required for retailers. He can ship the items to retailer when he got the purchase order from retailer. He deals with generating reports on items, orders and stock etc.

Retailer is registered and verified by sub-location in-charge. He is responsible to maintain the items for selling to customers. He can send purchase order to Sub-location In-charge for getting items that are required for customers. He deals with generating reports on items, orders, bills and stock etc.

The supplier supplies the items based on the order provided by the administrator.

The customer receives the bills from the retailer based on his purchases.

This project fulfills the desires of users to enhance the communication among different type of people such as administrator, Sublocation Incharge and Retailer. And the administrator's job is simplified to the maximum extent.

This system mainly consists of five modules ...

1. Master maintenance

2. Receiving

3. Shipment

4. Billing

5. Reports

Master Maintenance :

Business Intelligence Network system maintains the following master details for various purposes.

i) Suppliers Details

ii) Sublocation Incharges Details

iii) Retailers Details

iv) Items Details

Receiving :

Business Intelligence Network System receives the stock in a validated manner against Purchase Order & Receipt No. Receipts can be tracked down to the pallet id level. Business Intelligence Network receiving process includes all the items necessary to receive, from unloading the trucks to recording the account. This system can perform the following receiving tasks ...

i) Purchase order entry

ii) Receipt entry of goods

Shipment :

Supply Chain Management System provides you a number of functions to maintain the flow of goods.

The following tasks are caused under this module ...

i) Transfer inventory

ii) Put inventory on hold

iii) View inventory balances

iv) View inventory transactions

Billing :

Supply Chain Management billing process allows the retailer to generate new bills and also allows viewing of existing bills.

Reports :

The reports process allows the user to produce the reports necessary for day to day chain management operations. The standard reports are ...

i) Inventory Reports

ii) Purchase Order Reports

iii) Administrative Reports

1.2.GOALS AND OBJECTIVES

Goals:

To automate the Business Intelligence Network in an easy and efficient manner.

To make the jobs of admin, sub-location, retailer easy and trouble free.

To make the application user friendly.

Objectives:

To acquire up to date details about inventory.

To know the status of the Supply Chain Management System.

To reduce the errors those are occurred in the manual system.

To generate the reports as per the management requirements.

To help in ordering of required items.

To provide maximum services to the users.

1.3.SOFTWARE AND HARDwARE REQUIREMENTS

Hardware Requirements:

Processor Pentium III

Speed 800 MHz

Monitor EGI/VGA

Hard Disk 20 GB

RAM 128 M B

Mouse Logitech

Key board TVS

Software Requirements:

Operating System Windows NT

Languages Java 2.0, Jsp, Jdbc.

Web Technologies HTML, JavaScript.

Back End Oracle 8.0

Documentation Tool Microsoft word 2000

ANALYSIS

2.1.USECASES

Business Intelligence Network System Use Čaše:

Fig: Business Intelligence Network Use case Diagram.

Administration Use Čaše:

Fig: Adminstrator Use case Diagram.

login

Brief Description:

This use čaše describes how the user logs on to Business Intelligence Network System.

Flow Of Events:

Basic Flow:

This use čaše starts when the actor wishes to log into Business Intelligence Network System.

The system requests the actor to enter his/her name and password.

The actor enters his/her name and password.

The system validates the entered name and password and logs the actor into system.

Alternative Flow:

Invalid Name / Password:

If in the basic flow the actor enters an invalid name and password the system displays an error message. The actor can choose to either return to beginning of basic flow or cancel the login, at which the use čaše ends.

Special Requirements:

None.

Pre Conditions:

None.

Post Conditions:

If the use čaše was successful the actor is now logged into the system. If not the system state is unchanged.

Extension Points:

None.

change password

Brief Description:

This use čaše is used to change the password of the Administrator, Sub-Location In-charge and Retailer in the Business Intelligence Network System.

Flow Of Events:

Basic Flow:

This use čaše is initiated when the actor wants to change the password.

System requests the actor to enter his/her details.

The actor enters the details.

The system validates the entered details and allows the actor to change the password.

The new password of the actor is stored in the respective database.

Alternative Flow:

Invalid Name / Password:

If the actor enters the invalid name and/or password, the system displays an error message. The actor can choose either return to the beginning of the basic flow or cancels the change password, at which point the use čaše ends.

Special Requirements:

None.

Pre Conditions:

The actor should already be an existing Retailer / Sub-Location Incharge / Administrator.

Post Conditions:

The new password becomes valid.

Extension Points:

None.

Item registration

Brief Description:

This use čaše is used to add a new item, delete any unused item information.

Flow Of Events:

Basic Flow:

This use čaše starts when the Administrator wishes to register new Item.

System asks the Item information from the Administrator i.e. Item name, per-unit cost.

Administrator enters the details.

Now a new instance of Item will be created in the Database.

Alternative Flow:

Invalid Details:

If Administrator enters invalid information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Administrator should logon to the system. Post Conditions:

If flow is successfully completed, new Item information will be generated in database.

Extension Points:

None.

reports

Brief Description:

This use čaše is used to provide appropriate Reports to Administrator.

Flow Of Events:

Basic Flow:

This use čaše starts when the Administrator wishes to see Reports such as total suppliers information, total stock avail etc.

System asks the constraints of Administrator.

Administrator specifies his constraints.

Required reports will appear before the Administrator.

Alternative Flow:

Invalid Details:

If Administrator specifies invalid constraints that will leads to empty report.

Special Requirements:

None.

Pre Conditions:

Administrator should logon to the system.

Post Conditions:

If flow is successfulh/ completed, required report for Administrator will generale.

Extension Points:

None.

stock

Brief Description:

This use čaše is used to provide appropriate information about the stock in the supply chain management to Administrator.

Flow Of Events:

Basic Flow:

This use čaše starts when the Administrator wishes to see Stock Information.

Administrator specifies his request.

System verifies the request of Administrator.

Stock information will appears before the Administrator.

Alternative Flow:

None.

Special Requirements:

None.

Pre Conditions:

Administrator should logon to the svstem.

Post Conditions:

If flow is successfullv completed, stock information will be displaved.

Extension Points:

None.

Admin-Subincharge Transaction Use Gase:

Fig: Adminstrator- Sub Location In-charge Transaction Usecase

SUBLOCATION INCHARGE REGISTRATION

Brief Description:

This use čaše is used to add a new Sub-Location In-charge, delete any unused Sub-Location In-charge information.

Flow Of Events:

Basic Flow:

This use čaše starts when the Administrator wishes to register new Sub-Location In-charge.

System asks the Sub-Location In-charge information from the Administrator i.e. Name of Person, address, phone number etc.

Administrator enters the Person details.

Now a new instance of Sub-Location In-charge will be created in the Database.

Alternative Flow:

Invalid Details:

If Administrator enters invalid information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Administrator should logon to the svstem. Post Conditions:

If flow is successfullv completed, new Sub-Location In-charge information will be generated in database.

Extension Points:

None.

administrator sales order

Brief Description:

This use čaše is used to add new sales order information.

Flow Of Events:

Basic Flow:

This use čaše starts when the Administrator wishes to release goods to a Sub-Location Incharge.

System asks the Sub-location In-charge Purchase Order information from the Administrator i.e. Order number etc.

Administrator enters the Purchase Order details. •& Use čaše will take the information from Purchase Order Details and updates the stock in Administrator stock and Sub-location In-charge Stock.

Alternative Flow:

Invalid Details:

If Administrator enters invalid purchase information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Administrator should logon to the system and Sub-location In-charge should send purchase order.

Post Conditions:

If flow is successfully completed, new Sales Order information will be generated iri database.

Extension Points:

None.

sublocation incharge purchase order

Brief Description:

This use čaše is used to add new purchase order information. Flow Of Events:

Basic Flow:

This use čaše starts when the Sub-location In-charge wishes to order the Items to Administrator.

System asks the Purchase Order information from the

Sub-location In-charge i.e. Cheque number, Item-id, Quantity etc.

Sub-location In-charge enters the Purchase Order details.

Now a new instance of Purchase Order will be created in the Database.

Alternative Flow:

Invalid Details:

If Sub-location In-charge enters invalid information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Sub-location In-charge should logon to the system.

Post Conditions:

If flow is successfully completed, new Purchase Order information will be generated in database.

Extension Points:

None.

Admin-Supplier Transaction Use Čaše

receipts

Brief Description:

This use čaše is used to add receipt information. This receipt will be collected from supplier to Administrator,

Flow Of Events:

Basic Flow:

This use čaše starts when the Administrator wishes to add new Receipt information.

Svstem asks the Receipt information from the Administrator.

Administrator enters the Receipt details.

Now a new instance of Receipt will be created in the Database.

Alternative Flow:

Invalid Details:

If Administrator enters invalid information that will leads to error.

Special Requirements:

None. Pre Conditions:

Administrator should logon to the svstem. Post Conditions:

If flow is successfullv completed, new Receipt information will be generated in database.

Extension Points:

None.

administrator purchase order

Brief Đescription:

This use čaše is used to add new purchase order Information.

Flow Of Events:

Basic Flow:

This use čaše starts when the Administrator wishes to order the Items to particular supplier.

System asks the Purchase Order information from the Administrator i.e. Cheque number, Item-id, Quantity etc.

Administrator enters the Purchase Order details.

Now a new instance of Purchase Order will be created in the Database.

Alternative Flow:

Invalid Details:

If Administrator enters invalid information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Administrator should logon to the svstem.

Post Conditions:

If flow is successfully completed, new Purchase Order information will be generated in database.

Extension Points:

None.

supplier registration

Brief Description:

This use čaše is used to add a new Supplier, delete any unused Supplier information.

Flow Of Events:

Basic Flow:

This use čaše starts where the Administrator wishes to register new Supplier.

System asks the Supplier information from the Administrator i.e. Name of Person, address, phone number etc.

Administrator enters the Person details.

Now a new instance of Supplier will be created in the Database.

Alternative Flow:

Invalid Details:

If Administrator enters invalid information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Administrator should logon to the system.

Post Conditions:

If flow is successfulh/ completed, new Supplier information will be generated in database.

Extension Points:

None.

Sub-Ret Transaction Use Čaše

retailer registration

Brief Description:

This use čaše is used to add a new Retailer, delete any unused Retailer information.

Flow Of Events:

Basic Flow:

This use čaše starts when the Sub-Location In-charge wishes to register new Retailer.

System asks the Retailer information from the Sub-Location In-Charge i.e. Name of Person, address, phone number etc.

Sub-Location In-Charge enters the Person details.

Now a new instance of Retailer will be created in the Database.

Alternative Flow:

Invalid Details:

If Sub-Location In-Charge enters invalid information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Sub-Location In-Charge should logon to the system. Post Conditions:

If flow is successfulh/ completed, new Retailer information will be generated in database.

Extension Points:

None.

SUBLOCATION INCHARGE SALES ORDER

Brief Description:

This use čaše is used to add new sales order information.

Flow of events:

Basic Flow:

This use čaše starts when the Sub-location In-charge wishes to release goods to a Retailer.

System asks the Retailer In-charge Purchase Order information from the Sub-location In-charge i.e. Order number etc.

Sub-location In-charge enters the Purchase Order details.

Use čaše will takes the information from Purchase Order Details and updates the stock in Sub-location In-charge stock and Retailer Stock.

Alternative Flow:

Invalid Details:

If Sub-location In-charge enters invalid purchase information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Sub-location In-charge should logon to the system and Retailer should send purchase order.

Post Conditions:

If flow is successfulh/ completed, new Sales Order information will be generated in database.

Extension Points:

None.

retailer purchase order

Brief Description:

This use čaše is used to add new purchase order information.

Flow Of Events:

Basic Flow:

This use čaše starts when the Retailer wishes to order the Items to particular Sub-Location Incharge.

System asks the Purchase Order information from the Retailer i.e. Cheque number, Item-id, Quantity etc.

Retailer enters the Purchase Order details.

Now a new instance of Purchase Order will be created m the Database.

Alternative Flow:

Invalid Details:

If Retailer enters invalid information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Retailer should logon to the system.

Post Conditions:

If flow is successfulh/ completed, new Purchase Order information will be generated in database.

Extension Points:

None.

Administration Report Use Čaše

administrator reports

Brief Description:

This use čaše generates the report based on the criteria mentioned by the Administrator.

Flow Of Events:

Basic Flow:

System allows the Administrator to select any one of the following options

i) Retailer Report

ii) Supplier Report

iii) Item Report

iv) Sublocation Incharge Report

v) Stock Report

a) Admin Stock

b) Sub-location In-charge Stock

c) Retailer Stock vi) Sales Order Report vii) Purchase Order Report viii)

The Administrator selects option

System performs the search based on the option selected by the Administrator and gives the search results in a forrnatted way as a report.

Alternative Flow:

Invalid Details:

If Administrator enters invalid option that will leads to error.

Special Requirements:

None.

Pre Conditions:

Administrator should logon to the system.

Post Conditions:

If flow is successful, the search results are given to the Administrator in a forrnatted way as a report. Otherwise, the use čaše terminates.

Extension Points:

None.

Sublocationincharge Report Use Gase

SUBLOCATION INCHARGE REPORTS

Brief Description:

This use čaše generates the report based on the criteria mentioned by he Sub-location In-charge.

Flow Of Events:

Basic Flow:

System allows the Sub-Location Incharge to select any one of the following options

i) Retailer Report

ii) Item Report

iii) Stock Report

a) Sub-location In-charge Stock

b) Retailer Stock

iv) Sales order Report

v) Purchase order Report

The Sub-Location Incharge selects option

System performs the search based on the option selected by the Sub-Location Incharge and gives the search results in a formatted way as a report.

Alternative Flow:

Invalid Details:

If Sub-Location Incharge enters invalid option that will leads to error.

Special Requirements:

None.

Pre Conditions:

Retailer should logon to the system.

Post Conditions:

If flow is successful, the search results are given to the Sub-location In-charge in a formatted way as a report. Otherewise, thc use čaše terminates.

Extension Points:

None.

Retailer Report U se ÄŒa se

retailer reports

Brief Description:

This use čaše generates the report based on the criteria mentioned by the Retailer.

Flow Of Events:

Basic Flow:

System allows the Retailer to select any one of the following options

i) Item Report

ii) Retailer Stock Report

iii) Bills Report

iv) Purchase Order Report

The Retailer selects option

System performs the search based on the option selected by the Retailer and gives the search results in a formatted way as a report.

Alternative Flow:

Invalid Details:

If Retailer enters invalid option that will leads to error.

Special Requircments:

None.

Pre Conditions:

Retailer should logon to the system.

Post Conditions:

If flow is successful, the search results are given to the Retailer in a formatted way as a report. Otherwise, the use čaše terminates.

Extension Points:

None.

BlLLS

Brief Description:

This use čaše is used to add bill information. This bill will be given to customer while he is purchasing from a retailer.

Flow Of Events:

Basic Flow:

This use čaše starts when the Retailer wishes to add new Bill information.

System asks the Bili information from the Retailer.

Retailer enters the Bili details.

Now a new instance of Bill will be created in the

Database that will updates the Retailer Stock

Information.

Alternative Flow:

Invalid Details:

If Administrator enters invalid information that will leads to error.

Special Requirements:

None.

Pre Conditions:

Retailer should logon to the svstem.

Post Conditions:

If flow is successfullv completed, new Bill information will be generated in database.

Extension Points:

None.

DESIGN

SEQUENCE DIAGRAMS

Login Sequence:

Change Password Sequence:

Fig: Change password Sequence Diagram.

Supplier Registration Seguence:

Subincharge Registration Sequence:

Item Registration Sequence:

Retailer Registration Sequence:

Admin Purchase Order Sequence:

Admin Sales Order Sequence:

Sub Location In-charge Purchase Order:

Sublncharge Sales Order Sequence:

Retailer Purchase Order Sequence:

Receipt Sequence:

Bill Sequence:

Admin Stock Seguence:

Subincharge Stock Seguence:

Retailer Stock Sequence:

Admin Report Sequence:

Fig: Administrator Report Sequence Diagram.

Subincharge Report Sequence:

Fig: Sub Incharge Report Sequence Diagram.

Retailer Report Seguence:

COLLABORATION DIAGRAMS

Login Collaboration:

Change Password Collaboration:

Supplier Registration Collaboration:

Item Registration Collaboration:

Subincharge Registration Collaboration:

Retailer Registration Collaboration:

Admin Purchase Order Collaboration:

Admin Sales Order Collaboration:

Subincharge Purchase Order Collaboration:

Subincharge Sales Order Collaboration:

Retailer Purchase Order Collaboration:

Receipt Collaboration:

Bill Collaboration:

Admin Stock Collaboration:

Subincharge Stock Collaboration:

Retailer Stock Collaboration:

Admin Report Collaboration:

Subincharge Report Collaboration:

Retailer Report Collabaration:

CLASS DIAGRAM

CLASS DIAGRAM

CLASS DIAGRAM

TABLES

Table Name: ADMINLOGIN

Name

Type

USERNAME

VARCHAR2

PASSWORD

VARCHAR2

Table Name: BILLS

Name

Type

BILLNO

NUMBER

RETAILERID

VARCHAR2

ITEMID

NUMBER

QTY

NUMBER

Table Name: ITEM

Name

Type

ITEMID

NUMBER

ITEMNAME

VARCHAR2

UNITCOST

VARCHAR2

Table Name: RECEIPTS

Name

Type

REPNO

NUMBER

WPOID

NUMBER

Table Name: RETAILER

Name

Type

RETAILERID

NUMBER

PASSWORD

VARCHAR2

NAME

VARCHAR2

HOUSENO

VARCHAR2

STREET

VARCHAR2

CITY

VARCHAR2

STATE

VARCHAR2

COUNTRY

VARCHAR2

PHONE

VARCHAR2

EMAIL

VARCHAR2

Table Name: RETAILERPAYMENT

Name

Type

RPOID

NUMBER

RETAILERID

NUMBER

PODATE

VARCHAR2

CHENO

VARCHAR2

Table Name: RETAILERPURCHASEORDER

Name

Type

RETAILERID

NUMBER

RPOID

NUMBER

ITEMNO

NUMBER

QTY

NUMBER

Table Name: SLPAYMENT

Name

Type

SUBPOID

NUMBER

PODATE

VARCHAR2

CHENO

VARCHAR2

Table Name: DESC SLPURCHASEORDER

Name

Type

SUBPOID

NUMBER

ITEMID

NUMBER

QTY

NUMBER

Table Name: DESC SLSALESORDER

Name

Type

RPOID

NUMBER

SLIID

NUMBER

SLPAYDATE

VARCHAR2

CHENO

NUMBER

ITEMNO

NUMBER

QTY

NUMBER

Table Name: SUBLOCATIONINCHARGE

Name

Type

SUBINCHARGEID

NUMBER

PASSWORD

VARCHAR2

NAME

VARCHAR2

HOUSENO

VARCHAR2

STREET

VARCHAR2

CITY

VARCHAR2

PHONE

NUMBER

EMAIL

VARCHAR2

STATE

VARCHAR2

LOCATIONNAME

VARCHAR2

MAXNOOFRETAILERS

VARCHAR2

COUNTRY

VARCHAR2

Table Name: DESC SUBLOCATIONSTOCK

Name

Type

ITEMID

NUMBER

QTY

NUMBER

Table Name: DESC SUPPLIER

Name

Type

SUPPLIERID

NUMBER

NAME

VARCHAR2

PHONE

NUMBER

EMAIL

VARCHAR2

HOUSE

VARCHAR2

STREET

VARCHAR2

CITY

VARCHAR2

COUNTRY

VARCHAR2

Table Name: WAREHOUSEPAYMENT

Name

Type

WPOID

NUMBER

PAYDATE

VARCHAR2

SUPPLIERID

NUMBER

CHEQUENO

VARCHAR2

Table Name: WAREHOUSEPURCHASEORDER

Name

Type

WPOID

NUMBER

ITEMID

NUMBER

QTY

NUMBER

Table Name: WAREHOUSESALESORDER

Name

Type

SLPOID

NUMBER

WAREHOUSESALEDATE

VARCHAR2

SHIPMENTDES

VARCHAR2

ITEMID

NUMBER

QTY

NUMBER

Table Name: WAREHOUSESTOCK

Name

Type

ITEMID

NUMBER

QTY

NUMBER

// Paste u r screens

CONCLUSION

The main objective of the project is to automate the "Business Intelligence Network". By using ORACLE as back-end and J2EE as front-end under WINDOW NT environment.

This system is used for efficient functioning of the management system works. It deals with maintaining Administrator, Sub-Location In-charge and Retailer.

This project "BUSINESS INTELLIGENCE NETWORK SYSTEM" is very useful and helpful because the effiency will improve with better way of communication among Administrator - Sublocation Incharge, Sublocation Incharge - Retailer.

Reliable and accurate reports could be available with in a very short time, which is not possible if done manually.

Writing Services

Essay Writing
Service

Find out how the very best essay writing service can help you accomplish more and achieve higher marks today.

Assignment Writing Service

From complicated assignments to tricky tasks, our experts can tackle virtually any question thrown at them.

Dissertation Writing Service

A dissertation (also known as a thesis or research project) is probably the most important piece of work for any student! From full dissertations to individual chapters, we’re on hand to support you.

Coursework Writing Service

Our expert qualified writers can help you get your coursework right first time, every time.

Dissertation Proposal Service

The first step to completing a dissertation is to create a proposal that talks about what you wish to do. Our experts can design suitable methodologies - perfect to help you get started with a dissertation.

Report Writing
Service

Reports for any audience. Perfectly structured, professionally written, and tailored to suit your exact requirements.

Essay Skeleton Answer Service

If you’re just looking for some help to get started on an essay, our outline service provides you with a perfect essay plan.

Marking & Proofreading Service

Not sure if your work is hitting the mark? Struggling to get feedback from your lecturer? Our premium marking service was created just for you - get the feedback you deserve now.

Exam Revision
Service

Exams can be one of the most stressful experiences you’ll ever have! Revision is key, and we’re here to help. With custom created revision notes and exam answers, you’ll never feel underprepared again.