Main zota abstract

Zota Health Care Pvt. Ltd

DR. S. & S. S. GHANDHY COLLEGE OF ENGINEERING & TECHNOLOGY

SURAT

6th SEMESTER

PROJECT REPORT OF

“Zota Health Care Pvt.Ltd”

SUBMITED TOInforamation Technology Department

YEAR-2013

GUIDED BY:- SUBMITED BY:- Mr. Laxman C. Ninama Girase Rakesh(106120316008)

Jariwala Hitanshu(106120316010) Panchal Aakash(096120316051)

Page No: 1 / 83


DR.S. & S. S. GHANDHY COLLEGE OFENGINEERING & TECHNOLOGY

SURATCERTIFICATE

This is to certify that Girase Rakesh,Jariwala Hitanshu,Panchal Akash student of Diploma in I.T. Department has successfully completed their project under title “Zota Health Care Management” in according with technical and theoretical specifications for the year 2013.

External Guide Course tutor H.O.D Principal

Page No: 2 / 83


Page No: 3 / 83


PROJECT PROFILE:-

Project Title : Zota Health Care Pvt.Ltd

Objective : To reduce the daily time Consumption for Data

entry, reduce the burden of manual work, for

effective management of effective tasks, for co-

ordination among different tasks etc.

End User : Zota Health Care Operators

Front End Tool : Microsoft Visual Basic 6.0

Back End Tool : Microsoft SQL Server 2005

Project Guide : Mr. Laxman C. Ninama

Submitted by : Girase Rakesh,Jariwala Hitanshu,Panchal Aakash

Submitted To : Dr. S. & S.S. Ghandhy Engg.college surat.(I.T Department)

Page No: 4 / 83


ACKNOWLEDGEMENT

Before penning a single word for the project, we take this opportunity to thank all those who have helped us directly or indirectly in making our project live and turn it into a successful piece of work. Many People have contributed to this project in a verity of ways. Words are not enough to describe their support and faith in us. But still we want to thank all of them.

Firstly, we would like to thank god and our parents who always bless us and motivate to achieve our desired goals in life.

We also express our thinks to Mr. Laxman C. Ninama of our heart who guided us as much as

possible and for giving us valuable information regarding to our project. Our Special thanks go to Mr.JatinBhai who gave us his various views and innovative ideas for this project.

The Project would not have been successfully completed without continuous support, motivation extended by our colleagues and friends who were always with us whenever we needed.

This was the first professional step towards the high profile career in computer field. So, we are thankful to IT Engineering Department for facilities that are provided to us for accessing the lab. It was a great experience of exposing as well as learning lot of new things in Computer Engineering. We are indebted to all those who provided reviews our task and we apologize to anyone if we may have failed to mention.

Last but not least, thanks to Dr. S & S.S. Ghandhy College of Engineering & Technology for providing us the platform to present the project.

Page No: 5 / 83


INDEX

Sr.No. Abstract Abstract Page No. Page No.

1. Company Profile 07Company Profile 07

2. Project Definition 11

3. System Profile 16

4. System Analyses 20

5 System Requirement Specification 24

6 Tool Information 27

7 Dataflow Diagram 34

8 Entity Relationship Model 43

9 Data Dictionary 47

10 Screen Shots 56

11 Testing 76

12 Conclusion 81

13 Bibliography:- 83

Page No: 6 / 83


Page No: 7 / 83


COMPANY PROFILE :-

The tormenting desire to serve mankind and also the ambition to make a dent in one of the fastest growing Pharma industries is the name ZOTA HEALTH CARE LTD. Now ZOTA is turned into a GROUP with 18Division in its fold, viz.

ZOTA HEALTH CARE LTD

ZOTA PHARMACEUTICALS

ATOZ PHARMACEUTICALS

SAYONA

MARLINE BIO CARE

PSYCHO GEM

Ceedee LIFE CARE

SPRINGER BIO-TECH

MEDI COST

MEXON HEALTHCARE

HEALTH PARK LABORATORIES

OPTHALGEM

NEERMN

CORPUS PHARMA

MAGENTA

DENTO GEM

DERMOGEM

VISION MEDILINK

To meet the demand of the trade, ZOTA Group can today boldly claim to have over Two thousand two hundred products in its mix. To free the doctors from the dependence on multiple of companies, ZOTA today offers an unmatched range of products under a single roof. The strength of the natural treatment too has been promoted with separate AYURVEDIC Division.

ZOTA formed the required traits of a truly STANDARD Pharma Organization with the ETHICS of not indulging into unscrupulous practice and unwavering QUALITY with ZERO DEFECT; in fact,ZOTA was approved with the prestigious ISO 9001:2005 Certification & CRISIL SE 1A. This Rating Indicates "HIGHEST" Performance Capability and "HIGH" Financial Strength. In addition to Quality Control, the company has adopted Total Quality Management System, which leaves

Page No: 8 / 83


no stone unturned to keep the product with International Quality Standards.

Our R&D is extensively working on unique and novel formulations especially in nutraceuticals.Already applied ten unique different formulations for patent and amongs them two products is applied for PCT for 142 countries. The formulation which has gone for PCT already introduced in domestic market and accepted by medical fraternity very well. RTFit is a unique and novel combination of two amino acids for liver disorders especially for alcoholic hepatitis with unique mode of action without any complication due to its natural origin. Apart from RTFit other patent applied formulations will be available shortly. Company has already started the clinical trial of RTFit in various liver disorders with good no. of patients to evaluate the efficacy and safety of RTFit.

ZOTA has setup the production facility for the EXPORT at Surat in the Surat Special Economic Zone, Nr. Sachin Railway Station, Sachin, Surat. (Gujarat). This manufacturing plant follows cGMP & WHO conditions comparable with the international regulations (MCC South Africa & MHRA U.K And USFDA.). The company is primarily involved in manufacturing of Tablets & Capsules (General group).

