1.

Introduction
1.1 Introduction
I.A.S is a company which makes Tractor parts with the label of I.A.S. They are distributing
their parts to the retailers in all south Punjab. They have the reputation of high-end quality parts
in the market. Their main office is near Vehari Chowk Multan.

They get their parts manufactured from different manufacturers with their own standard
requirements. Their manufactured parts are then packed with their company’s packing and then
kept in their stores. Required parts are then transported to different shopkeepers on the loader
vehicle of the company.

The business structure of their company is totally depending on old manual book system which
includes number of problems. With the proposed Business Management System their company
will have a transition from manual system to a computerized management system. Their current
system includes ledger of all the manufacturers from where they manufacture their parts and
their payments throughout past years with each and every detail. Then there is a ledger of all
the shop keepers who collect their parts and then sale it to their customers, it also includes the
dates, payment history and bill number. Their manual system also includes the information of
their employees and their payment history which is sometimes divided on weekly basis rather
than monthly on the demand of their workers. It also includes the payment history and
information receipts of the carriers who always bought their parts from manufacturers to their
stores; it also includes all the calculation of daily, weekly, monthly and even yearly details of
their sales and profits.

The important thing I considered is to have a system with the most basic interface because most
of the employees working there are not well educated and have lack of awareness about modern
day technology so it will only make sense to have an application having maximum benefits
with a simple and easy interface to use and understand.

1.2 Problem Statement

The major problem with their manual management system is the lack of security. All of their
information and record history is just on a piece of paper, so in a case of emergency those
ledgers or records can become vulnerable which will be a huge lose. The other major problem
is the lack of knowledge about their remaining stock in stores.

Current system has many problems. In this section we discuss those problems.

 All the works are carried out with pen and paper.
 Sometime stock information will be not typed accurately
 Sometime user cannot get the proper information about the product.
 Buyers cannot place the order easily.
 This system is not efficient and take long time.

The major problem in the supply of spare parts, is planning, executing, the required spares
planning. Spare parts requirement requires articulate planning procedural lead time, and the
correct required spares. Drawing/specification should be confirm to standards. The Purchase
order should given correct description, code no: drawings and amendments if any in due course.
The supplier should be a A class supplier. The major problem in spares part management is
identification and procurement of exact match. Normally in Pakistan, the technicians on the
road are not aware of exact specifications and try to fit the materials available with them to
make quick money. Standard workshops are the best solution. They procure and manage spares
parts from genuine source and exact match.

Identification of spare parts is not a problem, but keeping inventory of the spares is the biggest
problem. How do you identify the correct spares, and do allow to keep excess inventory. A
good planning for spares, with proper drawing/identification/requirement of spares is required.
Forecast the required quantity and keep minimum stock.

1.3 Motivations
The idea about the improvements and positive changes of a manual system to a computerized
system and then all the opportunities that comes with that to improve a business gives me
motivation to introduce information technology in the traditional business sector of Pakistan.
And beside this experts say that individual and team motivation is the leading factor affecting
the productivity of a project team. There are a few steps the Project Manager should take to
ensure that the foundation of sound motivation is in place in the project environment. And I
will keep these point in minds:

 Set realistic goals. ...

 Be direct. ...
 Conduct weekly or monthly review sessions. ...
 Praise small victories. ...
 Walk the walk. ...
 Supply feedback from the start. ...
 Provide incentives. ...
 Highlight the benefits of the work.

1.4 Objective
The main objective of this project is to develop a system to convert manual system into
computerized system. Other objective is to provide them organized form of information
regarding their stock, clients and manufacturers as well as their employees. Application will
provide modern way to manage their business and they will be able to have a more secure and
reliable management system.

And objectives of auto parts management are to provide the desired level of customer service,
to allow cost-efficient operations, and to minimize the auto parts investment.

1.5 Scope of Project

The scope of the project is an offline inventory management system which will be used to
manage the whole operation of I.A.S so I named it as the Business Management System. It will
be a desktop application which can be used by the manager or the employee working there. It
will have login ID and password for each user.

1.6 Project Deliverables

Project will be submitted with the following deliverables:
Project Thesis
CDs
Executable Code
1.7 SDLC Models
SDLC stands for Software Development Life cycle. It is complete process to design the
software which starts form requirements analysis and ends on Maintenance. The most
important and popular SDLC models are given below:

 Waterfall Model
 Iterative model
 Spiral model
 V-shaped model
 Agile Model

