Shoppers Management System2

8/3/2019 Shoppers Management System2

1/60


2/60

Shoppers Management System

Person using this software can maintain records of daily transaction in

a paperless form. User can also search the details of the facilities that

to be avail in the wedding at faster and efficient way.

2. PROBLEM SELECTION

Page 2


3/60


One of the most difficult tasks of system analysis is developing a clear,

in-depth understanding of the problem being investigated, without which

it becomes impossible to specify the requirements for a new project with

any accuracy. Several questions should be posed for this.

Some of those may be:

What is the problem?

How complex is it?

What are its likely causes?

What are possible solutions to the problem?

The earlier system used in organisation for storing the information of the

customers was either manual or semi-automated . If we talk about manual

and semi-automated system, Manual work is very time consuming and prone

to errors. The information of the customers records were recorded manually

on papers or entered on to computer without systematic approach. Existing

system has many drawbacks as being manual or semi-automated, it is prone to

errors. Generally Hardware shops have large database. The maintaining of

customers records is totally manual. It is very time consuming and tedious

job. If user wants to update or delete the existing details of a items search is

done manually in that case. As the system is manual so to get required

information is a hectic job. If any old data or information is to be fetched then

its a great problem for the user to get the information in short time of span ,as

to get the information from files is no so easy. The user has to wait for listgeneration until he gets the required information. Even after the information

fetched may be wrong .As in Manual system silly mistakes are always

possible .Whole system is so time consuming that user feel its a burden to do

searching and sorting. In existing system there is no facility for the user to

delete duplicate records, to generate list of information available and no

search criteria, as everything has to be done manually. So they are not totally

reliable and any record can be misplaced easily as all the record is stored onthe paper.

Page 3


4/60


At present all the activities of the Hardware Shop like adding, modifying and

deleting of new records were done manually. Cumulative like total amount

collected, numbers of customers paying bill etc .Are also maintained manually

in the registers for the transactions being made.

3. PROJECT MONITORING SYSTEM

Page 4


5/60


Objective of the software is to simplify the bill generation system of the

HARDWARE SHOP MANAGEMENTSYSTEM

Using computers

3.1 Existing system

The existing system Hardware Shop Management is basically manual or semi

automated. The record of different customers is kept by the directory and is

recorded manually in the register maintained in the company or entered on the

computer without systematic approach. Existing system has many drawbacks

as being manual or semi-automated; it is prone to errors. If a user wants to

enquire anything regarding the customers, adding or searching items and then

he has to wait as the system is manual so as to get the required information is

a hectic job. If any record is mismatched then a user has to take full

responsibility.

Limitation of existing system :

The earlier experiences have shown that manual monitoring of customers

enquire about their status, Often fails to achieve the desired enquiry, mainly

because of the following reasons:-

> Difficult to keep track of each & every record of the customers.

> Manual preparation of customers lists takes very long time.

> Information anytime & anywhere is not possible

> Lot of paper work

> Manual procedure of providing information is not reliable.

> Maintaining database

> Record entry

> Searching & updating records

Page 5


6/60


OBSERVATION & DRAWBACK OF EXISTING SYSTEM

After observing the existing system very deeply we find the followingdrawbacks and loopholes in the older system.

Every task that is performed in the Hardware shop was totally manual

therefore it was time consuming, as well as there is a chance of human errors in

calculations like repair charges, instalments etc. Hence the system suffers on

Accuracy front.

Since every task is manual and a lot of paperwork was performed it proved to

be an extra cost of papers and other office stationary regarding it on the company. Along with extra expenditure on papers a storage space is also required to

store files and records.

System lacks very badly in security areas and there is no safety assurance of

secret information. Since everything is in human hands access of data by an

unauthorized person may be possible this is one of the most harmful drawback.

Only single copy of items is maintained so in case of any damage or loss to

data it will be impossible to recover it. Services as well as Responses are slow and this will be a major point

regarding the competition in the market.

Historic records are not available on a minutes notice if required by customer

