Project Doc Omen Tat Ion

8/8/2019 Project Doc Omen Tat Ion

1/80

FINAL PROJECT DOCUMENTATION

(General Inventory Management System)

General Inventory Management System

DEVELOPED BY:

FAHAD SHAHZAD Roll No: N447143

SYED MURTAZA Roll No: N447144

INAM ULLAH Roll No: N447147

Students of BS (CS) Final Semester

Supervised By: Mr. Asif SohailDepartment Of Computer Science

Allama Iqbal Open University,

H-8, Islamabad


2/80

Year 2007

Declaration

We hereby declare that this software, neither as a whole nor as a part thereofas been copied out from any source. It is further declared that we developed

this software and this report entirely on the basis of our personal efforts

made under the sincere guidance of our project supervisor.

If any part of this software probed to be copied or found to be a report of

some other, we shall standby the consequences.

No portion of the work presented in this report has been submitted insupport of any application for any other degree or qualification of this or any

other University or institute of learning.

We further declare that this software and all associated documents, reports,

and records are submitted as partial requirement for the degree of BS (CS).

We understand and transfer copyrights for these materials to Allama IqbalOpen University, Islamabad.

We shall not sale this software and documents and shall not get any

Financial gains from these.

STUDENT NAMES: SIGNATURES:

INAM ULLAH Signature: ____________

FAHAD SHAHZAD Signature: _____________

SYED MURTAZA Signature: _____________


3/80

PROJECT SUPERVISOR: SIGNATURE: ____________

Final Approval

This is to certify that we have read the project report titled as (General

Inventory Management System) submitted by students as mentioned below.

It is our judgment that this report is of sufficient standard to warrant its

acceptance by Allama Iqbal Open University, Islamabad, for BS (CS)

degree.

Examination committee

1. Internal Supervisor

Designation

Study Center Computer People 2000, Sialkot

2. Internal Examiner

Designation

Study Center Computer People 2000, Sialkot

3. External Examiner .

Designation .

Study Center/Organization .


4/80

Acknowledgment

All thanks and praise to ALLAH the Almighty who blessed us with

Knowledge and courage to accomplish this job.

We are thankful to our parents whose prayers helped in every problem

pf life and the provision of necessary resource to facilitate us.

We are thankful to our teachers who helped us to carry out this job

and provide us guidance to complete this project specially Mr. ASIF,

project supervisor and the teachers who taught us were excellent in their

fields and they gave us new ideas and meanings to the problem related to our

academic and regular life.

We are especially thankful to the administration of organizations for

providing us all the necessary information about the organization required

for completing the project.

Especially we are thankful to Mr. AJMAL, Mr. MUHAMMAD

JAWAD and Mr. MUHAMMAD FAISAL who helped us a lot and proved

to be an excellent resource person along with the excellent guiding skills and

friendly nature.

In the end we want to thank all our sincere friends and class fellows

who stood by us in every situation. We pray for all to be a useful and sincere

beneficent asset for themselves and for their country.


5/80

Project In Brief

Project Title: GENERAL INVENTORY MANAGEMENT SYSTEM

Organization: GENERAL (ANY ORGANIZATION CAN USE IT)

Objectives: Atomize the Manual Inventory system

Developed By: 1) INAM ULLAH (N447147)

2) FAHAD SHAHZAD (N447143)

3) SYED MURTAZA (N447144)

Supervised By: Mr. Asif Sohail

Tools Used: Ms Visual Basic 6

Ms Office XP 2003

Ms SQL Server 2000

Crystal Report

Erwin 4

Operating System: Windows XP Professional


6/80

System Used: Pentium 4 (1.8 GHZ or Greater)

Abstract

Need:

Mostly organization use Manual System to manage all their records .Their

manual system works very slowly and management of records becomes

difficult. The growth of any organization and its outlets require an efficient

computerized system which is faster than the manual system and to keep

their records efficiently in the ongoing system.

Objectives & Scope Of Work:

Our goal is to provide a computerized Inventory

Management System for organizations to manage their records efficiently.

Features:

1-Perpetual:

The system provided will be perpetual i.e. the record will be updated

along with the transaction.

2- Flexibility:

The system will provide the user flexibility of adding or

removing any category or attributes of the Database.


7/80

Method Of Studying:

a) Direct meetings with the resource person to understand their

requirements.

b) Studying the working methodology of the organization.

c) Observing the working criteria of the Existing system used in

organization and draw backs in it.

Major Finding:

Inflexible:Manual record keeping system was not much efficient.

Concluding Remarks:

This is just the beginning for us but now it will step toward progress.

The inventory system must be refined according to modern values.

The system should be easy to use.

It will save lots of time, complexities and minimize the administrative

overhead.


8/80

TABLE OF CONTENTS

CHAPTER # 1 INTRODUCTION

1.1 BRIEF INTRODUCTION OF THE ORGANIZATION

1.2 PROBLEM DEFINITION

1.3 SCOPE OF THE PROJECT

1.4 BROAD BASED OBJECTIVES

1.5 SPECIFIC OBJECTIVES

1.6 FEASIBILTY REPORT

CHAPTER # 2 EXISTING SYSTEM ANALYSIS

2.1 INTRODUCTION

2.2 DETAIL STUDY OF EXISTING SYSTEM

2.3 DRAW BACKS IN EXISTING SYSTEM

2.4 MAIN ANALYSIS DIAGRAM

CHAPTER # 3 PROPOSED SYSTEMS

3.1 OBJECTIVES

3.2 SYSTEM PROPOSAL

3.3 MAIN SYSTEM DIAGRAM

3.4 BENEFITS/MAIN FEATURES OF THE PROPOSED

SYSTEM

CHAPTER # 4 SYSTEM DESIGN

4.1 INPUT DESIGN

4.2 OUTPUT DESIGN

4.3 CODE DESIGN

4.4 USER INTERFACE DESIGN

4.5 DATABASE DESIGN


9/80

CHAPTER # 5 SYSTEM IMPLEMENTATIONS

5.1 INTRODUCTION

5.2 METHOD USED FOR IMPLEMENTATION

CHAPTER # 6 SYSTEM TESTING & EVALUATION

6.1 TESTING STRATEGIES

6.2 CODE TESTING

6.3 PROJECT TESTING REPORT6.4 USER TRAINING

6.5 CONCLUSIONS

CHAPTER # 7 FUTURE EXTENSIONS

7.1 INTRODUCTION

CHAPTER # 8 USER GUIDE

8.1 INTRODUCTION

REFERENCES

Books and materials referenced to with author, title, publishing

company, year of publication, page number

APPENDICES1) ER- Model

2) Sample input screens

3) Sample output screen


10/80

C H A P T E R

INTRODUCTION

CONTENTS:

BRIEF INTRODUCTION OF THEORGANIZATION

PROBLEM DEFINITION

SCOPE OF THE PROJECT

BROAD BASED OBJECTIVES

SPECIFIC OBJECTIVES

FEASIBILTY REPORT

1


11/80

BRIEF INTRODUCTION OF THEORGANIZATION

Any organization like factory or departmental store whichdeals with

the selling, purchasing & ordering of different items can usethis

application because it is general inventory managementsystem.

This system can be used in many situations where inventoryof items

are expected. This system can deal with items like

Mobile phones;

Accessories of any items,

Chemicals used in factory,

Household things, raw material used in factories,

Garments,

Cosmetics,

Stationary,Etc.

PROBLEM DEFINITION


12/80

Mostly organizations use manual systems for their stock &storing

data. By using manual system, management needs a lot oftimes for

checking the stock of any product. It is also difficult formanagement

to note the daily sale in the register at end of any day andcollect the

sale of all the days at the end of every month. By calculatingor

knowing about the profit & loss. But still loss or profit isntknown

exact. Management cant know at any time about the exact

performance of any organization or departmental store.

SCOPE OF THE PROJECT

Scope of the project is to provide a computerized inventory

management system. If any organization or departmentalstore use


13/80

system then following tasks can be performed:

Minimize resource consumption,

Maximize utilization of the resources,

Provide help to management to know about every thingor matter about the organization or departmental store,

Helps management in decision making to increase theperformance of any organization,

Information can be obtained easily.

BROAD BASED OBJECTIVES