Waterfall model

Waterfall is a type of SDLC model, in which development of the software goes in a downwards
direction from analysis to maintenance just like the flow of waterfall. This SDLC model
includes execution of each stage completely and then moving towards next stage. This model
is not the best choice for long term or complex project as the requirements cannot be stable in
complex project.

Phases of waterfall include:

Requirement Analysis
 System Design
 Implementation
 Testing
 Deployment
 Maintenance

Use cases for the Waterfall SDLC model

The requirements are precisely documented
Product definition is stable
The technologies stack is predefined which makes it not dynamic
No ambiguous requirements
The project is short

Iterative SDLC model

The Iterative SDLC model does not need the full list of requirements before the project starts.
The development process may start with the requirements to the functional part, which can be
expanded later. The process is repetitive, allowing to made new versions of the product for
every cycle. Each iteration includes the development of a separate component of the system,
and after that, this component is added to the functional developed earlier. The phases of
Iterative SDLC model include:

 Analysis
 Design
 Coding
 Testing
 Implementation

Use Cases of Iterative model:

The requirements are strictly predefined
Applied to the large scale projects
The main task is predefined but the detail may advance with time
Spiral SDLC model

The spiral model combines the idea of iterative development with the systematic, controlled
aspects of the waterfall model. This Spiral model is a combination of iterative development
process model and sequential linear development model. The phases of Spiral SDLC model
include:
 Determine Objectives
 Identify Risks
 Development and Test
 Plan the Next Iteration

Use Cases for Spiral model:

The requirements to the final product are strictly predefined
Applied to the large-scale projects
The main task is predefined, but the details may advance with the time

Agile SDLC model

Agile software life cycle is very different from other traditional SDLC models. It works with
the requirement defined at each module and after getting the requirements, module is prepared.
In agile development customer is able to see the results at any specific point and it can respond
to change in design and requirements if needed. The phases of Agile include
 Requirements
 Architecture and Design
 Development
 Test and Feedback

Use cases for agile model:

The user needs change the scope of project dynamically
When rapid production is important
When the final design is not clear

1.8 SDLC Model Chosen

Choosing the right SDLC model for your software development project will require careful
thought. But keep in mind that a methodology for planning and guiding your project is only
one ingredient for success.
I have chosen RAD model for my project as it may help me developing my application rapidly.

1.9 Procedure

Analysis

Design

Coding

Tesing

Maintenance
2. Literature Review and Analysis
2.1 Literature Review
I always felt that there can be few major improvements in their way of doing business as I
know them personally so I did some research on how to achieve those improvements. I found
that they can boost their business performance if they can have the whole information of each
aspect of their business on their fingertips. Employees normally working there are not highly
educated and hence they always prefer manual system to run business, I researched few
companies who are working on a bigger level than IAS and how are they running their business.
One of those companies in this particular field is Millat Tractors. I was impressed the way these
companies have made a transition from typical framework of their business to a modern
framework which involves information technology. All those companies are using some sort
of applications to manage their business, now they know how much they are left with their
stock and how their employees are working and most importantly all the calculations of their
business are now easily calculated even if those calculations are their monthly or yearly profits
including their sales.

So with the same framework in mind I started studying on how can I computerize the business
structure of IAS with the help of an application and for that purpose it was important for me to
see some of those same sort of application systems running to control these sort of businesses.

2.2 Existing Systems

To understand and see how exactly some companies are utilizing and taking advantage from
their management applications, I am going mention three companies below:

2.2.1 Existing System I

New Pak Autos is a Store Selling Car parts for the past 40 years and I personally know them.
About 4 years ago they installed an application system which was developed by some
developer. I met them at that time and they explained me about how they are going to make
the transition from their existing manual system to a computerized system. Obviously I was
not getting that information at that time for my own system I was just interested to know about
the benefits. They told me that they are going to put each and every item into their database
and then they will know exactly how much each item is remaining and then they can order for
that particular item. The only challenge they told me was to teach their uneducated employees
how to work with that. The major benefit they see with this approach is the security of data
through backup as few years back their store catches fire and hence was destroyed with all of
their record ledgers.

2.2.2 Existing System II

