Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

M362 - Definitions > Unit 11 > Flashcards

Unit 11 Flashcards

1
Q

application object

A

A user-defined object in a CORBA application.

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

at-most-once

A

A semantics of invocation in which the invocation will block and will either successfully receive a result or fail due to an exception, resulting in a synchronous communication.

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

attribute (XML)

A

An attribute describes the properties of an element.

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

client (CORBA)

A

A CORBA object acting in the role of a client in some operation.

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

Common Data Representation (CDR)

A

A set of data types that may be used to represent types in various implementation languages in CORBA interfaces.

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

Common Intermediate Language (CIL)

A

In .NET, the common intermediate language to which all languages are compiled – equivalent to bytecode in Java.

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

Common Language Infrastructure (CLI)

A

In .NET, the collection of technologies allowing various implementation languages to run on different platforms.

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

Common Language Runtime (CLR)

A

The .NET environment that performs the task of just-in-time compilation of CIL to a platform-dependent code, and is also responsible for the lifecycle of .NET processes, including garbage collection.

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

Common Object Request Broker Architecture (CORBA)

A

The part of the OMG specification commonly known as CORBA, which specifies the properties an ORB must have to be CORBA compliant.

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

common service

A

In CORBA, common services are generic services that are useful across applications and domains, including support for printing, mobile agents and internationalisation.

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

Common Type System (CTS)

A

In .NET, the CTS defines mappings to and from supported implementation languages and the Microsoft Intermediate Language (MSIL).

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

component model

A

A set of standards describing the characteristics of a type of component, governing the implementation, documentation and deployment of components.

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

container (web service)

A

An environment used to deploy a Java EE or CORBA component and providing services to that component such as support for security and transactions.

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

CORBA compliant

A

In CORBA, software implementing the CORBA specification is said to be CORBA compliant.

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

CORBA services

A

Services that are often needed in distributed applications, such as support for naming, transactions and security.

See service.

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

cross-compiler

A

A compiler that will allow the creation of compiled code for a platform other than the one on which the development is undertaken.

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

discovery service

A

A component whose job it is to store details about services that are available on a network and respond to client requests for information about those services.

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

Document Object Model (DOM)

A

A platform-independent XML validation standard defining how to read and manipulate an HTML or XML document as an object representing a tree data structure, and providing random access to XML elements.

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

document type definition (DTD)

A

A DTD describes valid element types for a particular type of XML document (having a particular root element) and the relationships of the elements to each other.

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

domain service

A

CORBA services that are needed within particular application domains, such as medical or financial systems.

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

Dynamic Invocation Interface

A

In CORBA, this interface allows a client to bypass a stub and interact directly with an ORB’s services.

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

Dynamic Skeleton Interface

A

In CORBA, this interface allows a server to dynamically create a new interface.

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

element (XML)

A

A semantic markup of text, approximately equivalent to a type.

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

eXtensible Markup Language (XML)

A

A form of semantic markup of text similar to HTML.

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

heterogeneous system

A

A system implemented using more than one kind of computer, operating system or communication protocol and particularly using more than one programming language.

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

IDL compiler

A

A compiler for an interface definition language (IDL).

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

implementation repository

A

In CORBA, a database used by a server to register information about servant objects and enabling a client to access servant operations.

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

indirection

A

The general technique of using an intermediate layer to facilitate communication between two parts of a system.

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

interface definition language (IDL)

A

An IDL describes the message-passing ability of components in terms of operation names and parameters and provides a layer of indirection above the component.

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

interface repository

A

A database of interface information in CORBA, similar to the registry in Remote Method Invocation (RMI).

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

interface (CORBA)

A

The general term for descriptions of components’ message-passing ability in terms of their operation names and parameters.

32
Q

Internet Inter-ORB Protocol (IIOP)

A

A protocol for use in inter-ORB communication in CORBA applications, and providing support for distributed communication.

33
Q

interoperability

A

The property of being usable by other systems, particularly in a heterogeneous system context.

34
Q

lookup service

A

The part of a discovery service used by clients to ask for information about registered services. The discovery service can then enable clients to choose between various services, or it can choose a service for them.

35
Q

loose coupling

A

A loosely coupled component is insulated from changes in another component due to the presence of a layer of indirection between them.

36
Q

mapping

A

Rules for translating from a language to an interface definition language, including specification of the relationships between types in communicating idioms.

37
Q

Microsoft Interface Definition Language (MIDL)

A

The language used to describe the interface to a .NET object.

38
Q

middleware

A

Any software acting as an intermediary between two components, and particularly software that hides the heterogeneity of components, thus facilitating interoperability.