Our Products:

Tablets

Oral Liquid

Dry Powder

Capsules

Softgel Capsules

Injectables

Ointment

Cream

Lotion

Medicated Soaps

Eye / Ear Drops

Ayurvedic Products

Toothgel

Mouthwash

Gumpaint

Shampoo

Page No: 9 / 83


Infrastructure

ZOTA Group is a professionally managed organization incorporating most modern management systems and procedures. ZOTA comprises highly qualified, well experienced and dedicated pharmaceutical and technical professionals from floor level to marketing.

Mission

Our mission is to provide innovative products to our customers at competitive rates and prompt delivery at the highest level of professional services. Today, ZOTA and its Division are present almost in every part of the country. The company is currently focused on making a renewed thrust in the international market with branded formulations as well as high quality generics.ZOTA has the Globe in the vision and determined to reach its Goal and expects you to makeZOTA your trusted Goal.

Page No: 10 / 83


Page No: 11 / 83


PROJECT DEFINATION:-

Zota Health Care Management is Windows bases Information System developed using Visual Basic 6.0 as Front End and SQL Server 2005 as Back End for the operator who is engaged taking Sales Order and then prepare sales order delivery challan and also make sales invoice for dealer.

System would be able to manage day-to-day transactions like, Purchasing product from supplier,Managing inventory stocks, Generating Delivery Challans, Invoices and Receipt Vouchers. System will be also capable to generate various reports for effective decision making.

MODULE SPECIFICATION:

1. Master Module2. Purchase Module3. Sales Module

1. Master ModuleThis module is related to all master data such as Supplier Master,Dealer Master ,Product Master and Bank Account Master.In this Module,we can also report the master information about the Supplier,Dealer and Product.

Scope:Maintaining Supplier MasterMaintaining Dealer MasterMaintaining all information about ProductMaintaining Bank Account Detail of Dealer and Supplier

2. Purchase ModuleThis module is related to Purchase Process has being Worked in Zota Health Care

Management.This module maintain purchase Enquiry,recived Quatation,order,invoice and delivery

Challan.

Scope:Preparing Purchase EnquiryReceiving Quatation Detail from SupplierPrepare Purchase OrderPrepare Purchase Dellivery ChallanPrepare Purchase Invoice for Supplier Prepare Payment Voucher

Page No: 12 / 83


3. Sales ModuleThis module is related to Sales Process has being Worked in Zota Health Care

Management.This module maintain information about the sales order,sales invoice and sales delivery challan.

Scope:Prepare Sales OrderPrepare Sales Dellivery ChallanPrepare Sales Invoice for DealerPrepare Receipt Voucher

Page No: 13 / 83


Project Activity ChartProject Activity Chart

No Task Name Start Finish Duration1 System Analysis 25/07/2012 01/08/2012 7d2 System Design 02/08/2012 10/08/2012 8d3 Database

Implementation11/08/2012 18/09/2012 8d

4 System Coding 19/09/2012 19/10/2012 30d5 Testing &

Implementation20/10/2011 30/11/2011 10d

6 Documentation 1/11/2011 5/11/2011 5d

Page No: 14 / 83


Schedule

Page No: 15 / 83

Weeks Months

Week 1 Week 2 Week 3 Week 4

1st

Month

Introduction to Institute.

Introduction to Visual Basic 6.

Introduction Of Existing System.

Collect all Basic things of System.

We are Gone For System Analysis In Industry.

Study the Industry in Detail.

2nd

Month

Study of Process of industry .

Start Basic Designing of Forms.

Continue learning of

programming language,

concepts.

Deciding the process model of the proposed project.

Finish the analysis and decide the GUI design of project

Start gathering information about the various Projects.

Collect all Information Of SQL SERVER2005.

All Query & Basic Connectivity Learn.

3rd Month

Work on the design features. Defining the system design with the database.

Complete the System Requirement Specification.

Complete the Diagrams Like Data Flow & Entity Relationship Diagram.

Complete Some Database in Sql Server2005.


System Profile

EXISTING MANUAL SYSTEM

The Zota Health care is pharma compony which provide product of medicine in all india This industry includes Following Departments Like:

Stock Management Department.. Bank Account Department Purchase Department. Sales Department.

According to number of Departments in this Industry they are Maintaining all the Details Manually. The Existing Manual System create many losses of information to the Industry .

The Manual System is main Problem of this Industry. In purchase Department the purchase manager facing problem in maintaining the all details of the Dealer which supplies the basic material to the Industry.

Today they are using Manual System to Maintain their Data and Information about their different types of Department.

Because of using Manual System their industry faces to many problems which are generated by the improper Management.

They are Maintaining Manually Details Following Contents. Supplier Details. Dealer Details.

Page No: 16 / 83


Stock Of Product Prepare Purchase Order Prepare Purchase Invoice Prepere Sales Order Prepere Sales Invoice

PROBLEMS FACED BY CURRENT MANUAL SYSTEM

[PROBLEM IDENTIFICATION]

Summary of Problem:

Delay in purchase Product from Suppliers. Problem in stock management like maintaining of product Details and Consumption details of

product. Delay in Delivery of Product. Their is no Standard System to Maintaining Following issues:

Details of Suppliers. Details of Dealers. Difficult to Maintenance of Stock of Product.

Difficult for Daily Bank Transaction of Account Details Because of Manual system.

Detailed Description of Problem :

Delay in purchase Product from Suppliers the reason behind this Problem is there is

Not be Standard System to purchase a Product.. Because of Manual System.

