PROJECT REPORT ON

SOLITAIRE
[SHARE ACCOUNTING SYSTEM]
IN
‘#########’

A PROJECT REPORT SUBMITTED TO

UNIVERSITY OF MUMBAI

BY

SANKET NAYAK (269)

PRANIT RAORANE (285)

B.Sc. (INFORMATION TECNOLOGY)

(2008-2009)

UNDER THE GUIDANCE OF

Mrs.INDRANI SEN

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR

QUALIFYING
B.SC.-(I.T.), SEMESTER – VI EXAMINATION

CHIKITSAK SAMUHA’S
S. S. & L. S. Patkar College of Arts &
Science
And
V. P. Varde College of Commerce & Economics
S. V. Road, Goregaon (E), Mumbai – 400
062
 CHIKITSAK SAMUHA’S
S. S. & L. S. Patkar College of Arts & Science
And
V. P. Varde College of Commerce & Economics
S. V. Road, Goregaon (E), Mumbai – 400 062

Project Certificate

CERTIFICATE
This is to certify that the project entitled
_______________________________________
Undertaken at the
___________________________________________________by
Mr./Ms._____________________________ Seat no. __________________ in
partial fulfillment of B.Sc. IT degree (Semester. VI) Examination had not
been submitted for any other examination and does not form part of
any other course undergone by the candidate.
It is further certified that he/she has completed all required phases of
the project.

Signature of Internal Guide Signature

HOD / In-charge / Coordinator
 College seal

Certificate from Guide / Company

(On Company’s Letterhead)

Certificate

This is to certify that the project entitled

_______________________________________
Undertaken at the
___________________________________________________by
Mr./Ms._____________________________ Seat no. __________________ in
partial fulfillment of B.Sc. IT degree (Semester. VI) Examination has
been completed under my supervision.

Signature of External
Guide
 Synopsis of the Project

The scope of every programming language in the

software field is very dynamic and is an amalgamation of its powers
and hard work and efforts of the programmer. Being the student of
B.Sc. (Information Technology) we were always keen to work on a
language which involves rational thinking while implementing it on
different aspects of life thus opening enormous horizons of
programming world.

The project is based on VB and uses SQL SERVER for

database connectivity. Since we had VB in 5th semester, this was a
kind project that included programming entities we aware of and had
a need for a user-friendly fast working application which could be
implemented for EVENT MANAGEMENT SYSTEMS.

Thus we developed system that handles tasks of SHARE

ACCOUNTING SYSTEM FOR A CO-OPERATIVE BANK such as
registering and storing the details of the customers, who apply for
shares, the processing of the share allocation flow, approval or
rejection of the membership, the calculation of dividend, and an
automatic allocation of the dividend to the respective members. The
project includes six main modules –General master, Application
Entry, Processing, Dividend, Reports and Security. We had review
meetings with our internal guide Mrs. Indrani Sen as a feedback
analysis.
Thus we developed system that handles tasks of Share
Accounting System for a Co-operative bank. Thus for our dedication
and patience that we have invested in successful completion of this
project we have named this system as “SOLIATIRE”.
 ACKNOWLEDGEMENT
I take this opportunity of submitting this report to express
my profound gratitude to the management of “S.S. & L.S.
Patkar College of Science and Commerce” for giving me
the opportunity to accomplish this project work.

I am very much thankful to “Mr. Uday Mashelkar” –

Principal, for their kind co-operation in the completion of my
project.

I am also grateful to our Head of Department “Mrs.

MALA KHARKAR” and my Project Guide “Mrs.INDRANI
SEN”, for being resourceful, helpful & also for their constant
support, encouragement and able Guidance, without which the
successful completion of this project would have been
impossible. Their positive attitude, forceful personality and
unwavering faith in me assured that I come out of the woods
whenever I encountered difficulties.

It is my earnest endeavor to express my sincere thanks

to the faculty for their kind co-operation, help and never ending
support.

I owe a lot to my client #######, the Proprietor of

#####.who helped me a lot in making of this software by
giving me useful information and support time and again.
 Last but not the least entire Computer Department
who directly or indirectly helped me in the completion of this
project and to God and my family without whose blessings,
support, motivation and encouragement this would not have
been possible.
 INDEX

