ISP CMS Thesis

ISP CANTEEN MANAGEMENT SYSTEM INTRODUCTION
Table of Contents
Table of Contents ......................................................................................................... 1
1. Introduction ................................................................................................................. 6
1.1. Product ................................................................................................................. 6
1.2. Project Scope ........................................................................................................ 8
1.2.1. Reason to develop this Project ...................................................................... 8
1.2.2. Scope of Project in the Market...................................................................... 8
1.3. Business Goals ..................................................................................................... 8
1.4. Document Convention.......................................................................................... 8
2. Proposed System ......................................................................................................... 9
2.1. Product Features ................................................................................................... 9
2.2. Product Characteristics ......................................................................................... 9
2.3. System Environment .......................................................................................... 10
2.3.1. System Used for the Project ........................................................................ 10
2.3.2. System Minimum Requirement to Run Properly........................................ 11
2.4. Design and Implementation Constraint .............................................................. 11
2.4.1. Front End .................................................................................................... 11
2.4.2. Back End ..................................................................................................... 12
3. System Requirements................................................................................................ 13
3.1. Functional Requirements.................................................................................... 13
3.1.1. Manage and View Category........................................................................ 13
3.1.2. Manage and View Item ............................................................................... 14
3.1.3. Manage and View Vendor .......................................................................... 15
3.1.4. Manage Purchases ....................................................................................... 16
3.1.5. Manages Returns ......................................................................................... 17
3.1.6. Manage Sales .............................................................................................. 18
3.1.7. View Graphs ............................................................................................... 19
3.1.8. View List ..................................................................................................... 19
3.2. Non Functional Requirements............................................................................ 20
1
3.2.1. Performance Requirements ......................................................................... 20

3.2.2. Safety Requirements ................................................................................... 20
3.2.3. Software Quality Assurance ....................................................................... 20
4. System Design .......................................................................................................... 22
4.1. Use Case Diagrams ............................................................................................ 22
4.1.1. Home Tab Use Case.....................................Error! Bookmark not defined.
4.1.2. Employee Tab Use Case ..............................Error! Bookmark not defined.
4.1.3. Inventory Tab Use Case ...............................Error! Bookmark not defined.
4.1.4. Purchase Tab Use Case ................................Error! Bookmark not defined.
4.1.5. Manufacturing Tab Use Case.......................Error! Bookmark not defined.
4.1.6. Sale Tab Use Case .......................................Error! Bookmark not defined.
4.1.7. Account Tab Use Case .................................Error! Bookmark not defined.
4.2. Data Flow Diagrams........................................................................................... 23
4.2.1. Company DFD ............................................................................................ 24
4.2.2. Warehouse DFD.......................................................................................... 25
4.2.3. Database DFD ..............................................Error! Bookmark not defined.
4.2.4. Log DFD ......................................................Error! Bookmark not defined.
4.2.5. User DFD .....................................................Error! Bookmark not defined.
4.2.6. Employee DFD ............................................Error! Bookmark not defined.
4.2.7. Employee Payroll DFD ................................Error! Bookmark not defined.
4.2.8. Inventory DFD .............................................Error! Bookmark not defined.
4.2.9. Purchases DFD.............................................Error! Bookmark not defined.
4.2.10. Vendor DFD .............................................Error! Bookmark not defined.
4.2.11. Manufacturing DFD .................................Error! Bookmark not defined.
4.2.12. Sales DFD ................................................Error! Bookmark not defined.
4.2.13. Customer DFD .........................................Error! Bookmark not defined.
4.2.14. Accounts DFD ..........................................Error! Bookmark not defined.
5. Database Design........................................................................................................ 26
5.1. Database ............................................................................................................. 26
2
5.1.1. Database Tables .......................................................................................... 26

5.2. Database Tables of ERP Lubricant System........................................................ 26
5.3. Database Diagram .............................................................................................. 29
5.3.1. Employee Module ........................................Error! Bookmark not defined.
5.3.2. Inventory Module.........................................Error! Bookmark not defined.
5.3.3. Purchases Module ........................................Error! Bookmark not defined.
5.3.4. Manufacturing Module ................................Error! Bookmark not defined.
5.3.5. Sales Module ................................................Error! Bookmark not defined.
5.3.6. Account Module...........................................Error! Bookmark not defined.
6. User Interface ............................................................................................................ 30
6.1. First Run Wizard .................................................Error! Bookmark not defined.
6.2. Login ...................................................................Error! Bookmark not defined.
6.3. Main ....................................................................Error! Bookmark not defined.
6.4. User .....................................................................Error! Bookmark not defined.
6.5. Employee .............................................................Error! Bookmark not defined.
6.6. Salary...................................................................Error! Bookmark not defined.
6.7. Attendance ...........................................................Error! Bookmark not defined.
6.8. Inventory .............................................................Error! Bookmark not defined.
6.9. Stock Adjustment ................................................Error! Bookmark not defined.
6.10. Price Adjustment .............................................Error! Bookmark not defined.
6.11. Transfer Stock..................................................Error! Bookmark not defined.
6.12. Vendor .............................................................Error! Bookmark not defined.
6.13. Purchases .........................................................Error! Bookmark not defined.
6.14. Vendor Payment ..............................................Error! Bookmark not defined.
6.15. Customer ..........................................................Error! Bookmark not defined.
6.16. Sales .................................................................Error! Bookmark not defined.
6.17. Customer Payment ...........................................Error! Bookmark not defined.
6.18. Account ............................................................Error! Bookmark not defined.
6.19. Transaction ......................................................Error! Bookmark not defined.
3
6.20. Report Designer ...............................................Error! Bookmark not defined.

