Brainscape's Knowledge GenomeTM

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


See full index

System Engineering > Midterms > Flashcards

Midterms Flashcards

1
Q

From the Greek word “systema”, meaning an organized whole

A

System

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

Came into being though natural processes

A

Natural Systems

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

Those that have been developed by human beings

A

Man-Made Systems

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

Made up of real components occupying space

A

Physical Systems

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

An organization of ideas, a set of specification and plans

A

Conceptual Systems

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

Those that have structure, but without activity

A

Static Systems

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

One that combines structural components with activity

A

Dynamic Systems

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

relatively self-contained and does not significantly interact with its environment

A

Closed System

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

Interact with their environment
Ex. Support Capability

A

Open-Loop System

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

A collection of components systems that produce results unachievable by the individual systems alone.

A

System of Systems (SOS)

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

Parts of the System, elements of which the system is composed

A

Components

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

Properties of the individual components

A

Attributes

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

Between (pairs of) components so that the components interact to support the system’s functionality (common purpose)

A

Relationships

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

Values of the attributes and relationships at a particular moment

A

State

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

A type of components that is static

A

Structural Components

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

Dynamic Components which “do the work”

A

Operating Components

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

Things which change, such as information, energy or material

A

Flow Components

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

Color, strength, size, weight, and power

A

Attribute of Components

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

if 2 hierarchical levels are involved in a given system, the lower is conveniently called subsystem

A

Systems and subsystems

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

Anything outside the system of the boundaries of the system is considered ___

A

Environment

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

An interdisciplinary approach and means to enable the realization of successful systems (INCOSE)

A

Systems Engineering

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

Defined as a methodical, multi-disciplinary approach for the design, realization, technical management, operations, and retirement of a system

A

Systems Engineering

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

That is, we say that a project is delivering a system, or is delivering a product

A

System as a product

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

Systems are much more than just the aggregation of hardware or software products

A

System as a Capability

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

A capability (in systems engineering) is created through the proper and effective interaction of people, process and technology

A

Capability System

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

A logical description of a system, the system’s mission is broken down into a hierarchical structure of its major functions - to form a functional hierarchy

A

Logical (Functional) Hierarchy

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

Here we can use a simple 4 - layer (common) representation of a system

A

Physical Hierarchy

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

Phase where the life cycle begins with the ________ phase with an idea for a system being generated as a result of a business planning

A

Pre-Acquisition Phase

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

This phase is focused on bringing the systems into being and into the service of the organization

A

Acquisition Phase

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

The system is operated (also supported) during the _____

A

Utilization phase

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

This phase could also be a mark of another life cycle

A

Retirement Phase

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

A Phase where design is the formal transition from the business world to the project world, i.e. from the mission statement to complete logical description of the system of interest

A

Conceptual Design Phase

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

Articulated and confirmed by the business management

A

Business Needs and Requirements (BNR)

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

BNR are elaborated by the stakeholders at the business operations level into a set of ______

A

Stakeholders Needs and Requirements

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

SNR are elaborated by requirements engineering into system requirements in the ________

A

System Requirements Specifications (SyRS)

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

BNR, SNR, and the SyRS are the key elements to establishing the _________

A

Functional Baseline (BSL)

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

Conceptual Design ends with the ______

A

Systems Design Review (SDR)

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

Converts the logical architecture of the initial FBL into descriptions of the physical subsystems (upper-level physical architecture) that will meet system requirements.

A

Preliminary Design Phase

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

Uses engineering disciplines to develop the individual subsystems, assemblies

A

Detailed Design & Development

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

Review at the end of this activity is called the ________

A

Critical Design Review (CDR)

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

Components are produced in accordance with the PBL specifications

A

Construction and/or Production

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

Major activities in the phase are:
- Operational use
- System support

A

Utilization and Retirement Phase

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

A linear and sequential approach where each phase (e.g., requirements, design, implementation, testing, deployment) is completed before the next one begins.

A

The Waterfall Model

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

(an extension of the Waterfall model) where development stages are paired with corresponding testing stages

A

“V” Model

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

Well-suited for projects where requirements are expected to evolve over time, and where feedback and refinement are critical to achieving the desired outcomes.

A

The Iterative Model

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

Emphasizes iterative development, strong focus on risk management and flexibility

A

Spiral Model

47
Q

Completed and accurate definition is fundamental to project success.

A

Requirements Engineering

48
Q

is required so that design decisions can be traced from any given system-level requirements down to a detailed design decision

A

Forward Traceablity

49
Q

any lower-level requirement is associated with at least one higher level requirements

A

Backward traceability

50
Q

Assures the customer that all requirements can be accounted for in the design at any stage

A

Traceability

51
Q

Systems Engineering maintains a life-cycle focus as decisions are made

A

Life Cycle Focus

52
Q

Systems Engineering is looking for optimal system-level performance.

A

System Optimization and Balance

53
Q

Systems Engineering integrates a diverse range of technical disciplines and specializations

A

Integration of Specializations/Disciplines

54
Q

Systems Engineering clearly has a technical role but also needs to have a very important management role.

A

Management

55
Q

We concentrate on the intent and main aim of each application of this foundation process

A

Systems Engineering Processes

56
Q

Oversees the systems engineering process

A

Systems Engineering Management

57
Q

Tools are available to help managers and process people undertake their tasks

A

Systems Engineering Tools

58
Q

Technical and non-technical disciplines are related to systems engineering

A

Related Disciplines

59
Q

Systems Engineering relies on the continual application of the simple problem-solving process of ______, _______, and ________

A

Synthesis, Analysis, and Evaluation

60
Q

Commences with the perceived need for the system

A

Analysis

61
Q

the “design” and “creation” functions

A

Synthesis

62
Q

________ is performed throughout its life-cycle:

