final inventory document.doc

7/27/2019 final inventory document.doc

1/26

1. INTRODUCTION

1.1 SYSTEM OVERVIEW

The main objectives of the project are to reduce manual work and avoiding the

human errors, and also avoid the time, which is used for storing and retrieving of data.

The sales and purchase order details, which are at present being done by manual process,

are to be computerized with the help of this project. All the details of the company are

maintained in a database and it is taken when in use. So this project substantially saves

time and effort. Retrieve a saved database from a disk and replace our existing database

with it. Use this backup in case of something happened to our existing database.

This system has been developed to overcome all the drawbacks in the Existing

System. Technology has developed at a very fast rate, but the most important aspect of

any system is the human know-how and the use of ideas to gear the computer. So that it

perform required task. This process is essentially what system development is all about.

This system is designed and developed according to the user requirements. It may be

better choice to select Sql-Server to maintain the database and Visual Basic. Net for front

end programming. Tables created will have fewer chances for corruption, whencompared to other databases .The. Net Technologies enable the application with

scalability and extended performance measurements for the industrial management.


2/26

1.2 ABOUT THE ORGANIZATION

DAFFODILLS INDIA, established in the year 2006 and it is located near

Edayarpalayam, Coimbatore.DAFFODILLS INDIA is the organization and the

development from based on the customer satisfaction and service towards the nation and

the clients in abroad.

Solutions are committed in providing innovative Software Solutions to its Clients and

recognize the importance of technology. DAFFODILLS INDIA seasoned software

Professional has Expertise in a wide range of technologies including, but limited to,

Web Technology

Client Server Technology

Database Design, Development and Administration

Customized Package Software implementation like Accounts

Development of System Software Low Level Programming

Server Side Programming

DAFFODILLS INDIA undertake Short Team and Long Term Projects on a contract

and regular basis with reputed Clients. DAFFODILLS INDIA goal is to clearly

understand their Clients need and provide them with real and lasting Solutions that meet

and exceed their Expectations.

The data generated has to be processed speedily and accurately to produce useful

formation that will help the organization in managing its business more efficiently and

effectively. This results in an increased need for the introduction of modern technology to

the transaction and events at source of origin and to make information available to the

user.


3/26

2. SYSTEM STUDY AND ANALYSIS

2.1 EXISTING SYSTEM

The present system is maintained in manual register. The production manager

prepares the production chart and evaluates the productivity. The register is maintained

for day-to-day activities, then posting is done to another register. In this system lot of

time is needed to prepare the maintain schedule

2.1.1 Drawbacks of the existing system:

In manual system large number of notebooks for each department is maintained.

Time taken is more and transaction is slow.

Absence of multitasking.

Modification or any correction is very difficult and errors occur frequently.

Manual works take more manpower.

In manual work followed by many functions hence calculations and transaction

details are difficult to maintain.

2.2 PROPOSED SYSTEM

The proposed system is trying to cover all the problems of existing system by

means of computerizing the entire work. The proposed system is the implementation of

VB.NET and SQL SERVER with many advanced features. VB.NET and SQL SERVER

are used to validate and connect the database.

To reduce the efforts and pains for the users and global accessing of data and data

source with the security system for the administrator and the organization planned to

computerize these overall activities.

The proposed system will give flexible and user-friendly solution for maintaining

all the details of purchase , sales and production. This system will reduce the time


4/26

consumption and the use of more manpower. It will maintain all datas properly and it can

be useful to achieve global standard quality and production in a user-friendly manner.

This system simplifies the task of the user by performing calculations

automatically. Sales information, report and personnel information are handled

efficiently by this system.

2.2.1 Advantages of the proposed system:

For Reducing man Power

For Reducing equipment costs, stock levels

For Peak load Processing

For Accuracy

For Better Customer Service

2.3 FEASIBILITY STUDY

Preliminary investigations examine project feasibility, the likelihood of the

