(BCSP – 064)

On
RETAIL SHOP MANAGEMENT SYSTEM
For
BCA –5th SEM
Submitted in the Partial fulfillment of the
Requirement for the Award of the Degree.
Submitted By

SUJATA KUMARI
ENROLMENT NO: 147996635
PROGRAMME- BCA
STUDY CENTER CODE- 0592(p)
GUIDE NAME- MRS. KALPANA KUMARI MCA FROM IGNOU
FRONT END- JAVA & BACK END- ORACLE

Page 1
 Table of Contents
Topics Pg.no
1. TITLE OF THE PROJECT 3

2. INTRODUCTION TO THE CLIENT 4

3. OBJECTIVE OF THE PROJECT 5

4. INPUT TO THE PROJECT 6

5. OUTPUT OF THE PROJECT 7

6. PROJECT CATEGORY 8-10

7. TOOLS/ PLATFORM 11

8. PRELIMINARY INVESTIGATION 12-14

9. ANALYSIS 15

10. DATA FLOW DIAGRAM[DFD] 16-22

11. ENTITY RELATIONSHIP DIAGRAM[ERD] 23

12. PROJECT SCHEDULING TECHNIQUE -GANTT CHART 24

13. PROCESS LOGIC 25-26

14. DATA STRUCTURE 27-30

15. INDUSTRY/CLIENT INFORMATION 31

17. FUTURE SCOPE/ENHANCEMENT OF THE PROJECT 32

Page 2
 TITLE OF THE PROJECT

‘RETAIL SHOP
MANAGEMENT
SYSTEM’
FOR
D. LAL & SONS , Main Market
Begusarai

Page 3
 INTRODUCTION TO THE CLIENT

D LAL & SONSis a Retailer shop of general stores products , located at Main Market,

Begusarai.The owner of the shop is Mr. K.K. LAL.The day to day transaction of this

retailer is very large because it deals with a large number of sales and purchase of general

stores products viz. grocery items, stationary, cosmetics, home used products, food

products, packed foods, dry fruits, daily use products in our life. The D LAL & SONS

delivers these products in all purchaser of begusarai. Gradually, the number of customers

are increasing day by day, and as a result the shop intention is to open different branches

at different city. As a result, in near future, it became a popular retailer shop or supplier

of dedicated items. It handles selling and purchasing, Staff Management, Billing of goods

sales & Purchase, Item Information, Customer Information, Customer Order entry details

and wide range of related Information etc.

Page 4
 Objectives of the Project
For partial fulfillment of Bachelor In Computer Applications from IGNOU.
Patna, this project was under taken to justify the knowledge gained in this three years
course and to prove the ability to develop real life projects in different fields.
Thesoftware that I developed is named “RETAIL SHOP
MANAGEMENT SYSTEM” has been prepared depicting the overall functioning of the
system and the features provided by the software. After this I referred the various books
on SQL, Reports, and ORACLE and with the knowledge.
Again started designing the database and generated codes for the various modules
keeping in mind the distinctive and features to be incorporated in the concerned
application software, With the experience gained I was able to diversify my knowledge
and skills in database technologies, designing user friendly interfaces, incorporating
portability features and utilizing features of efficient programming.
The software developed “RETAIL SHOP MANAGEMENT SYSTEM”
computerizes the entire functioning of the saidRetailer shop department of the “D LAL
& SONSfor Departmental Store”. It enables to keep the information of all customer,
Sale Purchase number and Facilities.
There are given several facilities, incentive as well. Thus to keep record of their
Retailer shop and other information, Retailer shop needs a software. My software is
created to fulfill their requirement.
After the closing of Retailer shop, per day Sale Purchase and others report is also
generated on the basis of database. This enables the manager to search a record to take
placed in a very short span to time. After the day end the transaction data is send to
another table names through trigger. The clearance report is also generated. The system
also allows the old records placed in the case diaries, which take up huge storage space
and their permanency are doubtful, to be transferred into electronic/digital form and
stored on hard disks/CD-ROM.
 To keep information of permanent customer.
 Supplier Information maintenance.
 Order Tracking of given items to the supplier.
 To keep information of facilities provided to customer.
 To keep the information of products of different company.
 To maintain information about Day by Day Selling of items.
 To maintain information about Purchasing of Different products
 Storing and Retrieval of Order’s Details.
 Generate Invoice.