or management staff.

This old system is unable to provide a clear and detailed view regarding

performance of company, separate departments and employed staff.

Procedure of ordering spare parts from different vendors are slow as detailsare to be searched in huge pile of papers.

Page 6


7/60


3.2 PROPOSED SYSTEM

The proposed system is automated .It has the facility for one to make

enquiries for a particular items .Hardware Shop Management System performfunctions like adding , displaying , modifying , deleting items.

This system is developed with a prime motto to provide a managerial,

analytical and controlling tool in hands of authorities and managers of the

hardware shop management system .It aims to provide them with solutions

that not only easy and manages the operator workload, but also gives them a

power to keep record of every minute detail involved.

Some of the benefits of the proposed system over existing system:-

1. Less need of manpower-very little manpower is requires here to handle

the customers as the entire thing is automated.

2. Faster and accurate generation of billsnow every report is available

within few seconds and earlier it was very time consuming.

3. Keeping information- keeping customers, items information is very

easy.

4. Online services: - adding, searching, updating, deleting, displaying.

Page 7


8/60


FEATURES OF PROPOSED SYSTEM:-

Facilities Details : The new proposed system stores and maintains the entire books details

automatically and accurately. It remembers all the records and can immediately produces

the required reports at any time without any errors.

2. Calculations : The new proposed system calculates the bill that is to be charged from

client. These calculations are done at very fast speed and also accurately.

1. Registers : There is no need of keeping and maintaining books and clients register manually. It remembers each and every record and we can get detail report of any

facilities at any time.

2. Speed : The new proposed system is very fast with 100% accuracy and saves time.

3. Manpower : The new proposed system needs less manpower. Less people can do

the large work.

4. SYSTEM STUDY

Page 8


9/60


This project will in RDBMS category because it will handle the huge data of

items and the details of the items in file and file will be related to each other

to produce required Information.

Hardware shop management system is basically a menu driven program. This

kind of format is designed considering the user requirements. This is to

provide an easy and faster method of operation to the user. The basic menu of

the program contains five options according to the user needs. The functions

and purpose of each option is explained below.

1. BUY PRODUCT :-This option will allow to purchase the product

available in the Mall.

2. LIST OF ITEMS : This option will shows the list of items to purchase

the product .This option also provides very easy interface, due to which the

customer can have various transactions easily.

3. EDITING : This option will edit the items of The Mall: - for example-

changing item name or changing the price of the item.

4. BILL GENERATED: This option is for displaying all the Bills that are

generated. All the Bills contain the current date at which the bill was created. The

user can perform following tasks:

1. Add part: This allow user to add new Hardware part that he wish to sold

from now on.

2. Modify part: This allow user to modify the existing items that he is selling.

3. Delete part: This allow user to delete the existing items that he is not

willing to sell from now on.

4. Exit: - This option allow user to exit from fourth option and hence return to

the main menu.

5. EXIT: - With the help of this option the user can exit from the main menu.

Validation check while taking input data from the user.

Page 9


10/60


1. Size of the field : Field size is checked while taking input in the

item price field. The price should be in the range specified.

2. Before making any updating: It has been checked that particular record is present in the file or not.

3. Before making any Deletions: It has been checked that user should

delete only those items that are displayed in the item list.

4.1 Feasibility Study

Feasibility is the determination of whether or not the project at hand isworthwhile. The process followed in making this determination is called a

feasibility study.

Page 10


11/60


4.2 TYPES OF FEASIBILITIES

4.2.1 Economic Feasibility:

The economic feasibility study (EFS) should demonstrate the net benefit of

the proposed application in light of the benefits and costs to the client.

COMPANIES are the main clients of this software. EFS is sent to the client

i.e. COMPANIES for approval and acknowledgement before moving to next

stage of system development process. The EFS is composed of a cover letter,

a business case, and analytical worksheets. In addition, supporting

documentation can provide additional detail on the elements and may be

included in the EFS if necessary to support the other components of the FFS.