system to meet the end users needs and its effective use of the available resources.

Three tests of feasibility those that are equally important are operational, technical and

economic feasibility.

2.3.1 Technical Feasibility

The goal of this project is to provide a complete intranet based web application

containing all the up to date information about the corporate meeting proceedings, task

assigned for the participants on the meetings and task status. The considerations for

technical analysis are associated with

Development risk :- The system elements are designed in such a way that the

essential functions and the performance of the system satisfies the constraints such as

responding to requests from irrespective of the number of locations (various departments)

of the users.


5/26

Resource availability: - The necessary hardware and software are available for the

system. In the system with available resources is enough to run the proposed system.

Technology: - The technology employed in this project supports the system in

such a way that it is easy for scheduling the group meetings, maintain the meeting

schedule and to keep track of the task status. It is user-friendly. Facility to invite for the

meeting and remind the task pending details using automatic mailing.

2.3.2 Operational Feasibility

In the proposed system its easy for us to monitor the employee performance, task

status and meeting schedule. The operation on the proposed system helps us to conduct

an effective scheduler for group meetings.

The proposed system is flexible to changes in the future so that a more operational

and useful system can be developed (ex. Web services). The proposed system is

beneficial as it meets the organizations operating requirements and it is user friendly.

Thus the system is operationally feasible.

2.3.3 Economic Feasibility

It is economically feasible because the corporate management provided all the

facilities and resources like hardware, software, Intranet and Internet used in this project.

It can be implemented in the Intranet, which incurs no cost. Since the system developed

is part of our curriculum so that development cost is minimal.

This system is useful for a corporate or for various departments or for any group

which is interested to organize the meetings effectively, thus save the time, money and

manpower.

2.3.4 Cost Estimation

Cost estimation models are mathematical algorithms or parametric equations usedto estimate the costs of a product or project. The results of the models are typically

necessary to obtain approval to proceed, and are factored into business plans, budgets,

and other financial planning and tracking mechanisms.


6/26

These algorithms were originally performed manually but now are almost

universally computerized. They may be standardized or proprietary, depending on the

type of business, product, or project in question. Simple models may use standard

spreadsheet products.

Models typically function through the input of parameters that describe the

attributes of the product or project in question, and possibly physical resource

requirements. The model then provides as output various resources requirements in cost

and time. Cost modeling practitioners often have the titles of cost estimators, cost

engineers, or parametric analysts.


7/26

3. DEVELOPMENT ENVIRONMENT

3.1 HARDWARE CONFIGURATION

Hardware specification of the system that is used in this project are,

Processor PENTIUM IV (1.8GHZ)

Memory 512 MB RAM

Cpu Clock Speed 400 MHZ

Hard disk 80 GB

Floppy Drive 1.44MB

Mouse Optical Mouse

Key board 108 Windows keyboard

Monitor 17 CRT

3.2 SOFTWARE CONFIGURATION

Software specification of the system that is used in this project is,

Operating System WINDOWS XP

Front end Dot Net 2005 (V.B)

Back end MICROSOFT SQL 7.0

3.3 PROGRAMMING ENVIRONMENT

3.3.1 VB.Net

The business sponsor is responsible for commissioning a software development

project, and usually owns the problem that the application is intended to solve. The role

of the business sponsor, and his expectations of software security, varies depending on

the nature of the business and the purpose of the software.

The business sponsor typically lacks technical expertise, but controls the development

budget and may support the implementation of software security for the followingreasons:

Security is a known requirement of the systems users.

Legislation dictates that the software must implement certain security measures.


8/26

Security features are necessary to compete with other products and look good on

marketing material.

Lacking formal requirements, the business sponsor will often have opinions to offer on

the importance and implementation of software security. These opinions may or may not

be in line with the real requirements of the project.

Business sponsors are often the biggest source of tension on a project when it

comes to the correct application of security. As you will see throughout this book,

software security can be applied only after a careful assessment of the application

