GSTproject2 D

[Year]
GOVERNMENT POLYTECHNIC RAJKOT
INFORMATION TECHNOLOGY DEPARTMENT
Project Report
On
GST Billing System
Prepared by :- Guided by :-
Jethva Dharmishtha P. (176200316039) M.T. VASA MEM
Chauhan Kajal H. (176200316016)
Chaniya Mustak U. (176200316014)
GST Billing System (Web Application) Page 1

NEAR AJI DAM CHOWK, BHAVNAGAR ROAD, RAJKOT-360002
th
This is to certify that JETHVA DHARMISHTHA P. student of 6 semester
Diploma in Information Technology has successfully completed the project entitled “
GST Billing System ” for the subject PROJECT II.
Head of Department:- Internal Guide: -
S. K. Paryani M.T. VASA MEM

th
This is to certify that CHAUHAN KAJAL H. student of 6 semester

th
This is to certify that CHANIYA MUSTAK U. student of 6 semester

ACKNOWLEDGEMENT
It is our pleasure to take this opportunity to thank all those who helped us directly or indirectly
in completion of this project.
We are heartily thankful to our project guide M.T. VASA, all faculty members of the
department of information technology in government polytechnic college Rajkot, for making
our project a grand success for us. This project would have been impossible without their
unwavering encouragement and trust in our ideas. They were always their unwavering
encouragement and trust in our ideas. They were always available for discussion whenever we
struggled and always found a way to guide us out of any situation. The discussion about the
project and the valuable advises given by them helped to make this project complete. We are
indebted to them for the pristine and enlightening guidance given to us throughout the semester.
We express our immense gratitude to our internal Project guides, for their encouragement,
guidance, understanding and lots of support and trust without which this project would not be a
success.

CHAPTER 1
ABSTRACT
 The purpose of the Online GST (Good and Services Tax) Billing is to automate
the existing manual system by the help of computerized equipment and full-fledged
computer software, fulfilling their requirements, so that their valuable data\information
can be stored for a longer period with easy accessing and manipulation of the same. The
required software and hardware are easily available and easy to work with.
 Online GST Billing, as described above, can lead to error free, secure reliable and
fast management system. It can assist the user to concentrate on their other activities
rather to concentrate on the record keeping. The Organization can maintain
computerized records without redundant entries. That means that one need not be
destructed by information that is not relevant, while being able to reach the information.
INTRODUCTION
1.1 PROJECT SUMMARY
In this Online GST Billing in our project managed all the information about
customer GST product, product type etc.
1.1.1 PURPOSE OF PROJECT

This Project we will prepare for our knowledge. This project has been the most
practical andexisting part of our learning experience and our own ideas, which would
be asset for our future carrier. The main purpose of our project is customer get easily

all the information about GST. We have created project (PHP and SQL). We have
prepared a project “Online GST Billing” we have covered all the GST information.
1.2 GOALS AND OBJECTIVES
1.2.1 GOALS
The Good and Services Tax (GST) is a value added tax levied on most goods and
services sold for domestic consumption. The GST is paid by consumers, but it is
remitted to the government by the business selling the goods and services. In effect,
GST provides revenue for the government.
1.2.2 OBJECTIVES
The good and services Tax which is being implemented from 1st July, 2017 is
proposed to be a unified tax for the entire nation. The intended objective of GST 2017 is
to replace a lot of other indirect and direct taxes like the VAT, service tax, luxury tax
etc.
GST (Good and Services Tax) rate is proposed to be 27% which is far higher
than the global standard of 16.4% for similar taxes, our finance minister, Mr. Run jaitely
on several occasions has mentioned that the rate is way too high.
 Ensuring that the cascading effect of tax on tax will be eliminated.

 Improving the competitiveness of the original goods and services, thereby
improving the GDP rate too.
 Ensuring the availability of input credit across the value chain.
 The main objective of the project on Online GST Billing is to manage the details
of product, product type, GST product, customer, and category.
It manages all the information about product, system user, category, and
product. The project is totally built at administrator end and thus only the