7. System Coding .......................................................................................................... 36
7.1. Coding Techniques ............................................................................................. 36
7.2. Coding Architecture ........................................................................................... 36
7.3. Code Sample ...................................................................................................... 37
8. System Testing .......................................................................................................... 41
8.1. User Login Test Case ..........................................Error! Bookmark not defined.
8.2. Warehouse Test Case ..........................................Error! Bookmark not defined.
8.3. User Test Case .....................................................Error! Bookmark not defined.
8.4. Employee Test Case ............................................Error! Bookmark not defined.
8.5. Salary Test Case ..................................................Error! Bookmark not defined.
8.6. Attendance Test Case ..........................................Error! Bookmark not defined.
8.7. Inventory Test Case .............................................Error! Bookmark not defined.
8.8. Adjustment Test Case..........................................Error! Bookmark not defined.
8.9. Production Test Case ...........................................Error! Bookmark not defined.
8.10. Purchases Test Case........................................................................................ 44
8.11. Sales Test Case ............................................................................................... 44
8.12. Vendor Test Case.............................................Error! Bookmark not defined.
8.13. Customer Test Case .........................................Error! Bookmark not defined.
8.14. Account Test Case ...........................................Error! Bookmark not defined.
8.15. Transaction Test Case ......................................Error! Bookmark not defined.
9. Process Model ........................................................................................................... 46
9.1. Systems Development Life Cycle (SDLC) .........Error! Bookmark not defined.
9.2. Process Model Used ............................................Error! Bookmark not defined.
9.2.1. Why is used RAD Model .............................Error! Bookmark not defined.
9.2.2. Why I used AGILE Model ...........................Error! Bookmark not defined.
9.3. Rapid SDLC Approaches ....................................Error! Bookmark not defined.
9.3.1. Prototyping ...................................................Error! Bookmark not defined.
9.3.2. End User Development (EUD) ....................Error! Bookmark not defined.
4
9.4. Traditional ERP Life Cycle .................................Error! Bookmark not defined.

9.4.1. Analysis and Design Stage...........................Error! Bookmark not defined.
9.5. Agile Development .............................................Error! Bookmark not defined.
10. Conclusion ............................................................................................................. 50
10.1. Achievements ................................................................................................. 50
10.2. Obstacles ......................................................................................................... 50
10.3. Future Scope ................................................................................................... 50
10.4. Few Words in the End .................................................................................... 50
5
Chapter 1
1. Introduction
1.1. Product
This is desktop based application for Institute of Southern Punjab in which the user can
login and manage the Items. End user can login and use this system. With implementing
this project will reduce the number of man power and introduce system management. ISP
Canteen Management System will provide all types of assistance with the
 Vendors Management
 Sales Management
 Purchases Management
 Inventory Management
This system when implemented will not only save man power but also provide:
 More efficiency
 Less chances of bearing any kind of fraud
 Less data redundancy
 Faster and accurate results
 Manage the difficult and large amount of data within lesser time than before and
provide it in accountable format.
 Enhance human resource work in short period of time.
First Module is Sales in which user can order any item that is available in the Item. It has
a record keeping system where you can see the sales list.
User can search in the list in various ways such as:
1. Serial No
2. Balance
3. Total
4. Product Name
6
This System has a Purchase Module in it. Here user can order Item and keep the record of
purchase order. Purchase record list is also available.
User can search in the list by:
1. Payment
2. Balance
3. Total
4. Vendor Name
5. Product Name
6. Product Status
This System also has a Vendor management system in which you can add new Vendor and
can also update, delete and activate or de-activate and search a Vendor. Vendor List is also
available. Search is done by followings:
1. Vendor Name
2. Vendor CNIC
3. Vendor Contact
4. Vendor Address
5. Vendor Balance
This System has a Item Management System in which user can add a new product and can
also update, delete, activate and de-activate a product. Product List is also in it. User can
search a product by:
1. Product Code
2. Product Name
3. Product Category
4. Product Status
5. Product stock
7
1.2. Project Scope

1.2.1. Reason to develop this Project
There are many application of this type which are providing record keeping system for sale
and purchase for Canteen use but there is not any in use in ISP this is made with ISP
Branding. User can keep the record of sales and purchases, can manage the Item.
1.2.2. Scope of Project in the Market

There are many Canteen shops. Almost none of them is using Canteen software because
they think it useless but this software is made in such a way that it will force them to use
this software as their work load will be reduced drastically and provide many more features
such as Item Management, Sales & Purchase Management and Graph Reports and List.
1.3. Business Goals

Following will be business goals of the ERP Lubricant in future after it is implemented:
 To boost up the Process of Canteen

 To Decrease time consumption
 To Ease the Vendors
 To replace the paper work thing
 This project will manage large amount of data in short time.
 No data redundancy.
 To reduce the time consuming
1.4. Document Convention

 Chapter No in Title, Font Arial, Size 20
 Chapter Name in Heading 1, Font Times New Roman, Size 18 Bold
 Main Heading in Heading 2, Font Times New Roman, Size 16 Bold
 Sub Heading in Heading 3, Font Times New Roman, Size 14 Bold
 Paragraph in Normal, Font Times New Roman, Size 12
