CHAPTER 1

1.1 Introduction

The project “Billing system” is an application to automate the process of ordering and
billing of a “Departmental store” .This web based application is designed considering the
chain of departmental store which is located in various cities. This application also
administrates its users and customers. In the ever-evolving landscape of business and
technology, efficient billing and invoicing systems play a pivotal role in streamlining
financial transactions, enhancing user experience, and fostering organizational growth.
The Online Billing System using Python is a robust and user-friendly solution designed to
address the challenges of modern businesses in managing their billing processes.

Key Features:

1. User Authentication:
o Secure user authentication ensures that only authorized personnel have
access to sensitive billing information.
2. Invoice Generation:
o The system facilitates the generation of detailed and customizable invoices,
allowing businesses to present clear and professional billing documents to
clients.
3. Product and Service Management:
o A centralized repository for managing products and services, enabling easy
addition, modification, or removal of items on invoices.
4. Customer Database:
o A comprehensive customer database allows businesses to store and manage
client information, fostering personalized communication and efficient
billing.
5. Payment Integration:
o Integration with various payment gateways to facilitate seamless and secure
online transactions, providing convenience for both businesses and clients.
6. Reporting and Analytics:
o Robust reporting features offer insights into financial data, helping
businesses analyze revenue trends, outstanding payments, and overall
financial health.
 7. Multi-user Collaboration:
o Support for multiple user roles and permissions, promoting collaborative
efforts within the organization while ensuring data security.
8. Automation and Reminders:
o Automated billing processes reduce manual effort and minimize errors,
with built-in reminders for upcoming payments and overdue invoices.

Goals of the System:

 Enhance the efficiency of billing and invoicing processes.

 Improve accuracy and reduce the likelihood of errors in financial transactions.
 Provide a user-friendly interface for both businesses and clients.
 Foster transparency and trust through clear and comprehensive billing
documentation.
 Enable businesses to adapt and scale their billing operations with ease.

As we delve into the development of this Online Billing System using Python, we aim to
create a solution that not only meets the functional requirements of businesses but also
sets the stage for future enhancements and adaptability in the dynamic business
environment.
 CHAPTER 2
Objective :

The objectives of an online billing system using Python can be diverse and depend on the
specific needs and goals of the organization implementing it. However, here are some
common objectives that such a system may aim to achieve:

1. Efficiency Improvement:
o Objective: Streamline billing processes and reduce manual effort.
o Explanation: Automate the generation of invoices, calculations, and other
repetitive billing tasks to increase overall efficiency and productivity.

Accuracy and Error Reduction:

o Objective: Minimize errors in billing calculations and data entry.

o Explanation: Implement checks and validations to ensure accurate billing
information, reducing the likelihood of mistakes and discrepancies.
2. Enhanced Customer Experience:
o Objective: Provide a seamless and user-friendly experience for clients.
o Explanation: Create a system that allows customers to easily access and
understand their invoices, make payments online, and view their
transaction history.
3. Financial Transparency:
o Objective: Foster trust and transparency in financial transactions.
o Explanation: Generate clear and detailed invoices, making it easy for
clients to understand charges and promoting a transparent billing process.
4. Payment Integration:
o Objective: Facilitate secure and efficient online payments.
o Explanation: Integrate with payment gateways to allow clients to make
payments electronically, reducing the reliance on traditional payment
methods.
5. Data Security:
o Objective: Ensure the confidentiality and security of billing data.
 o Explanation: Implement robust security measures to protect sensitive
billing information from unauthorized access or data breaches.
6. Adaptability and Scalability:
o Objective: Build a system that can adapt to changing business needs and
scale with growth.
o Explanation: Design the system architecture in a modular and scalable
manner to accommodate new features, changes in business processes, and
increasing volumes of transactions.
7. Reporting and Analytics:
o Objective: Provide insights into financial data for informed decision-
making.
o Explanation: Incorporate reporting and analytics features to generate
meaningful reports on revenue trends, outstanding payments, and other key
financial metrics.
8.
9. Multi-User Collaboration:
o Objective: Support collaboration among different roles within the
organization.
o Explanation: Define user roles and permissions to ensure that different
team members have the appropriate access levels and can collaborate
effectively.
10. Compliance with Regulations:
o Objective: Ensure adherence to legal and regulatory requirements.
o Explanation: Design the system to comply with relevant billing and
financial regulations to avoid legal issues and penalties.

2.2 Project category:

The project category of an online billing system using Python falls under several broader
classifications, mainly related to its functionality, purpose, and application. Below are
potential project categories for an online billing system:

1. Finance and Accounting:

 o Description: This category focuses on financial management and
accounting systems that include billing as a key component. It is suitable
for projects aiming to automate billing processes within an organization.
2. E-commerce and Retail:
o Description: Projects in this category are typically associated with online
stores or retail businesses. An online billing system can manage
transactions, generate invoices, and handle payments for products or
services sold through an e-commerce platform.
3. Business Management:
o Description: Encompassing various aspects of business operations, this
category includes projects that aim to streamline administrative tasks, with
billing being a crucial function. It may integrate with other business
management tools.
4. Web Development:
o Description: This category is relevant for projects focusing on web-based
applications. An online billing system is often implemented as part of a
web development project, utilizing technologies like Django or Flask in
Python.
5. SaaS (Software as a Service):
o Description: For projects providing billing functionalities as a service,
especially common in cloud-based solutions. This category may involve
subscription-based billing systems and can cater to a wide range of
industries.
6. Small Business Solutions:
o Description: Tailored for small businesses, this category involves projects
that offer simplified and cost-effective online billing solutions. These
systems may include basic features suitable for small-scale operations.
7. CRM (Customer Relationship Management):
o Description: In a CRM context, billing functionalities are integrated to
manage and maintain customer relationships efficiently. This category is
suitable for projects aiming to enhance customer interactions through
effective billing.
8. Payment Processing:
o Description: Projects in this category focus specifically on payment
processing solutions, incorporating billing as an integral part. These
systems are crucial for secure and streamlined online transactions.
9. Automation and Productivity Tools:
o Description: This category includes projects designed to automate tasks
and enhance overall productivity. An online billing system can contribute
to the automation of financial processes within an organization.
10. Open Source Contributions:
o Description: Projects falling under this category involve developing open-
source billing solutions that can be adopted and customized by a broader
community. Contributions to open-source billing projects can benefit
various
2.3Types of reports

There are various types of online billing systems that can be developed using Python,
depending on the specific needs and requirements of businesses. Here are some common
types:

1. Simple Invoice Generator:

o Description: Basic billing system that generates invoices for products or
services. Suitable for small businesses or freelancers.
2. Subscription Billing System:
o Description: Manages recurring billing for subscription-based services.
Common in SaaS (Software as a Service) applications.
3. E-commerce Billing System:
o Description: Integrates with an e-commerce platform to handle online
transactions, generate invoices, and manage order-related billing.
4. Point of Sale (POS) Billing System:
o Description: Used in retail environments, this system facilitates real-time
billing and inventory management at the point of sale.
5. Telecom Billing System:
o Description: Specifically designed for telecom companies to handle billing for
services such as phone calls, data usage, and subscriptions.
6. Utility Billing System:
o Description: Manages billing for utilities such as electricity, water, and gas.
Commonly used by utility companies.
7. Hospital Billing System:
o Description: Tailored for the healthcare sector, it handles billing for medical
services, treatments, and hospital stays.
8. Hotel Billing System:
o Description: Used in the hospitality industry to manage room charges,
restaurant bills, and other services offered by hotels.
9. Legal Billing System:
o Description: Designed for law firms to manage billing for legal services,
consultations, and other legal-related activities.
 10. Educational Institution Billing System:
o Description: Manages billing for educational services, tuition fees, and other
charges in schools, colleges, or training institutions.
11. Event Billing System:
o Description: Handles billing for events, conferences, and seminars, including
registration fees, ticket sales, and associated costs.
12. Online Banking Billing Integration:
o Description: Integrates billing functionalities with online banking systems,
allowing users to view and pay bills directly through their banking portal.
13. Customized Industry-Specific Billing System:
o Description: Tailored billing solutions for specific industries or businesses
with unique billing requirements.
14. Multi-Currency Billing System:
o Description: Supports billing in multiple currencies, catering to businesses
with international clients or operations.
15. Government Billing System:
o Description: Designed for government entities to manage billing for various
services and fees.

When developing an online billing system using Python, it's important to identify the specific
industry or business requirements and tailor the system accordingly. Each type of billing
system may have unique features and functionalities to address the specific needs of the
targeted domain.
 CHAPTER 3
3.1Technologies and Tools:

When developing an online billing system using Python, you'll need a combination of
technologies and tools to build a robust and functional application. Here's a list of key
technologies and tools that are commonly used in such systems:

1. Python:
o Description: The core programming language for developing the application
logic and backend functionalities.
o Usage: Backend development, server-side scripting.
2. Django or Flask (Web Frameworks in Python):
o Description: Web frameworks that simplify web development and provide
features such as routing, templating, and ORM (Object-Relational Mapping).
o Usage: Building the web application and handling HTTP requests.
3. HTML, CSS, JavaScript:
o Description: Frontend technologies for creating the user interface and
handling client-side interactivity.
o Usage: Designing and styling web pages, client-side validation.
4. Bootstrap or other Frontend Frameworks:
o Description: Frontend frameworks that provide pre-designed UI components
and layout structures.
o Usage: Enhancing the visual appearance and responsiveness of the user
interface.
5. Database (e.g., PostgreSQL, MySQL, SQLite):
o Description: Storage of data related to customers, products, invoices, and
transactions.
o Usage: Storing and retrieving data in a structured manner.
6. ORM (Object-Relational Mapping) Library (e.g., SQLAlchemy for Python):
o Description: Simplifies database interactions by mapping database tables to
Python objects.
 o Usage: Interacting with the database using Python objects instead of raw SQL
queries.
7. Payment Gateway Integration (e.g., Stripe, PayPal):
o Description: External services that handle online payment processing
securely.
o Usage: Integrating with the chosen payment gateway for processing
transactions.
8. User Authentication and Authorization:
o Description: Mechanisms to secure user accounts and control access to
different parts of the application.
o Usage: Managing user logins, ensuring data privacy.
9. RESTful API (Optional):
o Description: Provides a structured way to expose functionalities for external
integration.
o Usage: Enabling external services or applications to interact with the billing
system.
10. Version Control System (e.g., Git):
o Description: Tracks changes to the codebase, facilitating collaboration and
code management.
o Usage: Managing code versions, collaborating with a team.
11. Containerization and Orchestration (e.g., Docker, Kubernetes):
o Description: Containerizing the application for consistency across different
environments.
o Usage: Ensuring the application runs consistently in various deployment
scenarios.
12. Web Server (e.g., Nginx, Apache):
o Description: Serves web pages and manages HTTP requests.
o Usage: Hosting the application and handling web traffic.
13. SSL/TLS Certificate (for HTTPS):
o Description: Provides secure communication over the web.
o Usage: Enabling secure and encrypted data transmission.
14. Integrated Development Environment (IDE) for Python (e.g., VSCode,
PyCharm):
 o Description: Provides a development environment with features like code
highlighting, debugging, and version control integration.
o Usage: Writing, testing, and debugging Python code.
15. Testing Frameworks (e.g., pytest, unittest):
o Description: Tools for writing and running tests to ensure the reliability of the
code.
o Usage: Implementing and executing unit tests for different components.