administrator is guaranteed the access. The purpose of the project is to build an
application program to reduce the manual work for managing the product, product
type, system user, GST product; it tracks all the details about the GST product,
customer, and category.
1.3 SCOPE
Under GST, supply is considered a taxable event for charging tax. The liability to
pay tax arises at the time of supply of goods or services.
 What is supply under GST

 Elements of supply
 Classification of supply and types
 The scope of supply: List of supplies and taxability.

CHAPTER 2
Project Management
2.1 Planning and scheduling
Good planning depends largely on project manager’s intuition and experience!
 Split project into tasks.

— Tasks into subtasks etc.
 For each task, estimate the time.

— Define tasks small enough for reliable estimation.
 Significant tasks should end with a milestone.
2.1.1 Process paradigm& Justification
The registration, payment and refund processes under GST will be routed through a
centralized common porter set up by GSTN. The common porter will act as interface
between the taxpayers, authorities, banks, RBI and accounting authorities.
At the back-end, the porter will be integrated with the it system of the central and state
government. The GSTN will be linked to the government database to verify the data submitted
on the GST porter by the taxpayer at the time of registration or filing of returns.

Diagram:

Diagram :

Justification:
 It is assumed that services depicted above are business (B2B) services.

 Furthermore, the broad taxability has been determining on the assumption that the
service provider has obtained registration in each state where the services are deemed to
be supplied.
 The tax implication has been determined on the assumption that the place of supply for
the T&L sector will be the location of the service recipient.

2.1.3 Milestones & Gantt Chart
Milestone = A verifiable goal that must be met after task completion
Clear unambiguous milestones are a necessity!
Monitor progress via milestones
 Sometimes there are events externals to your project that you want to track. If you cannot
link to them because they are not in project plan you can create a milestone to represent
them in your own project.
 Milestone shows tasks of the project. Design is the milestone of the project & Coding is
another milestone.
 Some milestones may need duration. For example, your project has an approval milestone
at the end of a phase and you know that the approval process will take time nr. About a
week.

System Analysis: - Jethva Dharmishtha
Chaniya Mustak
Chauhan Kajal
System Design: - Jethva Dharmishtha

Chaniya Mustak
Chauhan Kajal
Database Design: - Jethva Dharmishtha

Chaniya Mustak
Chauhan Kajal
Form Designing: - Jethva Dharmishtha

Chaniya Mustak
Chauhan Kajal
Coding: - Jethva Dharmishtha

Chaniya Mustak
Chauhan Kajal
Testing: - Jethva Dharmishtha

Chaniya Mustak
Chauhan Kajal

 WEEK 1: Introduction
 WEEK 2: Requirement Listing.
 WEEK 3: Roles & Responsibility Analysis.
 WEEK 4: Detailed study of Project.
 WEEK 5: Database design.
 WEEK 6: Creation of DFD diagram, design phase.
 WEEK 7: Development of basic application using PHP.
 WEEK 8: Start with analysis & decide the flow of the project.
 WEEK 9: Testing of Online Optical.
 WEEK 10: Documentation of Online Optical.

Gantt chart:

2.1.4 Schedule Representation
 First schedule: Activities to be treated as supply even if made without
consideration.
 Second schedule: Activities to be treated as supply of Goods of services.
 Third schedule: Activities/Transections which shall not be treated as supply of Good
or services.

CHAPTER 3
Literature Survey :
Srinivas K. R (2016) in his Article “issue and challenges of GST in India” he has
specified that focal and state governments are engaged to collect individual duties according
to the Indian constitution which is probably going to change the entire of present aberrant
tax collection structure [1].
Girish Garg in year (2014) has specified about Goods and service Tax in this article. He
communicated the India of GST. Its difficulties, opening, highlight and effect on India,
which finishes up, GST as a greatest expense changes in India that build the assessment
accumulations and upgrade general development of the economy [2].
Monika Sehrawat and Upasana Dhanda in year (2015) clarified that usage of GST
collection approach it would be allocated similarly assessment creation and administrations
with least assessment rate which result in expended the duty base and limited the exception.
It estimated to help in building up a powerful and adaptable expense administration [3].
Ekta Nurala and priyanshi rastogi in year (2016) have clarified that the primary point of
GST is to streamline the current roundabout duty framework with a solitary expense of
utilization of products and ventures make and deals. It is acknowledged worldwide and
around 140 nations of the world are following the GST law. it will be connected on
merchandise and enterprises at each phase of worth to be added to the products which
incorporates all backhanded duties of focal and state government. Use of GST in India will
bring about the development of economy and lift the general GDP of the country [4].