Page 5
 Input of the Project
 User_id is entered to find the detailed information of general stores products
Detail

 PId is entered to find the details registered products under the retailer shop.

 Scode is entered to find the staff details working in retailer shop.

 CustCode is entered to maintain Customer Info.

 Order No is entered to maintain customer’s Orders .

 SaleId is maintained to view the sale details.

 Number of Total quantity of product purchased by the customer.

 Billing has been generated on the basis of BillId.

Page 6
 Output of the Project
 Detailed general stores products information.

 Balance general stores products report of that retailer shop.

 Supplier details.

 Income/Expense details.

 The transaction activity done by the Customers daily or monthly.

 Customer detailed information.

 Detailed enquiry information.

 Detailed of the Worker information.

 Generate Bill for concerned dealing.

 Generation of Report of Day to Day Transactions of all regards.

Page 7
 Project category
JAVA
Java is a programming language originally developed by James Gosling at Sun
Microsystems (which has since merged into Oracle Corporation) and released in 1995 as a
core component of Sun Microsystems' Java platform. The language derives much of its
syntax from C and C++, but it has fewer low-level facilities than either of them. Java
applications are typically compiled to bytecode (class file) that can run on any Java virtual
machine (JVM) regardless of computer architecture. Java is a general-purpose, concurrent,
class-based, object-oriented language that is specifically designed to have as few
implementation dependencies as possible. It is intended to let application developers "write
once, run anywhere" (WORA), meaning that code that runs on one platform does not
need to be recompiled to run on another. Java is as of 2012 one of the most popular
programming languages in use, particularly for client-server web applications.
Principles
James Gosling, the creator of Java

There were five primary goals in the creation of the Java language:

1. It should be "simple, object-oriented and familiar"

2. It should be "robust and secure"
3. It should be "architecture-neutral and portable"
4. It should execute with "high performance"
5. It should be "interpreted, threaded, and dynamic"

Versions

Major release versions of Java:

 JDK 1.0
 JDK 1.1
 J2SE 1.2
 J2SE 1.3
 J2SE 1.4
 J2SE 5.0
 Java SE 6
 Java SE 7

RDBMS
A relational database management system (RDBMS) is a database management system
(DBMS) that is based on the relational model as introduced by E. F. Codd, of IBM's San
Jose Research Laboratory. Most popular databases currently in use are based on the
relational database model.
Relational database is a new way of thinking about how data should be structured and
stored . The key to this type of database in understanding the relationship within data ,
then structuring the information base to reflect those relationship. In this way an

Page 8
information base would be built. That could stand the test of time. The goal of relational
database is to build a database in which only the data changes, not the structure itself. The
old way of doing this type if work is called the traditional approach.
A relational database is a database that is perceived by the user as the collection of
time varying normalized relation of assorted degrees. In other words, In relational database
the no. of rows and columns and contents may change with time due to modification,
deletion, insertions. Relational operators like union, intersection, Cartesian product etc.
can be used to operate on the database . Since each relation in the database is independent,
there are no relationship between relations. A relational database is a collection of relations
of two-dimensional tables. A relation does not contain any duplicate tuples.

