CONTENTS

Sr no. Contents

1. Introduction.

2. Objective

3. Justification and need of the system

4. Advantages of system

5. Hardware and software requirement

6. Requirement analysis for the project

7. Input and output design

8. Characteristic of system

9. Recognition of need

10. Dfd

11. Forms and coding

12. Testing

13. Result and conclusion

14. Bibliography

1
 INTRODUCTION
GST is the most ambitious and remarkable indirect tax reform in India’s

post-Independence history. Its objective is to levy a single national uniform

tax across India on all goods and services. GST has replaced a number of

Central and State taxes, made India more of a national integrated market, and

brought more producers into the tax net. By improving efficiency, it can add

substantially to growth as well as government finances. Implementing a new

tax, encompassing both goods and services, by the Centre and the States in a

large and complex federal system, is perhaps unprecedented in modern

global tax history. GST is a tax on goods and services with comprehensive

and continuous chain of set-off benefits up to the retailer level. It is

essentially a tax only on value addition at each stage, and a supplier at each

stage is permitted to set-off, through a tax credit mechanism, the GST paid

on the purchase of goods and services. Ultimately, the burden of GST is

borne by the end-user (i.e. final consumer) of the commodity/service. With

the introduction of GST, a continuous chain of set-off from the original

producer’s point and service provider’s point up to the retailer’s level has

been established, eliminating the burden of all cascading or pyramiding

effects of an indirect tax system. This is the essence of GST. GST taxes only

the final consumer. Hence the cascading of taxes (tax-on-tax) is avoided and

production costs are cut down.

2
GST Management System Java – In this project we discuss about like how

develop GST Billing System project using Java language. Most of

companies are now develop GST based android application & web

applications software. The reason was our central government strictly

follows the rules and regulations. So all of business persons are come to one

computer GST billing.

Every small grocery store also obey the government rules. Suppose if we

miss that, they file the fine. That’s the reason was all store owners. GST

(Goods & Service Tax) change so many business peoples and ordinary

persons.

It is the systematic management of Data, which is the center of existence of

almost all systems. It is one such system, the GST system that is being

catered to, here.

This software is developed to manage the bill submission process in shop or

organization. Using this system shop employee can generate bill with GST

calculation for customer for his purchase and can also print its bill copy for

customer. In Inventory Maintenance & Billing using GST system employee

can save bill & its details. Employee can submit bill of various amount. The

main propose of this Inventory Maintenance & Billing using GST system

project is developing a system that automate the bill submission and GST

calculation with bill print. In retail, wholesale shop or buy and sale goods

organization bill submission and GST billing calculation are very tiresome

3
work and maintaining the record of bill is very difficult and time consuming.

In present system, user has to work manually to maintain bill.

This system maintains regular, updated information pertaining to each

student in the records.

4
Current System:-

Currently in most of our shops or market does not use computers for performing

their daily tasks. There are a limited number of shop that use Microsoft Office

products, such as Ms. Word and Ms. Excel for performing their daily inventory

tasks. Most of them do not even have the Information that computers can make

a great difference in the way they are doing their tasks when they are

programmed to do so. In the existing system all transactions, dealings of

products, purchasing of products were done Manually which time consuming?

Reports are prepared manually as and when needed. Maintaining of reports is

very tedious task.

Problem Statement:- In today’s fast paced society, it’s very hard to be

competitive without using cutting-edge technology available in market. After

years of business, the data has grown much. It is becoming a challenge for

person to manage that data in an effective way. To be more productive in order

processing, he needs a solution which can facilitate their current processes with

use of technology and software. With increased amount of orders, it is

becoming difficult for salesperson to manage orders in effective and efficient

manner. It is very hard to go through all paper work and backtracking orders. If

there is any complain or review of any order, it takes large amount of effort and

time to backtrack and fix the problem. These results in loss of resources.

5
MANUAL HANDLING OF RECORDS RESULTS IN:

· Massive paper work.

· Cumbersome updating.

· Threat of loss of files.

· Redundancy in information storage.

· Tedious report generation.

· Anomalies due to incorrect updates.

· Requirement of excessive manpower.

Hence to enable the smooth and efficient functioning of the above

system, the automation of the system is highly recommended. This

would mean that the complete mechanization of the system, which

refers to the handling of all the records and data in a computerized

fashion.

6
How is AUTOMATION achieved?

Automation is achieved by the maintenance of a centralized database with

