BOOK TRANSACTION SYSTEM

Transcription

1 BOOK TRANSACTION SYSTEM NORHAFIZAL AHMAD Faculty of Computer Universiti Teknologi Malaysia SITI WARDAH ABDUL HAMID Faculty of Computer Universiti Teknologi Malaysia FATIN FARHANA MAS UD Faculty of Computer Universiti Teknologi Malaysia ABSTRACT In this report we describe the iterative design and testing for Book Transaction System at University of Malaya library. The reports describe the problem at the system design, implementation of the system, overview on the feedback and evaluation of the system. AUTHOR KEYWORDS Author Keywords Human-Computer Interaction; HCI; Book Transaction System; System app; General Terms Human Factors; Design; PROBLEM Our team very keen to develop and upgrade a new interface which are combined from an existing interface using 2 separate machines become one machine (include borrowing & returning). Achievement and goal for this system is to design and introduce Book Transaction Process to users. Enter your problem: - Process borrow & return books has been divided to different system which are Self Check Machine (Borrows) & Self Return Machine (Return); - User have to bring their Matric Card to access the system; - Receipt will be given after end up the process. User will get 2 receipts during Borrow and returning to the system. In Addition, there is no detail of penalty Information stated in the receipt; - Sometimes the scanner has a problem to detected a book barcode and user have to repeating the process; - User who had penalty should pay manually At the library counter; - There is no system voice to guide disable User for using this interface; USERS The Book Transaction System is primarily target for 4 users which are student, staff academic, supporting staff and alumni members. SOLUTION There are some points to upgrade the existing interface such as: STEP 1 (BORROW) - Touch matric card for registration purpose for those user who were are not register. User must fill in the information need it such as , mobile no & address; - User compulsory to register their thumb at the screen provided. This is the other option for user to do using the system. STEP 2 (BORROW) - User scan the book barcode - The details of book information will be appear in the screen such as Customer Name, Title of Book, Barcode ID, Date of borrows, due date of return, Total Items and Penalty of Information. - User have to verify an information stated before sending the verification through their registered . STEP 3 (RETURN) - Touch matric card/ thumb print at the screen; - Scan barcode and enter the book into a machine drawer and confirmation returning of book will be appear in the screen. User have to verify the message appear for completing this process; - An information of book will be send through given (TQ ).

2 STEP 3 (RETURN + PENALTY) - Touch matric card/ thumb print at the Screen; - Information of penalty will be appearing in the screen such as Title of Book, Barcode ID, Over Due Date and Amount of Penalty. - User can pay the penalty through online payment system with selected bank provided in the system such as CIMB Bank, Bank Islam and BSN. - Returning process can be continuing as at STEP 3 (RETURN). PERSONAS Mr. Adib is a final year student at Faculty of Engineering, University of Malaya. He always do Assignments, final year project, and thesis. He Needs references such as internet and books to get additional information to his project. He borrows numbers of books at the library frequently. He usually wanted to return the books and at the same time borrow another book but have to use separate machine and it is very inconvenience. He always forgot to bring his Matrix Card to the library for return and borrowing purpose, a bit clumsy as he always forgot where he put things. He hopes to find easier command at the machine provided for return and borrowing. Dr. Shazatul Ermiza is a lecturer at Faculty of Law. She likes simple things and a short tempered person as she doesn t like to complicate things. She rarely brings cash in her wallet and finds difficulty to pay the penalty in cash when she wanted to return the borrowed book. As a lecturer she has limited times and often busy with consultant works and classes. She finds that the library system for returning and borrowing books takes too much of time because given two machine which are too far away. She hates to queue at counter to pay penalty and hopes for a better solution. Mr. Yuvaneswaran A/L Maniam is a 40 years Old former student at University of Malaya. He currently working as a Consultant at a private company and went outstation frequently to overseas. He rarely in Malaysia and always missed the deadline given to the return the books. Plus, he always lost the receipt and he always does not remember the date to return the book. In additional, the information at receipt can blur in time. It can trouble him as he has bad eyesight. When the receipt goes blur the date of books return can t be seen. There is no notification indicates that he have to return the book on the deadline. TASKS Below are the major tasks we initially expected all users of borrowing, returning and penalty system to be comfortable and confident computing. 1. User Sign Up Goal: Allow the user to activate matric card and register for thumbprint Precondition(s): For those users not register yet Subtask(s): User must click SIGN UP! for starting the process 2. User Sign In Goal: Allow the user to scan matric card or use thumbprint to access the system Precondition(s): Matric card must be in good condition and scan the thumbprint after receiving lighting signal from the place provided Subtask(s): User must click SIGN IN for starting the process 3. Select Task for Borrowing and Returning of Books Goal: Allow the user to select task for borrow book or return book Precondition(s): User must identified which task want to select based on user purpose Subtask(s): User must click BORROW BOOK or RETURN BOOK 4. Borrow Book Goal: Allow the user to scan the book barcode at drawer book provided Precondition(s): User must put the book properly at the drawer book for scanner detected the barcode