Features Of RDBMS :
· Database is represented as a collection of relations. The relational database eliminated
all parent child relationships and instead represented all data in the database as simple
tuple or attributes table of data values.
· Each table is independent and there is no structure or any relationship between tables.
· The user interfaces of RDBMS are non-procedural.
Normalization
The logical design of the database, including the tables and the relationships between them, is the
core of an optimized relational database. A good logical database design can lay the foundation for
optimal database and application performance. A poor logical database can impair the
performance of the entire system.
A logical database design involves using formal methods to separate the data into multiple, related
tables. A greater number of narrow tables(with fewer columns)is characteristics of a database. A
few wide tables(with more columns)is characteristics of an un normalized database.
Some of the benefits of Normalization include:
 Faster sorting and index creation.
 A large number of clustered indexes.
 Narrower and more compact indexes.
 Fewer indexes per table, which improves the performance of INSERT,UPDATE and
DELETE statements.
 Fewer NULL values and less opportunity for inconsistency, which increase database
compactness.
Reasonable normalization often includes few regularly executed queries that use
joins involving more than four tables. Sometimes the logical database design is already fixed
and total redesign is not feasible. If the database is accessed through stored procedures, this
schema change could take place without affecting applications. It not, it might be possible
to create a view that hides the schema change applications. There are three main Normal
forms, each with increasing level of normalization:-

First Normal Form(1 NF):- A table is in 1NF if it does not contain repeating groups.

Second Normal Form(2 NF):-A table is in 2NF when all its non key attributes are fully
dependent on the key attributes.

Third Normal Form(3 NF):-A table is in 3NF if all the non key attribute of the table are
independent of all other non key fields of the same table.

Page 9
 There are additional normalization levels, such as Boyce codd Normal form(BCNF),
Fourth Normal Form(4NF) and Fifth Normal Form(5NF).

ORACLE
The Oracle Database (commonly referred to as Oracle RDBMS or simply as
Oracle) is an object-relational database management system (ORDBMS) produced
and marketed by Oracle Corporation.
Database Schema

Most Oracle database installations traditionally came with a default schema called SCOTT. After
the installation process has set up the sample tables, the user can log into the database with the
username scott and the password tiger. The name of the SCOTT schema originated with Bruce
Scott, one of the first employees at Oracle (then Software Development Laboratories), who had a
cat named Tiger.

Oracle Corporation has de-emphasized the use of the SCOTT schema, as it uses few of the
features of the more recent releases of Oracle. Most recent examples supplied by Oracle
Corporation reference the default HR or OE schemas.

Features Of Oracle:
 Ease of installation and use
 Scalability
 Data warehousing
 System Integration with other server software
 Flexibility
 Security
 Robustness

Other default schemas include:

 SYS (essential core database structures and utilities)

 SYSTEM (additional core database structures and utilities, and privileged account)
 OUTLN (utilized to store metadata for stored outlines for stable query-optimizer execution
plans.
 BI, IX, HR, OE, PM, and SH (expanded sample schemas containing more data and structures
than the older SCOTT schema).

Page
10
 Tools/ Platforms to be used

Hardware Requirements
 Pentium IV Processor
 512 MB RAM
 80 GB Hard Disk
 15’’ Monitor
 Keyboard
 Mouse
 Printer

Software Requirements
Operating system : Windows XP SP2

RDBMS(BACK END) : Oracle 10g

Front-end : JAVA

IDE : NetBean 6.1

Page
11
 PRELIMINARY INVESTIGATION

Requirement Analysis
Study of the Existing System.
The Process of transaction has been studied at D LAL & SONS by me and
documented. The Analysis shows following that
(i) No Standard Computerized System was so far developed.
(ii) Each day and Month Receipt is Generated Manually and stock
details are entered in the manual hard copy.
(iii) It is required to store infoabout stocks, workers, General stores
products, orders , Customers, supplier etc.
(iv) Data entered should be cross verified for correctness on line so that
wastage of stationary reduced.
(v) Printing of Bill Form will be done through HP Laser Printers A4
and A3 Size both on Pre-Printed Stationary.
(vi) It was required that System shall be easy and simple in use.
(vii) Data Entry process shall be simple and fast.
(viii) System shall have been required for self verifiable for claim of
customer regarding data filled in order and delivery entry Form.
(ix) Security is measure concern. There is a requirement to maintain
security from Admin Panel for total work.

Feasibility Study:-
a) Operational Feasibility:- TheProposed system is operationally
feasible. The users of organization are capable to work with the
changed environment. They can easily work with the system after
taking trainings.