requirements; however, the business sponsor often wants to bring the application into

production as quickly as possible, and this creates a tension between the careful

application of a planned security policy and the business requirement that the application

ship quickly.

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .NET Framework

is designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment whether object

code is stored and executed locally, executed locally but Internet-distributed, or executed

remotely.

To provide a code-execution environment that minimizes software deploymentand versioning conflicts.

To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on the

.NET Framework can integrate with any other code.

ADO.NET Overview


9/26

ADO.NET is an evolution of the ADO data access model that directly addresses

user requirements for developing scalable applications. It was designed specifically for

the web with scalability, statelessness, and XML in mind.

ADO.NET uses some ADO objects, such as the Connection and Command

objects, and also introduces new objects. Key new ADO.NET objects include the

DataSet, DataReader, and DataAdapter.The important distinction between this evolved

stage of ADO.NET and previous data architectures is that there exists an object -- the

DataSet -- that is separate and distinct from any data stores. Because of that, the DataSet

functions as a standalone entity. You can think of the DataSet as an always disconnected

recordset that knows nothing about the source or destination of the data it contains. Inside

a DataSet, much like in a database, there are tables, columns, relationships, constraints,

views, and so forth.

A DataAdapter is the object that connects to the database to fill the DataSet. Then,

it connects back to the database to update the data there, based on operations performed

while the DataSet held the data. In the past, data processing has been primarily

connection-based. Now, in an effort to make multi-tiered apps more efficient, data

processing is turning to a message-based approach that revolves around chunks of

information. At the center of this approach is the DataAdapter, which provides a bridge to

retrieve and save data between a DataSet and its source data store. It accomplishes this by

means of requests to the appropriate SQL commands made against the data store.

The XML-based DataSet object provides a consistent programming model that

works with all models of data storage: flat, relational, and hierarchical. It does this by

having no 'knowledge' of the source of its data, and by representing the data that it holds

as collections and data types. No matter what the source of the data within the DataSet is,

it is manipulated through the same set of standard APIs exposed through the DataSet and

its subordinate objects.

While the DataSet has no knowledge of the source of its data, the managed

provider has detailed and specific information. The role of the managed provider is to

connect, fill, and persist the DataSet to and from data stores.

The OLE DB and SQL Server .NET Data Providers (System.Data.OleDb and

System.Data.SqlClient) that are part of the .Net Framework provide four basic objects:


10/26

the Command, Connection, DataReader and DataAdapter. In the remaining sections of

this document, we'll walk through each part of the DataSet and the OLE DB/SQL

Server .NET Data Providers explaining what they are, and how to program against them.

The following sections will introduce you to some objects that have evolved, and some

that are new. These objects are:

Connections. For connection to and managing transactions against a database.

Commands. For issuing SQL commands against a database.

DataReaders. For reading a forward-only stream of data records from a SQL Server data

source.

DataSets. For storing, remoting and programming against flat data, XML data and

relational data.

DataAdapters. For pushing data into a DataSet, and reconciling data against a database.

Commands

Commands contain the information that is submitted to a database, and are

represented by provider-specific classes such as SQLCommand. A command can be a

stored procedure call, an UPDATE statement, or a statement that returns results. You can

also use input and output parameters, and return values as part of your command syntax.

The example below shows how to issue an INSERT statement against the Northwind

database.

DataReaders

The DataReader object is somewhat synonymous with a read-only/forward-only

cursor over data. The DataReader API supports flat as well as hierarchical data. A

DataReader object is returned after executing a command against a database. The format

of the returned DataReader object is different from a recordset. For example, you might

use the DataReader to show the results of a search list in a web page.

DataSets and DataAdapters

DataSets

The DataSet object is similar to the ADO Recordset object, but more powerful,

and with one other important distinction: the DataSet is always disconnected. The

DataSet object represents a cache of data, with database-like structures such as tables,

columns, relationships, and constraints. However, though a DataSet can and does behave