For very small applications and certain expansions to the existing processes,

the business case and analytical information may be presented in the cover

letter.

There isnt an order or magnitude rule of thumb that applies generally.

The alternative dismissal/selection process depends on other things, such as,

how well an alternative meets the project purpose and need, and the totality of environmental impacts. What if an alternative that cost 4 or 5 times more than

other alternatives but in turn had 4 to 5 times less environmental impacts?

Depending on the type of resources and impacts, you might not to be able to

rule that alternative out on the basis of dollar cost alone.

Conversely, an alternative that was much cheaper than others but with

unacceptable impacts might be considered unacceptable depending on the

resources, impacts and others values the alternative brings with it.

The feasibility study is one of the most misunderstood aspects of developing a

location based leisure facility. Yet, it is perhaps the most important step, as

mistakes at this early stage can permanently handicap the projects

performance, perhaps fatality. A good feasibility study is more that just a set

of financial projections. Done properly, it becomes the market-driven strategic

plan that is the road map for all subsequent decisions. As much as answering

the question Is a project feasible? a good study also addresses the question

Page 11


12/60


of what is most feasible and what should all its attributes be to assure

maximum success.

4.2.2 Technical Feasibility:

This is concerned with specifying equipment and software that will

successfully satisfy the user requirement. The technical needs of the system

may vary considerably, but might include:

A. The facility to produce outputs in a given time.

B. Response time under certain conditions.

C. Ability to process a certain volume of transactions at a particular speed.

D. Facility to communicate data to distant location.

After examining technical feasibility, we give more importance to the

configuration of the system than actual make of hardware. The configurationgives the complete picture about the systems requirements: Ten to twelve

workstations are required, these units should be interconnected through LAN so

that they could operate and communicate smoothly. They should have enough

speeds of input and output to achieve a particular quality of printing.

4.2.3 Behavioural Feasibility :

It is mainly related to human organizational and political aspects. The points

Page 12


13/60


to be considered are:

What changes will be brought with the system?

What organizational structures are disturbed?

What new skills will be required?

Do the existing staff members have these skills?

If not, can they be trained in due course of time?

Generally project will not be rejected simply because of operational

Infeasibility but such considerations are likely to critically affect the nature

and scope of the eventual recommendations.

For operational feasibility study we appointed a small group of people who are familiar with

information system techniques, who understand the parts of the business that are relevant to

the project and are skilled in system analysis and design process.

STEPS IN FEASIBILTY ANALYSIS:

Feasibility analysis involves eight steps:-

1. Form a project team and appoint a project leader.

2. Prepare a system flowchart.

3. Enumerate potential candidate system.

4. Describe and identify characteristics of candidate system.

5. Determine and evaluate performance and cost effectiveness of each

candidate system.

6. Weight system performance and cost date.

7. Select the best candidate system.

8. Prepare and report final project directive to management.

5. SYSTEM ANALYSIS

Page 13


14/60


System analysis is the first step toward making the program, under this system

analysis the programming team is made understood about the requirements

from the user end and those requirements are being analysed that whether the

requirements of the user can be meet by using some simple methods:

Drawing the context Diagram :-> In this portion, simple model is created

which specifies the boundaries and interfaces of the proposed system with

external world.

Development of a prototype :-> In this portion, the prototype (working

model) of the project is made by the programmers with basic content to show

how the program would look and work lie when its made then that assent tothe user to take its advices for changes that he would wanted.

Model the requirements :-> Under this portion, the incorrect inconsistent

and missing requirements are found by the means of graphical tools such as

ER Diagrams, and Data dictionaries etc.

Finalize the requirements :-> After modelling the requirements, working of

system becomes cleared. Flow of data among the modules has been

understood .Now the requirements are finalized and being placed in a

prescribed format.

5.1 System Requirement Specifications

Hardware Requirement Specifications:

Page 14


15/60


Page 15

Requirement Server

Processor PC with Pentium III-class

