production planing control

8/3/2019 Production Planing Control

http://slidepdf.com/reader/full/production-planing-control 1/100

1

Sutex Bank College of Computer Application & Science &M. G. Shah Institute Of Graduation of Medical Technology

(ACCRICATED ‘B’ (CGPA 2.55) By NAAC (DEC.-2009))

PROJECT REPORT ON

PRODUCTION PLANNING CONTROL

AS A PARTIAL REQUIREMENT FOR THE DEGREE

OF

BACHELOR OF COMPUTER APPLICATION

(B.C.A.)

SUBMITTED BY:Mr. PRATIK SATIKUNVARMr. JITHIN PONATHIL

Internal Guider:MR. VIRAL POLISHWALA

ORGANIZATION:(ABM WOOD DECOR)

co-ordinatorABM wood decor.



2

Sutex Bank College of Computer Application & Science &

M. G. Shah Institute Of Graduation of Medical Technology(ACCRICATED ‘B’ (CGPA 2.55) By NAAC (DEC.-2009))

BACHELOR OF COMPUTER APPLICATION

Certificate

This is to certify that Mr. PRATIK SATIKUNVAR AND PONATHIL JITHIN (B.C.A. VIth Semester Exam No. 446 & 436 ) has successfully completed his project work entitled “ PRODUCTION PLANNING CONTORL” At ABM WOOD DECOR as a partialrequirement for degree of “Bachelor of Computer Application” during the academic year2010-2011.

MR. VIRAL POLISHWALA Mrs. NavitaGandhiLecturer, I/c Principal

Date: Place: Amroli



3

To Whom It May Concern

This is certifying that Mr. PRATIK SATIKUNVAR AND PONATHIL JITHIN ExamNo: 446, 436, (B.C.A. VI Semester) Sutex Bank College of Computer Application & Science hasSuccessfully Completed There Project Work entitled “PRODUCTION PLANNINGCONTORL ”

The period of there Project Training was from 1-1-2011 to 10-4-2011. They are

completed the project on “PRODUCTION PLANNING CONTORL ” using Microsoft VisualStudio 2008 with Microsoft SQL Server 2005. The System requirement Study, Design &Development Successfully is done in satisfactory way. During the project, they are found to beVery enthusiastic about learning new things. We are highly satisfied with efforts they have put induring the Project Duration.

Wish them great success in Future.

Place: Surat

Date:

Co-ordinator,ABM wood decor

(ABM wood decor)



4

Preface

With Great Pleasure we undertake the writing of document or the PMS(“PRODUCTION PLANNING CONTORL ”) because it is a fact to be proud of that we are

the students undertaking education in the field of Computer Application which is being offeredat Graduation Level in VNSGU ( Veer Narmad South Gujarat University), Surat.

As a student of Computer Field, we must be encouraged by the Growth & rapiddevelopments in the software industry, keeping in mind the ever-Increasing demand forsoftware & software engineers the University has arranged for the third year level.

Thus it is out moral & obligatory duty to take this as a part of out Studies with greatenthusiasm & Seriousness and given it the due Importance. For this we have gone through adevelopment program of 6 th month.



5

ACKNOWLEDGEMENT

When we reach the completion of the project giving Credit becomes a must, Aswithout the support of other so many People’s help and guidance this project could not becompleted successfully.

My humble thanks to all staff members of our college “Sutex Bank College of Computer Application & Science, Amroli” for the co -operation and keep Interest extended bythem, throughout my degree course. It is the Base that they have built, which sustains suchgoods jobs.

We are must grateful to following individuals for their time, Talents Interest inour work. First of all, We would like to thank Mr. Sanjay Dabhoya(Chairmen ABM WOOD DECOR) for granting us an opportunity to work on this project.

At the outset, we express our sincere thank and gratitude to Mr. Viralpolishwala. Lecturer (BCA Dept., Amroli, Surat) for her Valuable Personal Guidance towards

developing of my “PRODUCTION PLANNING CONTORL ” Software.

Last but not least, our heartfelt appreciation goes to al those not named Here,but who have rendered their cooperation , Little or more , directly or indirectly In the course of development of this System & Preparation of this document.

Thanking All.