11/26

much like a database, it is important to remember that DataSet objects do not interact

directly with databases, or other source data. This allows the developer to work with a

programming model that is always consistent, regardless of where the source data resides.

Data coming from a database, an XML file, from code, or user input can all be

placed into DataSet objects. Then, as changes are made to the DataSet they can be

tracked and verified before updating the source data. The GetChanges method of the

DataSet object actually creates a second DatSet that contains only the changes to the data.

This DataSet is then used by a DataAdapter (or other objects) to update the original data

source.

The DataSet has many XML characteristics, including the ability to produce and

consume XML data and XML schemas. XML schemas can be used to describe schemas

interchanged via WebServices. In fact, a DataSet with a schema can actually be compiled

for type safety and statement completion.

DataAdapters (OLEDB/SQL)

The DataAdapter object works as a bridge between the DataSet and the source

data. Using the provider-specific SqlDataAdapter (along with its associated SqlCommand

and SqlConnection) can increase overall performance when working with a Microsoft

SQL Server databases. For other OLE DB-supported databases, you would use the

OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection

objects.

The DataAdapter object uses commands to update the data source after changes

have been made to the DataSet. Using the Fill method of the DataAdapter calls the

SELECT command; using the Update method calls the INSERT, UPDATE or DELETE

command for each changed row. You can explicitly set these commands in order to

control the statements used at runtime to

Resolve changes, including the use of stored procedures. For ad-hoc scenarios, a

Command Builder object can generate these at run-time based upon a select statement.

1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two

new objects, the DataSet and Data Adapter, are provided for these scenarios.


12/26

3. ADO.NET can be used to get data from a stream, or to store data in a cache for

updates.

4. There is a lot more information about ADO.NET in the documentation.

5. Remember, you can execute a command directly against the database in order to

do inserts, updates, and deletes. You don't need to first put data into a DataSet in order to

insert, update, or delete it.

6. Also, you can use a DataSet to bind to the data, move through the data, and

navigate data relationships

3.3.2 About SQL server

Enabling the information age is the slogan upon which oracle is founded, but it is

more than a slogan to engineers who dedicated their knowledge and experience to the

task of delivering this information with accuracy and speed. in this age of information,

just getting the data is not enough. The data is so vital to business must be dependable,

accurate and delivered as quickly as possible. Moreover, this is where oracle stands right.

The oracle the database has a logical layer and physical layer. The physical layer consists

of the files that reside on the disk; the components of the logical layer map the data to

these physical components.

Data base management system

A database system is a collection of integrated data that are to be stored together in a

single location. It enables the sharing of data among various users as and when required.

DBMS is software with capabilities to organize, manipulate and manage the data.

DBMS has evolved from hierarchical to network to relational model. Today it is most

widely accepted model .The relational model has three aspects.

Structures:

Structures are well-defined objects that store the data of the database. The structures and

the data confined with in them can be manipulated by operations.

Operations:

Operations are clearly defined actions that allow users to manipulate the data and

the structures of the database. The operations on a database must adhere to a predefined

set of integrity rules.


13/26

Integrity rules:

Integrity rules are the laws that govern, which operations are allowed on the data

structure of the database. Integrity rules protect the data and the structure of the database.

RDBMS offers benefit such as-Independence of physical data storage and logical data

base structure.

Easy access to all the data in the database.

Complete flexibility in the database design.

Reduce data storage over head and redundancy.

Relational database management:

The relational database management system uses only its relational capabilities to

manage the informations stored in its database.


14/26

4. SYSTEM DESIGN AND DEVELOPMENT

DESIGN PROCESS

Designing is the first activity for any system. It is the process of applying

various techniques and principles for the purpose of defining a system. There is various

type of designing. They are as follows

4.1 INPUT DESIGN

Input design is the method by which valid data are accepted from the user. This

part of the designing requires very careful attention. If the data going into the system is