Review of literature:
 Empowered Committee of Finance Ministers (2009) introduced their First Discussion

Paper on Goods and Services Tax in India Which analyzed the structure and loopholes if
any in GST.
 Indirect Taxes Committee of Institute of Chartered Accounts of India (ICAI) (2015)

submitted a PPT naming Good and Services Tax (GST) which stated in brief details of
the GST and its positive impact on economy and various stakeholders.
 The Institute of Companies Secretaries of India (ICSI) (2015) published a Reference on

Good and Service Tax to provide the information on the concept of GST in details.
 Sijbren (2013): Sijbren and others suggested, a modern goods and services to alleviate
the problem of India ‘s current indirect tax system.

CHAPTER 4
System Requirements Study
4.1 User Characteristic:

There are two types of user in this system the highest level of user is the Administrator
who reserves all
the right of administrative work in the news website.
4.1.1 Administrator:
 Administrator will be given a unique ID and password to login.
 Admin can insert, update and delete products which is displayed to the end user.
4.2 Hardware and Software Requirements:
HARDWARE REQUIREMENT
System : Pentium – 4 or More
Hard disk Drive : 10 GB or More
Base Memory Size : 16 MB or More
Monitor : VGA Color Monitor
Printer : Inkjet Printer
SOFTWARE REQUIREMENT
Operating System : Windows XP / Vista
Front – End : Php
Back – End : Sql Server 2010

CHAPTER 5
System Analysis
5 .1 Study of Current System
5.1.1 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM
1) Current system is a manual system.

2) Currently Administration process is little slow but we have tried to minimize it to its
maximum.
3) More paper work has to be done to maintain all activities.
5.2 REQUIREMENTS OF NEW SYSTEM
FUNCTIONAL REQUIREMENTS
In this portion, we discover all the functionality of our system according to end –
user need like:
 Allow the user to maintain all his/her information.

 Assign/update/delete record for particular user which will be very helpful in
identifying.
 The user should be able to share his/her profile in the system.
 The system should be able to access the profile and other related information.

NON – FUNCTIONAL REQUIREMENTS
 System should be user friendly.

 System should be reliable, accurate and specific.
The quality in software development process is by periodic reviews
documentation and
verification at all appropriate stage. Software engineering followed throughout the process
of development of
system. The quality in software product is ensured by embedding following quality
attributes in software
package. These attributes are readability, modularity, modifiability, portability,
maintainability, proper
error reporting.
 There is also risk of unauthorized access. So in this system we give

appropriate username and password.
 The application is highly interactive with database at each and every point of
addition, deletion and updating of record. The following diagram would be
better way to show the qualities of the system. The various features such as
implementation, reliability, scalability is shown as in the form of diagrams.

5.3 Function of System
5.3.1 The Use Case Diagram Of Whole System

ER-Diagram

5.5 Activity Diagram

Chapter 6: System & Database Design
System Design
6.1 PACKAGE DIAGRAM:
A package diagram in unified modeling language depicts the

dependencies between the packages that make up the model.
In addition to standard UML dependency relationship, there
are 2 special types of dependencies between packages :
Packet Import
Packet Merge
Packet Import is “the relationship of importing the namespaces

and packages, package to its own namespace.” By default, the
unlabeled dependencies between two packages are interpreted as a
package import relationship. In this relationship the target within
the package will be imported in the source package.
Packet Merge is the direct relationship between that indicates
the content of two packages which are to be combined. It is
very similar to generalization in the sense that the source
element conceptually adds the characteristics resulting in an
element that combines the characteristics of both.
In this relationship if the element exists within both, the source
package and the target package, then source elements definition
will be expanded to include the target elements definition.

[Fig 5.1 Package Diagram]
6.2 COMPONENT AND DEPLOYMENT DIAGRAM
A component is the structured class representing a modular part of the system

with encapsulated content and whose manisfacitation is replaceable within the
environment.
A component has its behavior defined in terms of provided interface and