processor, 1GHz or above

RAM Windows 2000 Professional,Windows XP Home 96MB;

Windows 2000 server 192MB

Windows XP Professional &

Window

Server 2003192 MB

Recommended :

128 MB for 2000 Professional,

256 MB for 2000 Server

160 MB for XP Home

256MB for XP Professional &Window

Video 1023 x 768, 256 colours

Recommended : High colour 16- bit

Mouse Microsoft Mouse or compatible

pointing devicePrinter Required


16/60


Software Requirement Specifications :

The computer on which you install your software should meet the following

system requirements.

Page 16

Windows 2000 Professional -96 MB;

Windows 2000 Server -192 MB;

Windows XP Home -96 MB;

Windows XP Professional & Windows Server 2003 192 MB

Table-5.1.1


17/60


Performance has not been turned for minimum system configuring. Increasing

your RAM above the recommended system configuration will increase your

performance, specifically when running multiple applications.

Table-5.1.2

5.2 ER DIAGRAM

Page 17

Quantity

ItemcodeAge

Customername


18/60


Fig-5.2.1

6. SYSTEM DESIGN

System functions

The HARDWARE SHOP MANAGEMENT SYSTEM will help in storing,

issuing, maintaining Items information.

The insertion, deletion, searching, modifying, adding all items from a system

can also be done in this system.

Page 18

Customer Purchase

Hardware

Pay

Bills

SexPart name

Partheading

Cost/price

Part code

Itemcost

Totalamount

Bill noDate of billgeneration

Quantity

Partname


19/60


System attributes

All these stages are taken into consideration while working on the initial

stages of the project-

1. Ease to use

2. Response time

3. Platforms

Software design is the first of three technical activities-Design, Code,Generation and Test That are required to build and verify the software. Each

activity transforms information in a manner that ultimately results in validated

computer software.

The Design task produces a data design, an agricultural design, an interface

design and component design.

The design of an information system produces the details that clearly describe

how a system will meet the requirements identified during system analysis.

The system design process is not step by step adherence of clear procedures

and guidelines .when I started working on system design, I face different type

of problems; many of these are due to constraints imposed by the user or

limitation of hardware and software available. Sometime it was quite difficult

to enumerate the complexity of the problems and solution thereof, since the

variety of likely problems is so great and no solutions are exactly similar

however the following consideration I kept in mind during design phase.

Design objective

The primary objective of the design is to deliver the requirements as specified

in the feasibility report. These are the some of the objective, which were kept

in mind.

Page 19


20/60


Practicality: The system is quite stable and can be operated by the people

with average intelligence and basic computer knowledge.

Efficiency : It has been tried to involve accuracy, timeliness and

comprehensiveness of the system output.

Cost : It is desirable to aim for the system with a minimum cost subject to the

condition that it must satisfy the entire requirements.

Flexibility : It has been tried that the system should be modifiable depending

on the changing needs of the user. Such modifications should not entail

extensive reconstructing or recreation of software. It should also be portable to

different computers systems.

Security : This is very important aspect, which was followed in this designing

phase and tries to covers the area of hardware reliability, fallback procedures

and physical security of data .

Page 20


21/60


Constraint

These are the following constraints:

Hardware: The existing hardware will obviously affect the system

design.

Software: The available software (operating system, utilities,

language, etc.) in the market will constrain the design.

Budget: The budget allocated for the project will affect the scope and depth of

design.

Time scale: The new system may be required by a particular time (e.g. thestart of a financial year). This may put a constraint on the designer to find the

best design interface with other systems

Page 21


22/60


6.1 Data Flow Diagram

Data flow diagrams are commonly used during problem analysis. Data flow

diagrams are quite general and not limited to problem analysis for software

requirement specification.

A DFD shows the flow of data through a system. It views a system a function

that transforms the input into desired outputs. Any complex system does not perform this transformation into a single step and a data will typically undergo

a series of transformation before it becomes an output. The DFD aims to

