Beruflich Dokumente
Kultur Dokumente
Uttar Pradesh
India 201303
Subject Name
Study COUNTRY
Roll Number (Reg.No.)
Student Name
ASSIGNMENTS
PROGRAM: BSc IT
SEMESTER-V
: Minor Project
: Malawi
: A1922711031(el)
: Ephraim Imfaitenga
INSTRUCTIONS
a) Students are required to submit all three assignment sets.
ASSIGNMENT
DETAILS
MARKS
Assignment A
Five Subjective Questions
10
Assignment B
Three Subjective Questions + Case Study 10
Assignment C
Objective or one line Questions
10
b) Total weightage given to these assignments is 30%. OR 30 Marks
c) All assignments are to be completed as typed in word/pdf.
d) All questions are required to be attempted.
e) All the three assignments are to be completed by due dates and need to
be submitted for evaluation by Amity University.
f) The students have to attach a scanned signature in the form.
Signature:
Date :
31th December 2014
) Tick mark in front of the assignments submitted
Assignment
A
Assignment B
Assignment C
Billing System
Abstract
Billing is the critical and an integral part of any business. Some of the current methods for
ordering, billing and report production system are very slow and time consuming. For an
average user or system developer, to decide on the most suitable format for their purpose
requires knowledge of the available software, their features and how they improve the
quality of a billing and ordering system. Therefore it is very important to make the right
choice first time, while the opportunity is still open.
In this project I have outlined some basic methods currently used in related industries to
improve some of the procedures and implementations in reports production, billing and
ordering systems.
I have carried through other peoples ideas, incorporating my own opinions, to formulate
suggestions on how this could be done better than before.
Acknowledgements
I would like to thank the following people: my classmates, family, Center coordinator and
my workmates for their help in the production and compilation of this minor project:
Alufeyo Mgungwe, workmate, whose help, ideas and support throughout, this minor
project
Peter Chimbayo, Center coordinator for his opinions on how the execution of the
project go about.I take this opportunity to express my profound sense of gratitude
and respect to all those who helped me throughout this venture.
Table of Contents
1. Introduction
2. Objective
3. Project category
4. Types of Reports
5. Technologies and tools
6. Hardware
7. Future scope
8. Analysis of Present System
9. Problem of Existing System
10. Characteristic of Proposed System
11. Feasibility Analysis
i.
Need for Feasibility Study
ii.
Technical Feasibility
iii. Behavioral Feasibility
iv.
Economic Feasibility
v.
Product Perspective
12. Data flow diagram
13. Entity Relation Diagram
1. Introduction
This project titled Billing system is an application to speed up and automate the process of
ordering and billing of a Departmental store .It is a biasedly web based application
which is designed considering the chain of departmental store placed in various towns and
cities. It also administrates its users and customers
2. Objective
This project will serve among many, the following objectives:
3. Project category
The project is mostly based on the concept of RDBMS (i.e. Relational Database
Management System). A database which store data in tables form of which has some
relations .
4.Types of reports
Billing Report
Daily Sales Report
Daily Product Report
Due Date Report (Report of a particular Day)
Monthly Customer Report
6. Hardware
CPU configuration
RAM 4 GB DDR2
AMD A4-4000 Processor
Monitor: 19 color
Operating System
Windows XP
7. Future Scope
Like all other systems this billing system will remain feasible in the long run only if
it provides the solutions to the current and future needs
This project will enable us to see reports regarding product and category
This project enable shop- keeper to maintain a great database of all customer who
visited and purchased product from the shop.
This project will assist the shop keeper in fast billing.
This will be easy to maintain in future prospect.
A lot of paperwork: Existing system requires lot of paper work even on small
transaction.
A n d a g a i n t h e r e i s n o s e c u r i t y i n t h e s e n s e t h a t any
unnatural cause (such as fire in the organization) can destroy all data. Even a loss
of single paper leads to difficult situation because all the papers are interrelated
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
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 w a y that the database
can be modified.
Data sharing possible: Data can be shared in proposed system. meaning that two
or more persons can use the same data in existing system depending on rights
access t o that data. Also the two or more departments in an organization can
easily interact with each other without the actual movement of data.
i.
As per SDLC the feasibility study is carried out to verify and 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:
Pure Technical
Behavioral
Economic
The technologies and the environment which are used in this project are:
SOFTWARE
Front End
1.
Language used:
ASP.NET. This language i s u s e d b e c a u s e i t
supports event driven programming feature.
2. ADO.NET
Back end
Supporting Software: SQL Server 2013. This is used to store data in the form
of tables. Simple and very easy to use.
OPERATING SYSTEM:
Platform:
Windows XP (professional). Normally our system requires
windows operating system, which is the most and readily available operating
system.
HARDWARE:
Intel based processor-run computer system, which have mouse and keyboard as
input devices. This has been decided for its case of availability and easy to upgrade.
The various registers maintained at the different department have enough
information recording, which will help in digitizing the available data
iii.
Behavioral feasibility:
This is an evaluation of the behavior of the end users, which may directly affect the
development of the system. Many people are resistant to change and computers have 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.
In one way or another when it comes to SDLC, the personal computer user in an
organization will be affected by the proposed system. Apparently the aim of the system is to
satisfy the information needs, and no employees will lose their position by the proposed
system. In fact after the feasibility study, the proposed system will help the organization in
reducing the tedious work involved. And furthermore the involvement of users in every
stage of the project is going to increase the success factor of the new product.
Currently most of the staff is not well educated in 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 a considerable amount of attention.
This system is also feasible for organization because it supports of the organization and its
strategic plan.
iv.
Economic feasibility:
This procedure is u s e d to determine the benefits and savings that are expected
from a candidate system and compare it with the costs. If the benefits outweigh costs, then
the decision is made to design and implement the system. Otherwise further alterations are
made in the proposed system
1. Hardware and software cost
2. Manpower cost
Customer
Bill Report
Billing System
View products
Order Product
View Customer Record
Add Customer
View Order
Add
Product
m.
This
provides
Add product
Administrator
Add category
Add Category
0-LEVEL
This is the 1st -Level of DFD for the billing system in between the processes of the billing
system. It describes the flow of information. Now billing system concern with the
customers choice of product. So there is a Product processing process, the order of
customer according to the choice. The Two another processes are therefore further
processing of the order and customers information in billing system database.
Customer
Order Processing
Bill Report
Order_Details
Customer Record
Processing
Order Product
Add
View
Customer
Record
View Products
Product
Processing
Customer
Add Products/Category
1-level DFD
Administrator
Product_ID
Product_Name
Product_Category
Has Order
E-R Diagram
Product
Start
Start
Input information
Yes
Is customer
Order the
product?
Yes
Calculate the
cost of product
No
No
Enter the
products/category
Information
Display the
product list
Stop
Show to the
customer
DATABASE DESIGN
DATABASE NAME
- BILLING SYSTEM DB
_CATEGORY_MASTER
COLUMN NAME
DATA TYPE
ID
INT(PRIMARY KEY)
CATEGORY_NAME
VARCAHR(MAX)
_CUSTOMER_MASTER
COLUMN NAME
Customer_ID
Customer_Name
Customer_Address
Date
DATA TYPE
INT
VARCAHR(MAX)
VARCAHR(MAX)
DATETIME
_ORDER_DETAILS
COLUMN NAME
Customer_ID
Order_ID
Units
Price
Discount
DATA TYPE
INT
INT
INT
FLOAT
FLOAT
_PRODUCT_MASTER
COLUMN NAME
_PRODUCT_ID
_PRODUCT_NAME
ID
PRICE
STOCK
REORDER_LEVEL
DATA TYPE
INT
VARCAHR(MAX)
INT(FOREIGN KEY)
FLOAT
INT
INT
MAIN FORM
ORDER PRODUCTS
CUSTOMER MASTER
ADD CATEGORY
NEW PRODUCT
EXIT
SUGGESTION
17. Conclusion.
For designing the billing system I have used simple data flow diagrams.
In general the project teaches basically the essential skills like:
Using system analysis and design techniques like data flow diagram in designing
the system.
Understanding the database handling and query processing
I think this system gave a lot of satisfaction to me. Though every task is never said to be
perfect in this development field even more improvement may be possible in this system.
A lot of knowledge have been learned a n d gained about system development field. I
hope this will prove fruitful to me in my future endeavors to become a system analysis and
development designer
18. References
-Handbook of Relation database design by Candace C Flaming and Barbara Von Halle
Addison-Communication of the ACM vol. 13
-www.programmingsimplified .com
-Complete References in C#, BPB publications
-Computer Science C++ Sumita Arora Class VI
-Using SQL-SERVER 2000, Microsoft publication
-SQL-SERVER 2000 BPB publication