MR.PRATIK SATIKUNVARMR.JITHIN PONATHIL



6

INDEX

1. Project Profile………………………………………………….............................................7

2. Environment Description2.1. Hardware and Software Requirements .................................................... 12 2.2. Technology Used ..................................................................................... 13

3. Existing System3.1. System Components ............................................................................... 15 3.2. Drawbacks of Existing System ................................................................. 16

4. System Planning

4.1. Feasibility Study ...................................................................................... 19 4.2. Requirement Analysis and Data Gathering ............................................... 20

5. Proposed System5.1. Scope ...................................................................................................... 24 5.2. Objectives ............................................................................................... 25 5.3. Constraints ............................................................................................. 26 5.4. Expected Advantages .............................................................................. 27

6. Detailed Planning6.1. UML(Uniform Model Language)

6.1.1. Use Case Diagrams ....................................................................... 30 6.2. Data Flow Diagram .................................................................................. 33 6.3. Process Specification ..........................................................................42 6.4. Entity-Relationship Diagram .................................................................. 48 6.5. Data Dictionary ....................................................................................... 50

7. System Design7.1. Database Design ................................................................................55 7.2. Input Design ............................................................................................ 62 7.3. Output Design ...................................................................................86

8. Software Testing......................................................................................959. Limitations and System Enhancement.........................................................9910. References..............................................................................................100



7

1.1 Project Profile

Project Title PRODUCTION PLANNING CONTROL

Project Description This system is used to maintain operation from order_entry todispatch of goods. The system also maintain material store forthe row material, and also system maintain information of employee, supplier, party etc. Mailing facilty is also available.Mail will be send automatically when order gets complete ormaterial quantity is insufficient. The system also includes the

facility to direct convert and store data from XML file to sqlserver.

Developed By Pratik SatikunvarJithin ponathil

Front End VB.NET 2008

Operating System Windows 7

Back End SQL Server-2005

Project Submitted Sutex Bank College of Computer Application & Science &M. G. Shah Institute Of Graduation of Medical Technology

Project Duration 1/01/2011 TO 10/04/2011



8

1.2 Company Profile



9



10



11

2.EnvironmentDescription



12

2.1 Hardware And Software Requirements

Hardware Requirement:-

Processor : - Intel Core2Duo E7400 2.80 GHZ or anyRAM : - 512 MB or higherHDD : - 40 GB or higherCam : - Optical webcamPrinter : - Laser printer

Software Requirement:-

Operating System : - Windows xp/ vistaDatabase :- SQL Sever 2005Application :- Microsoft Visual Studio 2008

Development Environment & Client Configuration :-

Processor : - Intel Core2Duo E7400 2.80 GHZRAM : - 2 GB.

HDD : - 160 GB.Operating System : -Windows Vista Home basicDatabase :- SQL Server 2005



13

2.2 Technology Used

In each and every System there is need of two different ends to handle the system. EachSystem requires the main Platform perform all tasks that will appear in system and these taskswill be performed by only Front End. The main need of taking front end is that all programming

that will be perform according to the environment and facility by the opted front end andtaking back end is that all database are kept in that base.

In our software (Production planning control) we using mainly two major technologiesto support our System as two different ends called as front end and back end. In our twodifferent ends called front end and back end. In our Software Microsoft Visual Studio 2008 willplay important role of Front end, Microsoft SQL Server 2005 will play role of back end in oursystem.

1 The main Programming Language that are widely used in Front end:

1. Microsoft Visual Studio 2008

2 Our Different Programming Environment:

2. Front End:-

Microsoft Visual Studio 2008Crystal reportGraphs(chart)Ms Excel and XML file.

3. Back End:-

Microsoft SQL Server 2005



14

3.Existing system



15

3.1 System Component

The existing or current system is completely manual in this way, there are different kindsof registers to record different kinds of transaction . There were wider range of paper works forthe production department. Some of registers kept in our system are:-

1. Order entry register2. Emloyee register3. Production register4. Material register5. Billing register

ORDER ENTRY REGISTER:-

Order entry register usually used to store the information about order whichcomes to the company by a party. This register consist of all information about order likeorder_no, type, quantity, party_info, date of dispatch etc.

EMPLOYEE REGISTER:-