Another similar business holder I know is Al Qamar Autos who are selling their Motor Bike
parts for the past 20 to 22 years and they have adopted similar approach to handle their business
with the help of an inventory management system with the main focus in mind of calculating
their stock. The additional function they have in their system is to print out their bill from the
computer and hence automatically adding the sales in total.

2.2.3 Existing System III

Al Nawaz traders are selling Solar panels, Batteries and UPS near Vehari chowk. Their
business framework is somewhat like IAS with stock in hold and then selling it to other
shopkeepers in different cities. They have been using their custom made inventory management
system which also includes computer generated receipts and all the directories of shopkeepers.
The main benefit they take from their software is to calculate who sold their batteries the most
on monthly and yearly basis and they award those shopkeepers with different gifts and lucky
draw. It is just one of the many advantages they see in their software.

2.2.4 Limitation in Existing Systems

 Existing system was manual.

 Time consuming as data entry which include calculations took lot of time.
 Searching was very complex as there could be 100’s of entry every year.
 The proposed system is expected to be faster than the existing system.

2.3 Proposed System

The proposed system for IAS is basically going to manage their whole business operations in
a way that every information will be there on their fingertips. The system I discussed with them
includes five major sections; those are Incoming Stock, Outgoing Stock, Stock in hand, Sales
and Employees. These five sections are the further classified. The admin will login into the
interface to add/remove/edit or to just see the daily progress of their business. This system will
not have computer generated receipts and the main reason behind this is the customer market
is mostly of village people who prefer it to be written by hands in a way that they can understand
but the receipt amount and number will be added to the outgoing directory on daily basis at the
end of the day

2.4 Comparison

Existing systems Proposed system

Old and Unfriendly Interface Friendly and Eye Catching Interface
Workflow was not fluid Workflow is fluid
No Advance Reporting Has Advance Reporting
Difficult Backup and Recovery One Click Backup and Recovery
No Authentication Secure Authentication
Hard to Operate Easy to Operate

2.5 Feasibility Report

All projects are feasible given unlimited resources and infinite time. Unfortunately, the
development of computer-based system in many cases is more likely to be plagued by scarcity
of resources and delivery date. Hence, we have made use the concept of reusability that is what
Object-Oriented Programming (OOPS) is all about.
The feasibility report of the project holds the advantages and flexibility of the project. This is
divided into three sections:
 Economical Feasibility
 Technical Feasibility
 Behavioral Feasibility

Economic Feasibility:

Economic analysis is the most frequently used method for evaluating the effectiveness of the
candidate system. More commonly known as cost/benefit analysis, the procedure is to be
determining the benefits and savings that are expected from a candidate and compare them
with costs. If benefits outweigh costs, then the decision is made to design and implement the
system.
A systems financial benefit must exceed the cost of developing that system. i.e. a new system
being developed should be a good investment for the organization. Economic feasibility
considers the following
 The cost to conduct a full system investigation.
 The cost of hardware and software for the class of application.
 The benefits in the form of reduced cost or fewer costly errors.
 The cost if nothing changes (i.e. The proposed system is not developed).

The proposed “INVENTORY MANAGMENT” is economically feasible because

 The system requires very less time factors.
 The system will provide fast and efficient automated environment instead of slow and
error prone manual system, thus reducing both time and man power spent in running
the system.
 The system will have GUI interface and very less user-training is required to learn it.
 The system will provide service to view various information for proper managerial
decision making.

Technical Feasibility:

Technical feasibility centers around the existing computer system (Hardware and Software)
and to what extend it support the proposed addition. For example, if the current computer is
operating at 80 percent capacity - an arbitrary ceiling - then running another application could
overload the system or require additional Hardware. This involves financial considerations to
accommodate technical enhancements. If the budgets are a serious constraint, then the project
is judged not feasible. In this project, all the necessary cautions have been taken care to make
it technically feasible. Using a key, the display of text/object is very fast. Also, the tools,
operating system and programming language used in this localization process is compatible
with the existing one.

Behavioral Feasibility:

People are inherently resistant to change, and computers have been known to facilitate change.
An estimate should be made of how strong a reaction the user staff is likely to have toward the
development of a computerized system. Therefore, it is understandable that the introduction of
a candidate system requires special efforts to educate and train the staff. The software that is
being developed is user friendly and easy to learn. In this way, the developed software is truly
efficient and can work on any circumstances, tradition, locales.
Behavioral study strives on ensuring that the equilibrium of the organization and status quo in
the organization are nor disturbed and changes are readily accepted by the users.