• Company Profile
 Description of Existing system
 Limitation of Existing system
 Proposed system

• Feasibility Study

• Objective & scope of project

• Theoretical Background

• Definition of problem

• System analysis & Design

• Pert chart

• Gantt chart

• Detailed Life cycle of project-

 Data Flow Diagram
 Entity Relationship Diagram
 Screen Designs

• Process involved

• Methodology used for testing

• Test Report

• Annexure
Data Dictionary
Future Enhancement
List of abbreviations
References

Company Profile
Company Name :

Established :

Location :

Tel No :

E-Mail :

DESCRIPTION OF EXISTING
SYSTEM
The study of existing system brought the following
issues to light.

 The ####. System is partly managed by an automation

system and mostly managed by manual system which has
some limitations.

 The Application entry is mostly manual and managing the

application is very difficult and a tedious job.

 The dividend allocation is also partly managed by an

automated system thus the work becomes more tedious.

LIMITATIONS OF EXISTING
SYSTEM
 Since the system is mostly manual it is highly error prone.

 Also the system is prone to human error in calculations.

 Maintenance of Applications & their storage is extremely

tedious.

 The work is more time consuming.

 Reports generation is time consuming.

 Information updating is tedious and takes lots of time.

 Dividend calculation is done mostly manually; which is not

reliable.

The proposed system tries to eliminate the

problems & limitations of the existing
system.
 Proposed System
The proposed system facilitates the user in the following
way:

• To store & update the applications along with the

details.

• To store the dates of the board meeting and the

respective employees of the bank who attend the
meeting.

• To calculate the dividend rate as per decided in the

board meeting and to allocate the dividend amount to
all the customers.

• To generate reports.

• To maintain the security of the software.

• To store & update the applications along with the

details.

Information about different members who apply for the

loan is stored here. Additional details such as the
Nationality, Occupation, and Account type of the member
are also stored. There is thorough checking done if the
applicant is a member of the bank and is not in the default
list.

• To
 FEASIBILITY STUDY

Feasibility study is totally depending upon the preliminary

investigations & requirements of the system. Hence we have to
determine the system requested is feasible or not. This helps us
to check technical, operational & financial feasibility of requested
system against the current system. Various types of feasibility
study we have done are operational, technical and financial which
are equally important.

 Technical feasibility:

######## is equipped with the following

hardware and software.

Hardware:
2.2 Ghz Pentium IV
128 MB DDR RAM
40 GB hard disk
3.5 inch floppy disk drive
Inkjet printer
Dot matrics printer
Software:
Microsoft Windows XP Professional
Microsoft SQL Server (Database).

Front End:
VISUAL BASIC 6 (Front End).

Back End:
An R-DBMS in Microsoft SQL Server
  Operational Feasibility:

The Owner was willing to implement use and support

the system. The Owner was also forthcoming to arrange
for deployment and training sessions with us in order to
fully utilize the efficiency of the system

 Economical feasibility:

As the Owner was planning to implement

automated system, there will be very affordable cost for this
Project. As Owner had to manually calculate the
transactional specification and perform all the operations on
his own, this system helped him out at faster rate and
generates accurate results, which also eliminated the human
errors that occurred, affordable implementation didn’t gave
rise to high economic issue.
 Objectives of the Project

The objectives of the Project are:-

 The main objective of the system is to maintain the working

of Event Management Systems with a maximum efficiency.

 To generate and store bills of customers.

 To generate and store reports.

 To allow User to see average profit per Month.

 To keep records of old bill and generate reports against

them.

 To keep a record of latest Service Providers with the cost.

 To make the system user- friendly, interactive and easy to

use.

 To keep records of customer details, daily events with

status, and payment.

 To keep the status of each event separately and thereby

removing any confusion between two events.
 Scope of the Project

The scope of the Project is:

The Project basically handles seven different menus:-

 APPLICATION SETTINGS: This module involves the name of the

Customer. The services needed by the customer are all inquired. The service
and the items that are needed are also stored in within this module. The
payments made in advance are stored here.

 SERVICE PROVIDERS: The names of the Service Providers are stored

within this module. It includes the Decorators, Caterers, Advertiser,
Photographers and Security Agency.

 Private Events: The details about the event are stored. The name of