Employee register usually used to store the information about employee detail likename, address, phone no, email, photo etc. And in other phase the incoming and outgoing timeof each employee is being store. So the accuracy of employee can be measured.

PRODUCTION REGISTER:-

Production register usally used to store information related to order in productiondepartment. As there are many process in production department, it is necessary to maintaineach unique register for the each and every process.



16

MATERIAL REGISTER:-

Material register usually used to store information related to raw material. Itkeeps track of total inventory for each and every product as well as daily incoming andoutgoing traction.

BILLING REGISTER:-

Billing register usually used to store information related to billing & pricing. Itkeeps track of payment for a particular order, for a particular party, for a particular timeduration etc.

3.2 Drawback Of Existing system

Each and every system has certain drawback which lead to a new system.In this traditional manual system for keeping track of order, production & billing in differentregister is probalematic. It is complicated for decision making. Following are some of thedrawback of manual system those are observed and need to overcome in a new system:-

1)HIGH AMOUNT OF PAPER WORK:-

Since all work is done manually in this way there is a wide range of use of paper. Eachand every transaction is recorded on the paper. So there would be high amount of stationery isrequired to maintain all the register and after a few year it is difficult to find any transactionsfrom a number of register.

2)LOW LEVEL OF SECURITY:-

In the current system all the work that is done is carried out on the register and sothere are not any security criteria to guard our data and any person can view and change data.Currently it is open to everyone.

3)TIME CONSUMING:-



17

In the current system all the process are carried out manully, so naturally it rquire more timeand will take more time in completing transaction.

4)EXPENSIVE IN MAINTAINING:-

As currently for even one order to be completed, it require a big bunch of paperwork,so it is expensive to maintain and there may be a major chance of mistake to be.

5)DELAY IN REPORT GENERATION:-Information processing is very lengthy and time consuming. So, actual

information/data which required to generate report are not timely provided. So , reportgeneration is delayed until required data is produced.



18

4.System planning



19

4.1 Feasibility Study

1 Technical Feasibility :- This project does require that much of higher & advanced

technology. It requires database interaction and it also requires to be accessed via web or

internet. This can be easily done. Also these should be a facility of sending reports andalso we are doing online video capturing. It must be developed within the six months of period excluding the time period for the testing and validation, verification. Thus it seemsthat the project is technically feasible to do.

1 Economical Feasibility:- In This project, we will require to purchase much of the web

cameras to take the photograph of a person or shut Video of that person, it is alreadypurchased by a company and the development of the project won’t cost too much as it

involves very few persons and also does not involve any other outsiders, but as it will beweb-enabled we do not have any extra cost of setting up a network. This is also feasibleeconomically.

1 Operational Feasibility:-This project is a live project and it will definitely be used at the

gate of the all furniture manufacturing company. Whether a person is computer expert ornot they will be able to run this Software and use it. It will be easily operable.



20

4.2 Requirement Analysis And Data Gathering

Requirement Gathering

Before developing an elegant software, best way to identify basic needs andfunctionality is to take interview of production manager and different departmentalmanagers and even management who are working in that specific area addressed byproposed application.

For gathering basic needs and functionalities, we had meeting with managerspersonally to understand required functionalities, also noted down some useful features tobe included.

By analyzing the information we understand following process requirement forsecurity system.

Understanding the process of security system

What type of forms should be included? How to manage all forms? How many types of data transaction should be included? How to manage login and logout process?

How to know how many orders received and how many completed on thatparticular day?

What type of different reports they want? How to manage all forms linked with each other? How to manage intercommunication with internet? How to capture images in online video? How to manage Net Meeting and Video conferencing?

Understand different type of user who uses this software

How many types of user going to use this system? What is the knowledge level of the user? Provide authorization and separate their functionality.



21

Extra Constraints User friendly Speed of system The GUI architecture Online facility using Internet

Requirement Analysis

We analyzed our gathered information and we have decided our system shouldhave following functionalities.

Authentication of users Admin Authorization of user account

For Login,For Time in,For Time out

Different types of module Authentication Send mail Net Meeting Online image capturing.

Patient M anagement System

Employee Maintaining employee information like, Add employee View employee Edit(delete, change) employee.

