Brainscape's Knowledge GenomeTM

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


See full index

TM354 > Block 3 - From architecture to product > Flashcards

Block 3 - From architecture to product Flashcards

1
Q

Adapter pattern

A

where component_A wraps component_B thereby becoming its interface;

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

analysis pattern

A

a high-level conceptual-analysis solution;

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

analytical completeness (FRs)

A

where SS is complete w.r.t. solely FRs;

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

applet

A

a plug-in component installed in the client browser;

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

Architectural pattern

A

describes a high-level recurring design solution;

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

architectural view

A

a model of the SS framed w.r.t. a specific stakeholder;

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

architecture specialisation

A

where specific components are selected;

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

assertion (handling) mechanism

A

a run-time construct evaluating SO precons / postcons / invariants;

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

assertions

A

= {precons, postcons, invariants}

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

asynchronous

A

where clientComponent can carry on without waiting for serverComponent’s response

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

basis-path testing (WBT)

A

where each statement in a method is tested 1+ times;

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

blackboard (data-centred)

A

an arch-pattern where users can update store and vice versa;

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

black box testing (BBT)

A

testing w.r.t. component’s spec;

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

boundary testing

A

where test data is produced around the partitions between the input subdomains;

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

bursty event

A

where event occurs in unpredictableClusters;

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

(test) case analysis (partitioning)

A

partitioning test data into subdomains;

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

cloud computing

A

where all software runs on third-party servers;

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

completeness (FRs)

A

where all FRs have been implemented;

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

component-based development (CBD)

A

where the SS is built with pre-existing components;

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

connector

A

reps the comm. between components in an arch-pattern;

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

container

A

a component that creates and encompasses other objects;

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

context dependency

A

where a component requires other services to provide its service;

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

coupling between objects (CBO) metric

A

the number of associations a class has with other classes;

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

cyclomatic-complexity metric (CCM)

A

= numberDecisionPoints + 1;

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

data-centred

A

an arch-pattern where there is a centralised persistent data store;

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

defensive programming

A

where precons should always be checked;

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

dependency injection

A

where a container object appropriately initialises a specific object for a client;

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

deployment model

A

reps specific components being implemented on machines;

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

depth-of-inheritance-tree (DIT) metric

A

the number of anscestors a class has;

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

Design by Contract (DbC)

A

where precons are assumed to have been met;

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

design pattern

A

describes a mid-level recurring design solution;

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

enterprise architectures

A

SSs designed for large orgs;

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

error guessing

A

where SOs are tested with random data;

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

executable documentation

A

where code is automatically checked against documentation at run-time;

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

extreme programming (XP)

A

an agile software development method;

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

Factory pattern

A

where a specialised object creates and initialises other objects;

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

fixture

A

the conditions&InputData for a test;

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

flexibility

A

how easily the SS can be modified;

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

foreign key

A

a column in a database table holding a key from a different table;

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

framework

A

a package providing behaviour common to a variety of applications;

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

heuristic evaluation

A

testing the SS wihout users;

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

HTTP

A

an interface for web-components to exchange data;

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

idiom

A

a programming-language specific pattern;

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

inertial convention

A

where componentStates outwith postcons are assumed to be unchanged;

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

integration testing

A

where the emergent properties of sets of components are tested;

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

interface

A

the SOs of a component;

47
Q

Java Enterprise Edition (Java EE)

A

a framework for consructing enterprise systems;

48
Q

jitter

A

variationInLatency;

49
Q

lack-of-cohesion-in-methods (LCOM) metric

A

numPairs of methods referencing the same attributes minus the numPairs that don’t;

50
Q

latency

A

stimulusProcessingTime;

51
Q

layered style

A

where components form a chain and can only message their immediate neighbours;

52
Q

location transparency

A

where consumers use a service without knowing where service is hosted;

53
Q

Mean Time to Change (MTTC)

A

the averageTime to fix a bug;

54
Q

miss rate

A

proportion of requests not responded to;

55
Q

model

A

a simplified rep of a problemDomain or softwareSolution;

56
Q

Model-View-Controller (MVC) pattern

A 
model = database;
view = UI-output;
controller = UI-input;
57
Q

notification pattern

A

where observerComponents register with a subjectComponent for updates;

58
Q

number-of-children (NOC) metric

A

