0% found this document useful (0 votes)
17 views

Major project synopsis

Uploaded by

nayansigupta29
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views

Major project synopsis

Uploaded by

nayansigupta29
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 29

A

PROJECT REPORT ON
BILLING SOFTWARE
BY

VISHESH GUPTA

(0913CS201025) NISHANT KOSHTI

(0913CS201013) ASTHA AGRAWAL

(0913CS201005)

Submitted to the department of Computer Science Engineering In


partial fulfilment of the requirement
for the degree of Bachelor of
Engineering In

COMPUTER SCIENCE ENGINEERING

SRI RAWATPURA SARKAR INSTITUTION OF TECHNOLOGY & SCIENCE


DATIA (M.P.)
RAJIVGANDHI TECHNICAL UNIVERSITY, BHOPAL
JUNE, 2024
TABLE OF CONTENT

Page no.

CERTIFICATE...............................................................................................................................................ii
DECLARATION...........................................................................................................................................iii
ACKNOWLEDGEMENT..............................................................................................................................iv
ABSTRACT….................................................................................................................................................v

LIST OF SYMBOL...........................................................................................................................vi

PROJECT STATEMENT............................................................................................................................vii
SCOPE STATEMENT...............................................................................................................................viii
STATEMENT OF WORK...........................................................................................................................ix
SOFTWARE DESIGN DOCUMENT.......................................................................................................x

1. INTRODUCTION...............................................................................................xi
2. PURPOSE..........................................................................................................xii

SYSTEM ARCHITECTURE......................................................................................................................xiii
ARCHITECTURAL DESIGN...................................................................................................................xiv
SOFTWARE REQUIREMENT SPECIFICATION(SRS)........................................................................xv
PROJECT SCREENSHOT.........................................................................................................................xvi

1.1WE.................................................................................................................................................xvii
1.2FD.................................................................................................................................................xviii
1.3FV...................................................................................................................................................xix

RELATIONAL DATABASE......................................................................................................................xx
ER DIAGRAM...........................................................................................................................................xxi
BIBLIOGRAPHY.......................................................................................................................................xxii
CERTIFICATE

It is certified that VISHESH GUPTA, ASTHA AGRAWAL, NISHANT


KOSHTI
of B.Tech
VIII semester in Computer Science engineering has successfully completed the
project

work on the BILLING SOFTWARE. They have shown sincere effort and keen
interest towards his works.

I have carefully gone through the contents of the project work and I am fully
satisfied with the work carried out by the candidates.

Mr. Avinash Samuel


Guide/Supervisor
COMPUTER SCIENCE ENGINEERING
ENGG. DEPTT
DECLARATION

I hereby declare that this submission is my own work and that, to


the best of my knowledge and belief, it contains no material
previously publishes or written by another person which to a
substantial extent has the award of any degree or diploma of the
university or their institute of higher learning except where due
acknowledgement has been made in the text .

Date………………

VISHESH GUPTA
(0913CS201025) ASTHA
AGRAWAL (0913CS201005)
NISHANT KOSHTI
(0913CS201013)
Final Year B.tech
(COMPUTER SCIENCE ENGINEERING)
ACKNOWLEDGEMENT

It’s great pleasure to present this project report on “BILLING


SOFTWARE” in partial fulfilment of B.TECH programme affiliated to
RGPV, Bhopal. At the outset, I would like to express my immense
gratitude to my project guide “AVINASH SAMUEL”.

I am falling short of works for expressing my feelings of gratitude


towards him for extending their valuable guidance about market
and support for literature, critical reviews of my project report and
above all the moral support he had provided me with all stages of
this project

I would also like to thank you my friends and my entire group


member for their help and cooperation throughout the project.

Date………

VISHESH GUPTA (0913CS201025)


ASTHA AGRAWAL (0913CS201005)
NISHANT KOSHTI (0913CS201013)
Final Year B.tech
(COMPUTER SCIENCE ENGINEERING)
ABSTRACT

