share accountin systems

8/7/2019 Share accountin systems

1/87


2/87

PROJECT REPORT ON

SOLITAIRE

[SHARE ACCOUNTING SYSTEM]IN#########

A PROJECT REPORT SUBMITTED TOUNIVERSITY 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 FORQUALIFYING

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

CHIKITSAK SAMUHASS. S. & L. S. Patkar College of Arts &

Science

AndV. P. Varde College of Commerce & Economics

S. V. Road, Goregaon (E), Mumbai 400062


3/87

CHIKITSAK SAMUHAS

S. S. & L. S. Patkar College of Arts & Science

And

V. P. Varde College of Commerce & EconomicsS. 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 SignatureHOD / In-charge / Coordinator


4/87

College seal

Certificate from Guide / Company

(On Companys 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 ExternalGuide


5/87


6/87

Synopsis of the Project

The scope of every programming language in the

software field is very dynamic and is an amalgamation of its powersand hard work and efforts of the programmer. Being the student ofB.Sc. (Information Technology) we were always keen to work on a

language which involves rational thinking while implementing it ondifferent aspects of life thus opening enormous horizons ofprogramming world.

The project is based on VB and uses SQL SERVER fordatabase connectivity. Since we had VB in 5th semester, this was akind project that included programming entities we aware of and hada need for a user-friendly fast working application which could beimplemented for EVENT MANAGEMENT SYSTEMS.

Thus we developed system that handles tasks of SHAREACCOUNTING SYSTEM FOR A CO-OPERATIVE BANK such asregistering and storing the details of the customers, who apply forshares, the processing of the share allocation flow, approval orrejection of the membership, the calculation of dividend, and anautomatic allocation of the dividend to the respective members. Theproject includes six main modules General master, ApplicationEntry, Processing, Dividend, Reports and Security. We had reviewmeetings 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 dedicationand patience that we have invested in successful completion of thisproject we have named this system as SOLIATIRE.


7/87

A CKNOWLEDGEMENT

I take this opportunity of submitting this report to expressmy profound gratitude to the management of S.S. & L.S.Patkar College of Science and Commerce for giving methe opportunity to accomplish this project work.

I am very much thankful to Mr. Uday MashelkarPrincipal, for their kind co-operation in the completion of myproject.

I am also grateful to ourHead of DepartmentMrs.MALA KHARKAR and my Project Guide Mrs.INDRANISEN, for being resourceful, helpful & also for their constantsupport, encouragement and able Guidance, without which thesuccessful completion of this project would have beenimpossible. Their positive attitude, forceful personality andunwavering faith in me assured that I come out of the woodswhenever I encountered difficulties.

It is my earnest endeavor to express my sincere thanksto the faculty for their kind co-operation, help and never endingsupport.

I owe a lot to my client #######, the Proprietor of#####.who helped me a lot in making of this software bygiving me useful information and support time and again.


8/87

Last but not the least entire Computer Departmentwho directly or indirectly helped me in the completion of thisproject and to God and my family without whose blessings,support, motivation and encouragement this would not havebeen possible.


9/87


10/87

INDEX

Company Profi le Description of Existing system

Limitation of Existing system Proposed system

Feasibi l i ty Study

Objective & scope of project

Theoretical Background

Definit ion of problem

System analysis & Design

Pert chart

Gantt chart

Detai led Life cycle of project- Data Flow Diagram Entity Relat ionship Diagram Screen Designs

Process involved

Methodology used for test ing

Test Report

Annexure

Data Dict ionaryFuture Enhancement

List of abbreviat ions


11/87

References

Company Profile


12/87

Company Name :

Established :

Location :

Tel No :

E-Mail :

DESCRIPTION OF EXISTINGSYSTEM


13/87

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 hassome limitations.

The Application entry is mostly manual and managing theapplication is very difficult and a tedious job.

The dividend allocation is also partly managed by anautomated system thus the work becomes more tedious.

LIMITATIONS OF EXISTINGSYSTEM


14/87

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 extremelytedious.

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 notreliable.

The proposed system tries to eliminate theproblems & limitations of the existingsystem.


15/87

Proposed System

The proposed system facilitates the user in the followingway:

To store & update the applications along with thedetails.

To store the dates of the board meeting and therespective employees of the bank who attend themeeting.

To calculate the dividend rate as per decided in theboard meeting and to allocate the dividend amount toall the customers.

To generate reports.

To maintain the security of the software.

To store & update the applications along with thedetails.

Information about different members who apply for theloan is stored here. Additional details such as theNationality, Occupation, and Account type of the memberare also stored. There is thorough checking done if theapplicant is a member of the bank and is not in the defaultlist.

To


16/87


17/87

FEASIBILITY STUDY

Feasibility study is totally depending upon the preliminaryinvestigations & requirements of the system. Hence we have todetermine the system requested is feasible or not. This helps usto check technical, operational & financial feasibility of requestedsystem against the current system. Various types of feasibilitystudy we have done are operational, technical and financial whichare equally important.

Technical feasibility:

######## is equipped with the followinghardware and software.

Hardware:

2.2 Ghz Pentium IV128 MB DDR RAM40 GB hard disk

3.5 inch floppy disk driveInkjet printerDot matrics printer

Software:Microsoft Windows XP ProfessionalMicrosoft SQL Server (Database).

Front End:VISUAL BASIC 6 (Front End).

Back End:An R-DBMS in Microsoft SQL Server


18/87

Operational Feasibility:

The Owner was willing to implement use and supportthe system. The Owner was also forthcoming to arrangefor deployment and training sessions with us in order tofully utilize the efficiency of the system

Economical feasibility:

As the Owner was planning to implementautomated system, there will be very affordable cost for thisProject. As Owner had to manually calculate thetransactional specification and perform all the operations onhis own, this system helped him out at faster rate andgenerates accurate results, which also eliminated the humanerrors that occurred, affordable implementation didnt gaverise to high economic issue.


19/87


20/87

Objectives of the Project

The objectives of the Project are:-

The main objective of the system is to maintain the workingof 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 againstthem.

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

To make the system user- friendly, interactive and easy touse.

To keep records of customer details, daily events withstatus, and payment.

To keep the status of each event separately and therebyremoving any confusion between two events.


21/87


22/87

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 theCustomer. The services needed by the customer are all inquired. The seand the items that are needed are also stored in within this module. Thpayments made in advance are stored here.

SERVICE PROVIDERS: The names of the Service Providers are swithin this module. It includes the Decorators, Caterers, Advertiser,Photographers and Security Agency.

Private Events: The details about the event are stored. The namthe company alongWith the estimated amount, Resource allocation,E


23/87

Theoretical Background

Front End:

VB


24/87

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

After we had chosen the subject for our project, the bigtask facing us was the language which we would have to use tomake our project simple and easy for Designing andImplementation.

Since our project is a GUI based application, High-levellanguage programs are easier to write and understand thanMachine-language programs primarily because numeric codes foraddresses and operators are replaced by more meaningful

symbolic codes.

The programmer must still know the details of how aspecific computer operates. He must also mentally translatecomplex operations and data structures into sequences of lowlevel operations which use primitive data types, that machinelanguage provides. The programmer must also be intimatelyconcerned with how and when data is represented within themachine. Basically, a High-level programming language allows aprogrammer to express algorithms in a more natural notation thatavoids many of the details of how a specific function works.

Visual Basic, Visual C++ is some of the programminglanguages that the programmer can use to develop GUI basedapplications. Here we selected Visual Basic as the language todevelop our project.

Microsoft Visual Basic is the fastest and easiest way to createapplication for Microsoft Windows whether you are experienced

professional or brand new to Windows programming. Visual Basicprovides you with a complete set of tools to simplify rapid applicationdevelopment.

So what is Visual Basic? The Visual part refers to the methodused to create the graphical user interface (GUI). Rather than writing


25/87

numerous lines of codes to describe the appearance and location ofinterface elements, you simply add pre-built objects into placescreen.

Visual Basic has many tools:

1) Data access features allow you to create databases, front-endapplication and scalable server-side component for most populardatabase formats, including Microsoft SQL Server and otherenterprise-level databases.