8
ISP CANTEEN MANAGEMENT SYSTEM PROPOSED SYSTEM
Chapter 2
2. Proposed System
2.1. Product Features
Main features of the developed system are as follows:
 Avoid from wastage of time and effort.
 Manage large amount of data with efficiency and accuracy.
 Easy to keep the record of sales.
 Easy to keep the record of purchases.
 Easy to keep the record of Item.
 Easy to keep the record of Vendors.
 Security of data is high.
 No data redundancy.
 Easy to view the details.
 Fewer complexes.
 Searching is easy.
 More reliable.
 User friendly.
2.2. Product Characteristics

There are essentially Eight Characteristics for the ISP Canteen Management System
 The 1st characteristic contains about Graphs

o Sales Purchase by Category
o Sales Purchase by Item
o Sales Purchase by Vendor
 The 2nd characteristic contains about Categories
o CRUD
9
o List
 The 3rd characteristic contains about Items
o CRUD
o List
 The 4th characteristic contains about Vendors
o CRUD
o List
 The 5th characteristic contains about Purchase
o Purchase
 The 6th characteristic contains about Return
o Purchase Return
 The 7th characteristic contains about Sale
o Sale
 The 8th characteristic contains about List
o Vendor
o Item
o Category
2.3. System Environment

2.3.1. System Used for the Project
2.3.1.1. Hardware Used
 Dell Laptop
 Core i7 Duo 2.4 GHz
 8GB RAM
 1TB Storage
 2GB DirectX 11 Supported Graphic Card
 Super Drive
2.3.1.2. Software Used

OS Related Information
 Windows 8.1 x64
 Resolution 1280x1024