Party Maintaining Party information like,



22

Add party View party Edit(delete, change) party.

Transactions Order entry Bill info. Order dispatch

Supplier info. Transporter info.

Intercommunication Video Conferencing Net Meeting Online Image Capture

Report Orders report Daily report Production report Inventory report Employee report Payment report Order dispatch report.



23

5.Proposed system



24

5.1 Scope

System can be able to manage various registers like Order entry, employee, production,material, billing Register.

System can able to accept user request.

System should able to imports data from xml file to database.

System can able to display request to the management.

System can be able to give detail information about all Orders and its equivalent parties.

System can able to give information about order is in which process during theproduction.

System can be able to give information about all employees.

System can give the information about parties, suppliers and transporters.

System can give all detail information about inventory and order dispatch reports.

System can be able to generate various kind of report that become helpful for variouslevel of user.

System can send email or directly send report via email.

System can able for Video Conferencing and Net Meeting through connecting withinternet.



25

5.2 Objectives

The new system will convert manual work to the computerized work.

By converting manual work to the computerized work in that case it will remove allpaper work and all stationary that will require till now maintain inventory, because fromnow inventory will be maintained by computer.

By maintaining all the work on computer will increase our accuracy as well as speed of our work.

The report can be generated at any time if managers wants to.

It will remove all clerical work that is done by many people instead of that only oneperson will acquire the whole work.

It can be used easily and the time saving.



26

5.3 Constraints

The constraints associated in the development of any software system include those thatare common to all system and constrains specific to the system. The common constrains mayinclude lack of managerial participation, tight development schedule, frequent change inrequirements of the management, etc. we have also experience similar types of constraints listedabove and others some of the constrains are listed below with which we have developed thissystem.

It is a general system and hence there is unique firm layout and format.

It require XP or higher version of o.s. including appropriate softwares

Numbers of user depends on the capability of the system.

This project is to be developed as a part of curriculum and to be submitted within aperiod of 4 month.

Net connection, Video shutting device and software are requiring for some of functionality.



27

5.4 Expected Advantages

High Security

There is high security mechanism provided by the proposed system. Nounauthorized person can make change in the data those are stored in system. Onlyauthorized person can change & also can make login.

Less Time Required

In our proposed system, all the processes are carried out by computer soobviously it will require time than traditional inventory system and in that sense; in willrequire less time to complete transactions and can process data very fast.

High Amount of Accuracy

In our new proposed system there are less amount of human activities areinvolved in that case it will have less effect in our accounts. The new system will performall calculation and manipulation automatically; in that case the data that we receive will

be accurate and much more reliable than the data that generated previously.

Intercommunication

In our system we have intercommunication facility are provided. It use forcommunicate with one manager to another manager at place they stay. When in intercommunication manager want to take decision about any problem ,he can take help of another manager in that case it is very useful.

Online image Capturing

In our system online capturing is one of the main advantages of our software.When manager want to capture some images of employees or item then manager caneasily use and capture images.



28

Report Creation

Information processing is very quick so actual data requirement to create reportsare timely provided. So reports can be generated at any time as required by management.

System Can Be Implemented

Since all requirements are fulfilled and satisfied by our comprised system and can

perform all tasks that provided by management, but in circumstances, if our managementwants to improve our system and they compel to make any changes in our existingsystem. We can improve that change according to the management requirement.



29

6.Detailed planning



30

6.1 Use case diagrams

Manage user

User

Administrator Operators



31

Authenticate

User Login

User Time in

User Time out



32

Manage data

Manage reports

Daily Report

Production Report

Payments Report

Orders Report

Inventory Report

Employee Report

User

Employee Management

Party Management

Order entry Management

Production Management

Inventory Management

User



33

6.2 Data flow diagram

ProductPlanningControl

0

Party

Orders andProduct info.

Send quotesInfo. About order return

Sales return message

Supplier

OrderRaw material

Bill and order detail

Purchase return messafe

Sales department Purchase department

Order,bill and orderreturn info.

Orders list

Sales return report

List of raw material

List of raw material toreturn and bill info

Purchase returnmessage

Context level diagram



34

company

OrderProcessing

System1

Order_entry

Material_track

Material info

MaterialTrackingSystem

2

checkreply

Materialavailable

yes Order_masterno

ProductionDepartment

3

Bill_master

Checkingquality

Isproper

Alsoyes

noyes

Paythebill Management

Dispatchgoods

5

Generateinvoice

4

Info of complete goods

Salesdepartment

6

1st level diagram



35

Inventory_master

Inventorystatistics

InventoryManagement

3.1

DailyTransaction

3.2

Search forPropergoods

Updateinventory

search

If

availableyes

Production

department

Giving info of orderno

Inform to management

Finshed_material

ImportMaterial

3.3Material to be

imported

UpdateInventory

Afterreplacing

Update inventoryAfter

importing

Purchase_master

Material to be replace

Purchasereturn

3.4

Management

2nd diagram of inventory management



36

Order_entry

Orderinformation Cutter3.1 Production_master

Cutterreport

StoreCutter

info

router3.2 Production_master

routerreport

Storerouter

info

Sanding3.3 Production_master

sandingreport

Storesanding

info

pasting3.4 Production_master

pastingreport

Storepasting

info

postform3.5

Production_master

Pastformreport

Storepostform

info

triming3.6 Production_master

Storetriming

info

b

Orderinformation



37

Order_entry

Orderinformation

Edgebending

3.7 Production_master

Edgebending

report

StoreEdge bending

info

cnc3.8 Production_master

Cncreport

Storecncinfo

membrane3.9 Production_master

Storemembrane

info

b

membranereport

packing3.10

Production_masterStorepacking

info

Orderinformation

Dispatch_master

Packing &Complete reprt

2nd diagram of Production department



38

Purchasedepartment

Supplier_mst

Purchaseproduct

info

Get messagefrom

Purchase return

3.4.2

Purchase_return

Reason & quanlity

Reason & quantity

supplier

Send quantity &Reason of

purchaseReturn3.4.1

Purchase_mst

Purchase returninfo

Problem message orpurchase return msg

Supplierinfo

2nd diagram of purchase return



39

Salesdepartment

Received billFromParty

6.1

party

sales

Validateproduct

ForReturns

6.2

Perform sales returntransaction &

icncrease stock6.3

Sales_return

Bill &partyinfo Bill &party info

Sales_detailRequest message for

return goods

Product toreturnwith

product

Salesreturn info



40

2nd diagram of sales return

Generateinvoice

4.1

Order_entry

Orderinformation

Bill_info

billinformation

Party

Sendinvoice

2nd diagram of Generate invoice



41

Dispatch order5.1

Order_entry

Orderinformation

Dispatch_order

Dispatchinformation

Party_info

Partyinformation

PartySendgoods

2nd diagram of Dispatch order



42

6.3 Process specification

User Login

UserLogin

This process checks weather an attempting user isauthorized or not, if not

Then it will not allow user to login.

User Login informationLogin successful/

error

Order Entry

Order Entry

This process takes information about order and insertorder into order_entry.

Order informationOrder inserted

successfully



43

Import data

Import data

This process directly imports data from excel or xmlinto database without manually entering data.

File in excel or xmlformat

Order insertedsuccessfully

Inventory operation

Inventoryoperation

This process takes item information and performoperations like insertion,deletion or updation of item.

Data about itemOrder inserted / updated/deleted

successfully



44

Daily transaction

DailyTransaction

This process allows recording of daily transactionmade in company and also update the inventory.

Data about transaction Update the inventory

Employee record

Employeerecord

This process performs insert,update or deleteoperation on employee info.

Data about employeeInsert/update/delete

employee record



45

party record

Partyrecord

This process performs insert,update or deleteoperation on Party info.

Data about partyInsert/update/delete

Party record

Supplier record

Supplierrecord

This process performs insert,update or deleteoperation on supplier info.

Data about SupplierInsert/update/delete

Supplier record



46

Transporter record

Transporterrecord

This process performs insert,update or deleteoperation on Transporter info.

Data about TransporterInsert/update/deleteTransporter record

Order dispatch

OrderDispatch

This process stores info about dispatch of order likedisp.date , party name,billing and shipping adress,ship

by and ship cost etc.

Data about order andtransportation

Stores info aboutorder dispatch



47

