SALES AND ACCOUNTING SOFTWARE.

Synopsis

Submitted by

1.

2.

Title Of The Project:-

“ Sales and Inventory Management System ”

Project Category:-

“ Windows Based Application Software ”

DEFINITION OF THE PROBLEM

The problem with the existing system is that it is totally manual. In the

existing system, to retrieve or update stock information the employee has to

manually do so by looking with in stock ledgers. Any transaction like credit or

debit, inventory addition, sales report,billing information,tax calculation,

everything has to be maintained manually by the employee. This is a very

tiresome and time consuming method to follow. Management of the whole

Sales and Inventory system is done in a very tedious manner like , the

purchasing party records are maintained manually in ledgers and each time

any insertion or updation takes place, the employee has to manually write

those changes in ledgers which is not only time consuming but also difficult to

handle. Handling thousands of transactions is annoying and in case of

searching any particular transaction record most of the times is a big head ache

for the employee. As every type of processing is done manually so even for the

very simple information employees have to get in contact with each other

physically.

THEORIETICAL BACKGROUND

“Sales and Inventory Management system is a fully computerized system that

will ensure timely availability of information for decision making at a click of

mouse. The proposed system is user friendly i.e. it provides graphical user

interface that is easy to use and interact with even by a layman.

Computerization of the proposed system ensures the secrecy and security of

information by providing password for authorized users.

The proposed system consists following modules:

1. Stock management

2. Sales Management

3. Billing and Report generation

4. Search & Query Section

a. Stock Search

b. Employee Query

c. Purchasing Party Search

5. Report Section

a. Sales Report

b. Tax Report

c. Credit and Debit report

6. System Administrator Section

a. Login Manager

b. Change Login

c. Create user

OBJECTIVE AND SCOPE

Computer science and Information Technology has brought revolution in all

aspects of daily life. While on the one hand it has made things easy, secure,

credible, fast and seamless; it has, on the other hand, opened new avenues and

streams for the financialcommunity. The proposed system “Sales and Inventory

Management System” has been also developed by keeping in view the problem

with manual system and all the above mentioned aspects. This topic is chosen

because of better Management edge. This system will improve the decision

making capability and managerial skills. This automation project will provides

a real time response with the click of mouse. The reliability of the proposed

system will also increase with increase in, portability and maintainability so

that the Quality Application Program will be developed and implemented.

The main objective of the proposed system is to automate the existing

manual system and to increase its overall efficiency with decrease in the

response time. The information retrieval from automated databases becomes

fast as well as efficient. Sorting or indexing large amount of information

becomes possible with the click of mouse and searching of a particular record

becomes fast and easier along with efficient utilization of memory..

Updating records is not a problem and also crosschecking records in

the proposed computerized system can be easily done. Mathematical,

accounting and logical errors would get automatically rectified in the proposed

system. Different reports can be generated with the click of a mouse. This

system increases the management’s response to the queries. Implementation of

Relational Database Management system (RDBMS), a backend tool in the

proposed system reduces data redundancy and utilizes memory more efficiently

as it reduces memory wastage and increases system efficiency.

This software package is developed with the intention of making the

management familiar as how the computers can be used for the efficient and

error free office environment which is very necessary for the smooth working

of any establishment.

The objectives of the proposed system can be summarized in following points:

Fast retrieval of related information or records.

Searching of particular record will become easier.

Versatile Report generation with desired report format.

Report generation of various sections becomes fast and accurate.

To provide safe and secure data backup and recovery.

To provide customer details in an integrated manner so that all his information

is connected thus reducing redundant data.

Reduces paper work.

Less response time.

Efficient utilization of memory.

Reduces data redundancy.

Efficient utilization of resources and information as assert to a proposed

system.

Maintaining information brevity, accuracy, timeliness etc.

Automatic updating of records whenever any record added or deleted

from the database the database records retains their order in sorted

manner.

Automatic creation of database and its tables.

Error free working environment.

Generating reports becomes fast, easier and efficient.

Validation of data is strictly there.

METHODOLOGY USED

The methodology used for developing this system is Prototyping Model.

Accepted (SRS)

Requirement Gathering

Quick Design

Review/Modify Requirements Build Prototype

Sales and Inventory Management

Coding

Testing

This model is used here because detailed input, output requirements are not present in

the beginning, and thus it is felt that a prototyping model will be more suitable for

development. In this model, we will create a quick design and then invite user to test

the developed system and refine requirements if any. Thus, the process for

development will be iterative.

HARDWARE REQUIRED:

Since the application is based on “TWO TIER ARCHITECTURE”, the

following hardware is required at:

1)Processor Pentium IV or higher.

2)512 MB of RAM or more.

3)80GB Hard Disk or more.

4) Monitor.

5) Keyboard & Mouse.

SOFTWARE REQUIRED:

a) Operating systems: - “WIN-XP” / “WIN-98” / “WIN-2000 SERVER or

ADVANCE SERVER” / “WIN-2003 SERVER or ADVANCE SERVER”,

b) Microsoft .Net Framework 3.5

c) Microsoft C#

d) Microsoft Visual Studio 2008

e) Microsoft SQL Server 2005.

TESTING TECHNOLOGIES USED: -

The methodology that will be used for testing in the development of this proposed

system is a combination of “UNIT TESTING” and “INTEGRATION TESTING”.

“INTEGRATION TESTING” further includes both the “TOP-DOWN

INTEGRATION” and the “BOTTOM-UP INTEGRATION”. When we talk about

the “UNIT TESTING” we have to take care of the each and every individual module.

This proposed system will be tested basically on this methodology. During the

application of the “INTEGRATION TESTING” initially we will opt for

“BOTTOM-UP INTEGRATION” as all the smallest modules of the proposed

system are tested in order to achieve higher degree of performance. The whole system

will be divided into “Logical Clusters” on the basis of the functionality. Hence

making the clusters and then perform testing is the basic criteria under “BOTTOM-UP

TESTING” which is being applied to the testing phase during the development of this

system. In the “TOP-DOWN INTEGRATION” testing is being started from the main

module i.e. the “Control Program” or the “Main Program”. The various features of

testing conclude to be the following:-

I. Initially we will opt for the “UNIT TESTING” and the various types of

activities that are performed under it are as follows: -

a. Evaluation of the Testing Domain.

b. Defining desired test zones.

c. Prioritization of Test data.

d. Initialization & Verification of “UNIT TESTING” Plan.

e. Performing “UNIT TESTING”.

f. Removing encountered errors.

g. Retesting of misbehaving functions encountered.

h. Final Test Review.

i. Migrating to next test technology (if all errors removed).

II. The next option available out of the adopted testing techniques is

“INTEGRATION TESTING” and the various activities involved in it are as

follows:-

a. Framing Testing Development Domain.

b. Dividing Test Code into clusters.

c. Application of “Bottom Up” Testing & removing Errors (if any).

d. Shifting Towards “Top Down” Testing & eliminating Errors

encountered (if any).

e. Considering Final Test output.

f. Delivering Validated Product.

.