Broad based objectives are those essential tasks which are

added in

Software. Following are the Broad based objectives:

Reduce human efforts,

Reduce the paper work,

Reduce repetitions,

Easy approach to obtain information,

Improve the performance of the management,


14/80


15/80

FEASIBILITY REPORTS

The main purpose of feasibility study is to consider theproposed

system with a view to decide weather the developed of theproposed

system is feasible for the organization in the underlyingcircumstance.

It is considered that whether the proposed system will meetall the

requirements of the organization with lesser cost and withimproved efficiency that the exciting if exists.

Feasibility of the project can be measured by followingpoints:

Operational Feasibility Report Technical Feasibility Report Economic Feasibility Report

1- Operational Feasibility Report:Operational Report gives

us the

information how to operate the project. It tells us that whichtools we

will need and use for successful Accomplishment of ourproject.

2- Technical Feasibility Report:Technical report gives us the

following information:


16/80

Is a project technically feasible?

Can defects be reduced to a level matching theapplications need?

Technical report is state of the art. It depicts the technical

complexities for the project.

3- Economical Feasibility Report:Economical report gives us

the

information, can development be completed at a cost thesoftware

organization its client or the market can afford it.

It is a measure of cost effectiveness of a project orsolution. It

tells us cost of a project.

SUMMARY REPORT

After performing these tests we conclude that the

project is feasible, that is the solution is acceptable to

the all concerned, from the point of view of performance

improvement.

The project is technically feasible as the solution can

have the capacity to work in a practical situation.


17/80

The project is also schedule feasible as we have a

substantial amount of time available to complete the

project according to university recommendations.

The economic feasibility is not determined for the time

being as we are not developing a project for commercial

purposes, and only as a coursework recommended by

the university.

However, in every project the cost effectiveness factor is

also considered to determine the cost for developing a

system and the benefits of the system. The cost may

include the technical staff required, the software tools,

the equipments, the methods and above all budgetary

details. If a project, however requires high cost but

provides low benefits is not feasible. If a project,

however, requires high costs and provides high benefits

is technically feasible but not economically.


18/80

C H A P T E R

EXISTING SYSTEMANALYSIS

CONTENTS:

INTRODUCTION

DETAIL STUDY OF EXISTING SYSTEM

DRAW BACKS IN EXISTING SYSTEM

MAIN ANALYSIS DIAGRAM

2


19/80

INTRODUCTION

This step involves the analysis of the whole system. Nothing

can be

Done without full analysis of the problem. In every field oflife, one

has to take a brief look at the problem 1st then tries toremove the

drawbacks. Any example you take from the real worldinvolves this

step of analysis & then proposing the solution of thatproblem. A

doctor before prescribing any medicine to the patientanalyze her/him

with the help of tests taken & his own analysis, an engineerwould

never build any thing before analyzing the environment.

Similarly, a system analyst needs to study the system deeply&

properly for the further actions. It is the most important stepin

developing a new system, the base of the whole systemdepend upon

the understanding of the analysis of the existing systembecause this


20/80

analysis will help to reduce the flaws in the existing systemwill

overcomes all the drawbacks.

Program or system study can be responsive only if theproblem is

Properly understood. Error in understanding leads to designerror.

Through study of existing system is necessary to design anew

system which is more efficient, flawless & reliable.

DETAIL STUDY OF EXISTING SYSTEM


21/80

Existing system is manual. Whenever the customer is come,the

seller helps him to buy his required item, the bill manually.Then

he gives original copy of invoice to customer & has a carboncopy of

invoice o cash memo of there own record.

If the customer pays his bill as a credit he accountant keepshis

records on the credit book with the name address invoice hiscredit

amount. Similarly, they purchase different items fromdifferent

companies for sale. If they bought as borrow then theykeeps the

record of creditors in creditors debit book with company

name & with

debit amount.

DRAW BACKS IN EXISTING SYSTEM

The manual system is work in the following ways:


22/80

There are registers in which a record of all the things &books is

Written when new stock is arrives. This is done on monthlybasis as

New stock arrives on every 1st day of the month aftereverything is

recorded then the whole stock is loaded in the basement &the extra