2) ActiveX technologies allow you to use the functionalityprovided by other application, such as Microsoft Word Processor,

Microsoft Excel Spreadsheet, and other Windows application. You caneven automate application and objects created using theProfessional or Enterprise editions of Visual Basic.

So to Design & Implement our project with ease and to developa Graphical User Interface we finally selected to use Visual Basic asour Front End.

So using Visual Basic we can develop a totally Graphical &

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

.


26/87

Back End:

Microsoft SQL Server 2000

A computer is more suited for database applicationbecause 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 fordatabase application, for you can put the entire information intothe computer which by virtue of its speed can perform variousoperations, such as searching for required information from the

database or storing the information in the database, arrangingthe information, calculating results etc, within a matter ofseconds. A database is a group of related records. It consists ofcolumns known as fields and rows known as records. They storeinformation about a particular entity.

A database is a collection of information thatsrelated to a particular subject or purpose, such as trackingcustomer orders or maintaining a music collection, If your

database isnt stored on a computer, or only parts of it are, youmay be tracking information from a variety of sources that youhave to coordinate and organize yourself.

For example, suppose the phone numbers of yoursuppliers are stored in various locations: in a card file containingsupplier phone numbers, in product information files in a filecabinet, and in a spreadsheet containing order information. If asuppliers phone number changes, you might have to update thatinformation in all three places. In a database, however, you onlyhave to update that information in one place the suppliersphone number is automatically update wherever you use it in thedatabase.