the company along
With the estimated amount, Resource allocation,E
 Theoretical Background
Front End:

VB
 We had chosen a LIVE PROJECT for a company named
Aticest Pvt.Ltd. The project is a GUI based database application.

After we had chosen the subject for our project, the big
task facing us was the language which we would have to use to
make our project simple and easy for Designing and
Implementation.

Since our project is a GUI based application, High-level

language programs are easier to write and understand than
Machine-language programs primarily because numeric codes for
addresses and operators are replaced by more meaningful
symbolic codes.

The programmer must still know the details of how a

specific computer operates. He must also mentally translate
complex operations and data structures into sequences of low
level operations which use primitive data types, that machine
language provides. The programmer must also be intimately
concerned with how and when data is represented within the
machine. Basically, a High-level programming language allows a
programmer to express algorithms in a more natural notation that
avoids many of the details of how a specific function works.

Visual Basic, Visual C++ is some of the programming

languages that the programmer can use to develop GUI based
applications. Here we selected Visual Basic as the language to
develop our project.

Microsoft Visual Basic is the fastest and easiest way to create

application for Microsoft Windows whether you are experienced
professional or brand new to Windows programming. Visual Basic
provides you with a complete set of tools to simplify rapid application
development.

So what is Visual Basic? The ‘Visual” part refers to the method

used to create the graphical user interface (GUI). Rather than writing
numerous lines of codes to describe the appearance and location of
interface elements, you simply add pre-built objects into place
screen.

Visual Basic has many tools:

1) Data access features allow you to create databases, front-end

application and scalable server-side component for most popular
database formats, including Microsoft SQL Server and other
enterprise-level databases.

2) ActiveX™ technologies allow you to use the functionality

provided by other application, such as Microsoft Word Processor,
Microsoft Excel Spreadsheet, and other Windows application. You can
even automate application and objects created using the
Professional or Enterprise editions of Visual Basic.

So to Design & Implement our project with ease and to develop

a Graphical User Interface we finally selected to use Visual Basic as
our Front End.

So using Visual Basic we can develop a totally Graphical &

Visual software which a User with very little knowledge of Computer
can easily operate on our Software.

.
 Back End:

Microsoft SQL Server 2000

A computer is more suited for database application

because of two reasons:-
1) It can hold large amount of data.
2) It operates at a very high speed.

There are two facts that make it ideal for

database application, for you can put the entire information into
the computer which by virtue of its speed can perform various
operations, such as searching for required information from the
database or storing the information in the database, arranging
the information, calculating results etc, within a matter of
seconds. A database is a group of related records. It consists of
columns known as fields and rows known as records. They store
information about a particular entity.

A database is a collection of information that’s

related to a particular subject or purpose, such as tracking
customer orders or maintaining a music collection, If your
database isn’t stored on a computer, or only parts of it are, you
may be tracking information from a variety of sources that you
have to coordinate and organize yourself.

For example, suppose the phone numbers of your

suppliers are stored in various locations: in a card file containing
supplier phone numbers, in product information files in a file
cabinet, and in a spreadsheet containing order information. If a
supplier’s phone number changes, you might have to update that
information in all three places. In a database, however, you only
have to update that information in one place – the supplier’s
phone number is automatically update wherever you use it in the
database.

Microsoft SQL Server is one of the most flexible

database creation and management software. It uses a very
compatible format for using databases with programming
languages like Visual Basic 6.0, Visual C++ and other ActiveX
capable languages.

Using MICROSOFT SQL SERVER, you can

manage all your information from you a single database file. Within
the file, you can use:

• Tables to store your data.

• Queries to find and retrieve just the data you want.
• Forms to view, add, and, update data in table.
• Reports to analyze or print data in a specific layout.
• Data access pages to view, update, or analyze the
database’s data from the Internet or an Intranet.

MICROSOFT SQL SERVER also provides high

security to the databases. It allows creating a user password and
system level security. It also secures the database from any
normal user who does not have required privileges.

So for all the above Reasons we have selected

MICROSOFT SQL SERVER as Back End.
 Definition of Problem