required interfaces.
A component serves as the type whose conformance is defined by these

provided and required interfaces. (Encompassing there both semantics). One
component can therefore be substituted by another only if two are the type
conformant.
Large pieces of systems functionality may be assembled by reusing the

components, and wiring together their required and provided interfaces.
A component is modeled throughout the development life cycle and successively

refined in development and runtime. A component may be manifested by one or
more artifacts.
Indirectly instantiated component is defined at the design time but does not exist
as the addressable object at execution time. Runtime behavior if the components
and its ports are defined by the runtime behavior of the classifiers of parts realizing
it. Several standard stereo types assume attributes for example: <<specification>>,
<<subsystem>>, <<focus>>.

Internals of components are hidden and inaccessible other then provided by its interfaces.
Although it may be dependent to other elements in terms of interfaces that are required, a
component is encapsulated and its dependencies are defined such that it can be treated as
independently as possible. A component is shown as the classifier with the keyword
<<component>>.
6.3 DATABASE DESIGN/DATA STRUCTURE:
5.3.1 Tables Description:
CUSTOMER:
Field Data Type Constraints
Cuid Integer Auto Increment
Cuname String Not null
Statusid Integer Foreign key
Address String Not null
City String Not null
Zip code Big int Not null
State String Not null
Country String Not null
Contact person String Not null
Phone Big int Not null
Mobile Big int Not null
Email String Not Null
Ptid Integer Foreign key
Panno Integer Not null
Gstno Integer Not null
Note Text Not null
ADD UNIT :

Unid Integer Auto Increment
Unit name String Not null

CITY:

Ctid Integer Auto Increment
CT name String Not null
Sid Integer Foreign key
COMPANY PROFILE :

Cpid Integer Auto Increment
Cpname String Not null
Address Text Not null
Zip code String Not null
phone1 String Not null
phone2 String Not null
Fax no String Not null
Mobile no String Not null
Email String Not null
Gstno String Not null
Panno String Not null
Bank detail String Not null
COUNTRY :

Ctid Integer Auto Increment
Cname String Not null

DELIVERYMODE :

Dmid Integer Auto Increment
Dmname String Not null
Spcost String Not null
ITEM:

Iid Integer Auto Increment
Itid Integer Foreign key
I name String Not null
Igid Integer Foreign key
Unid Integer Foreign key
Sprice String Not null
Minstock String Not null
ID detail Text Not null
Statusid Integer Foreign key
ITEMGROUP :

Igid Integer Auto Increment
Igname String Not null

ITEMTYPE :

Itid Integer Auto Increment
Itname String Not null
PAYMENT_TERMS:

Ptid Integer Auto Increment
Ptname String Not null
REGISTER :

Uid Integer Auto Increment
Uname String Not null
Password String Not null
Mobile String Not null
Image String Not null
cid Integer Foreign key
Sid Integer Foreign key
Ctid Integer Foreign key
STATE :

Sid Integer Auto Increment
cid Integer Foreign key
Sname String Not null

STATUS :

Statusid Integer Auto Increment
Status String Not null
SUPPLIERS:

Spid Integer Auto Increment
Spname String Not null
Spcode String Not null
Zip code Big integer Not null
Contact person String Not null
phone1 Big integer Not null
phone2 Big integer Not null
Fax no Big integer Not null
Mobile no Big integer Not null
Ptid String Not null
WAREHOUSE :

Wid Integer Auto Increment
Wname String Not null
6.4Normalization
Database normalization is the technique of organizing the data in the database. It is

the systematic approach of decomposing data tables to eliminate the data redundancy
and undesirable characteristics Insertions, pupations, deletions alnamolies.
It is a multistep process that puts data into tabular form by removing the
duplicated data from the relation table. Normalization is used mainly for 2
purposes
Eliminating the redundant, useless data

Ensuring the data dependencies makes sense i.e. data is logically stored.
Normalization rule is divided into following
normal forms First normal form

