Brainscape's Knowledge GenomeTM

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


See full index

QA > R1 > Flashcards

R1 Flashcards

1
Q

is defined inengineeringas the process of bringing together the component sub-systemsinto one system and ensuring that the subsystems function together as a system.

A

System Integration

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

Methods of Integration (3)

A
  • Vertical Integration
  • Star Integration
  • Horizontal Integration / Enterprise Service Bus (ESB)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

is the process of integrating subsystems according to their functionality by creating functional entities also referred to assilos.

A

Vertical Integration

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

is a process of systems integration where each system is interconnected to each of the remaining subsystems.

A

Star Integration

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

is an integration method in which a specialised subsystem is dedicated to communication between other subsystems.

A

Horizontal integration or Enterprise Service Bus (ESB)

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

involves the overall testing of a complete system of many subsystem components or elements. The system under test may be composed of hardware, or software, or hardware with embedded software, or hardware/software with human-in-the-loop testing.

A

System Integration Testing

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

is a collection of open protocols and standards used for exchanging data between applications or systems.

A

Web Service

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

Web Service Roles (3)

A
  • Service Provider
  • Service Requestor
  • Service Registry
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Components of Web Services (3)

A
  • SOAP (Simple Object Access Protocol)
  • UDDI (Universal Description, Discovery and Integration)
  • WSDL (Web Services Description Language)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

is a style of software design where services are provided to the other components by application components, through a communication protocol over a network.

A

Service-oriented Architecture (SOA)

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

Four properties of SOA

A
  • It logically represents a business activity with a specified outcome.
  • It is self-contained.
  • It is ablack box for its consumers.
  • It may consist of other underlying services
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

SOA Characteristics (8)

A
  • Based on open standards
  • Foster inherent reusability
  • Foster intrinsic interoperability
  • Emphasises extensibility
  • Fundamentally autonomous
  • Promotes dynamic discovery
  • Promotes architectural composability
  • Supports incremental implementation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

is an application that is composed largely of services, which are often in a hierarchy.

A

Service-oriented Applications

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

Potential Benefits of SOA (5)

A
  • Efficient and effective usage of ‘Business Services
  • Improved Integration, intrinsic interoperability
  • Organizational agility • Loosely-coupled with
  • Drives business processes closer to end users
  • Leverage and integrate existing applications
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q
  • is a communication protocol that lets application exchange information over HTTP and can communicate between applications via internet
A

SOAP

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

SOAP Elements (5)

A
  • Message
  • Envelope
  • Header
  • Body
  • Fault
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

the root element of a SOAP message that defines the XML document as a SOAP message

A

Envelope

18
Q

If present it must be the first child element of the Envelope and is an Application-specific information of the SOAP Message

A

Header

19
Q

The actual SOAP message for the ultimate endpoint of the message it contains request and response

A

Body

20
Q

Indicates Error Messages, it must appear as child element of the Body and can only appear once in a SOAP message

A

Fault

21
Q

it is designed to store and transport data and was also designed to be self-descriptive

A

XML (eXtensible Markup Language)

22
Q

XML Structure (3)

A
  • An XML declaration
  • A document type declaration
  • A body or document instance
23
Q

is a piece of markup (which may span multiple lines of a file) that identifies this as an XML document. The declaration also indicates whether the document can be validated by referring to an external Document Type Definition (DTD)

A

XML Declaration

24
Q

follows the XML declaration. The purpose of this declaration is to announce the root element and to provide the location of the DTD

A

Document Type Declaration

25
Q

is the bulk of the information content of the document.

A

Document Body

26
Q

helps to restrict tags and specify the order of tags used in the XML. Can be embedded within the XML or an external file.

A

DTD (Document Type Definition)

- XML Validaiton

27
Q

is more advanced than DTD and can specify the data type of the value stored inside tags. Must always be an external file.

A

XSD (XML Schema Definition)

- XML Validation

28
Q

Pitfalls in System Integration (11)

A
  • Teams lose focus of the overall goal
  • Absence of Main Project Leader
  • Formal Roles and Responsibilities
  • Weekly Status
  • Scope Creep
  • Delivery Time
  • Time Control
  • Quality Assurance
  • Commitment and Communication
  • Structured, Proven Methods
  • Budgeting/Estimating
29
Q

Time Control (2)

A
  • Effort Variance

- Staffing Variance

30
Q

the difference between the original estimate and the sum of the actual time spent and the estimate to complete.

A

Effort Variance

31
Q

the difference between the amount of time spent on the project minus the amount of time scheduled to be spent on the project at that point in time.

A

Staffing Variance

32
Q

They get distracted by other important but less critical objectives. (Pitfalls in System Integration)

A

Teams lose focus of the overall goal

33
Q

Establish one person who will have overall control of the project. There can be joint project leaders, but one person must have overall control. (Pitfalls in System Integration)

A

Absence of Main Project Leader

34
Q

Each member of the project team must have their roles and responsibilities specifically defined at the beginning of the project. (Pitfalls in System Integration)

A

Formal Roles and Responsibilities

35
Q

These reports must be prepared without exception and must reflect the actual status of the project.(Pitfalls in System Integration)

A

Weekly Status

36
Q

The IS (Information Systems) community is too willing to bend when it comes to users begging and pleading to make changes to the original scope. (Pitfalls in System Integration)

A

Scope Creep

37
Q

If it takes longer than six to seven months to have a tangible usable deliverable from the system—it’s too long. (Pitfalls in System Integration)

A

Delivery Time

38
Q

Tracking two simple variances can help identify problems before they become unmanageable. (Pitfalls in System Integration)

A

Time Control

39
Q

Members of the project team are often too caught up with the specifics of the project to identify unforeseen pitfalls. (Pitfalls in System Integration)

A

Quality Assurance

40
Q

Too many times systems integration projects are initiated without a full understanding of the mission. (Pitfalls in System Integration)

A

Commitment and Communication

41
Q

With Client/Server and Open Systems technology, many clients think they can accomplish the project without formal structure or adherence to a methodology. (Pitfalls in System Integration)

A

Structured, Proven Methods

42
Q

Too often, IS is forced into the position of telling the users/sponsors what the system will cost before knowing all the features and functions to be implemented. (Pitfalls in System Integration)

A

Budgeting/Estimating

QA (2 decks)

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