Bill info

Bill info.

This process stores billing information of the order likeAmount,paid,remainning amount,bill no,order no,bill

date,due date etc.

Data about order andbill

Stores info about billof order

Payment info

Paymentsinfo.

This process receive payments for the order andupdate bill info for that order. F necessary it will apply

interest on payment.

Data about bill andpayments

Updates the bill info



48

6.4 Entity-relationship diagram



49

Party

Part _nam

Importance

Contact person

Address

PhoneFax

Email

Order

Order

Order no

Serial no

ParticularQuantity

Product

Colo

Part _name

d

MM

Isgiven

M

Productio

Process_nam

Order n

Serial

date

Type

Quantity in

Quantity out

1

Dispatc

M

M

Payment

Pays

1

M

Order no

Part _nam Bill no

Amount

Payed

Remainnin

Due date

date



50

6.5 Data dictionary

Name Login Info

Alias None

Where and HowUsed

Login(input/output)

Description Username,password

Name order Info

Alias None

Where and HowUsed

Order_entry(input/output)Bill_info(input/output)

Production(input/output)Order_dispatch(input/output)

Description Order_no,serial_no etc.



51

Name material Info

Alias None

Where and HowUsed

Item_master(input/utput)Daily_transaction(input/output)

Description Item_no,quantity,ideal_quantity,warn_quantity,

Default supplier,description etc.

NameDaily Info

Alias None

Where and How

Used

Item_master(input/utput)

Daily_transaction(input/output)

Description Item_no,quantity,ideal_quantity,warn_quantity,Default supplier,description etc.

Nameproduction Info

Alias None

Where and HowUsed

Order_entry(input/utput)Production(input/output)

Process(input)

Description Order_no,serial_no,process_name,type,quantity_in.quantity_out,date, etc.



52

NameEmployee Info

Alias None

Where and HowUsed

employee_master(input/utput)mailinfo(input)

Description Employee_no,employee_name,address,dob,doj,Phone,mail etc.

NameParty Info

Alias None

Where and How

Used

Party_info(input/utput)

Order_entry(input)Bill_info(input)Order_dispatch(input)

Description Party_name,importance,contact person,address,phone,email etc.

Namesupplier Info

Alias None

Where and HowUsed

supplier(input/utput)item_master(input)

Description supplier_name,supplier_no,contact person,address,phone,emailetc.



53

Nametransporter Info

Alias None

Where and HowUsed

transporter(input/utput)order_dispatch(input)

Description transporter_name,vehicle,contact person,address,phone,emailetc.

NameOrder sispatch Info

Alias None

Where and HowUsed

Order_dispatch(input/utput)Order_entry(input/output)

Transporter(output)Party_info(input/output)

Description Order_no,serial_no,party_name,billing address,shippingaddress,ship by,ship cost,date etc.

Namebill Info

Alias None

Where and HowUsed

Bill_info(input/utput)Order_entry(input/output)Party_info(input/output)

Description Order_no,serial_no,bill_no,party_name,amount,paid,remainning,Date,Due_date etc.



54

7.System Design



55

7.1 Database design

Bill_info

Category

Color1



56

Color2

Daily_transaction

Order_dispatch



57

Employee_master

Item_master



58

Measure

order_entry



59

Party_info

Passwd



60

Process

Production

Supplier



61

Transporter



62

7.2 Input design1) Main page



63

2)Profile



64

3)Order_entry



65

4) Import data from XML



66

5) Item master



67

6)Item master- Category



68

7)Item master-unit measure



69

8) Item master-supplier



70

9) Item master-supplier operation



71

10) Daily transaction



72

11) Production



73

12)production-process



74

13) Time in authenticate



75

14) Time out authenticate



76

15) Employee master



77

16) Party information



78

17) Order Dispatch



79

18) Order dispatch- transporter



80

19) Order dispatch- transporter operation



81

20) Bill information



82

21) Bill Information-party



83

22) Bill Information-party operation



84

23) Payment



85

24) Sent Mail



86

7.3 Output design 1)Daily Report



87

2) Order Dispatch Report



88

3) Employee Report



89

4) Inventory Report



90

5) Orders Report



91

6) Payment Report per party



92