Second normal form
Third normal form
BCNF
6.3.1 First Normal Form:
As per the first normal form no two rows of data can contain the similar information
i.e. each room must contain the unique information such that multiple columns cannot
be fetched when the queries are fired. Each table must be dividing into multiple rows
and each row must have the primary key that distinguishes it as the unique value
6.3.2 Second normal form:
Primary key is usually single column, but sometimes more than one column can be
combined to create the primary key. As per the second normal form there must not
be any partial dependencies of any column on the primary key. that means for the
table that has concatenated primary key, each column in the table that is not the
part of primary key must depend upon the concatenated for concatenated key for
existence. If any columns depend on only one part of consented then table fails
second normal form.
6.3.3 Third normal form:
Third normal form applies that every non-prime attribute of the table must depend
on the primary key, or else we can say that there should not be any case that non-
prime attribute is determined with another non-prime key attribute. So this
transitive functional dependency should be removed from table and also table must
be in second normal form.
6.3.4 BCNF:
Boynce and cod normal form is the higher version of third normal form. This form
deals with certain types on anomaly that are not handled in third normal form. A
3NF table that does not have the multiple overlapping candidate keys is said to be
in BCNF

6.5 INPUT/OUTPUT AND INTERFACE DESIGN:
6.5.1 MAIN MODULES OF NEW SYSTEM:
 Client:
It can login
It can store the company information
It can store the stock information
It can store the customer information
it can store the warehouse information
It scan calculate the GST
6.5.2 SELECTION OF HARDWARE AND SOFTWARE.
[Table 6.5.2.1 Hardware Selection]

6.5.2.1 Software Selection:
[Table 6.5.2.2 Software Selection]
SCREENSHOTS
Log in page

Add company :
Items :

CHAPTER 7
IMPLEMNETATION
IMPLEMNETATION
7.1 Implementation environment:
Challenges Identified for successful design and implementation of this project are
dominated by: complexity, reliability, transparent data access while respecting
security. The Project was a result of group consensus
The team was having only one member and a guide. The team structure depends on
the management style of the origination, the number of people in the team, their skill
levels and the problem difficulty.
After completion of each module, a module testing was performed to test the system.
testing was performed on each when the development was completed, system
7.2 PROGRAM/ MODULE SPECIFICATIONS
One main module is dealing with this application

 User
The user module is the main module in our system. User can maintain and visualize
all the records of user and this module can be used by certain users like hostel owners
etc. They can use this by using their respective Use rid and password details.
The employee or user module is another module of the system. Here user has to first
register in web application and then they can login through his/her user id and
password. After words will be to access all functionality of the application. All user
functionality resides within this module a kept intact intentionally from the main admin
module
7.3 SECURITY FEATURES:
Our System provides different level of security.

Here user have unique username and password.
User has right to block any user.
All users also have security like unique user_id and password along with the security
question and answer which can be used for recovery purpose.
The Transaction between pages is done in encrypted way so user never knows the
flow of control and flow data in the application.

7.4 CODING STANDARS:
Normally, good software development organization requires their programmer to add

here to some well-defined and standard style of coding called coding standard.
The Software needs to be updated from time to time according the changing needs of
Users. So some standards are to be maintained in implementation and Coding, so that
if the software needs to be modified due to some changes in User needs or some
enhancements to be done, then it’s easy for the person to find some specific modules,
pages, functions, variables or even the tables or stored procedures in the database.
This type of naming standards is called as “Naming Conventions”. It is very useful to
reduce user errors and also ease the search process to find required information like
variable, procedure, etc.

CHAPTER 8
RESULT ANALYSIS
TESTING
Various parameters like implementation environment, program modules and coding

standards are explained in previous chapter while this chapter is aimed to provide
brief account of testing the software.
There are two principal motives of testing the software
1. To rectify the error in execution

2. To check the viability of software
The testing ensures that the software is according to the required specification.
Standards and performs the task meant for it. The testing is done by our in house
employee that act as novice user and test the application with all possible way to find
the bugs and error as well as check validation.
8.1 TESTING PLAN:
Testing is carried out at the following three stages:

Design
Implementation
Coding
8.1.1 Design Testing
 The design errors are to be rectified at the initial stage. Such errors are very difficult
to repair after the execution of software.
8.1.2 Implementation Testing
 The errors occurred at this stage can’t be overlooked because such errors do not allow
