Se Flashcards
(123 cards)
1
Q
From the Greek word “systema” means “organized whole”
A
System
2
Q
A regularly interacting or interdependent group of items forming a unified whole
A
System
3
Q
A combination of interacting elements organized to achieve one or more stated
purposes
A
Engineered System
4
Q
It is 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
5
Q
Is an interdisciplinary, collaborative approach to the engineering of systems
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
6
Q
Incorporated both technical and management processes
A
Systems Engineering
7
Q
They must analyze, specify, design, and verify the system to ensure that its
functional, interface, performance, physical, and other quality characteristics,
and cost are balanced to meet the needs of the system stakeholders
A
Systems Engineering
8
Q
They 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
Systems Engineering
9
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
10
Q
The principle that whole entities exhibit properties which are meaningful only
when attributed to the whole, not to its parts
A
Emergence
11
Q
Building blocks of a systems and contains hardware, software, personnel,
facilities, policies, documents, and databases
A
Elements
12
Q
made up of combinations of elements
A
System
13
Q
can be divided into a hierarchy of sets of elements, that include subsystem,
components, subcomponents, and parts
A
System
14
Q
Elements of a System
A
Components
- Attributes
- Relationships
15
Q
is a set of interrelated components functioning together toward some common
objectives or purposes
A
System
16
Q
operating parts of the systems contains input, process, and output
A
Components
17
Q
properties (characteristic, configuration, qualities, powers, constraints, and state)
of the components and of the system as a whole
A
Attributes
18
Q
between pairs of linked components are the result of engineering the attributes
of both components so that the pair operates together effectively in contributing
to the system’s purpose
A
Relationship
19
Q
Systems Components
A
Structural Components
- Operating Components
- Flow Components
20
Q
Always start using ______or _______
A
Data
Information
21
Q
Advantages of Concurrent Engineering
A
- This model is applicable to all types of
software development processes - It is easy to understand and use
- It gives immediate feedback from testing
- Provides an accurate feature of the
current state of a project
22
Q
Advantage of Waterfall Process Model
A
- This model is simple and easy to
understand and use - It is easy to manage due to its phase has
specific deliverables and review process - Waterfall model works well for smaller
projects where requirements are clearly
define
and very well understood
23
Q
Disadvantage of Waterfall Process Model
A
- No working software is produced until
late during the life cycle - Poor model for long and ongoing projects
- High amounts of risks and uncertainty
- It’s not a good model for complex and
object oriented projects
24
Q
collects the information, help of SRS, CRS, BRS software, customer, business
requirements specifications
A
Requirements Analysis
25
Feasibility Study, high level people analyze whether the project is doable or not.
Considers economic, operation, technical, schedule
Specification
26
architecture of the project. Uses HLD (flowchart, decision tree), LLD
(Components), high and low level design Implementation
- coding, Uses program
language such java, phyton
Design
27
function, according to the requirements of customers or clients Installation
- if the system is bug free or virus free
Test
28
error correction, enhancement of capabilities, optimization
Maintenance
29
Waterfall Process Model
1. Requirements Analysis
2. Specification
3. Design
4. Test
5. Maintenance
30
Advantages of Spiral Model
1. It provides continuous and repeated
development which helps in risk
management
2. It provides the past development and the
futures are added in a systematic manner
3. Clients get the opportunity to see the
software or products after every cycle
4. It is the most preferable model for large
and complex projects or software
31
Disadvantages of Spiral Model
1. Spiral models are expensive due to the
high level of expertise required for risk
analysis
2. The spiral model is not suited for small
projects
3. The overall success of the project
depends on the risk analysis phase
32
System relationships
1. first order relationship
2. second-order relationships
3. redundancy
33
Association of two systems that benefit each other An example is symbiosis
First order relationship
34
called synergistic, are those that are complementary and add to system
performance
Second order relationship
35
exists when duplicate components are present for the purpose of assuring
continuation of the system function in case of component failure.
Redundancy
36
a lower system, if two hierarchical levels are involved in a given system
subsystem
37
are the parts that perform the processing
Operating components
38
four system limits, boundaries or scope
1. environment
2. inputs
3. outputs
4. throughput
39
everything that remains outside the boundary of a system
Environment
40
materials, energy, information often pass through the boundaries
Input
41
material, energy, information that pass from the system to the environment
Output
42
enters the system in one form and leaves the system in another
Throughput
43
are the material, energy, or information being altered
Flow components
44
at whatever level in the hierarchy, consists of all components, attributes, and
relationships needed to accomplish one r more objectives.
Total system
45
purposeful action performed by a system
Function
46
limits an operation of a system and define the boundary within which it is
intended to operate
Constraints
47
Classification of system
Natural system
- human-made system
- human modified system
- conceptual system
- physical system
- static system
- dynamic system
- closed system
- open system
48
Include those that came into being through natural processes
Natural system
49
Are those in which human beings have intervened through components
attributes and relationships
Human made system
50
Is a natural system into which a human made system has been integrated as a
subsystem
Human modified system
51
Are organizations of ideas
Conceptual system
52
Are those that manifest themselves in physical form those made up of real
components occupying space
Physical system
53
Those that have structure but without activity as viewed in a relatively short
period of time
Static system
54
Is one whose states do not change because it has a structural components but no
operating or flow components as exemplified by a bridge
Static system
55
Exhibits behaviors because it combines structural components with operating
and or flow components
Dynamic system
56
Is one that is relatively self contained and does not significantly interact with its
environment
Closed system
57
Allows information energy and platter to across its boundaries. It interacts with
their environment example being plants ecological systems and business
organizations
Open system
58
The product life cycle
Acquisition phase
- utilization phase
- design phase
- startup phase
- operation phase
- retirement phase
59
It may involve both the customer or procuring agency and the producer or
contractor
Acquisition phase
60
It may include a combination of contractor and customers (or ultimate user)
activities
Utilization phase
61
Is a systematic approach to creating a system design to simultaneously considers
all phases of all the life cycle from conception through disposal to include
consideration of production distribution maintenance phase out and so on
Concurrent engineering
62
____ should not only transform a need into a system configuration but should
also ensure the designs compatibility with related physical and functional
requirements
Design
63
Introduced by Royce in 1970 initially for software development
Waterfalls process model
64
It was introduced by boehm 1986 which is adapted from waterfall model
Spiral process model
65
It is a risk driven approach for the development of products or system
Spiral process model
66
It is a model introduced by Forsberg and Mooz
Vee process model
67
This model starts with user needs on the upper left and ends with a user
validated system on the upper right
Vee process model
68
Four stages of spiral processing model
Planning
risk analysis
engineering and execution
evaluation
69
first and most important phase of the system design and development process
Conceptual design phase
70
it is an early and high-level life-cycle activity with the potential to establish,
commit, and otherwise predetermine the function, form, cost, and development
schedule of the desired system and its products
Conceptual design phase
71
it should be performed with the objective of translating a broadly defined "want"
into a more specific system-level requirement
Need analysis
72
A 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
73
System Operational Requirements
1. Mission
2. Performance or physical parameters
3. Operational deployment or distribution
4. Operational life cycle
5. Utilization requirement
6. Effectiveness factors
7. Environment
74
Translates customer requirements into technical requirements
Product planning
75
Translates technical requirements into component characteristics
Product design
76
the systems engineering process generally commmences with the identification
of a "want" or "desire" for something based on some "real" deficiency
Product definition
77
Identifies process steps and parameters and translates them into process
characteristics
Process planning
78
Assigns control methods to process characteristics
Process control planning
79
It extends the translation of system level requirements into design requirements
for the subsystem level
Preliminary design phase
80
It refers to a specific or discrete action that is necessary to achieve a given
objective
Function
81
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
82
Is 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
83
Requirements for Feasibility Anslysis
Identify the various possible design
approaches that can be pursed to meet the
requirements
- Evaluate the most likeley candidates in
terms of performance effectiveness,
logistics requirement, and life-cycle
economic criteria
- Recommend a preferred approach
84
identification of the prime mission of the system and alternate or secondary
mission
Mission definition
85
definition of the operating characteristics or functions of the system such as size,
weight, range, accuracy, bits, capacity, transportation, receive, etc.
Performance and Physical Parameters
86
identification of the quantity of equipment, software, personnel, facilities, and
so on.
expected geographical location to include transportation and mobility
requirements
Operational deployment or distribution
87
anticipated time that the system will be in operational use
Operational life cycle (horizon)
88
percentage of total capacity, operational cycles per month, facility loading, etc.)
Utilization requirements
89
Effectiveness Factors
a) Cost/system effectiveness
b) Operational availability, readiness rate,
dependability
c) Logistics support effectiveness
d) Mean time between maintenance
(MTBM)
e) Failure rate
f) Maintenance downtime (MDT)
g) Facility utilization
h) Operator skill levels
i) Task accomplishment requirements
j) Personnel efficiency
90
Serves as a basis in the development of the following:
- Electrical and mechanical design for functional packaging, condition monitoring
and diagnostics provisions
- Reliability models and block diagram
- FMECA
- FTA
- RCM Analysis
- System safety/ hazards analysis
- Maintainability Analysis
- Level of repair analysis
- MTA
- OTA
- OSDs
- Supportability analysis
- Operating and maintenance procedures
- Functionality and disposability analysis
Functional analysis
91
system is expected to operate (e.g., temperature, humidity, artic or tropics,
mountains, or flat terrain, airborne, ground, shipboard, etc.
Environment
92
Maintenance and Support Concept
1. Maintenance and support planning
2. Supply support (spare/repair parts and
associated inventories)
3. Maintenance and support personnel
4. Training and training support
5. Test, measurement, handling, and
support equipment
6. Packaging, handling,
storage/warehousing, and transportation
7. Maintenance facilities
8. Computer resources (hardware and
software)
9. Technical data, information systems, and
databases structures
93
specific performace-related factors are identified and applied with the objectives
of ensuring that the system will be designed and developed such that it will
satisfactorily accomplish its intended mission
Technical performance measure
94
Technical Performance Measures (TPMs)
Process time (days)
- Velocity (mph)
- Availability (Operational)
- Size (feet)
- human factors
- Weight (pounds)
- Maintainability (MTBM)
95
In a generic sense, can be defined as "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
96
This technique is a straightforward method that assigns equal reliability
requirements for all subsystems based on the system requirements. While being
easy to compute, it lacks the sophistication to discriminate between actual
subsystem reliabilities.
Equal Apportionment Technique
97
is that characteristic of design and installation that reflects the ease, accuracy,
safety, and economy of performing maintenance actions
Maintainability
98
Detail design baseline derived during ________
Preliminary design
99
Steps of Detail Design and Development Phase
1. Definition of system elements
2. Preparation of design data
3. Development of physical models of the
system or major system component
4. Conductance of system integration and
test.
100
Procurement and acquisition of _________ begin, components are combined and
integrated into a next higher assembly, and a physical model of a system is
constructed fortest and evaluation
System Concept
101
The integration, test and evaluation steps constitute a bottom-up activity and
should result in a ________ that can be assessed for a compliance with initially
specified customer requirements
Configuration
102
Enumeration:
Integration of system elements
Hardware,
- Components
- Software
- People
- System Requirements
- Real Estate
- Facilities
- Data/Information
- Consumables
103
As an additional aid to the designer, physical three-dimensional scale models or
_______ are sometimes constructed to provide a realistic simulation of a
proposed system configuration
Mockup
104
A ________ represents the production/construction configuration of a system
(and its elements) in all aspects of form, fit, and function except that it has not
been fully "qualified" in terms of operational and environmental testing
Prototype model
105
The purpose it to assist in the verification and technical concepts and various
system design approaches. Areas of noncompliance with the specified
requirements are identified and corrective action is initiated as required.
System prototype development
106
Enumeration:
Design Documentation methods
design drawings
- Materials and part lists
- Analyses and reports
107
represent a working system or/an element of the system, that will exhibit the
functional performance characteristic define in this specification
Engineering models
108
represents working of element of the system that reflects the end product in
terms of functional performance and physical dimensions
Service test model
109
Enumeration:
Detail Design Reviews
Equipment/Software design Review
- Critical design Review
- design Review Goal
110
comprehensive analysis of all the equipment, software, and any other elements
Equipment/ software design
111
will be doing after comprehensive analysis of all the elements, before releasing to
the production
Critical design review
112
Stages of System Testing and Evaluation
Analytical
- Type I Testing
- Type II Testing
- Type III Testing
- Type IV Testing
113
it pertains to certain design evaluation that can be conducted early in the system
life cycle using computerized techniques to introduce CAD, CAM, CALS,
simulation, rapid prototyping, and related approaches
Analytical
114
it refers primarily to the evaluation of the system components in the laboratory
using engineering breadboards, bench test models, service test models, rapid
prototyping
Type 1 testing
115
Enumeration:
Type 2 Testing
1. Environmental Qualifications
2. Reliability Qualification
3. Maintainability Demonstration
4. Support Equipment Compatibility
5. Technical Data Verification
6. Personnel Test and Evaluation
7. Software Compatibility
116
Evaluation of prototype and production models (production sampling)
Type 2 testing
117
temperature cycling, shock and vibration, humidity, sand and dust, salt spray,
acoustic noise, explosion proofing, and electromagnetic interface
Environmental qualification
118
sequential testing, life testing, environmental stressscreening (ESS), and test,
analyze and fix
Reliability qualifications
119
verification of maintenance tasks, task times and sequences, maintenance
personnel quantities, and skill levels, degree of testability and diagnostic
provisions, prime equipment - test equipment interfaces, maintenance
procedures, and maintenance facilities
Maintainability Demonstration
120
verification that software meets the system requirements, the compatibility
between software and hardware, and that the appropriate quality provisions
have been incorporated
Software compatibility
121
system test and evaluation requirements defined
Conceptual Design
122
it is conducted during the system operational use and life-cycle support phase,
includes formal tests that re sometimes conducted to acquire specific
information relative to some are of operation or support
Type 4 testing
123
have been incorporated
Software compatibility
it includes the completion of formal tests and designed field test sites by user
personnel over an extended period of time. Operating personnel, operational
test and support equipment, operational spares, applicable computer software,
and validated operating and maintenance procedures are used.
Type 3 testing
