Midterms Flashcards
(114 cards)
1
Q
From the Greek word “systema”, meaning an organized whole
A
System
2
Q
Came into being though natural processes
A
Natural Systems
3
Q
Those that have been developed by human beings
A
Man-Made Systems
4
Q
Made up of real components occupying space
A
Physical Systems
5
Q
An organization of ideas, a set of specification and plans
A
Conceptual Systems
6
Q
Those that have structure, but without activity
A
Static Systems
7
Q
One that combines structural components with activity
A
Dynamic Systems
8
Q
relatively self-contained and does not significantly interact with its environment
A
Closed System
9
Q
Interact with their environment
Ex. Support Capability
A
Open-Loop System
10
Q
A collection of components systems that produce results unachievable by the individual systems alone.
A
System of Systems (SOS)
11
Q
Parts of the System, elements of which the system is composed
A
Components
12
Q
Properties of the individual components
A
Attributes
13
Q
Between (pairs of) components so that the components interact to support the system’s functionality (common purpose)
A
Relationships
14
Q
Values of the attributes and relationships at a particular moment
A
State
15
Q
A type of components that is static
A
Structural Components
16
Q
Dynamic Components which “do the work”
A
Operating Components
17
Q
Things which change, such as information, energy or material
A
Flow Components
18
Q
Color, strength, size, weight, and power
A
Attribute of Components
19
Q
if 2 hierarchical levels are involved in a given system, the lower is conveniently called subsystem
A
Systems and subsystems
20
Q
Anything outside the system of the boundaries of the system is considered ___
A
Environment
21
Q
An interdisciplinary approach and means to enable the realization of successful systems (INCOSE)
A
Systems Engineering
22
Q
Defined as a methodical, multi-disciplinary approach for the design, realization, technical management, operations, and retirement of a system
A
Systems Engineering
23
Q
That is, we say that a project is delivering a system, or is delivering a product
A
System as a product
24
Q
Systems are much more than just the aggregation of hardware or software products
A
System as a Capability
25
A capability (in systems engineering) is created through the proper and effective interaction of people, process and technology
Capability System
26
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
Logical (Functional) Hierarchy
27
Here we can use a simple 4 - layer (common) representation of a system
Physical Hierarchy
28
Phase where the life cycle begins with the ________ phase with an idea for a system being generated as a result of a business planning
Pre-Acquisition Phase
29
This phase is focused on bringing the systems into being and into the service of the organization
Acquisition Phase
30
The system is operated (also supported) during the _____
Utilization phase
31
This phase could also be a mark of another life cycle
Retirement Phase
32
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
Conceptual Design Phase
33
Articulated and confirmed by the business management
Business Needs and Requirements (BNR)
34
BNR are elaborated by the stakeholders at the business operations level into a set of ______
Stakeholders Needs and Requirements
35
SNR are elaborated by requirements engineering into system requirements in the ________
System Requirements Specifications (SyRS)
36
BNR, SNR, and the SyRS are the key elements to establishing the _________
Functional Baseline (BSL)
37
Conceptual Design ends with the ______
Systems Design Review (SDR)
38
Converts the logical architecture of the initial FBL into descriptions of the physical subsystems (upper-level physical architecture) that will meet system requirements.
Preliminary Design Phase
39
Uses engineering disciplines to develop the individual subsystems, assemblies
Detailed Design & Development
40
Review at the end of this activity is called the ________
Critical Design Review (CDR)
41
Components are produced in accordance with the PBL specifications
Construction and/or Production
42
Major activities in the phase are:
- Operational use
- System support
Utilization and Retirement Phase
43
A linear and sequential approach where each phase (e.g., requirements, design, implementation, testing, deployment) is completed before the next one begins.
The Waterfall Model
44
(an extension of the Waterfall model) where development stages are paired with corresponding testing stages
"V" Model
45
Well-suited for projects where requirements are expected to evolve over time, and where feedback and refinement are critical to achieving the desired outcomes.
The Iterative Model
46
Emphasizes iterative development, strong focus on risk management and flexibility
Spiral Model
47
Completed and accurate definition is fundamental to project success.
Requirements Engineering
48
is required so that design decisions can be traced from any given system-level requirements down to a detailed design decision
Forward Traceablity
49
any lower-level requirement is associated with at least one higher level requirements
Backward traceability
50
Assures the customer that all requirements can be accounted for in the design at any stage
Traceability
51
Systems Engineering maintains a life-cycle focus as decisions are made
Life Cycle Focus
52
Systems Engineering is looking for optimal system-level performance.
System Optimization and Balance
53
Systems Engineering integrates a diverse range of technical disciplines and specializations
Integration of Specializations/Disciplines
54
Systems Engineering clearly has a technical role but also needs to have a very important management role.
Management
55
We concentrate on the intent and main aim of each application of this foundation process
Systems Engineering Processes
56
Oversees the systems engineering process
Systems Engineering Management
57
Tools are available to help managers and process people undertake their tasks
Systems Engineering Tools
58
Technical and non-technical disciplines are related to systems engineering
Related Disciplines
59
Systems Engineering relies on the continual application of the simple problem-solving process of ______, _______, and ________
Synthesis, Analysis, and Evaluation
60
Commences with the perceived need for the system
Analysis
61
the "design" and "creation" functions
Synthesis
62
________ is performed throughout its life-cycle:
Evaluation
63
The basic analysis - synthesis - evaluation loop is applied iteratively throughout the system life cycle
Systems Engineering Process
64
Elements are attributed to the source and are normally gathered via interview or workshop
Elicitation
65
Entails breaking a higher-level requirements into those lower-level requirements that are explicitly required by it.
Decomposition
66
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
Derivation
67
_______ and ________ are not for novices and require requirements engineers (or business analysis) to understand
Elicitation/Elaboration
68
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)
Requirements
69
Something that the system should do or provide
Functional Requirement
70
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
Non-functional requirement
71
The first and most important phase of the system design and development process
Conceptual System Design
72
Given that identified need for a system, the next stage of system planning and architecting can be initiated called the Program Management Plan (PMP)
System Planning and Architecting
73
Identify various system-level design alternatives that could be pursued in response to the need
System Design and Feasibility Analysis
74
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
System Operational Requirements
75
Identification of the prime and secondary (alternative) missions of the system
Mission Definition
76
Definition of the operating characteristics and functions (size, weight, speed, range, accuracy, flow rate, capacity, transmit, receive, throughput etc.)
Performance and Physical Parameters
77
Identification of the quantity of equipment, software, personnel, facilities, (and so on) and the expected geographical location to include transportation and mobility requirements
Operational Deployment and Distribution
78
Anticipated time that the system will be in operational use
Operational life cycle (horizon)
79
Anticipated usage of the system and its elements
Utilization requirements
80
System requirements specified as figures-of-merit (FoMs)
Effectiveness factors
81
Definition of the environment in which the system is expected to operate
Environmental factors
82
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
System Maintenance and Support
83
Include corrective and preventive maintenance
Levels of maintenance
84
dictate that an item (in the event of failure) is nonrepairable, partially repairable, or fully repairable.
Repair Policies
85
may be responsibility of the customer, producer (supplier), or a third-party
Organizational responsibilities
86
Criteria must be established for the various elements of maintenance support
Maintenance Support Elements
87
Consist of the effectiveness factors associated with the support capability
Effectiveness requirements
88
This includes temperature, shock and vibration, humidity noise, arctic vs tropical environment, mountainous vs flat terrain, shipboard vs ground conditions
Environment
89
The objective here is to derive the overall performance goals (and be clear) as to which the system must be designed.
Technical Performance Measures
90
Team approach to help ensure that the voice of customer is reflected in the ultimate design
Quality Function Deployment
91
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
Functional Analysis and Identification
92
At this point, decisions must be made regarding:
System Trade off Analysis
93
The results from the previous activities are used to establish the specific "design-to" requirements for the system (the ultimate objective of this stage)
System Specifications
94
Design information is released and reviewed for compliance with the basic system-equipment requirements.
Conceptual Design Review
95
Causality driven, holistic approach to describing the interactive relationships between components inside a system as well as influences from outside the system
Systems Thinking
96
Methodology used to study the behavior of complex systems over time
System Dynamics
97
Refers to how key variables in a system change over time
System Behavior
98
When an initial quantity of something starts to grow, and the rate of growth increases
Exponential Growth
99
When the quantity of interest starts either above or below a goal level and over time moves towards the goal
Goal-seeking behavior
100
When initial exponential growth is followed by goal-seeking behavior, which results in the variable leveling off
S-shaped Growth
101
When the quantity of interest fluctuates around some level
Oscillation
102
Snapshot of all relationship that matter
Causal Loop Diagrams
103
Components of system that can change overtime
Variables
104
Links between variables are the verbs in the system
Links
105
Reinforcing loop is a loop that amplifies changes in system
Feedback loop
106
Shows relationship among variables which have the potential to change overtime
Stocks and Flow Diagrams
107
Accumulation of stuff, either concrete, such as dollars or groundwater that can increase or decrease overtime
Stock
108
Describes actions or processes that transport stuff
Flow
109
Holds information about the system that affects rate of flows or affects value of another converter
Converter
110
Moves information from one elements to another
Connector
111
Can be represented within flow/rate equations or as a distinct item in stocks and flow diagram
Constant
112
Stocks that lie outside of the model's boundary
Sources and links
113
Commonly occurring combination of reinforcing and balancing feedback
System Archetypes
114
A focused methodology for carefully listening to the voice of the customer (VOC)
Quality Function Deployment
