Please enable JavaScript.

Coggle requires JavaScript to display documents.

CHAPTER 4 SYSTEM DESIGN - Coggle Diagram

- - - - Restrict user access to screen locations where data is entered
      - Provide a descriptive caption for every field, and show the user where to enter the data and the required or maximum field size
      - Display a sample format if a user must enter values in a field in a specific format - separator
      - Require an ending keystroke for every field
      - Do not require users to type leading zeroes for numeric fields
      - Do not require users to type trailing zeroes for numbers that include decimals
      - Display default values so operators can press the ENTER key to accept the suggested value
      - Use a default value when a field value will be constant for successive records or throughout the data entry session
      - Display a list of acceptable values for fields, and provide meaningful error messages
      - Provide a way to leave the data entry screen at any time without entering the current record
      - Provide users with an opportunity to confirm the accuracy of input data before entering it
      - Provide a means for users to move among fields on the form
      - Design the screen form layout to match the layout of the source document
      - Allow users to add, change, delete, and view records
      - Provide a method to allow users to search for specific information
  - - - service in which data is captured via tick or check boxes and other items where areas are filled in with simple lines or shapes in order to get the right answer.
      - usually multiple choice answers / yes or no questions
      - the ability to extract data from particular text boxes
        in order to gather the most and least popular responses
    - - manually entered text, copying exactly what the person who filled out the feedback form has written.
      - not possible for computers to completely automate handwriting and this can be a somewhat more costly procedure
  - - - data entry is performed on a specified time schedule [ daily, weekly, monthly, or longer ]
    - - popopular online input method = source data automation
      - Source data automation is fast and accurate, and minimizes human involvement in the translation process.
      - Advantages:
        
        immediate validation
        
        availability of data
      - batch input - used in specific situations
  - - - 1)Sequence check
      - 2)Existence check
      - 3)Data type check
      - 4)Range check
      - 5)Reasonableness check
      - 6)Validity check
      - 7)Combination check
      - 8)Batch controls
  - - - Email
      - Blogs
      - Instant messaging
  - - - produces one or more lines of output for each record processed
      - detail line - each line of output printed
      - one detail line prints for each employee
      - all fields in the record do not have to be printed
      - figure shows a simple detail report of employee hours for a chain of retail stores
    - - useful when the user wants information only on records that might require action, but does not need to know the details
      - displays only those records that meet a specific condition or conditions
    - - Upper-level managers often want to see total figures and do not need supporting details
      - reports used by individuals at higher levels in the organization include less detail than reports used by lower-level employees
  - - - The report footer, which appears at the end of the report, can include grand totals for numeric fields and other end-of-report information.
      - appears at the beginning of the report, identifies the report, and contains the report title, date, and other necessary information.
    - - appears at the top of the page and includes the column headings that identify the data.
      - short but descriptive
      - used to display the report title and the page number
    - - stretch across the report, with uniform spacing and suitable margins at top, bottom, right, and left.
    - - displayed and grouped in a logical order.
    - - can print a group header above the first detail line and a group footer after the last detail line in a group
      - can have the report calculate and display totals, averages, record counts, and other data for any group or subgroup
    - - User involvement is essential, but users often don’t know what they want without seeing samples.
    - - reports should be uniform and consistent.
      - A system produces multiple reports, each report should share common design elements.
      - Abbreviations used in reports also should be consistent.
  - - - Output security protects privacy rights and shields the organization’s proprietary data from theft or unauthorized access.
      - All sensitive reports should be stored in secure areas.
      - The IT department is responsible for output control and security measures
      - USB, FireWire, and PCMCIA, as well as wireless interfaces such as Wi-Fi and Bluetooth.
    - - focus on input control during every phase of input design, starting with source documents that promote data accuracy and quality.
      - When a batch input method is used, the computer can produce an input log file that identifies and documents the data entered
      - necessary measures to ensure that input data is correct, complete, and secure.
      - Data security policies and procedures protect data from loss or damage, which is a vital goal in every organization.
      - Sensitive data can be encrypted, or coded, in a process called encryption, so only users with decoding software can read it.
- - - - Often, the user interface mainly consisted of process-control screens that allowed the user to send commands to the system
      - As information management evolved from centralized data processing to dynamic, enterprise-wide systems, the primary focus also shifted — from the IT department to the users themselves
      - User-centered system
    - - (GUI) a huge improvement, because it used icons, graphical objects, and pointing devices.
      - designers strive to translate user behavior, needs, and desires into an interface that users don’t really notice.
      - started in the 1980s with users typing complex commands in green text on a black screen.
      - Main objective is to create a user-friendly design that is easy to learn and use
      - ) describes the relationship between computers and people who use them to perform their jobs
      - the interface will be based on the perspective of a user rather than a computer engineer, programmer, or systems analyst.
    - - Understand the Business
      - Maximize Graphical Effectiveness
      - Think Like a User
      - Use Models and Prototypes
      - Focus on Usability
      - Invite Feedback
      - Document Everything
  - - - Clearly label all controls, buttons, and icons
      - Select only those images that users can understand easily, and provide on-screen instructions that are logical, concise, and clear
      - Show all commands in a list of menu items
      - Make it easy to navigate
    - - Organize tasks, commands, and functions in groups that resemble actual business operations
      - Create alphabetical menu lists
      - Provide shortcuts so experienced users can avoid multiple menu levels
      - Use default values if the majority of values in a field are the same
    - - Ensure that Help is always available
      - Provide user-selected Help and context-sensitive Help
    - - Create input masks
      - Display event-driven messages and reminders
      - Establish a list of predefined values that users can click to select
      - Build in rules that enforce data integrity
    - - Facilitate the system design objectives, rather than calling attention to the interface
      - Create a design that is easy to learn and remember
      - Design the interface to improve user efficiency and productivity
      - Write commands, actions, and system responses that are consistent and predictable
    - - Use appropriate colors to highlight different areas of the screen
      - Use special effects sparingly
      - Use hyperlinks that allow users to jump to related topics
      - Group related objects and information
    - - Remember that users are accustomed to a pattern of red=stop, yellow=caution, and green=go
      - Provide a keystroke alternative for each menu command
      - Use familiar commands if possible
      - Provide a Windows look and feel in your interface design if users are familiar with Windows-based applications
    - - Display messages at a logical place on the screen, and be consistent
      - Alert users to lengthy processing times or delay.
      - Allow messages to remain on the screen long enough for users to read them.
      - Let the user know whether the task or operation was successful or not.
      - Provide a text explanation if you use an icon or image on a control button.
      - Use messages that are specific, understandable, and professional
    - - List box – scroll bar
      - Drop-down list box
      - Option button, or radio button
      - Check box
      - Calendar control
      - Switchboard
  - - - Menu bar
      - Toolbar
      - Command button
      - Dialog box
      - Text box
      - Toggle button