3 Subtask(s): User must click NEXT for continuing the process 5. Return Book Goal: Allow the user to scan the book barcode at drawer book provided Precondition(s): User must put the book properly at the drawer book for scanner detected the barcode Subtask(s): User must click NEXT for continuing the process 7. Notifications (Borrow & Return) Goal: Notification will be sent to user shortly to mention returning of period within one month from the date of borrowing and Notification of books return receipt will be sent to user Subtask(s): User must click FINISH to complete the process DESIGN Final Design The final design of Book Transaction System exists as a machine of Borrowing, Returning and Penalty System build for University of Malaya Library using Microsoft Office (PowerPoint). The machine will be located at the lobby of library. The main page of Book Transaction System has been design with clearly label text and buttons. We wanted to make sure users are confronted with the interface features they absolutely need to begin the process of borrowing and returning of books. Everything is clearly and easy to understand to interact with the system. 6. Penalty Goal: User can pay the penalty through CIMB Clicks, PayPal and Maybank2u Online Banking Precondition(s): User must clear up the penalty overdue to proceed to next process for returning of book purpose. User must insert ID of payment. Subtask(s): User must click CIMB Clicks, PayPal and Maybank2u for continuing the process 7. Notifications for completion of payment Goal: Notification will be appear after completion penalty payment Subtask(s): User must click NEXT for continuing the process Figure1. MAIN PAGE Book Transaction System is positioned in the centered of the interface to inform users the name of the system they are using. The icon of owl carrying a book is symbolic to show that the system easier to use it. To the right of the main page have a two button which are SIGN IN and SIGN UP!. For Sign Up function to inform users for registration their particulars and thumbprint. This Sign In button will link the users to select task process involved.

4 Figure2. SIGN IN After user clicking SIGN IN button, users are brought to page displaying a SIGN IN page to scan the matric card or use thumbprint to access the next page as below:- Figure5. BORROW BOOK This page instructed towards user who want to borrow books and to inform user to insert the book at the drawer book & scanner barcode. Figure3. SIGN UP SIGN UP is the process for user those who not register for using this system. The user compulsory to use matric card and thumbprint for data registration. Figure6. RETURN BOOK This page instructed towards user who want to return books and to inform user to insert the book at the drawer book & scanner barcode. Figure4. SELECT TASK This page was designed to allowed user to select task which are borrow and return book button. Figure7. NOTIFICATION FOR BORROW BOOKS This page has been designed for giving notification of the transaction will be sent to user immediately. This page also mention about the validation of returning book period within one month from the date of borrowing.

5 Figure8. NOTIFICATION FOR RETURN BOOKS This page has been designed for giving notification for the return transaction and notification of books return receipt will be sent to user . Figure11. NOTIFICATION FOR PENALTY This page has been designed to inform user about completion payment by user. Transaction ID will be appearing at the screen to make confirmation payment. An notification will sent to user as a payment proof of this transaction. IMPLEMENTATION Figure9. PENALTY This page has been designed for those users have penalty overdue to make clearance payment before user return their book. There are having three banks to make online banking which are CIMB Clicks, PayPal and Maybank2u. Figure10. Completion of Payment ID This page has been designed to complete user purchase using the details from user payment ID. Background We have discovered the system in our current library of University of Malaya while borrowing and returning books. We found that there were two different machines in processing both borrowing and returning books. We realized that some students experienced difficulties in using the machine as it is not totally userfriendly. The librarians were so kind enough as to help the students out. While observing the incident, we suddenly got an idea on how to create a system that is convenient to all students, lecturers and alumni s. Since borrowing books are frequent activities among the students, the Book Transaction System were designed to save time, save paper because no need to provide the receipt, reduced of attendance library at the counter and so on. In the making of this system, we gathered feedbacks from students and lecturers who tried on the existing system. Most of them has given a constructive comment to improve and upgrade it to be more efficient, helpful and user-friendly.