place/store hired to store the stock. After all the recording ofthe stock

in a register, the things needed in the store or shop aretaken out of

the stock & are available for sale, there is no record of thenumber of

copies sold for a particular book. There is no proper systemof

issuing a bill to customer as the bill is written on a piece ofpaper &

the total is calculated manually. This can sometimes produce

inaccurate results as human beings can make mistake.Following are the main draw backs of the existing system:

1. Chances of too many errors like improper stock keeping

erroneous calculation of bill etc.

2. The manual system is too much time consuming andold fashioned.


23/80

3. It is not properly giving services to managementbecause it is not efficient.

4. Wastage of time.

5. Huge volume of documentation.

6. A lot of paper work.

7. Difficult to maintain records.

8. Extra usage of stationary.

9. Extra usage of Human resource.

10. No specific report system and lot of time requiredto prepare reports.

11. No long life future planning.

12. Current situation of organization is unknown

To overcome the difficulties faced by organization and tomaintain

the record properly the new proposed system will be moreprecise

and efficient.


24/80

C H A P T E R

PROPOSED SYSTEM

CONTENTS:

INTRODUCTION

PROPOSED SYSTEM

OBJECTIVES OF THE PROPOSED SYSTEM

MAIN ANALYSIS DIAGRAM

3


25/80

INTRODUCTION

After analyzing the existing system and encounteringthe

shortcomings of the present system, it was necessary toremove its

deficiencies and give a worthy solution for presentlyencountered

problems. The proposed system has therefore beensuggested

keeping in view the need and demand of the organization.

Frequent visits to the organization (Store) and interviews of

the

concerned staff and some executive to understand theexisting

working strategy are the basis of the proposed system.


26/80

PROPOSED SYSTEM

After knowing the existing manual system andencountering the

shortcomings of the present procedure of getting knowledgeabout

stock, purchasing & selling of items, invoice records of

creditors and

debtors it is necessary to overcome the drawback of thecurrent

system and gave a worthy solution of the problem. Theproposed

application for Stores is therefore been suggested keeping innew the

needs and comforts of the user.


27/80

OBJECTIVES OF THE PROPOSED

SYSTEM

The main goal of this project is to design andimplement a GUI

system in which data entry, report generation and queriesare

possible, which help the management in decision making.

Following

objectives are kept in mind while proposing the system:

The proposed system should be more efficient than theexisting system.

The interface should be user friendly and provide helpto user, where required Should have the capability andprocess information which is entered into it.

It should be error free and reliable.

To make data reliable.

It should minimize redundancy of data.

It should be a comprehensive.

It should be a comprehensive data consisting ofinsertion updating accession and deletion of any record.

Keep every thing nice and simple for all users.


28/80

The system should generate reports whenever ifdemanded by the user.

SYSTEM PROPOSAL

The pc based application is proposed which could the

necessary requirements about billing of customers, anddebited


29/80

records is small tie and in organization to get accuratereports. It will

provide its organization with required information such as:

1. Detail information about a specific items its quality inhands, its price per unit, when to order this item forrepurchase.

2. No of customers, Orders, Sale and Purchase Details anditems they have purchase from store.

3. Total quality sale of specific item on per day basis.

4. Total sale of all items on per day basis.

By using the system organization can make the reports and

information up to date. Consequently the whole procedureresults in

the better performance of the organization.

MAIN SYSTEM DIAGRAM:


30/80

BENEFITS/MAIN FEATURES OF THEPROPOSED SYSTEM


31/80

A pc based menu driven computerized system is

proposed which could satisfy the necessary requirementsand

improve upon the currently running system considering theobjectives

of the proposed system its main features are:

Following features are kept in mind while proposing thesystem.1. User Interface/Friendly:

For better user interaction thescreen

would be well designed keeping in mind that enter should besimple

and easy for the user and data will be accepted in the samemanner

as it is done manually.

2. Checks:Various checks will be provided in the data

entry,

updating and deletion modules to appropriate action. Thechecks may

be to avoid duplicate record, item validation, range checksetc, the


32/80

system will give appropriate message upon the conflict witheach

check.

3. Updating:System will also provide the facility of

updating. Any