the further process.
8.1.3 Coding Testing
 The coding procedure plays significant role in software designing. The improper coding
of any software can generate inconsistent results. Such errors may occur due to
incorrect syntax or false logic. If the errors at coding stage remain unnoticed may give
rise to grave failure of the system.

8.2 TESTING STRATEGY:
A strategy for software testing integrates software test case design method into a well-
planed series of steps that result in the successful construction of the software.
The strategy provides the roadmap that describes the steps to be conducted as a part of
testing, then these steps are planned and then undertaken, and how much effort, time
and resource will be required.
We have tested our whole system using bottom up testing strategy.
Bottom up testing involves integrating and testing the modules to the lower levels in
the hierarchy, and then working up hierarchy of modules until the final module is
tested.
Bottom up testing strategy shows how actual testing is to be done with whole system
but it does not show any detail about each module testing.
For each module testing we have decided to test each lower level module with white
box testing strategy.
When all modules are tested successfully then I will move to one step up and
continue with white box testing strategy.
When all modules will be tested successfully then I will integrate those modules and
try to test integrated system using black box testing strategy.
Why Black Box Testing in my Project?
In our project whatever I have implemented was going to be tested by internal guide
Mr. Amit Parmer without knowing our code, so there was a black box testing
involve directly.
Why White Box Testing in my Project?
During the project I was making the applications, I knew how it should proceed
internally; I needed to Debugging also for testing our small functionalities.
Why interface Testing in our Project?

We examined the code to be tested and explicitly list each call to an external component.
In the system, standards test for GUIs have been performed, which are as follows:
Testing the screen control for its position and side.
The position and the related labels for all controls were checked.
Name of the form in system is given appropriately.\
All menu functions and sub functions were verified for correctness.\
Validations for all input were done.
Whether the system prompts the user with appropriate message all required fields aren’t
left blank.

8.3 TESTING METHODS
8.3.1 Unit Testing
 The unit testing is meant for testing smallest unit of software. There are two
approaches namely bottom-up and top-down. In bottom up approach the last module
is tested and then moving towards the first module while top down approach reverses
the action. In present work we opt for the first one.
8.3.2 Integration Testing
 The integration testing is meant to test all the modules simultaneously because it is
possible that all the modules may function correctly when tested individually. But
they may not work altogether and may lead to unexpected outcome.
8.3.3 Validation Testing
 After the integration testing software is completely assembled as a package,

interfacing error have been uncovered and corrected, and then validation testing may
begin. Validation can be defined in many ways but a simple definition is what a
validation succeeds when software functions in a manner that can be reasonably
accepted by the user.
8.3.4 Storage Testing
 The database of the system has to be stored on the hard disk. So the storage capacity
of the hard disk should be enough to store all the data required for the efficient
running of the system

CHAPTER 9
LIMITATION AND FUTURE ENHANCEMENT
LIMITATION AND FUTURE ENHANCEMENT
 Though we tried our best in developing this system but as limitations are mere parts
of any system so are of our system. Some limitations of “GST Billing System” are
as under:
9.1 LIMITATION
This is online application so user needs to have internet connection as well as android
supported mobile phones.
It works only on android Platform mobile phones.
9.2 FUTURE ENHANCEMENT
Right now we are creating this application at city level but in future we will try to
implement for general module so this project will work on state level.
Next step would be to make an Android of it.
And then the iOS platform will be implemented.