incorrect, the processing and output will magnify these errors. Inaccurate input data arethe most common cause of error in data processing.

The input design is carried out such a way that the input screens are user friendly. The

goal of designing input is to make input data entry as easy and error free. Input screens

filter the invalid data from becoming an operational data at each entry phase. This is

achieved by providing proper checks and validations.

4.2 OUTPUT DESIGN

Designing computer should proceed in well thought out manner. The term output

means any information produced by the information system whether printed or displayed.

When analyst design computer out put they identified the specific output that is needed to

meet the requirement.

Computer is the most important source of information to the users. Output design

is a process that involves designing necessary outputs that have to be used by various

users according to requirements. Efficient intelligent output design should improve the

system relationship with the user and help in decision making. Since the reports are

directly required by the management for taking decision and to draw the conclusion must

be simple, descriptive and clear to the user. Options for outputs and forms are given in

the system menus.


15/26

4.3 CODE DESIGN

The Internal Documentation of the Source Code beings with the selection of

identifies names, continues with placement and composition of commenting and

concludes with the visual organization of the program. Unnecessarily long identifiers

provide a potential for error, hence they are avoided.

In the system design phase, code design has an important role. Each data item

must have a unique identity and must be related to other items of the same data type. The

code design offers

Uniqueness

Expansibility

Conciseness

Simplicity

Versatility

Portability

The code design makes corresponding input data into specify tables, with required

fields to it. The tables are viewed in the way of queries. The fields are set to the

corresponding area of the form. Every machine code and its activity are retrieved from

table. The code and the activity of the machine are differing from each machine. At the

run time code and activity are loaded with corresponding values.

4.4 DATABASE DESIGN

A database should provide integration, Integrity and a data independence table in

a database contains information pertaining to a specific entity. To maintain the tables in

an effective way, It should be normalized to ensure that the number of tables does no

exceed the optimum level unless it is mandatory.

To prevent unauthorized access, security measures have been provided. This may

prevent unauthorized persons using data that is private. The normalization techniques

have been used to design the table such that the use of all the tables is made easy.


16/26

The various relations between different tables, the number of fields in each table

and the type, width of each field were analyses. The names of the fields and tables where

so chosen that the users would not face any problem in identifying the table structure.

The various relations between different tables, the number of fields in each table

and the type, width of each field were analyses. The names of the fields and tables where

so chosen that the users would not face any problem in identifying the table structure.

A database is a collection of interrelated data stored with minimum redundancy to

serve many users quickly and efficiently. The general objective of database design is to

make the data access easy, inexpensive and flexible to the user

Database design is a process of modeling an enterprise in the real world. In fact, a

database itself is a model of the real world that contains selected information needed by

the enterprise. Many models and languagessome formally and mathematically defined,

some informal and intuitiveare used by designers.. The steps in the development of the

conceptual model are;

Data Analysis

Relational Identity

Graphical Representation

Design Process

Employee details, employee salary details, material issued, material inward ,

vendor list , purchase order , sales order, billing, quotation , company ,login , product ,

sales , stock and feedback and item sale offer are the tables maintained in the database.


17/26

5. TESTING AND IMPLEMENTATION

System development is done in many different ways. It forms the basis of all

methodologies. The approach that is being implemented for this project is structured

approach. Structured programming, structured analysis, structured design are thetechnique for structured approach. This is implemented for this system development.

Structured programming is one that begins with one beginning and one ending,

and each step in the program execution consists of one of the three programming

constructs. One of the concepts of structured programming is implemented in this project.

(i.e.) top down approach is implemented. Through this complex programming is divided

into hierarchy of modules.

Two main principles of structured design are the program module should be

designed so they are loosely coupled or highly cohesive out of which highly cohesive is

being used.

Structured analysis defines system-processing requirements by identifying by all

of the events that will cause a system to react in someway. Each event leads to a different

system activity. These activities are then taken and data flow diagram is created showing

