1

Based on text CB1A3-II, judge the following items.

  1. The expression “red tape” (l.2) means politically-motivated and inconsistent official procedures.
  2. The basic meaning conveyed by “to enhance” (l.2) and to leverage (l.10) can also be found in to better.
  3. To be entitled (l.9) is synonymous with to be eligible for.
  4. The word “overall” (l.3) means in general terms in the text.

 

Decide which alternative below is correct.

2

It can be said from text 8A5AAA that cryptography and technology have
3

Choose the option that presents the statement that best conveys the central idea of text 8A5BBB.
4
In terms of comprehension of the text above, decide which of the statements below is correct.
5

In text 6A6AAA, the word “timely" (l.11) is used to convey that the Arizona Judicial Department's ITD provides information and solutions

6

In text 8A5BBB, the word “often” (R.27) can be correctly replaced by
7
In text CB1A3-I, the passage
8

Text 3A7AAA

Software architecture is a complex topic. Due to its

complexity, our profession has produced a variety of definitions,

each more or less useful depending on your point of view. Here is

a definition from my first book, Journey of the Software

Professional: "A system architecture defines the basic "structure"

of the system (e.g., the high level modules comprising the major

functions of the system, the management and distribution of data,

the kind and style of its user interface, what platform(s) will it run

on and so forth)".

This definition is pretty consistent with many others.

However, it lacks some important elements, such as specific

technology choices and the required capabilities of the desired

system. A colleague of mine, Myron Ahn, created the following

definition of software architecture. It is a bit more expansive and

covers a bit more ground than my original: "Software architecture

is the sum of the nontrivial modules, processes, and data of the

system, their structure and exact relationships to each other, how

they can be and are expected to be extended and modified, and on

which technologies they depend, from which one can deduce the

exact capabilities and flexibilities of the system, and from which

one can form a plan for the implementation or modification of the

system".

We could extend these definitions from the technical point

of view, but this wouldn't provide a lot of value. More than any

other aspect of the system, architecture deals with the "big picture".

The real key to understanding it is to adopt this big picture.

Moreover, while these definitions are useful, they are far too

simplistic to take into account the full set of forces that shape, and

are shaped by, an architecture. In truth, I doubt that any single

definition of software architecture will ever capture all of what we

believe to be important.

Luke Hohmann. Defining software architecture. In: Beyond

software architecture: creating and sustaining winning

solutions. Boston: Addison-Wesley, 2003, p. 1-2 (adapted)

In the first line of text 3A7AAA, the expression “Due to" could

be correctly replaced by

9

In text 8A5AAA, the word “unless” (R.20) conveys the idea of
10

Without altering the meaning of text 6A6BBB, the expression “covert signals" (l.3) could be replaced by