By leveraging these technologies and tools, you can develop a scalable, secure, and feature-
rich online billing system using Python. The choice of specific tools may depend on your
project requirements, scalability needs, and the preferences of your development team.
 CHAPTER 4
Hardware requirments of this project:

The hardware requirements for an online billing system can vary based on factors such as the
scale of the application, the expected user load, and the specific functionalities it
encompasses. Here are general hardware requirements for a small to medium-scale online
billing system:

1. Server:
o Processor: A multi-core processor (e.g., Quad-core or higher) for handling
concurrent requests.
o RAM: At least 8 GB of RAM for smooth operation, with the exact amount
depending on the size of the dataset and the concurrent user load.
o Storage: SSD (Solid State Drive) for faster data access and storage capacity
based on the anticipated data volume.
2. Database Server:
o Processor: Similar to the application server, a multi-core processor is
recommended.
o RAM: Adequate RAM (8 GB or more) for handling database operations
efficiently.
o Storage: SSD for the database storage with capacity based on the expected
data growth.
3. Load Balancer (if applicable):
o Processor: Sufficient processing power to distribute incoming web traffic
across multiple servers.
o RAM: Adequate RAM to handle the load balancing tasks.
4. Network Infrastructure:
o Network Interface Cards (NICs): Gigabit Ethernet or higher for fast and
reliable communication between servers.
o Router and Switches: Quality networking equipment to ensure seamless data
flow.
5. Backup System:
 o Storage: Sufficient storage capacity for regular backups of the application and
database.
o Automated Backup Solutions: Implement automated backup solutions to
ensure data integrity and recovery options.
6. Firewall and Security Measures:
o Firewall: Hardware firewall to protect against unauthorized access.
o Security Software: Antivirus, intrusion detection, and other security software
to safeguard the system.
7. Power Backup:
o Uninterruptible Power Supply (UPS): Ensure a UPS system to prevent data
loss and system downtime during power outages.
8. Monitoring Tools:
o Hardware Monitoring Tools: Utilize tools for monitoring server health,
resource usage, and performance metrics.

o Logging Infrastructure: Implement logging mechanisms for tracking system

activities and identifying issues.
9. Scalability Considerations:
o Scalable Architecture: Design the system with scalability in mind to
accommodate growth in data volume and user load.
o Cluster Configuration: Consider a clustered or distributed architecture for
improved scalability and fault tolerance.

Software reuirments of the project

The software requirements for an online billing system using Python typically involve a
combination of development tools, frameworks, and software components. Here's a list of key
software requirements for building and running an online billing system:

1. Python:
o Description: The core programming language for developing the application
logic.
 o Version: Use a version that is compatible with the chosen frameworks and
libraries.
2. Web Framework (Django or Flask):
o Description: Choose a web framework in Python to simplify web development
and handle various aspects of the application.
o Version: Latest stable version of Django or Flask.
3. Database Management System (e.g., PostgreSQL, MySQL, SQLite):
o Description: Choose a database system to store and manage data related to
customers, invoices, and transactions.
o Version: Latest stable version of the selected database.
4. Object-Relational Mapping (ORM) Library (e.g., SQLAlchemy for Python):
o Description: An ORM library simplifies database interactions by mapping
database tables to Python objects.
o Version: Latest stable version compatible with the chosen database.
5. HTML, CSS, JavaScript:
o Description: Frontend technologies for creating the user interface and handling
client-side interactivity.
o Browser Compatibility: Ensure compatibility with popular web browsers.
6. Frontend Framework (e.g., Bootstrap):
o Description: Use a frontend framework for styling and layout to enhance the
visual appearance and responsiveness of the user interface.
o Version: Latest stable version of the chosen framework.
7. Payment Gateway Integration Library (e.g., Stripe API, PayPal SDK):
o Description: Libraries or SDKs for integrating with payment gateways to handle
online transactions securely.
o Version: Latest stable version compatible with the chosen payment gateway.
8. User Authentication and Authorization:
o Description: Implement authentication and authorization mechanisms to secure
user accounts and control access.
o Security Libraries: Use security libraries for secure password storage and session
management.
9. RESTful API (Optional):
 o Description: If needed, implement a RESTful API to expose functionalities for