This stuff contains the details description about the “BILLING


SOFTWARE”. It describe its objectives, coverage, implementation,
committee and maintenance. It also shows its case study and
analysis made for this project.
LIST OF SYMBOL

* Star
_ Hyphen

= Equal
() Small braces
[] Large braces
< Less than
> Greater than
+ Addition
- Subtraction
, Comma
% Percentage
: Semi common
@ At the rate
PROBLEM STATEMENT & SCOPE STATEMENT

Problem statement
Problems that are facing by the users while managing their bills

Welcome to BIILING SOFTWARE. This project is for managing day


by day users details and making this task a piece of cake.

In old Billing systems it is very difficult to manage all details of


users. But with the help of my Billing System, it becomes very
easy to manage your details very effectively. We build this app to
make easy to store and manage the users details.
In this software you store all kinds of information like-
1. Customer Id
2. Bill No.
3. Phone No.
Project Scope

Project Title : Billing Software

Date : Prepared By :
Project Justification:

This project is basically updating the user details into a internet based
application so that the users an easily get the receipt of their products.

etc.,
Product Characteristic and Requirement :

 Secured database

 Easy To use

 Better result
Project Management Deliverables:

Project plan, research finding report, work breakdown structure, scope


statement, project charter, lessons learned report etc.,

Project-related Deliverables:

Research report, design document, software code, hardware, test plan,


project benefit measurement plan etc.,

Project Success Criteria:

Our main goal is to complete this project within allotted deadline and also

within the budget allotted. It is necessary to develop a methos for capturing

the benefits while the Billing System is being developed, tested and after it is

rolled out.

If the project takes a little longer time to complete or costs a little more
than planned, the

firm will still view it as a success if it has a good payback and helps to

promotes the firm’s image as an excellent management organization.


STATEMENT OF WORK

 Scope of Work

The Billing Software will manage different types of user


information such as phone number, email, and any other way to
contact which will be update on the platform to make a more
efficient in the upcoming days.
It will be easier for the user to store their precious information on
the Billing System.

 Location of Work

The client for this project is the user who want to save their details
to access them only the store where this billing system is present.

 Period of Performance

The duration of the project is 3.5 months. All the tasks are equally
distributed among team members to accomplish the goal of
completing the project.

 Delivered Schedule

Deliverable Date Due


Written report part 1 : Week 2

Statement of work and project


plan
Written report part 2 : Week 4
Project scope & problem
statement/ requirement
specification
Written report part 3 :
Week 7
Problem analysis & research
report
Written report part 1 :

Prototype implementation or Week 10


practical experimental work

Written report part 1 :

Review of results and statement Week 11


of findings (include test reports)

Written report part 1 :


On going assessment at
Status report and project diary supervisor meetings

 Application Standard

The project “Billing Software” follows various programming standards.

 Acceptance Criteria

The acceptance criteria for the users:


* The website has to communicate with the database
* Users can easily search the ID with in few minute
* Maintaining the account details of the users

 Additional Requirement
Qualified team members are very important. Team members
have to basic knowledge in the following areas: A knowledge in
programming languages such as HTML, CSS, Python and MySQL.
SOFTWARE DESIGN DOCUMENT

 Introduction
Software Design Document is the design work product that
formally documents the design of the software components.
Software Document gives us the detailed description about the
flow of the project.

 Purpose
Software Design Document defines the modules, interfaces and
the interaction between modules and interface. It also helps us in
giving information about how the system will look the appearance
of the user interface and the information about static ad dynamic
view of the system.

The detailed design document is the developer’s blueprint. It


provide precise direction to software programmers about how
basic control and data structure will be organized.

Typically, the detailed design document consists of table and diagram


that translate the functional specification into data structure, data
flows and algorithms.

The detailed design document is written before programming


starts. It describe how the software will be structure and what
functionality will be included. This document forms the basis for all
future design and coding.

The designer’s goal is to develop a model that achieve the


