bio medical equipment

8/17/2019 Bio Medical Equipment

1/54

1. INTRODUCTION

1.1 PROJECT DESCRIPTION

This system entitled “BIO-MEDICAL EQUIPMENTS AUTOMATION” has a

database to maintain the records of sales and stock of bio-medical equipments. The importance

of this project is to computerize and maintain the records of purchase sales and stock details with

cash transaction and maintenance.

This project provides a facility to do billing and stock maintenance. As this is a generic

project it can be used by a wide variety of outlets (retailers and wholesalers to automate the

process of manually maintain the records related to the subject of maintaining the stock and cash

flows.

This software helps you to track all the profits! loss! profitable clients and products of

equipment shop moreover it is accounting software. "le#ible and adaptive software suited to

stores of any size.

MODULES

$upplier details

%urchase &tem 'etails

'amaged quipments

$tock details

$ale item

)ustomer *ill

$ervice details

+


2/54

2. SYSTEM CONFIGURATION

2.1 HARDWARE SPECIFICATION

%rocessor , &ntel %entium /0z or faster

1A/ , 2 3*

0ard disk drive , 4 3* of available hard-disk space for installation

)lock $peed , 5 /0z

/onitor , )olor /onitor

%rinter , 6aser %rinter

7eyboard , /ulti /edia

/ouse , 8ptical /ouse

2.2 SOFTWARE SPECIFICATION

Technology , /icrosoft 9isual $tudio 2+

"ront end , 9isual *asic.:et

*ack end , $;6 $erver 24

2.3 SOFTWARE DESCRIPTION

FRONT END- VB.NET

2


3/54

/icrosoft .:T is a set of /icrosoft software technologies for rapidly building and

integrating


4/54

managed code is self-describing. The managed environment of the runtime eliminates many

common software issues.

P$&0#",,"

The runtime also accelerates developer productivity. "or e#ample! programmers can write

applications in their development language of choice! yet take full advantage of the runtime! the

class library! and components written in other languages by other developers.

P$'&$)!*

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services! managed code is never interpreted. A feature

called just-in-time (@&T compiling enables all managed code to run in the native machine

language of the system on which it is e#ecuting. "inally! the runtime can be hosted by high-

performance! server-side applications! such as /icrosoft $;6 $erverB and &nternet

&nformation $ervices (&&$.

M!*!+0 C&0

The code that targets .:T! and which contains certain e#tra &nformation - CmetadataD -

to describe itself. *oth managed and unmanaged code can run in the runtime! only managed code

contains the information that allows the )61 to guarantee! for instance! safe e#ecution and

interoperability.

BAC END- SQL SERVER

/icrosoft $;6 $erver is a relational database management system developed

by /icrosoft. As a database! it is a software product whose primary function is to store and

retrieve data as requested by other software applications! be it those on the same computer or

those running on another computer across a network (including the &nternet. There are at least a

dozen different editions of /icrosoft $;6 $erver aimed at different audiences and for workloads

E

http://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Relational_database_management_system


5/54

ranging from small single-machine applications to large &nternet-facing applications with many

concurrent users.

&t included native support for managing


6/54

3. SYSTEM STUDY

3.1 EISTING SYSTEM

At present equipment store they maintain their day to day transactions manually. These

shops have thousands of products and they need to track of all these products to check the stock!

price etc. &f they donGt return the products to the distributor in time then they lose that much

amount. $o it is very essential to track e#piry items prior one month or before! then only they can

able to return these products back. To find the product is also another risky job.

3.1.1 DRAWBACS OF EISTING SYSTEM

/anual maintenance

1isk of data loss

/aintenance is not effectively done

&nformation canGt be retrieved easily

3.2 PROPOSED SYSTEM

The problem is formulated based on the e#isting system and the user requirements. The

present system has lot of difficulties. *ut the proposed system has been designed to overcome

these difficulties.

3.2.1 ADVANTAGES OF THE PROPOSED SYSTEM

Hpdating in fast and easy

&t is user friendly

'ata can be maintained accurately

ffort and workspace will be reduced

'amage details can be verified easily

4. SYSTEM DESIGN

5


7/54

4.1 INPUT DESIGN

&nput design is a part of overall system design that needs careful attention and if

includes specifying the means by which actions are taken. A system user interacting through

a workstation must be able to tell the system whether to accept input produce a report or end

processing.

The collection of input data is considered to be the most e#pensive part of the system

design. &nput design is the process of converting the user-originated inputs to a computer-

based format. The design for handling input specifies how data are accepted for computer

processing.

$ince the inputs have to be planned in such a manner so as to get the relevant

information e#treme care is taken to obtain the information. &f the data going into the system

is incorrect then the processing and outputs will magnify these errors. The major activities

carried out are

• )ollection of needed data from the source

• )onversion of data into computer accepted from

