IMPLEMENTING USABILITY IN AN ONLINE STOCK

RESERVATION SYSTEM

CASE STUDY: BLUELINE SYNERGY LIMITED

OSCAR WAMBUGU KARWIMBO

BIT-001-6049/2012
DECLARATION

The research proposal is my original work and has not been presented to any other examination
body.

Name: ………………………………………………………………….

Registration No…… ……………………………………………………….

Sign ………………………………………………………………………….

Date ………………………………………………………………

The research has been submitted with my approval as the University Supervisor.

Name: …………………………………………………………………………….

Sign ………………………………………………………………………………..

Date ………………………………………………………………………………..
Table of Contents
DECLARATION ..............................................................................................................................2
CHAPTER ONE ...............................................................................................................................5
1.1 INTRODUCTION .............................................................................................................................. 5
1.2 STATEMENT OF THE PROBLEM: ..................................................................................................... 5
1.3 RESEARCH AREA: .......................................................................................................................... 5
1.4 PROPOSED SOLUTION .......................................................................................................................... 6
1.5.0. OBJECTIVES ..................................................................................................................................... 6
1.5.1. General objective ........................................................................................................................ 6
1.5.2. Specific objectives ...................................................................................................................... 6
1.6 RESEARCH QUESTION ......................................................................................................................... 6
1.7 PROJECT JUSTIFICATION ...................................................................................................................... 6
1.8 PROJECT SCOPE. .................................................................................................................................. 6
CHAPTER TWO: ............................................................................................................................7
2.0 LITERATURE REVIEW............................................................................................................7
2.1 INTRODUCTION .................................................................................................................................... 7
2.2 THEORETICAL REVIEW/ CONCEPTUAL FRAMEWORK .......................................................................... 7
2.2.1 Web Usability .............................................................................................................................. 7
2.2.2 Web Stickiness ............................................................................................................................. 8
2.2.3.0. Attributes of usability............................................................................................................... 8
2.2.4. Usability Evaluation.................................................................................................................. 11
2.2.5.0. Enhancing Usability ............................................................................................................... 12
CHAPTER 3: ...................................................................................................................................... 14
3.1. INTRODUCTION ................................................................................................................................. 14
3.2. METHODOLOGY ................................................................................................................................ 14
3.3.0. FEASIBILITY STUDY ................................................................................................................ 14
3.3.1. operational feasibility ............................................................................................................... 14
3.3.2. Economic feasibility .................................................................................................................. 14
3.3.3. Technical feasibility ................................................................................................................... 14
 3.3.4. Behavioral feasibility ................................................................................................................. 14
3.4. REQUIREMENTS ELICITATION ........................................................................................................... 15
3.4.1. Interviews.................................................................................................................................. 15
3.4.2. Questionnaire ........................................................................................................................... 15
3.4.3. Observation ............................................................................................................................... 16
3.5. DATA AND SYSTEM ANALYSIS ......................................................................................................... 16
3.6.0. SYSTEM SPECIFICATION ................................................................................................................ 17
3.6.1 User Requirements ..................................................................................................................... 17
3.6.2 Functional Requirements ........................................................................................................... 17
3.6.3 Design Specification .................................................................................................................. 19
3.6.4. Design ....................................................................................................................................... 19
3.7.0. SYSTEM ARCHITECTURE ............................................................................................................... 24
3.7.1. Use case Diagram ...................................................................................................................... 25
3.7.2. Activity Diagram....................................................................................................................... 27
3.7.3. Database Design........................................................................................................................ 29
CHAPTER FOUR .......................................................................................................................... 33
4.0 INTRODUCTION ............................................................................................................................ 33
4.1 SYSTEM CODE GENERATION ............................................................................................................. 33
4.2.0. TESTING......................................................................................................................................... 39
4.2.1.0. Testing Plan ............................................................................................................................ 39
4.3. ACHIEVEMENTS ................................................................................................................................ 41
4.4. PROBLEMS ENCOUNTERED...................................................................................................................... 41
4.4 LIMITATIONS ............................................................................................................................... 41
4.5 CONCLUSIONS ............................................................................................................................. 42
4.6 RECOMMENDATIONS ......................................................................................................................... 42
REFERENCES .................................................................................................................................... 43
APPENDICES .................................................................................................................................... 44
APPENDIX 1 ................................................................................................................................................ 44
APPENDIX 2 ................................................................................................................................................ 45
APPENDIX 3 ................................................................................................................................................ 46
APPENDIX 4 QUESTIONNAIRE ........................................................................................................................ 47
APPENDIX 5 SAMPLE CODE............................................................................................................................ 50
CHAPTER ONE

1.1 Introduction.

Blueline Synergy Limited is a Kenyan owned business specializing in ICTs, located at New
Rehema Hse (1st floor), Rhapta Road, Westlands Which is an integrator of competitive, innovative
business solutions that develop cutting edge IT solutions Blueline helps to facilitate SMEs reach
their fullest potential in terms of IT and leverage the gap in competition with large companies and
thus giving them a level playing field in their respective businesses. They tailor their services to
meet the needs of their clients whose budgets don’t allow for the costs of working with large scale
enterprises. Given the significant role ICT plays in enabling service delivery, Blueline Synergy is
focused on working with SMEs to increase their revenue and reduce costs in their businesses
through technology. Blueline encourages their clientele to focus on their core functions to increase
their productivity as they themselves focus on facilitating an ICT infrastructure that is reliable and
functional thus reducing their operation costs up to 60%.

1.2 Statement of the problem:

The biggest problem is the inability of the clients of the organization to find the stock they desire
weeks later after stock replenishment. The current system does not provide such information to
the regular clients which results to delay of service delivery due to long queues at the beginning
of every month as clients rush to purchase the newly available stock before the organization
experiences a stock out. This particular processes have proven to be cumbersome to the clients and
the organization and as a result the organization has experience a decrease in the client base.

1.3 Research area:

Web usability is the ease of use of a website. Some broad goals of usability are the presentation
of information and choices in a clear and concise way, a lack of ambiguity and the placement
of important items in appropriate areas. Another important element of web usability is ensuring
that the content works on various devices and browsers. Another concern for usability is
ensuring that the website is appropriate for all ages and genders.
The idea of Usability is centered on the concept of making the interface of the website more
user friendly. Some of the common aspects of Usability are simplicity, consistency,
familiarity, clarity, credibility, relevancy and accessibility. The focus is to make users feel at
ease and remove all the bottlenecks from the conversion path so that users don’t have to deal
with any inconvenience while browsing or purchasing a product online.
1.4 Proposed Solution
The Inventory monitoring system will be designed to enable consumers be able to make
reservations of stocks from their respective remote locations. This will enable the company to have
a clear estimated figure of stocks to import and render quick reliable services to the associated
consumers.

The stock system will be developed to enable consumers to make stock reservations remotely thus
making the newly replenished stock accessible to the organizations’ clients

1.5.0. Objectives
1.5.1. General objective
To develop a system that will enable consumers to make reservation of stocks and issue stock
notifications relevant to the consumers remotely.

1.5.2. Specific objectives

1) To develop a system that will ease all transaction activities carried out within the organization.
2) To carry out analysis and design of the system
3) To conduct a feasibility of the existing system and the resources required to carry through.

1.6 Research Question

1) What are various methods of usability evaluation and their appropriateness to the system
development?
2) How can usability be enhanced during system development?
3) What are available usability heuristics?

1.7 Project Justification

the system will implement accessibility by enabling end users to be able to make stock reservations remotely
thereby reaching users of different browsers and mobile devices hence increasing the number of potential
customers able to access the site.

1.8 Project Scope.

The proposed system will target clients of Blueline synergy limited who repeatedly experience frustrations
due to frequent stock outs. The proposed system will be able to allow consumers to make stock reservations
prior to the organizations’ stock imports. The proposed system should also keep the organizations’ client
updated on the expected stock replenish dates, stock price variations, available product offers and discounts
and any other relevant notifications to the consumers.
CHAPTER TWO:

2.0 LITERATURE REVIEW

2.1 Introduction
As Internet is becoming a powerful channel in e-commerce, the website plays an important role as
a “cyber store” through which consumers have their initial and on-going interactions with the Web
retailers. In business to consumer transactions environment, website has become a major
information source and cyber store to purchase online. Up to now, numerous studies have focused
on the design principle of websites and the measurement of Web usability. Unlike the previous
research, this study concentrates on the relationship among usability of the website and
stickiness of potential online shopper toward Web retailers from the B2C ecommerce perspective,
because it has been suggested that elements of human computer interface design have a significant
influence on customer attitudes and perceptions of trustworthiness of a supplier. From the
relationship marketing perspective, since it always costs more to attract new customers than to
retain current customers, customer retention is more critical than customer attraction. Increasing
customer retention could improve long-term profitability in the business The key to customer
retention is customer satisfaction (Zhang and M. von Dran 2001-2002). Consequently, if a
customer is satisfied with the use of a specific website, he/she will continuously use the website to
purchase online. Reichheld and Schefter (2000) found that acquiring consumers on the Internet is
more expensive than on conventional channels and that if consumers cannot stick to the business’
website, the e-business model will collapse. Therefore, understanding consumers’ expectations
and how they feel about the website they use is becoming very important concern in the B2C e-
commerce (Zhang and M. von Dran 2001-2002). Nonetheless, it is little known about the effect of
human-computer interaction on the sticky behavior of website users to purchase online. The
purpose of this research is to explore the relationship between Web usability and users repurchase
intention and to identify the effect of Web stickiness constructs in the relationship.

2.2 Theoretical review/ Conceptual Framework

2.2.1 Web Usability

The usability of website has received attention in the human computer interaction (HCI) literature.
Prior to widespread use of the web, usability of information systems was equivalent to a set of
design principle (Palmer 2002). According to Nielsen (1993), the key element is (1) consistency
of the interface, (2) response time, (3) mapping and metaphors, (4) interaction styles, and (5)
multimedia and audiovisual. As the Web became a robust channel in the ecommerce, usability
research began to focus more specifically on extending the basic usability principles into the Web
environment (Shneiderman 1998; Nielsen 2000; Palmer 2002). Nielsen (2000) extends the
following principles for Web design: (1) navigation, (2) response time, (3) credibility, and (4)
content. Some previous research has shown the impact of website design on the customer’s initial
perception of the company (Roy et al. 2001). The website in the B2C e-commerce is a web
retailer’s face to the consumer. Potential customers look at web retailer’s online presence before
doing any business with it. Since the Web is a strong medium in the context of online transaction,
Web retailers are pursuing the most effective and competitive web design to communicate with
potential consumers, motivate them to access or purchase their products and services, and engender
consumers’ trust. The website is an entry facilitator or barrier in achieving these goals in a Web-
based transaction environment (Zhang and M. von Dran 2001-2002). Unlike the physical store,
the switching costs on the Internet are low. If consumers don’t find what they want, cannot figure
out how to purchase, or do not feel safe giving their personal information, they will leave the site
by only a mouse-click. The initial visit to the website can be triggered by the advertising or other
promotional methods. But If the website doesn’t have usability, the percentage of those who
complete a purchase after visiting the site will not be increased (Nielsen and Norman 2000).

2.2.2 Web Stickiness

The concept of stickiness in the Web world is currently defined multiple ways. Media Metrix, the
leading digital media measurement company, measures stickiness solely on the average time spent
at a site per usage month. Nemzow (1999) divided stickiness into short-term stickiness and long-
term stickiness. Short-term stickiness is easily replicated by competitors. Long-term stickiness
needs to grow even stickier over time, creating a financial hurdle that discourages customers from
switching to competitors. Davenport (2000) points out that stickiness is critical on the e-commerce
and that its main concern is how much actual viewer attention they attract over time. From the
perspective of information technology, stickiness is the “first indication that companies are
focusing not just on information distribution but on usage as well” (Davenport 2000, p.58). Dahui
and Yadav (2001) suggested that user satisfaction, lack of motivation to switch, and perceived
switching cost may lead stickiness toward a website.

2.2.3.0. Attributes of usability

The extent to which a product can be used by specified users to achieve specified goals with
effectiveness, efficiency, and satisfaction in a specified context of use"

This definition can be expanded, and made more comprehensive, by including five characteristics
which must be met for the users of a product:

1) Effective
2) Efficient
3) Engaging
4) Error Tolerant
5) Easy to Learn
6) Effective
2.2.3.1. Effectiveness
Is the completeness and accuracy with which users achieve specified goals? It is determined by
looking at whether the user’s goals were met successfully and whether all work is correct.