several files dealing with the different categories mentioned earlier. They

would provide with the central storage of data leading to several benefits for

all. The programmer would cater to all the entries and updates in the

programming concepts developed.

ADVANTAGES OF AUTOMATION

· Removal of redundancy.

· Easy availability of all required information at a glance.

· Provision of easy updates and upkeep of records thereby

decreasing anomalies and maintaince.

· Easy generation of reports.

· No scope of skipping any defaulters.

· Easy searching for any particular data required.

Hence automation would lead to the availability of precise and correct data

with increased efficiency and easy availability. The system

7
 OBJECTIVE OF THE GST SYSTEM

The main objective of the GST system is to compute the fees of a student

studying in the institution.

Also the objective includes maintenance of the records of the students in the

institute. An institute may contain hundreds of students so to keep a record

of all of them we need a system that is user friendly & easy to understand

and operate.

The objective also includes searching of a particular student easy & less

time consuming than the traditional method where the records were

maintained by hand and searching involved hours.

If you want to remove (delete the name) a particular student form the

institute by the old traditional methods then you don’t know the number of

relevant papers that the student may be having & you are not able to remove

all the papers. So this may lead to incorrect records of students in the

institute.

Updating the records of the students in the institute becomes much easier,

simpler and less time consuming.

8
· The system helps to manipulate the records of the student without

any problem & by easier methods and ways. Anyone with the

knowledge of computers, and with authentic password can make

changes in the records of the students and update them through

the systems facility.

9
 JUSTIFICATION AND NEED OF THE SYSTEM

Earlier the institute used to maintain its records of the students on

papers, which was an unreliable source so: -

· Records that were needed at a point time were not easily

available or traceable and could not be retrieved instantly or in

time.

· If records of a student are to be updated then mismatch in the

information was there as some times you may forget to update

information related to that record.

· If the records were wrongly entered then it was very difficult to

verify them.

· Searching for a particular record was a very hectic and a time

consuming process.

· Adding a new record needed all the related records also to be

updated but there used to be problems in updating all the

records.

· Traditional methods of maintaining the record was very time

consuming.

· Earlier methods were very costly and error prone.

10
ADVANTAGES OF THE SYSTEM

· There is fast retrieval of data and a lot of time is saved.

· The data is stored at a secure place, which in our case is the

Hard disk or the Floppy disk.

· The records can be easily maintained by anyone.

· The updation of the previous, existing records is easier and

simpler.

· Records can be easily added to the database and relevant

records get updated simultaneously.

11
HARDWARE AND SOFTWARE REQUIREMENTS

MINIMUM HARDWARE REQUIRED TO BUILD THE

PROJECT COMPRISES OF: -

· 100 MHz of 486 Processor

· 16 MB of RAM

SOFTWARE USED TO BUILT THE PROJECT COMPRISES OF: -

· MICROSOFT VISUAL STUDIO 6.0

· Microsoft Visual Basic 6.0

· Microsoft Office 2000

· Microsoft Access

12
REQUIREMENTS ANALYSIS FOR THE PROJECT

Analysis means identification, understanding and critically examining the

system and its parts (sub-systems) for the purpose of achieving the goals

(objectives) set for the system as a whole through modifications, changed

interrelationship of components, deleting or merging or separating or break

up of components. It may also involve upgrading the system as a whole.

Requirements analysis is usually the first phase of large-scale software

development project. It is undertaken after a feasibility study has been

performed to define the precise costs and benefits of a software system. The

purpose of this phase is to identify and document the exact requirements for

the system.

13
INPUT AND OUTPUT DESIGN
Input Design

Inaccurate input data are the most common cause of errors in data

processing. Error entered by data entry operators are controlling by

input design in this system. Input design is the process of

converting user- originated inputs to a computer – based format. In

the system design phase, expanded data flow diagram identifies

logical data flows, data stores, sources, and destination. A systems

flow chart specifies master files (database), transaction fields and

computer programs. Input data are collected and organized into

groups of similar data .Once identified, appropriate input, media

are selected for processing.

Input Data

The goal of designing input data in this system is to make data

entry as easy, logical, and free from errors as possible. In entering

data the operators need to know the following:

14
 1. The allocated space for each field. For example the

allocated space for student name must contain the

student name.

2. Field sequence, which must match that in the source

document.

When we approached input data design, we design the source

documents that capture the data and then select the media used to

enter them into the computer.

Source Documents

