SYSTEM ENGINEERING Flashcards

1
Q

derived during preliminary design

A

DETAIL DESIGN AND DEVELOPMENT PHASE

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

Overall system and its major subsystem in hand, one may proceed to the realization of specific system components.

A

DETAIL DESIGN AND DEVELOPMENT PHASE

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

GIVE 2 DETAIL DESIGN REQUIREMENTS

A
  1. Procurement and acquisitions of system components begin, components are combined and integrated into a next higher assembly and a physical model of a system is constructed for test and evaluation.
  2. The integration, test, and evaluation steps constitute a bottom up activity and should result in a CONFIGURATION that can assessed for compliance with initially specified customer requirements.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

bases on the result from the requirements established during the conceptual and preliminary system design phase

A

Evolution of Detail Design

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

the design team has been established with the overall objective of integrating the various system elements into a final system configuration

A

Evolution of Detail Design

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

such elements include not only mission related hardware and software but also people, real estate and facilities, data information, consumables and the materials and resources

A

Evolution of Detail Design

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

GIVE 10 SYSTEM INTEGRATION ELEMENTS

A
  1. HARDWARE
  2. COMPONENT
  3. SOFTWARE
  4. PEOPLE
  5. SYSTEM REQUIREMENTS
  6. MATERIALS/RESOURCES
  7. REAL ESTATE
  8. FACILITIES
  9. DATA/INFORMATION
  10. CONSUMABLES
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

sometimes constructed to provide a realistic simulation of a proposed system configuration

A

MOCKUPS

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

The advance of computerized methods must be supported with conventional design documentation methods such as

A
  1. Design Drawing
  2. Material and Part List
  3. Analyses Report
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

represents the production/construction configuration of a system in all aspects of form, fit, function except that it has not been fully qualified in terms of operational and environmental testing.

A

System Prototype Development

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

to accomplish a specified amount of testing for the purposes of design evaluation prior to entering a formal test and evaluation phase

A

System Prototype Development

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

assist in the verification of technical concept and system design approaches.

A

System Prototype Development

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

Comprehensive analysis of all the equipment software and any other elements

A

Equipment/ Software Design Review

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

Will be doing after comprehensive analysis of all elements before releasing to the production.

A

Critical Design Review

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

The success of a formal design review is dependent on depth planning, organization, and data preparation

A

Design Review Goal

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

established during the conceptual design phase of life cycle preferably in parallel with the definition of the overall design requirements for the system.

A

System Test, Evaluation and Validation

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

pertains to certain design evaluation can be conducted in early system life cycle using computerized techniques to introduce CAD, CAM, CALS, simulation, rapid protoyping and related approaches.

A

ANALYTICAL

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

refers primarily to the evaluation of system components in the laboratory using engineering breadboards, bench test models, service test modles, rapid protoyping and the like.

A

TYPE I TESTING

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

Temperature cycling, shoch and vibration, humidity, sand and dust, salt spray, acoustic noise, explosion proofing and electromagnetic interface.

A

Environmental Qualification

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

Sequential testing, life testing, environmental stress screening and test analyze and fix

A

Reliability Qualification

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

Verification of maintenance tasks, task times and sequence maintenance personnel quantities and skill levels, degree of testability and diagnostic provisions prime equipment

A

Maintainability Demonstration

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

Verification of compatibility among prime equipment, test,and support equipment and group handling equipment

A

Support Equipment Compatibility

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

The verification and validation of operating procedures, maintenance procdeures and supporting data

A

Technical Data Verification

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

Verify to ensure the compatibility among the human and equipment, the personnel quantities and skill levels required and training needs.

A

Personnel Test and Evaluation

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

Verification that software meets the system requirement, the compatibility between software and hardware and the appropriate quality provisions have been incorporated.

A

Software Compatibility

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

It includes the completion of formal test at designed field test sites by user personnel over an extended period of time.

A

Type III Testing

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

Operating personnel, operational test and support equipment, operational spares, applicable computer software, and validated operating maintenance procedures are used

A

Type III Testing

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

It is conducted during the system operational use and life cycle support phase includes formal tests that are sometimes conducted to acquire specific information relative to some area of operation or support

A

Type IV Testing

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

sino crush ko?

A

syempre wala chz secret!!!!

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

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

A

CONCEPTUAL DESIGN PHASE

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

should be presented in specific qualitative and quantitative terms and in enough detail to justify progressing to the next step.

A

Statement of the Problem

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

should be performed with the objective of translating a broadly defined “want” into a more specific system-level requirement.

A

Need Analysis

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

It is accomplished with the objective of evaluating the different technological approaches that may be considered in responding to the specified functional requirements.

A

Feasibility Analysis

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

Anticipated time that the system will be in operational use

A

Operational Life Cycle (horizon)

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

Anticipated usage of the system and its elements

A

Utilization requirement

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

Effectiveness factors

A

a. Cost/System effectiveness
b. Operational availability, readiness rate, dependability
c. Logistics support effectiveness
d. Main time between maintenance (MTBM)
e. Failure rate (λ)
f. Maintenance downtime (MDT)
g. Facility utilization
h. Operational skill levels
i. Task accomplishment requirements
j. Personnel efficiency, and so on

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