capture the transformations that take place within a system to the input data so

that eventually the output data is produced.

The agent that performs the transformation of data from one state to another is

called a process. So, a DFD shows the movement of data through the different

transformations or processes in the system. Named circle show the processes

and data named arrows entering or leaving the bubbles represent flows

Process activity

The rectangle represents a source and sinks and is a net originator or

consumer of data. A source or sink is typically outside the main system of

study.

Page 22


23/60


DATA FLOW DIAGRAM

O LEVEL DFD

Request List of Items

Fig-6.1.1

Page 23

Shoppers

stop

Product

Cash memo

Customer


24/60


DFD FOR MAIN MENU

Processing

DETAIL

Processing

Fig-6.1.2

DFD FOR MODIFY

Page 24

3. DISPLAY

CASH MEMOAND PRINT IT.

1. ENTERSUITABLE DATA

2. HOW MUCH

QUATITY YOUWANT TO BUY.

Main menu


25/60


PROCESSING

DETAIL

PROCESSING

Fig-6.1.3

DFD FOR DELETE

Page 25

1.Entersuitablechoice.

2. What itemyou want tomodify.

3. Item ismodified.

Modify


26/60


PROCESSING

DETAIL

PROCESSING

Fig-6.1.4

6.2 FLOWCHART

Main menu

Page 26

2. What itemyou want todelete.

3. Item isdeleted.

Delete

1.Entersuitablechoice.


27/60


For adding a Item

Page 27

Start

1. PURCHASE

2. LIST OF ITEMS

3. EDITING

4. BILL GENERATED

5. QUIT

7 exit

If case =1

If case= 2

If

C a s e= 3If case=4If case=5

Stop

Purchase

View items

Edit items

Bill display

Exit

Start

Enter a Item

Itemadd

ed?

Save Item

Do uwantto add

moreItems?

Item not added

End

FIG 6.2.1


28/60


For viewing all Items

Page 28

Start

Enter name of theitem

Itemmatched?

Displayitem

Do u

wanttoviewmore?records?

Item not found

FIG 6.2.2


29/60


For modifying a item

Page 29

Start

Enter a item

Itemmatched?

Item matched

Do uwant tomodify

moreitems?

Item not matched

end

FIG 6.2.3


30/60


For deleting a item

Page 30

Start

Enter a item

Is theitemcorrect

Itemdeleted

Do uwant todeletemoreitems?

Item not matched

end

FIG 6.2.4


31/60


32/60


33/60


34/60


35/60


6.3.4 ACCOUNT ATTRIBUTE

Page 35

S.NO ATTRIBUTE NAME DATA TYPE SIZE DECRIPTION

1 *T_PARTNAME CHAR 1 TAKE PART NAME

2 T_QTY FLOAT 4 TAKE QUANTITY

3 T_PRICE FLOAT 4 TAKE PRICE

4 CODE INT 2 RETURN CODE

5 BILLNO INT 2 RETURN BILLNO

6 LENGTH INT 2 LENGTH

7 DATE INT 2 DATE OF ISSUE

8 PRICE FLOAT 4 RETURN PRICE

9 QUANTITY FLOAT 4 RETURN QUANTITY

10 NAME CHAR 30 RETURN NAME


36/60


7.SYSTEM TESTING AND IMPLEMENTATION

TESTING STRATEGIES

Testing is the filter to catch defect before they are discovered by the

customer. Every time customer runs the program, it generates the test case.

We want our test cases to find the defect first. Software development is a

human activity with huge potential for errors. Testing helps release helps

assure quality and save money.

TESTING OBJECT:-

Purpose for testing is:-

To find error. To demonstrate that software function appears to be working

according to the specifications.

To reduce the number of errors detected by customer.

To have confidence in the software system.

TESTING STEPS:-

We start testing each individual new components and work our way out.

Unit test

Integration test

High order test

Customer acceptance testing

Different testing techniques are used at different time in the process.

Page 36

ABLE


37/60


TYPE OF TESTING

