The Difference between the Summary Report and Exception Report - Math Problem Example

System Analysis Name Institution Tutor Date 1. What is the difference between the summary report and exception report? Summary report is an internal type of output that categorizes information meant for managers. It does not contain a lot of details and it is mainly adopts graphical format of representation using charts. On the other hand an exception report is an internal type of output that specifically filters data to exceptions of reports to some specified standard or condition. 2. What are some examples of external reports? Invoices Bills 3. What are some examples of pictorial charts? Includes a painting, a sculpture, a drawing (a map, diagram, plan, or chart). 4. Why should graphic output used? Graphic output is the use of a chart or a graph to convey or pass across information. Graphic output is used owing to the fact that a picture can convey more meaning as compared to words. The graphs are able to assist the users of the system to grasp data and trends relationships that are not easily decipherable in number columns. 5. What is the relationship between source documents and data entry? A source document is a document that contains the data that has to be entered into the system database. Data entry is the processing of transferring the information from the source document into the database system. 6. What is the difference between OMR and OCR? Optical Mark Recognition (OMR) is the type of technology that detects presence or absence of a mark but not necessarily its shape. Optical Character Recognition is the kind of technology that enable imaging and scanning systems the ability to turn images of characters that are machine-printed into characters that are machine readable. OCR is less accurate as compared to OMR. OMR is the most accurate and fastest. 7. For biometric input, what and how is data entered and processed into information systems? Devices for biometrics consists of: a software that converts information that is scanned into digital form and goes ahead to compare match point, a device for scanning or a reader, and a database required for storage of biometric data for purpose of comparison. Biometric data is normally encrypted when gathered in an effort to prevent theft. Biometrics verification works on the back end. For conversion of the biometric input, by use of a software application; specific points of data are identified as match points. The match points when they reach the database they are subsequently processed by use of an algorithm which translates the information into value that is numeric. The value in the database is compared with the biometric input entered by the end user into a scanner and authentication into the system is either denied or approved. 8. Under what circumstances should we choose to use radio buttons or check boxes? Radio buttons and check buttons are elements of selection. Check buttons are commonly used when presented with the choice to make many options as desirable at a time from a number of options that is limited. There may be only one check box and you can select no option or as many as possible. Radio option is normal used in choosing a single option at a time from a number of options that are limited. Radio buttons are arranged in groups putting at least two radio buttons in the same group. If the user fails to select any option a separate no option a radio button labeled ‘no option’ should be created to include this kind of option. 9. What are the similarities of a drop-down list and combo box? Combo box comes from a drop-down list control. Similar to the drop-down control, if the user picks or selects an item from the drop-down list found in the combo control, the data item will appear in the prompt area of control. User interface design 10. Who are the expert users? Why are they called experts? Expert users are people who are able to use the interface with a lot of ease. They are called experts since they possess a vast of experience. 11. Why can some user interfaces cause users to feel confused, panicky, or frustrated? User interfaces cause users to feel confused, panicky, or frustrated because when they do not get the desired results or when the result are far from what was anticipated. 12. How should the interfaces handle errors? Interfaces handle errors by returning to the initial source of the direction. Crash or freeze will not impede scripting interface. 13. Explain paging and scrolling? Scrolling is the sliding of text, video or images across a display or monitor. Paging encourages viewing of a page; through it a second version of the website is created constituting individual screens. 14. What are the four common conversion strategies? Parallel: the old system is used with the new system together. Pilot: Part of the organization is converted to the new system without causing disturbance to the rest of the organization. Abrupt cut-over/Cold turkey: The strategy involves turning off the old system and turning on to the new system at the end of one business day. Phase-in: this involves or entails the organization being subjected to some type of ‘rolling’ conversion where by one subsystem is changed one by one to the new system until the who organization is upgraded. 15. What are some potential problems of using abrupt cut-over as a conversion strategy? This type of conversion is very risky since so much data can be lost if the new system fail to take off. There is trouble if the introduced new system does not work. It require more preparation to install the new system. 16. What are some potential problems of using parallel conversation as a conversation strategy? In this kind of conversion there is extra burden to the workers who have to cope with operating two kinds of systems at the same time. The procedure is tedious and requires a lot more concentration which takes toll of the workers’ productivity. Double reports and double data entry, makes this kind of conversion expensive or costly and at the same time labor intensive (Galitz, 2007). 17. What is the difference between alpha testing and beta testing? Alpha testing is the kind of testing done after code is majorly complete or has most of functionality and before the user gets involved. In some circumstances a part group of users are engaged. In most situations this testing is carried out in-house or using testing firms from outside in close liaise with the department of software engineering. Alpha testing is the testing of acceptance using a customer in the new product development environment. Beta testing is the kind of testing performed after a product is code complete. Betas are usually widely spread out and even in some circumstance distributed to the entire public in the anticipation of them to buy the final product when it is launched. Beta is the testing for acceptance using multiple customers in the customer environment. Jakob Nielsen criteria Visibility of the system status It is important for the system to keep users abreast of what is going on by employing appropriate feedback system within the shortest time possible. In accordance with Jakob Nielsen requirements the British Airways web page for managing ones booking; The website is good example of this policy. Potential customers can book for flights online. The homepage should be attractive enough to excite the interest of the customers and consequently retain them. Home pages are treated as front pages of newspapers and magazines. Match between system and the real world The language used must be familiar to the users and avoid system oriented terminologies. It should be logical and natural. A good example of this is found at Emirates Airline Web page. The website offers such simple instruction without technical gimmick. User control and freedom The users should be given the liberty to leave unwanted state when they choose system functions by mistake. Extended dialogue should be avoided and supports redo and undo. Barclays Bank home page is good because it gives this freedom and control to the user. Consistency and standards Ambiguity of words, actions and situations should be avoided and platform convections followed. The use of the words Icon Keys on the Hilton website page can be quite confusing to novice. Error prevention Error messages may be good, but in the first instance errors should be prevented from occurring. Users are to be represented with a confirmation option prior to committing to a certain action. Many systems have accomplished this for instance the Boeing website. It has achieved this quality. Recognition rather than recall The user should be compelled to remember information from one part of the dialogue to another. Instructions that are to be used should easily retrievable or visible. The Jakon Nielson webpage on Feature Richness and User Engagement. < http://www.useit.com/alertbox/features.html>. The website embraces this policy since it provides links that quicken the work of the user. The Tesco web page: requires remembrance of passwords, club-card number and postcard which can be tedious. Flexibility and efficiency of use The system or screen should allow users to tailor frequent actions. The web page of British Airways for flight management is a good example of this case. Aesthetic and minimalist design Irrelevant information should be included in the dialogues. If rarely used information is included it leads to reduction of visibility. The web page of Sidney Hilton Hotel contains so many features that may not be relevant to what the user is looking for. Help users recognize, diagnose, and recover from errors Messages concerning errors should be presented in plain and simple language. The Hilton Hotel website is god and easy to navigate from errors. Help and documentation A system should provide documentation and help, and give concrete steps to be carried out and should be precise. Excel tutorial web page provides a good example. Read More