Lesson 1 & 2 Flashcards
Meaning of the Greek word “systema”
Organized whole
A regularly interacting or independent group of item forming a unified whole
Systems
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
A combination of interacting elements organized to achieve one or more stated purposes
Engineered System
Specialization of system which fullfils the basic properties of all systems, but which is explicitly man-made, contains technology, exists for purpose and is engineered through a series of managed life cycle activities to make it better able to achieve that purpose.
Engineered System
Interdisiplinary, collaborative approach to the engineering of systems (of any type) which aims to capture stockholder needs and objectives ad to transform these into a description of holistic, life-cycle balanced system solution which both satisfies the minimum requirements and optimizes overall project and system effectiveness according to the values and the stakeholders.
Systems engineering
Incorporates both technical and management process.
Systems engineering
A person who practices systems engineering
Systems Engineer
Supports the life cycle process beginning early in conceptual design and continuining throughput the lifecycle of the system through its manufacture, deployment, use, and disposal.
Systems Engineer
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.
Systems Engineer
Helps ensure the elemets 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
Systems Engineer
(In broad community) may mean an engineered system, a natural system, a social system, or all three.
System
Focuses on the domain of the engineered system (ES)
Systems engineering
Treated as a special form of engineered system
Sociotechnical systems
The degree to which a system’s design or code is difficult to understand because of the numerous components or relationships among components
Complexity
The principle that whole entities exhibit properties which are meaningful only when attributed to the whole, not to its parts
Emergence
Made up of combination of elements
System
Building blocks of a systems and are not just hardware but can also include software, and can even include personnel, facilities, policies, documents, and data bases
Elements
Divided into a hierarchy of sets of elements that include subsystems, components, subcomponents, and parts
System
Set of interrelated components functioning together toward some common objective(s) or purpose(s).
System
Parts of a system. the operating parts of a system consisting of input, process, and output.
Components
Properties (characteristics, configuration, qualities, owners, constraints, and state) of the components and of the system as a whole
Attributes
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(s).
Relationships
Purposeful action performed by a system
Function
Common system function is that of _____ material, energy, or information
Altering
Embraces input, output, process
Alteration
Static parts (systems that alter)
Structural components
Parts that perform the processing (systems that alter)
Operating components
Material, energy, or information being altered (systems that alter)
Flow components
Symbiosis, association of two unlike organisms for the benefit of each other
First order relationships
Synergistic, those that are complementary and add to system performance
Second-order relationships
Exists when duplicate components are present for the purpose of assuring continuation of the system function in case of component failure
Redundancy
The lower system, if two hierarchical level are involved in a given system
Subsystem
Everything that remains outside the boundaries of a system
Environment
Material, energy, and/or information often pass through the boundaries
Inputs
Material, energy, and/or information that pass from the system to the environment
Outputs
Enters the system in one form and leaves the system in another form
Throughput
At whatever level in the hierarchy, consists of all components, attributes and relationships needed to accomplish one or more objectives
Total System
(Placed on the system) limit its operation and define the boundary within which it is intended to operate.
Constraints
Include those that came into being through natural processes
Natural Systems
Those in which human beings have intervened through components, attributes, and relationships
Human-made systems
Natural system into which a human-made system has been integrated as a subsystem
Human-modified systems
An organizations of ideas
Conceptual systems
Are those that manifest themselves in physical form. Those made up of real components occupying space
Physical systems
Those that have structure, but without activity (as viewed in a relatively short period of time)
Static systems
One whose states do not change because it has structural components but no operating or flow components, as exemplified by a bridge
Static systems
Exhibit behaviors because it combines structural components with operating and/or flow components
Dynamic systems
One that is relatively self-contained and does not significantly interact with its environment
Closed systems
Usually exhibit the characteristic of equilibrium resulting from internal rigidity that maintains the system in spite of influences from the environment
Closed systems
Only provides a context for the system
Environment
Allows information, energy, and matter to cross its boundaries.
Open systems
Interact with their environment; exhibit the characteristics of steady state, wherein a dynamic interaction of system elements adjusts to changes in the environment.
Open systems
Self-regulatory and often self-adoptive
Open systems
May involve both the customer (or procuring agency) and the producer (or contractor)
Acquisition Phase
May include a combination of contractor and customer (or ultimate user) activities
Utilization Phase
Systematic approach to creating 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
Simultaneously responsive to customer needs and to life-cycle outcomes
Life cycle - guided design
Introduced by Royce in 1970, initially for software development
Waterfall Process Model
Collect information and data (waterfall model)
Requirement Analysis
Feasibility; specify if software is doable or not (waterfall model)
Specifications
Defines architecture of the project (WM)
Design
Focus on the models (flowchart, flow diagram, decision tree)(WM)
High Level Design (HLD)
Focus on components (WM)
Low Level Design (LLD)
Must work on the encoding of the project (WM)
Implementation
Testing th functionality (WM)
Test
Bug-free or error-free, deployment of system (WM)
Deployment/Installation
Includes error correction/to value the software overtime (WM)
Maintenance
Boehm, 1986; Adopted from waterfall model; Iterative; Prototyping; Risk driven approach for development of products or system
Spiral Process Model
Includes planning process, tasks, resource defining, team planning, estimation of cost, schedules (SPM)
Planning
To overcome the problems and risk (technical and management risks) (SPM)
Risk Analysis
Done by engineers and developers (all coding, testing, and developing of software takes place) (SPM)
Engineering and Execution
Product is assessed by the client (inclides all the above phases) (SPM)
Evaluation
Forsberg and Mooz; this model starts with user needs on the upper left and ends with a user-validated system on the upper right
Vee Process Model
Foundation of the entire system design
Conceptual Design Phase (CDP)
The first and most important phase of the system design and development process.
Conceptual Design Phase (CDP)
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 systems and its product(s).
Conceptual Design Phase (CDP)
Should be presented in specific qualitative and quantitative terms and in enough detail to justify progressing to the next step.
Statement of the Problem
Generally commences woth the identification of a “want” or “desire” for something based on some “real” deficiency.
System Engineering Process
Should be performed with the objective of translating a broadly defined “want” into more specific system-level requirement.
Need Analysis
It is accomplished with the objective of evaluating the different technological approaches that may be considered in responding to the specified functional requirements
Analysis/Feasibility Analysis
What are the three things to be considered in Analysis Feasibility Analysis
Access Technical Requirement, Potential User (Market), Legal Consideration
The prime mission of the system and alternate or secondary missions.
Mission Definition
The operating characteristics or functions of the system such as size, weight, range, accuracy, bits, capacity, transportation, receive, etc.
Performance and Physical Parameters
The quantity of equipment, software, personnel, facilities, and so on, and the expected geographical locationn to include transportation and mobility requirements
Operational Deployment or Distribution
Anticipated time that the system will be in operational use
Operational Life Cycle
Anticipated usage of the system and its elements (e.g., hours of operation per day, percetage of total capacity, operational cycles per month, facility loading, etc.)
Utilization Requirement
System requirements specified as (Cost/system effectiveness, Operational availability, Readiness rate, Dependability, Logistics support effectiveness, Mean time between maintenance (MTBM), Failure rate, Maintenance downtime (MDT), Facility utilization, Operator skill levels, Task accomplishment requirements, Personnel efficiency)
Effectiveness Factors
The system is expected to operate (e.g., temperature, humidity, arctic or tropics, mountainous or flat terrain, airborne, ground, shipboard, etc.)
Environment
Should include a range of values as applicable and should cover all transportation, handling, and storage modes.
Environment
May be applied as “design-to” criteria for the prime, the maintenance, and logistics support.
Technical Performance Measures (TPMs)
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)
A structured process or mechanism for determining customer requirements and transporting them into relevent technical requirements that each functional area and organization level can understand and act upon.
Quality Function Deployment (QFD)
Reflects the needs and wants of the customer, Starting point of desiging products and processes
Voice of Customer (VOC)
Translates customer requirements into technical requirements
Product Planning
Translates technical requirements into component characteristics
Product Design
Identifies process steps and parameters and translates them into process characteristics
Process Planning
Assigns control methods to process characteristics
Process-Control Planning
The most critical step in the system
Preliminary Design Phase
It is also known as advance development
Preliminary Design Phase
It extends the translation of system level requirement into design requirements for the subsystem level
Preliminary Design Phase
Refers to a specific or discrete action that is necessary to achieve a given objective
Function
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
Serves as a basis in the development of the following: reliability models and block diagram, Fault-tree analysis, System safety/hazard analysis, maintainability analysis, level-of-repair analysis, supportability analysis, and etc.
Functional Analysis
Given the identification of the system elements, the next step id to ___________ or apportion the requirements specified for the system down to the level desired to provide a meaningful input design.
Allocate
This involves a top-down distribution of the quantitative and qualitative criteria through the QFD analysis.
Allocation of Requirements
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
This technique is a straightforward method that assigns equal reliability requirements for all subsystems based on the system requirements.
Equal Apportionment Technique
The failure rate for the system is first determined and then previous history or other estimation methods are used to provide a weighing (WI) for each subsystem to determine what the individual subsytem failure rate must be to achieve the system reliability requirement.
ARINC Apportionment Technique
Characteristic of design and installation that reflects the ease, accuracy, safety, and economy of performing maintenance actions
Maintainability
Detail design baseline derived during preliminary design
Detail Design and Development Phase
Overall system and its major subsystems in hand, one may proceed to the realizaton of specific system components
Detail Design and Development Phase
The design team has been established with the overall objective of integrating the various system elements into a final system configuration
Evolution of Detail Design
The application of computer-aided engineering (CAE) and computer-aided design (CAD) enables the projection of many different design alternatives throughout the life cycle.
Detail Design Tools and Aids
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
The objective is to accomplish a specified amount of testing for the purpose of design evaluation prior to entering a formal test and evaluation phase.
System Prototype Development
The purpose is to assist in the verification of technical concepts and various system design approaches. Areas of noncompliance with the specificied requirements are identified and corrective action is initiated as required.
System Prototype Development
Comprehensive analysis of all of the equipment, software, and any other elements.
Equipment/Software Design Review
Generally, will be doing after comprehensive analysis of all the elements, before releasing to the production.
Critical Design Review
The success of a formal design review is dependent on depth planning, organization, and data preparation
Design Review Goal
Initially establish during the conceptual design phase of life cycle, preferably in parallel with the definition of the overall design requirements for the system
System Test, Evaluation, and Validation
The examination and assessment of a system in terms of worth, quality of performance, degree of effectiveness, anticipated cost and so on.
System Test, Evaluation, and Validation
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
It refers primarily to the evaluation of system components in the laboratory using engineering beadboards, bench test models, service test modules, rapid prototyping, and the like
Type I Testing
Temperature cycling, shock and vibration, humidity, sand, and dust, salt spray, acoustic noise, eplosion proofing, and electromagnetic interface.
Environmental Qualification
Sequential testing, life testing, environmental stress screening (ESS) and test, analyze, and fix
Reliability Qualification
Verification of maintenance tasks, tasks 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
verification of the compatibility among the prime equipment, test and support equipment, and ground handling equipment
Support Equipment Compatibility
The verification and validation of operating procedures, maintenance procedures, and supporting data.
Technical Data Verification
Verification to ensure the compatibility among the human and equipment, the personnel quantities and skill level required, and training needs
Personnel Test and Evaluation
Verification that software meets the system requirements, the compatibility between software and hardware, and that the appropriate quality provisions have been incorporated
Software Compatibility
It includes the completion of formal tests at desgined 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 III Testing
It is conducted during the system operational use and life-cycle support phase, includes formal tests that are sometimes conduced to acquire specific information relative to some area of operation or support.
Type IV Testing
