Configuring the Physical Architecture Flashcards

1
Q

captures the structural representation of the design solution, as well as the engineering drawing, diagrams, models, from which the solution was derived.

A

Physical Architecture

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

establishes the arrangement and integration of relationships of structural units and components.

A

Structural Design Solution

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

3 ELEMENTS OF STRUCTURAL DESIGN SOLUTION

A
  1. Software Structural Design Solution
  2. Software Integration Strategy
  3. Software Operational Environment
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

is an element of structural design solution that identifies the software product configuration, structural assemblages, software integration strategy, and interface that characterize the software design.

A

Software Structural Design Solution

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

3 PARTS OF SOFTWARE STRUCTURAL DESIGN SOLUTION

A
  • Software Product Configuration
  • Structural Units
  • Structural Component
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

part of software structural design solution that identifies the structural units and components that are assembled and integrated.

A

Software Product Configuration

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

represents the fundamental design elements or software building block.

A

Structural Units

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

represents compound software building blocks comprised of two or more structural units or lower-level components.

A

Structural Component

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

is an element of software structural design solution that identify the sequence of assembly ad integration task.

A

Software Integration Strategy

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

2 TYPES OF ASSEMBLAGES IN SOFTWARE INTEGRATION STRATEGY

A
  • Structural Assemblages
  • Graphical User Assemblage
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

represents the assembly and integration tasks that generate a structural component.

A

Structural Assemblages

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

Composed of only the graphical-bases display and components.

A

Graphical User Assemblage

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

an element of structural design solution that identifies the computing equipment, external systems, and related software application of the software product.

A

Software Operational Environment

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

3 TERMS UNDER SOFTWARE OPERATIONAL ENVIRONMENT

A
  • Computing Environment
  • Interface Relationship
  • External Interface
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

the set of computing technology resources.

A

Computing Environment

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

identifies the agreements and commitments for the software product.

A

Interface Relationship

17
Q

identifies the data exchanges protocol and format for data shared among interfacing system and application.

A

External Interface

18
Q

an external system or software application that the software product under development must interface with.

A

External Systems

19
Q

are identified from the set of functional units specified by the functional architecture.

A

Structural Units

20
Q

8 BEHAVIORAL ANALYSIS (Model Design Presentation)

A
  1. Functional Decomposition Diagram
  2. Operational Model
  3. Execution Timeline
  4. Entity-Relationship Diagram
  5. Interface Block Diagram
  6. Structural Configuration Diagram
  7. Engineering Assembly Diagram
  8. Software Integration Diagram
21
Q

depiction of the functional hierarchy.

A

Functional Decomposition Diagram

22
Q

depiction of the operational or business process.

A

Operational Model

23
Q

a depiction of the software product or process execution timeline.

A

Execution Timeline

24
Q

relationship of the physical interface to other element in the architecture.

A

Entity-Relationship Diagram

25
a depiction of the physical interface.
Interface Block Diagram
26
depiction of structural elements.
Structural Configuration Diagram
27
a variation of structural configuration diagram that identifies the structural sub elements.
Engineering Assembly Diagram
28
a variation of structural configuration diagram that identifies the version, file name, location, etc. of each structural element.
Software Integration Diagram
29
is any informative gathering exercise where two or more design alternatives are analyzed.
Trade Study
30
can only be provided by extensive design evaluation of evert failure mode that may be possible.
Software Dependably
31
is used to generate a mockup of an engineering assembly for the purpose of evaluating the performance, usability, and aesthetic association.
Software Prototyping
32
4 PRIMARY FORM OF PROTOTYPING
1. Rapid Prototyping 2. Evolutionary Prototyping 3. Incremental Prototyping 4. Extreme Prototyping
33
a form of prototyping that creates a working model of various parts of the software product at a very early stage, after relatively short investigation.
Rapid Prototyping
34
a form of prototyping that creates a robust prototype in a structure manner and constantly refining it.
Evolutionary Prototyping
35
a form of prototyping that which the final product is built as separate prototype that are integrated into an overall product configuration.
Incremental Prototyping
36
a form of prototyping that is used for developing web applications.
Extreme Prototyping
37
3 THINGS TO EVALUATE (Software Product Performance Evaluation)
1. Design responsiveness 2. Design Dependability 3. Resource Utilization