Sie sind auf Seite 1von 23

Amity Campus

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

14. Data tables


15. Flow chart
16. Input forms
17. Conclusion
18. References

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:

Provides economic/financial reports to the owner monthly or weekly and lastly


yearly.
Add and maintain customer details.
Add and maintain description of new products.
Add and maintain new entered category of products.
Add and maintain records of available products.
Provides a convenient solution of billing pattern.
Make an easy to use environment for users and customers.

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

5. Technologies and Tools

Web Technology: ASP.NET (Microsoft visual studio 2013 framework 4.5)


Database:
MySQL 5.6
Development Tool: MS Visual Studio 2013
Web Server:
IIS
Web browser: Internet Explorer
Languages Used: C#.net, JavaScript
Others: Themes, CSS

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.

8. Analysis of present system


Before beginning a new system it is utmost important to critically study the system that will
be modified, improved or replaced. There is need to analyze how this system uses
hardware, software, network and the people resources to convert data resources, like
transaction data, into information products, such as reports and displays. Therefore we
should document how the information system activities of input, processing, output, storage
and control are accomplished.

9. Problem of existing system

Not user friendly:


The existing system is not user friendly because the retrieval and storing of data is
slow and data is not maintained efficiently
Inability of modification of data:
Not possible to manage huge sum of data effectively and efficiently for efficient results,
storing the details of the customers etc.
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.

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

Manual operator control:


errors.

Inability of sharing the data:


Data cannot be shared in the existing system.
Meaning 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 and strategic competitive advantages.

Manual operator control is there and leads to a lot of

10. Characteristics of the proposed system

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.

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.

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.

No or very few paperwork:


The proposed system will save some costs
because it requires very few paper works or does not require any paper work at
all. All the data is stored into the computer immediately and various bills and
reports can be generated through computers. Since all the data is kept in a database
no data of the organization can be destroyed. Moreover work becomes very easy
because there is no need to keep data on papers.

Support strategic competitive advantage: Proposed system supports strategic


competitive advantages. Since the proposed systems provide easiness in reports
generating it will provide strategic advantages among competitors.
Computer operator control: Computer operator control will minimize errors
or no errors at all. Moreover storing and retrieving of information is easy. So
work can be done very fast and in time.

11. Feasibility analysis


Title: Feasibility report for the computerization of the various activities of an
Organization.
Background: The Organization facing the problem of inconsistent and out of time
information in its activities. M o r e t i m e i s consumed for generating r e p o r t s ,
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 visits in the various
departments of the organization. The following documents and sources were looked up:

i.

The purchase order that contain items to be purchased.

The accounts register.

Purchase order issued to vendors.

Bills received from vendors.


Bills given to the customers.

Purchases return forms given to vendors.

Need for feasibility study

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

ii. technical feasibility


Technical feasibility dwells 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 80% capacity load ( an arbitrary value ), then another
application could overload the system or require additional hardware. And again if
the budget is serious constrain then the project is judged not feasible.

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

12. Data flow diagram


A data flow diagram is graphical representation that depicts the information flow and the
transforms that are applied as date moves from input to output. It can be used to represent
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 helps understanding the basic flow of data from one
process to another process. This Data Flow Diagram represents fundamental overview of
the billing system.

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

13. 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 c o n n e c t i n g d i f f e r e n t
entities a n d
r e p r e s e n t i n g m e a n i n g f u l dependencies between them
Attributes which specify various properties of entities and relations
involved in a system. .
Data Objects: A data object is a representation of almost any composite information that
must be understood by the software. By composite information, we mean something that
has a number of different properties or attributes. A data object encapsulates data only there
is no reference within a data object to operations that act on the data.

Cust_ID C_Name C_ Address

Product_ID

Product_Name
Product_Category

Has Order

E-R Diagram

Product

15. Flow chart


Flow chart is a graphical representation using symbol to show the step by step sequence of
operation, activities or procedures used in computer system analysis, activity analysis and in
program sequence representation. It presents the simple flow project.

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

Sample appearance of the snapshots of forms of the system

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