the processing details including inputs and outputs.

The most important development activity is preparation of computer program

needed for the system. The system flowcharts, input charts, output charts, are transferred

into program. In each stage of preparation, the program has been tested and errors are

corrected if any. All accuracy measures falls into account while testing the program.

While preparing the program, to avoid the error message, if one button is

functioning for particular record might be formatted, as other has been enabled.The

change over method is the process where the existing manual system is to be replaced by

the new computerized system.

The following changes are made during the change over plan, Change over plan

has to be made carefully, so as to minimize the problem that may arise from human

errors. The activities to be performed during the change over plan have to be identified

and the responsibilities should be assigned to individuals in the organizations.


18/26

5.1 TESTING

Software testing is the last phase of the software development cycle. Testing is

very important for the success of a system. System testing makes a logical assumption

that if all parts of the system are correct, then the goal has been achieved.

The testing should be done at the end of all development steps. Even though the

final testing and verification are inevitable for better life and functionality of the

software.

The major phases in testing are design of test plan, setting up test case and test

candidate and test procedure, testing and correction. This is a cycle process and the

software will circulate through all the steps till it attains the required quality.

The testing is carried in the following steps,

1. Unit Testing

2. Validation Testing

3. System Testing

4. Acceptance Testing

5. Regression Testing

6. Database Testing

5.2 Unit Testing

Unit testing refers testing of all the individual programs. This is sometimes calledas program testing. This test should be carried out during programming stage in order to

find the errors in coding and logic for each program in each module. Unit test focuses

verification effort on the smallest unit of software design module. In this project, the user

must fill each field otherwise the user to enter values.

5.3 Validation Testing

Valid and invalid data should be created and the program should be made to process

this data to catch errors. When the user of each module wants to enter into the page by

the login page using the use rid and password .If the user gives the wrong password or

use rid then the information is provided to the user like you must enter user id and

password.


19/26

Here the inputs given by the user are validated. That is password validation,

format of date are correct, textbox validation. Changes that need to be done after result of

this testing.

Input Testing

Here system is tested with all variable combination of inputs. User may type data

in situations like entering password, numerical details etc. The system is tested with

all the cases and it responded with appropriate error messages.

Output Testing

Here the output is tested to view whether that the screen is what which is desired.

It is also checked whether it is to the satisfaction of the user. Changes that need to

be done can be done after the result is seen.

5.4 . System Testing

System testing is used to test the entire system (Integration of all the modules). It

also tests to find the discrepancies between the system and the original objective, current

specification and system documentation. The entire system is checked to correct

deviation to achieve correctness.

5.5. Acceptance Teasing

Acceptance testing is performed on a collection of business functions in a

production environment and after the completion of functional testing. This is the final

stage in the testing process before the system is accepted for operational use. This testing

should be done with original data and with the presence of the users. This test confirms

the system ready for production.

5.6 Regression Testing

Regression testing refers to the retesting components / functionality of the system

to ensure that they function properly even after and change has been made to parts of the

system. As detects are discovered in a component, modification are made to correct them.

5.7. Database Testing

The purpose of database testing is to determine how well the databases are meets

requirements. This is an ongoing process because no database is static. When table is

created, a mirror of the same should be created and stored. The original one should be left


20/26

alone and its mirror images go through the various tests. This process continues until

changes can be implemented in the original table.

5.8 Implementation

Implementation is the phase where the developed component is installed in the

working place. The operation of the software was monitored and the results were

recorded. Implementation is the stage of the project where the theoretical design is turned

into a working system. This involves careful planning, investigation of the current system

and its constrains on implementation, design of methods to achieve the change over and

evaluation of change over methods.

The problems encountered are converting files training users, creating accurate

files and verifying print outs for integrity. The objective is to put the tested system into

operation while holding costs, risks and personnel irritation to a minimum. It involves

creating computer compactable files, training the operational staff and installing

terminals and hardware.