10
Front End Related Information

 Visual Studio 2013
 C Sharp (C#)
 .Net Framework 4.0
 Telerik 2016 Q1 UI for Winform
 Material Skin for Android Theme
Back End Related Information

 dbForge Studio for SQL Server 4.5.70
 Microsoft SQL Server 2012
Other Software
 eDraw Max 7.9: For making diagrams for reports
 Microsoft Word 2013: For report making
2.3.2. System Minimum Requirement to Run Properly

 Intel Dual Core 2.0 GHz
 2GB Ram
 5GB Free Space
 Windows 7
 Resolution 1024x768
 .Net Framework 4.0
 Microsoft SQL Server Express 2012
2.4. Design and Implementation Constraint

2.4.1. Front End
2.4.1.1. Visual Studio
Microsoft Visual Studio is an integrated development environment (IDE)
from Microsoft. It is used to develop computer programs for Microsoft Windows, as well
as web sites, web applications and web services. Visual Studio uses Microsoft software
development platforms such as Windows API, Windows Forms, Windows Presentation
Foundation, Windows Store and Microsoft Silverlight. It can produce both native code and
managed code.
2.4.1.2. C Sharp (C#)

C# is a multi-paradigm programming language encompassing strong typing, imperative,
declarative, functional, generic and object-oriented (class-based), and component-oriented
programming disciplines. C# is one of the programming languages designed for the
11
Common Language Infrastructure. It is basically used to developed desktop based

application.
2.4.1.3. .NET Framework

.NET Framework (pronounced dot net) is a software framework developed
by Microsoft that runs primarily on Microsoft Windows. It includes a large class
library known as Framework Class Library (FCL) and provides language
interoperability (each language can use code written in other languages) across
several programming languages. Programs written for .NET Framework execute in
a software environment (as contrasted to hardware environment), known as Common
Language Runtime (CLR), an application virtual machine that provides services such as
security, memory management, and exception handling. FCL and CLR together constitute
.NET Framework.
2.4.1.4. Telerik UI for Winform

Telerik UI for WinForm is a built-in user interface. Unlike other languages tools used for
make interface and layout of any application one has to select different colors and
developer gets stuck in choosing color scheme but Telerik provides built-in and systematic
and coded interfaces.
2.4.1.5. Material Skin

This is used for providing controls that act as or look as they are from android
2.4.2. Back End

2.4.2.1. dbForge for SQL Server
DB Forge Studio for SQL Server is a powerful IDE for SQL Server management,
administration, development, data reporting and analysis.
The tool will help SQL developers to manage database, speed up routine tasks, as well as,
to make complex database changes.
2.4.2.2. Microsoft SQL Server

Microsoft SQL Server is a relational database management system developed
by Microsoft. As a database server, it is a software product with the primary function of
storing and retrieving data as requested by other software applications which may run
either on the same computer or on another computer across a network (including the
Internet).
12
ISP CANTEEN MANAGEMENT SYSTEM SYSTEM REQUIREMENTS
Chapter 3
3. System Requirements
Following are the functions of the project briefly describes in this chapter. By functions
here it is meant most common used event occurring in the project. Any event or function
can have more than one course of action.
3.1. Functional Requirements
3.1.1. Manage and View Category

Identifier Any Person having access to the OS and who can open Software
can manage and view categories.
Purpose To manage and keep track of the categories of items.
Priority High.
Pre-Conditions Must be on Category Form
Post-Conditions Category is managed
Typical Course of Action
SN Actor Action System Response
1. When user clicks category tab he is shown list of System will retrieve all the
categories and fields to insert, update or delete the arrived categories
categories. information from the
database and display to
user.
2. When the person fills the fields and click add System will then enter the
button. That new category appears in the list required data in the
database and save it.
3. User when click on a category in a list. Its data System will display the
appears in the fields where user can either update data into the fields and will
or delete the data by clicking respective buttons either update or delete the
category upon click. And
then will update the list.
13
Alternate Course of Action
1. User tries to click update and delete category but System will show error
not selected the category before. message box: ‘No Item
Selected’.
2. User tries delete an category which is used in items System will show error
message: ‘Sorry we can’t.
Category is used in Items.
Inactivate the Category if
it’s not required further.”
3.1.2. Manage and View Item

can manage and view items.
Purpose To manage and keep track of the items that go in or out for the
canteen.
Priority High.
Pre-Conditions Must be on Item Form
Post-Conditions Item is managed
1. When user clicks items tab he is shown list of System will retrieve all the
items and fields to insert, update or delete the items arrived items information
from the database and
display to user.
button. That new item appears in the list required data in the
14
3. User when click on an item in a list. Its data System will display the
item upon click. And then
will update the list.
1. User tries to click update and delete item but not System will show error
selected the item before. message box: ‘No Item
Selected’.
2. User tries delete an item which is used in purchases System will show error
or sales message: ‘Sorry we can’t.
Item is used in purchase
or sales. Inactivate the
item if it’s not required
further.”
3.1.3. Manage and View Vendor

can manage and view vendors.
Purpose To manage and keep track of the vendor from whom we are
buying items
Priority High.
Pre-Conditions Must be on Vendor Form
Post-Conditions Vendor is managed
1. When user clicks vendors tab he is shown list of System will retrieve all the
vendors and fields to insert, update or delete the arrived vendors
vendors information from the
15
database and display to

user.
button. That new vendor appears in the list required data in the
3. User when click on an vendor in a list. Its data System will display the
vendor upon click. And
then will update the list.
1. User tries to click update and delete vendor but not System will show error
selected the vendor before. message box: ‘No Vendor
Selected’.
2. User tries delete a vendor which is used in System will show error
purchases message: ‘Sorry we can’t.
Vendor is used in
purchases. Inactivate the
vendor if he is not
required further.”
3.1.4. Manage Purchases

Identifier User can manage the purchases of ISP Canteen items.
Purpose To manage and view the purchases made for the canteen
Priority High.
Pre-Conditions User must be on purchase form.
Post-Conditions Purchase entry is made
16
Sr# Actor Action System Response
1. User Click Purchase Tab System Show Purchase

Form
2. User Select Vendor Vendor Info Displayed
3. Insert items in cart Add items to cart
4. Input money paid Change balance field
5. Click save button Display purchase entered

successfully
1. If no items in the cart Display no item in cart list
2. If not vendor selected Display no vendor

Selected
3.1.5. Manages Returns

Identifier Allow Users to Manage Returns for Purchases.
Purpose To manage the Return of Items to the Vendor.
Priority High.
Pre-Conditions Must be on Return Form
Post-Conditions Return is made.
17
1. User Click Return Tab System Show Return Form
2. User Enter Purchase Invoice No Invoice Detail is shown
3. User made changes in the invoice
4. Update the money given or taken Change balance field
5. Click save button Display return made

successfully
2. If not invoice entered Display enter invoice

number.
3.1.6. Manage Sales

Identifier User can manage the sales of ISP Canteen items.
Purpose To manage and view the sales made for the canteen
Priority High.
Pre-Conditions User must be on sales form.
Post-Conditions Sales entry is made
1. User Click Sales Tab System Show Sales Form
2. Insert items in cart Add items to cart
18
3. Input money paid Change balance field
4. Click save button Display sales entered

successfully
3.1.7. View Graphs

Identifier Allow to users to show detail of items, category or vendors in
graphs
Purpose To view the graphical detail of sales and purchases by categories,

items or vendors
Priority High.
Pre-Conditions User must be on Dashboard
Post-Conditions Graphs are displayed
1. Select Start and End Date
2. Click Go Display Histograms and

Pie charts
3.1.8. View List

Identifier Allow to users to show detail of sales, purchases or returns in list
Purpose To view the detail of sales and purchases or returns
Priority High.
19
Pre-Conditions User must be on List
Post-Conditions LIst are displayed
1. Select Start and End Date
2. Click Go Display List
3.2. Non Functional Requirements
3.2.1. Performance Requirements

 24 X 7 availability.
 Secure Access control.
 Error correction: Ensure users can correct errors with minimal problems. For
examples if source or destinations have been slightly miss-stated, then correction
should be easy.
 Confirmation from users before altering any data.
3.2.2. Safety Requirements
 No incorrect data insertion
3.2.3. Software Quality Assurance
3.2.3.1. Availability
This is a desktop application so it will be available as soon as computer is powered on.
3.2.3.2. Reliability
It means the extent to which program performs with required precision. This Application
is extremely secure because of its authentication system that only an authorized user can
access the system.
20
3.2.3.3. Usability
Unlike others this Application is made very user friendly has shortcuts and quick buttons
and shortcuts keys
3.2.3.4. Flexibility
It is effort required to modify operational program. Three tier architecture is used for
development has separate classes for each data objects are made so modification to one file
doesn’t affect other
3.2.3.5. Customizability
This is an ISP Canteen Management System so it has way of customization that a user can
made for its own need of business.
21
ISP CANTEEN MANAGEMENT SYSTEM SYSTEM DESIGN
Chapter 4
4. System Design
Systems design is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. Systems design could
be seen as the application of systems theory to product development.
Modeling Language
Designers are assisted be the existence of modeling languages. They can be used to express
information, knowledge or systems in a structure that is defined by a consistent set of rules.
A modeling language can be graphical or textual.
4.1. Use Case Diagrams

A UML Use Case Diagram is a diagram that describes usage behaviors of a system from
an outside user's point of view. Those usage behaviors are organized into units of use cases.
UML Use Case Notations
Following notations are used in use case
 Use Case Notation is used to describe a set of activities performed by actors on an

object. When it is completed, a use case will yield a result that can be observed
 Association Notation is used to describe a relation between an actor and a use case
where the actor is involved in the use case in someway.
 Extend Notation is used to describe an extension relation between two use cases
where one acts as the base use case and the other acts as an add-on use case.
 Include Notation is used to describe an include relation between two use cases
where one acts as the parent use case and the other acts as a child use case.
22
4.1.1. ISP Canteen Management Use Case Diagram
This use case tells how the user can use the system. User is actor here.
4.2. Data Flow Diagrams

A Data Flow Diagram (DFD) is a diagrammatic representation of the information flows
within a system, showing:
 how information enters and leaves the system,
 what changes the information,
 where information is stored.
The Notation
Processes - jobs that are done with the data. A process transforms incoming data flow into
outgoing data flow.
Data stores - files, databases, archives. They can be manual, digital or temporary.
External entities/terminators in a business or other system - other systems or people
beyond the control of the current system. These are the places which provide the
organization with data, or have data sent to them by the organization (e.g. customers,
partners, government bodies). External entities are sources and destinations of the system's
inputs and outputs.
Connecting data flows - arrows show how data flows from one place to another. Flows
that cross the system boundary are known as Input Output Descriptions. Label the arrows
with the name of the data that moves through it.
23
Here are the basic DFD shapes:
4.2.1. Level 0 DFD
This is simple Level 0 DFD with only one process.
24
4.2.2. Level 1 DFD
A more detailed version of ISP Canteen System
25
ISP CANTEEN MANAGEMENT SYSTEM DATABASE DESIGN
Chapter 5
5. Database Design
5.1. Database
Databases are designed to offer an organized mechanism for storing, managing and
retrieving information. They do so through the use of tables. If you are familiar with
spreadsheets like Microsoft Excel, you are probably already accustomed to storing data in
tabular form. It is not much of a stretch to make the leap from spreadsheets to databases.
5.1.1. Database Tables
Just like Excel tables, database tables consist of columns and rows. Each column contains
a different type of attribute and each row corresponds to a single record. For example,
imagine that we were building a database table that contained names and telephone
numbers. We would probably set up columns named FirstName, LastName and
TelephoneNumber. Then we would simply start adding rows underneath those columns
that contained the data we are planning to store.
5.2. Database Tables of ISP Canteen Management
26
27
28
5.3. Database Diagram
A database schema of a database system is its structure described in a formal

language supported by the database management system(DBMS) and refers to the
organization of data as a blueprint of how a database is constructed (divided into database
tables in the case of Relational Databases). The formal definition of database schema is a
set of formulas (sentences) called integrity constraints imposed on a database. These
integrity constraints ensure compatibility between parts of the schema. All constraints are
expressible in the same language. A database can be considered a structure in realization
of the database language. The states of a created conceptual schema are transformed into
an explicit mapping, the database schema. This describes how real world entities are
modeled in the database.
5.3.1. ISP Canteen Diagram
This modules show relationship between employee and its properties such as salary, type,
work, attendance, report, departments, advance etc
29
ISP CANTEEN MANAGEMENT SYSTEM USER INTERFACE
Chapter 6
6. User Interface
6.1. Title Bar and Main Menu
This is the main menu of the application click on an item and item related items will be
shown. Here we have Dashboard, Categories, Items, Vendors, Sales, Purchases, Returns
and List.
6.2. Dashboard Menu
When user click on the Dashboard further a Tab Menu will be shown to user can select
categories, items or vendors to see their Histogram and Pie Charts.
6.3. Categories Graphs
Categories Related Graphs Are shown here related to sales and purchases
30
6.4. Items Graphs
Items Related Graphs Are shown here related to sales and purchases
6.5. Vendors Graphs
Vendors Related Graphs Are shown here related to sales and purchases
31
6.6. List
When user click on the List further a Tab Menu will be shown to user can select sales,
purchases or returns to see their List.
6.7. Sales List
Sales List is shown
6.8. Purchases List
Purchases List is shown
6.9. Returns List
Returns List is shown
32
6.10. Categories Tab
Here user can add, update, delete or view categories
6.11. Items Tab
Here user can add, update, delete or view items
6.12. Vendors Tab
Here user can add, update, delete or view vendors
33
6.13. Purchase Tab
Here user manages purchase invoice
6.14. Return Tab
Here user manages return for purchases
34
6.15. Sales Tab
Here user manages sales
35
ISP CANTEEN MANAGEMENT SYSTEM SYSTEM CODING
Chapter 7
7. System Coding
7.1. Coding Techniques

There are three widely used programming paradigms: procedural programming, functional
programming and object-oriented programming. C# supports both procedural and object-
oriented programming.
Object-oriented programming (OOP) is a programming paradigm that uses objects and

their interactions to design applications and computer programs.
There are some basic programming concepts in OOP:
 Abstraction
 Polymorphism
 Encapsulation
 Inheritance
The abstraction is simplifying complex reality by modeling classes appropriate to the

problem. The polymorphism is the process of using an operator or function in different
ways for different data input. The encapsulation hides the implementation details of a class
from other objects. The inheritance is a way to form new classes using classes that have
already been defined.
Objects
Objects are basic building blocks of a C# OOP program. An object is a combination of data
and methods. The data and the methods are called members of an object. In an OOP
program, we create objects. These objects communicate together through methods. Each
object can receive messages, send messages and process data.
7.2. Coding Architecture

A "tier" can also be referred to as a "layer". A wedding cake is said to have tiers while a
chocolate cake is said to have layers, but they mean the same thing.
In the software world Tiers/Layers should have some or all of the following characteristics:
Each tier/layer should be able to be constructed separately, possibly by different teams of

people with different skills.
36
Several tiers/layers should be able to be joined together to make a whole "something".
Each tier/layer should contribute something different to the whole. A chocolate layer cake,
for example, has layers of chocolate and cake.
There must also be some sort of boundary between one tier and another. You cannot take
a single piece of cake, chop it up into smaller units and call that a layer cake because each
unit is indistinguishable from the other units.
Each tier/layer should not be able to operate independently without interaction with other
tiers/layers.
It should be possible to swap one tier/layer with an alternative component which has similar
characteristics so that the whole may continue functioning.
7.3. Code Sample

7.3.1. Integers Validate Class
public static class ValidateInteger
{
public static void OnlyIntergers(KeyPressEventArgs e)
{
if (!char.IsControl(e.KeyChar) && !char.IsDigit(e.KeyChar))
{
e.Handled = true;
}
public static void IntergersWithDecimal(object sender, KeyPressEventArgs e)

{
if (!char.IsControl(e.KeyChar) && !char.IsDigit(e.KeyChar) && (e.KeyChar !=
'.'))
{
e.Handled = true;
}
// only allow one decimal point

if ((e.KeyChar == '.') && ((sender as TextBox).Text.IndexOf('.') > -1))
{
e.Handled = true;
}
}
37
7.3.2. Function to Save Sales

try
{
if (gridItem.RowCount == 0)
{
MessageBox.Show("No Item in the List.", "Sale Error",
MessageBoxButtons.OK, MessageBoxIcon.Error);
return;
}
functions.ExecuteParatemerizedSQLCommand(
"INSERT INTO SaleTable (Id, Date, ListTotal, Discount,
Total) VALUES (@p1, @p2, @p3, @p4, @p5)",
lblSerialNo.Text, DateTime.Now, lblListTotal.Text,
txtDiscount.Text, lblTotal.Text
);
for (int i = 0; i < gridItem.RowCount; i++)

{
functions.ExecuteParatemerizedSQLCommand(
"INSERT INTO SaleDetailTable (Sale, Item, Price,
Quantity, Total) VALUES (@p1, @p2, @p3, @p4, @p5)",
lblSerialNo.Text, gridItem.Rows[i].Cells[0].Value,
gridItem.Rows[i].Cells[4].Value, gridItem.Rows[i].Cells[5].Value,
gridItem.Rows[i].Cells[6].Value
);
functions.ExecuteParatemerizedSQLCommand("Update
ItemTable SET Stock = Stock - @p1 WHERE Id = @p2",
gridItem.Rows[i].Cells[5].Value, gridItem.Rows[i].Cells[0].Value);
}
MessageBox.Show("Sale No. " + lblSerialNo.Text + " Billed
Successfully", "Sale Success", MessageBoxButtons.OK,
MessageBoxIcon.Information);
}
catch (Exception E)
{
MessageBox.Show(E.Message);
}
38
7.3.3. Sales Add to Cart Function

int Stock = int.Parse(txtStock.Text);
int Price = int.Parse(txtPrice.Text);
if (txtStock.Text.Equals(""))
{
MessageBox.Show("Please Enter Stock.", "Sale Error",
return;
}
if (txtPrice.Text.Equals(""))
{
MessageBox.Show("Please Enter Price.", "Sale Error",
return;
}
if (Stock == 0)
{
MessageBox.Show("Stock is 0.", "Sale Error", MessageBoxButtons.OK,
MessageBoxIcon.Error);
return;
}
if (Price == 0)
{
MessageBox.Show("Price is 0.", "Sale Error", MessageBoxButtons.OK,
MessageBoxIcon.Error);
return;
}
if (int.Parse(txtStock.Text) > int.Parse(lblStock.Text))
{
MessageBox.Show("Requested Quantity is More then Stock.", "Sale Error",
return;
}
for (int i = 0; i < gridItem.RowCount; i++)
{
if (gridItem.Rows[i].Cells[0].Value.ToString().Equals(ItemId.ToString()))
{
MessageBox.Show("Item already in the List.", "Sale Error",
return;
}
}
39
gridItem.Rows.Add(ItemId, functions.ExecuteReader("SELECT Name FROM

ItemTable WHERE Id = " + ItemId), lblPrice.Text, lblStock.Text, txtPrice.Text,
txtStock.Text, float.Parse(txtPrice.Text) * int.Parse(txtStock.Text), "Remove");
CalculateTotal();
40
ISP CANTEEN MANAGEMENT SYSTEM SYSTEM TESTING
Chapter 8
8. System Testing
8.1. Adding Category Test Case

Test Case No: 1 Test Case Name: Add Category
Test Case Description: Adding New Category
Pre-Condition: Must be on Category Tab
Steps Actions System Response

1 Write Category
2 Check or Uncheck for
Activeness
3 Click Add Button Check If Category Already Exist with Such Name
or Must have at least 4 characters If not exist and
have more than 4 characters then category is added
and displays new category in the list otherwise
show respective error
Post-Condition: New Category is Added and displayed in the list.
8.2. Updating Category Test Case

Test Case No: 2 Test Case Name: Update Category
Test Case Description: Update Existing Category

1 Select Category from List Fill fields from Selected Category
2 Update Category Info
3 Click Update Button Check If Category Already Exist with Such Name
or Must have at least 4 characters If not exist and
have more than 4 characters then category is
updated and display updated category in the list
otherwise show respective error
Post-Condition: Category is Updated and displayed in the list.
8.3. Delete Category Test Case

Test Case No: 3 Test Case Name: Delete Category
Test Case Description: Delete Existing Category
41

1 Select Category from List Fill fields from Selected Category
2 Click Delete Button Check If Category is used in Items If not then
category is deleted and remove category from the
list otherwise show error
Post-Condition: Category is Deleted and removed from the list.
8.4. Adding Item Test Case

Test Case No: 4 Test Case Name: Add Item
Test Case Description: Adding New Item
Pre-Condition: Must be on Item Tab

1 Write Item Info
Activeness
3 Click Add Button Check If Item Already Exist with Such Name or
Must have at least 4 characters If not exist and have
more than 4 characters then Item is added and
displays new Item in the list otherwise show
respective error
Post-Condition: New Item is Added and displayed in the list.
8.5. Updating Item Test Case

Test Case No: 5 Test Case Name: Update Item
Test Case Description: Update Existing Item

1 Select Item from List Fill fields from Selected Item
2 Update Item Info
3 Click Update Button Check If Item Already Exist with Such Name or
more than 4 characters then Item is updated and
display updated Item in the list otherwise show
respective error
Post-Condition: Item is Updated and displayed in the list.
8.6. Delete Item Test Case

Test Case No: 6 Test Case Name: Delete Item
Test Case Description: Delete Existing Item
42

1 Select Item from List Fill fields from Selected Item
2 Click Delete Button Check If Item is used in Items If not then Item is
deleted and remove Item from the list otherwise
show error
Post-Condition: Item is Deleted and removed from the list.
8.7. Adding Vendor Test Case

Test Case No: 7 Test Case Name: Add Vendor
Test Case Description: Adding New Vendor
Pre-Condition: Must be on Vendor Tab

1 Write Vendor Info
Activeness
3 Click Add Button Check If Vendor Already Exist with Such Name or
more than 4 characters then Vendor is added and
displays new Vendor in the list otherwise show
respective error
Post-Condition: New Vendor is Added and displayed in the list.
8.8. Updating Vendor Test Case

Test Case No: 8 Test Case Name: Update Vendor
Test Case Description: Update Existing Vendor

1 Select Vendor from List Fill fields from Selected Vendor
2 Update Vendor Info
3 Click Update Button Check If Vendor Already Exist with Such Name or
more than 4 characters then Vendor is updated and
display updated Vendor in the list otherwise show
respective error
Post-Condition: Vendor is Updated and displayed in the list.
43
8.9. Delete Vendor Test Case

Test Case No: 9 Test Case Name: Delete Vendor
Test Case Description: Delete Existing Vendor

1 Select Vendor from List Fill fields from Selected Vendor
2 Click Delete Button Check If Vendor is used in Items If not then Vendor
is deleted and remove Vendor from the list
otherwise show error
Post-Condition: Vendor is Deleted and removed from the list.
8.10. Purchases Test Case

Test Case No: 10 Test Case Name: New Purchases
Test Case Description: Validate Purchases Process
Pre-Condition: User must be on Purchases Tab

1 Select Vendor
2 Enter Items in Cart and
set price and quantity
3 Enter Given Amount
4 Click Save Button Check vendor Selection, Whether grid control is
empty or not, and whether given amount is entered
Post-Condition: Purchase is saved and message is displayed.
8.11. Return Test Case

Test Case No: 11 Test Case Name: Purchases Return
Test Case Description: Validate Return Process
Pre-Condition: User must be on Return Tab

1 Enter Purchase Invoice Display Purchase Invoice Detail
2 Update Items in Cart
3 Update Amounts
4 Click Save Button Check customer Selection, Whether grid control is
empty or not, and whether taken amount is entered
Post-Condition: Return is processed and message is displayed.
44
8.12. Sales Test Case

Test Case No: 12 Test Case Name: New Sales
Test Case Description: Validate Sales Process
Pre-Condition: User must be on Sales Tab

1 Enter Items in Cart and
set discounted price,
quantity
2 Enter Amount Taken
3 Click Save Button Check whether grid control is empty or not, and
whether taken amount is entered
Post-Condition: Sale is saved and message is displayed.
45
ISP CANTEEN MANAGEMENT SYSTEM PROCESS MODEL
Chapter 9
9. Process Model
9.1. Systems Development Life Cycle (SDLC)
SDLC includes a systematic process of planning, designing, and creating an information
system for organizations.
It is often better to have a structured methodology to avoid mishaps and coordinate the
design and development tasks properly among the members of a large systems
development team.
Systems Approach—Complex problems are broken up into smaller manageable problems

using a systems’ hierarchy, and then developing a solution for each problem within the
hierarchy.
46
9.2. Process Model Used

RAD Model is used for development of this ISP Canteen management System.
9.3. Why is used RAD Model

Rad Model is used because of its rapid development nature and you can update any module
without disturbing any other module.
9.4. Rapid SDLC Approaches

9.4.1. Prototyping
 This approach does not go through the analysis and design phase.
 It implements a skeleton or a prototype of the actual system with a focus on data
input and output.
 The idea is to demonstrate the system functionality to the users.
 Feedback is incorporated into the new system and demonstrated back to the users.
 This approach has proven to be very effective with user interactive systems because
the prototype is eventually converted into a full-scale system.
9.4.2. End User Development (EUD)

Users are trained to develop their own applications (e.g., a departmental employee tracking
system with an SQL SERVER db).
47
9.5. Traditional ERP Life Cycle
9.5.1. Analysis and Design Stage

 A decision on the software is made and decide on consultants and SMEs.
 Analysis of user requirements.
 Map the differences between the current business process and the embedded
process in the ISP Canteen management software.
 Design a change management plan, a list of embedded processes, user interface
screens, and customizable reports in the ISP Canteen management software.
 Data conversion.
 System conversion.
 Training.
9.6. Agile Development

 Agile methodologies start with smaller sets of requirements, they start small and
deliver functionality incrementally in a series of releases.
 No single release covers all requirements, but every release delivers more than the
previous one.
48
 Users are able to provide feedback quickly on how the system meets their needs
and also if a requirement is missing or wrong, it can be corrected quickly.
9.7. Architecture Used: Three Tier Architecture is used:

9.7.1. Three Tier Architecture
A three-tier architecture is a client-server architecture in which the functional process logic,
data access, computer data storage and user interface are developed and maintained as
independent modules on separate platforms. Three-tier architecture is a software design
pattern and a well-established software architecture.
9.7.2. Tiers in Three Tier Architecture

 Presentation Tier: Occupies the top level and displays information related to
services available on a website. This tier communicates with other tiers by sending
results to the browser and other tiers in the network.
 Application Tier: Also called the middle tier, logic tier, business logic or logic tier,
this tier is pulled from the presentation tier. It controls application functionality by
performing detailed processing.
 Data Tier: Houses database servers where information is stored and retrieved. Data
in this tier is kept independent of application servers or business logic.
49
ISP CANTEEN MANAGEMENT SYSTEM CONCLUSION
Chapter 10
10. Conclusion
11.1. Achievements
 Using Material theme in winform.
 Easy to use Canteen System.
11.2. Obstacles
 This is about ISP Canteen Management. It was hard to find interface best suited
for this project and even making my own design
 Creating new design that is easy to understand
 Implementation of this design in the project
11.3. Future Scope

 Making the interface more easy and beautiful
 Adding more Functionalities to the system
11.4. Few Words in the End

I learned a lot through this project. This project has sharpened my concept of C#.Net.
I learned a lot about different documentation. The success of this project may give pleasure
to billions of people wanting this ISP Canteen management system. This project not only
tested my technical skills but also my temperament.
There were times that I almost lost hope but I recovered through constant concentration
and hard work.
If any kind of suggestion, improvements, more efficient development idea please feel free
to communicate with me.
50
ISP CANTEEN MANAGEMENT SYSTEM CONCLUSION
51

ISP CMS Thesis

Uploaded by

Copyright:

Available Formats

ISP CMS Thesis

Uploaded by

Document Information

Original Title

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

ISP CMS Thesis

Uploaded by

Copyright:

Available Formats

ISP CANTEEN MANAGEMENT SYSTEM INTRODUCTION

3.2.1. Performance Requirements ......................................................................... 20

5.1.1. Database Tables .......................................................................................... 26

6.20. Report Designer ...............................................Error! Bookmark not defined.

9.4. Traditional ERP Life Cycle .................................Error! Bookmark not defined.

User can search in the list in various ways such as:

User can search in the list by:

1.2. Project Scope

1.2.2. Scope of Project in the Market

1.3. Business Goals

 To boost up the Process of Canteen

1.4. Document Convention

Main features of the developed system are as follows:

 Avoid from wastage of time and effort.

 Manage large amount of data with efficiency and accuracy.

 Easy to keep the record of sales.

 Easy to keep the record of purchases.

 Easy to keep the record of Item.

 Easy to keep the record of Vendors.

 Security of data is high.

 Easy to view the details.

2.2. Product Characteristics

 The 1st characteristic contains about Graphs

2.3. System Environment

2.3.1.2. Software Used

Front End Related Information

Back End Related Information

2.3.2. System Minimum Requirement to Run Properly

2.4. Design and Implementation Constraint

2.4.1.2. C Sharp (C#)

Common Language Infrastructure. It is basically used to developed desktop based

2.4.1.3. .NET Framework

2.4.1.4. Telerik UI for Winform

2.4.1.5. Material Skin

2.4.2. Back End

2.4.2.2. Microsoft SQL Server

3.1. Functional Requirements

3.1.1. Manage and View Category

Purpose To manage and keep track of the categories of items.

Pre-Conditions Must be on Category Form

Post-Conditions Category is managed

Typical Course of Action

SN Actor Action System Response

Alternate Course of Action

SN Actor Action System Response

3.1.2. Manage and View Item

Pre-Conditions Must be on Item Form

Post-Conditions Item is managed

Typical Course of Action

SN Actor Action System Response

Alternate Course of Action

SN Actor Action System Response

3.1.3. Manage and View Vendor

Pre-Conditions Must be on Vendor Form

Post-Conditions Vendor is managed

Typical Course of Action

SN Actor Action System Response

database and display to

Alternate Course of Action