mistake detected or any other necessary updating can easilybe

made through updating. User may update any field with theexception

of PK defined for that table because database does not allowthis.

5. Deletion:Facility of deletion of a particular record is also

provided

to the authorized user. Only those records can be deletedthat do not

have a foreign key relationship with some other table.

6. Ease of Use:The developed application is User -

Friendly

software to handle and use. Data entry, deletion, searches,exit is all

provided on a single form.

7. Application Security:The security of the application is


33/80

implemented by allowing only organization user to log on the

application and performed desired task.

8. Consistency:

Uniform notations have been usedthroughout the

application. Efforts have made to keep the datahomogenous. This

had been accomplished by reducing data redundancy, insertand

update anomalies.

C H A P T E R

SYSTEM DESIGN

CONTENTS:

INTRODUCTION

INPUT DESIGN

4


34/80

OUTPUT DESIGN

CODE DESIGN

USER INTERFACE DESIGN

DATABASE DESIGN

INTRODUCTION

Design is the first step in moving from the problem domaintowards

Solution domain. Design is essentially the bridge b/w

requirements

specification and the final solution for satisfying theRequirements.

It may be the process of applying various techniques andprinciples

for the purpose of defining a device, a process andapplication or a

system. Before the Development of any system it isimportant to


35/80

make its design before its implementation. Design of thesystem must

be flexible and easy for the user.

System Design is divided into following steps.

Input design

Output design

Code design

User interface design

Database design

INPUT DESIGN

Input is the information that is required for the user forfurther

processing by the system. Input design activity is related todesign of

reviewing such information from the user in well format.

Data entry forms of application are design toget data

input. Mostly text fields, input boxes, combo boxes are usedfor data

input. Also some checks are applied on data entry so thatuser avoids

invalid data entry. Before designing of input taking systemslength

and type of each field is determined.


36/80

GENERAL PRINCIPLE OF INPUT DESIGN

1. Entry only variable data

2. Dont enter data that cant be stored or calculated in

computer programs.

3. Use codes for appropriate attributes.

4. Include instructions for completing the form.

5. Minimize the amount of handwriting.

6. Data entered should be sequenced.

7. Place portions of the form that arent to be input in or

about the lower right portion of the source document.

8. Ensure that the data is valid.

Following checks can ensure validation of data like

- Completeness checks

- Limited and range checks

OUTPUT DESIGN

The output design also plays an important role incomputerized


37/80

systems. User wants the perfect and on time outputs whichcan make

system more and more efficient. In designing outputfollowing factors

are kept in mind.

1. Computer outputs should be simple to read andinterpret,

2. Title is given to every report or output screen,

3. Section headings are included to divide large pieces of

information,

4. Purpose of output should be clearly mentioned.

TYPES OF OUTPUTS

There are two types of outputs.

Screen Outputs

Printed Outputs

Screen Outputs:These are such statements which gives

retrieval of


38/80

data on screen. Since the System is database oriented so thesystem

should be appropriate and good for showing outputs. Screenoutputs

may be in the shape of message box, labels and some other

components of language.

Printed Outputs:Printed outputs are typically concerned with

reports

of different types. e.g. Stock Report, Product Report etc.

CODE DESIGN

Coding is a process of writing instruction that can be run on

computer hardware.

In the coding phase, the design of a system is translated into

machine readable code by using specific language. Although

the coding phase doesnt effects the structure of the system,

it has great impact on the internal structure of modules,

which affects the test ability and understands ability of the

system.

The goal of the coding phase is to produce simple and clear

program. That aim is not to reduce the coding effort but toprogram in


39/80

a manner such that the testing and maintenance cost arereduced.

USER INTERFACE DESIGN

The user interface design is the activity comprising

interaction

between the system users, and the computer.

There are several types of user interface styles. These

different types of interface styles are blended when we

design systems with GUIs.

With the advent of graphical operating system, the world

of computing went through a dramatic change. It opened

up a whole new world of graphics. Interface such as GUIs

became very popular because displayed on screen.

The primary requirement for an interface is that it is

easy to use. A user must be able to react intuitively to

an interface provided to him.

The design process for user interface design is iterative