2.6 Statement of Work

A statement of work (SoW) is a document routinely employed in the field of project
management. It defines project-specific activities, deliverables and timelines for a vendor
providing services to the client. The SOW typically also includes detailed requirements and
pricing, with standard regulatory and governance terms and conditions.

ORGANIZATION
NAME
CONTACT
ADDRESS

PROJECT
NAME
 BRAND
PRODUCT
BEGIN DATE
END DATE
DURATION

ASSUMPTIONS

GOALS
OBJECTIVE
SCOPE
DELIVERABLES

PAYMENTS
ADVANCE
MID
TOTAL COST

2.7 Gantt Chart

A Gantt chart is a type of bar chart that illustrates a project schedule, named after its
inventor, Henry Gantt (1861–1919), who designed such a chart around the years 1910–
1915. Modern Gantt charts also show the dependency relationships between activities and
current schedule status.

A Gantt chart, commonly used in project management, is one of the most popular and useful
ways of showing activities (tasks or events) displayed against time. On the left of the chart is a
list of the activities and along the top is a suitable time scale. Each activity is represented by a
bar; the position and length of the bar reflects the start date, duration and end date of the
activity.
3. System Design
3.1 Introduction
Systems design is the process of defining the architecture, 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. There is some overlap with the disciplines
of systems analysis, systems architecture and systems engineering.

3.2 Data Flow Diagram

The Data Flow Diagram shows the flow of data or information. It can be partitioned into single
processes or functions. Data Flow Diagrams can be grouped together or decomposed into
multiple processes.

The DFD is an excellent communication tool for analysts to model processes and functional
requirements. Used effectively, it is a useful and easy to understand modeling tool. It has broad
application and usability across most software development projects. It is easily integrated with
data modeling, workflow modeling tools, and textual specs. Together with these, it provides
analysts and developers with solid models and specs. Alone, however, it has limited usability.
It is simple and easy to understand by users and can be easily extended and refined with further
specification into a physical version for the design and development teams.
The different versions are Context Diagrams (Level 0), Partitioned Diagrams (single process
only -- one level), functionally decomposed, and leveled sets of Data Flow Diagrams.

Data Store

A repository of information. In the physical model, this represents a file, table, etc. In
the logical model, a data store is an object or entity.

Data Flows

DFDs show the flow of data from external entities into the system, showed how the data
moved from one process to another, as well as its logical storage. There are only four symbols:
Squares representing external entities, which are sources or destinations of data.

Rounded rectangles representing processes, which take data as input, do something to it, and
output it.

Arrows representing the data flows, which can either, be electronic data or physical items.
Open-ended rectangles representing data stores

There are several common modeling rules for creating DFDs:

 All processes must have at least one data flow in and one data flow out.
 All processes should modify the incoming data, producing new forms of outgoing data.
 Each data store must be involved with at least one data flow.
 Each external entity must be involved with at least one data flow.
 A data flow must be attached to at least one process.
3.2.1 Context DFD

A context diagram is a top level (also known as "Level 0") data flow diagram. It only contains
one process node ("Process 0") that generalizes the function of the entire system in relationship
to external entities.

This is simple Level 0 DFD with only one process

3.2.2 Level 1 DFD

A level 1 data flow diagram (DFD) is more detailed than a level 0 DFD but not as detailed as
a level 2 DFD. It breaks down the main processes into subprocesses that can then be analyzed
and improved on a more intimate level.

A more detailed DFD of Computer Shop System

3.3 Use Case Diagram
UML Use Case Diagrams. Use case diagrams are usually referred to as behavior diagrams used
to describe a set of actions (use cases) that some system or systems (subject) should or can
perform in collaboration with one or more external users of the system (actors).

A use case diagram contains four components.

 The boundary, which defines the system of interest in relation to the world around it.
 The actors, usually individuals involved with the system defined according to their
roles.
 The use cases, which are the specific roles played by the actors within and around the
system.
 The relationships between and among the actors and the use cases.

3.4 Sequence Diagram

UML sequence diagrams model the flow of logic within your system in a visual manner,
enabling you both to document and validate your logic, and are commonly used for both
analysis and design purposes. Sequence diagrams are the most popular UML artifact for
dynamic modeling, which focuses on identifying the behavior within your system. Other
dynamic modeling techniques include activity diagramming, communication
diagramming, timing diagramming, and interaction overview diagramming. Sequence
diagrams, along with class diagrams and physical data models are in my opinion the most
important design-level models for modern business application development.