CHAPTER 10
CONCLUSION AND DISCUSSION
CONCLUSION AND DISCUSSION
10.1 SELF ANALYSIS AND PROJECT VIABILITIES:
During period of training at supermarket we had strictly followed standard web site
development approach, which allowed us to visualize the theoretical points that we
learned.
We have experienced the energetic and live working environment, norms and ethics.
That one has to follow, proper business procedures, planned and disciplined approach
required for the work and much more. This helped to enrich our knowledge and gain
confidence to work in such a professional organization and to deal with such corporate
world and practical situations.
While working at college we got very friendly environment by our internal guide
which was very helpful in building the confidence to develop such a project.
And most importantly we got the problem solving attitude while developing the
project.
10.2 PROBLEM ENCOUNTERED AND POSSIBLE SOLUTIONS
Problem: while started designing application we faced the designing issue like layout
should be proper in every pages and main problem we faced is layout should be same
in each size of screen whether small or large android device
Solution: Solution for above mention problem we give a weight sum that equally
divide the layout and layout should not change with the screen size is change.
10.3 SUMMARY OF PROJECT WORK
After doing this project, we have learned many things and we would like to thank all
the concerned individuals who have contributed to our precious learning.
We have also understood the importance of naming conventions and coding
conventions in development process. As our nature of the project we were following
proper steps of development properly.
In first phase, we have learned to prepare the requirement catalogue functional
specification, design specification, system development life cycle. We went on many
websites and application which are providing same facilities as our project to
understand real case scenario. In the next phase we have whole system to develop
which should be user friendly and easy to use.
We have also understood the importance of naming conventions and coding conventions
in development process. Though the project was taking too long and we faced many
difficulties which had been resolved by effective guidance of professors and our
external guide.
Every organization faces the situation in which it has to deal with vast amount of data.
Moreover, this data has to be analyzed over a long period of time. Hence not only a
Reliable storage, but proper medium to study the data is required. In our project Homeliness’,
we have succeeded in doing the same.
We are sure that we can perform better and better as we step up on the ladders of the
experience.

GSTproject2 D

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GSTproject2 D

Uploaded by

Copyright:

Available Formats

[Year]

GOVERNMENT POLYTECHNIC RAJKOT

INFORMATION TECHNOLOGY DEPARTMENT

GST Billing System

Jethva Dharmishtha P. (176200316039) M.T. VASA MEM

Chauhan Kajal H. (176200316016)

Chaniya Mustak U. (176200316014)

GST Billing System (Web Application) Page 1

Head of Department:- Internal Guide: -

S. K. Paryani M.T. VASA MEM

GST Billing System (Web Application) Page 2

Head of Department:- Internal Guide: -

S. K. Paryani M.T. VASA MEM

GST Billing System (Web Application) Page 3

Head of Department:- Internal Guide: -

S. K. Paryani M.T. VASA MEM

GST Billing System (Web Application) Page 4

GST Billing System (Web Application) Page 5

1.1 PROJECT SUMMARY

1.1.1 PURPOSE OF PROJECT

GST Billing System (Web Application) Page 6

1.2 GOALS AND OBJECTIVES

 Ensuring that the cascading effect of tax on tax will be eliminated.

GST Billing System (Web Application) Page 7

 What is supply under GST

GST Billing System (Web Application) Page 8

2.1 Planning and scheduling

Good planning depends largely on project manager’s intuition and experience!

 Split project into tasks.

 For each task, estimate the time.

 Significant tasks should end with a milestone.

2.1.1 Process paradigm& Justification

GST Billing System (Web Application) Page 9

GST Billing System (Web Application) Page 10

GST Billing System (Web Application) Page 11

 It is assumed that services depicted above are business (B2B) services.

GST Billing System (Web Application) Page 12

Milestone = A verifiable goal that must be met after task completion

Clear unambiguous milestones are a necessity!

Monitor progress via milestones

them in your own project.

GST Billing System (Web Application) Page 14

System Design: - Jethva Dharmishtha

Database Design: - Jethva Dharmishtha

Form Designing: - Jethva Dharmishtha

Coding: - Jethva Dharmishtha

Testing: - Jethva Dharmishtha

GST Billing System (Web Application) Page 15

 WEEK 2: Requirement Listing.

 WEEK 3: Roles & Responsibility Analysis.

 WEEK 4: Detailed study of Project.

 WEEK 5: Database design.

 WEEK 6: Creation of DFD diagram, design phase.

 WEEK 7: Development of basic application using PHP.

 WEEK 9: Testing of Online Optical.

 WEEK 10: Documentation of Online Optical.

GST Billing System (Web Application) Page 16

GST Billing System (Web Application) Page 17

GST Billing System (Web Application) Page 18

GST Billing System (Web Application) Page 19

 Empowered Committee of Finance Ministers (2009) introduced their First Discussion

 Indirect Taxes Committee of Institute of Chartered Accounts of India (ICAI) (2015)

 The Institute of Companies Secretaries of India (ICSI) (2015) published a Reference on