Through the definition of operational requirements and the maintenance concept for the system, specific performance-related factors are identified and applied with the objective of ensuring that the system will be designed and developed such that it will satisfactorily accomplish its intended mission(s).

A

Technical Performance Measures (TPMS)

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

structured process or mechanism for determining customer requirements and
translating them into relevant technical requirements that each functional area and organization level can understand and act upon

A

QUALITY FUNCTION DEPLOYMENT (QFD)

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

It is focused on the voice of the customers and is developed in Japan (1960)

A

QUALITY FUNCTION DEPLOYMENT (QFD)

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

Preliminary design is also known as

A

Preliminary Design Phase

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

an iterative process of breaking requirements down from the system level to the subsystem, and as far down the hierarchical structure as necessary to identify input design criteria and /or constraints for the various elements of the system

A

Functional Analysis

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

refers to a specific or discrete action that is necessary to achieve a given objective.

A

Function

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

Functional Analysis Serves as a basis in the development of the following:

A

-Electrical and mechanical design for functional packaging, condition monitoring and diagnostic provisions.
-Reliability models and block diagram
-Failure mode, effect, and criticality analysis (FMECA)
-Fault-tree analysis (FTA)
-Reliability-centered maintenance (RCM) analysis
-System safety/hazard analysis
-Maintainability analysis
-Level-of-repair analysis
-Maintenance task analysis (MTA)
-Operator task analysis (OTA)
-Operational Sequence Diagram (OSDs)
-Supportability analysis
-Operating and maintenance procedures
-Producibility and disposability analysis

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

this involves a top-down distribution of the quantitative and qualitative criteria through the QFD analysis.

A

Allocation of Requirements

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

the probability that a system or product will perform in a satisfactory manner for a given period of time when used under specified operating conditions.

A

Reliability

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

characteristics of design and installation that reflects the ease, accuracy, safety, and economy of performing maintenance actions.

A

Maintainability

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

Translates customer requirements into technical requirements

A

Product Planning

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

Assigns control methods to process characteristics

A

Process-Control Planning

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

Identifies process steps and parameters and translates them into process characteristics

A

Process Planning

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

Translates technical requirements into component characteristics

A

Product Design

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

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

A

Operational deployment or distribution

52
Q

Evaluate the most likely candidates in terms of performance, effectiveness, logistics requirements, and life-cycle economic criteria.

A

Requirements for Feasibility Analysis

53
Q

design and development of a preferred system architecture that will ultimately be responsive to the identified customer need.

A

Purpose of Conceptual Design

54
Q

from the Greek systema, meaning an “organized whole”

A

Systems

55
Q

a regularly interacting or interdependent group of items forming a unified whole

A

Systems

56
Q

a collection of elements and a collection of inter-relationships amongst the elements such that they can be viewed as a bounded whole relative to the elements around them

A

Systems

57
Q

Key concepts of Systems

A

Interaction
Whole
Elements
Interrelationships

58
Q

A combination of interacting elements organized to achieve one or more stated purposes.

A

Engineered System

59
Q

a specialization of system which fulfills the basic properties of all systems, but which is explicitly man-made, contains technology, exists for a purpose and is engineered through a series of managed life cycle activities to make it better able to achieve that purpose.

A

Engineered System

60
Q

an interdisciplinary, collaborative approach to the engineering of systems (of any type) which aims to capture stakeholder needs and objectives and to transform these into a description of a holistic, life-cycle balanced system solution which both satisfies the minimum requirements and optimizes overall project and system effectiveness according to the values of the stakeholders.

A

Systems Engineering

61
Q

incorporates both technical and management processes.

A

Systems Engineering

62
Q

“A person who practices systems engineering” whose systems engineering capabilities and experience include sustained practice, specialization, leadership, or authority over SEactivities.

A

System Engineer

63
Q

supports a set of life cycle processes beginning early in conceptual design and continuing throughout the lifecycle of the system through its manufacture, deployment, use and disposal.

A

Systems Engineer

64
Q

must analyze, specify, design, and verify the system to ensure that its functional, interface, performance, physical, and other quality characteristics, and costare balanced to meet the needs of the system stakeholders.

A

System Engineer

65
Q

helps ensure the elements of the system fit together to accomplish the objectives of the whole, and ultimately satisfy the needs of the customers and other stakeholders who will acquire and use the system.

A

System Engineer

66
Q

may mean an engineered system, natural system, a social system, or all three.

A

System

67
Q

focuses on the domain of the engineered systems (ES).

A

System engineering

68
Q

treated as a special form of engineered system.

A

Sociotechnical systems

69
Q

The degree to which a system’s design or code is difficult to understand because of numerous components or relationships among components.

A

Complexity

70
Q

The principle that whole entities exhibit properties which are meaningful only when attributed to the whole, not to its parts.

A

Emergence

71
Q

is made up of combinations of elements.

A

System

72
Q

can be divided into a hierarchy of sets of elements that include subsystems, components, subcomponents, and parts.

A

System

73
Q