PRESENT SYSTEM
No Users tool for reports. Owner has to update daily
transaction, generated manual database. Then he can generate
bills for his customer on event basis. And for previous bills he
have to search the record manually form the database which is
more tedious.
If new customer or new supplier introduced in the firm or if
previous supplier left the organization. Then owner has to
maintain their information and records in database manually.
If customer places new subscription then owner has to
process that subscription manually also he has to keep in mind
when each subscription he made.He also has to have a constant
touch with Service Providers. And needs to store their detail;
which is done manually.
Drawback of Present System
• System is Not User friendly.
• Security Problem.
• Accessing, deleting and adding problems.
• Searching and maintenance problem.
• Currently major part of the job in the company is carried out
on Papers.
• No proper workload distribution.
• No proper management of work carried out at firm.
• Escalation process carried out manually which is a tedious
job.
• Data being mishandled, retrieving of data and data
manipulation becomes tedious.
 Proposed System

• Escalation of Cases.

• Work Load Distribution.

• User Friendly Application.

• Easy retrieval of data and proper data maintenance.

• Provides notification as and when possible and also

generates timely reports.

• The Proposed System has a centered database where all

the data can be complied and kept together due to which
every user can log and query the data from the database.

• Referential integrity of Relational Database is followed.

• User friendly prompts are provided for users.

• Use of shortcuts to access different processes is provided.

 • Reports allow generation of reports dynamically with
desired query.

• Easy navigation is provided for maintaining proper flow of system.

3rd August - 3rd Sep 24th Oct → 31st Oct
Scope &
Design &
Initial
GUI 1st Feb → 19th Feb
Requireme
nts Analysis / Testing
Software
Requireme
nts Development
7th Sep → 18th Oct
6st Dec → 29th Jan
 August 08 September 08 October 08 November 08 December 08
W W W W W W W W W W W W W W W W W W W W
1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
1) Scope &
Initial
Requirement
Meet
guidelines
Id needs and
Constraints
Det. Goals
and scope
Establishing
specifications
Milestone-Scope and Initial Specification completed.

2) Analysis &
S/W Req.
Feasibility
Study
Needs
Analysis
Time / Cost
analysis
Prepare and
Review SRS

Milestone – Analysis completed.

3) Design
Develop func.
Specifications
Preparing
diagrams
Obtain
Approval.

Milestone – Design completed.

4) Devlpment
Develop code

January 09 February 09
W W W W W W W W
1 2 3 4 1 2 3 4
Develop code
Develop GUI
Initial Dev.
Testing

Milestone-Development Complete

5)Testing
Unit Testing
White Box,
Black Box
test

Milestone – Testing Complete

 DATA FLOW DIAGRAM

A Data flow diagram (DFD) is graphical system model that

show all of the main requirements for an information system in

one diagram : inputs & outputs, processes, and data storage.

Symbols used in Data Flow Diagram are as follows:

 Process: Step by step instructions are followed
That transforms
inputs into outputs.

Data Flow: Data flowing from place to

place such as an input or output
to a process.

Entity: Any object or person that is

engage in transaction

Data store: Data at rest, being stored for

later use

CONTEXT LEVEL 0: -
 Customer Detail

Payment / Salary
Subscription Detail

Payment
CUSTOMER 0 Employee
VELOCE
Bill

Employee Detail

Daily Transaction
 Daily Transaction Details
1.0 Trans_Paper
Daily Transaction

Trans_Magzine

Customer Details

CUSTOMER 2.0 Customer

Customer
Details

Details Bill
3.0
Bills
Bills
Bills Pay
 Level 1

Day Feed Details

U/R
1.1
Trans
Day Feed

CUSTOMER

U/R

1.2 Trans_Paper
Manual Feed
Details
U/R

Trans_Magzine
 Customer Details

2.1 U/R Customer

New Customer
Cust_ID

Details

Customer
U/R Customer
2.2
Update Customer

Details U/R
2.3 Preferences
Update Preferences
 Details

3.1 U/R Bills

Customer Bill

Pays

Customer
Bill U/R Bills
3.2
Generate Bill

Details
 U/R Preferences
2.3.1
Customer Update Paper
Details Preferences

Details
U/R
Preferences
2.3.2
Update Magzine
Preferences
Details
 Entity Relationship Diagram

Entity Relationship Diagram (ERD) can express

overall logical structure of a database graphically.

T h e c o m p o n en t s o f E - R D i a g r a m a r e :