Sometimes Problem in Stock Department can not provide detailed informationabout Purchase Product and Product consumed during Sales.. Even in the Existing System it is Difficult to calculate the Surplus in stock for Product consumption. So Purchase Manager will delay to place purchase order which ultimately results to the late delivery to Supply in Specified time Duration when the Product require to Sales Department .Which results to the disturbance in the Sales procedure .

Another problem is difficult to maintain dead stock of Product.

Page No: 17 / 83


Delay in Deliver product to Dealer the reason behind in this problem Sales

Department can not maintain the details of Product requirement notification that are use in Sales procedure .So Sales manager will delay to place details of Product requirement to Stock manager .

There is no Standard System to maintain details about Dealer and Supplier. which results problem in calculating the bill payment of an Dealer and Supplier because of this

reason sometime misunderstanding between management and Dealer and Supplier.

Sometime Dealer or Supplier leaves the Industry Using the Manual System difficult to store details of Supplier and details of Dealer.

Difficult to generate the daily Product consumption rate and the cost of consumption Product in existing system.

Expected Outcome:-

In Our first phase of project we are visited industry three & Five times .In this phase we are analysis all process and activity of industry.

All work are doing on manually so they are facing some problem.

This problem we are describe in problem summary. We are develop project for Zota Health Care PVT. LTD. industry base on their requirement and provided information to our project team.

We Will shifting their manually work to computer work so.Their Timework is Reduced and Solve Their Existing Problem That They Are Facing Today.

We are solve existing problem of manually system by following form

1. We are solve problem of delay in purchase Materials by using Standard System in which we are providing intercommunication between Stock Department and Purchase Department.

2. Easy for Stock Department to maintaining of Product Details ..

3. Proper Standard system for maintaining Stock and Purchase so Delivery of Product on given time .

4. Easy to Generate daily Consumption Rate of Product and Product Cost because of computer system better than manually system and more correct than existing system.

5..Because Of Standard System There Is ,Easy For Maintain The Stock of Stock Of

Page No: 18 / 83


Delivery challan,Stock Of Sales Challan,Stock Of Purchase Invoice , Stock Of Sales Invoice,Stock Of Payment Voucher,And Stock Of Receipt Voucher For Account Department.

6. Because Of Standard System There Is Easy for Bank Transaction Of Industry And Maintaining Bank Account Of Industry For Account Department.

Page No: 19 / 83


System Analysis

Activity In Purchasing Material :-

Following process chart of industry describes internal process of purchase of material, Inventory management, Production process, Role of Account Department

.

Fig 1.2 Purchase Process of Industry

Page No: 20 / 83


Purchase Process of industry :-

First Process Is Purchase Manager Gives Product Note To Admin Manager.And Then Administrator Gives the Product Target Note To Purchase Department.

Then Purchase Manager first inform to admin of Industry then Send purchase inquiry to their Suppliers of material .Then Suppliers send their respective Quotation to Purchase Manager Then Purchase department check Quotation on predefined rules or standard material then select quotation and send purchase Order to selected quotation of supplier of material

Fig 1.5 Process of Purchase & Payment

Supplier Delivers Material To Stock Depts. And Give The Purchase Challan Inventory Department Then Suppiler send Invoice to Account Department then Account Manager Give Payment Voucher

to Suppiler. After purchasing material then Inventory Department delivers Material to Production And

Maintenance Department .

Then Production chain is completed then product is dispatch to Sales Department and Sales Department sends Sales Invoice To Account Department then product delivery to Job Order Dealer then Client give Receipt voucher to Account manager .

Scope Of Departments :-

1.Inventory Department:- Receive Purchase Challan. Prepare Material Issued Note(MIN).

2.Purchase Department:- Send Purchase Inquiry. Receive Quotation. Give The purchase Order .

Page No: 21 / 83


Maintain Supplier Details and His Personal Account.

3.Account Department:- Receive Purchase Invoice. Prepare The Payment Voucher. Receive Sales Invoice. Receive Receipt Voucher from Job Order Contractor. Maintain Bank Account Details.

4.Sales Department:- Generate Sales Invoice . Generate Sales Challan. Receive Dellivery Challan

Methodology :

Feasibility Study Project schedule E-R diagram Context diagram Data flow diagram Table layout Coding Testing Documentation

Page No: 22 / 83


Page No: 23 / 83


SYSTEM REQUIREMENTS SPECIFICATION(H/W Specification)

(1) HARDWARE REQUIREMENTS OF THE SYSTEM:

This phase of the software development process deals with a brief study of different hardware used

in the computerized system. There is a list of hardware materials used during the making and also during the

use of the proposed system. As the new system to be made into a computerized functional system,

requirement of a computer is must. All the hardware needed here are generally the basic configuration of a

typical office computer. A list of the hardware requirement used in the system given below:

Minimum Configuration :-

To run the application software of the system in the computer the minimum configuration

required is as below:

233 MHz Pentium processor or other compatible.

Intel Chipset Motherboard.

32 MB SD-RAM.

2 – 4 GB Hard-Disk.

4x Compact Disc drive or faster.

1.44 MB Floppy Disk Drive.

Mouse.

Dot Matrix Printer.

Recommended Configuration:

Page No: 24 / 83


The system can run on the above mentioned system, however for perfect ness and clearness it

is recommended to use a computer system having the below listed configuration. The configuration

listed below can give best and optimum result at instance during the working of the system.

1 GHz Pentium 4 processor or other compatible.

Intel 81x Chipset Motherboard.

512 MB SD-RAM.

10-20 GB Hard-Disk.

52x Compact Disc drive or faster.

1.44 MB Floppy Disk Drive.

Color Monitor. [ 800 x 600 Display ]

Keyboard.

Mouse.