It can sometimes be difficult to separate effectiveness from efficiency, but they are not the same.
Efficiency is concerned primarily with how quickly a task can be completed, while effectiveness
considers how well the work is done. Not all tasks require efficiency to be the first principle. For
example, in interfaces to financial systems (such as banking machines), effective use of the system
withdrawing the correct amount of money, selecting the right account, making a transfer correctly
are more important than marginal gains in speed. This assumes, of course, that the designer has
not created an annoying or over-controlling interface in the name of effectiveness.

The quality of the user assistance built into the interface can have a strong impact on effectiveness.
The effectiveness of an interface often relies on the presentation of choices in a way that is clearly
understandable to the user. The more informative an interface can be, the better users are able to
work in it without problems. Good interface terminology will be in the user’s language and
appropriate to the task.

Another design strategy to increase effectiveness is to offer redundant navigation, especially for
ambiguous situations. Although this may create inefficient paths, it allows the user to work
effectively by making more than one choice lead to the correct outcome. This can be especially
valuable in interfaces which support infrequent users or those often unfamiliar with the content
domain.

2.2.3.2. Efficient
Efficiency can be described as the speed (with accuracy) in which users can complete the tasks for
which they use the product. ISO 9241 defines efficiency as the total resources expended in a task.
Efficiency metrics include the number of clicks or keystrokes required or the total ‘time on task’

It is important to be sure to define the task from the user’s point of view, rather than as a single,
granular interaction. For example, a knowledge base which doled out small snippets of information
might be very efficient if each retrieval was considered one task, but inefficient when the entire
task of learning enough to answer a user’s question is considered.

Navigation design elements such as keyboard shortcuts, menus, links and other buttons all have
an impact on efficiency. When they are well-designed, with clearly expressed actions, less time
and effort are needed for the user to make navigation and action choices.

Making the right choices for efficient use of the software depends on an understanding of the users
and how they prefer to work. For example, are they likely to use the interface infrequently or to be
habitual users who might learn hidden controls and shortcuts? Do they use the keyboard, mouse
or other input devices? For example, keyboard shortcuts can be extremely efficient for proficient
users who work with the interface intensively. If they are the primary interaction tool, they can
slow down users who are unfamiliar with them, or with the software. Similarly, an interface
structured around a set of hierarchical choices which may be the best solution for one-time or
infrequent users, might be frustratingly slow as the only way of interacting with a frequently-used
program.

2.2.3.3. Engaging
An interface is engaging if it is pleasant and satisfying to use. The visual design is the most obvious
element of this characteristic. The style of the visual presentation, the number, functions and types
of graphic images or colors (especially on web sites), and the use of any multimedia elements are
all part of a user’s immediate reaction. But subtler aspects of the interface also affect how engaging
it is. The design and readability of the text can change a user’s relationship to the interface as can
the way information is chunked for presentation. Equally important is the style of the interaction
which might range from a game-like simulation to a simple menu-command system.

Like all usability characteristics, these qualities must be appropriate to the tasks, users and context.
The style of engagement that is satisfying for a repetitive work tool is different than an e-commerce
site. Even within the same class of interfaces, different users may have widely divergent needs.
What is important is that the design meet the expectations and needs of the people who must use
the interface.

2.2.3.4. Error Tolerant

The ultimate goal is a system which has no errors. But, product developers are human, and
computer systems far from perfect, so errors may occur. An error tolerant program is designed to
prevent errors caused by the user’s interaction, and to help the user in recovering from any errors
that do occur.

Note that a highly usable interface might treat error messages as part of the interface, including
not only a clear description of the problem, but also direct links to choices for a path to correct the
problem. Errors might also occur because the designer did not predict the full range of ways that
a user might interact with the program. For example, if a required element is missing simply
presenting a way to fill in that data can make an error message look more like a wizard. If a choice
is not made, it can be presented without any punitive language. (However, it is important to note
that it is possible for an interface to become intrusive, or too actively predictive.)

For those errors which are out of the control of the interface – system failures or other disasters -
take a lesson from flight attendants and quietly, calmly guide the user through the process of
helping the program recover from the problem.

Some guidelines for preventing errors are:

1) Make it difficult to take incorrect actions. Design links and buttons to be distinctive, use
clear language, avoiding technical jargon, and be sure that dependent fields or choices
appear together.
 2) Make it difficult to take invalid actions. Limit choices when possible to those which are
correct, provide clear examples for data entry, present only appropriate navigation options.
3) Make it difficult to take irreversible actions. Provide the ability to back track, provide
means to undo or reverse actions, avoid dead-end screens. Don’t indiscriminately use
confirmations – users become insensitive to them.
4) Plan for the unexpected. Allow for users to add new entries, take exceptional routes through
the interface or make choices you did not predict. Be polite about "correcting" mistakes
that may arise from this lack of foresight.

2.2.3.5. Easy to Learn

One of the biggest objections to "usability" comes from people who fear that it will be used to
create products with a low barrier to entry, but which are not powerful enough for long, sustained
use.

But learning goes on for the life of the use of a product. Users may require access to new
functionality, expand their scope of work, explore new options or change their own workflow or
process. These changes might be instigated by external changes in the environment, or might be
the result of exploration within the interface.

An interface which is easy to learn allows users to build on their knowledge without deliberate
effort. This goes beyond a general helpfulness to include built-in instruction for difficult or
advanced tasks, access to just-in-time training elements, connections to domain knowledge bases
which are critical to effective use.

Allows users to build on not only their prior knowledge of computer systems, but also any
interaction patterns they have learned through use in a predictable way. Predictability is
complementary to interface consistency. A consistent interface ensures that terminology does not
change, that design elements and controls are placed in familiar locations and that similar functions
behave similarly. Predictability expands this to place information or controls where the user
expects it to be. This concept has been discussed in connection with Palm Pilot design– and
especially important if you make an interface which goes beyond the boundaries of simple
platform design standards. Good use of predictability requires careful user analysis and
observation, but can make new functions easy to learn by providing controls where the user expects
them to be.

2.2.4. Usability Evaluation

There exist multiple methods of evaluating usability depending on available resources (time
facilities and labor), evaluator experience, ability and preference, and the stage of development of
the tool under review.

In broad terms it is worth making the following distinctions between evaluation methods:
 1. User-based: where a sample of the intended users tries to use the application
2. Expert-based: where an HCI or usability expert makes an assessment of the application
3. Model-based: where an HCI expert employs formal methods to predict one or more criteria
of user performance