Entity: Entity is a thing or object

in a
Real world that is
Distinguishable from all
o t h er
Objects.

Attributes: Descriptive property of a

Entity.

Relationship: It is an association
among
Several entities

Link: It links attributes to entity

sets and
Entity
frmsplash
frmLogin
Process Involved
 A Process is a particular course of action intended to achieve a desired
result. It is heart and soul of any system. Without process not a single task can be
performed.

Our proposed system involved the following process:

• When you begin to create a report using proposed system, it asks for the type
of log-in the person will select i.e. Administrator or as a Normal User. If the
person enters as an Administrator, he then only has the privileges to create
different types of reports or view his own reports. If the person logs in as a
Normal User, then he can only be able to view the previously made reports
by the Administrator.

• As the Administrator logs in, he gets the option to select whether to create a
new report or to view previously made reports. If he selects to view the
reports, he gets the list of all existing reports made by him. Then he can
select the appropriate report which he wants to view. If he selects to create
new report, he has to enter the name of new report. Then the type of driver
and the DSN (Data Source Name) through which he will connect his
database to the system are selected. Once he selects the driver type and DSN
name, the connection gets automatically established.

• Then an option can be chosen, whether to perform a manual query or to

perform a select query. If he selects manual query type, he has to input a
query to the database to get the desired output. According to the performed
query, the result will be displayed to the Administrator through which he can
select column name from the given table.

• In the select type, the Administrator will directly select the table-name on
which the query has to be performed. The columns corresponding to that
table will be displayed to him. These columns are used further to select the
values for the type of chart. Then he can select a type of chart to be viewed
for the output i.e. a Bar chart, Line graph, Dot graph and a Pie chart etc .
 Water Fall Model

Problem
Definition

Analysis

Design

Coding

Testing

Maintenance

This model contains to break up the identifiable activities into a series

of actions each of which must be completed before the next begins.
These activities are as follows:

Problem Definition:-

A clear statement of problem is

crucial of the success of the software. It helps not only to develop but
also the user to understand the problem better.
 Analysis:-

After the problem definition is known, we

concentrated on the scope of the system and what will be the various
processes involved. The system will get the personal details of the
Customer, Paper details, Magazine details, Transaction details, and
Employee details also. The details will be entered by Owner itself. The
system will generate some reports for the Transaction per month, Bill
Payment per month, different alerts regarding the offers.

Design:-

The design phase with the various concepts

of system design, such as data structure, software Architecture and
algorithms. This phase translates the requirements into a
representation of Software. This is the stage, which answers the
questions of “HOW?” we put a lot of efforts in designing. We designed
five modules for system namely Customer details, Subscription
details, Transaction details, Employee details, and generates Reports.

Coding:-

This refers to the translation of design into

machine readable form. The more detailed the Design the easier is it
to code.

Testing:-

Once the code is written it should be tested

for correctness. Testing may involve the individual Units or the whole
system. It requires a detailed plan as to what, when and how to test.
We have Performed white box testing, Black box testing, Unit testing,
Integration testing.
 Maintenance:-

After the software has been installed it may

undergo some changes. This may occur due to a Change in the user
requirements, change in operational environment or an error in
software, which has not been fixed while testing. The proper follow up
of the system and error solving in post implementation phase is what
is called as maintenance.
System Maintenance & Evaluation

 Maintenance :

After the system was installed it was continuously analyzed

for defects, errors & compatibility problems. In case of an error
or problem, it was rectified on the spot or within an acceptable
time frame.

 Evaluation :

In today’s world, none of the system is completely perfect.

As the various requirements of user keeps on changing, the
software needs to be further modified. <<<>>> is a report
generation tool which is used to represent data in different
formats. Also, our proposed system can be further enhanced.

Our system has following limitations as follows:-

 All the various generated reports are in form of a file
which is stored on the machine’s disk consuming some
amount of space.
 This system does not supports multi-table queries in which
more than one table is used.
 Also this system does not perform any of the summary
query operations.

The new features can be added in our system to overcome

the above limitations. These are:
 We would like to reduce the disk space occupied by
our system’s report file.
 The proposed system should support various multi-
tables queries as well as sub-queries operations.
 The proposed system should support various