132 Column Dot Matrix Printer/Laser Printers.

500 V.A UPS. [Used in case of power failure]

(2) SOFTWARE REQUIREMENTS OF THE SYSTEM :-

Along with the hardware, used in the system it requires software to make a system as well as to run a

system with the computer hardware. Collection of different types of hardware into a specific type can form a

computer but it can not execute different process on its own. For efficient and proper working of any system

software must be installed. This software may be in the form of operating system or application software. To

make the system one also needs to use software.

Software used in designing (code) of the system:

Operating System : Microsoft Windows XP.

Application Software : Microsoft SQL Server [ Back - End Tool]

Microsoft Visual Basic 6.0 [Front - End Tool]

Page No: 25 / 83


Page No: 26 / 83


Tools Information

Microsoft Visual Basic 6.0[Front-End Tool]

To develop any system along with the bach-end tools which Provides a Microsoft SQL Server to the Database and Solve the database quries like oracle,to make a system interactive with the use of front-end tools into the picture.The front-end toolsMake the user Interface with the System and also Provide User-Friendly Environment to the System.

This rich language enables you to develop many different types of Application.You can create Program that intersect with the hardware.

It is Programming language used to create Window base Application.Visual Basic is an old BASIC language.It Makes it Very easy to get User Interface partion of your application up and Running

Microsoft Visual Basic 6.0 is one of the front-end tool provided by M icrosoft Inc.Microsoft Visual Basic 6.0 ProvidesA fast way to Develop application for Microsoft windows.

Advantage of Visual Basic 6.0

During Design time,it is possible to to see how the program will look at Runtime. VB Helps in making your Program look quite Effective and Beautiful You Can add Menus,tool bars,text boxes,ect.to blank Window. It ie less time Consuming and more user Friendly.

Disadvantage of Visual Basic 6.0

The Program that are developed utilize more Memory. Visual Basic requires operating system which supports visual Programming. GUI is Provided by visual basic which takes some more time then other non visual Programming for

Execution of the Program

Microsoft SQL Server 2005 [Back-end tool]:

Page No: 27 / 83


Microsoft SQL Server 2005

Microsoft® SQL Server TM Microsoft® SQL Server™ 2005 extends the performance,

reliability, quality, and ease-of-use of Microsoft SQL Server version 7.0. Microsoft SQL Server 2005

includes several new features that make it an excellent database platform for large-scale online

transactional processing (OLTP), data warehousing, and e-commerce applications.

The OLAP Services feature available in SQL Server version 7.0 is now called SQL Server 2005

Analysis Services. The term OLAP Services has been replaced with the term Analysis Services.

Analysis Services also includes a new data mining component

The Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server 2005

Meta Data Services. References to the component now use the term Meta Data Services. The term repository

is used only in reference to the repository engine within Meta Data Services.

SQL Server is more than just the database engine. While the database engine is at the core of the

product, and obviously the most important component, there are a number of additional applications bundled

with the database engine, such as the tools and utilities used to manage the SQL Server environment, as well

as other components and server applications that extend the capabilities and features of SQL Server.

SQL Server Database Engine

SQL Server's database engine is the primary server application in the SQL Server package. Following

are the main responsibilities of the database engine:

Provide reliable storage for data sent to the engine

Provide a means to rapidly access this data

Provide consistent access to the data

Control access to the data through security

Enforce data-integrity rules to ensure the data is accurate and consistent

Page No: 28 / 83


Microsoft® SQL Server™ 2005 features include:

1) Internet Integration.

The SQL Server 2005 database engine includes integrated XML support. It also has the scalability,

availability, and security features required to operate as the data storage component of the largest Web

sites. The SQL Server 2005 programming model is integrated with the Windows DNA architecture for

developing Web applications, and SQL Server 2005 supports features such as English Query and the

Microsoft Search Service to incorporate user-friendly queries and powerful search capabilities in Web

applications.

2) Scalability and Availability.

The same database engine can be used across platforms ranging from laptop computers running

Microsoft Windows® 98 through large, multiprocessor servers running Microsoft Windows 2005 Data

Center Edition. SQL Server 2005 Enterprise Edition supports features such as federated servers, indexed

views, and large memory support that allow it to scale to the performance levels required by the largest

Web sites.

3) Enterprise-Level Database Features.

he SQL Server 2005 relational database engine supports the features required to support demanding

data processing environments. The database engine protects data integrity while minimizing the

overhead of managing thousands of users concurrently modifying the database.SQL Server 2005

distributed queries allow you to reference data from multiple sources as if it were a part of a SQL Server

2005 database, while at the same time, the distributed transaction support protects the integrity of any

updates of the distributed data. Replication allows you to also maintain multiple copies of data, while

ensuring that the separate copies remain synchronized. You can replicate a set of data to multiple,

mobile, disconnected users, have them work autonomously, and then merge their modifications back to

the publisher.

Page No: 29 / 83


4) Ease of install

SQL Server 2005 includes a set of administrative and development tools that improve upon the

process of installing, deploying, managing, and using SQL Server across several sites. SQL Server 2005

also supports a standards-based programming model integrated with the Windows DNA, making the use

of SQL Server databases and data warehouses a seamless part of building powerful and scalable systems.

These features allow you to rapidly deliver SQL Server applications that customers can implement with

a minimum of installation and administrative overhead.

5) Data warehousing.

SQL Server 2005 includes tools for extracting and analyzing summary data for online analytical

processing. SQL Server also includes tools for visually designing databases and analyzing data using

English-based questions

6) Reliable Storage:-

Reliable storage starts at the hardware level. This isn't the responsibility of the database engine, but

it's a necessary part of a well-built database. Although you can put an entire SQL database on an old IDE

drive (or even burn a read-only copy on a CD), it is preferable to maintain the data on RAID arrays. The

most common RAID arrays allow hardware failures at the disk level without losing data.

Using whatever hardware you have decided to make available, the database engine handles all the

data structures necessary to ensure reliable storage of your data. Rows of data are stored in pages, each

8KB in size. Eight pages make up an extent and the database engine tracks which extents are allocated to

which tables and indexes.

7) Rapidly Accessing Data:-

SQL Server provides rapid access to data by utilizing indexes and storing frequently accessed data in

memory.

SQL Server allows the creation of clustered and no clustered indexes, which speed to data by using

the index pointers to find data rows rather than having to scan all the data in the table each time. For

an in-depth discussion of indexes and how they are used to improve query performance.

Page No: 30 / 83


Memory is allocated by SQL Server database to be used as a data cache to speed accesses to data by

reducing the number of required physical I/Os to the disks. When pages are requested from the database,

the server checks to see if they are already in the cache. If not, it reads them off the disk and inserts them

into the data cache. With sufficient memory, the next time the data needs to be accessed; it should still

be in cache, avoiding the need to access the disk drive(s). A separate process runs continuously and

attempts to keep frequently accessed information in memory by pushing old pages that haven't been

accessed recently out of the cache to make room for newly accessed pages. If the pages contain

modifications, they are written to disk first before being removed from cache; otherwise the old pages

are simply discarded.

8) Providing Consistent Access to Data:-

Getting to your data quickly doesn't mean much if the information you receive is inaccurate. SQL

Server follows a set of rules to ensure that the data you receive back from queries is consistent.

The general idea with consistent access is to allow only one client at a time to change the data, and to

prevent others from reading data from the database while it is undergoing changes.

Transactional consistency has several levels of conformance, each of which provides a trade-off

between accuracy of the data and concurrency.

9) Controlling Access:-

The database server provides security at multiple levels. Security is enforced at the server level, the database

level, and at the database object level. Access to the server is verified by either a username or

password, or through integrated network security.

Integrated security uses the client's network login credentials to establish identity.

10) Enforcing Data Integrity Rules:-

Some databases have to serve the needs of more than a single application. A corporate database that

contains valuable information might have a dozen different departments wanting to access portions of

the database for different needs.

In this kind of environment, it is impractical to expect the developers of each application to agree on

an identical set of standards for maintaining data integrity.

Page No: 31 / 83


For example, one department might allow phone numbers to have extensions, whereas another

department does not need that capability. One department might find it critical to maintain a relationship

between a customer record and a salesman record, whereas another might care only about the customer

information.

The best way to keep everybody sane in this environment—and to ensure that the data stays

consistent and usable by everyone—is to enforce a set of rules at the database level. This is

accomplished through the database objects, including rules, defaults, triggers, stored procedures, and

data-integrity constraints.

Page No: 32 / 83


Page No: 33 / 83


Data Flow Diagram:-

The data flow diagrams are pictorial or graphical representation of the outline of the system study.

The data flow diagram covers all the processes and data storage area which takes place during any

transaction in the system. The data flow diagrams are functionally divided into context level, Zero level, and

First level and Second level data flow diagrams.

Symbols used in DFDs:-

(1) Process : - Here flow of data is transformed. E.g. Purchase of items, update inventory file, etc.

(2) External Entity : A source or destination of data which is external to the system. E.g. Customer, Supplier etc.

(3) A data flow : It is packet of data. It may be in the form of document, letter etc.

(4) Data store : Any store data but with no reference to the physical method of storing.

Page No: 34 / 83


Data Flow Diagram

Context level Diagram:

Page No: 35 / 83


First Level Diagram:-

Page No: 36 / 83


First Level Diagram:-

Page No: 37 / 83


Second Level Diagram:-

Page No: 38 / 83



Page No: 39 / 83



Page No: 40 / 83



Page No: 41 / 83


Page No: 42 / 83


Entity Relationalship Diagram

ER Diagram

SYMBOLS USED FOR DIAGRAMS

ER Diagram:-

ER Model is a Graphical tool to represent the model. We logical structure of database (Entity & the

relationship Exist among entity set).

ER Model is base, which represents a real world which consists a set of object.

Components of ER Model:-

1. Entity.

2. Attributes.

3. Relationship.

4. Key attributes.

There are two types of Entity set.

1. Strong Entity.

Strong Entity can be describing this Symbol.

2. Weak entity.

Weak Entity can be describing this Symbol

Basically there are six types of attributes.

1. Single valued attributes.

Page No: 43 / 83


2. Simple valued attributes.

3. Multi valued attributes.

4. Composite attributes.

5. Null valued attributes.

6. Derived valued attributes.

Many types of Key uses in DBMS, but generally using only two keys.

1. Primary Key:-

2. Foreign Key:-

The mainly useful Symbol of ERD is Relationship Symbols

1. This Symbol is used for Describe Strong relationship

This Symbol is used for Describe weak relationship

Link:-

Generalization:-

Page No: 44 / 83


ER-Diagram:

Page No: 45 / 83


Page No: 46 / 83


DATA STORE [TABLES USED]

Data Dictionary

1.Login_Form:

Column Name Data Type Size Constraint

1 LF_User_Id Varchar 202 LF_Password Varchar 20 Primary Key

2.Product Master


1 Prd_Id Varchar 52 Prd_Name Char 203 Batch_No Numeric 25 Primary Key4 Prd_Type Char 105 Prd_Unit Char 106 Prd_Packing_Size Numeric (5,0)7 Prd_Curr_Stock Numeric (5,0)8 Prd_Retail_Rate Numeric (5,0)9 Prd_Dealer_Rate Numeric (5,0)10 Prd_Date Datetime (5,0)11 Prd_Market_By Char 20

3.Supplier Master


1 Supp_Id Varchar 5 Primary Key2 Supp_Name Char 203 Supp_Address Varchar 254 Supp_City Char 105 Supp_State Char 206 Supp_Pincode Numeric (5,0)7 Supp_Con_Name Char 208 Supp_Con_No1 Numeric (12,0)9 Supp_Con_No2 Numeric (12,0)10 Bank_Name Char 20

Page No: 47 / 83


11 TransPort_Name Char 20

4.Dealer Master


1 Dealer_Id Varchar 5 Primary Key2 Dealer_Name Char 203 Dealer_Address Varchar 254 Dealer_City Char 105 Dealer_State Char 206 Dealer_Pincode Numeric (5,0)7 Dealer_Con_Name Char 208 Dealer_Con_No1 Numeric (12,0)9 Dealer_Con_No2 Numeric (12,0)10 Bank_Name Char 2011 TransPort_Name Char 20

5.Bank Account Master


1 TypeOfUesr char 202 Date Datetime 03 User_Id Numeric 254 Account_No Varchar 10 Primary Key5 Holder_Name Char 106 Account_Type char 107 Bank_Name Char 208 Branch_Name char 209 Min_Balance Numeric (5,0)10 Curr_Balance Datetime (5,0)11 Prd_Market_By Char 20

6. Purchase_Enquiry_Details:


1 PED_Sr_No Varchar 5 Foreign Key2 PED_Particulars Char 253 PED_Quality Char 10

Page No: 48 / 83


4 PED_Unit Char 105 PED_Quantity Numeric (5,0)6 PED_Remarks Char 30

7. Purchase_Enquiry_Master:


1 PEM_Sr_No Varchar 5 Primary Key2 PEM_Indent_Sr_No Varchar 5 Foreign Key3 PEM_Party_Id Varchar 5 Foreign Key4 PEM_Date Datetime5 PEM_Indent_Date Datetime6 PEM_Expected_Delivery_Date Datetime7 PEM_Expected_Quotation_Date Datetime8 PEM_Payment_Condition Char 159 PEM_Prepared_By Char 25

8. Purchase_Quotation_Details:


1 PQD_Sr_No Varchar 5 Foreign Key2 PQD_Particulars Char 253 PQD_Quality Char 104 PQD_Unit Char 105 PQD_Rate Numeric (5,2)6 PQD_Quantity Numeric (5,0)7 PQD_Remarks Char 25

9. Purchase_Quotation_Master:


1 PQM_Sr_No Varchar 5 Primary Key2 PQM_Date Datetime3 PQM_PE_Sr_No Varchar 5 Foreign Key4 PQM_PE_Date Datetime5 PQM_Party_Id Varchar 5 Foreign Key6 PQM_Delivery_Date Datetime7 PQM_Advance_Payment Numeric (8,0)

Page No: 49 / 83


8 PQM_Validity Numeric (2,0)9 PQM_Payment_Condition char 1510 PQM_Prepared_By Char 25

10. Purchase_Order_Details:


1 POD_Sr_No Varchar 5 Foreign Key2 POD_Particulars Char 253 POD_Quality Char 104 POD_Unit Char 105 POD_Rate Numeric (5,2)6 POD_Quantity Numeric (5,0)7 POD_Remarks Char 25

11. Purchase_Order_Master:


1 POM_Sr_No Varchar 5 Primary Key2 POM_Date Datetime3 POM_PQ_Sr_no Varchar 5 Foreign Key4 POM_PQ_Date Datetime5 POM_Party_Id Varchar 5 Foreign Key6 POM_Delivery_Date Datetime7 POM_PV_Sr_No Varchar 5 Foreign Key8 POM_Payment_Condition Char 159 POM_Advance_Paid Numeric (8,2)10 POM_Prepared_By Char 25

12.Purchase_Challan_Details:


1 PCD_Sr_No Varchar 5 Foreign Key2 PCD_Particulars Char 253 PCD_Quality Char 104 PCD_Unit Char 105 PCD_Quantity Numeric (5,0)6 PCD_Remarks Varchar 30

Page No: 50 / 83


13. Purchase_Challan_Master:


1 PCM_Sr_No Varchar 5 Primary Key2 PCM_Date Datetime3 PCM_Party_Id Varchar 5 Foreign Key4 PCM_PO_Sr_No Varchar 5 Foreign Key5 PCM_PO_Date Datetime6 PCM_Vehicle_No Varchar 47 PCM_Driver_Name Char 258 PCM_Expected_Delivery_Date Datetime9 PCM_Prepared_By Char 25

14. Purchase_Invoice_Details:


1 PID_Sr_No Varchar 5 Foreign Key2 PID_Particulars Char 253 PID_Quality Char 104 PID_Unit Char 105 PID_Rate Numeric (5,2)6 PID_Quantity Numeric (5,0)7 PID_Amount Numeric (8,2)8 PID_Remarks Varchar 50

15. Purchase_Invoice_Master:


1 PIM_Sr_No Varchar 5 Primary Key2 PIM_Date Datetime3 PIM_PC_Sr_No Varchar 5 Foreign Key4 PIM_PC_Date Datetime5 PIM_Party_Id Varchar 5 Foreign Key6 PIM_Total_Amt Numeric (8,2)7 PIM_Tax_Per Numeric (2,2)8 PIM_Discount_Per Numeric (2,2)9 PIM_Advance_Paid Numeric (8,2)10 PIM_Prepared_By Char 25

Page No: 51 / 83


16. Purchase_Voucher_Master:


1 PVM_Sr_No Varchar 5 Primary Key2 PVM_Date Datetime3 PVM_Party_Id Varchar 5 Foreign Key4 PVM_Due_Amt Numeric (8,2)5 PVM_Paid_Amt Numeric (8,2)6 PVM_Pending_Amt Numeric (8,2)7 PVM_Payment_Mode Char 68 PVM_Prepared_By Char 25

17. Receipt_Voucher_Master:


1 RVM_Sr_No Varchar 5 Primary Key2 RVM_Date Datetime3 RVM_Party_Id Varchar 5 Foreign Key4 RVM_Receivable_Amt Numeric (8,2)5 RVM_Received_Amt Numeric (8,2)6 RVM_Pending_Amt Numeric (8,2)7 RVM_Payment_Mode Char 68 RVM_Prepared_By Char 25

18. Sales_Order_Details:


1 SOD_Sr_No Varchar 5 Foreign Key2 SOD_Particulars Char 253 SOD_Unit Char 104 SOD_Rate Numeric (8,2)5 SOD_Quantity Numeric (8,0)6 SOD_Remarks Varchar 50

19. Sales_Order_Master:

Page No: 52 / 83



1 SOM_Sr_No Varchar 5 Primary Key2 SOM_Date Datetime3 SOM_Dealer_Type Char 204 SOM_Party_Id Varchar 5 Foreign Key5 SOM_Delivery_Date Datetime6 SOM_Advance_Paid Numeric (8,2)7 SOM_Payment_Condition Char 158 SOM_Prepared_By Char 25

20. Sales_Challan_Details:


1 SCD_Sr_No Varchar 5 Foreign Key2 SCD_Particulars Datetime3 SCD_Unit Char 104 SCD_Quantity Numeric (10,0)5 SCD_Remarks Varchar 50

21. Sales_Challan_Master:


1 SCM_Sr_No Varchar 5 Primary Key2 SCM_Date Datetime3 SCM_SO_Sr_No Varchar 5 Foreign Key4 SCM_SO_Date Datetime5 SCM_Dealer_Type Char 206 SCM_Party_Id Varchar 5 Foreign Key7 SCM_Vehicle_No Numeric (4,0)8 SCM_Driver_Name Char 209 SCM_Expected_Delivery_Date Datetime10 SCM_Prepared_By Char 20

22. Sales_Invoice_Details:

Page No: 53 / 83



1 SID_Sr_No Varchar 5 Foreign Key2 SID_Particulars Char 253 SID_Unit Char 104 SID_Rate Numeric (8,2)5 SID_Quantity Numeric (8,0)6 SID_Amount Numeric (8,2)7 SID_Remarks Varchar 50

23. Sales_Invoice_Master:


1 SIM_Sr_No Varchar 5 Primary Key2 SIM_Date Datetime3 SIM_SC_Sr_No Varchar 54 SIM_SC_Date Datetime5 SIM_Party_Id Varchar 5 Foreign Key6 SIM_Toatal_Amt Varchar 57 SIM_Tax_Per Numeric (2,0)8 SIM_Gross_Amt Numeric (8,2)9 SIM_Discount_Per Numeric (2,0)10 SIM_Advance_Paid Numeric (8,2)11 SIM_Prepared_By Char 25

Page No: 54 / 83


Page No: 55 / 83


SCREEN LAYOUTS

[INTERFACES OF THE SYSTEM ]

This section refers to the various types of interfaces which the user has to face during operating the

computerized system of “ Zota Health Care Management “.

The section refers with the entire interface [Screens] a user will have to face while operating the

current system. It shows the various screens appearing for different transactions. All the screens of different

transactions in the system are shown here.

The different transaction’s screens shown here are in the below given order:

Login Screen.

Change UserName

Change Password

Muiliple Document Interface[MDI]

Master

Product Master

Supplier Master

Dealer Master

Bank Account Master

Purchase

Purchase Enquiry

Received Quotation

Purchase Order

Purchase Delivery Challan

Purchase Invoice

Sales

Sales Order

Page No: 56 / 83


Sales Delivery Challan

Sales Invoice

Voucher

Create Receipt Voucher

Create Voucher Voucher

Exit

Page No: 57 / 83


(1) Logo Form:

This is first page is describes loading of Project.

Page No: 58 / 83


2.Login Form

This is a Login Form which is used to enter your data and hence stores all the values. Security level is

maintained here, as it can only be logged by a specific user name followed by a password code.

In Case if it is not found to be correct, the user would not be able to login (it is also case sensitive)

3.Change Username

This Form is used to change the Username.

Page No: 59 / 83


4.Change Password

This Form is use to Change Password.

5.Main Screen(MDI)

This is a MDI Form. When we run the Project, there are Menu Likes the Master, Transaction, Report

for filling up the forms Reports for viewing the data in Report Format

Page No: 60 / 83


(6) Purchase Enquiry:

In this Form Information about Purchase enquiry is stored.

Page No: 61 / 83


(7) Received Quatation

This Form is use to display and enter the Quatation from the Supplier.

Page No: 62 / 83


(8) Purchase Order

This Form is use to create Purchase Order.

Page No: 63 / 83


(9) Purchase Dellivery Challan

This Form is use to create Purchase Dellivery Challan.

Page No: 64 / 83


(10) Purchase Invoice

This Form is use to create Purchase Invoice to maintain the Account Information.

Page No: 65 / 83


(11) Product Master

This Form is use to store all information about the Product.

Page No: 66 / 83


(12) Supplier Master

This Form is use to store the all information about the Supplier.

Page No: 67 / 83


(13) Dealer Master

This Form is use to store the all information about the Dealer.

Page No: 68 / 83


(14) Bank Account Master

This Form is use to store the all information about theBank Account of all Supplier and Dealer.

Page No: 69 / 83


(15) Payment Voucher