b) Technical Feasibility:- The system are technically feasible

because the available hardware and software components can support
the proposed system. There is no extra accommodation is required to
run the system.
c) Economic Feasibility:- After covering the requirements and
components, the cost-benefits are analyzed deeply and after extensive
study the system will provide high benefit to the organization as
compared to prior transaction environment.

Page
12
 Overview of Proposed System
On the basis of analysis of system and requirement of automation process
System has been divided into three parts viz. Data Entry & Processing and
invoice Printing.

Software Requirement Specification (SRS).

Software Requirement Specification of RETAIL SHOP MANAGEMENT
SYSTEM
1.0 Introduction
1.1 Purpose – The Purpose of this document is to describe the
external requirement for the computerization of given
requirements as a part of D LAL & SONS, on the basis of
information provided by the Computer Cell and other
Official, It also describes the interface for the system. The
basic purpose of the project is to automate each
functionalities of said retailer shop in mode, so that one can
do one’s transaction from any part of the world.
1.2 Scope – This document is the only one that describes the
requirement of the system. It is meant for use by the
developers and will be the basis for validating the final
delivered system. Any changes made to the requirement in
the future will have to go through a formal change approval
process.
1.3 Definition, Acronym & Abbreviation. – Not Applicable.
1.4 SoftwareconsultancyResponsibility[NICESOFTECH]
(a) Developing the system.
(b) Installing the system in Computer.
(c) Conducting any user training that might be needed for
using the system.
Software Principles Used
Software principles are the principles on the basis of which we conceive a computer
system. Actually these are not strict as to apply all the principles to software, rather the
principles which are relevant shall be applied. Each software system specific to a client
has to compromise on certain issue due pressure from client. However each and every
software must follow some minimum requirements as standard to make software
development more easy.

Page
13
I used spiral process model along with Prototyping process model as our guiding. System
was installed at client with functionality to evaluate and again revaluation all these events
were consolidated as one in analysis part but in reality it was actually in pieces.
The Spiral Model
The spiral model, originally proposed by Boehm [BOE88], is an evolutionary software
process model that couples the iterative nature of prototyping with the controlled and
systematic aspects of the linear sequential model. It provides the potential for rapid
development of incremental versions of the software. Using the spiral model, software is
developed in a series of incremental releases. During early iterations, the incremental
release might be a paper model or prototype. During later iterations, increasingly more
complete versions of the engineered system are produced.A spiral model is divided into a
number of framework activities, also called task regions. Typically, there are between
three and six task regions.
These six regions are as follows: -
§ Customer communication: - tasks required to establish effective communication
between developer and customer.
§ Planning: - tasks required to define resources, timelines and other project-related
information.
§ Risk analysis: - tasks required to assess both technical and management risks.
§ Engineering: - tasks required to build one or more representations of the application.
§ Construction and release: - tasks required to construct, test, install and provide user
support (e.g., documentation and training).
§ Customer evaluation: - tasks required to obtain customer feedback based on evaluation
of the software representations created during the engineering stage and implemented
during the installation stage.

Page
14
 Complete Structure of the Program

 Analysis