2.2.5.0. Enhancing Usability

Usability is one of the major and often overlooked aspects of web design. Indeed, it should be
considered even prior to the commencement of designing any website be it an eCommerce site or
one that just provides basic information about a product. Usability should be part of the entire
website or software development process. But usability does not stop there. After the website is
launched,

usability testing should dictate what enhancements should be made to the live website. In this
article, I will be discussing five simple ways in which you can improve the usability of your
website.

2.2.5.1. Focus on Readability

Readability is one of the signs that indicate website usability problems. If your site has readability
issues, then there is a high chance that your visitors will get annoyed and abandon it. This
essentially means you lose potential customers. Hence, you must take the necessary steps to ensure
that your site has no readability issues.

In an earlier article, we explained how you can make your site more readable and hence usable by
following typography usability guidelines. Adequate amount of white space, proper paragraph
formatting and displaying of lists using bullet points will also contribute towards making your
website content more readable. Additionally, you can place your design elements such as sidebars,
banners and text boxes on your site in such a way that they do not distract the users when they are
going through the site.

2.2.5.2. Background Color, Texture and Contrast

There are various considerations that need to be made before selecting color. One of the main
reasons is because of the ways in which different colors affect the user’s psychology and
experience. Before selecting the background color of your site, spend some time and think what
color your end-users would prefer. For instance, if you are designing a website for ecologists, you
must go for colors associated with earth and ecology, shades of green, brown or blue. The same
goes for selecting the pattern or textures, used in the background.

Also, check whether there is a contrast between the background color and font color. Otherwise,
it becomes difficult for the users to differentiate between the font and the background.
2.2.5.3. Selection of Images and their placement
Make it a ground rule to use high quality and relevant images on your site. Choose your images
carefully so that they immediately appeal to your target audience and make the necessary impact
on them. For example, if it is a food blog, you can use images of recipes which seem to have been
torn out of an old cookbook. This will set your site apart from other food blogs.

Additionally, make sure that your images do not look out of the place; an image which is not placed
properly, sticks out like a sore thumb on the website. This may distract the end-users and they will
have a negative impression about your site. For more advice about optimization of images for
usability, you can read this recent blog post from Chris Fernandez.

2.2.5.4. Navigation
Nowadays, most of the users access the websites from their mobile devices apart from desktops
and laptops. Therefore, you must make sure that your users are able to navigate your website easily
on their mobile devices as well. To start with, you must select a simple layout and use it on all
your web pages. Additionally, you must do away with horizontal scrolling which the users find
really irritating irrespective of the device they use to browse the site.

2.2.5.5. Effortless Usage

Your users must use your site with ease. You can make this possible in a number of ways like:

1) Limited scrolling – be it horizontal or vertical

2) Making it easy for your users to accomplish their tasks such as taking a call-to-action with
few clicks
3) Not asking users to fill unnecessary, lengthy forms
4) Making sure that users are able to identify links and call-to-action buttons easily
5) Highlighting new arrivals or important products or services on the site so that your regular
visitors can find them with ease
CHAPTER 3:
3.1. Introduction
This chapter contains the research design, survey population, sampling design source of data, data
collection and data analysis.
3.2. Methodology
Structured System Design Analysis Methodology (SSADM) will be adopted as software. The methodology
will help achieve the objective of the system implementation. The model to be used is waterfall model,
which is a sequential software development process, in which progress is seen as flow gradually downwards
through the phases of Requirement which is a description to be developed system. Analysis encompasses
that task that goes into determining the needs and conditions to be met. Design refers to all the activities
involved in conceptualizing, framing, implementing, commissioning and modifying. Implementation,
Verification and Maintenance. It will provide a structured approach. The model itself progresses gradually.

3.3.0. Feasibility Study

A feasibility study is a preliminary study is undertaken to determine and document a project's viability. The
term is also used to describe the preliminary analysis of an existing system to see if it is worth upgrading
all or a part. It is also a way used to determine whether the solution is achievable, given the organization's
resources and constraints.

3.3.1. operational feasibility

The benefits of the proposed system are;

1) Ability to handle large amounts of data

2) Fast and accurate information is possible

3) Security features based on user roles

4) Easy report generations

3.3.2. Economic feasibility

The project is economically feasible as it requires a web browser to gain access. Only cost incurred
are service provider internet charges.

3.3.3. Technical feasibility

To develop this application, an internet connection, a database server, a web server and software
are required. The current project is technically feasible as the application is to be deployed and run
on an android emulator.

3.3.4. Behavioral feasibility

The application should be behaviorally feasible since it requires no technical guidance, all the
modules are user friendly and execute in a manner they were designed to.
3.4. Requirements elicitation
3.4.1. Interviews
This method is used to collect the information from groups or individuals. Analyst selects the
people who are related with the system for the interview. In this method the analyst sits face to
face with the people and records their responses. The interviewer must plan in advance the type of
questions he/ she is going to ask and should be ready to answer any type of question. He should
also choose a suitable place and time which will be comfortable for the respondent.

1) Goals of an interview
2) Solicit ideas and opinions
3) Find facts, verify facts, and Clarify facts.
4) Get the end-user involved.
5) Identify requirements

3.4.2. Questionnaire
It is the technique used to extract information from number of people. This method can be adopted
and used only by a skillful analyst. The Questionnaire consists of series of questions framed
together in logical manner. The questions are simple, clear and to the point. I used this method as
it is very useful for attaining information from people who are concerned with the usage of the
system and is a very cheap source of fact finding.

S/No Question Respondents Response

1. Do you have computers in 14 The department had computers which

the Stock department? were used to mostly, checking mails
and office duties like typing memos
and letters.

2. What are the challenges of 27 Most of the respondents found the

the current system? current system caused a lot of
inefficiency and unmentionable delay.

4. What methods are used to 30 The respondents confirmed that

communicate/inform information was passed through
about point of sale memos, letters and orally.
activities?
5 Do you think the new 28 Most of the management staff believed
system will help to that implementing the System will
improve and reduce improve their services at the
inconvenience department.

Table 1.0: Questionnaire

3.4.3. Observation
Unlike the other fact finding techniques, in this method the analyst himself visits the organization
and observes and understand the flow of documents, working of the existing system, the users of
the system etc. Used to validate the data collected from other methods and when the complexity
of the system prevents a clear explanation by the End-users.