Sequence diagrams are typically used to model:

Usage scenarios. A usage scenario is a description of a potential way your system is used. The
logic of a usage scenario may be part of a use case, perhaps an alternate course. It may also be
one entire pass through a use case, such as the logic described by the basic course of action or
a portion of the basic course of action, plus one or more alternate scenarios. The logic of a
usage scenario may also be a pass through the logic contained in several use cases. For example,
a student enrolls in the university, and then immediately enrolls in three seminars.
The logic of methods. Sequence diagrams can be used to explore the logic of a complex
operation, function, or procedure. One way to think of sequence diagrams, particularly highly
detailed diagrams, is as visual object code.

The logic of services. A service is effectively a high-level method, often one that can be
invoked by a wide variety of clients. This includes web-services as well as business transactions
implemented by a variety of technologies.

Sequence Diagrams captures:

 the interaction that takes place in a collaboration that either realizes a use case or an
operation (instance diagrams or generic diagrams)
 high-level interactions between user of the system and the system, between the system and
other systems, or between subsystems (sometimes known as system sequence diagrams)

3.5 Class Diagram

In software engineering, a class diagram in the Unified Modeling Language (UML) is a type
of static structure diagram that describes the structure of a system by showing the system's
classes, their attributes, operations (or methods), and the relationships among objects.

Purpose of Class Diagrams

 Shows static structure of classifiers in a system
 Diagram provides basic notation for other structure diagrams prescribed by UML
 Helpful for developers and other team members too
  Business Analysts can use class diagrams to model systems from business perspective

A UML class diagram is made up of:

 A set of classes and
 A set of relationships between classes

3.6 ER Diagram
The entity relationship (ER) data model has existed for over 35 years. It is well suited to data
modelling for use with databases because it is fairly abstract and is easy to discuss and explain.
ER models are readily translated to relations. ER models, also called an ER schema, are
represented by ER diagrams.

ER modelling is based on two concepts:

 Entities, defined as tables that hold specific information (data)
 Relationships, defined as the associations or interactions between entities

An entity is an object in the real world with an independent existence that can be differentiated
from other objects. An entity might be
 An object with physical existence (e.g., a lecturer, a student, a car)
 An object with conceptual existence (e.g., a course, a job, a position)