The Organization maintains Supplier, order entry, order tracking, finalization of
orderline, stock checking, General stores products,Staff, Customer,Sale,Purchase,
Products Details, Enquiry,Billing of transaction, stocks of general stores products of
different models, advertisement etc . There is a deep requirement for providing
information to the end customers situated anywhere in the Bihar state to know about the
retailer shop and to deal with the company and perform reliable transaction. So,
application is required to be developed as early as possible. The firm’s procedure was
studied extensively to image out the practices of accounting followed. Different involved
information in firms transaction reports are compiled from the data of last two year as
well as the current year. Proper investigation of transactions revealed so many
information’s however recorded but not as per the standard but the meaning of
transactions can be constructed by proper investigation.
The testing process was also affected and was time consuming, takes a long time and
therefore proper control cannot be applied as and when necessary rather after a time
when things come in view while compilation of data for the final commission etc.
The manual Testing system is unable to fulfill the information requirement efficiently due
to increased activity and expansion of business. The manual system is following the
system of sale purchase transaction. Basically it records all transaction in a manual file, it
records everything like a daybook into it. Manual files are handled daily,Monthly and
yearly. The manual process was also complex and time consuming due to huge amount of
data and improper recording.
The study of existing system requires before computerized application. The system being
a large system covering entire things of firm, it is divided into modules to each the
complexity.

Page
15
 Data Flow Diagram (DFD) :-
System Design of “RETAIL SHOP MANAGEMENT SYSTEM [RSMS] ” With
Reference ToD LAL & SONS for Departmental Store , Begusarai[BIHAR]

SHOP_DETAILS

ITEM DETAILS CUSTOMER_BILL

RETAIL SHOP
WORKER_DETAILS
MANAGEMENT SUPPLIER_BILL
SYSTEM
CUSTOMER_DETAILS WORKER_SALARY

ORDER_DETAILS DAY TO DAY REPORT

SUPPLIER_DETAILS

LOGIN DETAILS

DATABASE

‘0’ LEVEL DFD

Page
16
YES

NO

1 LEVEL DFD
RETAIL SHOP
Login MANAGEME
process NT SYSTEM

“INVALID PWD”

Item stock
Module

Sale/Purchase
Module

Order
Tracking &
Invoicing/
Billing

DATABASE

Page
17
2ND LEVEL DFD
Item stock

Query

Entry
process &
qty
updation

DATABASE

Cust Info

Booking STOCK
MASTER

Qty verify

DATABASE

Page
18
 2ND LEVEL DFD

SaleItem Charges

Sale Sale
master Master File

Qty count

DATABASE

3RD LEVEL DFD

Query Type

Query Query Report

Query Criteria

DATABASE

Page
19
3RD LEVEL DFD

Sale/Purchase

Purchase
details
updation
Sale
details
updation

DATABASE

Page
20
3RD LEVEL DFD
Purchase Order
Purchase Remittence File
process

Sipplier_Info Purchase Bill

DATABASE

Invoicing/B Order
line
illing
billing

Query
&
Report

Purchase Sale
billing billing

DATABA
SE

Page
21
  ER-Diagram
PID# IName
SName Address
IType

SUPPLIER 1 Purchase N ITEM

M Company
SupId# Contact Price
TotaL Qty
VatTinNo Amount
1
PurchaseId# PType
Sell
PDate
VATTIN# PName
PURCHASE
KDate WName 1

M 1
SHOP take WORKER

SAddres Address
SName WId#
s OrderNo
RegDate SDate
Paticulars Qty SALE DETAIL
M N

give ORDER SaleId# Particulars

M
Amt
1
ODate SalePrice
Orderno#

OrderNo Total
1 M
SHOP OWNER generate
BILLING
BDate Tax
Scode# Dept NetAmt
BillId#
contact
Address
SName

Page
22
  GANTT CHART ForRETAIL SHOP MANAGEMENT SYSTEM [RSMS]

SRS
PROCESSES
ANALYSIS

DESIGN

CODIGN

TESTING

IMPLEMENTATION

10days 08days 08days 50days 10days 04days

TIME

Page
23
 Process Logic
 Operator Interface Module
Logic:
Step 1: Display Login Dialog
Step 2: Get Data Source
Step 3: Get OperatorCode
Step 4: Get Password
Step 5: If OperatorId and Password match,Connect to Database
Do Step 6
Else
Do Step 3
Step 6: End
 General stores products Detail Module