3.5. Data and System analysis

The data collected was later analyzed in order to identify the areas where the system developed
would cover and the changes to be made. The results of the questionnaires and the observations

Table 1.2: Respondents Data

Number of questionnaires issued 57

Number of questionnaires returned 45

Number of questionnaires not returned 10

 QUESTIONNAIRE ANALYSIS
Questionnaire Analysis

60 57

50 45
40
30
20
10
10
0
NUMBER OF QUESTIONNAIRES NUMBER OF QUESTIONNAIRES NUMBER OFF QUESTIONNAIRES
ISSUED RETURNED NOT RETURNED

Figure 1.0: questionnaire response

3.6.0. System Specification

3.6.1 User Requirements
The User Requirements Specification describes the business needs for what users require from the
system. User Requirements Specifications are written early in the validation process, typically
before the system is created. They are written by the system owner and end-users, with input from
Quality Assurance. Requirements outlined in the user requirement specification are usually tested
in the Performance Qualification or User Acceptance Testing. User Requirements Specifications
are not intended to be a technical document; readers with only a general knowledge of the system
should be able to understand the requirements outlined in the user requirement specification.

3.6.2 Functional Requirements

This is a description of activities and services the system must provide to the organization’s. They
include:

1) The login activity handles users that want to access the application and there it confirms
username and password then if correct they are granted access. In the login there is the
communication of the application and database.
2) Shopping cart page where all the available items are stocked for reservation. The picture
represents the item and a small description about its features. The price per month is also
indicated and you can choose to proceed with the reservation by clicking the button
"reserve" which will take you to another page where there is further instruction for
completion.
3) Stock reservation page that loads after the client selects the stock of his/her preference
whereby the client is expected to fill in his/her relevant credentials and select the suitable
payment method in order to complete the booking process.
4) The admin panel consists of two section, namely; the update stock and reserved items
respectively. The update stock section is the section where the admin uploads the newly
arrived stock to the site with the required detailed information of the stock, whereas the
reserved items section allows the admin to view the client’s reservation details and the
stock reserved.
5) Reservation page consists of the client’s detailed reservation information where the receipts
can be presented at any time for reservation where the client is expected to print and present
the receipt on the date the client wishes to claim the reserved stock.
3.6.3 Design Specification
Design Specifications describe how a system performs the requirements outlined in the Functional
Requirements. Depending on the system, this can include instructions on testing specific
requirements, configuration settings, or review of functions or code. All requirements outlined in
the functional specification should be addressed; linking requirements between the functional
requirements and design specification is performed via the Traceability Matrix.

3.6.4. Design
System design is the process of producing design specifications that will satisfy the requirements
specified during system analysis. The design process will entail:

3.6.4.1. Logical design

This involves the process of refining user needs until you get a feature of the type of system they need. This
gives the user’s view of the system and the logical flow of different activities to be performed by the user
using the system.

Figure 1.1: Logical design for shopping Cart login

 USER) SYSTEM DATABASE

login

request reservation details

enter requested details

updates the data to database

saved successfully

request the item reserved maximum

request data from database

returns requested data

request daily, monthly and weekly report

generates requested data

displays the report

Figure 1.2: Logical design for stock reservation Generation

USER) SYSTEM) DATABASE

Require user details

Enter user details

Give details
Request user details

Request user details Replay user details

Give user details

Update data to database

Query database

Figure 1.3: Logical design for users’ signup:

3.6.4.2. Physical Design

This will consider the physical environment which will support the logical flow of my system. E.g.
hardware, files and program procedures. It translates abstract logical design into a specific
technical design for my new system.
Figure 1.3: Physical design of the Admin login page
Figure 1.4: Physical design of Admin Panel
Figure 1.5: Physical design of reservation information page

3.7.0. System Architecture

Is the conceptual model that defines the structure and behavior of a system. An architecture
description is a formal description and representation of a system, organized in a way that supports
reasoning about the structures and behaviors of the system. System architecture can comprise
system components, the externally visible properties of those components, the relationships
between them. It can provide a plan from which products can be procured, and systems developed,
that will work together to implement the overall system.
Figure 1.4: Structure of the system

3.7.1. Use case Diagram

Use Cases are typically used to describe the typically visible interactions that the system will have
with users and external system. It is a graphical representation that describes how users will interact
with the system. This system comprises a number of subsystems that integrate together to form the
overall system requirements and functionality.
Figure 1.5: use case diagram
Figure 1.5: Class diagram

3.7.2. Activity Diagram

An activity diagram is a variation of a state machine in which the states represent the performance of actions
or sub activities and the transitions are triggered by the completion of the actions or sub activities. It
represents a state machine of a procedure itself.

The activity diagram below shows the log in activity

Figure 1.6: Activity Diagram - Login

3.7.3. Database Design
3.7.3.1Product Database Table

Product_ID, product_code, category_name, product_name, product_img_name, product_price,

Table 2.0: 1st Normal form (i)

Product Product_c Category_n Product_n Product_descri Product_img_ Product_p

_ID ode ame ame ption name rice

6 CD-4854 Roters Tractor ERERE yellow 40000

8 3848AJB Farm utility mower Powerful Tractor 30000

Japanese
brand

9 TC384 mowers Tractor Lorem ipsu tractor 400000

26 LA2344 landmover Landmove Good cond agric 50000

r
Table 2.1: 1st Normal form (ii)

product_name product_price product_code product_description

Roters 40000 CD-4854 ERERE

Mower 30000 3848AJB Powerful Japanese

brand

Tractor 400000 TC384 Lorem ipsu

Landmovers 50000 LA2344 Good cond

Table 2.2: 2nd Normal form (i)

product_name product_price

Tractor 40000

Mower 30000

Tractor 400000

Landmover 50000
 Table 2.3: 2nd Normal form (ii)

product_name product_description

Tractor ERERE

Mower Powerful Japanese brand

Tractor Lorem ipsu

Landmover Good cond

3.7.3.2. Reserved Items

customer_ID, from_date, to_date, fname, lname, Phone, Payment, amount, code, codec

Customer_ID from_date To_date fname lname Phone Payment amount code codec

1 2016-10- 2016- Kalvim Manuel 0719997855 mpesa 300000 OEKG5849 CD-58674

4 10-27

Table 2.4: 1st Normal form (i)

Table 2.5: 2nd Normal form

Fname from_date to_date phone Payment

Kalvim 2016-10-04 2016-10-27 0719997855 300000

 Table 2.6: 3rd Normal form

Phone from_date to_date Payment

0719997855 2016-10-04 2016-10-27 300000

Table 2.7: Product table

Field Data type size Constraint

product_ID Int 11 Primary key

Product _code Varchar 60

Category_name Varchar 60

Product_name Varchar 255

Product_description Longtext NOT NULL

Product_img_name Varchar 60

Product_price Decimal (10,2)

Table 2.8: Reserved items Table
Field Data type size Constraint

Customer_ID Int 11 Primary key

from_date Varchar 50

To_date Varchar 50

Fname Varchar 255

Lname Integer 255

Phone Int 11

Payment Varchar 50

Amount Float NOT NULL

Code Varchar 255

Codec Varchar 50

CHAPTER FOUR
4.0 Introduction
This chapter involves generating the code for the android application. It generally means writing
of the source code of the application

4.1 System Code Generation

There are various classes in the application e.g. Login page, uploadstock page, stock reservation
page, and reservation information. The software used in generating the source code for this
application is dream weaver, notepad++ and Wamp Server.
Figure 2.0: Login page

The login activity handles users that want to access the application and there it confirms username
and password then if correct they are granted access. In the login there is the communication of
the application and database.
Figure 2.1: Shopping cart Page

page where all the available items are stocked for reservation. The picture represents the item and
a small description about its features. The price per month is also indicated and you can choose to
proceed with the reservation by clicking the button "reserve" which will take you to another page
where there is further instruction for completion.
Figure 2.2: stock reservation page

Page that loads after the client selects the stock of his/her preference whereby the client is expected
to fill in his/her relevant credentials and select the suitable payment method in order to complete
the booking process.
Figure 2.3: Admin Panel

The admin page consists of two section, namely; the update stock and reserved items respectively.
The update stock section is the section where the admin uploads the newly arrived stock to the site
with the required detailed information of the stock, whereas the reserved items section allows the
admin to view the client’s reservation details and the stock reserved.
Figure 2.5: Reservation information page

Page consists of the client’s detailed reservation information where the receipts can be presented
at any time for reservation where the client is expected to print and present the receipt on the date
the client wishes to claim the reserved stock.
4.2.0. Testing
As mentioned before in this report the about the test plans, it was decided that the system testing
would be an ongoing regular process until the successful completion of the project. This involves
a consideration of strategies that are to be adopted by the user during system operation and the
practical tasks to be completed which include:

4.2.1.0. Testing Plan

Software applications need to be tested to ensure that they conform to the set standards and
specifications. Tests may be conducted on units or individual modules, or even to the collection of
these modules. The goal was to ensure that the software specifications were met. The project then
underwent the following major test phases.

4.2.1.1. Module Testing

The several and different modules of the system were tested separately to ensure they generate the
desirable output. This ensured that errors in the integrated system are minimal. Both black box and
white box testing were employed in this phase to ensure the client was contented with the modules’
implementation.

4.2.1.2. System Testing

The application requires a test after it has been integrated and in use to ensure the output generated
is desirable, the application is running effectively and efficiently and that unexpected results are
realized.

4.2.1.3. Acceptance Testing

Acceptance is the measure of how users find it easy to migrate to the application and agree that
whatever they had desired has been achieved. The client should put across his/her contentment
with the developed application. User acceptance will be conducted as soon as delivery is realized.

4.2.1.4. Usability Testing

This is making sure that objects are usable even after they have been completely tested. This test
involves whether the users will be compatible with the system. This was achieved by involving
different users with different level of computer knowledge and skills to interact with the
application.
 Test Case Action taken Test data

1 Enter Wrong username and password for user at Displays error message Username: haze,hey
the login form password: asdfghjkl,
zxcvbnm
2 Enter correct username and password for user at Displays Main Menu Username:
the login form admin@gmail.com
password: qwerty12
3 Enter Correct username and user position Configure Users is active Username:
admin@gmail.com
password:qwerty12
4 Enter Correct username and user position Displays Home Page but Username:
the configure users button admin@gmail.com
is not active password: qwerty12

5 Select Add product option and enter the required New product info is
information. added in the database

6 Select reserve, section option A reservation is made

7 Select Reports details option and enter the Reports are generated
required fields according to form opened

8 Press Cancel under main menu or log in form A message box prompting
for a yes or no selection
whether to close the
program

Table 3.0: Usability Testing

4.3. Achievements
The following was met all the objectives detailed in the project proposal, which included:

1) Improve data security

2) Automate record filing and retrieval
3) Provide a central database for easy access of data
4) Increase efficiency and usability
5) Improve data consistency and integrity

4.4. Problems encountered

1) Logical errors in the systems’ operations e.g. ‘Action cancelled by associated object.
2) Inadequate computer time
3) Power failure
4) Semantic errors e.g. ‘Type mismatch’ in code variables.
5) Loss of files due to improper backing up procedures.
6) Loss of files due to computer virus attacks
7) Syntax error in code written.
8) Disk failures.
4.4 Limitations
The challenges encountered:

1) Access to the company’s databases was restricted. Being granted access to Blueline Synergy’s
database proved to be cumbersome since only the organization’s administrator and the tech
support personnel have clearance to access the database and it requires special permission for
an external personnel to be granted permission to gain access of the database which is standard
procedure in Blueline Synergy for security reasons.
2) Uncooperative clients. Most Blueline Synergy personnel had a tight working hours schedule
and most of them were only available during lunch hour, other personnel never had time to
carry out interviews or respond to questionnaires due to work related deadlines that took much
of their time.
3) Constant machine failures. the Wamp server application was failing to load the application
constantly which resulted to purchase of the recent Wamp server version that was compatible
with the application.
4) Money. The project funding process proved to be a challenge since the funding for most of
the budgeted items were not readily available.

4.5 Conclusions
Usability and user-centered design are iterative. The work proceeds in a cycle of hypothesis and
evaluation, with a picture of users and design solutions to meet their needs building in richness
and completeness with each iteration. The five E’s (effective, efficient, engaging, error tolerant,
easy to learn) provide the practitioner with a set of characteristics which can be used to organize
and analyze information from users. They offer trace-ability from initial information-gathering
through requirements setting and finally in evaluation. This might allow the understanding of the
specific needs around each characteristic to grow, or be an opportunity to confirm whether the user
requirements were chosen correctly in the early stages of the project. In either case, they let you
go beyond "ease of use" in a practical way and help make it easier to make products more usable.
The application that has been developed has been able to help calculate estimated units. Users can
view charges incurred where those charges are stored in the database.