Each entity is described by a set of attributes (e.g., Employee = (Name, Address, Birthdate
(Age), Salary).
Each attribute has a name, and is associated with an entity and a domain of legal
values. However, the information about attribute domain is not presented on the ERD.

Relationships are the glue that holds the tables together. They are used to connect related
information between tables.
Relationship strength is based on how the primary key of a related entity is defined. A weak,
or non-identifying, relationship exists if the primary key of the related entity does not contain
a primary key component of the parent entity.

3.7 Database
A database is a collection of information that is organized so that it can be easily accessed,
managed and updated.
Data is organized into rows, columns and tables, and it is indexed to make it easier to find
relevant information. Data gets updated, expanded and deleted as new information is added.
Databases process workloads to create and update themselves, querying the data they contain
and running applications against it.
Computer databases typically contain aggregations of data records or files, such as sales
transactions, product catalogs and inventories, and customer profiles.

3.7.1 Database Schema

A database schema is a collection of metadata that describes the relations in a database. A

schema is also described as the layout or blueprint of a database that outlines the way data is
organized into tables.
A database schema is the skeleton structure that represents the logical view of the entire
database. It defines how the data is organized and how the relations among them are associated.
It formulates all the constraints that are to be applied on the data.

A database schema defines its entities and the relationship among them. It contains a
descriptive detail of the database, which can be depicted by means of schema diagrams. It’s
the database designers who design the schema to help programmers understand the database
and make it useful.
3.8 Normalization
Normalization is the branch of relational theory that provides design insights. It is the process
of determining how much redundancy exists in a table. The goals of normalization are to:
 Be able to characterize the level of redundancy in a relational schema
 Provide mechanisms for transforming schemas in order to remove redundancy

1st 2nd 3rd Boyce 4th 5th 6th

Norm Norm Norm Codd Norm Norm Norm
Form Form Form NF Form Form Form

Normalization theory draws heavily on the theory of functional dependencies. Normalization

theory defines six normal forms (NF). Each normal form involves a set of dependency
properties that a schema must satisfy and each normal form gives guarantees about the presence
and/or absence of update anomalies. This means that higher normal forms have less
redundancy, and as a result, fewer update problems.

All the tables in any database can be in one of the normal forms we will discuss next. Ideally,
we only want minimal redundancy for PK to FK. Everything else should be derived from other
tables. There are six normal forms, but we will only look at the first four, which are:
 First normal form (1NF)
 Second normal form (2NF)
 Third normal form (3NF)
 Boyce-Codd normal form (BCNF)

BCNF is rarely used.

3.8.1 Normalization Forms

First Normal Form

In the first normal form, only single values are permitted at the intersection of each row and
column; hence, there are no repeating groups.

To normalize a relation that contains a repeating group, remove the repeating group and form
two new relations.

The PK of the new relation is a combination of the PK of the original relation plus an attribute
from the newly created relation for unique identification.

Second Normal Form

For the second normal form, the relation must first be in 1NF. The relation is automatically in
2NF if, and only if, the PK comprises a single attribute.

If the relation has a composite PK, then each non-key attribute must be fully dependent on the
entire PK and not on a subset of the PK (i.e., there must be no partial
dependency or augmentation).
Third Normal Form

To be in third normal form, the relation must be in second normal form. Also, all transitive
dependencies must be removed; a non-key attribute may not be functionally dependent on
another non-key attribute.

Boyce Codd Normal Form

When a table has more than one candidate key, anomalies may result even though the relation
is in 3NF. Boyce-Codd normal form is a special case of 3NF. A relation is in BCNF if, and
only if, every determinant is a candidate key.
4. Development
4.1 Development Plan
I have used Rad Model for my development

4.1.1 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.

4.1.2 Rapid SDLC Approaches

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.

4.1.3 Hardware Tools

Processor: Core i3 2.80 GHz

RAM: 8GB
Harddisk: 500GB

4.1.4 Software Tools

Following Tools are used for making this system

Language: C Sharp or C#
IDE: Visual Studio 2017:
Framework: .Net Framework 4.5
Technology: Winform
UI and Reporting Framework: DevExpress 18.1.4
Database: SQL SERVER 2012
DB IDE: DbForge for Sql Server 5.1
Drawing: Microsoft Visio 2016
Report Making: Microsoft Word 2016

4.2 Platform (Microsoft)

Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is
used to develop computer programs, as well as websites, web apps, web services and mobile
apps. 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.

4.3 Language (C Sharp)

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

4.3.1 Creating User Interface

User Interface were made using drag and drop facility beside this UI Framework DevExpress
was used to create more good looking, professional and responsive design

4.3.2 Levels of Coding

Coding was done by keeping in view the 3-tier architecture. Visual studio itself provide 2 tier
it keeps drag and drop code separate from other logic. But in 3 tier we further divide that logic
into business logic and database logic.

4.3.3 OOP

Features like inheritance, encapsulation and other oop features were used by default. Every
custom Form or Control is inheriting from the basic form or control provided by visual studio
itself

4.3.4 Dialog Box

Dialog Box are used to show exception, success and error alerts. A few examples are given
below

4.3.5 Events

Mouse and Keyboard events are used beside them dropdown change event, and data grid
selection changed event are also used.

4.3.6 Error Handling

Errors are handled very wisely so that the software should not close unexpectedly. Few
examples are given below.
4.3.7 Forms and Controls

I have created following custom forms and controls

4.3.8 Why I choose C#

I have chosen c# because it is very easy to create desktop application with it and criteria to
create a computer shop management system was fulfilled by c#. and hardware work like
printing was also added very easily.
5. Deployment
5.1 Implementation
A product software implementation method is a blueprint to get users and/or organizations
running with a specific software product.

The method is a set of rules and views to cope with the most common issues that occur when
implementing a software product: business alignment from the organizational view and
acceptance from human view.

The implementation of product software, as the final link in the deployment chain of software
production, is in a financial perspective of a major issue.

It is stated that the implementation of (product) software consumes up to 1/3 of the budget of
a software purchase (more than hardware and software requirements together).

When the main point of the computer study program is to implement counter measures to bots
and bugs.

5.1.1 Location
The software was implemented at IAS

5.1.2 Hardware
I told them to buy:
Processor: Core 2 Dou 2.4 Ghz
Ram: 2Gb
HDD: 160Gb

5.2 Configuration
I installed sql server on their system. Made the installer of the software with automatic database
connection setting. And database creation and table creation and insert one record for admin
user in admin table for login

5.3 Testing
5.3.1 Purpose
Software testing enables making objective assessments regarding the degree of conformance
of the system to stated requirements and specifications.
Testing verifies that the system meets the different requirements including, functional,
performance, reliability, security, usability and so on. This verification is done to ensure that
we are building the system right.
In addition, testing validates that the system being developed is what the user needs. In essence,
validation is performed to ensure that we are building the right system. Apart from helping
make decisions, the information from software testing helps with risk management.
Software testing contributes to improving the quality of the product. You would notice that we
have not mentioned anything about defects/bugs up until now.

5.3.2 Unit Testing

Testing performed on each module or block of code during development. Unit Testing is
normally done by the programmer who writes the code.
5.3.3 Integration testing
Testing done before, during and after integration of a new module into the main software
package. This involves testing of each individual code module. One piece of software can
contain several modules which are often created by several different programmers. It is crucial
to test each module's effect on the entire program model.

5.3.4 System testing

Testing done by a professional testing agent on the completed software product before it is
introduced to the market.

5.3.5 Acceptance testing

Beta testing of the product done by the actual end users.

5.4 Test Cases

1. Test case: Admin Login
Test case: Login Priority(H,L): High
Test objective: Verifying login
Test descriptions: “user enter the required field, press login button”, client program
contact to the server, server contact with database, database update the result and send the
results to the user.
Requirements verified: Yes
Test environment: Person must have the software
Test setup/ pre-condition: Software must be opened and user must be logged out
Location Expected result
The user will login to access application “Login successfully”. Display main menu.
Pass: Yes Condition: Pass Fail: No
Problem /issues: NIL
Status: Successfully Executed

2. Test case: Part Insert

Test case: Add New Part Item Priority(H,L): High
Test objective: To Insert New Part in the system
Test descriptions: “user enter the required field, press save button”, client program
contact to the server, server contact with database, database update the result and send the
results to the user.
Requirements verified: Yes
Test environment: Person must be logged in
Test setup/ pre-condition: Person should be in Manage Item Page
Location Expected result
Part will be added to the system “Item added successfully”. Clear the fields.
Pass: Yes Condition: Pass Fail: No
Problem /issues: NIL
Status: Successfully Executed

3. Test case: Supplier Insert

Test case: Add New Supplier Priority(H,L): High
Test objective: To Insert New Supplier in the system
Test descriptions: “user enter the required field, press save button”, client program
contact to the server, server contact with database, database update the result and send the
results to the user.
Requirements verified: Yes
Test environment: Person must be logged in
 Test setup/ pre-condition: Person should be in Manage Supplier Page
Location Expected result
Supplier will be added to the system “Supplier added successfully”. Clear the fields.
Pass: Yes Condition: Pass Fail: No
Problem /issues: NIL
Status: Successfully Executed

4. Test case: Order

Test case: Insert Order Priority(H,L): High
Test objective: To Insert Order in the System
Test descriptions: User select supplier. Add Items in the cart. Fill payment fields, press
save button, client program contacts to the server, server contact with database, database
update the result and send the results to the user.
Requirements verified: Yes
Test environment: Person must be logged in
Test setup/ pre-condition: Person should be in Order Page
Location Expected result
Order will be added to the system “Order made successfully”. Clear the fields.
Pass: Yes Condition: Pass Fail: No
Problem /issues: NIL
Status: Successfully Executed
Conclusion
According to our client requirements we have developed the POS System as offline based
which is much backdated compare to new tech era? For future upgradation we will transform
this offline system into online based. Currently users need to enter every detail manually.

This system has some benefits to their staffs. Currently they are keeping every record by written
down in memo manually. At least this system will give them relieve from exhausted life which
they are dealing with their customers. Besides this system will make them more reliable to its
customers as all the customers records will be kept safely than any previous
times. Moreover, they can manage their stock more handily.
Reference
SMARTDRAW
http://www.smartdraw.com

TECHNOPEDIA
https://www.techopedia.com

UML-DIAGRAM
http://www.uml-diagrams.org

GURU99
https://www.guru99.com/