summary queries.
 Also we would like to further add few more types of
charts & graphs.
 Cost & Benefits Analysis
To analyze the cost and benefits of our proposed system, we
have used COCOMO Model (Constructive Cost Model). It is most
complete & thoroughly documented model. COCOMO Model
divides system into three classes of systems. These are:
• Embedded
• Organic
• Semi-detached

Our system falls into the category of Organic class. Basic

form of COCOMO Model is exclusively based on program size
expressed in KDLOC (Kilo Delivered Lines of Code).
b
Effort = a * KDLOC

Where, a and b are two parameters of the model whose

specific values are selected upon class of software systems.
For Organic systems,
1.05
Effort = 2.4 * KDLOC

The COCOMO Model also determines the development

schedule,
M (expressed in months) using previously calculated effort. For
Organic system,
0.38
M = 2.5 * Effort
 COCOMO Model is also used to estimate software
maintenance. The formula is based on previous effort estimate.

Effortmaintenance = ACT * Effort

Where, ACT is Annual Change Traffic that is a fraction of

KDLOC undergoing change during the year.
 TESTING
Testing is very vital for any system to be successfully
implemented. The common view is that it is performed to prove
that there are no errors in a program. Therefore the most
useful and practical approach is with the explicit intention of
finding the errors. The system is tested experimentally to
ensure that the software does not fail. The system is run
according to its specifications and in the way the user expects.
Following testing practices are used. The system will process as
normal input preparation of test-sample data.

Following testing practices were used:

White-box Testing:

White box testing is a security testing method that

can be used to validate whether code implementation follows
intended design, to validate implemented security
functionality, and to uncover exploitable vulnerabilities.

White box testing requires access to the source code.

Though white box testing can be performed any time in the life
 cycle after the code is developed, it is a good practice to
perform white box testing during the unit testing phase.

It requires knowing what makes software secure or insecure,

how to think like an attacker, and how to use different testing
tools and techniques. The first step in white box testing is to
comprehend and analyze source code, so knowing what makes
software secure is a fundamental requirement. Second, to create
tests that exploit software, a tester must think like an attacker.
Third, to perform testing effectively, testers need to know the
different tools and techniques available for white box testing. The
three requirements do not work in isolation, but together.

White-box testing provides the following functions:

1. Guarantees that all independent paths within a module have
been exercised at least once.
2. Exercises all logical decisions on their true and false sides.
3. Executes all loops at their boundaries and within their
operational bounds.
4. Exercises internal data structures to ensure their validity.

Black Box Testing –

Black-box testing is the craft of testing a program

from the external view. We look at how the program operates in
its context, getting to know needs and reactions of the users,
hardware and software platforms.

Black-box Testing is testing without knowledge

of the internal workings of the item being tested.
For example, when black box testing is applied to
software engineering, the tester would only know the "legal"
inputs and what the expected outputs should be, but not how the
program actually arrives at those outputs. It is because of this
that black box testing can be considered testing with respect to
the specifications, no other knowledge of the program is
necessary. The tester and the programmer can be independent of
each other’s work. Black-box test design treats the system as a
"black-box", so it doesn't explicitly use knowledge of the internal
structure. Black-box test design is usually described as focusing
on testing functional requirements.

Black Box testing in our application attempts to find errors

in following categories –
 Incorrect or missing functions
 Interface errors
 Errors in data structure or external database asses
 Behavior or performance errors
 Installation and termination errors
 Strategies used for Testing

Unit Testing

Each and every module was intensively tested to check for errors and
defects. All possible mistakes were rectified. Manually code is tested like logical
errors.
Once the manual checking is over the compilation has been done.
Syntactical error if any has to be corrected.

After the clean compilation of the program, some dummy data

as per specifications has been used for testing of that module to see if it works as
specified.
TEST REPORT
Relationship
 Database Names

Name of the Tables:

1. CUSTOMER
2. PAPERS
3. MAGAZINE
4. TRANS_PAPERS
5. PAYMENT
6. BILLS
7. TRANS_MAGZINE
8. PAPERPATTERN
 Table Information
Table I

(a) INFORMATION:

Name : CUSTOMER
No. of fields : 11
Description : This table stores the Customer record
Associated by the FIRM.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size