39
Q

mode

A

A modifier for a parameter in an operation definition, such as in CORBA’s interfaces, describing what may legally be done with the parameter. For example, whether the parameter may be read from, or written to.

40
Q

namespace

A

A hierarchical partitioning of names that provides a way of uniquely identifying any name in a context such as an XML document or software application.

41
Q

namespace prefix

A

The use of a namespace name as a qualifier for the simple name of an element or attribute, so forming an extended name.

42
Q

object (CORBA)

A

In CORBA, the general term for an object within a CORBA application, incorporating user-defined client and server objects as well as those implementing standard specifications such as those contained in common services.

43
Q

object adaptor

A

A component facilitating communication between an ORB and a CORBA servant.

44
Q

Object Management Architecture (OMA)

A

The architecture produced by the OMG,
of which CORBA is a part; described as an ‘open, vendor independent specification
for an architecture and infrastructure that computer applications use to work
together over networks’.

45
Q

Object Management Group (OMG)

A

The group responsible for the Object Management Architecture (OMA).

46
Q

object service (CORBA)

A

A general description for operations provided by objects in the context of CORBA.

47
Q

object type (CORBA)

A

In CORBA, a type defined by an interface within a module, specifying message-passing behaviour for a class of objects in a CORBA application.

48
Q

OMG Interface Definition Language (OMG IDL)

A

The interface definition language specified by the Object Management Group for use in CORBA.

See interface definition language (IDL).

49
Q

OMG Object Model

A

A platform-independent description of CORBA objects, operations, interfaces and types.

50
Q

operation (CORBA)

A

A general term for the message-passing ability of components in CORBA applications, roughly equivalent to a method.

51
Q

prologue

A

The first part of an XML document, which declares its version number and may include information such as the encoding (character set).

52
Q

qualified name

A

A name formed from a prefix and a simple name in XML.

53
Q

registration service

A

A component providing a way of registering interfaces in a repository to allow a client to perform service discovery.

54
Q

resolving a name

A

The process by which an object reference is associated with a particular servant object in a CORBA application; a binding of a reference to an object name.

55
Q

root element

A

The first element in an XML document, which encloses other elements and acts as a way of identifying the type of a document.

56
Q

Ruby on Rails

A

An approach to the development of web-based access to databases that uses a database specification, and scaffolding to provide the most commonly required operations.

57
Q

scaffolding

A

The technique of providing an infrastructure delivering commonly required operations and allowing modification for special cases, so facilitating rapid development.

58
Q

scope of discovery

A

The extent to which a service discovery application will search for a service matching a request.

59
Q

servant

A

An object, under the control of a server, providing a CORBA operation to a client.

60
Q

server (CORBA)

A

A CORBA object acting in the role of a server in some operation.

61
Q

service

A

A generic term describing the message-passing ability of components, but particularly used in service-oriented systems.

62
Q

service-oriented architecture

A

An architecture in which the main unit of communication is a message as opposed to a method invocation. Service providers use an interface to describe their services, and can be connected together in arbitrary configurations.

63
Q

skeleton

A

A layer between a servant and an ORB in a CORBA application.

64
Q

Simple API for XML (SAX)

A

An API providing access to XML as a stream of data and allowing serial access to elements, but not random access.

65
Q

simple name

A

A name used to uniquely identify an XML document’s namespace.

66
Q

SOAP

A

An XML-based protocol supporting communication between distributed systems and widely used in web services.

67
Q

software component

A

A software element that conforms to certain requirements for interoperability defined by a component object model. In particular, software components support the goal of composability to create higher functionality than they individually provide.

68
Q

stub

A

A layer between a client and an ORB in a CORBA application.

69
Q

tight coupling

A

A tightly coupled component communicates directly with another in such a way that changes in one are liable to affect the other.

70
Q

Universal Description, Discovery and Integration (UDDI)

A

An XML-based standard used by a server to register WSDL descriptions of web services and by a client to discover such services. As such it allows the creation of directories for web services.

71
Q

valid

A

An XML document is valid if it is well formed and conforms to a DTD.

72
Q

web service

A

An example of the network services paradigm in which software services are provided via the Web, particularly using HTTP, web pages and SOAP as communication mechanisms.

73
Q

Web Services Description Language (WSDL)

A

A language used by UDDI for the description of web service operations using XML.

74
Q

well formed

A

The property of an XML document of being syntactically (as opposed to semantically) correct.

75
Q

XML Schema Definition (XSD)

A

An XML-based description of an XML document, allowing for better type checking than a DTD and more rigorous constraints for XML documents to meet.

M362 - Definitions (12 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions