Please enable JavaScript.

Coggle requires JavaScript to display documents.

CHAPTER 4 SYSTEM DESIGN - Coggle Diagram

- - - - i. Understand the Business
        
        The interface designer must understand the underlying business functions and how the system supports individual, departmental, and enterprise goals.
        
        ii. Maximize Graphical Effectiveness
        
        Studies show that people learn better visually.
        
        The immense popularity of Apple Mac OS and Microsoft Windows is largely the result of their graphical user interfaces that are easy to learn and use.
        
        iii. Think Like a User
        
        A systems analyst should understand user experience, knowledge, and skill levels.
        
        To develop a user-centered interface, the designer must learn to think like a user and see the system through a user’s eyes.
        
        iv. Use Models and Prototypes
        
        From a user’s viewpoint, the interface is the most critical part of the system design because it is where he or she interacts with the system
        
        It is essential to construct models and prototypes for user approval.
        
        v. Focus on Usability
        
        The user interface should include all tasks, commands, and communications between users and the information system.
        
        Each screen option leads to another screen, with more options.
        
        The objective is to offer a reasonable number of choices that a user easily can comprehend.
        
        vi. Invite Feedback
        
        Even after the system is operational, it is important to monitor system usage and solicit user suggestions.
        
        You can determine if system features are being used as intended by observing and surveying users.
        
        vii. Document Everything
        
        You should document all screen designs for later use by programmers.
        
        If you are using a CASE tool or screen generator, number the screen designs and save them in a hierarchy similar to a menu tree.
- - - - -
        
        to ensure the quality, accuracy, and timeliness of input data
        
        Good input design requires attention to human factors as well as technology issues
        Data Entry Screens
        
        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
        5.Do not require users to type leading zeroes for numeric fields
        6.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
        8.Use a default value when a field value will be constant for successive records or throughout the data entry session
        9.Display a list of acceptable values for fields, and provide meaningful error messages
        10.Provide a way to leave the data entry screen at any time without entering the current record
        
        4.2.4 Data Capture vs Data Entry
        - Data entry - 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
        
        4.2.4 Input & Data Entry Method
        
        first decision is whether to use batch or online input methods
        
        each method has advantages and disadvantages
        
        systems analyst must consider the following factors
        
        a. Batch Input
        
        data entry is performed on a specified time schedule [ daily, weekly, monthly, or longer ]
        
        example: batch input occurs when a payroll department collects time cards at the end of the week and enters the data as a batch
        
        b. Online Input
        
        Many large companies use a combination of source data automation and a powerful communication network to manage global operations instantly.
        
        4.2.6 Input Mask & Validation Rules
        
        8 types of data validation rules:
        
        Sequence check
        
        Existence check
        
        Data type check
        
        Range check
        
        Reasonableness check
        
        Validity check
        
        Combination check
        
        Batch controls
- - - - a. Detail reports
        
        produces one or more lines of output for each record processed
        
        detail line - each line of output printed
        
        a detail report can be quite lengthy.
        example : a large auto parts business
        -if the firm stocks 3,000 parts, then the detail report would include 3,000 detail lines on approximately 50 printed pages.
        b. Exception reports
        
        displays only those records that meet a specific condition or conditions
        
        useful when the user wants information only on records that might require action, but does not need to know the details
        
        c. Summary reports
        
        Upper-level managers often want to see total figures and do not need supporting details
        -example : a sales manager might want to know total sales for each sales representative, but not want a detail report listing every sale made by them
      - 4.2.10 Design Report Principles
        
        must be attractive, professional, and easy to read.
        
        -example: a well-designed detail report should provide totals for numeric fields
        -to produce a well designed report, the analyst must consider design features such as report headers and footers, page headers and footers, column headings and alignment, column spacing, field order and grouping of detail lines
        
        Report headers and footers
        
        Every report should have a report header and a report footer.
        
        The report footer, which appears at the end of the report, can include grand totals for numeric fields and other end-of-report information.
        
        Column heading alignment
        Centering headings over maximum field widths, as shown in Example 3, is not ideal when many of the actual values are shorter than the maximum width.
        
        Column spacing
        
        A crowded report is hard to read, and large gaps between columns make it difficult for the eye to follow a line.
        
        Some report designers use landscape orientation when working with a large number of columns; others prefer to break the information into more than one report.
        
        Field order
        
        Fields should be displayed and grouped in a logical order.
        
        For example, the report shown in Figure shows the detail lines printed in alphabetical order within store number, so the store number is in the left column, followed by the employee name.
        
        Grouping detail lines
        
        Often, it is meaningful to arrange detail lines in groups, based on a control field.
        
        For example, using the department number as a control field, individual employees can be grouped by department.
        
        Repeating fields
        Report design is an art, not a science.
        User involvement is essential, but users often don’t know what they want without seeing
        
        Consistent design
        
        Abbreviations used in reports also should be consistent.
        
        For example, when indicating a numeric value, it is confusing for one report to use #, another NO, and a third NUM.