A Web Service Booking System - Research Proposal Example

This evaluation is conducted to understand how well the product has met its objectives. It also helps determine the effectiveness of the product when launched to the customers. This task involves creating a tutorial CD that will be used to create a web service booking system. For applying the target audience who are not aware of the basics and insist on understanding the booking system through web-enabled devices, we have included and explained the concept of HTML, PHP and MySQL. It is an initiative to assist intermediate and advanced users in understanding the booking system that uses web services for web-enabled devices for reservation by setting PHP, Mysql, and content management guidelines.

The product has an important context as it enables the consumers to use the online reservation system, reducing time and money. The product will also embellish students and others to jive into their passion and own their content in a public domain. It will portray a great experience of learning, especially to the students. It will also be used in the software industry and businesses and companies that would like to create their own websites.The tutorial's main feature is that it provides the ease of learning the application with the CD-Rom, containing all the information under one shed.

The tutorial can be carried anywhere, anytime thus adding to the mobility of understanding the process. While the institutes provide all this information or data, it is always better to start courses at your end and practice the same. The investment of time and money can be reaped with the simple use of the CD. The tutorial has two parts; one is the content to present, i.e. the learning material for the users, which has to be amicable to quality and cater to the consumer's needs. Second, is the fabric presentation so that it is easy to understand and meet the standards developed for such a kind of work?

We will now discuss some theories about the completeness and correctness of such work, and these requirements must be met to get the most out of this tutorial.

In case customer calls up on a toll free number, it might be possible that the customer service people might not attend to him or her. Often the phone might be engaged or the customer might be put on hold. This would not help in solving any urgent query of the customer. Further, toll free numbers would mean extra cost to the company as these numbers are tariff free for the customers. Neilsen Heuristics The usability problem is defined as a issue that is found in the software product. The following lists of heuristics can assisting in improving the system usability, additionally can guide the users with useful interaction design.

These are close to ten general principles that are used in the user interface design. These are known as "heuristics". These principles are more like the nature of rules of thumb, in comparison to the usability guideline that can be flexible at all times. Visibility of system status Under this, the users should be informed at all times, by using the methodology of giving adequate and appropriate feedback within a stipulated timeframe. Match between system and the real world The system encourages builders or techies to use consumer’s language.

This may be done by using phrases or words or concepts that the consumer can relate to rather than being system oriented, which may deflate the interest in the tutorial. Following the real-world conventions can make information realty appealing and logical. User control and freedom It has been seen that users choose functions or systems by mistake. In such as case, if processes that clearly marks "emergency exit" can help the users in exiting such as scenario with ease than getting into extended dialogue and infusing frustration.

Support undo and redo. Consistency and standards Users should also not get confused by the connotation of different words, like situations, or actions. They should be clearly given advice so that they are able to follow the guidelines without being hasty or perplexed. Follow platform conventions. Error prevention The idea of creating platform that can help in resolving the issue even before it arises is a perfect strategy that should be adopted. It should be either done by eliminating error-prone conditions or check for them.

They should also give users confirmation option before beginning to start the process. Recognition rather than recall Also, minimizing the user's memory should be another plan adopted; this can be expedited by making objects, actions, and options visible. The user should not be strained to remember information from dialogue to another. Instructions should be retrievable and visible whenever the user is in need. Flexibility and efficiency of use Accelerators that are not seen by the novice user can accelerate the interaction for expert users, the system should be defined in such a form that it should be able to cater to the experienced and inexperienced users.

Allow users to tailor frequent actions. Aesthetic and minimalist design Information that would be used rarely or may be completely irrelevant should be be included. The relative visibility of the relevant dialogue gets diminishes if irrelevant dialogue covers the entire ground, thus defaming the objective completely. Help users recognize, diagnose, and recover from errors Messages such as the one used for errors should be exhibited in plain language without using any codes. Being precise and crisp will enable the users to identify more with the problem.

This will also constructively enable them to either suggest a solution or look for external reading material. Help and documentation It is thought to be better that all the systems should have documentation and help guide that can further enhance the usability. The ease to search this information should be the prime objective of providing the documentation. Shneiderman’s eight rules There are eight stages that make a good interface design, which should be kept in mind before developing the prototyping design.