Questões de Concurso
Comentadas para analista de tecnologia da informação - desenvolvimento de sistemas
Foram encontradas 1.235 questões
Resolva questões gratuitamente!
Junte-se a mais de 4 milhões de concurseiros!
( ) Um banco de dados relacional é composto de tabelas ou relações.
( ) Cada tabela é um conjunto de tuplas, ou linhas. ( ) As linhas de uma tabela devem, necessariamente, estar ordenadas. ( ) Existem três tipos de chaves: a primária, a alternativa e a estrangeira. ( ) Em sua especificação, devem ser definidas, no mínimo, tabelas e linhas.
Basicamente, um sistema de banco de dados é um sistema computadorizado capaz de armazenar informações e permitir que usuários acessem e atualizem essas informações. Analise as afirmativas a seguir, relacionadas a um sistema de banco de dados:
I. Entidade é um objeto distinguível da realidade modelada a ser representado no banco de dados;
II. Relacionamento define as associações entre entidades e não necessariamente associa somente entidades diferentes;
III. Modelo de dados é a representação física, na máquina real, dos componentes abstratos que constituem o modelo;
IV. Cardinalidade de uma entidade em um relacionamento é a propriedade que especifica o número de ocorrências de entidades associadas a cada atributo.
Estão(está) CORRETA(S) somente as afirmativas:
Embedded software is very important economically because almost every electrical device now includes software. There are therefore many more embedded software systems than other types of software system. If you look around your house you may have three or four personal computers. But you probably have 20 or 30 embedded systems, such as systems in phones, cookers, microwaves etc
Responsiveness in real time is the critical difference between embedded systems and other software systems, such as information systems, web-based systems, or personal software systems, whose main purpose is data processing. For non-real- time systems, the correctness of a system can be defined by specifying how system inputs map to corresponding outputs that should be produced by the system. In response to an input, a corresponding output should be generated by the system and, often, some data should be stored. For example, if you choose a create command in a patient information system, then the correct system response is to create a new patient record in a database, and to confirm that this has been done. Within reasonable limits, it does not matter how long this takes.
However, in a real-time system, the correctness depends both on the response to an input and the time taken to generate that response. If the system takes too long to respond, then the required response may be ineffective. For example, if embedded software controlling a car braking system is too slow, then an accident may occur because it is impossible to stop the car in time.
(Extraído de: Software Engineering, I. Sommerville, 9th Edition, 2011, pg. 538.)
Embedded software is very important economically because almost every electrical device now includes software. There are therefore many more embedded software systems than other types of software system. If you look around your house you may have three or four personal computers. But you probably have 20 or 30 embedded systems, such as systems in phones, cookers, microwaves etc
Responsiveness in real time is the critical difference between embedded systems and other software systems, such as information systems, web-based systems, or personal software systems, whose main purpose is data processing. For non-real- time systems, the correctness of a system can be defined by specifying how system inputs map to corresponding outputs that should be produced by the system. In response to an input, a corresponding output should be generated by the system and, often, some data should be stored. For example, if you choose a create command in a patient information system, then the correct system response is to create a new patient record in a database, and to confirm that this has been done. Within reasonable limits, it does not matter how long this takes.
However, in a real-time system, the correctness depends both on the response to an input and the time taken to generate that response. If the system takes too long to respond, then the required response may be ineffective. For example, if embedded software controlling a car braking system is too slow, then an accident may occur because it is impossible to stop the car in time.
(Extraído de: Software Engineering, I. Sommerville, 9th Edition, 2011, pg. 538.)
Embedded software is very important economically because almost every electrical device now includes software. There are therefore many more embedded software systems than other types of software system. If you look around your house you may have three or four personal computers. But you probably have 20 or 30 embedded systems, such as systems in phones, cookers, microwaves etc
Responsiveness in real time is the critical difference between embedded systems and other software systems, such as information systems, web-based systems, or personal software systems, whose main purpose is data processing. For non-real- time systems, the correctness of a system can be defined by specifying how system inputs map to corresponding outputs that should be produced by the system. In response to an input, a corresponding output should be generated by the system and, often, some data should be stored. For example, if you choose a create command in a patient information system, then the correct system response is to create a new patient record in a database, and to confirm that this has been done. Within reasonable limits, it does not matter how long this takes.
However, in a real-time system, the correctness depends both on the response to an input and the time taken to generate that response. If the system takes too long to respond, then the required response may be ineffective. For example, if embedded software controlling a car braking system is too slow, then an accident may occur because it is impossible to stop the car in time.
(Extraído de: Software Engineering, I. Sommerville, 9th Edition, 2011, pg. 538.)
A Capacity Management Information System or CMIS is a collection of IT infrastructure usage, capacity and performance information that has been gathered in a consistent manner and stored in one or more databases. It is the single book of record for all usage, capacity, and performance data, complete with associated business, application and service statistics. Any IT staffer needing access to capacity management data can potentially use a CMIS.
IT service management processes frequently accessing CMIS data are:
• Capacity planning
• Performance management
• Service level management
• Help/Service desk
• Incident management
• Problem management
• Configuration management
(Extraído de: www.teamquest.com.br/…/ whitepaper /)
Na frase “Any IT staffer needing access to capacity management data can potentially use a CMIS" o termo staffer, no contexto, tem o significado de
A Capacity Management Information System or CMIS is a collection of IT infrastructure usage, capacity and performance information that has been gathered in a consistent manner and stored in one or more databases. It is the single book of record for all usage, capacity, and performance data, complete with associated business, application and service statistics. Any IT staffer needing access to capacity management data can potentially use a CMIS.
IT service management processes frequently accessing CMIS data are:
• Capacity planning
• Performance management
• Service level management
• Help/Service desk
• Incident management
• Problem management
• Configuration management
(Extraído de: www.teamquest.com.br/…/ whitepaper /)
De acordo com o texto, um CMIS é uma coleção de informações de uso, capacidade e desempenho de infraestrutura de TI que tem sido