CONTENTS

1. Synopsis
2. System Analysis
 CFD
 DFD
3. Fundamental requirement
 I/O Requirement
 Process Requirement
 Storage Requirement
 Control Requirement
4. System Design
 I/O Design
 Process Design
 Database Design
5. Coding and Testing
10. Implementation Issue
11. User manual
12. Future Enhancement
13. Conclusion
14. Bibliography
 OBJECTIVES OF THE PROJECT

Objective:
A computer shop management system sells various types of hardware and software
accessories such as Laptop, Antivirus and Keyboard etc. It’s very hard for the shopkeeper
to remember their cost price and in what price these items to be sold. As the market goes
up and down for various products daily, so there should be some proper medium through
which prices of these items can be changed frequently without any problem. There are
many customers who will make their payment online, so there should be a medium to
take their credit card as input and reduce exact amount from their account. This computer
shop management system will enable its user’s keep their customers report secure, so that
next time these customers when arrive to their shop, do not have to enter their details
again. Buyers will also able to select products options while purchasing through
computer screen and can make their payment from that particular screen and pick up their
materials which they have selected at the pickup center within the shop.

Existing System:

Existing computer shop management system only having the potential to perform
processing task for limited section. In this system shopkeeper have to enter customer’s
report every time whenever they visited their shop. There was no any medium to find the
customers record using any unique key or customers id. If the records of any items is to
be revised, then search operation is performed to find the item and make updation. Stock
report and making query on daily selling reports was not possible. It was not possible by
the shopkeeper to track which salesman was responsible to sell particular product and
what price and time. The present system was not able to make balance sheet, only the
daily transaction was saved in the file, which was sended to the charted accountant office
to prepare balance sheet which is again not secure with respect to the customer’s details.
As product identification was done only using the particular product serial number, thus
problem in identifying which product has been solved.
Proposed System:

In this proposed computer shop management system all the requirements has been added
which makes the computer shopkeeper to perform all their tasks by their own such as
knowing details of daily transactions, preparing balance sheet and knowing stock details
of each products under their shop by just one click. Each customers will have a unique
bill id, customer id and product id along with the description of product such as model
number, name, number of quantities, price of each product, total price along with the date
and time. Each working member within the shop will have unique id which will help the
shopkeeper to know who has made how much transaction in their shop. Customers will
get a secure gateway method by which they can make their payment using their credit
and debit card. To make bills and perform other transaction within the shop each working
member will have unique id and password. Using these id, system will able to identify
which person is having the admin responsibility and which person has assigned which
task that he or she can performed.

HARDWARE & SOFTWARE REQUIREMENT

(A) HARDWARE REQUIREMENT-

An Intel based central processing unit capable of running any sort of windows
operating system such as Pentium based workstation.

 Minimum 64 MB RAM (128 MB Desirable) at server.

 Minimum 60 MB of free disk space for files.
 A CD Rom drive
 Minimum 48 MB of RAM at workstation.
 VGA 15” color monitor for workstation.

(B) SOFTWARE REQUIREMENT-

The software requirements are as follows.

 Windows 98 or Above
 C editor
 Microsoft word
 INTRODUCTION

Computer Shop system involves maintaining of account related information. This

requires grater accuracy, speed that is why the proposed system is the computerization of
the existing system. The computerization system does the job monitoring the record in
easy and effective manner as stated below:

 Efficiently handles customer, account related data.

 Monitor transaction and makes related information.
 Keeps records of customer account detail and other information.
 Generates reports.

Account system involved maintaining data related different customer and his transaction.
This required greater accuracy, speed that is why the proposed system is the
computerization of the existing system. The computerized system does the job of the
monitoring the information easy and effective manner.

.
 DISCRIPTION OF EXISTING SYSTEM

In the ongoing process, the records are maintained manually and the paper work is more.

Entering Record-
Entry of each record is done manually each time the record is done
Manually .each time the record is maintained on paper and it maximizes the maintenance
of additional files.

Searching the record-

Due to absence of unique identification of person the searching of record takes much
time. And in the wastage of time increase.

Deleting the Record-

In the current system there is no concept of deleting record.

Modification of Records-
If any modification is required it is done directly on the documents being preserved in
correspondence to account information.

Sorting of Records-
All the record of Account is maintained on papers. And if in any case we want to see any
particular record we have to search a lot of pages.
 PROBLEMS

1. As the work is carried out manually so the requirement of the maintenance of

record.
2. The system is handled manually so it requires a lot of time to maintain the
records.
3. The current system is not reliable as manually recording often leads to mistakes
and no accurate result are found.
4. No feasibility
5. As huge data is to be maintaining, so it’s not easy to maintain the huge data
without any error, which in turn makes the less efficient.
 DISCRIPTION OF PRAPOSED SYSTEM

To avoid the limitation of current system it’s necessary to design and develop a new
system which have the following benefit and the existing system.

(a)Everything is automated which reduce the risk factor.

(b)Flexibility in generating of information.

(c)Quick retrieved and maintenance of data.

(d)Highly accurate.

(e)User satisfaction.
 FEASIBILITY STUDY

Feasibility study is a report directed management. It evaluates the impact of the proposed
changes in the area(s) in question. The report is a formal document for management, brief
enough and sufficiently, non technical to be understandable, yet detailed enough to
provide the basis for system design.

Technical feasibility

Technical feasibility centers around the existing system (hardware, software, etc) into
what it can sort the proposed addition.
 Present system Vs. Candidate System

CRITERIA PRESENT SYSTEM CANDIDATE SYSTEM

System accuracy 75% 90%

Growth potential Average Good
Response time Average Good
User friendly No Yes

Economical Feasibility

Economical analysis in the most frequently used method for evaluation the
effectiveness of a candidate system. This procedure is to determine the benefits and
saving that are expected from a candidate system and compare it with cost.
Present system Vs. Candidate System

CRITERIA PRESENT SYSTEM CANDIDATE SYSTEM

System Performance Only one task can be One computer system

performed at a time perform more then one task
User training 15 days or more In a minimum time
System Operation Fair Very Good

Operational Feasibility

Employees of any organization are inherently resistant to changes because they believe
that it will be very difficult to adapt in the new system. Computers have been to facilitate
changes. it is well known that computerization has something to do with transfers,
retraining and changes in employee job status.
Present system Vs. Candidate System

CRITERIA PRESENT SYSTEM CANDIDATE SYSTEM

Operation time The present system takes It takes less time in
more time for displaying comparison to present
procedures system.
Reliability It is less reliable It is more reliable.
Accuracy 75% 95%
Retrieval It takes few minutes It takes few seconds
Feasibility Study
 A study was undertaken to compare the existing manual system with the new
proposed system to be developed.

Economic Feasibility

The Bank Account System will considerably reduce the manpower and to time
necessary to manage the process and generate the report for the following imperative
action to be taken place on the basis of the reports. The proposed system will require only
the Person to manage the Contacts. The new system will generate the reports
automatically optimizing the efforts and time required.
Thus proposed system is economically feasible because it is being developed
with out having to incur the heavy development costs and it will considerably reduce time
and effort required managing the present system.

Technical Feasibility

The proposed system, which is to be developed, will be installed at Personal

Computer. Since we have to also install the computer systems with the configuration
given below:-
System Configuration
 One PC with any version above Windows98
 Turbo C editor
 Switches to connect the computer’s Together
So we have necessary Hardware and Software supporting the implementation
of the proposed system. There is however a need of the one technical person to
effectively manage the resource in the computer. Since there are no technical constraints
the project is technically feasible.
Behavioral Feasibility

Since the new system is going to solve the difficulties that come in the manual
system of the procurement, reports in handwritten. So proposed system is completely
feasible is terms of the behavior.

Project Plan
The Objective of the software project planning is to provide a framework that
enables an owner to make reasonable estimate of the resources, cost and schedule. The
project leader is responsible for designing the system precisely according the requirement
specified by the customer. He is also responsible for maintenance of the system for
certain period of time. Since cost of maintenance is much higher than cost of developing
system. Thus to reduce developing and maintenance cost, to provide the system in
predefine time proper planning of system is necessary.
For this project, we used the Waterfall Model. The methodology has the following
phases:
 Initial Investigation