4.6 Recommendations
To make this system an even better system, the following recommendations should be considered:

1) Integration of the system to the company servers would ensure excellent results where real
time data would be sent based on the account.
2) The help dialogue should be expanded to include more details about every facet of the program
operation from the time the user logs in to the time he shuts the program down
3) Improving multiple search procedures to provide criteria such as names, date apart from ID
4) Improvising of mobile money transfer in the shopping cart.
References
1) (Zhang and M. von Dran 2001-2002).
2) Reichheld and Schefter (2000)
3) (Zhang and M. von Dran 2001-2002).
4) (Palmer 2002). According to Nielsen (1993)
5) Shneiderman 1998; Nielsen 2000; Palmer 2002). Nielsen (2000
6) (Roy et al. 2001).
7) Bergman, E. and Haitani, R. "Designing the Palm Pilot" in Bergman, E. Information
Appliances and Beyond. Morgan Kaufmann: San Francisco, 2000
8) ISO 9241-11: 1998 Ergonomic requirements for office work with visual display terminals
– Part 11: Guidance on usability
9) Landauer, T. K. The Trouble with Computers: Usefulness, Usability, and Productivity. The
MIT Press: Cambridge, MA, 1995.
10) Quesenbery, W. " UPA 99 Workshop Report: Crossing the Chasm - Promoting Usability
in the Software Development Community. " UPA Common Ground, Vol 10 No 1, March
2000
11) This paper was published in the Proceedings of the 48th Annual Conference, Society for
Technical Communication, 2001
12) Thttp://www.wqusability.com/articles/more-than-ease-of-use.html
 APPENDICES

Appendix 1
Table 3.1: Project Schedule

No Activities Estimated Expected Actual Expected Actual

Start End Date End Date Deliverable
Duration Start Date
weeks Date

1 Writing Proposal 4 22/01/16 19/01/16 Proposal

2 Literature review 2 20/01/16 03/02/16 Review of past

literature

3 Proposal 1 04/02/16 11/02/16

submission
presentation

4 Data collection 2 12/02/16 19/02/16 User requirements

5 Analysis 2 20/02/16 03/03/16 Use case descriptions

and diagrams

6 Design 2 04/03/16 17/03/16 Class and sequence

diagrams

7 Implementation 2 18/03/16 03/04/16 Computer system

8 Testing 3 04/04/16 25/04/16 Test report

9 Validation and 1 26/04/16 02/05/16 Validation report

verification

11 Submission of the 1 04/05/16 11/05/16 Final Documentation

documentation report
and presentation
 Appendix 2
ACTIVITIES JAN-FEB MARCH- JULY

No of weeks 1-2 3-5 6-7 8-10 10-15 15-24 24-28

Project
identification

Project plan

Data analysis

System analysis

System design

System coding

System Testing

System
Documentation

Table 3.2: GANTT CHART

 Appendix 3
Item Description Pieces Amount Per Total Amount
item

1. Internet 2 hours per week 56 hours 140 per hour 7,840

for 28 weeks

2. Windows 10 1 3,000

3. Dreamweaver 1 2,000

4. MYSQL 1 2,500

5. Miscellaneous 5,000

6. WAMPP 1 Free

7. Mozilla 1 Free

Web Browser

Total 27,340

Table 3.3: Project Schedule

Appendix 4 Questionnaire

All Employees
1) How can you describe the look and feel of the current system?

Very Appealing Appealing Fair Poor Very Poor

2) How would you describe the navigation of the system?

Very Easy Easy Fair Difficult Very Difficult

3) The textual appearances of the system in one word please describe it.
________________________________________________________
4) he searching tools in the current system rate it.
Very Fast Fast Fair Slow Very Slow

5) Please rate the appearance of the text fields, buttons, text box etc. is it appealing?
Yes No

6) The login form is it easy to use/ operate?

Yes No

7) The forms currently available can anyone easily operate/use them with ease?
Yes No

8) The validation of information is it present?

Yes No

9) In general, is the system easy to use?

Yes No

The Employees (Cleaners)

1) According to your experience with the current System, would you classify it as an
efficient system?

Yes No

2) Do you have literacy of computers?

Yes No
 3) How can you rate the speed of the current system?

Very Fast Fast Good Slow Very Slow

4) The retrieval of information from the database is it?

Very Fast Fast Good Slow Very Slow

5) Do you support the implementation of an efficient system?

Yes No

If No, Why?
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
___________

6) How long does it take to load a given any information (below is in seconds)?
1-5 6-10 11-15 16-20 21-40

7) How long does it take to save a given any information (below is in seconds)?
1-5 6 -10 11-15 16-20 21-40

8) How long does it take to serve a given a client (below is in minutes)?

1-5 6-10 11-15 16-20 21-40

9) What would you like to be changed and why?

________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
_____________________________________________________________________
 The General Managers

1) Do you support the implementation of an efficient system?

Yes No

If No, Why?
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
___________

2) How many workers/cleaners are there in the company currently?

________
3) How can you rate the operations of the system?

Very Fast Fast Good Slow Very Slow

4) According the time you have worked at the White Rose have you heard any complain
with the current system by the employees?
Yes No

5) What would you like to be changed and why?

________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
_____________________________________________________________________
Appendix 5 User Manual
The User account and the Administrators account controls the main functions of the system. The
administrator uses a username and password to log into the system and through this, the data
provided by the system is at the administrator’s disposal. The client only fills in his/her credential
after selecting the item to reserve which is displayed to both the user and the administrator,
however the user is able to print the receipt of after paying the reservation fee to present on the
day the client comes to secure his/her items.

Through the laid down interfaces, the system enables addition of data including binary data into a
linked database which in turn manipulates the data accordingly. After completion in using the
system, the user has an option to Log out which prompts the system to save works by the system
user and hence closing that window. After log out, the user has to log in again before performing
any other tasks.

1) Adding data in the databases is done by the Add button which adds according to the
arrangement of the textboxes.
2) Deleting data is done by the Delete button that clears data and files that are selected from
the display and the databases.
3) Updating a record is done by the Update Button Which highlights a set of data from rows
and changing them to a newer form.
4) The refresh buttons return the databases latest form.
5) The search bar allows the user to search the databases for contents specified.
Appendix 6 Sample code
Admin Process

