 |
1 | |
It is always possible to make a clear distinction between information and function within a WebApp. |
| | A) | true |
| | B) | false |
|
|
2 | |
There are two distinct types of functionality that should be addressed as part of functional design. They are: |
| | A) | user-level functionality and application level functionality |
| | B) | user-case derived functions and ad hoc functions |
| | C) | visible functions and invisible functions |
| | D) | architectural functions and component-based functions |
|
|
3 | |
Functionality associated with user interaction support provides the mechanisms by which a user carries out specific tasks. |
| | A) | true |
| | B) | false |
|
|
4 | |
Which of the following is not an application-level functionality: |
| | A) | Application interaction support |
| | B) | Application information support |
| | C) | Application task support |
| | D) | Application functional support |
|
|
5 | |
User level functions that are described at the use case level can be partitioned into components that have clearly defined roles and interfaces. |
| | A) | true |
| | B) | false |
|
|
6 | |
In designing the functional architecture, it is useful to have first developed an initial information architecture. |
| | A) | true |
| | B) | false |
|
|
7 | |
A UML component diagram is a reasonable way to represent the functional architecture for a WebApp. |
| | A) | true |
| | B) | false |
|
|
8 | |
In developing the functional architecture, the scenarios can be decomposed into the following functional categories: |
| | A) | Content aggregation, navigation, submission, and system support |
| | B) | Information selection, compilation, processing, and system interaction |
| | C) | Form entering, submission, processing, and page generation |
| | D) | Data analysis, linking, provision, and system maintenance |
|
|
9 | |
The functional architecture should be designed independently of any consideration or selection of technologies. |
| | A) | true |
| | B) | false |
|
|
10 | |
The MVC architecture decouples an application interface from navigation and from application behavior, and keeps interface, application and navigation separate, thereby simplifying implementation and enhancing reuse. The key elements of the architecture are |
| | A) | mechanism, verification and configuration |
| | B) | model, verify and complete |
| | C) | make, validate and compare |
| | D) | model, view and controller |
|
|
11 | |
WAE notation provides support for the following key notation: |
| | A) | analysis view, logical view, and component view |
| | B) | design view, construction view, deployment view |
| | C) | work view, analysis view, and efficiency view |
| | D) | work view, architecture view, environmental view |
|
|
12 | |
State modeling allows a design to examine which important aspect of a WebApp |
| | A) | logical aspect |
| | B) | behavioral aspect |
| | C) | component level aspect |
| | D) | architectural aspect |
|
|
13 | |
A state diagram incorporates |
| | A) | states, stimuli, and transitions |
| | B) | states, content and classes |
| | C) | states, observations, and results |
| | D) | states, boundaries, and collaborations |
|
2009 McGraw-Hill Higher Education