the building blocks of a systems and are not just hardware but can also include software, and can even include personnel, facilities, policies, documents and databases.

A

Elements

74
Q

set of interrelated components functioning together toward some common objectives) or purpose(s).

A

System

75
Q

The parts of a system. The operating parts of a system consisting of input, process, and output.

A

Components

76
Q

the properties (characteristics, configuration, qualities, powers, constraints, and state) of the components and of the system as a whole.

A

Attributes

77
Q

The purposeful action performed by a system.

A

Function

78
Q

static parts

A

Structural components

79
Q

are the parts that perform the processing.

A

Operating components

80
Q

are the material, energy, or information being altered.

A

Flow components

81
Q

the color of an automobile

A

Characteristic

82
Q

the strength of a steel beam

A

Quality

83
Q

the number and arrangement of bridge piers

A

Configuration

84
Q

the capacitance of an electrical circuit

A

Power

85
Q

the maximum speed permitted by the governor of a turbine

A

Constraint

86
Q

whether or not a person is talking on the telephone

A

State

87
Q

An example is symbiosis, the association of two
unlike organisms for the benefit of each other.

A

First order relationships

88
Q

called synergistic, are those that are complementary and add to system performance.

A

Second-order relationships

89
Q

exists when duplicate components are present for the purpose of assuring continuation of the system function in case of component failure.

A

Redundancy

90
Q

made up of components, and many components can be broken down into smaller components.

A

System

91
Q

the lower system, if two hierarchical levels are involved in a given system. A system in its own right, except it normally will not provide a useful function on its own, it must be integrated with other subsystems to make a system.

A

Subsystem

92
Q

Air Transportation

A

System

93
Q

Aircraft, terminal, ground support equipment, and controls

A

Subsystem

94
Q

Equipment items, people, and information

A

Components

95
Q

everything that remains outside the boundaries of the system

A

Environment

96
Q

material, energy, and/or information often pass through the boundaries

A

Input

97
Q

material, energy, and/or information that pass from the system to the environment

A

Outputs

98
Q

enters the system in one form and leaves the system in another form

A

Throughput

99
Q

at whatever level in the hierarchy, consists of all components, attributes, and relationships needed to accomplish one or more objectives. Each system has objectives (providing purposes) for which all system components, attributes, and relationships have been organized.

A

Total System

100
Q

placed on the system limit its operation and define the boundary within which it is intended to operate. Similarly, the system places boundaries and constraints on its subsystems.

A

Constraints

101
Q

include those that came into being through natural processes.

A

Natural systems

102
Q

those in which human beings have intervened through components, attributes, and relationships.

A

Human-made systems

103
Q

a natural system into which a human-made system has been integrated as a subsystem.

A

Human-modified system

104
Q

organizations of ideas

A

Conceptual systems

105
Q

those that manifest themselves in physical form.

A

Physical systems

106
Q

those that have structure, but without activity (as viewed in a relatively short period of time).

A

Static systems

107
Q

whose states do not change because it has structural components but no operating or flow components, as exemplified by a bridge.

A

Static systems

108
Q

Those made up of real components occupying space.

A

Physical systems

109
Q

exhibits behaviors because it combines structural components with operating and/or flow components.

A

Dynamic system

110
Q

is one that is relatively self-contained and does not significantly interact with its environment.

A

Closed systems

111
Q

One that does not interact significantly with its environment.

A

Closed systems

112
Q

usually exhibit the characteristic of equilibrium resulting from internal rigidity that maintains the system in spite of influences from the environment.

A

Closed systems

113
Q

allows information, energy, and matter to cross its boundaries.

A

Open system

114
Q

interact with their environment, examples being plants, ecological systems, and business organizations.

A

Open systems

115
Q

They exhibit the characteristics of steady state, wherein a dynamic interaction of system elements adjusts to changes in the environment. Because of this steady state, they are self-regulatory and often self-adaptive.

A

Open system

116
Q

may involve both the customer (or procuring agency) and the producer (or contractor).

A

Acquisition Phase

117
Q

may include a combination of contractor and customer for ultimate user) activities.

A

Utilization Phase

118
Q

as a systematic approach to creating a system design that simultaneously considers all phases of the life cycle, from conception through disposal, to include consideration of production, distribution, maintenance, phase-out, and so on.

A

Concurrent Engineering

119
Q

guided design is simultaneously responsive to customer needs (i.e., to requirements expressed in functional terms) and to life-cycle outcomes.

A

Lifecycle

120
Q

should not only transform a need into a system configuration but should also ensure the design’s compatibility with related physical and functional requirements.

A

Design

121
Q

Introduced by Royce in 1970, initially for software development.

A

Waterfall Process Model

122
Q

a.k.a Sequential Improvement Model

A

Spiral Process Model

123
Q

Boehm, 1986.
Adapted from Waterfall model
Iterative
Prototyping

A

Spiral Process Model

124
Q

Risk driven approach for the development of products or system

A

Spiral Process Model

125
Q

developed by Forsberg and Mooz

A

“VEE” Process Model

126
Q

This model starts with user needs on the upper left and ends with a user-validated system on the upper right.

A

“VEE” Process Model