Logic:
Step 1: Start & Display General stores products Entry Detail Screen
Step 2: Get Data Source
Step 3: Validate Each Entries
Step 4: Save To Database
Step 5: End
 Enquiry Detail Module
Logic:
Step 1: Start & Display Enquiry Screen
Step 2: Enter concerned enquiries.
Step 3: Validate Each Entries
Step 4: Save To Database
Step 5: End
 General stores products Order Detail Module
Logic:
Step 1: Start & Display Order Entry Form
Step 2: Get Data Source
Step 3: Verify concerned Orders from the General stores products Database
Step 4: Enter Customer Details
Step 5: Verify Customer’s Entries
Step 6: Save To Database
Step 7: End
 Purchase General stores products Entry Module
Logic:
Step 1: Start & Display Purchase Entry Form
Step 2: Get Data Source
Step 3: Verify Purchase entries from Order’s Entries
Step 4: Verify Stocks
Step 5: Save To Database
Step 6: Generate Bill & Send it to the Printer in mode

Page
24
 Step 7: End

 Supplier Entry Module

Logic:
Step 1: Start & Display Supplier Entry Form
Step 2: Get Data Source
Step 3: Verify Supplier entries details
Step 4: Save To Database
Step 5: End

 Worker Entry Module

Logic:
Step 1: Start & Display Worker Entry Form
Step 2: Get Data Source
Step 3: Verify Staff entries details
Step 4: Save To Database
Step 5: End

 Billing Entry Module

Logic:
Step 1: Start & Display Invoice Form
Step 2: Get Data Source
Step 3: Cross checking of each particulars
Step 4: Save To Database
Step 5: Print it if required
Step 6: End

Page
25
 DATA STRUCTURE

User Id Table
Table name: - User_security

Field Description Field name Data type Length Remark

User Name Usr_id Varchar2 15 Primary key

Password Pwd Varchar2 15

Role Role Varchar2 15

General stores products type

Table name:-prod_type

Field description Field name Data type Size Remark

General stores products Prod_tp Varchar2 10 Primary key
type
General stores products Prod_nm Varchar2 20
name
General stores products Prod_mdl Varchar2 20
model
Company name Sh_nm Varchar2 30
Sell price Sell_price Number 7,2
Stock Stock Number 3
Cost price Cost_price Number 7,2
Advanced order Adv_odr Varchar2 2

General stores products detail

Table name:-Prod_dtl

File description Field name Data type Size Remark

Registration number Regis_no Varchar2 10 Primary key
General stores Prod_tp Varchar2 2 Foreign key
products type
Manufacturing date Manuf_dt Date
Date of purchase Purch_dt Date
Warranty session Warr_sess Varchar2 10

Shop details

Page
26
 Table name:-Sh_dtl

Field description Field name Data type Size Remark

Shop-id Sh_id Varchar2 3 Primary key

Shop name Sh_nm Varchar2 30

Address Addr Varchar2 100

Phone no Ph Varchar2 11
Product available Prd_avl Varchar2 50

Head of shop Sh_hd Varchar2 30

Purchase
Table name:-Purch_Sr
Field description Field name Data type Size Remark

Purchase Id B_id Varchar2 7 Foreign key

Particulars Parti Varchar2 10 Foreign key

Date of purchase Purch_dt Date

Total amount Tot_amt Number 7,2
Reduction Rdc Number 4
Tax Tax Number 4
Paid amount Pd_amt Number 9,2
Customer details
Table name:-Customer_dtl
Field description Field name Data type Size Remark

Customer-id Cust_id Varchar2 4 Primary key

Customer name Cust_nm Varchar2 30
Address Addr Varchar2 100