external integration.
o API Frameworks: Use frameworks like Django REST Framework or Flask-
RESTful.
10. Integrated Development Environment (IDE) for Python (e.g., VSCode, PyCharm):
o Description: Choose an IDE for writing, testing, and debugging Python code.
o Version: Latest stable version of the selected IDE.
11. Version Control System (e.g., Git):
o Description: Use a version control system to track changes to the codebase,
collaborate with a team, and manage code versions.
o Repository Hosting: Choose a platform for hosting the Git repository.
12. Containerization and Orchestration Tools (e.g., Docker, Kubernetes):
o Description: Containerize the application for consistency across different
environments and for easy deployment.
o Version: Latest stable version of Docker or Kubernetes.
13. Web Server (e.g., Nginx, Apache):
o Description: Choose a web server to serve web pages and manage HTTP requests.
o Version: Latest stable version of the selected web server.
14. SSL/TLS Certificate (for HTTPS):
o Description: Obtain an SSL/TLS certificate to enable secure and encrypted data
transmission.
o Certificate Authority: Choose a reputable certificate authority.
15. Testing Frameworks (e.g., pytest, unittest):
o Description: Use testing frameworks for writing and running tests to ensure the
reliability of the code.
o Version: Latest stable version of the chosen testing framework.
 CHAPTER 5
5.1Future Scope

The future scope of an online billing system developed using Python can be diverse and may
involve enhancements, expansions, and adaptations to meet evolving business needs and
technological advancements. Here are some potential future directions and areas of
improvement for an online billing system:

1. Integration with Emerging Technologies:

o Explore the integration of emerging technologies such as artificial intelligence
(AI), machine learning (ML), and blockchain for enhanced security,
automation, and data analytics within the billing system.
2. Enhanced User Experience:
o Continuously improve the user interface and experience to make the billing
system more intuitive, responsive, and accessible to users. Implement user
feedback mechanisms for ongoing refinement.
3. Mobile Application Development:
o Develop a mobile application version of the billing system to cater to users
who prefer to manage invoices and payments on mobile devices. Ensure cross-
platform compatibility for broader accessibility.
4. Advanced Reporting and Analytics:
o Expand reporting and analytics capabilities to provide more comprehensive
insights into financial data, customer behavior, and business trends.
Incorporate data visualization tools for better data interpretation.
5. Automated Billing Workflows:
o Implement advanced automation features for billing workflows, reducing
manual intervention in routine tasks. Explore options for automated invoice
generation, payment reminders, and reconciliation.
6. Enhanced Security Measures:
o Stay updated on the latest security standards and technologies to fortify the
system against cyber threats. Implement multi-factor authentication,
encryption, and other security measures to safeguard sensitive billing data.
7. API Integrations:
 o Enable seamless integration with third-party applications, accounting software,
and other business tools through well-documented APIs. This allows for better
interoperability and a more connected business ecosystem.
8. Globalization and Multi-Currency Support:
o Enhance the system to cater to businesses with international operations by
providing support for multiple currencies, localization features, and
compliance with global financial regulations.
 CHAPTER 6

6.1ANALYSIS OF PRESENT SYSTEM:

Before we begin a new system it is important to study the system that will be improved
or replaced (if there is one). We need to analyze how this system uses hardware,
software, network and the people resources to convert data resources, such as transaction
data, into information products, such as reports and displays. Thus we should document
how the information system activities of input, processing, output, storage and control
are accomplished.

1. PROBLEM OF EXISTING SYSTEM

 Inability of modification of data:The managing of huge data effectively and