Microsoft SQL Server is one of the most flexibledatabase creation and management software. It uses a very


27/87

compatible format for using databases with programminglanguages like Visual Basic 6.0, Visual C++ and other ActiveXcapable languages.

Using MICROSOFT SQL SERVER, you canmanage all your information from you a single database file. Withinthe 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

databases data from the Internet or an Intranet.

MICROSOFT SQL SERVER also provides highsecurity to the databases. It allows creating a user password andsystem level security. It also secures the database from anynormal user who does not have required privileges.

So for all the above Reasons we have selected

MICROSOFT SQL SERVER as Back End.


28/87


29/87

Definition of Problem

PRESENT SYSTEM

No Users tool for reports. Owner has to update dailytransaction, generated manual database. Then he can generatebills for his customer on event basis. And for previous bills hehave to search the record manually form the database which ismore tedious.

If new customer or new supplier introduced in the firm or ifprevious supplier left the organization. Then owner has tomaintain 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 mindwhen each subscription he made.He also has to have a constanttouch 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.


30/87

Escalation process carried out manually which is a tediousjob.

Data being mishandled, retrieving of data and data

manipulation becomes tedious.


31/87

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 alsogenerates timely reports.

The Proposed System has a centered database where allthe data can be complied and kept together due to whichevery 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.


32/87

Reports allow generation of reports dynamically withdesired query.

Easy navigation is provided for maintaining proper flow of system.


33/87


34/87

Scope &

InitialRequireme

nts Analysis /Software

Requirements

Design &

GUI

Testing

3rd August - 3rd Sep

Development7th Sep 18th Oct

24th Oct 31st Oct

6st Dec 29th Jan

1st Feb 19th Feb


35/87

August 08 September 08 October 08 November 08 December 08

W1

W2

W3

W4

W1

W2

W3

W4

W1

W2

W3

W4

W1

W2

W3

W4

W1

W2

W3

W4

1) Scope &

Initial

Requirement

Meetguidelines

Id needs andConstraints

Det. Goalsand scope

Establishingspecifications


36/87

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

Preparingdiagrams

Obtain

Approval.

Milestone Design completed.

4) DevlpmentDevelop code

January 09 February 09

W1

W2

W3

W4

W1

W2

W3

W4

Develop code

Develop GUI

Initial Dev.Testing

Milestone-Development Complete

5)Testing

Unit Testing

White Box,Black Box

test

Milestone Testing Complete


37/87


38/87


39/87

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:


40/87

Process: Step by step instructions are followe

That transforms

inputs into outputs.

Data Flow: Data flowing from place to

place such as an input or outputto a process.

Entity: Any object or person that isengage in transaction

Data store: Data at rest, being stored forlater use

CONTEXT LEVEL 0: -


41/87

0

VELOCE

CUSTOMER Employee

Payment / Salary

Employee Detail

Subscription Detail

Payment

Bill

Customer Detail

Daily Transaction


42/87

CUSTOMER

1.0

Daily Transaction

2.0

Customer

Details

Daily Transaction Details

Customer Details

Details

Bills

Bill

Pay

Trans_Paper

Customer

3.0

Bills Bills

Trans_Magzine


43/87

Level 1

CUSTOMER

1.1Day Feed

1.2

Manual Feed

Trans

U/R

Trans_Paper

U/R

Details

Day Feed Details

Trans_Magzine

U/R


44/87

Customer

2.1New Customer

2.2Update Customer

2.3Update Preferences

Customer

Customer

Preferences

U/R

U/R

U/R

Customer Details

Cust_ID

Details

Details


45/87

Customer

3.1Customer Bill

3.2Generate Bill

Bills

Bills

U/R

U/R

Details

Bill

Details

Pays


46/87

Customer2.3.1

Update PaperPreferences

2.3.2

Update Magzine

Preferences

Pref

Prefe

U/R

U/R

Details

Details

Details


47/87


48/87

Entity Relationship Diagram

Ent ity Relat ionship Diagram (ERD) can expressoveral l logical structure of a database graphical ly.

The components of E-R Diagram are:

Entity: Entity is a thing or objectin a

Real world that isDist inguishable from al l

otherObjects.

Attributes: Descriptive property of aEntity.

Relationship: It is an associationamong

Several entities

Link: It links attributes to entitysets and

Entity


49/87


50/87


51/87

frmsplash


52/87

frm Login


53/87

Process Involved


54/87

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 anew 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 .


55/87


56/87

Water Fall Model

This model contains to break up the identifiable activities into a seriesof actions each of which must be completed before the next begins.

These activities are as follows:

Problem Definition:-

A clear statement of problem iscrucial of the success of the software. It helps not only to develop butalso the user to understand the problem better.

Problem

Definition

Analysis

Design

Coding

Testing

Maintenance


57/87

Analysis:-

After the problem definition is known, weconcentrated on the scope of the system and what will be the variousprocesses involved. The system will get the personal details of theCustomer, Paper details, Magazine details, Transaction details, andEmployee details also. The details will be entered by Owner itself. Thesystem will generate some reports for the Transaction per month, BillPayment per month, different alerts regarding the offers.

Design:-

The design phase with the various conceptsof system design, such as data structure, software Architecture andalgorithms. This phase translates the requirements into arepresentation of Software. This is the stage, which answers thequestions of HOW? we put a lot of efforts in designing. We designedfive modules for system namely Customer details, Subscriptiondetails, Transaction details, Employee details, and generates Reports.

Coding:-

This refers to the translation of design intomachine readable form. The more detailed the Design the easier is itto code.

Testing:-

Once the code is written it should be testedfor correctness. Testing may involve the individual Units or the wholesystem. 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.


58/87

Maintenance:-

After the software has been installed it mayundergo some changes. This may occur due to a Change in the userrequirements, change in operational environment or an error insoftware, which has not been fixed while testing. The proper follow upof the system and error solving in post implementation phase is whatis called as maintenance.


59/87


60/87

System Maintenance & Evaluation