SYSTEM TESTING

System testing of software or hardware is testing conducted on a complete,

integrated system to evaluate the system's compliance with its specified

requirements. System testing falls within the scope of black box testing, and

as such, should require no knowledge of the inner design of the code or logic.

As a rule, system testing takes, as its input, all of the "integrated" software

components that have successfully passed integration testing and also the

software system itself integrated with any applicable hardware system(s). The

purpose of integration testing is to detect any inconsistencies between the

software units that are integrated together (called assemblages) or between

any of the assemblages and the hardware. System testing is a more limiting

type of testing; it seeks to detect defects both within the "inter-assemblages"and also within the system as a whole.

Testing the whole system

System testing is performed on the entire system in the context of a FunctionalRequirement Specification(s) (FRS) and/or a System Requirement

Specification (SRS). System testing is an investigatory testing phase, where

the focus is to have almost a destructive attitude [citation needed] and tests not

only the design, but also the behaviour and even the believed expectations of

the customer. It is also intended to test up to and beyond the bounds defined in

the software/hardware requirements specification(s).

Page 37


38/60


UNIT TESTING

In computer programming, unit testing is a software verification and

validation method where the programmer gains confidence that individualunits of source code are fit for use. A unit is the smallest testable part of an

application. In procedural programming a unit may be an individual program,

function, procedure, etc., while in object-oriented programming, the smallest

unit is a method, which may belong to a base/super class, abstract class or

derived/child class.

Unit testing can be done by something as simple as stepping through code in a

debugger; modern applications include the use of a test framework such as x-Unit.

8. DOCUMENTATION

Page 38


39/60


MAIN MENU

BUY PRODUCT MENU

Page 39


40/60


Purchase by viewing list

Page 40


41/60


LIST OF PRODUCT MENU

Page 41


42/60


EDITING MENU

Page 42


43/60


Product to be added

Page 43


44/60


ADD RECORD

Page 44


45/60


Product added

Page 45


46/60


MODIFY RECORD

Page 46


47/60


Record to be modified

Page 47


48/60


Record Modified

Page 48


49/60


List of products modified

Page 49


50/60


Delete product

Page 50


51/60


Record to be deleted

Page 51


52/60


To delete record

Page 52


53/60


Record deleted

Page 53


54/60


List of products after deletion

Page 54


55/60


BILL GENERATED MENU

Page 55


56/60


9. CONCLUSION

This project is designed to meet the requirement of a Custom Duty Department. It

has been developed in C++ and the database has been built in C++ binary file only

Page 56


57/60


, keeping in mind the specification of the system.

For designing the system we have used simple data flow diagrams.Overall the

project teachers us the essential skill like:

1. Using system analysis and design techniques like data flow diagram in

2. designing the system.

3. Understanding programming logic and language in C++.

10. SCOPE OF PROJECT

In the proposed system we computerized and automated all the tasks that are

earlier done manually and required paperwork. In this proposed system every

item will be kept on electronic storage medium rather than on paper files.

Page 57


58/60


Inputs are to be taken by different forms on Graphical User Interface that is

handled by front end. Also the proposed system will give instant report

regarding the customer, inventory, sales and past transactions. Proposedsystem will be efficient enough to generate informative reports for the help of

management whenever required.

Project will do the items registration, bill calculation, Stock transaction entry.

The new system is also equipped with the alarming system about inventory

shortages and facility to provide quick view and instant info retrieval.

The following will be the functionality of the proposed system described in

brief

1) Automation of reception work with easy to use interface.

2) Electronic storage of data in form of records.

3) Centralized management reporting and decision support.

4) Accurate and timely control of different tasks.

5) Adequate reporting to each division.

11. References

Books are often referred to as mans best friend while making a project a basic

framework. While enhances clarity of expression and provides a better

understanding of the subjects. They serve as a guide to the overall development of

the project.

Page 58


59/60


60/60


5) EOF: End of File

Documents

Shoppers Management System2