Flexible Input Controls - Assignment Example

Input Controls Input Controls Functions of Input Controls Input controls are tools commonly used in graphical user interfaces toconstrain the user-fed values in order to fulfill the validation and data integrity rules that pertain to a given database-driven application. According to Shelly & Rosenblatt (2012), flexible input controls are capable of allowing end-users to feed invalid data while enabling them to take note of uncertain values with the hope that the uncertain and invalid data values are bound for correction at some later time. Examples of Input Controls i. Text Fields Text fields are graphical control elements aimed at enabling users to feed text information that can be utilized by an application. Often times, the text fields allow single-line texts for systems requiring single lines of inputs, and multi-line text fields in case of systems requiring more than a single line of input. ii. Buttons Buttons are graphical elements that provide end-users of a system with a simplified approach to initiate events like confirmation of an action or performing a more customized query search. iii. Drop Down Lists Drop down lists are graphic control elements that allow end-users to select an individual value from a given list. When inactive, this type of list will display an individual value. If activated, the list drops down a set of values. iv. Label Labels are graphic control elements capable of providing descriptive and suggestive texts about the data values that end users are supposed to supply in the respective parts of a user interface. Data Integrity Errors Human mistakes plus naivety forms part of the reasons behind data integrity errors that arise in applications (Shneiderman & Plaisant, 2010). Often times, the human mistakes are manifest during data collection. It is in this light that user interfaces are mostly equipped with the input controls in order to reduce data entry errors. Here to discuss are ways in which the absence of each of the aforementioned input controls can lead to data integrity errors. i. Text Fields Use of text fields is an input approach that captures details that are unique to end-users like mail address and credit card numbers. Any user who notices the absence of a text field in a system that requires more personalized information like credit card numbers and mail addresses is likely to get frustrated or spend a significant time trying to figure out any better way through which he/she could supply the personalized information. In either case, accuracy will be unlikely thus increasing the chances of errors in the integrity of the data supporting the application in question. ii. Buttons Absence of a CANCEL button on a user interface can limit the ability of the end-users to recover from mistakes that they could make while feeding information. Consequently, the back end database system can end up storing inaccurate data. iii. Drop Down Lists Values featured in drop down lists are in most cases defined as per the business rules that govern the database integrity checks. As such, their absence limits an applications ability to permit values within the business domains thus increasing the chances of inaccuracy in the data. iv. Labels Labels are often followed by controls that allow users to enter data. The absence of levels can make end-users remain in the dark since they will not know what to feed where. If this state is coupled with lack of codes that can perform validation checks, end-users can end up feeding information that does not much with the respective table fields associated with the table fields supporting the application. Restricting User Interfaces i. Advantages One of the advantages of restricting user interfaces is that it provides a foundation for attaining an optimum performance within a system. With a restriction in the user interface, an application’s response time can remain rapid while minimizing delays or waiting (Darcey & Conder, 2012). Further, optimization can be attained by presenting end-users only with content that they need at a particular instance. For instance, a bank system could restrict user interfaces in such a way that a person logged in as a teller is presented with a form that bears fields such as Client ID_NO, account number, name, email address and branch name to suit creation of new bank accounts, then present an individual logged in as an account owner with a form that features a single text field for feeding an account number to suit balance enquiries. Another advantage of restricting user interfaces is that it opens an avenue for undertaking online transactions. Basically, such transactions will often require passwords alongside details like credit card information. In restricting the user interfaces exposed to end-users using given business criteria, the providers of the involved goods and services can raise revenue whilst ensuring that the provided services are enjoyed only by the individuals who have meet the predefined business conditions. ii. Disadvantages User interfaces are intended for use by the human race where assumptions are inevitable. In this regard, uncontrolled restrictions on a user interface could send end-users the message that a greater perspective of a system is not meant for their use. Consequently, they might end up disregarding the need to learn the operations that are crucial for their day-to-day interaction with an application. If cultivated for long, this habit can lead to reduced interest in an application thus increasing the chances of data integrity errors. Efforts to restrict user interfaces will in most cases result into elaborated development time and delayed delivery for applications. In their bid to restrict user interfaces, application developers never keep user-friendliness at bay. Unfortunately, increasing the user-friendliness that pertains to an application’s interfaces often implies additional challenges for UI designers plus programmers given that the move necessitates inclusion of extra functionalities within the application. In addition, the present development scenarios still deem testing of GUI prototypes with the actual end-users of an application as the only sure test for user-friendliness. There is no doubt that doing this for different user groups that an application under development is targeting can increase the development time and probably lead to delayed deliveries. User Interface Design for a Web-Based Hotel Reservation System Fig 1.1 showing a user interface for hotel reservation designed using DIA tool References Darcey, L., & Conder, S. (2012). Sams teach yourself Android application development in 24 hours. Indianapolis, Ind: Sams. Shelly, G. B., & Rosenblatt, H. J. (2012). Systems analysis and design. Boston: Course Technology Cengage Learning. Shneiderman, B., & Plaisant, C. (2010). Designing the user interface: Strategies for effective human-computer interaction. Boston: Addison-Wesley. Read More