6 Motivation Once a layout was chosen and agreed upon unanimously by the group, we jumped straight into the technical implementation, believing that the rest of the design could be done in conjunction. Although our initial aspirations involved creating full web application with using Microsoft Office (PowerPoint). We are try and error on this system but sometimes fail to get a good result from the user. The user said, the system is not enough or complete because still not friendly user. We are discuss back regarding this matter and come out with a new idea and feedback from user. Finally, we are fulfill what the user needed and we are felt satisfied on this system. Setup From the start, we decided that we wanted our functional prototype to be accessible in one system which are voice navigation, matric card, and thumbprint & disable button. Now we separate it to get friendlier user, easier for user to understand and using it. This was definitely a great decision for how little work it took to setup. Also, we wanted to create notification to inform that user will get information about returning period and completed the payment. The reason is to save the paper and only using to get notification. For one, it made user testing much more convenient for both parties. Our testers were glad to be able to do their tests at the one place like at library and it is successfully test and get a minor comment from the user. Our setup for this hosted environment was simple. We used Microsoft Office (PowerPoint) to make a prototype. Execution When we finished setting up our development environment, we began executing on our designs through Microsoft Office (PowerPoint). Throughout the process, we tried to establish and measure certain metrics that would let us know how effective the mechanics of the design were. One of the primary challenges was to ensure that the user could identify and use each of the button properly. The disable button, we were using at this in some areas, but failed in others to understand. The Button Sign In, Sign Up, Next, Borrow, Return are a simple button. Another core focus of our implementation was interactivity. Many traditional sites filter results by resubmitting a different query to the server. We opted for a more dynamic, modern approach, fetching all of the data at once and doing the manipulations in place, as needed. This is a totally feasible technique, even when using real data, given the power and flexibility of most modern system in the Library University EVALUATION Throughout the design process of Book Transaction System, we went through several updated versions of the interface and some processes based on user feedback that we has received. The two main types of evaluation we performed using our interface were Paper Prototyping and User Testing. Paper Prototyping The first method of evaluation we performed on our system was paper prototyping. To start this process, we sketched, type it properly in the Microsoft Word and paste in purple cardboard for our best representation of the Book Transaction System interface. We also provided for four type of small cardboard to instruct user do the related process were included: Sign up & Borrow 2 Books, Sign in & Borrow 2 Books, Return Book without Penalty & Return Book with Penalty. We did this for users could successful in all processes while using this system. Figure12. PAPER PROTOTYPE IN ACTION

7 Through the prototyping test, we found that our users were happy, convenient and easier to understand with tasks given from the beginning process. Figure13. PAPER PROTOTYPE IN ACTION Once having produced the materials needed to perform paper prototyping test, we created the briefing needed to present to volunteer users who agreed to help us and provide us with their feedback. The briefing quickly informed the user what it is and how this system works. We also told the user what they will be doing based on the given process card as shown in Figure14. While briefing given to user, we has highlighted that the procedure is voluntary and they can raise their hand at any time if they failed to continue the particular process. We had three users perform our four tasks using the paper prototype we had created for this study. The four tasks were: 1. New User: Select Sign Up, touch matric card for thumbprint registration, select task for borrow book, scan each book barcode at the drawer book and click finish. 2. Existing User: Sign In to your account using Matric Card/Thumbprint, select task for borrow book, scan each book barcode at the drawer book and click finish. 3. Sign In your account, select task for return book, insert the book at the drawer book for scanned purpose, click next and finish. 4. Sign In your account, Penalty overdue payment, insert Payment ID, select task for return book, insert the book at the drawer book for scanned purpose, click next and finish. We also received a useful feedback from users wanting to do more with the system. Some felt that the current interface not so much interactive with the warm color. There were no reminder sent near the due date of borrow book. For these cases, we will changed the interface be more attractive colors and we will think how to upgrade the notification system in the future revision. User Testing The last method of evaluation performance was User Testing. The preparation of this method of evaluation was very similar to that of paper prototyping processes. For this stage we have identified nine of users from Faculty of Engineering, University of Malaya. The reason why we have choose our users from the particular faculty because my project leader and me are working here. As a staff here, we have so much choices to identified our users from any different level and position. Furthermore, we have planned this user testing on (Friday) in the ISO Meeting Room, Level 4, Engineering Tower, Faculty of Engineering with provided 2 units Laptops on the table. We just allowed 2 users for each session to perform during this user testing. We were planned the particular steps: Welcome them and give some briefing on the system about, give them the consent form, User has performed the system, fill up the feedback form. In recognition of users involved in this user testing, we have prepared lunch in the room. Figure14. USER TESTING IN ACTION

8 REFLECTION Figure15. USER TESTING IN ACTION When we went through this user testing with 9 of users, we were measured from users feedback as belows result: During the course of the iterative design process creating Book Transaction System, the team learned a how the problem the system in started process until the ending process. The number of design revisions we ve made combined with the prototype testing performed allowed us to rapidly test and implement new features. Our team also initially highly underestimated just how much work good User Interfaces (UIs) and User Experience (UX) takes. There are many small things that continue to pop up that likely would have been easier to deal with in the low-fidelity prototyping stage. Each issue may be small, but when there are a lot of them, they tend to add up very quickly and do not create the greatest user experience. In the paper prototyping stage, the features we chose to prototype (Registration, Borrowing, Returning and Penalty). It is main point in the system towards user to apply it. CONCLUSION Users were very acceptable to the idea of Book Transaction System especially those in our targeted user profiles. Implementing Book Transaction System through the iterative process. Allowed for us to implement features Faster, better respond to user feedback, and overall react quicker changes needed then would have been possible to accomplish using the waterfall design process. Figure16. MEASUREMENT FROM USERS FEEDBACK Overall the user testing showed that most of our design worked well and can be introduced to the University of Malaya Library. ACKNOWLEDGMENT We thank to Dr. Nor Anita Fairos Ismail, Lecturer for Human Computer Interaction, University of Technology Malaysia to guidance us on heuristic evaluation. We also thank to Mr. Mahbob Yusof, Deputy Chief Librarian of University of Malaya Library for allowed us did the several research and interview among the library students to made this Book Transaction System successes.