Embed Size (px)
Citation preview
76
CHAPTER 5
SYSTEM IMPLEMENTATION
The new system implementation will cover the hardware and software requirements for
developer and client, alpha and user acceptance testing, as well as screenshots of the
new system.
5.1 System Requirements
In this section, author will elaborate more on the hardware and software specification
used in new system implementation. The assumption for system requirement is the
system will work on one computer only.
5.1.1 Hardware Specification
For hardware specification is divided into two, for developer and for client. The
computer used for the development is different from where the system is installed.
5.1.1.1 Developer
Category Minimum Requirement
Processor Intel(R) Core(TM) Duo CPU T2400, 1.83GHz
Memory 2GB DDR2 RAM
Hard Disk 40GB 5400RPM
Hard Drive DVD-ROM drive
Display 1280x800 or higher resolution
Network Card Intel® PRO/Wireless 3945ABG Network Connection
Table 5.1 Developer Hardware Requirement
77
5.1.1.2 Client
Category Minimum Requirements
Processor Intel Pentium 3 or 4/ AMD Athlon Processor
Memory 256MB RAM
Hard Disk 40GB 5400RPM
Display 1280x800 or higher resolution
Network Card Intel® PRO/Wireless 3945ABG Network Connection
Table 5.2 Client Hardware Requirement
5.1.2 Software Requirements
Software requirements also cover software for developer and client computer. In order to
develop and implement the new system, it is necessary to use key software as stated
below:
5.1.2.1 Developer Software
Software stated below are the main software used for developing the new system using
ASP.Net web application:
Microsoft Windows XP or 7
Microsoft Visual Studio 2008
Microsoft SQL Server 2008
Microsoft Office Excel 2007
Internet Information Service (IIS)
78
5.1.2.2 Client Software
Basically there is no particular software requirement for client computer, as long as the
computer can access web browser such as Internet Explorer, Mozilla Firefox, and others.
However, the minimum software requirements for client computer will be:
Microsoft Windows XP or 7
Internet Information Service (IIS)
Web browser (i.e. Internet Explorer, Mozilla Firefox, Google Chrome, etc)
5.2 Testing
5.2.1 Alpha Testing
Alpha testing is done by the programmer himself in order to find if there are any bugs or
errors before handling the program to the end user. All bugs and errors should be fixed
for the program to work properly as expected. Programmer found some bugs especially
on the database linkage to the program where the page failed to retrieve requested sales
data from the database. It turned out that there was a slight misspelling on the database
query code and all errors has been fixed properly. No documentation is recorded for this
testing phase.
5.2.2 User Acceptance Testing
This testing phase is done by testing users of the program with several test cases and
author did the testing to two users, store manager and one staff. The purpose of this
testing is to make sure that the new developed system meet the user requirements. User
79
acceptance testing focuses on some main things, there are user interface, system
functions, and user suggestions if any improvement is required.
From the acceptance testing, overall the user is satisfied with the new system. Every
aspect is fully met the requirements and user expectations. User stated some suggestion
for the future development; however user felt that this system is enough for current
implementation.
5.2.2.1 Test Case
No Test Cases for Manager Page Expected Output Result
1 Launch the system Sales database is opened and
shows the login page
Pass
2 Login for manager with valid
information
Login is successful and
redirect to the home page
Pass
3 Choose „Stock List‟ menu Stock List is opened Pass
4 Choose „Edit‟ on one sales item The edit bar is shown and user
can change the data
Pass
5 Save the edited sales item The changes is saved and
display the edited sales item
on the stock list
Pass
6 Cancel to edit the sales item The changes will not be saved
and direct to the stock list
page
Pass
7 Open „Tambah Stock Baru‟
menu
The page is opened Pass
80
8 Add new sales item to database
by click on Save button
The newly added item is saved
and displayed on the stock list
Pass
9 Cancel adding new item by
choose the Cancel button
Reset the form Pass
10 Choose „Bon Tunai‟ menu The page is opened Pass
11 Create new cash invoice with
valid input
Saved the invoice and redirect
to Bon Tunai confirm page
Pass
12 Cancel creating new cash invoice
by click on button „Batal‟
Reset the form Pass
13 Choose „Bon Kredit‟ menu The page is opened Pass
14 Create new credit invoice with
valid input
Saved the invoice and redirect
to Bon Kredit confirm page
Pass
15 Cancel creating new credit
invoice by click on button „Batal‟
Reset the form Pass
16 Choose the „Pelanggan‟ menu The „Daftar Pelanggan‟ page
is opened
Pass
17 Edit the customer data The edit bar is shown and user
can change the data
Pass
18 Save the edited customer data The changes is saved and
display the edited data on the
customer list
Pass
19 Cancel to edit the customer data The changes will not be saved
and direct to the customer
page
Pass
81
20 Open „Tambah Daftar
Pelanggan‟ menu
The page is opened Pass
21 Add new customer data to
database by click on Save button
The newly added customer is
saved and displayed on the
customer list
Pass
22 Cancel adding customer by
choose the Cancel button
Reset the form Pass
23 Choose the „Edit Bon Tunai‟
page
The page is opened Pass
24 Fill in the form with valid name,
month, and year then continue
List the selected data Pass
25 Delete the cash sales entry The sales entry will be deleted
from list
Pass
26 Edit the cash invoice The page will redirect to the
edit invoice form
Pass
27 Save the edited cash invoice The changes is saved and the
edited sales entry will be listed
in the Rekap page
Pass
28 Choose the „Edit Bon Kredit‟
page
The page is opened Pass
29 Fill in the form with valid name,
month, and year then continue
List the selected data Pass
30 Delete the credit sales entry The sales entry will be deleted
from list
Pass
82
31 Edit the credit invoice The page will redirect to the
edit invoice form
Pass
32 Save the edited credit invoice The changes is saved and the
edited sales entry will be listed
in the Rekap page
Pass
33 Open the „Rekap Bon Tunai‟
menu
The page is opened. Pass
34 Fill in the form with valid month
and year then continue
List the selected data Pass
35 Open the „Rekap Bon Kredit‟
menu
The page is opened. Pass
36 Fill in the form with valid month
and year then continue
List the selected data Pass
37 Choose Keluar button to exit and
log out from the system
User will log out and redirect
to the login page
Pass
38 Choose Batal button to cancel the
log out
User will be redirect to the
homepage
Pass
Table 5.3 Test Cases for Manager Page
No Test Cases for Staff Page Expected Output Result
1 Login for staff with valid
information
Login is successful and
redirect to the home page
Pass
2 Choose „Stock List‟ menu Stock List is opened Pass
83
3 Choose „Bon Tunai‟ menu The page is opened Pass
4 Create new cash invoice with
valid input
Saved the invoice and redirect
to Bon Tunai confirm page
Pass
5 Cancel creating new cash invoice
by click on button „Batal‟
Reset the form Pass
6 Choose „Bon Kredit‟ menu The page is opened Pass
7 Create new credit invoice with
valid input
Saved the invoice and redirect
to Bon Kredit confirm page
Pass
8 Cancel creating new credit
invoice by click on button „Batal‟
Reset the form Pass
9 Choose „Keluar‟ menu The page is opened Pass
10 Choose Keluar button to exit and
log out from the system
User will log out and redirect
to the login page
Pass
11 Choose Batal button to cancel the
log out
User will be redirect to the
homepage
Pass
Table 5.4 Test Cases for Staff Page
Next step, author creates a “Dirty Test Cases” to test the system from any errors. This
test case will test the negative process of the system.
No Test Cases Expected Output Result
1 Login for manager with invalid
information
Login is unsuccessful and
system give error warning
Pass
2 Add new sales item without The system will give error Pass
84
filling in the form warning
3 Create new cash invoice with
invalid input
System will give error
warning and unable to
continue to confirm page
Pass
4 Create new credit invoice with
invalid input
System will give error
warning and unable to
continue to confirm page
Pass
5 Add new customer without
filling in the form
The system will give error
warning
Pass
6 Edit the cash invoice with invalid
input
System will give error
warning and unable to
continue to confirm page
Pass
7 Fill in the „Edit Bon Tunai‟ form
with invalid name, month, and
year then continue
System will show no data Pass
8 Edit the credit invoice with
invalid input
System will give error
warning and unable to
continue to confirm page
Pass
9 Fill in the „Edit Bon Kredit‟ form
with invalid name, month, and
year then continue
System will show no data Pass
10 Fill in the „Rekap Bon Tunai‟
form with invalid month and year
then continue
System will show no data Pass
11 Fill in the „Rekap Bon Kredit‟
form with invalid month and year
System will show no data Pass
85
then continue
12 Login for staff with invalid
information
Login is unsuccessful and
system give error warning
Pass
13 Create new cash invoice with
invalid input (from Staff page)
System will give error
warning and unable to
continue to confirm page
Pass
14 Create new credit invoice with
invalid input (from Staff page)
System will give error
warning and unable to
continue to confirm page
Pass
Table 5.5 Dirty Test Cases
5.2.3 Usability Testing
Next testing is usability testing, conducted in Abadi Motor shops on January 5th
, 2013.
The purpose of testing was to assess the usability of the user interface design, system
functionality, and access to information provided. All templates used in this usability
testing are derived from usability.gov [20].
Total of 6 users participated in both task-related and post-task overall survey to ensure a
stable result. Each individual session lasted for approximately 10 minutes. All
participants are member of Abadi Motor and have little experience in using website and
web application; there are three users act as admin and three as staffs that will use the
system after the implementation. Admin will do tasks number 1 to 8, where staffs will
do tasks 9 to 11.
After each task, the administrator asked the participant to rate the interface on a 5-point
scale with measures ranging from Strongly Disagree to Strongly Agree. Post-task
scenario subjective measures included:
86
How easy it was to perform tasks
Accurate information provided
Time matters
After the last task was completed, the test administrator asked the participant to rate the
website overall by using a 5-point scale (Strongly Disagree to Strongly Agree) for eight
subjective measures including:
Ease of use
Frequency of use
Learn ability - how easy it would be for most users to learn to use the website
Information facilitation – how quick participant could find information
Usefulness
For this testing, author developed a set of test cases derived from the use case diagram
for two actors.
No Actor Tasks Details
1 Manager User Login Username: manager; password:
manager. Login must be successful
2 Manager Look Up Item Availability Search item number 12261-0M010
3 Manager Create New Purchase Invoice Create one new „Bon Tunai‟ with
name: manager. Input: Qty 1, Part
number: 04445-0B010.
4 Manager Edit Purchase Invoice Search the Bon Tunai with name:
manager, month 1, year 2013. Change
the qty to 2, save.
87
5 Manager Add new item Input new item, then save.
User 1: 90915-YZZD2; 60,000;
42.5%; 100.
User 2: 90915-YZZD4; 60,000;
42.5%; 100.
User 1: 90915-TD004; 72,000; 32.5%;
100.
6 Manager Edit sales item Search item number 12261-0M010,
change the discount to 50%.
7 Manager Produce monthly bill Rekap Bon Kredit for name „Tes
Kredit‟, month 12, year 2012.
8 Manager View sales data Open the customer data.
9 Staff User Login Username: staff; password: staff.
Login must be successful
10 Staff Look Up Item Availability Search item number 12261-0M010
11 Staff Create New Purchase Invoice Create one new „Bon Kredit‟ with
name: staff. Input: Qty 1, Part number:
04445-0B010.
Table 5.6 Usability Testing Test Cases
88
Task Completion Rate for Manager
Participant Task
1
Task
2
Task
3
Task
4
Task
5
Task
6
Task
7
Task
8
1 √ √ √ √ √ - √ √
2 √ √ √ - √ √ √ √
3 √ √ √ √ √ √ √ √
Success 3 3 3 2 3 2 3 3
Completion
Rates 100% 100% 100% 66.6% 100% 66.6% 100% 100%
Table 5.7 Task Completion Rate for Manager
For the completion rates, all users successfully did all tasks, except task 4 and 6. One
user failed to complete task 4, which is edit purchase invoice and also one user failed to
complete task 6 (edit sales item) resulting completion rates of 66.6%. While other tasks
got completion rates of 100%.
The errors happened because users failed to locate the function menu, however the error
did not represent the user as a whole, and it will not impact anything on the system
usability. Therefore no modification needed on user interface of the system.
Task Completion Rate for Staff
All participants for staff page successfully complete task 9 to 11, resulting in 100%
completion rates.
Participant Task
9
Task
10
Task
11
4 √ √ √
5 √ √ √
89
Participant Task
9
Task
10
Task
11
6 √ √ √
Success 3 3 3
Completion
Rates
100% 100% 100%
Table 5.8 Task Completion Rate for Staff
Task Ratings
After the completion of each task, participants rated the ease or difficult of completing
the task for three factors:
How easy it was to perform tasks
Accurate information provided
Time matters
The 5-point rating scale ranged from 1 (Strongly disagree) to 5 (Strongly agree). Agree
ratings are agree and strongly agree ratings considered as the user agrees that the tasks
are easy to perform, the system provides accurate information, and spent little time
doing the tasks.
Easy perform tasks:
Most participants agree that nearly all tasks are easy to perform as they got 100% rating.
However some tasks get average rating, there are create new invoice, edit sales item,
produce monthly bill, and view sales data, means they are still doable but need more
effort. To conclude, all tasks are relatively easy to perform.
System provides accurate information:
In general, participants consider they can get accurate information from each tasks.
Some tasks get average rating of 66.6%, there are create new invoice, add new item, edit
and sales item. The rest of tasks get 100% rating means participants found that the
system gives them accurate information.
90
Timely matters:
Participants found that they took the longest time in doing task 3 which is creating new
purchase invoice. Task 6 and 7 which is add new item and produce monthly bill took the
second longest time to complete. The rest of tasks are considered can be completed in
shorter time.
Below are tables containing the result of each task ratings given by the participants:
Task Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
Mean Percent
agree
Weight 1 2 3 4 5
1 0 0 0 1 2 4.67 100.00%
2 0 0 0 2 1 4.33 100.00%
3 0 0 1 1 1 4.00 66.67%
4 0 0 0 0 3 5.00 100.00%
5 0 0 0 2 1 4.33 100.00%
6 0 0 1 2 0 3.67 66.67%
7 0 0 1 1 1 4.00 66.67%
8 0 0 1 0 2 4.33 66.67%
9 0 0 0 1 2 4.67 100.00%
10 0 0 0 1 2 4.67 100.00%
11 0 0 0 2 1 4.33 100.00%
Table 5.9 Ease of Finding Information
Task Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
Mean Percent
agree
Weight 1 2 3 4 5
1 0 0 0 1 2 4.67 100.00%
2 0 0 0 0 3 5.00 100.00%
3 0 0 1 1 1 4.00 66.67%
4 0 0 0 2 1 4.33 100.00%
5 0 0 1 1 1 4.00 66.67%
6 0 0 1 2 0 3.67 66.67%
7 0 0 0 1 2 4.67 100.00%
8 0 0 2 1 0 3.33 33.33%
9 0 0 0 1 2 4.67 100.00%
91
10 0 0 0 1 2 4.67 100.00%
11 0 0 0 2 1 4.33 100.00%
Table 5.10 Accurate Information Provided
Task Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
Mean Percent
agree
Weight 1 2 3 4 5
1 0 0 0 3 0 4.00 100.00%
2 0 0 1 2 0 3.67 66.67%
3 0 0 2 1 0 3.33 33.33%
4 0 0 0 1 2 4.67 100.00%
5 0 0 0 2 1 4.33 100.00%
6 0 0 1 2 0 3.67 66.67%
7 0 0 1 1 1 4.00 66.67%
8 0 0 0 1 2 4.67 100.00%
9 0 0 0 0 3 5.00 100.00%
10 0 0 0 1 2 4.67 100.00%
11 0 0 1 2 0 3.67 66.67%
Table 5.11 Time Matters
Task Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
Mean Percent
agree
Weight 1 2 3 4 5
1 0 0 0 1 2 4.67 100.00%
2 0 0 0 2 1 4.33 100.00%
3 0 0 0 2 1 4.33 100.00%
4 0 0 0 3 0 4.00 100.00%
5 0 0 1 2 0 3.67 66.67%
6 0 0 1 1 1 4.00 66.67%
7 0 0 1 2 0 3.67 66.67%
8 0 0 0 2 1 4.33 100.00%
9 0 0 0 3 0 4.00 100.00%
10 0 0 0 1 2 4.67 100.00%
11 0 0 0 1 2 4.67 100.00%
Table 5.12 Overall Result
92
Task
Ease to
Perform
Task
Accurate
Information
Time
Matters Overall
1- User Login 4.7 (100%) 4.7 (100%) 4 (100%) 4.7 (100%)
2 - Look Up Item Availability 4.3 (100%) 5 (100%) 4 (100%) 4.3 (100%)
3 - Create New Purchase
Invoice 4 (66.6%) 4 (66.6%) 3.3 (33.3%) 4.3 (100%)
4 - Edit Purchase Invoice 5 (100%) 4.3 (100%) 4.7 (100%) 4 (100%)
5 - Add new item 4.3 (100%) 4 (66.6%) 3.7 (66.6%) 3.7 (66.6%)
6 - Edit sales item 3.7 (66.6%) 3.7 (66.6%) 4. 7 (100%) 4 (66.6%)
7 - Produce monthly bill 4 (66.6%) 4.7 (100%) 4 (66.6%) 3.7 (66.6%)
8 - View sales data 4.3 (66.6%) 4.3 (100%) 4.7 (100%) 4.3 (100%)
9 - User Login 4.7 (100%) 4.7 (100%) 5 (100%) 4 (100%)
10 - Look Up Item Availability 4.7 (100%) 4.7 (100%) 4.7 (100%) 4.7 (100%)
11 - Create New Purchase
Invoice 4.3 (100%) 4.3 (100%) 3.7 (66.6%) 4.7 (100%)
*Percent Agree (%) = Agree & Strongly Agree Responses combined
Table 5.13 Mean Task Ratings & Percent Agree
Time on Task
The testing process recorded the time on task for each participant. Some tasks were
inherently more difficult to complete than others and is reflected by the average time on
task.
As seen from the table 5.8, task 5 which is adding new item took the longest time to
complete with average of 35.80 seconds. The shortest completion time recorded on task
9, which is login for staff with average of 13.10 seconds. Conversely completion times
93
ranged from 13 second to 35 seconds, all below one minutes to complete each task with
most times around 30 seconds.
Task User 1 User 2 User 3 User 4 User 5 User 6 Average
1 12.62 20.00 16.00 - - - 16.21
2 11.00 16.00 18.60 - - - 15.20
3 25.83 40.50 37.50 - - - 34.61
4 28.23 36.20 31.40 - - - 31.94
5 29.80 37.60 40.00 - - - 35.80
6 27.99 32.00 38.30 - - - 32.76
7 25.55 22.00 27.80 - - - 25.12
8 09.00 14.00 18.20 - - - 13.73
9 - - - 09.30 12.00 18.00 13.10
10 - - - 18.18 25.00 20.30 21.16
11 - - - 24.97 43.70 30.50 33.06
Total 02:50.0 03:38.3 03:47.8 00:52.5 01:20.7 01:08.8 01:07.3
Table 5.14 Time on Task (in seconds)
Errors
Author only recorded two errors happened during usability testing, where some users
failed to complete a particular task. There are task 4 and 6, edit purchase invoice and
edit sales item with one error each. There is no other error recorded in the testing
progress. As explained before, errors did not represent the user as a whole, and it will
not impact anything on the system usability. Therefore no modification needed on user
interface of the system.
94
Summary on Data
Task Task
Completion
Errors Time on Task
(in seconds)
Satisfaction*
1 3 0 16.21 4.7 (100%)
2 3 0 15.20 4.3 (100%)
3 3 0 34.61 4.3 (100%)
4 2 1 31.94 4 (100%)
5 3 0 35.80 3.7 (66.6%)
6 2 1 32.76 4 (66.6%)
7 3 0 25.12 3.7 (66.6%)
8 3 0 13.73 4.3 (100%)
9 3 0 13.10 4 (100%)
10 3 0 21.16 4.7 (100%)
11 3 0 33.06 4.7 (100%)
Table 5.15 Summary of Data
* Satisfaction = Mean combined rating across three post-task measures: How easy it was
to perform tasks, accurate information provided, and timely matters.
Overall Metrics
After task session completion, participants rated the site for five overall measures. These
measures include:
Ease of use
Frequency of use
Usefulness
Learn ability - how easy it would be for most users to learn to use the application
Information facilitation – how quick participant could find information
95
All of the participants (100%) agreed (i.e., agree or strongly agree) that the website was
easy to use, quick to find information, and they will frequently use the system. They also
believe most users will learn to use the system in no time. At last, the majority of
participants (80%) agreed that the system will be useful for them in everyday business.
See table 5.12 below.
Table 5.16 Overall Rating Result
Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
Mean
Rating
Percent
Agree
Ease of Use - - - 3 2 4.4 100%
Usefulness - - 1 2 2 4.2 80%
Frequency of Use - - - - 5 5 100%
Learn ability - how
easy it would be for
most users to learn
to use the
application
- - - 4 1 4.2 100%
Information
facilitation – how
quick participant
could find
information
- - - 2 3 4.6 100%
96
5.3 Implementation
The new system will be implemented on the Abadi Motor owner‟s (store manager)
personal laptop. The entire application folders, server, and database, as well as
supporting software will be copied and installed to the laptop. The idea is to connect the
laptop computer to the external monitor to be used in the shop by the staff, or simply use
the laptop to access the system. Therefore the laptop will act as the PC and the system
data will be securely recorded. This is also because of the system is offline, so it will
cause so much hassle to use more than one computer as the database and system is only
installed in one place. However if in the future the system will need to be installed on
more computers, it still applicable using the LAN cable to connect the database.
The system will mostly use during office hours because invoices are recorded by the
staff and rarely by the store manager. However store manager still have privilege to
create and edit the invoice created by staffs. If store manager wants to check on the sales
or do some update to the data, he can do it anywhere anytime using his laptop.
While it is implemented, the new system is expected to give more efficiency and data
security to Abadi Motor. It will also help daily operational activities and improve sales
performance; hopefully it can also improve customer service performance. The new
sales database system will support the business as the stepping stone to help the growth
of the business line, especially toward expanding business to the online e-commerce
store.