Page
27
Phone no Ph Varchar2 16
Mobile Mob Varchar2 16
Worker Details
Table name:- Worker
Field description Field name Data type Size Remark
Worker-id Scode Varchar2 3 Primary key
Name Nm Varchar2 30
Address Addr Varchar2 100
Phone no Ph Varchar2 16
Date of Joining Doj Date
salary B_sall Number 7,2
depttype Desig Varchar2 20
Max-leave allow Lv_max Number 2
Customer sell details
Table name :-cust_sell_dtl
Field description Field name Data type Size Remark
Registration no Regis_no Varchar2 10 Foreign key
Customer-id Cust-id Varchar2 4 Foreign key
Date of selling Dt_sell Date
Selling-price Sell_price Number 7,2
Tax Tax Number 5,2
Paid amount Pd_amt Number 9,2
Customer commission Com_amt Number 5,2
amount

Receipt table
Table name:-rcpt_tbl
Field description Field name Data type Size Remark

Receipt-no Rcpt_no Varchar2 7 Primary key

Registration-no Regis_no Varchar2 10 Foreign key
Customer-id Cust_id Varchar2 7 Foreign key
Pay-date Pay_dt Date
Pay-amount Pay_amt Number 5,2
Total Tot Number 7,2

Page
28
Order table
Table name:-odr_tbl
Field description Field name Data type Size Remark
Order no Odr_no Varchar2 5 Primary key
Order date Odr_dt Date
Customer name Cust_nm Varchar2 40
Address Addr Varchar2 100
Dist Dist Varchar2 30
State State Varchar2 30
Pin Pin Number 6
Phone no Ph Number 16
Mobile Mob Varchar2 16
General stores products Prod_tp_id Varchar2 12
type required

No of item required Req_no Number 3

General stores productsSale

Table name:-Prod_Sell

Field description Field name Data type Size Remark

Saleid Saleid Varchar2 7 Primary key

Sale date Sale_dt Date
General stores products Prod_tp Varchar2 2 Foreign key
type
No of item No_o_itm Number 3
Total amount Tot_amnt Number 9,2

Page
29
Introduction to NICESOFTECH

NiceSoftech is a private limited software development company headed by Mr.

AMIT KUMAR. The purpose of the establishment of company is to provide
smooth technology aspects in IT sectors by developing software with emerging
technological factors .GNS is leading the work of data processing and software
development by developing and processing voluminous data for different Agencies
like Railway Recruitment board, housing board, colleges, insurance sectors,
departmental stores, cyber cafes etc all involving voluminous data requiring sharp
edge technology and expertise. The organization has a well established software
section exploring the new technology and employing them for their client to gain the
benefit of emerging technologies. The new trends like OMR, scanning application
forms, animation and printing photographs on certificates, OCR technology, bio-
metric technology etc are employed to enhance the data processing tasks, the
organization is also working in the field of internet related services. The web site
development web security, e- commerce, accounting is also explored and running
successfully.
The said project entitled ”RSMS” has been developed under this software
consultancy.

Address:
NiceSofTech
2nd floor, Rishi Bazar Complex
Kadam Kuan , patna-3
+91-9199789525 / 9852309693

Page
30
 SCOPE/FUTURE ENHANCEMENT OF APPLICATION

Limitations of the system:

 System works in all platforms and its compatible environments.
 It can work either on desktop environment or client/server architecture.
 User cannot do any changes without the permission of Admin.
Future Enhancements:
It is not possible to develop a system that makes all the requirements of the user. User
requirements keep changing as the system is being used. Some of the future
enhancements that can be done to this system are:
 Since a new item has been launched time to time, so it can be easily
included in the existing application without affecting the entire module.
 The proposed system database is an RDBMS and any changes could be
easily incorporated into the information system in future when
management decides to computerize its other process of new requirement.
 New fields can be added without affecting the system performance.
 The system is built on RDBMS technology, therefore all especial ties of an
RDBMS system and future scope can also be defined from here.
 Any shop that has similar requirements can adopt this application after
doing slight modifications

Page
31