• 9erification of converted data

The input forms involved in this project are!

$upplier "orm

%urchase &tem "orm

'amaged quipments "orm

$tock "orm

$ales "orm

$ervice "orm

4.2 OUTPUT DESIGN

I


8/54

The output design has been done so that the results of processing should be

communicated to the user. ffective output design will improve the clarity and performance

of outputs. 8utput design phase of the system is concerned with the )onvergence of

information to the end user friendly manner.

The output 'esign should be efficient! intelligible so that system relationship with the

end user is improved and thereby enhancing the process of decision making. Therefore

output design is the one which intimates design guidelines or standards which have been

established through a master plan process. The master plan or output design framework is

the vision.

&t should be accompanied by a design rationale that e#plains the objectives! with the

design code providing instructions to the appropriate degree or precision of the more

detailed output design work.

The reports generated in this project are!

$upplier 1eport

%urchase 1eport

'amaged quipments 1eport

$tock 1eport

*illing

$ervice 1eport

4


9/54

4.3 DATABASE DESIGN

The entire project has been developed keeping in view of the data computing technology!

in mind. The specification has been normalized up to ?:" to eliminate all the anomalies that may

arise due to the database transaction that are e#ecuted by the general users and the organizational

administration. The user interfaces are browser specific to give distributed accessibility for the

overall system.

The internal database has been selected as /$-$;6 server 24.The basic constructs of

table spaces! clusters and inde#es have been e#ploited to provide higher consistency and

reliability for the data storage. The /$-$;6 server 24 was a choice as it provides the

constructs of high-level reliability and security. At all proper levels high care was taken to check

that the system manages the data consistency with proper business rules or validations.

The database connectivity was planned using the latest C$;6 )onnectionD technology

provided by /icrosoft )orporation. The authentication and authorization was crosschecked at all

the relevant stages.


10/54

4.4 MODULE DESCRIPTION

15 S#667,$ D"!,7%

This module is to maintain the supplier details who supply the different types of

equipments. The personal details of supplier are maintained.

25 P#$(!% I") D"!,7%

This module consist details of items purchased by shopkeeper. The items

purchased from supplier are indicated in this module.

35 D!)!+0 E8#,6)*"%

This module is to indicate the damaged equipment details while purchasing. The

amount refunded is also maintained in this module.

45 S"&9 0"!,7

&t indicates the total number of items in the stock! number of items sold and

remaining items in the stock.

:5 S!7 I")

&t indicates the number of items sold! date and time. The updated information is

stored in stock.

;5 C#%"&)$ B,77

The bill generated after purchasing an item by the customer. The total is

calculated based upon the number of items purchased by the customer.

7) Service Details

This module is to indicate the service details of the equipments. The customer

details and service charge are maintained in this module.

:. SYSTEM TESTING

Testing is the process of confirming that a program or system does what it is proposed

off! Testing is the only way to assure the quality of sJw and it is an umbrella activity rather that a

+


11/54

separate phase. This is an activity to be performed in parallel with the sJw efforts and one that

consists of its own phase of analysis! design! implementation! e#ecution and maintenance.

'uring analysis and design! an sJw verification plan and acceptance test plan is prepared.

The verification plan describes the methods to be used in verifying that the requirements are

satisfied by the design documents and that the source is consistent with the requirements

specification and design documents. The acceptance test plan includes test cases! outcomes and

