SYSTEM ENGINEERING Flashcards
1
Q
derived during preliminary design
A
DETAIL DESIGN AND DEVELOPMENT PHASE
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
3
Q
GIVE 2 DETAIL DESIGN REQUIREMENTS
A
- 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.
- 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.
4
Q
bases on the result from the requirements established during the conceptual and preliminary system design phase
A
Evolution of Detail Design
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
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
7
Q
GIVE 10 SYSTEM INTEGRATION ELEMENTS
A
- HARDWARE
- COMPONENT
- SOFTWARE
- PEOPLE
- SYSTEM REQUIREMENTS
- MATERIALS/RESOURCES
- REAL ESTATE
- FACILITIES
- DATA/INFORMATION
- CONSUMABLES
8
Q
sometimes constructed to provide a realistic simulation of a proposed system configuration
A
MOCKUPS
9
Q
The advance of computerized methods must be supported with conventional design documentation methods such as
A
- Design Drawing
- Material and Part List
- Analyses Report
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
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
12
Q
assist in the verification of technical concept and system design approaches.
A
System Prototype Development
13
Q
Comprehensive analysis of all the equipment software and any other elements
A
Equipment/ Software Design Review
14
Q
Will be doing after comprehensive analysis of all elements before releasing to the production.
A
Critical Design Review
15
Q
The success of a formal design review is dependent on depth planning, organization, and data preparation
A
Design Review Goal
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
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
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
19
Q
Temperature cycling, shoch and vibration, humidity, sand and dust, salt spray, acoustic noise, explosion proofing and electromagnetic interface.
A
Environmental Qualification
20
Q
Sequential testing, life testing, environmental stress screening and test analyze and fix
A
Reliability Qualification
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
22
Q
Verification of compatibility among prime equipment, test,and support equipment and group handling equipment
A
Support Equipment Compatibility
23
Q
The verification and validation of operating procedures, maintenance procdeures and supporting data
A
Technical Data Verification
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
25
Verification that software meets the system requirement, the compatibility between software and hardware and the appropriate quality provisions have been incorporated.
Software Compatibility
26
It includes the completion of formal test at designed field test sites by user personnel over an extended period of time.
Type III Testing
27
Operating personnel, operational test and support equipment, operational spares, applicable computer software, and validated operating maintenance procedures are used
Type III Testing
28
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
Type IV Testing
29
sino crush ko?
syempre wala chz secret!!!!
30
The first and most important phase of the system design and development process.
CONCEPTUAL DESIGN PHASE
31
should be presented in specific qualitative and quantitative terms and in enough detail to justify progressing to the next step.
Statement of the Problem
32
should be performed with the objective of translating a broadly defined “want” into a more specific system-level requirement.
Need Analysis
33
It is accomplished with the objective of evaluating the different technological approaches that may be considered in responding to the specified functional requirements.
Feasibility Analysis
34
Anticipated time that the system will be in operational use
Operational Life Cycle (horizon)
35
Anticipated usage of the system and its elements
Utilization requirement
36
Effectiveness factors
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
37
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).
Technical Performance Measures (TPMS)
38
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
QUALITY FUNCTION DEPLOYMENT (QFD)
39
It is focused on the voice of the customers and is developed in Japan (1960)
QUALITY FUNCTION DEPLOYMENT (QFD)
40
Preliminary design is also known as
Preliminary Design Phase
41
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
Functional Analysis
42
refers to a specific or discrete action that is necessary to achieve a given objective.
Function
43
Functional Analysis Serves as a basis in the development of the following:
-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
44
this involves a top-down distribution of the quantitative and qualitative criteria through the QFD analysis.
Allocation of Requirements
45
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.
Reliability
46
characteristics of design and installation that reflects the ease, accuracy, safety, and economy of performing maintenance actions.
Maintainability
47
Translates customer requirements into technical requirements
Product Planning
48
Assigns control methods to process characteristics
Process-Control Planning
49
Identifies process steps and parameters and translates them into process characteristics
Process Planning
50
Translates technical requirements into component characteristics
Product Design
51
Identification of the quantity equipment , software, personnel, facilities, and so on, and the expected geographical location to include transportation and mobility requirements.
Operational deployment or distribution
52
Evaluate the most likely candidates in terms of performance, effectiveness, logistics requirements, and life-cycle economic criteria.
Requirements for Feasibility Analysis
53
design and development of a preferred system architecture that will ultimately be responsive to the identified customer need.
Purpose of Conceptual Design
54
from the Greek systema, meaning an "organized whole"
Systems
55
a regularly interacting or interdependent group of items forming a unified whole
Systems
56
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
Systems
57
Key concepts of Systems
Interaction
Whole
Elements
Interrelationships
58
A combination of interacting elements organized to achieve one or more stated purposes.
Engineered System
59
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.
Engineered System
60
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.
Systems Engineering
61
incorporates both technical and management processes.
Systems Engineering
62
"A person who practices systems engineering" whose systems engineering capabilities and experience include sustained practice, specialization, leadership, or authority over SEactivities.
System Engineer
63
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.
Systems Engineer
64
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.
System Engineer
65
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.
System Engineer
66
may mean an engineered system, natural system, a social system, or all three.
System
67
focuses on the domain of the engineered systems (ES).
System engineering
68
treated as a special form of engineered system.
Sociotechnical systems
69
The degree to which a system's design or code is difficult to understand because of numerous components or relationships among components.
Complexity
70
The principle that whole entities exhibit properties which are meaningful only when attributed to the whole, not to its parts.
Emergence
71
is made up of combinations of elements.
System
72
can be divided into a hierarchy of sets of elements that include subsystems, components, subcomponents, and parts.
System
73
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.
Elements
74
set of interrelated components functioning together toward some common objectives) or purpose(s).
System
75
The parts of a system. The operating parts of a system consisting of input, process, and output.
Components
76
the properties (characteristics, configuration, qualities, powers, constraints, and state) of the components and of the system as a whole.
Attributes
77
The purposeful action performed by a system.
Function
78
static parts
Structural components
79
are the parts that perform the processing.
Operating components
80
are the material, energy, or information being altered.
Flow components
81
the color of an automobile
Characteristic
82
the strength of a steel beam
Quality
83
the number and arrangement of bridge piers
Configuration
84
the capacitance of an electrical circuit
Power
85
the maximum speed permitted by the governor of a turbine
Constraint
86
whether or not a person is talking on the telephone
State
87
An example is symbiosis, the association of two
unlike organisms for the benefit of each other.
First order relationships
88
called synergistic, are those that are complementary and add to system performance.
Second-order relationships
89
exists when duplicate components are present for the purpose of assuring continuation of the system function in case of component failure.
Redundancy
90
made up of components, and many components can be broken down into smaller components.
System
91
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.
Subsystem
92
Air Transportation
System
93
Aircraft, terminal, ground support equipment, and controls
Subsystem
94
Equipment items, people, and information
Components
95
everything that remains outside the boundaries of the system
Environment
96
material, energy, and/or information often pass through the boundaries
Input
97
material, energy, and/or information that pass from the system to the environment
Outputs
98
enters the system in one form and leaves the system in another form
Throughput
99
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.
Total System
100
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.
Constraints
101
include those that came into being through natural processes.
Natural systems
102
those in which human beings have intervened through components, attributes, and relationships.
Human-made systems
103
a natural system into which a human-made system has been integrated as a subsystem.
Human-modified system
104
organizations of ideas
Conceptual systems
105
those that manifest themselves in physical form.
Physical systems
106
those that have structure, but without activity (as viewed in a relatively short period of time).
Static systems
107
whose states do not change because it has structural components but no operating or flow components, as exemplified by a bridge.
Static systems
108
Those made up of real components occupying space.
Physical systems
109
exhibits behaviors because it combines structural components with operating and/or flow components.
Dynamic system
110
is one that is relatively self-contained and does not significantly interact with its environment.
Closed systems
111
One that does not interact significantly with its environment.
Closed systems
112
usually exhibit the characteristic of equilibrium resulting from internal rigidity that maintains the system in spite of influences from the environment.
Closed systems
113
allows information, energy, and matter to cross its boundaries.
Open system
114
interact with their environment, examples being plants, ecological systems, and business organizations.
Open systems
115
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.
Open system
116
may involve both the customer (or procuring agency) and the producer (or contractor).
Acquisition Phase
117
may include a combination of contractor and customer for ultimate user) activities.
Utilization Phase
118
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.
Concurrent Engineering
119
guided design is simultaneously responsive to customer needs (i.e., to requirements expressed in functional terms) and to life-cycle outcomes.
Lifecycle
120
should not only transform a need into a system configuration but should also ensure the design's compatibility with related physical and functional requirements.
Design
121
Introduced by Royce in 1970, initially for software development.
Waterfall Process Model
122
a.k.a Sequential Improvement Model
Spiral Process Model
123
Boehm, 1986.
Adapted from Waterfall model
Iterative
Prototyping
Spiral Process Model
124
Risk driven approach for the development of products or system
Spiral Process Model
125
developed by Forsberg and Mooz
"VEE" Process Model
126
This model starts with user needs on the upper left and ends with a user-validated system on the upper right.
"VEE" Process Model