and can be represented by using spiral model.

The activities of spiral model are:


40/80

1. User, Task And Environment Analysis And Modeling,

2. Interface Design,

3. Interface Construction

4. Interface Validation

PRINCIPLE OF USER INTERFACE DESIGN

During user interface design, following guidelines are

followed:

- Placing the user in control

- Reducing the users memory load

- Making the interface consistent- Hide technical details

- User familiarity


41/80

Basic Components Of A Interface:

- Windows

- Buttons

- Text boxes

- List boxes

DATABASE DESIGN

Physical database design is a process of mapping

database structures from logical design to physical

storage structures such as files and tables. Physical

database design is a activity in a activity in any

database design having following steps:

o Define database to DBMS.

o Decide on physical organization of

data

o Design program.


42/80

DESIGN OF DATABASE


43/80

C H A P T E R

SYSTEM IMPLEMENTATION

CONTENTS:

INTRODUCTION

METHOD USED FOR IMPLEMENTATION

KEY ELEMENTS IN METHOD USED FORIMPLEMENTATION

5


44/80

INTRODUCTION

Implementation is the next phase in the system

development life cycle. Implementation includes all thoseactivities

that take place to convert from the old system to the newone.

In Implementation basically we find the way to develop thesystem. In

Implementation phase coding is performed. Implementationis also

called System Development. In this phase system is built ormeets

the proposed and designed specification.


45/80

METHOD USED FOR IMPLEMENTATION

Method used for Implementation is divided

into some phases1. Analysis2. Design3. Coding4. Testing

When we adopt any Method for Implementation it consists ofthe

phases given above.

1. Software requirement Analysis:Software

requirement Analysis

is the first phase of the method used for Implementation. To

understands the nature of the program to be built thesoftware

engineer must understand the information domain for thesoftware, as

well as required function behavior, Performance andInterface.

2. Design:Software design is the next step of methodused for

implementation. It is a process that focuses on theattributes of the


46/80

program such as Data structure, Software architecture,Interface

Representation and procedural Details.

The Design process Translates requirements into the

representation of the software that can be accessed forthe quality

before coding begins. Design may be procedural orDetailed

Design.

3. Coding:After designing next activity of method for

implementation is Coding. The design must be translatedinto a

machine readable form. The code generation step performsthis task.

Coding process is also called Development orImplementation.

4. Testing:Once code has been generated, program

testing

begins. Testing phase insures that there are no errors and

bugs in

the system. System is tested by using many differentapproaches.


47/80

KEY ELEMENTS IN METHOD USED FORIMPLEMENTATION

There are some key elements which plays animportant role in implementation methods:

1. Software And Database Selection


48/80

2. Software And Database Design

3. Selecting Suitable Software Process Model

C H A P T E R

SYSTEM TESTING & EVALUATION

CONTENTS:

6


49/80

INTRODUCTION OF SOFTWARE TESTING

TESTING OBJECTIVES

TESTING PRINCIPLES

TESTING STEPS

TESTING STRATIGIES

CODE TESTING

PROJECT TESTING REPORT

USER TRAINING

CONCLUSIONS

Introduction of software Testing

In a software development project errors can beinjected at

any stage during the development. For each stage there aresome

techniques with which we can detect errors and bugs fromour

system.Testing is a phase where errors remaining fromearlier


50/80

phases are detected.

TESTING OBJECTIVES

Testing objectives can be stated as:

1. Testing is a process of executing a program with the

intent of finding an error.

2. A good test case is one that has a high probability of

finding an as-yet-undiscovered error.

3. A successful test is one that uncovers an as-yet-

undiscovered error.


51/80

TESTING PRINCIPLES

Testing principles are given below:

1. All tests should be traceable to customer requirements.

2. Tests should be planned long before testing begins.

3. Testing should begin in the small and progress toward

testing in the large.

4. Exhaustive testing is not possible.

5. To be most effective, testing should be conducted by an

independent third party.


52/80

TESTING STEPS

Software is tested from two different perspectives:

Internal program logic is exercised using white box test case

design techniques, and software requirements are exercised

using black box test case design techniques.

In both cases, the intent is to find the maximum number of

errors with the minimum amount of effort and time.