capabilities demonstrated by each test case. "ollowing completion of the verification plan and

Acceptance plan! an sJw verification review is held to evaluate the adequacy of the plans.

'uring product evolution! in-process audits are conducted to verify consistency and

completeness of the work products. &tems to be audited for consistency include interface

specification for hardware and software, internal design verses functional requirements verses

test descriptions.

%rior to product delivery! a functional audit and a physical audit performed. The

functional audit reconfirms that all the requirements have been met. The physical audit verifies

that the source code and all associated documents are complete! consistent with one another and

ready to deliver. An sJw verification summary is prepared to describe the results of all reviews.

U*," T%",*+

This testing method considers a module as single unit and checks the unit at interfaces

and communities with other modules rather than getting into details at statement level. 0ere the

module will be treated as *6A)7*8

8utputs for a given set of input combination are pre calculated and are generated by the module.

I*"+$!",&* T%",*+

0ere all the pre-tested individual modules will be assembled to create a larger system

and tests are carried out at system level to make sure that all modules are working with each

++


12/54

other. This testing methodology helps in making sure that all modules which are running

perfectly when checked individually and are also running cohesion with other modules. "or this

testing we create test-cases to check all modules once and then a generated test combination of

test paths with the system to make sure that no path is making its way into chaos.

V!7,0!",&* T%",*+

Testing is major quality control measure employed during software development. &ts

basic function is to detect errors. $ub functions when combined may not produce than it is

desired. 3lobal data structures can represent the problems. To uncover errors that are associated

with interfacing the objective is to make test modules and built a program structure that has

detected by design. &n a non-incremental integration all the modules are combined in advance

and the program is tested as a whole. 0ere error will appear in an end-less loop function.

;. SYSTEM IMPLEMENTATION

The implementation phase focuses on change that is associated with error correction!

adaptations required as the softwareKs environment evolves! and changes due to enhancements

brought about by changing customer requirements.

8ver time! the original environment (#.! )%H! operating system! business rules! e#ternal

+2


13/54

product characteristics for which the software was developed is likely to change. Adaptive

maintenance results in modification to the software to accommodate change to its e#ternal

environment.

)omputer software deteriorates due to change! and because of this! preventive

maintenance! often called software re engineering! must be conducted to enable the software to

serve the needs of its end users. &n essence! preventive maintenance makes changes to computer

programs so that they can be more easily corrected! adapted! and enhanced. $oftware

configuration management ($)/ is an umbrella activity that is applied throughout the software

process.

An implementation is a realization of a technical specification or algorithm as a program!

software component! or other computer system through computer programming and deployment.

/any implementations may e#ist for a given specification or standard.

A special case occurs in object-oriented programming! when a concrete class implements

an interface> in this case the class is an implementation of the interface and it includes methods

which are implementations of those methods specified by the interface.


14/54

$ystem is fully 3H& based. &t is easy operate and user friendly. %latform includes the

inbuilt backup and recovery facility. =orking on the project was a good e#perience. =orking

together in teams helped us to communicate better.

=e understand the importance of planning and designing as a part of bio medical

processing system. The concept of peer-reviews helped to rectify the problems as and when they

occurred and also helped us to get some valuable suggestions that were incorporated by us.

'eveloping the project has helped us to gain some e#perienced on real time development

procedures.

FUTURE ENHANCEMENT

&t is desirable to aim for a system with a minimum cost subject to the condition that it

must satisfy the entire requirement. 1eusable software reduces design! coding and testing cost by

amortizing effort over several designs.

1educing the amount of code also simplifies understanding! which increases the

likelihood that the code is correct. =e follow up both types of reusability, $haring of newly

written code within a project and reuse of previously written code on new projects.

BIBLIOGRAPHY

BOO REFERENCES

+E


15/54

+. 3ardiner! ileen and 1onald 3. /usto. LThe lectronic *ook.L &n $uarez! /ichael "eli#!

and 0. 1. =oudhuysen. The 8#ford )ompanion to the *ook. 8#ford, 8#ford Hniversity

%ress! 2+! p. +5E.

