Distributed Software Engineering Flashcards

1
Q

(MP)*Browsing the Web is the most common example of a situation where this architecture is used

A

two-tier client/server (C/S) architecture with thin clients

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

(MP) Commonly used to “modernize” legacy systems when separating application processing and data management is impractical

A

two-tier client/server (C/S) architecture with thin clients

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

(MP)*Applications with relatively stable end-user functionality used in an environment with well-established system management

A

two-tier client/server (C/S) architecture with fat clients

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

(MP)*An example of this type of architecture is a banking ATM system for which the hardware in the teller machine carries out most of the customer-related processing associated with transactions

A

two-tier client/server (C/S) architecture with fat clients

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

(MP)architecture with a bank ATM system which delivers cash and other banking services to users.

A

two-tier client/server (C/S) architecture with fat clients

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

(MP)Suitable for mobile applications where Internet connectivity cannot be guaranteed

A

two-tier client/server (C/S) architecture with fat clients

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

(MP)*architecture with a scalable Internet banking system

A

multi-tier client/server (C/S) architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

(MP)An example of this type of C/S architecture is an Internet banking system in which the bank’s customer database supports database processing, a web server provides the application services and data management, and the user’s computer supports an Internet browser

A

multi-tier client/server (C/S) architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

(MP)Suitable for applications where both the data and the application are volatile, and for applications where data from multiple sources are integrated.

A

multi-tier client/server (C/S) architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

(MP)*example of this architecture might be an easily extendable data mining system comprised of multiple standard data sources, a number of independent data “integrators” each attempting to deduce different relationships, graphical relationship “visualizers” and report generators

A

distributed component architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

(MP)architecture with a data mining system that looks for relationships between the data stored in a number of databases

A

distributed component architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

(MP)Some argue that this is less intuitive/natural than a client/server architecture, making systems more difficult to visualize, understand, and design

A

distributed component architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

(MP)All components are objects that provide services to, and receive services from, other objects; communication is via middleware.

A

distributed component architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

(MP)Objects provide general services that may be called on by other objects. This approach may be used for implementing client-server systems

A

distributed component architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

(MP)*This architecture has the advantage of being highly redundant and therefore both fault-tolerant and tolerant of nodes disconnecting from the network

A

peer-to-peer architecture (P2P)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

(MP)Examples of systems employing this architecture include Freenet, ICQ, and Jabber.

A

peer-to-peer architecture (P2P)

17
Q

(MP)*Appropriate where the system primarily involves the exchange of information between individual computers on a network and there is no need for this information to be centrally stored or managed (e.g., file-sharing systems)

A

peer-to-peer architecture (P2P)

18
Q

(MP)*Appropriate for computationally intensive applications for which it is possible to separate the processing required into a large number of independent computations

A

peer-to-peer architecture (P2P)

19
Q

(MP)*examples include web-based mail systems such as Yahoo! and Gmail, and office application such as Google docs

A

software as a service (SaaS)

20
Q

(MP)*Provides functionality on a remote server with client access through a web browser. The server maintains the user’s data and state during an interaction session. Transactions are usually long (e.g., editing a document)

A

software as a service (SaaS)

21
Q

(MP)Software delivery method whereby a software system is hosted remotely on a provider’s server (a “cloud”)

A

software as a service (SaaS)

22
Q

(MP)*An approach to structuring a software system as a set of separate, stateless services that may entail multiple providers and may be distributed.

A

service-oriented architecture (SOA)

23
Q

(MP)*Some developers of systems based on this architecture have opted to replace existing “inefficient” protocols developed to be open standards with so-called RESTful protocols having inherently lower overhead

A

service-oriented architecture (SOA)

24
Q

(MP)A strategy for designing and building software products through the composition of existing capabilities and services

A

service-oriented architecture (SOA)

25
Q

(MP)Structures a system as a set of separate, stateless services that may be provided by multiple providers and distributed. Typically, transactions are short, whereby a service is called, does something, and then returns a result

A

service-oriented architecture (SOA)

26
Q

(MP)**Commonly used in real-time systems where there may be separate processors associated with data acquisition from the system’s environment, data processing, and computation and actuator management.

A

master-slave architecture

27
Q

(MP)*architecture with a real-time traffic control system that has three logical processes that run on separate processors

A

master-slave architecture

28
Q

(12-SC) which one of the following is “the most important development that has affected distributed software systems in the past few years”?

A

The service-oriented approach

Other Wrong:

  • The CORBA middleware standard.
  • The message-based (non-synchronous) distributed component interaction model
  • Client-server computing.
  • Peer-to-peer technologies
29
Q

(QA)Briefly describe the scalability issue, and explain the distinction between “scaling-up” and “scaling-out” in addressing this issue

A

How can a system be constructed so as to deliver a high quality service (QoS) as demands on the system increase? Systems can be designed to “scale-up” by replacing resources with more powerful ones, and/or “scale-out” by adding additional resources

30
Q

Briefly describe the transparency issue

A

Should the distributed system in question appear to the user as a single (i.e., not a distributed) system, or would it be better for users to understand that the system is, in fact, distributed so they can better cope with problems that may arise?

31
Q

Briefly describe the openness issue

A

Should the system in question be designed using standard, generally accepted protocols that would support the integration of components from many suppliers that can interoperate with other system components, or should more specialized (possibly more efficient, more secure, etc.) protocols be used that would restrict the designer’s freedom in this regard?

32
Q

(11-QA) One of the factors that may need to be considered when implementing SaaS is multi-tenancy. From the users’ perspective, what are the two basic goals or objectives associated with multi-tenancy?

A

Giving each user the impression of being the sole system user, and allowing the efficient sharing of the system’s resources

33
Q

**(11-QA) **One of the factors that may need to be considered when implementing SaaS is multi-tenancy. From a designer’s perspective, what is required in order to achieve these goals/objectives?

A

The system must be designed so that there is an absolute separation between the system functionality and the system state. (Thus, all operations should be “stateless”.)

34
Q

(QA)Briefly describe Security

A

How can usable security policies be defined and implemented that apply across a set of independently managed systems?

35
Q

(QA)Briefly describe QOS

A

How should the QOS delivered to system users be specified and how should system be implemented to deliver an acceptable QOS to all users?

36
Q

(QA)Briefly describe Failure Mangement

A

How can system failures be detected, contained, and repaired?