Maintenance :

After the system was installed it was continuously analyzed

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

Evaluation :

In todays world, none of the system is completely perfect.As the various requirements of user keeps on changing, thesoftware needs to be further modified. is a report

generation tool which is used to represent data in differentformats. 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 filewhich is stored on the machines disk consuming someamount 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 summaryquery operations.

The new features can be added in our system to overcomethe above limitations. These are:


61/87

We would like to reduce the disk space occupied byour systems report file.

The proposed system should support various multi-

tables queries as well as sub-queries operations. The proposed system should support varioussummary queries.

Also we would like to further add few more types ofcharts & graphs.


62/87

Cost & Benefits Analysis

To analyze the cost and benefits of our proposed system, we

have used COCOMO Model (Constructive Cost Model). It is mostcomplete & 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. Basicform of COCOMO Model is exclusively based on program size

expressed in KDLOC (Kilo Delivered Lines of Code).

Effort = a * KDLOC b

Where, a and b are two parameters of the model whosespecific values are selected upon class of software systems.For Organic systems,

Effort = 2.4 * KDLOC 1.05

The COCOMO Model also determines the developmentschedule,

M (expressed in months) using previously calculated effort. ForOrganic system,

M = 2.5 * Effort 0.38


63/87

COCOMO Model is also used to estimate softwaremaintenance. The formula is based on previous effort estimate.

Effortmaintenance = ACT * Effort

Where, ACT is Annual Change Traffic that is a fraction ofKDLOC undergoing change during the year.


64/87

TESTING

Testing is very vital for any system to be successfullyimplemented. The common view is that it is performed to provethat there are no errors in a program. Therefore the mostuseful and practical approach is with the explicit intention offinding the errors. The system is tested experimentally toensure 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 asnormal input preparation of test-sample data.

Following testing practices were used:

White-box Testing:

White box testing is a security testing method thatcan be used to validate whether code implementation followsintended design, to validate implemented securityfunctionality, 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


65/87

cycle after the code is developed, it is a good practice toperform 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 testingtools and techniques. The first step in white box testing is tocomprehend and analyze source code, so knowing what makessoftware secure is a fundamental requirement. Second, to createtests that exploit software, a tester must think like an attacker.

Third, to perform testing effectively, testers need to know thedifferent tools and techniques available for white box testing. Thethree requirements do not work in isolation, but together.

White-box testing provides the following functions:1. Guarantees that all independent paths within a module havebeen exercised at least once.2. Exercises all logical decisions on their true and false sides.3. Executes all loops at their boundaries and within theiroperational bounds.


66/87

4. Exercises internal data structures to ensure their validity.

Black Box Testing

Black-box testing is the craft of testing a programfrom the external view. We look at how the program operates inits context, getting to know needs and reactions of the users,hardware and software platforms.

Black-box Testing is testing without knowledgeof the internal workings of the item being tested.

For example, when black box testing is applied tosoftware engineering, the tester would only know the "legal"inputs and what the expected outputs should be, but not how theprogram actually arrives at those outputs. It is because of thisthat black box testing can be considered testing with respect to


67/87

the specifications, no other knowledge of the program isnecessary. The tester and the programmer can be independent ofeach others work. Black-box test design treats the system as a"black-box", so it doesn't explicitly use knowledge of the internalstructure. Black-box test design is usually described as focusingon testing functional requirements.

Black Box testing in our application attempts to find errorsin following categories

Incorrect or missing functions

Interface errors

Errors in data structure or external database asses

Behavior or performance errors

Installation and termination errors


68/87

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.


69/87


70/87

TEST REPORT


71/87


72/87


73/87

Relationship


74/87

Database Names

Name of the Tables:

1. CUSTOMER2. PAPERS3. MAGAZINE

4. TRANS_PAPERS5. PAYMENT6. BILLS7. TRANS_MAGZINE8. PAPERPATTERN


75/87

Table Information

Table I

(a) INFORMATION:

Name : CUSTOMERNo. of fields : 11Description : This table stores the Customer record

Associated by the FIRM.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size1 CustId Text Primary

Key50

2 LineId Text PrimaryKey

50

3 Cname Text -- 504 CAddress Text -- 100

5 ContactPerson

Text -- 25

6 TelNo Number -- 117 Mobile Number -- 108 Fax Number -- 119 DateOfJoinin Date/Time -- 8


76/87

g10 Balance Number -- 1511 After Number -- 15

Table II

(a) INFORMATION:

Name : PAPERSNo. of fields : 9Description : This table stores the Paper providedby the

Firm.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size1 PId Text Primary

Key50

2 PName Text -- 503 PMonCos Number -- 54 PTueCos Number -- 55 PWedCos Number -- 5

6 PThuCos Number -- 57 PFriCos Number -- 5


77/87

8 PSatCos Number -- 59 PSunCos Number -- 5

Table III

(a) INFORMATION:

Name : MAGAZINENo. of fields : 3Description : This table shows the Magazine

provided by The Firm.

(a) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size1 MId Text Primary

Key50

2 MName Text -- 503 MCos Number -- 5

Table IV

(a) INFORMATION:


78/87

Name : TRANS_PAPERSNo. of fields : 6Description : This table shows transaction of thepapers.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size1 TransId Text Primary

Key50

2 CustId Text PrimaryKey

50

3 Pid Text -- 504 DateofSub Date/Time -- 105 NoofSub Number -- 5

6 P_U_Cos Number -- 10

Table V

(a) INFORMATION:

Name : PAYMENTNo. of fields : 11Description : This table shows transaction of thepapers.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint FieldSize

1 PayId Text Primary Key 502 CustId Text Foreign Key 503 DoB Date/Tim

e

Foreign Key 50


79/87

4 BillNo Number Foreign Key 105 BillAmount Number -- 10

6 PaidAmount Number -- 10

7 DofPayment Date/Time -- 8

8 ModeofPay Text -- 209 BDatFrom Text -- 810 BDatTo Text -- 811 Balance Number -- 15

Table VI

(a) INFORMATION:

Name : BILLSNo. of fields : 6Description : This table shows the Bills recordsprovided

By the firm.

(b) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size


80/87

1 Bid Number PrimaryKey

50

2 BlData Text PrimaryKey

50

3 StartD Text -- 504 EndD Text -- 105 StBillNo Number -- 5

6 EnBillNo Number -- 10

Table VII

(a) INFORMATION:

Name : TRANS_MAGAZINENo. of fields : 6

Description : This table shows transaction of themagazine

(b) DESIGN:


81/87

Sr.No. Field Name Data Type Constraint Field Size1 Id Text Primary

Key50

2 CustId Text PrimaryKey

50

3 Mid Text -- 204 DoSub Date/Time -- 85 NoSub Number -- 5

6 PuCost Number -- 10

Table VIII

(a) INFORMATION:

Name : PAPERPATTERNNo. of fields : 4Description : This table shows transaction of themagazine

(a) DESIGN:

Sr.No. Field Name Data Type Constraint Field Size1 Refid Number Primary

Key50

2 Patid Text PrimaryKey

50

3 Pid Text -- 204 Noofsub Number -- 8


82/87

Future Enhancement

We going to convert our system to website,so that customer can interact with us by visit ingour website.


83/87

Due to onl ine website the customers cancheck for newly launched market offers avai lable,onl ine subscript ion & and complaint box service etc.


84/87

List Of Abbreviations


85/87

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


86/87

References


87/87

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.0Authors: Julia. Case BradleyPublisher: TATA-McGraw HILL

Book: SQL Complete ReferenceAuthor Name: Groff WeinbergPublisher: TMH

Web Sites:

www.yahoo.comwww.google.com
http://www.yahoo.com/http://www.google.com/http://www.yahoo.com/http://www.google.com/

share accountin systems

Documents