1 CustId Text Primary 50
Key
2 LineId Text Primary 50
Key
3 Cname Text -- 50
4 CAddress Text -- 100
5 ContactPers Text -- 25
on
6 TelNo Number -- 11
7 Mobile Number -- 10
8 Fax Number -- 11
9 DateOfJoinin Date/Time -- 8
 g
10 Balance Number -- 15
11 After Number -- 15

Table II

(a) INFORMATION:

Name : PAPERS
No. of fields : 9
Description : This table stores the Paper provided
by the
Firm.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size

1 PId Text Primary 50
Key
2 PName Text -- 50
3 PMonCos Number -- 5
4 PTueCos Number -- 5
5 PWedCos Number -- 5
6 PThuCos Number -- 5
7 PFriCos Number -- 5
 8 PSatCos Number -- 5
9 PSunCos Number -- 5

Table III

(a) INFORMATION:

Name : MAGAZINE
No. of fields : 3
Description : This table shows the Magazine
provided by
The Firm.

(a) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size

1 MId Text Primary 50
Key
2 MName Text -- 50
3 MCos Number -- 5

Table IV

(a) INFORMATION:
Name : TRANS_PAPERS
No. of fields : 6
Description : This table shows transaction of the
papers.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size

1 TransId Text Primary 50
Key
2 CustId Text Primary 50
Key
3 Pid Text -- 50
4 DateofSub Date/Time -- 10
5 NoofSub Number -- 5
6 P_U_Cos Number -- 10
Table V

(a) INFORMATION:

Name : PAYMENT
No. of fields : 11
Description : This table shows transaction of the
papers.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field

Size
1 PayId Text Primary Key 50
2 CustId Text Foreign Key 50
3 DoB Date/Tim Foreign Key 50
e
 4 BillNo Number Foreign Key 10
5 BillAmount Number -- 10
6 PaidAmount Number -- 10
7 DofPayment Date/Tim -- 8
e
8 ModeofPay Text -- 20
9 BDatFrom Text -- 8
10 BDatTo Text -- 8
11 Balance Number -- 15

Table VI

(a) INFORMATION:

Name : BILLS
No. of fields : 6
Description : This table shows the Bills records
provided
By the firm.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size

 1 Bid Number Primary 50
Key
2 BlData Text Primary 50
Key
3 StartD Text -- 50
4 EndD Text -- 10
5 StBillNo Number -- 5
6 EnBillNo Number -- 10

Table VII

(a) INFORMATION:

Name : TRANS_MAGAZINE
No. of fields : 6
Description : This table shows transaction of the
magazine

(b) DESIGN:
 Sr.No. Field Name Data Type Constraint Field Size
1 Id Text Primary 50
Key
2 CustId Text Primary 50
Key
3 Mid Text -- 20
4 DoSub Date/Time -- 8
5 NoSub Number -- 5
6 PuCost Number -- 10

Table VIII

(a) INFORMATION:

Name : PAPERPATTERN
No. of fields : 4
Description : This table shows transaction of the
magazine

(a) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size

1 Refid Number Primary 50
Key
2 Patid Text Primary 50
Key
3 Pid Text -- 20
4 Noofsub Number -- 8
 Future Enhancement

• W e g o i n g t o c o n v er t o u r s y s t e m t o w e b s i t e ,
so that customer can interact with us by visiting
our website.
• Due to online website the customers can
c h e c k f o r n ew l y l a u n c h e d m a r k e t o f f e r s a v a i l a b l e,
o n l i n e s u b s c r i p t i o n & a n d c o m p l a i n t b o x s er v i c e e t c .
List Of Abbreviations
Variable Naming Conventions:

Objects Prefixes

1. Form frm

2. Textbox txt

3. Combobox cbo

4. Groupbox grp

5. Picture box pic

6. Label lbl

7. Link Label lbl

8. Checkbox chk
References
For the Purpose of building the successful project, “VELOCE”,
that handles management of the newspaper at the owner side,
various sources of were used.

Bibliography:

Book: Programming with Visual Basic 6.0

Authors: Julia. Case Bradley
Publisher: TATA-McGraw HILL

Book: SQL Complete Reference

Author Name: Groff Weinberg
Publisher: TMH

Web Sites:

www.yahoo.com
www.google.com