The most crucial phase of managing system projects is planning to launch a
system investigation, we need a master plan detailing the steps to be taken, the people
to be questioned, and outcome expected. The initial investigation has the objective of
determining whether the user’s request has potential merits the major steps are
defining user requirements, studying the present system and defining the performance
expected by the candidate system to meet user requirements. The first step in the
system development life cycle is the identification of need. There may be a user
request to change, improve or enhance an existing system. The initial investigation is
one way of handling these needs. The objective is to determine whether the request is
valid and feasible before a recommendation is reached to do nothing, improve or
modify the existing system, are to build a new one.
Thus for an effective maintenance, paper follow-up and handling of the
data resulting from different information in records, it felt necessary to develop a
Bank account System so that monitoring and maintenance of record data could be
done.
 INFORMATION GATHERING

A key parts of the system analysis is gathering information about the present system. The
developer must know that information to gather, where to find it, how to collect it, and
what to make of it.
The proper use of tools for gathering information is the key to successful analysis.
The tools are

 The Traditional Interview

 Questionnaires
 On-site Observation

The major objective of on-site observation is to get as close as possible to the real system.
In the interest to get more potential information we personally approached the senior
officials of the concerned department.
Required data are collected as forms.

 Analysis phase

It includes the study of the problem and creation of the System Requirement
Specification (SRS) Document. The most crucial phase of the managing system projects
is analysis. It requires the people to be questioned, study of manual system if it exits, and
on the site observations. Analysis is necessary to understand the problem, the software
system is to solve
The analysis model is concise, precise abstraction of what the desired system
must do, not how it will done. Thus, main emphasis in analysis phase is on identifying
what is needed from system. The objective is to determine whether the request is valid
and feasible before a recommendation is reach to do nothing , improve or modify the
existing system, or to building a new one. Thus Bank Account System is automation of
the existing manual system.
 An SRS establishes the basis for agreement between the client and the
developer on what the software will do. An SRS provides references for validation of the
final product. A high quality SRS is prerequisite to high quality software, which reduces
overall development cost of system.

 Design Phase

It begins when the analysis phase and thus requirements documents, for the
software to be developed has been prepared. The objective of the design process is to be
to produce a model or representation of the system, which is used to build the system.
The design of the system is essentially a blueprint or plan for solution for system.
Design process for software system has two levels:
1. System Design
2. Object Design

The System Design is the high-level strategy for solving the problem and building a
solution. System design includes decisions about the organization of the system into
subsystem, the allocation of the subsystem to hardware and software component and
major conceptual and policy decisions that for the detailed design.
The Object Design phase determines the full definitions of the classes and the
association used in the implementations as well as interfaces and algorithms of the
methods used to implement operations.

 Implementation of the project required the design of the system developed in

the design phase of the project to be coded and implemented. The modules
defines in the design phase are coded in ‘C’ language. Integration phase
requires the integration of the various modules developed in the project
implementation phases. In implementation, it is important to follow good software
engineering practice so that tracing to the design is straightforward and so that the
 implemented system remains flexible and extensible, thus it reduce cost of
maintenance and enhancement of the system.

 Testing Phase includes the conformation of the acceptance criteria set down in
the system requirements specification document. The development of the software
system involved a series of activities where opportunities for injection of human
fallibilities are enormous. Error may begin occur at every stage of the system
development where the objectives may be erroneously or imperfectly specified as
well as later design and development stage. Software testing is critical element of
software quality assurance and represents the review of specification, design and
coding. Testing can’t show the absences of defects, it can only show that software
defects are present.

Packaging and Deployment phase comes after completion of the software.

Application packaging is the act of creating a package that can install our application
onto user’s computer. A package consists of the files that contain compressed project
files and any other necessary files the user needs to install and run the application. These
files may include setup programs secondary files, or other needed files. The additional
files vary based on the type of packaging. One can create two kind of packaging –
standard package or internet packages. If we plan to distribute on disk, floppy or via a
network share, we should create a standard package for our application. If we plan to
distribute via an internet or internet site, we should create an Internet package
 CONTEXT FLOW DIAGRAM

COMPUTER
CUSTOMER CUSTOMER
SHOP

SYSTEM
TESTING TECHNIQUES