efficiently for efficient results, storing the details of the consumers etc. in such a way
that the database can be modified as not possible in the current system.

 Not user friendly:The existing system is not user friendly becausethe retrieval and
storing of data is slow and data is not maintained efficiently.

 Difficulty in reports generating: Either no reports generating in a current system or

they are generated with great difficulty reports take time to generate in the current
system.

 Manual operator control: Manual operator control is there and lead to a lot of chaos
and errors.

 Lot of paperwork: Existing system requires lot of paper work and even a small
transaction require many papers fill. Moreover any unnatural cause (such as fire in the
 organization) can destroy all data of the organization. Loss of even a single paper led
to difficult situation because all the papers are interrelated.

 Inability of sharing the data: Data cannot be shared in the existing system. This
means that no two persons can use the same data in existing system. Also the two
departments in an organization cannot interact with each other without the actual
movement of data.

 No support in decision-making: Existing system does not support managerial decision-

making
2. CHARACTERSTIC OF THE PROPOSED SYSTEM

1. Easiness in modification of data: The proposed system provides managing of huge

data effectively and efficiently for efficient results, storing the details of the
customers, employees etc. in such a way that the database can be modified.

2. User friendly: The proposed system is user friendly because the retrieval and
storing of data is fast and data is maintained efficiently. Moreover the graphical user
interface is provided in the proposed system,
which provides user to deal with the system very easily.

3. Reports are easily generated: Reports can be easily generated in a proposed

system. So any type of reports can be generated in a proposed system, which helps
the managers in a decisions-making activity.

4. Sharing the data is possible: Data can be shared in proposed system. This means
that two or more persons can use the same data in existing system provided that they
have right to access that data. Also the two or more departments in an organization
can easily interact with each other without the actual movement of data.

5. No or very few paperwork: The proposed system either does not require paper
work or very few paper works is required. All the data is feted into the computer
immediately and various bills and reports can be generated through computers. Since
all the data is kept in a database no
 CHAPTER 7

ANALYSIS

Title: Feasibility report for the computerization of the various activities of the company.

Background: The Company facing the problem of inconsistent and out of time
information in its activities. Very much time is consuming for report generation, which
is not very helpful for decision making. So we want a system, which provide immediate
information.

Method of study: The analysis procedure comprised of field trips in the various
departments of the company. The following documents and sources were looked up:

 The purchase order that contain items to be purchased.

 The accounts register.

 Purchase order issues to vendors.

 Bills receive from vendors.

 Bills give to the customers.
 Purchase return forms (if any ) give to vendors.
 CHAPTER 8

NEED FOR FEASIBILITY STUDY:

The feasibility study is carried out to test whether the proposed system is worth being
implemented. Feasibility study is a test of system proposed regarding its work ability, its
impact on the organization ability to meet user needs and effective use of resources. It is
usually carried out by a small number of people who are familiar with the information
system techniques, understand the part of the business or organization that will be
involved or effected by the project and are skilled in the system analysis and design
process.

The key consideration involve in the feasibility study are:

1. Technical
2. Behavioral
3. Economic

1. TECHNICAL FEASIBILITY

Technical feasibility centers on the existing computer system ( hardware, software etc )
and to what extent it can support the proposed system addition. For example, if the current
system is operating at 70% capacity ( an arbitrary value ), then another application could
overload the system or require additional hardware. If the budget is serious constrain then
the project is judged not feasible.
The technologies ant the environment which are used in this project are
 Front End

1. Language used: ASP.NET. We use this language is supports

event driven programming feature.

2. ADO.NET

Back end

Supporting Software: SQL Server 2005. This is used to storing data

in the form of tables. It is easy to use.

OPERATING SYSTEM:

Platform: Windows XP . Our system requires window operating

system, which is easily available.

HARDWARE:

Intel based processor-run computer system, which have keyboard and mouse as
input devices. This has been decided for its case of availability and up-gradation.

The various registers maintained at the different department have enough

information recording, which will help in digitizing the available data.

2. BEHAVIOURAL FEASIBILITY:

An evaluation of the behavior of the end users, which may effect the envelopment of the
system. People are inherently resistant to change and computers have to know to facilitate
changes and computers have to known to facilitate changes. An estimate should be made
of how strong a reaction the user staff is likely to have towards the development of a
computerized system. It is a common knowledge that a computer installation
has
something to do with turnover, transfer, retraining and changes in employee job status,
therefore the introduction of a candidate system requires special effort to educate, sell and
train the staff on new ways of conducting business.

The personal of the user organization will be affected by the proposed system. As the aim
of the system is only to satisfy the information needs, no employees will loose their
position by the proposed system. In fact the proposed system will help the organization in
reducing the voluminous work involved. Also the involvement of users in every stage of
the project is going to increase the success factor.

The staff in not well educated for running a computerized system. They are adamant in
perceiving a mechanical process of working as they have long been used to the manual
entry system. This aspect needs considerable amount of attention.

Our system is also feasible for organization because it supports of the organization and its
strategic plan.

3. ECONOMIC FEASIBILITY:

The procedure is to determine the benefits and savings that are expected from a candidate
system and compare it with the costs. If a benefit outweighs costs, then the decision is
made to design and implement the system. Otherwise further alterations are made in the
proposed system

1. Manpower cost

2. Hardware/software
Data flow diagram:

A data flow diagram is graphical representation that depicts the information flow and the
transforms that r applied as date moves from input to output. It can be used to represent a
software at any level of abstraction. In fact DFDs may be partitioned in to levels. That
represents increasing information flow and functional details.
DFDs are defined in levels with every level decreasing the level of abstraction as well as
defining a greater detail of the functional organs of the system. A zero level DFD also known
as context or fundamental system model represents the entire software elements as a single
bubble with input and output data entities which are indicated as incoming and outgoing
arrows. Data Flow Diagram help understanding the basic flow of data from one process to
another process. This 0 level DFD represents fundamental overview of the billing system

3. Entity Relation Diagram

Entity Relation Diagram represents the object relationship pairs in graphical forms thus
we can say that the primary goal of ER diagrams is represent data objects along with their
relationships.
ER model for data uses three features to describe data:
 Entities which satisfy distinct real world items in an application
 Relationships connecting different entities and representing meaningful
dependencies between them
 Attributes which specify various properties of entities and relations involved in
a system.
Customer

No

DATABASE DESIGN

DATABASE NAME - BILLING SYSTEMDB

 _CATEGORY_MASTER
COLUMN NAME DATA TYPE
ID INT(PRIMARY KEY)
CATEGORY_NAME VARCAHR(MAX)

1
_CUSTOMER_MASTER
COLUMN NAME DATA TYPE
Customer_ID INT
Customer_Name VARCAHR(MAX)
Customer_Address VARCAHR(MAX)
Date DATETIME

2
_ORDER_DETAILS
COLUMN NAME DATA TYPE
Customer_ID INT
Order_ID INT
Units INT
Price FLOAT
Discount FLOAT

3
_PRODUCT_MASTER
COLUMN NAME DATA TYPE
_PRODUCT_ID INT
_PRODUCT_NAME VARCAHR(MAX)
ID INT(FOREIGN KEY)
PRICE FLOAT
STOCK INT
REORDER_LEVEL INT
9 SNAPSHOTS OF THE PROJECT
 10 : CONCLUSION

This was our project of System Design Lab about “Billing System”.
Development of this System takes a lot of efforts from us. We think this system
gave a
lot of satisfaction to all of us.
Though every task is never said to be perfect in this development field even
more
improvement may be possible in this system.
We learned so many things and gained a lot of knowledge about development
field.
We hope this will prove fruitful to us