DRUG ORDER MANAGEMENT SYSTEM

Guided by: Mr.G.Kishore Assoc.professor(Information technology)

Team members:A.Mounika

reddy(11Q91A1206) N.karthik(11Q91A1229)Suram

Sivanandhan(11Q91A1250)

CONTENTS Introduction Abstract

Proposed system

Existing system

software requirements

Hardware requirements

Modules

Modules and their description

Block diagram

Uml diagrams

testing

conclusion

Screenshots

references

AbstractThis Project “Drugs Orders Management System” is a solution to Aurobindo Pharma to take the orders from its distributors who are geographically distributed

Each user of this system has an unique id and password where user id is used for their identification

The admin provides facility to view and delete customer’s details

And also admin can add, delete, view and update vendor details, category details, discount details and also stock details.

Each user details are kept private where nobody can misuse those details

The payment modes includes DD, Cheque, and online payment mode Credit Card.

EXISTING SYSTEM In this we could store the data manually.

In the existing system data storing was

not

so easy.

Retrieving data is very difficult.

Problem StatementRetrieving the data is difficult

Time consumption is more

Travelling charges are more

Proposed system

The proposed system can be accessed from any part of the world

It is an user friendly system

The admin can view,delete,add the details of the customer

Time consumption is less

Travelling charges are less

Retrieving and maintaing the data is easy

System SpecificationsSoftware requirements

Hardware requirements

Software Requirements•Operating System : WindowsXP•User Interface : HTML, CSS•Client-side Scripting : JavaScript•Programming Language : Java•Web Applications :JDBC,Servlets,

JSP•Database : Mysql•Server Deployment : Apache tomcat

Hardware requirements

Processor : PentiumIV

Hard Disk : 160GB

RAM : 1GB

Modules Administration Module

Reports Module

EndUser Module

WebUserInterface Module

Modules and their description1. Administration Module: In this module admin can add product ,

vendors ,category,discount ,stock and view customer details

And also he can update,delete the product, vendors,category details,discount details,stock details.

Reports module In this module we can view all the

information regarding how many number of customers and vendors.

We can view different categories of products.

we can view discount details and also stock details.

End-User Module In this module customers send orders

for products to admin.

Web-User Interface

Web user Interface will provide the interface to the user to communicate with the system

Block daigram

UseCase Diagrams

Use-case diagram

Use-case diagram

Sequence Diagrams

Sequence communication diagram

Class Diagram

Object Diagram

State Diagram

Activity Diagrams

Component Diagram

Deployment Diagram

Testing Testing is the process of detecting

errors. Testing performs a very critical role for quality assurance and for ensuring the reliability of software.

WHITE-BOX Testing +UNIT Testing

+LINK Testing +INTEGRATION Testing +SYSTEM TestingBLACK-BOX Testing

white-box testing

This is a unit testing method where a unit will be taken at a time and tested thoroughly at a statement level to find the maximum possible errors.

The white box testing is also called Glass Box Testing.

Unit testing

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the process specifications testing is done to uncover errors within the boundary of the module.

All modules must be successful in the unit test before the start of the integration testing begins.

Link Testing

Link testing does not test software but

rather the integration of each module in system.

Integration testing

After the unit testing we have to perform integration testing. The goal here is to see if modules can be integrated properly.

This testing activity can be considered as testing the design and hence the emphasis on testing module interactions.

System testing

Here the entire software system is tested. The reference document for this process is the requirements document, and the goal is to see if software meets its requirements.

Here entire ‘ATM’ has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not.

Black-box testing

This testing method considers a module as a single unit and checks the unit at interface and communication with other modules rather getting into details at statement level.

Here the module will be treated as a block box that will take some input and generate output. Output for a given set of input combinations are forwarded to other modules.

Conclusion

This Project “Drug Order Management System” is a solution to Aurobindo Pharma to take the orders from its distributors who are geographically distributed.

This new system not only takes the orders from distributors for Aurobindo Pharma but it also facilities.

The administration, as well as the report generation for the firm.

It can be accessed from any part of the world, as opposed to stand alone or manual system, and provides information at any time, anywhere.

The organization people can do administration over the products, vendor, customer (only deletion in case of dealer ship cancellation) etc.

Screenshots

references

  ORACLE 8 MASTERING CLIENT- SERVER CONCEPTS

Steven M. Bobrowski SYSTEM ANALYSIS AND DESIGN James A. Senn

VISUAL BASIC 5 DATABASE Dennis Kennedy Joe Garrick Bill Harper Jason T. RoffSOFTWARE ENGINEERING Roger S. Pressman