The development of software systems involves a series of production activities where

opportunities for injection of human fallibilities are enormous. Errors may begin to occur
at every inception of the process where the objectives may be erroneously or imperfectly
specified as well as later design and development stages. Because of human inability to
perform and communicate with perfection, software development is accompanied by
quality assurance activity.
Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding.
The increasing visibility of software as a system element and attendant “costs” associated
with a software failure is motivating forces for well planned, through testing.

Software Testing Fundamentals

During earlier definition and development phases, the engineer attempts to build
software from a concept to tangible implementations. Now comes the testing. The
engineer creates a series of test cases that are intended to demolish the software has
been built. In fact testing is the one step in the software engineering process that could be
viewed as destructive rather than constructive.
Testing required that the developer discard preconceived notion of the “correctness “of
the software just developed and overcome a conflict of the interest that occurs when error
are uncovered.
 TESTING OBJECTIVES

A numbers of rules that can serve well as testing objectives:

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 high probabilities of finding an as yet
undiscovered error.
3. A successful test is one that uncovers an as yet undiscovered error.

Our objective is to design test systematically uncover different classes of errors and do so
with minimum amount of time and effort. Data collected as testing is conducted provide a
good indication of software reliability and some indication of software quality as a whole.
But there is one thing that testing can not do.
Testing can not show the absence of defects, it can only show that software defects are
present.

Test information flow

Information flow for testing follows the pattern described in the figure:
Two classes of input are provided:
1. A software configuration that includes a software requirement specification, a
design specification, and Source code
2. A test configuration that include a Test Plane and Procedure, any testing tools that
are to be used, and test cases and there expected results.
Software
Configuration

Test Results Evolutio

n
Errors
Expected
Testin Results
g Debug
Model

Error Data Rate

Corrections
Test Configuration
Reliabilit Predicted
y
Reliability
 USER MANUAL

There is no use of mouse to handle the software .The keyboard is meant for providing
any sort of inputs. There is only vertical menu with key access.

Vertical menu includes the following under their respective headings.

1. ADD ACCOUNT: the personal directory file.

2. DELETE ACCOUNT: Delete Customer Account details.

3. MODIFY ACCOUNT: This modifies the details of Account holder.

4. DISPLAY ACCOUNT INFORMATION: This displays the customer

Debit & Credit Account

5. SEARCH: find the customer information.

6. EXIT: close Bank account system.

 SCOPE OF FUTURE ENHANCEMENT

The application certainly has same striking advantage over manual system. There will be
no paper work as possible and the information will be updated as it changes.
 It is automation of Telephone directory system.
 With this system one can generate the report of the address.
 It secures the database of Telephone directory system from the unauthorized
person.
 The operator does not require any previous training because of its user
friendliness the operator is free from any technicality of the backend processing,
that is how database is maintained.
 If the process of the working changes in future then the alteration in the system
will be done easily and will not cause in the mismanaging of data.
 Furthermore with its implementation very large amount of data will be secure and
editing and addition or deletion of data is done very easily.
 In future according to the user’s requirement it can be updated so that to reach the
user specification.
 CONCLUSION

The application certainly has some striking feature over manual system. User queries
have become quite accurate and efficient. Lot of paper work has been eliminated. Future
modification and enhancements have become quite easier now in comparison to the
previous manual system.
Last but one of the most important advantages of the banking system is that, through this
system the whole procedure will take too less time in comparison of the manual system.
No doubt BAS will be helpful for institutes in all procedure, which will be monitoring
through Account. At the first step BAS will only be installed in the bank .The main
advantage of BAS is that, it will become a powerful tool in establishment of better system
in comparison of the existing system. It helps to protect the system from the corruption.
After installation of BAS in the bank, there is a greater possibility of stabilization a clear
and fair system, which will be accurate, update and fast.
There is no doubt that there always remains some scope of improvement. The important
thing is that the system developed should be flexible to accommodate any future
enhancements. This system can be used to provide some enhancement without rewriting
of existing code.
 BIBLIOGRAPHY

 THINKING IN C BY BRUCE ECKEL

 SYSTEM ANALYSIS AND DESIGN BY ELIAS AWAD
 INTERNET COLLECTION