7) Payment Report per order



93

8) Production report



94

8.Software testing



95

8.0 Software testing

Testing is just like quality assurance to review products and related documents forcorrectness, completeness, reliability, and maintainability. And it includes assurance that thesystem meets the specifications and requirements for its intended use and performance. Thecommon view of the testing is to prove that there are no errors.

System testing is too much expensive as well as it is not possible for analyst to prove thatsoftware is free and clear of errors.

We have use the following testing strategy:

Code Testing:

The code testing examines the logic of the program. To follow this testing we havedeveloped test cases that result in every instruction in the program or module; that every pathis specific combination of conditions that is handled by the program.

However, code testing does not define the failure of the system. As well as this testingdoes not determine that whether the system meets its specification nor does it determineswhether all aspects are implemented.

Specification Testing:

To perform specification testing, we have to examine the specification – defines that thesystem should do and how it should do under various conditions. Then test cases aredeveloped for each conditions or combinations of conditions. So we can determine whetherthe system performs according to its specification requirement.

For example, one of our specifications in security aspects is that only administrator canuse some of the facilities (like Create User, Delete User, and Grant Permission). If yousuccessfully login as “Root” then only you will be assigned to perform the above operations.

Unit Testing:

Unit testing forces first on the modules, independently of one another to locate the errorsin coding and logic that contained within that another module alone



96

For example, Test cases needed to check user, whether user is authorized or not, as well as if user is authorized then which permissions are granted and than checks whether user allows to dofunction with respect to the permission assigned to him/her.

We have performed unit testing from bottom up, tested each components of the modulesindependently, than integrate all the components and tested each modules independently.After that we have merged all the modules and tested the whole system.

System Testing:

System testing does not test the software per second but rather the integration of each module in the system. The primarily but rather is the compatibility of eachindividual module. Analysts try to find areas where module has been assigned differentspecification for data length type and data element name.

For example, one module may expect that data for No to be a number.

While other module expect it to be a character data item. The system may itself not report to this is an error.

Storage Test:

We have to specify capacity for the system when it is designed and constructed.Capacity measure in terms of the number of records than the disk will handle or file cabcontain.

System can handle patient of much more. And size of the disk where our databaseis stored is 40 GB, which is good enough.

Performance Test:

When we are developing a design, their concerns are more on reports, inputs, andprocessing sequence than on performance time.

Performance time testing is conducted prior to implementation to determine howlong it takes to receive a response to an inquiry.



97

We have used only one connection for the whole system, which also helpful toincrease performance time.

In the beginning, we cannot measure the performance time but after system isloaded with data we can sure about performance.

Recovery Testing:

The system should be capable to recover the stored data if user has performed the

illegal operation or delete records.

For example, we have provided facility, when user delete database, there is afacility of backup to recover database. It means user have chance to recover backupdatabase.

Output Consideration:

All the reports were produced & documented as per the general requirement of patient management. The reports are in the required as per the usual requirements. Theformats, depending on the need of organization, can vary as compared to designedformats.



98

9.Limitation and system

enhancement



99

9.0 System limitation and enhancement

System Limitation

Each and every system has some limitations that can restrict then to work on a particularenvironment. Through our system is provided high amount of accuracy and quick datageneration there is still some limitations that led us to in greater deficiency to work on thatsystem. Some of the limitation that is observed during all the process is mentioned below.

1. Accounting is IgnoredIn our system there is a work related to transaction but our system does not haveAccount system for the patient and other money transaction related in ourorganization

2. For Networking purpose, it is not UsefulOut system is work on stand alone PC, for widely use networking is compulsory butin our system it is not possible.

3. data cannot backup or restored if files are currently open

If we want to create back up or use restoration if a file or a directory is currentlyopened then these operation can not possible and may crush our program.

System Enhancement

In future our system can include Accounting system, Networking scope and Good Backupand restore Facility.



10 References

1. MSDN Library of Microsoft Visual Studio 2005

2. Websites

2.1. Google.com

2.2. wikipedya.com

2.3. a1vbcode.com

2.4. vbcodeheven.com

2.5. codeguru.com

2.6. dotnethaven.com

2.7. codeproject.com

2.8. vbtutor.com

production planing control

Documents