Source document are captured initially on original paper or a

source document. In this system the source documents are entered

into the system directly through the keyboard. The source

document is logical and easy to understand. Each area in the form

is clearly identified and specified for the user what to write and

where to write it.

15
Input Media and Device

Source data are input into the system through the keyboard and

mouse. For example if we fill the form of student details then we

use the keyboard and mouse for input the required information.

Input Design Guidelines

The design of input play very significant role in getting the correct

output. It covers all phase of input from creation of initial from

creation of input data (original recording) to actual entering the

data to the system for processing. The input design is the link that

ties the information system into the world of its users. The various

objectives of input design involving in this system are as follows:

Controlling Amount of Data

In this system reducing data requirement is a major concern. By

reducing input requirement we speed the entire process from data

capture to processing to provide results to user.

16
Avoiding Delay

When processing is delayed owing to data preparation or data

entry, the cause is called a bottleneck. To avoiding bottlenecks

when designing input is one of the objectives of this system.

Avoiding Errors in Data

The third objective deals with errors. Since the batch codes data is

inputted, there are fewer opportunities for the errors to occur for

data redundancy. In this system checking the redundancy of data

that is entered reduces error.

Keeping the Process Simple

In this system achievement of all of the objectives are mentioned in

the simplest possible manner which is user friendly. In this system

student management presents the simple process for management .

17
Major Concerns Regarding Input

Important points to be considered here are as follows:

What input is needed?

How and where is the input created?

How should the source documents be designed?

What format should be used for the input records?

What medium should be used for recording the input?

Output Design

Presenting the data processed by a computer-based information

system in an attractive and usable form has become very

essential these days.

There are three main reasons why outputs from the computer are

required in this system. They are:

18
 i. Output is required for communicating to the persons

concerned.

ii. For re-input to the computer for being concerned with

other data and further processing.

iii. For permanent storage.

Types of Output

Outputs of this system are of different forms. The most common

are reports, displays of screen, etc. Outputs of this are placed

into two categories.

Application Output

Operating Output

Application Output

These are the outputs desired out of this system to meet its

objectives. Output as a requirement to meet the objective, batch

details, students status , daily ,monthly ,yearly registration report

are the example of such output.

19
Operating Output

These outputs are mainly generated for use of student

management staff and gives various indication as to how the

system operates.

Warning messages, status indicators etc. are the example of such

output. These types of output are not concerned for the users.

Output Devices

The output devices used in the system are printers, Video

Display Units (VDUs). Printer is used to print the various types

of reports. VDUs are mainly used for displaying various input

screens.

Output Design Consideration

Output to be produced is dependent upon the following

consideration:

20
Type of User and Purpose

Generally different levels of users will have different

requirements from the system. Some want student details. Some

want batch status report.

Content

The data that are needed is included in the output. These are

related to the purpose of the output. For example a student status

report needed student registration number, and batch status

report needed batch code.

Format

This refers to the arrangement of data on the report, titles, and

headlines. In this system data arrangement, titles and headlines

are in proper format, which is user friendly.

21
 CHARACTERISTICS OF SYSTEM

The following characteristics are present in this system:

1. Organization

This system represents an organization. Organization implies

structure and order. In this system there is arrangement of

components that helps to achieve objectives. In the design of

this system, from adding the student to the institute to

generating the daily registration report represents the

organization structure. When all the components are linked

together, they work as a whole system for generating required

result.

2. Interaction

In this system each component functions with other

components. For example daily registration report is interacting

with students details, course details , batch details and payment

details.

22
 RECOGNITION OF NEED

Necessity is the mother of all inventions. Therefore first and

foremost step to develop any project is to determine what the
necessity/need of the user is, why the user needs another system
what are the drawbacks of the present system and for determining
the problem in present system requires investigation of the present
system this investigation leads to an idea about the problem and the
need of the user.

The next step is called feasibility analysis in this it is analyzed

whether the proposed system (computerized student

management system) can solve the problem and whether the

proposed system can be developed within the resources

provided by the user.

Feasibility Analysis

By feasibility analysis it can be founded whether the proposed

system meets performance requirements or not.

23
DATA FLOW DIAGRAM

24
25
26
27
28
29
30
 CODING

MODULE
// Java Program to compute GST

// from original and net prices.

import java.io.*;

class GFG

static float Calculate_GST(float org_cost,

float N_price)

// return value after calculate GST%