A

Evaluation

63
Q

The basic analysis - synthesis - evaluation loop is applied iteratively throughout the system life cycle

A

Systems Engineering Process

64
Q

Elements are attributed to the source and are normally gathered via interview or workshop

A

Elicitation

65
Q

Entails breaking a higher-level requirements into those lower-level requirements that are explicitly required by it.

A

Decomposition

66
Q

Requirements engineering drawing some inference. The stakeholder did not mention the req’t directly but the derived req’t is necessary part of the system design if one or more directly stated requirements is to be met

A

Derivation

67
Q

_______ and ________ are not for novices and require requirements engineers (or business analysis) to understand

A

Elicitation/Elaboration

68
Q

A the result of the formal transformation of one or more needs into an agreed-to obligation from an entity to perform some function or possess some quality (within specified constraints)

A

Requirements

69
Q

Something that the system should do or provide

A

Functional Requirement

70
Q

Some property, quality or attribute, that the system must possess, a condition that must be met, or a constraint under which is must operate or be developed

A

Non-functional requirement

71
Q

The first and most important phase of the system design and development process

A

Conceptual System Design

72
Q

Given that identified need for a system, the next stage of system planning and architecting can be initiated called the Program Management Plan (PMP)

A

System Planning and Architecting

73
Q

Identify various system-level design alternatives that could be pursued in response to the need

A

System Design and Feasibility Analysis

74
Q

Once the need and technical approach have been defined, it is necessary to translate this into some form of “operational scenario” or a set of operational requirements

A

System Operational Requirements

75
Q

Identification of the prime and secondary (alternative) missions of the system

A

Mission Definition

76
Q

Definition of the operating characteristics and functions (size, weight, speed, range, accuracy, flow rate, capacity, transmit, receive, throughput etc.)

A

Performance and Physical Parameters

77
Q

Identification of the quantity of equipment, software, personnel, facilities, (and so on) and the expected geographical location to include transportation and mobility requirements

A

Operational Deployment and Distribution

78
Q

Anticipated time that the system will be in operational use

A

Operational life cycle (horizon)

79
Q

Anticipated usage of the system and its elements

A

Utilization requirements

80
Q

System requirements specified as figures-of-merit (FoMs)

A

Effectiveness factors

81
Q

Definition of the environment in which the system is expected to operate

A

Environmental factors

82
Q

The prime system elements must be designed in such a way that they can be efficiently and effectively supported through the entire system life cycle and the maintenance and support infrastructure must be responsive to this requirement

A

System Maintenance and Support

83
Q

Include corrective and preventive maintenance

A

Levels of maintenance

84
Q

dictate that an item (in the event of failure) is nonrepairable, partially repairable, or fully repairable.

A

Repair Policies

85
Q

may be responsibility of the customer, producer (supplier), or a third-party

A

Organizational responsibilities

86
Q

Criteria must be established for the various elements of maintenance support

A

Maintenance Support Elements

87
Q

Consist of the effectiveness factors associated with the support capability

A

Effectiveness requirements

88
Q

This includes temperature, shock and vibration, humidity noise, arctic vs tropical environment, mountainous vs flat terrain, shipboard vs ground conditions

A

Environment

89
Q

The objective here is to derive the overall performance goals (and be clear) as to which the system must be designed.

A

Technical Performance Measures

90
Q

Team approach to help ensure that the voice of customer is reflected in the ultimate design

A

Quality Function Deployment

91
Q

Functional analysis is the iterative process of breaking down requirements from the system-level, to the subsystem, and so on to identify input design criteria

A

Functional Analysis and Identification

92
Q

At this point, decisions must be made regarding:

A

System Trade off Analysis

93
Q

The results from the previous activities are used to establish the specific “design-to” requirements for the system (the ultimate objective of this stage)

A

System Specifications

94
Q

Design information is released and reviewed for compliance with the basic system-equipment requirements.

A

Conceptual Design Review

95
Q

Causality driven, holistic approach to describing the interactive relationships between components inside a system as well as influences from outside the system

A

Systems Thinking

96
Q

Methodology used to study the behavior of complex systems over time

A

System Dynamics

97
Q

Refers to how key variables in a system change over time

A

System Behavior

98
Q

When an initial quantity of something starts to grow, and the rate of growth increases

A

Exponential Growth

99
Q

When the quantity of interest starts either above or below a goal level and over time moves towards the goal

A

Goal-seeking behavior

100
Q

When initial exponential growth is followed by goal-seeking behavior, which results in the variable leveling off

A

S-shaped Growth

101
Q

When the quantity of interest fluctuates around some level

A

Oscillation

102
Q

Snapshot of all relationship that matter

A

Causal Loop Diagrams

103
Q

Components of system that can change overtime

A

Variables

104
Q

Links between variables are the verbs in the system

A

Links

105
Q

Reinforcing loop is a loop that amplifies changes in system

A

Feedback loop

106
Q

Shows relationship among variables which have the potential to change overtime

A

Stocks and Flow Diagrams

107
Q

Accumulation of stuff, either concrete, such as dollars or groundwater that can increase or decrease overtime

A

Stock

108
Q

Describes actions or processes that transport stuff

A

Flow

109
Q

Holds information about the system that affects rate of flows or affects value of another converter

A

Converter

110
Q

Moves information from one elements to another

A

Connector

111
Q

Can be represented within flow/rate equations or as a distinct item in stocks and flow diagram

A

Constant

112
Q

Stocks that lie outside of the model’s boundary

A

Sources and links

113
Q

Commonly occurring combination of reinforcing and balancing feedback

A

System Archetypes

114
Q

A focused methodology for carefully listening to the voice of the customer (VOC)

A

Quality Function Deployment

System Engineering (1 decks)

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