Input, Output, and User Interface Design
Input Design
Management and users make important decisions based on system outputs. These outputs are produced from data that is either input or retrieved from databases. And any data in the databases must have been first input.Today most inputs are designed by rapidly constructing prototypes. These prototypes may be simple computer-generated mock-ups, or they may be generated from prototype database structures such as those developed for Microsoft Access. These prototypes are rarely fully functional. They won't contain security features, data editing, or data updates that will be necessary in the final version of a system. Furthermore, in the interest of productivity, they may not include every button or control feature that would have to be included in a production system.
During requirements analysis, inputs were modeled as data flows that consist of data attributes. Even in the most thorough of requirements analysis, we will miss requirements. Input design may introduce new attributes or fields to the system. This is especially true if output design introduced new attributes to the outputs—the inputs must always be sufficient to produce the outputs. Inputs can be classified according to two characteristics: (1) how the data is initially captured, entered, and processed and (2) the method and technology used to capture and enter the data.
Output Design
Outputs are the most visible component of a working information system. they are often the basis for the users' and management's final assessment of the system's value. During requirements analysis, we defined logical output requirements. During decision analysis, we are considered different physical implementation alternatives.
Most outputs are designed by rapidly constructing prototypes. These prototypes may be simple computer-generated mock-ups with dummy data, or they may be generated from prototype databases such as Microsoft Access, which can be rapidly constructed and populated with test data. These prototypes are rarely fully functional. They won't contain security features or optimized data access that will be necessary in the final version of a system. Furthermore, in the interest of productivity, we may not include every button or control feature that would have to be included in a production system.
During requirements analysis, outputs were modeled as data flows that consist of data attributes. Even in the most thorough of requirements analysis, we will miss requirements. Output design may introduce new attributes or fields to the system.Outputs can be classified according to two characteristics: (1) their distribution and audience and (2) their implementation method.
One way to classify outputs is according to their distribution inside or outside the organization and the people who read and use them.
Internal outputs are intended for the system owners and system users within an organization. They only rarely find their way outside the
organization. Internal outputs support either day-to-day business operations or management monitoring and decision making.
The opposite of internal outputs is external outputs. External outputs leave the organization. They are intended for customers, suppliers,
partners, and regulatory agencies. They usually conclude or report on business transactions. Examples of external outputs are invoices,
account statements, paychecks, course schedules, airline tickets, boarding passes, travel itineraries, telephone bills, purchase orders, and mailing labels.
Interface Design
we integrate output and input design into an overall user interface that establishes the dialogue between users and computer. The dialogue determines everything, from starting the system or logging into the system, to setting options and preferences, to getting help. And the presentation of the outputs and inputs is also part of the interface. We need to examine the screen-to-screen transitions that can occur. In client/server applications (e.g. network-based Windows) and Web applications (e.g., Internet- or intranet-based browsers), the user has many alternative paths through menus, hyperlinks, dialogues, and the like. This makes for very accommodating and friendly user interfaces, but it greatly complicates design and programming.
Today most user interfaces are designed by rapidly constructing prototypes. These prototypes are generated using rapid application development environments such as Microsoft's Visual Studio. These prototypes are rarely fully functional, but they do contain enough functionality to demonstrate the interface. For example, a help system prototype may be functional to the extent that it calls up a few sample screens to demonstrate levels of assistance. Or a security system might have just enough functionality to demonstrate representative log-in errors even though it is not actually authenticating users. When we get to the construction phase of the life cycle, programmers and analysts will complete the functionality
User Interface Technology
Most of today's user interfaces are graphical. The basic structure of the graphical user interface (or GUI) is provided within either the computer operating system or the Internet browser of choice. In client/server information systems, the user interface client is implemented to execute within the PC operating system. In Internet and intranet information systems, the user interface is implemented to execute within the PC's Web browser.