return (((N_price - org_cost) * 100)

/ org_cost);

// Driver code

public static void main (String[] args)

float org_cost = 100;

float N_price = 120;

System.out.print(" GST = " + Calculate_GST

(org_cost, N_price) + "%");

}
31
// This code is contributed

// by vt_m.

// Java program to validate the

// GST (Goods and Services Tax) number

// using regular expression.

import java.util.regex.*;

class GFG {

// Function to validate

// GST (Goods and Services Tax) number.

public static boolean isValidGSTNo(String str)

// Regex to check valid

// GST (Goods and Services Tax) number

String regex = "^[0-9]{2}[A-Z]{5}[0-9]{4}"

+ "[A-Z]{1}[1-9A-Z]{1}"

+ "Z[0-9A-Z]{1}$";

// Compile the ReGex

Pattern p = Pattern.compile(regex);

32
 // If the string is empty

// return false

if (str == null)

return false;

// Pattern class contains matcher()

// method to find the matching

// between the given string

// and the regular expression.

Matcher m = p.matcher(str);

// Return if the string

// matched the ReGex

return m.matches();

// Driver Code.

public static void main(String args[])

33
 // Test Case 1:

String str1 = "06BZAHM6385P6Z2";

System.out.println(isValidGSTNo(str1));

// Test Case 2:

String str2 = "06BZAF67";

System.out.println(isValidGSTNo(str2));

// Test Case 3:

String str3 = "AZBZAHM6385P6Z2";

System.out.println(isValidGSTNo(str3));

// Test Case 4:

String str4 = "06BZ63AHM85P6Z2";

System.out.println(isValidGSTNo(str4));

// Test Case 5:

String str5 = "06BZAHM6385P6F2";

System.out.println(isValidGSTNo(str5));

34
class Gst{

public static void main(String arg[]){

float amount;

float gstrate;

float gst;

float total;

System.out.println("enter the amount for GST calculation");

Scanner n=new Scanner(System.in);

amount=n.nextInt();

System.out.println("enter the Gst rate for GST calculation");

Scanner gr=new Scanner(System.in);

gstrate=gr.nextInt();

System.out.println("enter amount = "+amount+" Gst Rate = "+gstrate+"%");

gst=(amount*gstrate)/100;

total=amount+gst;

System.out.println("GST calculation");

if(gstrate==5)

35
 {

System.out.println("GST calculation in 5% ");

System.out.println("Total Gst "+gstrate+"% charge ="+gst );

System.out.println("Total Amount ="+total);

}else if(gstrate==12)

System.out.println("GST calculation in 12% ");

System.out.println("Total Gst "+gstrate+"% charge ="+gst );

System.out.println("Total Amount ="+total);

}else if(gstrate==18)

System.out.println("GST calculation in 18% ");

System.out.println("Total Gst "+gstrate+"% charge ="+gst );

System.out.println("Total Amount ="+total);

}else if(gstrate==28)

System.out.println("GST calculation in 28% ");

System.out.println("Total Gst "+gstrate+"% charge ="+gst );

System.out.println("Total Amount ="+total);

else{

System.out.println("as per indian rule gst calculate only 4 type

5%,12%,18%,28% ");

System.out.println(" you type GST RATE "+gstrate);

36
 TESTING
Testing is performed to prove that program is error free. Testing

is the process of executing a program with explicit intention of

finding errors, that’s, making the program fails. A successful

test is one that finds an error.

In order to uncover errors in the system, a series of test steps

unit, integration, validation and system level tests were planned

and executed.

The following criteria and corresponding tests were applied for

all test phases.

Interface integrity:

Internal and external interfaces were tested as each module is

incorporated into the structure .

Functional validity:

37
Tests designed to uncover functional errors were conducted.

Information content:

Tests designed to uncover errors associated with local or global

data structures are conducted.

Performance:

Tests designed to verify performance bounds established during

software design were conducted. Tests designed to verify

performance bounds established during software design were

conducted. Following are some special testing:

1. Unit Testing:- Unit testing concentrates on the smallest

unit of software design. Each unit or part of a module or

function is tested. Unit testing gives stress on the modules

independently of one another, to find errors. This helps the

tester in detecting errors in coding and logic that are

contained within that module alone. The errors resulting

from the interaction between

38
 modulesare initially avoided. The test cases needed for

unit testing should exercise each condition and option.It

can be performed from the bottom up, starting with

smallest and lowest level modules and preceeding one at a

time.

2. Module Testing:- Units combine and form module.

Module testing refers to the number of connections and

tests required between a calling and a called module. The

complexity if these connections between two or more

modules are tested. Each module separately is also tested.

When each module is tested and if each of them is

properly working then we can be ensured about the

working a whole system.

3. System Testing:- System testing is done after module

testing. System testing is designed to uncover the

weaknesses that were not found under module

testing.These weaknesses can be forced system

39
 failures and validation of the total system as it will be

implemented by its user(s) in the operational system or

environment. In system testing the total system is tested

for recovery and failure after various major failures to

ensure that no data is lost during the emergency.System

testing makes a logical assumption that if all the parts of

the system are correct, goal will be successfully activated.

Some special system tests are as follows:

(a) Peak Load Test: It determines whether the system will handle

the volume of activities that occur when the system is at the

peak of its processing demand.

Example, test the system activitating all terminals at the

same time.

(b) Storage Testing: It determines the capacity pf the system to

store transaction data on a disk or in other files. Example,

verify documentation statements that system

40
 will store 10000 records of 400 bytes length on a single

flexible disk.

(c) Performance Time Testing: It determines the length of time

used by the system to process transaction data. This test is

conducted prior to implementation to determine how long it

takes to get a response to an inquiry, makes a backup copy of

a file or send a transmission and get a response.

(d) Recovery Testing: It determines the ability of user to recover

data or restart system after failure. Example, load backup

copy of data and resume processing without data or integrity

loss.

(e) Procedure Testing: It determines the clarity of

documentation on operation and use of system by having

users do exactly what manuals request. Example, powering

down system at the end of the week.

41
4. Alpha Testing:- A developer of the system of software

foresees how the customer is going to use a program. And

there may be some errors that can remain unseen by the

developer. Thus the customer or the user is given a chance

to check whether the program is working properly or not

and also to check whether the program satisfies the needs

of the user.

The alpha test is conducted by the customer at the

developer site. The program is tested in the natural setting

with the customer. The developer checks for errors record

all the errors and usage problems in the software. As alpha

tests are conducted under the supervision of a developer

we can say that these tests are conducted in a controlled

environment.

5. Beta Testing:- Beta testing is conducted at one or more

customer site by the end user of the software. The

developer is not present with the end user. Thus

42
beta testing is not conducted in a controlled environment. All

the problems of the customer are recorded which are being

encounted during beta testing. The developer is given all

the reports at regular intervals of time. The developer of

the software makes changes in the software according to

reports which he gets from his customer. The developer

last prepares the software product as desired by the

customer and also prepares the software product for its

release in the market.

43
 CONCLUSION

In conclusion, GST and types of GST play a crucial role in the Indian

economy. The three types of GST, CGST, SGST, and IGST, are

designed to create a unified tax structure, reduce cascading of taxes,

and ensure that the tax burden is fairly shared between the Central

and State Governments.

Taxserve was very helpful for in learning about financial and

management aspect in the organization. During SIP I have gained

knowledge of GST and how actual auditing is done to findout

frauds done by seller to save tax. In this process I came that working

in an organisation and studying about working in organisation is

very different.

The results of the project are the fee receipt and the monthly fee

paid report generated by the software.

44
 BIBLIOGRAPHY
1. Krajcevski, Pavel, Srihari Pratapa, and Dinesh Manocha.
"GST." ACM Transactions on Graphics 35, no. 6 (November
11, 2016): 1–10. http://dx.doi.org/10.1145/2980179.2982439.

2. Helfer, R., and G. Taeschler. "GST." Schweizer Archiv für

Tierheilkunde 154, no. 6 (June 1, 2012): 266–69.
http://dx.doi.org/10.1024/0036-7281/a000344.

3. Hutchinson, Dan. "GST UPDATE." Australian Veterinary

Journal 78, no. 6 (June 2000): 372.
http://dx.doi.org/10.1111/j.1751-0813.2000.tb11804.x.

4. Katzman, Neil Bernard. "GST Rebates." Canadian Pharmacists

Journal / Revue des Pharmaciens du Canada 139, no. 4 (July
2006): 7. http://dx.doi.org/10.1177/171516350613900404.

5. Lasnier, Elisabeth. "Alpha GST." EMC - Biologie Médicale 1,

no. 1 (January 2006): 1–2. http://dx.doi.org/10.1016/s2211-
9698(06)76019-8.

45