functional requirement while operating with in key constraints
such as performance goal and hardware. The main goal is create a
design which is simple, easy, understood, easily communicate and
easily built tested design.
SYSTEM ARCHITECTURE

To develop software for Billing System the architecture that we


are implement is Three Tier Architecture. The user interface,
Application logic layer and data storage layer together called as
Three Tier Architecture.

 User Interface Layer


The user Interface layer will consists of everything shown directly
to the client. This layer will communicate only with the Application
Logic Layer. This layer will also be responsible for initial validation
of any user inputted data.
Any validation that requires communication to the Data Storage Layer
will however be completed at the Logic Layer.

 Application Logic Layer


The business logic for our projects is Visual Basic. It will be
response for providing a secure connection to the Data Storage
Layer and formatting the information received from the SQL Server
for presentation to the User Interface Layer. Scripts that returns
user specific data, such as advisory stream selection will be run on
the Data Storage Layer.

 Data Storage Layer


The Data Storage Layer will record all information by the logic and
user interface layer. This data will include subjects details for the
stream and general user and admin user information. All
passwords stored in the database will be encrypted to prevent
unauthorized access. Within the data storage layer is a collection
of SQL Queries will provide access to the data in a meaningful way.
SOFTWARE REQUIREMENT SPECIFICATION (SRS)

Purpose
The main objectives of this document is to illustrate the
requirement of the project Billing System. The document gives the
detailed description of both the functional and non-functional
requirements proposed by client.

Document Convention
The following are the list of conventions used in this document and
the project as well:

 User : A general login id assigned to most users.


 Client : Intended users for the software.
 SQL Server : A server used to store data in an organized format.
 Data flow diagram : It shows the dataflow between the entities.
 User interface layer : This section pf the assignment
referring to what the user interacts with directly.
 Application logic layer : This section of the assignment
referring to the web server.
 Data storage layer : This section of the assignment referring
to where all data is recorded.
Functional Requirement

This section gives the list of Functional requirement which are


applicable to the Billing System.

 Interface Requirement
This section describe how the software interface with other
software product or users for input or output.

 User Interface
Describe how this product interface with the user.
GUI – Describe the graphical user interface if present. This section
should include a set of screen dumps or mockup to illustrate user
interface features.
Description – The user interface must be customizable by
the administrator.
Critically – This issue is essential to overall system. All the
modules provided with the software fit into this graphical
user interface and accomplish to the standard defined.
Technical Issues – In order to satisfy this requirement the design
should be simple and all the different interface should follow a
standard template.
Risks – To reduce the circumstances under which this requirement
might not able to be satisfied, all the designer must have been
developed websites previously.
Dependencies with other requirement – All the user interface should
be able to interact with the user management module and a part
of the interface must be dedicated to the module.
Non Functional Requirement

Hardware Interface

 Operating System : Window 11

 Processor : AMD RYZEN 5 5500U with Radeon Graphics 2.10 GHz

 Ram : 8 GB

 Hard Disk : 1 TB

 SSD : 256 GB

Software Interface

 Editor : Visual Studio Code

 Frontend : PYTHON

 Backend : PYTHON, Supporting MySQL

 Database : MySQL Server


ARCHITACTURAL DESIGN

Project Pages Shots


Here the user fill the necessary details over the system which will help
him in to make the bill reciept.

After enter the details, now can click the add to cart
button to generate the bill of the user
After add to cart, user will click on the generate bill button to get the right will of
their item that be purchased.

Now, the will is create as per user details, if user wants to save the bill then the user
click on the save will button.
If the user wants to the bill as a hard copy for any problem in the
future then hi click on the print button

This clear button help to clear all the details of the first user.
RELATIONAL DATA STRUCTURE
ENTITY RELATIONSHIP (E-R) DIAGRAM
BIBLIOGRAPHY

 http://www.geeksforgeeks.com
 http://www.slideshare.com
 http://www.coursera.com
 http://www.javapoint.com
 http://www.tutorialpoint.com

You might also like