Questões da Prova CESPE - 2017 - TRE-PE - Analista  Judiciário - Análise de Sistemas

Foram encontradas 60 questões

Resolva questões gratuitamente!

Junte-se a mais de 4 milhões de concurseiros!

Q792296 Inglês
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
Alternativas
Q792295 Inglês
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).
The author of text 3A7AAA concludes that
Alternativas
Q792293 Inglês
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).
About the definition for software architecture, text 3A7AAA shows that
Alternativas
Q792292 Programação
Assinale a opção que indica a descrição correta de um array denominado empregados que contenha três objetos compostos pelo registro do primeiro e do último nome de um empregado em uma matriz J S O N. 
Alternativas
Q792291 Banco de Dados
Tabela 3A6AAA
dados da tabela:
ID; nome; idtipo; preco
25; creme; 3; 11,50
31; arroz; 4; 12,50
34; leite; 1; 14,00
42; sabão; 5; 11,00
46; carne; 1; 12,75
48; shampoo; 5; 12,30
58; azeite; 1; 13,25
Assinale a opção que apresenta o comando S Q L correto para se incluir um novo campo idcategoria do tipo INT nos dados da tabela 3A6AAA, denominada tbproduto.
Alternativas
Respostas
1: C
2: D
3: A
4: D
5: B