2. Le-book L. 8#ford 'ictionaries. April 2+. 8#ford 'ictionaries. April 2+. 8#ford

Hniversity %ress. (accessed $eptember 2! 2+.

3. 'amon Allison! Andy 8lsen! and @ames $peer! 9isual *asic .:T )lass 'esign

0andbook, )oding ffective )lassesG $ep F! 2?.

4. 1oger $. %ressman! M$oftware ngineering, A %ractionerGs ApproachG! /c3raw-0ill

&nternational dition! "ifth edition! 2+.

WEBSITE REFERENCES

+. www.w?schools.com

2. www.dotnet-tricks.com

?. http,JJwww.sqlserver.comJE. www.tutorialspoint.com

APPENDICES

1. DATA FLOW DIAGRAM

+F

http://www.worldcat.org/oclc/370356568http://www.worldcat.org/oclc/370356568http://oxforddictionaries.com/view/entry/m_en_us1242960http://www.worldcat.org/oclc/370356568http://oxforddictionaries.com/view/entry/m_en_us1242960


16/54

L7 =

V,> S!7% 0"!,7%

R"$,

L7 1

V,> E8#,6)*"% P#$(!% 0"!,7%

+5

%urchase)ustomer *illing

*io /edicalquipments

*io /edicalquipments

%urchase)ustomer


17/54

N#)/$ &' I")%

T&"!7 A)*"

G*$!"

*illing 1eport

L7 2

I0? *!) %$, 0"!,7%

+I

$ales

*illing

3ives

quipment)ustomer

$ervice


18/54

A)*"

G*$!"

$ervice 1eport

2. TABLE STRUCTURE

1) Tale !a"e# Supplier details

$ri"ar% &e%# SID

+4

%ayment


19/54

2) Tale !a"e# Purchase Item details

$ri"ar% &e%# PID

+

F,70 N!) D!"! T6 S,@ D%$,6",&*

$&' nvarchar 2 $upplier &'

$name nvarchar F :ame of $upplier

Addr nvarchar + Address of the supplier

%hno bigint 2 %hone number of the supplier

F,70 N!) D!"! T6 S,@ D%$,6",&*

%&' nvarchar 2 &tem &d

/name nvarchar F :ame of &tem

;ty int 2 ;uantity of the &tem %urchased

%rice float 2 %rice of the &tem

%date date NNN %urchase 'ate


20/54

') Tale !a"e# Damaged Equipment details

F(rei* &e%# PID

2

F,70 N!) D!"! T6 S,@ D%$,6",&*



;ty int 2 ;uantity of the &tem 'amaged



21/54

+) Ta

le !a"e# Customer Details

$ri"ar% &e%# CID

2+

F,70 N!) D!"! T6 S,@ D%$,6",&*

)&' nvarchar 2 )ustomer &dentification :umber

)name nvarchar F :ame of the )ustomer

Addr nvarchar + Address of the customer

%hno long 2 %hone number

1date date NNN 1egistered date


22/54

,) Tale !a"e# Sales details

$ri"ar% &e%# BIDF(rei* &e%# PID, CID

-) Tale !a"e# Service details

F(rei* &e%# PID, CID

22

F,70 N!) D!"! T6 S,@ D%$,6",&*

*&' nvarchar 2 *ill :umber




;ty number 2 ;uantity of the &tem


Tot float 2 3rand Total

$date date NNN $ales 'ate

F,70 N!) D!"! T6 S,@ D%$,6",&*


)name nvarchar 2 )ustomer :ame



Amt float 2 $ervice Amount

$edate date NNN $ervice 'ate


23/54

7) Tale !a"e# Stock DetailsF(rei* &e%# PID

2?

Fiel

!a"e

Data T%/e Si0e Descri/ti(*

PID nvarchar 20 Item Identifcation um!er

Pname nvarchar "0 ame o# Item

$qt% &oat 20 $pdated 'uantit% o# the Item

Price &oat 20 Price o# the Item

$date date (((( $pdated date


24/54

SAMPLE SCREENS

2E


25/54

2F


26/54

25


27/54

2I


28/54

24


29/54

2


30/54

?


31/54

?+


32/54

?2


33/54

??


34/54

?E


35/54

?F


36/54

?5


37/54

?I


38/54

?4


39/54

SAM$LE CODI!G

Imports S%stem)Data

Imports S%stem)Data)SqlClient

Pu!lic Class #rmSeller

Dim con *s e+ SqlConnection

Dim cmd *s e+ SqlCommand

Dim a *s Integer 0

Private Su! -oadData!ase./

con)Close./

con)ConnectionString Data Source)1S'-EP3ESS4Initial

Catalog5eeva4Integrated Securit%6rue

con)7pen./

End Su!

Private Su! Clear5rid8ie+./

9or Each ro+ *s Data5rid8ie+3o+ In Data5rid8ie+:)3o+s

Data5rid8ie+:)3o+s)3emove.ro+/

e;t

End Su!

?


40/54

Private Su! !tInsert(Click.B%8al sender *s S%stem)7!6r%

cmd)Connection con

cmd)Parameters)*dd?ith8alue.@Sname, t;tsellername)6e;t/

cmd)Parameters)*dd?ith8alue.@Conno, t;tcontact)6e;t/

cmd)Parameters)*dd?ith8alue.@Email, t;tmail)6e;t/

cmd)Parameters)*dd?ith8alue.@*ddress, t;taddress)6e;t/

cmd)E;ecuteon'uer%./

>AsgBo;.Details o# Seller are Success#ull% Inserted, v!In#ormation,

Success#ull% Inserted/

con)Close./

>Catch e; *s E;ception

> >AsgBo;.Details are not Inserted Please 6r% -ater, v!In#ormation,

Error In Inserting Seller Details/

>End 6r%

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

E


41/54

Clear5rid8ie+./

-oad:./

clear./

End Su!

Private Su! !tClear(Click.B%8al sender *s S%stem)7!


42/54

t;taddress)6e;t ro+)Cells./)8alue)6oString./

End I#

End I#

Catch e; *s E;ception

End 6r%

End Su!

Private Su! !t$pdate(Click.B%8al sender *s S%stem)7!Dim ans+er *s -ong

6r%

cmd)Parameters)Clear./

>ans+er AsgBo;.*re %ou sure to $pdating Data, v!Feso,

$pdating 3ecord/

>I# .ans+er v!Fes/ 6hen

cmd)Connection con

cmd)Parameters)*dd?ith8alue.@Sname, t;tsellername)6e;t/

cmd)Parameters)*dd?ith8alue.@Conno, t;tcontact)6e;t/

cmd)Parameters)*dd?ith8alue.@Email, t;tmail)6e;t/

cmd)Parameters)*dd?ith8alue.@*ddress, t;taddress)6e;t/

E2


43/54

cmd)Parameters)*dd.@Sno, SqlD!6%pe)8arChar/)8alue

t;tsellerid)6e;t


AsgBo;.Seller Details $pdated, v!In#ormation, Succes#ull%

$pdated/

con)Close./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

-oad:./

Ae)3e#resh./

>Else

>t;tSerialo)9ocus./

>End I#


AsgBo;.$na!le to $pdate 3ecord Please 6r% -ater, v!In#ormation,

Error in $pdating 3ecord/

End 6r%

clear./

End Su!

E?


44/54

Private Su! !tDelete(Click.B%8al sender *s S%stem)7! Dim ans+er *s -ong

6r%


>ans+er AsgBo;.*re %ou sure to Deleting Data, v!Feso, Delete

3ecord/

>I# .ans+er v!Fes/ 6hen

cmd)Connection con

>cmd)Parameters)*dd?ith8alue.@ProductCode, ttProductCode)6e;t/


AsgBo;.Details Deleted, v!In#ormation, Success#ull% Deleted/

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

-oad:./

Ae)3e#resh./

EE


45/54

>Else

> t;tSerialo)9ocus./

>End I#


AsgBo;.$na!le to Delete 3ecord Please 6r% -ater, v!In#ormation,

Error in Deleting/

End 6r%

clear./

End Su!

Private Su! clear./

t;tsellerid)Clear./

t;tsellername)Clear./

t;tcontact)Clear./

t;tmail)Clear./

t;taddress)Clear./

End Su!

End Class

Imports S%stem)Data

Imports S%stem)Data)SqlClient

EF


46/54

Pu!lic Class #rmProducts

Dim con *s e+ SqlConnection

Dim cmd *s e+ SqlCommand

Dim da *s e+ SqlData*dapter.select G#rom t!lProductDetails:, con/

Dim ds *s e+ DataSet

Dim d!ind *s e+ BindingSource

Dim a *s Integer 0

Private Su! #rmProducts(-oad.B%8al sender *s S%stem)7!


47/54

e;t

End Su!

Private Su! !tInsert(Click.B%8al sender *s S%stem)7! 6r%

I# t;tProductame)6e;t 7r t;t'uantit%)6e;t 7r t;tPrice)6e;t

6hen

AsgBo;.Please Enter all Details, v!In#ormation, 9ill *ll the Details/

Else

t;tProductame)9ocus./

cmd)Connection con

cmd)Parameters)*dd?ith8alue.@Productname,

t;tProductame)6e;t/

cmd)Parameters)*dd?ith8alue.@'t%, t;t'uantit%)6e;t/

cmd)Parameters)*dd?ith8alue.@$nit, cm!$nitSelect)6e;t/

cmd)Parameters)*dd?ith8alue.@Price, t;tPrice)6e;t/

cmd)Parameters)*dd?ith8alue.@Aa#urdate,

D6Aanu#ctureDate)8alue/


AsgBo;.Product Details are Success#ull% Inserted, v!In#ormation,

Success#ull% Inserted/

EI


48/54

con)Close./

con)7pen./


cmd)Connection con


t;tProductame)6e;t/

cmd)Parameters)*dd?ith8alue.@'t%availa!le, t;t'uantit%)6e;t/






con)Close./

End I#

> Catch e; *s E;ception

>AsgBo;.ProductDetails are not Inserted Please 6r% -ater,

v!In#ormation, Error In Inserting Product Details/

> End 6r%

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

E4


49/54

Clear5rid8ie+./

-oad:./

clear./

End Su!

Private Su! !tClear(Click.B%8al sender *s S%stem)7!


50/54

t;tproductid)6e;t ro+)Cells.0/)8alue)6oString./

t;tProductame)6e;t ro+)Cells.:/)8alue)6oString./

t;t'uantit%)6e;t ro+)Cells.2/)8alue)6oString./

cm!$nitSelect)6e;t ro+)Cells./)8alue)6oString./

t;tPrice)6e;t ro+)Cells./)8alue)6oString./

D6Aanu#ctureDate)8alue ro+)Cells."/)8alue)6oString./

End I#

End I#


End 6r%

End Su!

Private Su! !t$pdate(Click.B%8al sender *s S%stem)7!


51/54


t;tProductame)6e;t/

cmd)Parameters)*dd?ith8alue.@'t%, t;t'uantit%)6e;t/





cmd)Parameters)*dd.@Productid, SqlD!6%pe)8arChar/)8alue

t;tproductid)6e;t


AsgBo;.Product Detail $pdated, v!In#ormation, Product Detail

$pdated/

con)Close./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

-oad:./

Ae)3e#resh./

Else


F+


52/54

End I#


AsgBo;.$na!le to $pdate 3ecord Please 6r% -ater, v!In#ormation,

Error in $pdating 3ecord/

End 6r%

clear./

End Su!

Private Su! !tDelete(Click.B%8al sender *s S%stem)7!


53/54

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

Clear5rid8ie+./

-oad:./

Ae)3e#resh./

Else


End I#


AsgBo;.$na!le to Delete 3ecord Please 6r% -ater, v!In#ormation,

Error in Deleting/

End 6r%

clear./

End Su!

Private Su! Button:(Click.B%8al sender *s S%stem)7!


54/54

Private Su! Button2(Click.B%8al sender *s S%stem)7!

bio medical equipment

Documents