Maintenance activities begin where conversion leaves off. Maintenance is handled

by the same planning and control used in a project. Maintenance can be classified as

corrective, adaptive or perceptive. Corrective measures means repairing process of

performance failures or making changes because of previously in corrected problems orfalse assumption. Adaptive Maintenance means changing the program functions.

Perceptive Maintenance means enhancing the performance or modifying the programs to

respond to the users addition or changing needs.

The implementation view of software requirements presents the real world

manifestation of processing functions and information structures. In some cases, physical

representation is developed as the first step in software design. The analyst must

recognize the constraints imposed by the pre defined system elements and consider the

implementation view of the function and information when such view is appropriate.


21/26

6. CONCLUSION AND FUTURE ENHANCEMENT

6.1 Conclusion

The Inventory Management System is successfully designed and developed to

fulfilling the necessary requirements, as identified in the requirements analysis phase,

such as the system is very much user friendly, form level validation and field level

validation are performing very efficiently.

This project is successfully designed and developed to fulfilling the necessary

requirements, as identified in the requirements analysis phase, such as the system is very

much user friendly, form level validation and field level validation are performing very

efficiently.

The new computerized system was found to be much faster and reliable and user

friendly then the existing system, the system has been designed and developed step by

step and tested successfully. It eliminates the human error that are likely to creep in the

kind of working in which a bulk quantity of data and calculations as to be processed.

The system results in quick retrieval of information that is very vital for the

progress any organization. Cost is minimized in case of stationary. Burden of manual

work is reduced as whenever transaction takes place, there is a no need to record it in

many places manually.


22/26

6.2 Future Enhancement

The software has been developed in such a way that it can accept modifications

and further changes. The software is very user friendly and future any changes can be

done easily.

Software restructuring is carried out. Software restructuring modifies source code

in an effort to make it amenable to future changes. In general, restructuring does not

modify the over all program architecture. It tends to focus on the design details of

individual modules and on local data structure defined within modules.


23/26

7. BIBLIOGRAPHY & REFERENCES

I. BOOKS

Elias.M.Award, System Analysis and Design Galgotia Publication Pvt.Ltd. 1991

Roger.S.Pressman, Software Engineering McGraw-Hill International Editions, 1991

Gary cornell & Jonathan Morrison, Programming VB.NET Pares publishers

Matt.j.Crounch, VB.NET programming Pearson Education, 2003 Edition.

Steven Holzner , Visual Basic.NET Programming

WEBSITES

www.programheaven.com www.programerheaven.com www.codeproject.com www.programheaven.com www.programerheaven.com www.codeproject.com www.SpeechRecognization.com www.MSDN.com www.google.com WWW.gotdotnet.com WWW.awprofessional.com WWW.dotnet247.com


24/26

APPENDICES

DATA FLOW DIAGRAM

dispatch

Purchase

Payment

Add/Less

Payment

Check Payment

Billing

Info

Prepare

Billing

Sales

Info

Purchase

Info

Item

Info

Purchase

Item

Supplier

Info

P_ Order

InfoOrder

ItemItem

Info

Item

Info

Check

Item

Order

ItemSalesOrder

Payment

Billing

Verify

Item

CUSTOMER

ORDER

ITEM

S_ Order

Item Table

Generate

Sales

Payment

Purchas

e

Raw

Meteria

lOrder

P_ Order Table

Su_ Table

Purchase

Updatin

g

Item

Delivered

ItemCUSTOMER

SUPPLIER

A

A

B

C

CC

Billing

BP_ Table

S_ Table

Producti

on


25/26

Customer Places

Order

Cust_id

cname

cadd

Prod_idP_nophoneno

quanity

check

s

StockSales to

make

sPayment

sales_id

cname

quantity

P_no

Cust_id

pname

Prod_id

quantityPnam

e

pname

Prod_id

Cust_i

d

paydate

amt


26/26

final inventory document.doc

Documents