53/80

TESTING STRATEGIES

Following testing strategies are adopted by us to ensure

software operability:

Black Box Testing:

It is also called Functional Testing.

Testing without the knowledge of theinternal system being tested.

Focuses on the functional requirements ofthe software.

Test cases are designed to find thefollowing types of errors in the software:

a) Incorrect or missing function,

b) Interface Errors,

c) Errors in data structure or database access,

d) Behavior & Performance errors,

e) Initialization & Termination Errors.

White Box Testing


54/80

It is also called structural testing or glass boxtesting.

It is used to test the internal procedural workingof a module.

It enables us to detect errors caused by typingmistakes.

Test cases are designed for the followingpurposes:

a) Ensure the all the independent paths within amodule have been exercised at least once.

b) Exercise all logical decisions on their true andfalse side.

c) Execute all loops at their boundaries and withintheir operational bounds.

d) Exercise internal data structure.

System Testing:

It consists of a series of tests to fully exercise acomputer based system.

It includes the following types of tests:

a) Recovery Testing.

b) Security Testing.

c) Stress Testing.


55/80

d) Performance Testing.

CODE TESTING

Code is tested by code reading and by adoptingany

strategy for testing code modules and program components.

The process of code reading is best done by reading thecode inside

out, starting with the innermost structure of the module.

For example we can adopt white box testing method andintegrating


56/80

testing method because this method can find many internalerrors.

PROJECT TESTING REPORT

After applying all testing methods such as

verification code reading analysis, White box testing andsystem

testing all helped us to ensure the proper functionality ofthe project

and removal of possible errors, since we are the developer ofthis

software we tested this software by sample data and triedto find out


57/80

errors and mistakes in the design and code of the software.

During the coding phase the code reading method helped usto

detect errors often not revealed by testing. As everyprogram have

bugs of some type in it. It is almost impossible to find everybug in a

commercial level program

As integrated software testing approach consist of several

stages

including module testing, program testing and acceptancetesting. In

module testing all the individual modules are tested andassessed as

working properly, they are combined so that program testingcan

begin.

User interfaces the systems security features, the ability todeal with

abnormal processing volume and the ability to recover fromsoftware

failures are tested. Acceptance testing as part of theintegrated

testing strategy was not conducted because we had todevelop


58/80

software not commercially but as a requirement of theuniversity. But

we had tried our best to ensure that the requirementsgathered

through the analysis phase must be met to a minimumextent, so that

it will help us to develop software in feature keep in mind,the main

procedures of commercial software.

USER TRAINING

With the burst of activity in end-user computing and the

appearance of new tools for computer professional,

training is becoming a major component ofimplementation. Whenever a system is acquired, which

often involve new hardware and software; both user and

computer professional generally need some type of

training. Often this is through classes give by developers

and through hands on leaning techniques.

For user training help documents, user guides and

manuals are also prepared

So end user can consult with these documents.

Training Approaches:


59/80

Two main categories of end-usertraining approaches are usually used:

- Instructor Led Methods

- Self Study Methods

1- Instructor Led Methods:

The most common instructorled

approach is the lecture, but this is seldom used by itself

in end-

user training. Discussion is often use along with lectureand

demonstration is also used specially when training userhow to

work, with new software. After the instructor

demonstrates the

task, users practice it own.

Developers may also give these classes.

2- Self Study Methods:

In recent years, increasingly more

user-training program have incorporated self-study

methods as part of the training process. Computer-based

training, tutorial and multimedia training systems are

examples of self-study methods. The users manual


60/80


61/80

CONCLUSIONSFinally we come to conclusion that the software testing

and evaluation phase helped a lot of to understand the basis

of software testing and its evaluation. During testing we

found that the software must be evaluated in such a way so

that it can operate in accordance with the requirements

gathered during system analysis. As every software is tested

with an intension so that all bugs and errors may have been

removed but software may present errors as they are

brought to production.

C H A P T E R

7


62/80

FUTURE EXTENSION

CONTENTS:

NEED OF EXTENSIONS

AREA NEEDING IMPROVEMENT

NEED FOR EXTENSIONS

As every man-made product is not complete in its own,

