According to Ventureline.com input controls are computer controls designed to provide reasonable assurance that transactions are properly authorized before processed by the computer, accurately converted to machine readable form and recorded in the computer, that data files and transactions are not lost, added, duplicated or improperly changed, and that incorrect transactions are rejected, corrected and, if necessary, resubmitted on a timely basis (www.ventureline.com). The use of input controls should never be overlooked. Input controls are a great way to deliver high quality implementation as a control, which will also deliver high quality output results. Each system respectively may have different needs for different input controls, but regardless of the specific purpose that is possible for any system the aspects that relate to input controls will affect both user and technical areas of the system. When users are interacting with a system they are concerned with the usability and accessibility if the system while designers are concerned with the validity and accuracy of the information being inputted. Input controls are a valuable tool, some input controls may implement certain test procedures in order to validate and verify entered information and depending on how the program is configured there may be either a recommendation presented to the user or an automatic process carried out to utilize the input controls. One type of input control is a validity check. Validity checks take place in order to verify that only certain formats or types of data can be entered into a system. These are commonly used in the design and implementation of relational databases (quickstarts.asp.net). In the case of a typical orders entry database for a business there will be unique IDs for each customer within the system, and every time a new customer is added into the system there will need to be a validity check to ensure that no IDs are duplicated. Also with a order database for a system there may be times where certain types of formats must be entered into specific fields, for example if there was a field for a date there would be a validity test to ensure that only an accurate date could be entered into the field in the correct format. Validity checks are an excellent tool to have they will ensure that all data entered is consistent across all fields and prevent possible errors that may make it difficult to run reports and analyze information. Another input control would be a reasonableness check. Reasonableness check identifies values that are questionable, but not necessarily wrong (Shelly and Rosenblatt, 2012). This will be used as a way of verifying specific values which, even though not incorrect in fact may present an unreasonable factor in terms of their use and there should therefore be a question raised in terms of if the values should be included or not. For example for a system dealing with employee payment amounts both $.05 and $5,000,000.00 are both valid dollar amounts over zero. However it is most likely that both of these entries could be errors due to their extreme values both low and high, the system should verify these values using a reasonableness check (Shelly and Rosenblatt, 2012). A sequence check is another example of an input control. A sequence check will be used as a form of input control in any specific circumstance where the input of information is based on the requirements for sequential numbers to be used and implemented. For example if a user must enter work orders in numerical sequence, then an out-of-sequence order number indicates an error, or if the user must enter transactions chronologically, then a transaction with an out-of-sequence date indicates an error (Shelly and Rosenblatt, 2012). A combination check is used when it is necessary to perform several multiple input controls to ensure that accurate and reasonable data is recorded at all times. There may be times when certain fields pass an individual input control measure but when combined with additional fields or information this would give rise to incorrect and invalid information and values being present within a system. For example, if an order input for 30 units of a particular item has an input discount rate applicable only for purchases of 100 or more units, then the combination is invalid either the input order quantity or the input discount rate is incorrect (Shelly and Rosenblatt, 2012). Each of these input controls could be linked to the user interface and this will provide the key method by which users will interact with the system. These input controls are usually in forms of controlled menus, tabs, and buttons when being looked at by a conventional user. User interfaces often have specific requirements to restrict access to certain sections of the user interface as well as certain system functions. This is done to ensure that the users only have the required levels of access to complete their designated tasks or responsibilities. With these measures in place the security of the system is enhanced because users would have less control over the system and would only be aloud to enter information into pre determined fields. This overall strengthens the integrity of the system. There can however be issues with restricting access in such a way, as there will be a considerable increase in the requirements that will be needed for validating and testing systems and each input control with the various accounts and restrictions which will be in place. There would also need to be a consideration of the relevant messages that should be displayed when users attempt to access areas or functionality to which they do not have access. Input controls are a very good tool to have when designing a system. Dependent upon the system that is being designed will dictate the type of input controls that are utilized in the system and dependent upon the system requirements that must be put in place.

References
INPUT CONTROLS Definition. (n.d.). Retrieved February 15, 2015, from https://www.ventureline.com/accounting-glossary/I/input-controls-definition/

ASP.NET Quickstart Tutorials. (2005, January 1). Retrieved February 15, 2015, from http://quickstarts.asp.net/QuickStartv20/(A(rPkzoZ1GtN_3dnl_uguWft3MCrjfN-h5QN-nPS0YIGb15KZGXk_mNEzhn0d7hc3hLLrfwjkYLlDNez9gMX35F1nmqDXsgUWr0))/aspnet/doc/validation/default.aspx

Shelly, G., & Rosenblatt, H. (2012). Systems Analysis and Design (9th ed.). Manson: Cengage Learning.