<?php

session_start();

require_once("connect.php");

require_once("functions.php");

if(isset($_POST['email']) && isset($_POST['password']) ){

$email=sanitize($_POST['email']);

$pass=sanitize($_POST['password']);

$password=md5($pass);

if(check_admin($email,$password)==true){

$_SESSION['user_email']=$_POST['email'];

header("Location:uploadstock.php");

else {

echo "<script language=\"javascript\">\n";

echo "alert('Wrong Username or Password ');\n";

echo "window.location='admin_login.php'";

echo "</script>";

?>
Reservation Process

<?php

session_start();

require_once("connect.php");

require_once("functions.php");

?>

<html lang="en">

<head>

<title>

BLOG

</title>

<meta charset="utf-8">

<meta name="viewport" content="width=device-width, initial-scale=1">

<link rel="stylesheet" href="css/bootstrap.min.css">

<link rel="stylesheet" type="text/css" media="all" href="css/style.css">

<script src="js/jquery.min.js"></script>

<script src="js/bootstrap.min.js"></script>

<script src="js/system.js"></script>

<link rel="stylesheet" href="css/jquery-ui.css" />

<script src="js/jquery-ui.js"></script>

<link rel="stylesheet" href="styles/style.css">

 <script>

/* jQuery ready function. Specify a function to execute when the DOM is fully loaded. */

$(document).ready(

/* This is the function that will get executed after the DOM is fully loaded */

function () {

$( "#from,#to" ).datepicker({

dateFormat: "yy-mm-dd",

changeMonth: true,//this option for allowing user to select month

changeYear: true //this option for allowing user to select from year range

});

);

</script>

</head>

<body>

<div class="container">

<div class="page-header">

<img src="images/header.jpg" class="img-responsive"></div>

<?php
require_once("nav2.php");

?>

<div class="col-md-3">

<div class="panel panel-default">

<div class="panel-heading">

<ul>

<li>

This is our official online stock booking receipts. The receipts can be

presented at any time for reservation.

Print this form and present it on the date of item claim</li>

<li>The information contained on this page is as true as you have provided as with.</li>

</ul>

</div></div></div>

<div class="col-md-6">

<div class="panel panel-default">

<div class="panel-heading">

<center><h4 class="panel-title" style="color:red;">YOUR RESERVATION

INFOMATION</h4></center>

</div>

<div class="panel-body">
<div class="table-responsive">

<?php

$codec=$_SESSION['codec'];

$sql=mysqli_query($conn,"SELECT * FROM reserved_items WHERE codec='$codec' LIMIT

1");

if(mysqli_num_rows($sql)>0){

?>

<table class="table table-bordered table-striped table-striped-column">

<?php

$row=mysqli_fetch_assoc($sql);

?>

<thead>

<tr>

<th>Booking Date</th>

<td><?php echo $row['from_date']; ?></td>

</tr>

<tr>

<th>Receipt No</th>

<td><?php echo $row['codec']; ?></td>

</tr>

<tr>

<th>Full Name</th>

<td><?php echo $row['fname']." ".$row['oname']; ?></td>

</tr>

<tr>

<th>Phone Num</th>

<td><?php echo $row['phone']; ?></td>

</tr>

<tr>

<th>Payments Method</th>

<td><?php echo $row['payment']; ?></td>

</tr>

<tr>

<th>Amount Paid</th>

<td><?php echo $row['amount']; ?></td>

</tr>

</thead>

<tbody>

<tr>

<form method="post" action="receipt.php">

<input type="hidden" name="date" id="date" value="<?php echo $row['from_date']; ?>">

 <input type="hidden" name="receipt_no" id="receipt_no" value="<?php echo
$row['codec']; ?>">

<input type="hidden" name="name" id="name" value="<?php echo $row['fname']."

".$row['oname']; ?>">

<input type="hidden" name="phone" id="phone" value="<?php echo $row['phone']; ?>">

<input type="hidden" name="payment" id="payment" value="<?php echo

$row['payment']; ?>">

<input type="hidden" name="amount" id="amount" value="<?php echo

$row['amount'];?>">

<td><input class="btn btn-default" type="submit" id="receipt" name="receipt"

value="Print Receipt"></td>

</form>

</tr>

<?php } ?>

</tbody>

</table>

</div>
</div></div></div>

<div class="col-md-1">

<?php

//echo $_SESSION['id'];

// unset($_SESSION['id']);

?>

</div>

</div>

</body></html>

Database connection
database: `stock_reservation`

--

-- --------------------------------------------------------

--

-- Table structure for table `products`

--

CREATE TABLE IF NOT EXISTS `products` (

`id` int(11) NOT NULL,

`product_code` varchar(60) NOT NULL,

`category_name` varchar(60) NOT NULL,

`product_name` varchar(255) NOT NULL,

`product_desc` longtext NOT NULL,

`product_img_name` varchar(60) NOT NULL,

`product_price` decimal(10,2) NOT NULL

) ENGINE=InnoDB AUTO_INCREMENT=27 DEFAULT CHARSET=latin1;

--

-- Dumping data for table `products`

--

INSERT INTO `products` (`id`, `product_code`, `category_name`, `product_name`,

`product_desc`, `product_img_name`, `product_price`) VALUES
(6, 'CD-4854', 'Roters', 'Tractor', 'ERERE', 'uploads/yellow.jpg', '40000.00'),

(8, '3848AJ8', 'Farm utility', 'Mower', 'powerfull jap[anees brand', 'uploads/tractor.jpg',

'3000.00'),

(9, 'TC384', 'Mowers', 'Tractor', '\r\nLorem ipsu', 'uploads/tractor.jpg', '400000.00'),

(26, 'LA2344', 'LandMover', 'Landmover', 'good cond', 'uploads/agric.jpgimage_2016-10-31-14-

00-23_58174067c7304', '50000.00');

--

-- Indexes for dumped tables

--

--

-- Indexes for table `products`

--

ALTER TABLE `products`

ADD PRIMARY KEY (`id`),

ADD UNIQUE KEY `product_code` (`product_code`);

--

-- AUTO_INCREMENT for dumped tables

--

--

-- AUTO_INCREMENT for table `products`

--

ALTER TABLE `products`

MODIFY `id` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=27;

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;

/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;