there is always a need for improvement. Because it is


63/80

our first project as a first effort, we have tried our best

to make available every functionality to the software.

But due to many constraints such as our programming

ability may not be up to the expertise need of a fully

functional system, or the technical abilities of the users,

or the time frame allowed to us to complete the project

would have not allowed us to enhance the capabilities of

the system. Also keeping in mind the idea of incremental

development paradigm (as adopted by the international

organizations) we preferred to design our project in

incremental stages. So that the users become aware of

the basic procedures of the system and would be able to

interact with more functional system, provided to them

in future.

AREAS NEEDING IMPROVEMENT

(FUTURE ENHANCEMENTS)

There are many areas in the software, which can be

enhanced or developed to further give the system an

extra ability to operate efficiently. Among several areas,

some of them are written below:

Database features can be introduced.

Design of the forms can be enhanced.


64/80

More front-end security and flexibility.

System can be converted into online System.

System can be developed with latest technology.

C H A P T E R

USER GUIDE

CONTENTS:

INTRODUCTION

TYPES OF HELP

USER MANUAL

8


65/80

INTRODUCTION

Almost every user of an interactive, computer-based

system requires help now and then.

In some cases, a simple question addressed to aknowledgeable colleague can do the trick. In others,

detailed research in a multivolume set of user manual

may do the only option. In many cases, however, modern

software provides online help facilities that enable a user

to get a question answered or resolve a problem without

leaving the interface.


66/80

TYPES OF HELP

Two different types of help facilities are encountered:

- Integrated

- Add-on

An integrated help facility is designed into the software

from the beginning. It is often context sensitive,

enabling the user to select form those topics that are

relevant to the actions currently being performed.

Obviously, this reduces the time required for the user to

obtain help and increase the friendliness of the

interface. For example the Tool-Tip-Text property of

controls in Microsoft Visual Basic6.0 enable the

developer to provide integrated help facilities for certain

actions, which require help for the user to operate the

system more accurately.


67/80

An add-on help facility is added to the software after thesystem

has been built. In many ways, it is really a users manualwith

limited query capabilities. The user may query aboutcertain

topics to find out related information.


68/80

USERS MANUAL OR USERS GUIDE:

Users manual or Users Guide can use graphical displays

or text to give information about the System. This

enables the user to understand the application more

frequently and he can interact with application more

easily.

Users manual or Users Guide of IMS is given as

Our product:The product we have launched is named as

INVENTORY MANAGEMENT SYSTEM OR IMS.

We have basically developed it for the organizations whichuse

manual system and face lots of difficulties in their business.

Working of System:Our developed

INVENTORY MANAGEMENT SYSTEM

is basically software which handles the information and dataof an

organization. It handles entities like Products, Customers,Suppliers,

Sale, Purchase, Customers order and Purchase order


69/80

and saves data about them. It also generates reports ondemand.

How To Operate:

To operate the system follows the steps:

a. Run IMS exe

b. After introduction screen login screen will be open

c. Enter the password, if password is correct then mainscreen of the system will appear this screen havethe buttons and menus of all the activities.

d. Click on desire buttons or menu.

e. Clicked task will open on screen, now you canperform your desired tasks.

REFERENCES

BEGINNING VISUAL BASIC 6BY PETER WRIGHTS

MASTERING IN VISUAL BASIC 6BY EVANGELOS PETROUSTSOS

MASTERING IN DATABASE IN VISUAL BASIC 6

BY EVANGELOS PETROUSTSOS

VISUAL BASIC 6BY C M ASLAM


70/80

MODERN DATABASE MANAGEMENTBY FRED R. MCFADD EN & JEFFERY A.HOFFER

APPENDICES


71/80

PRODUCT FORM


72/80

CUSTOMERS FORM


73/80

SUPPLIERS FORM


74/80

SALES FORM


75/80

PURCHASES FORM


76/80

PURCHASE ORDERS FORM


77/80

CUSTOMERS ORDER FORM


78/80

TRANSACTIONS FORM


79/80

RELATIONSHIP BETWEEN TABLES


80/80

Project Doc Omen Tat Ion

Documents

Transcript of Project Doc Omen Tat Ion