 |
1 | |
An WebApp designer should consider three key issues when performing information design: |
| | A) | content, composition and navigation |
| | B) | architecture, structure and content |
| | C) | relationships, collaboration and objects |
| | D) | classes, messages and collaboration |
|
|
2 | |
For large WebApps, the information design is best developed using a: |
| | A) | bottom-up approach |
| | B) | top-down approach |
|
|
3 | |
A reasonable definition of information architecture (IA) is: The structural design of an information space to facilitate task completion and intuitive access to content. |
| | A) | true |
| | B) | false |
|
|
4 | |
A good information architecture exhibits: |
| | A) | composition with multiple dynamic data |
| | B) | temporal relationships |
| | C) | separation of content and information |
| | D) | all of the above |
| | E) | none of the above |
|
|
5 | |
Assume that you’ve decided to open an on-line store that sells golf balls. You intend to offer the 6 different types of balls from each of 8 manufacturers. Your best choice for structuring the information space would be a: |
| | A) | linear structure |
| | B) | hierarchical structure |
| | C) | network structure |
| | D) | matrix structure |
|
|
6 | |
As a general rule the link “fan-out” shouldn’t exceed more than 4 for most Web pages. |
| | A) | true |
| | B) | false |
|
|
7 | |
A blueprint shows how the various content objects map into a specific information structure. |
| | A) | true |
| | B) | false |
|
|
8 | |
Which of the following statements is not true. A blueprint . . .: |
| | A) | allows you to visualize how a WebApp might fit together |
| | B) | focuses on the functionality supported by a WebApp |
| | C) | allows you to discuss what navigational paths will address given tasks |
| | D) | might show which content is static and which is dynamic |
|
|
9 | |
There are a number of different mechanisms for accessing information. These include: |
| | A) | WebApp mechanisms that allow a user to understand what navigation options are available at any given time |
| | B) | Interface mechanisms that provide the user with an indication of where he is and what he is currently seeing |
| | C) | Navigation mechanisms that allow users to travel within the information structure. |
| | D) | all of the above |
| | E) | none of the above |
|
|
10 | |
Constraining the scope of search in a WebApp: |
| | A) | will result in more effective access to all of the WebApp content |
| | B) | should be used where some of the content is not amenable to structured navigation. |
| | C) | is usually implemented in order to simplify the indexing process. |
| | D) | creates problems with integration with external search engines such as Google. |
|
|
11 | |
A wireframe model is equivalent to a prototype in representing and prioritizing various information and navigation elements. |
| | A) | true |
| | B) | false |
|
|
12 | |
The Dexter Hypertext Reference Model was intended as a design model to support effective information design of WebApps |
| | A) | true |
| | B) | false |
|
|
13 | |
The Relationship Management Methodology (RMM) is used primarily as a tool during |
| | A) | information design |
| | B) | navigation design |
| | C) | interface design |
| | D) | architectural design |
|
|
14 | |
The Relationship Management Methodology (RMM) is an early navigational design approach that encompasses the following set of activities: |
| | A) | relationship analysis, class management methods, and collaborative design |
| | B) | object analysis, class management methods, and collaborative design |
| | C) | feasibility analysis, entity-relationship (E-R) modeling, slice design, navigation design, and construction. |
| | D) | all of the above |
|
|
15 | |
In the Relationship Management Methodology (RMM), an information slice represents the information which: |
| | A) | will be stored as a single unit |
| | B) | should be presented together to the users |
| | C) | is derived directly from external sources |
| | D) | all of the above |
|
|
16 | |
WebML |
| | A) | is quite similar to XML |
| | B) | incorporates workflow modeling, presentation and content adaptation, personalization, and design patterns. |
| | C) | allows the depiction of the functional architecture as well as the information space |
| | D) | none of the above |
|
|
17 | |
The WebML data model captures the content, the relationships between these content items, and the functional processes for managing these content items: |
| | A) | true |
| | B) | false |
|
|
18 | |
Web Application Extensions for UML (WAE) is best suited to capturing the design of: |
| | A) | the database schemas used to store the WebApp content |
| | B) | the user interaction with a WebApp |
| | C) | the interaction between the client-side navigation and the server side functionality. |
| | D) | WebApp performance characteristics. |
|
2009 McGraw-Hill Higher Education