| Lesson 2 | Web Interaction Model |
| Objective | Review the Web Interaction model. |
Review the Web Interaction Model
The Web Interaction Model provides you with one way of understanding how Web processes work together.
This model accounts not only for hardware, software, and networks, but also for the user's experience.
The Web Interaction Model is based on the idea of a series of layers operating dynamically, with each layer responding to input and data from the other layers.
This model accounts not only for hardware, software, and networks, but also for the user's experience.
The Web Interaction Model is based on the idea of a series of layers operating dynamically, with each layer responding to input and data from the other layers.
Web Interaction Model:
Signs and Metaphors - Information Architecture
- Signs are visual markings or sounds that present information and metaphors cue users about the functionality of the site through the use of icons or images. Together, Signs and Metaphors create the look and feel of the site.
- Information Architecture organizes Signs and Metaphors into a cohesive structure. In addition, it lays down the path for navigating through the site.
- Software comprises underlying components (applications) that enable the display of Signs and Metaphors. In addition, software creates, stores, and manages all resources available over the Web.
- A network is a series of computers that communicate with each other. Common protocols used on the Internet are TCP, IP, HTTP, FTP, and SMTP (the Internet email protocol).
- Hardware includes the user's computer equipment, also
1) Web servers, 2) database servers, 3) mail servers, 4) domain name servers, and 5) firewall servers.
On the network side, hardware includes fiber optic cables, routers, hubs, and other network equipment.
Web Interaction Model
Programmers are confronted by a series of challenges when they design interactive Web programs. Web interactions take place via Web browsers. With browsers, consumers can whimsically navigate among the various stages of a dialog and can thus confuse the most sophisticated corporate Web sites. In turn, Web services can fault in frustrating and inexplicable ways.
The quickening transition from Web scripts to Web services lends these problems immediacy. To address this programming problem, we develop a foundational model of Web interactions and use it to formally describe two classes of errors. The model suggests techniques for detecting both classes of errors. For one class we present an incrementally checked record type system, which effectively eliminates these errors. For the other class, we introduce a dynamic safety check, which catches the mistakes relative to simple annotations of the programmers.
Limitations of the Web Interaction Model
You should keep in mind that there is overlap between the layers of the model. Each layer represents a discrete element of the Web.
In some cases, elements support the layers above them, but in all cases, each layer is affected by the others. This model makes distinctions among the elements of the Web, so you can consider your options for each element independently when you are clarifying your Web site needs. Your organization's business goals should drive the choices made at each layer.
In some cases, elements support the layers above them, but in all cases, each layer is affected by the others. This model makes distinctions among the elements of the Web, so you can consider your options for each element independently when you are clarifying your Web site needs. Your organization's business goals should drive the choices made at each layer.
Examine Multiple Elements
When planning a Web site, examine multiple elements. Consult all team members for input in their area of expertise.
End user satisfaction is affected by every component and layer of your Web site. The next lesson provides a review of the Web Development Process Model.
End user satisfaction is affected by every component and layer of your Web site. The next lesson provides a review of the Web Development Process Model.
What Is Interaction Design?
Mobile interaction design can be a somewhat confusing term for those just beginning their careers in interface design.
Often used interchangeably, interaction design and interface design are completely different concepts, and it is important not to mistake one for the other. In fact, the two ideas can appear to be so similar that a casual reading of this text could make it seem as if we are confusing the two as well. They have separate definitions, however, and although they do work together to achieve the same goal, they are actually quite different.
Interface design involves the technical pieces and intricate design language created and mandated by a platform developer for use in a specific operating system. On a popular mobile system such as Android, this includes standards such as using Roboto as a system font or applying the Holo Light or Dark visual theme styles that specify suggested color, font size, line height, or other properties of phone interfaces. Apple has its own carefully defined set of interface design standards.
Often used interchangeably, interaction design and interface design are completely different concepts, and it is important not to mistake one for the other. In fact, the two ideas can appear to be so similar that a casual reading of this text could make it seem as if we are confusing the two as well. They have separate definitions, however, and although they do work together to achieve the same goal, they are actually quite different.
Interface design involves the technical pieces and intricate design language created and mandated by a platform developer for use in a specific operating system. On a popular mobile system such as Android, this includes standards such as using Roboto as a system font or applying the Holo Light or Dark visual theme styles that specify suggested color, font size, line height, or other properties of phone interfaces. Apple has its own carefully defined set of interface design standards.