numImmediateDescendants of a parentClass;

59
Q

path parameter

A

URI/pathParameter;

60
Q

peer-to-peer

A

a cliver network;

61
Q

performance

A

how well a SS can process serviceRequests;

62
Q

pipe and filters

A

filter = processor; pipe = pipe

63
Q

polymorphism

A

where the particular object responding to a serviceRequest is determined at runTime;

64
Q

postcondition

A

an assertion that must be true on completion of a UC or SO;

65
Q

precondition

A

an assertion that must be true commencement of a UC or SO;

66
Q

presentation layer

A

= UI;

67
Q

primary key

A

the attribute that uniquely identifies each row of a databaseTable;

68
Q

product

A

the object produced by the Factory object;

69
Q

product line

A

a set of related software products;

70
Q

provided interface

A

the SO-outputs of a component;

71
Q

publish-subscribe

A

where subscribersComponents register to receive updates from a publisherComponent;

72
Q

quality attribute scenario

A

specifying an NFR in detail to inform arch-decisions;

73
Q

Quantity pattern

A

gives guidance on how to rep dimensioned quantities;

74
Q

random testing (BBT)

A

where testData is randomly generated for the input domain;

75
Q

record

A

a row of a database table;

76
Q

refactoring

A

improving clarity of an SO’s code without changing without changing the SO’s precons / postcons / invariants;

77
Q

regression testing

A

test(allPreviousTests & newTest);

78
Q

repository

A

centralised store of persistent data;;

79
Q

required interface

A

the SO-inputs of a component;

80
Q

Requirements pattern

A

a description of knowledge used in the elicitation of requirements;

81
Q

response-for-a-class (RFC) metric

A

size(classResponseSet);

82
Q

response set

A

all (own, inherited and invoked) methods of a class;

83
Q

restart testing

A

testing that SS can recover from errors of internal state;

84
Q

RESTful

A

= REpresentational State Transfer + ful = where a webService users a lean interface (e.g. HTTP);

85
Q

security testing

A

tests that SS’s security cannot be breached;

86
Q

service-oriented architecture (SOA)

A

where applications are built out of loosely coupled services;

87
Q

service-oriented pattern

A

where providers make services available to consumers;

88
Q

signature

A

= SO-returnType + SO-name + SO-parameters;

89
Q

Singleton pattern

A

where no more than one instance of a specific class is created;

90
Q

software architecture

A

= components + relations;

91
Q

software metrics

A

measurable quantities that inform SQFs;

92
Q

SQF

A

one of the 11 attributes of a SS:

  • correctness
  • reliability
  • efficiency
  • integrity
  • usability
  • maintainability
  • flexibility
  • testability
  • portability
  • reusability
  • interoperability
93
Q

sporadic event

A

= infrequent&Isolated;

94
Q

start-up testing

A

tests that SS can start in a working configuration;

95
Q

statelessness

A

= component has no memory;

96
Q

stochastic event

A

occurs according to a well-defined probability distribution;

97
Q

straight-through path

A

the path where all loop / if conditions evaluate to false and switch statements evaluate to default;

98
Q

stress testing

A

testing that SS can operate at limits of its resources;

99
Q

subdomain

A

a set of inputValues requiring the same processing = equivalenceClass;

100
Q

test case

A

the conditions&Data for checking whether SO satisfies its assertions;

101
Q

test-driven development (TDD)

A

tests before code;

102
Q

throughput

A

numEvents dealt with in a given time;

103
Q

unit testing

A

where components are tested in isolation;

104
Q

usability testing

A

where UI is tested w.r.t. intendedUsers;

105
Q

user-command testing

A

testing userCommands w.r.t. tolerance to syntax / dataInput errors;

106
Q

user-defined type

A

a bespoke sourceAlphabet;

107
Q

validation

A

checking SS w.r.t. customerRequirements;

108
Q

verification

A

checking SS w.r.t. designSpec;

109
Q

view (MVC)

A

UI-output;

110
Q

viewpoint / concern

A

a perspective on SS w.r.t. a particular stakeholder;

111
Q

virtual machine

A

a simulation of a computer;

112
Q

weighted-methods-per-class (WMPC) metric

A

= sumForClass(method-CCMs);

113
Q

white box testing (WBT)

A

testing w.r.t. component’s code;

TM354 (3 decks)

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