This Form is use to create Payment Voucher for Supplier.

Page No: 70 / 83


(16) Receipt Voucher

This Form is use to create Receipt Voucher for Dealer.

Page No: 71 / 83


(17) Sales Order

This Form is use to create Sales Order.

Page No: 72 / 83


(18) Sales Dellivery Challan

This Form is use to create Sales Dellivery Challen.

Page No: 73 / 83


(19) Sales Invoice

This Form is use to create Sales Invoice to maintain the Account Information.

Page No: 74 / 83


System TestingSystem Testing

Page No: 75 / 83


Software Testing:-

When a system is developed, it is hoped that it performs properly. In practice, however, some errors

always occur. The main purpose of testing a system is to find the errors and correct them. A successful

test is one that finds an error. The main objectives of system testing are:

To ensure that during operation the system will perform as per specifications.

To make sure that the system meets user’s requirements during operation.

To verify that the controls incorporated in the system function as intended.

To see that when correct inputs are fed to the system the outputs are correct.

To make sure that during operations, incorrect input, processing and outputs will be detected.

Quality Assurance

The amount and complexity of software produced today stagger the imagination. Software

development strategies have not kept pace, however and software products fall short of meeting

application objectives. Consequently controls must be developed to ensure a quality product.

Basically, quality assurance defines the objectives of the project and reviews the overall activities so

that errors are corrected early in the development process.

The goals and their relevance to the quality assurance of the system are as follows:

Quality Factors Specifications

The goal of this stage is to define the factors that contribute to the quality of candidate system. Several

factors determine the quality of the system:

1. Correctness

2. Reliability

3. Efficiency

4. Usability

5. Maintainability

6. Testability

7. Portability

8. Accuracy

9. Error Tolerance

10. Expandability

11. Access Control

Page No: 76 / 83


12. Communicativeness

Software Requirements Specification

The quality assurance goal of this stage is to generate the requirements document that provides this

technical specification for the design and development of the software.

Software Design Specifications

In this stage, the software design document defines the overall architecture of this function and features

described in the software that provides the functions

and features describes in the software requirements document.

Software Testing and Implementation

The quality assurance goal of the testing phase is to ensure that completeness and accuracy of the

system and minimize the resulting process. In the implementation phase, the goal is to provide a

logical order for the creation of the modules and in turn, the creation of the system.

Maintenance and support

This phase provides the necessary software adjustment for the system to continue to comply

with the original specifications. The quality assurance goal is to develop a procedure for correcting

errors and enhancing software.

Unit & Integration Testing:-Unit & Integration Testing:-

Black Box Testing

The functionality of the application was tested with the requirement specification. This was done to

ensure that the functionality expected was captured as per the requirement specified.

This testing is also known as functional testing. Black Box Testing is a software testing

technique whereby the internal functionality of the item being tested is not known to the tester. For

example, in a black box test on software design, the tester only knows the inputs, what the expected

Page No: 77 / 83


outcomes are, and not the program arrives at those outputs. The tester does not ever examine the

programming code and does not need any further knowledge of the program other than its

specifications.

White Box Testing

This is basically done to ensure that the logic applied is correct and to check where the code fails.

This is done knowing the logical flow of the functionality and implementation. White box testing is

used because:

Logic errors and incorrect assumptions are most likely to be made when coding “special cases”.

Need to ensure that these execution paths are tested.

May find assumptions about execution paths to be incorrect and so make deign errors. White box

can pick these errors out.

Unit Testing

Since the system is made by dividing it in modules, all the modules play an important role in the system

so each unit had to be individually tested. The development was done in iteration and after each

iteration was completed, test cases were prepared and all the features tested. During development,

developers test their own code. When the test is passed, they are moved over for integration testing.

Testing was done to ensure both the functionality and the security aspects of the system. The test cases

designed must involve the execution of the operation with different user roles and privileges.

Alpha & Beta Testing:-Alpha & Beta Testing:-

It is virtually impossible for a software developer to foresee how a customer will really

use a program.

When custom software is built for one customer, a series of acceptance tests are conducted

to enable the customer to validate all requirements.

Page No: 78 / 83


If the software is developed as a product to be used by many customers, it is impractical to

perform formal acceptance tests with each one. Most software professional use a process

called alpha and beta testing to uncover the errors that only the end-user seems able to find.

ALPHA TESTING :

The alpha test is conducted at the developer’s site by a customer. The software is used with

a developer “looking over the shoulder” of a user and recording errors and usage problems.

BETA TESTING :

The beta test is conducted at one or more sites by the end user of the software. Unlike the

alpha testing we were not present. Therefore the beta test is a “live” of the application of

the software in an environment that cannot be controlled by the developer.

Page No: 79 / 83


Conclusion

Objective

Page No: 80 / 83


To reduce the daily time consumption for data entry. To reduce the burden of manual work. For effective management of different tasks. For co-ordination among different tasks.

Scope

Maintaining Details of all Employee. Maintaining Details of Material, Product details. Maintaining Details following

Purchase Order Details Delivery Challan Details Indent Details Quotation Details Purchase Invoice Details Payment Voucher Details Receipt Voucher Details Sales Invoice Details Cheque Details Bank Account Details Purchase Enquiry Details Kardex Details Material Consumption Details Material Requirement Notification

Maintaining Details of Supplier Maintaining Details of Dealer

Client Details Job Order Contracter Details

It keeps the details Company.

Page No: 81 / 83


Bibliography:-

Web site :

www.W3School.com

Page No: 82 / 83

http://www.W3School.com/


www.Microsoft.com

Books : Black Book of Visual Basic

Visual Basic 6.0SQL SERVER 2005

Page No: 83 / 83

http://www.Microsoft.com/

Healthcare

Main zota abstract