Session 1
Overview of Systems Engineering
Module Leader : Dr. Govind R. Kadambi
M S Ramaiah School of Advanced Studies
Session Objectives
To get an overview of Systems Engineering To understand the definition and focus of Systems Engineers To grasp the scope and characteristics of Systems Engineering To get exposure on system design and development To study the role and needs of System Engineering To understand the standard and perspectives of Systems Engineering
M S Ramaiah School of Advanced Studies
Session Topics
Definitions of: System and Systems Engineering Focus and Scope of systems Engineering Characteristics of Systems Engineering Development Activities of Systems Engineering Systems Engineering Process Systems Design Process System Development Model Systems Engineering and Product Development Standards and Perspectives of Systems Engineering Need and role of Systems Engineering Building Blocks of Systems Engineering Contributions of Systems Engineering
M S Ramaiah School of Advanced Studies
3
What is a System?
Definition of a System (NASA Systems Engineering Handbook) A system is a set of interrelated components which interact with one another in an organized fashion toward a common purpose System components may be quite diverse Persons and Organizations Software and Data Equipment and Hardware Facilities and Materials Services and Techniques
M S Ramaiah School of Advanced Studies
4
What is a System?
A purposeful collection of inter-related components working together towards some common objective A system may include software, mechanical, electrical and electronic hardware and be operated by people System components are dependent on other system components The properties and behaviour of system components are inextricably inter-mingled
M S Ramaiah School of Advanced Studies
5
Systems Engineering & Component Engineering
Science Determines what Is Component Engineering Determines what Can Be Systems Engineering Determines what Should Be
M S Ramaiah School of Advanced Studies
Systems Engineering
Definition of Systems Engineering (NASA SE Handbook)
Systems Engineering is a robust approach to the design, creation, and operation of systems.
Systems Engineering consists of
Identification and quantification of system goals Creation of alternative system design concepts Performance of design trades Selection and implementation of the best design (balanced and robust) Verification that the design is actually built and properly integrated in accordance with specifications Assessment of how well the system meets the goals
M S Ramaiah School of Advanced Studies
7
What is Systems Engineering ?
System Thinking A certain objective is given ; to find ways and means for its realisation requires the system specialist (or team of specialists) to consider alternative solutions and to choose those offering optimisation at maximum efficiency and minimum cost in a tremendously complex network of interactions von Bertalanffy, 1973
M S Ramaiah School of Advanced Studies
8
Systems Engineering?
M S Ramaiah School of Advanced Studies
What is Systems Engineering?
M S Ramaiah School of Advanced Studies
10
Focus of Systems Engineering
Need
From Original Need To Final Product
What needs are we trying to fill? What is wrong with the current situation? Is the need clearly articulated? Who are the intended users? How will they use our products? How is this different from the present?
The Whole System The Full System Life Cycle
Operations Concept
Functional Requirements What specific capability will we provide?
To what level of detail? Are element interfaces well defined?
System Architecture
What is the overall plan of attack? What elements make up the overall approach? Are these complete, logical, and consistent? Which elements address which requirements? Is the allocation appropriate? Are there any unnecessary requirements? Are the details correct? Do they meet the requirements? Are the interfaces satisfied? Will the solution be satisfactory in terms of cost and schedule? Can we reuse existing pieces? What is our evidence of success? Will the customer be happy? Will the users needs be met?
Allocated Requirements
Focus of Component Engineering
On Detailed Design And Implementation
Detailed Design
Implementation
Test & Verification
M S Ramaiah School of Advanced Studies
11
Systems Engineering
M S Ramaiah School of Advanced Studies
12
Systems Engineering
M S Ramaiah School of Advanced Studies
13
Scope of Systems Engineering
System Engineers are competent in both technical leadership and Systems Management Good System Engineers should have knowledge and experience of all phases System Engineers often focus on one life cycle like architecture and design versus development or operation
M S Ramaiah School of Advanced Studies
14
Characteristics of Systems Engineers
M S Ramaiah School of Advanced Studies
15
Development Activities of Systems Engineers
M S Ramaiah School of Advanced Studies
16
Beneficial Approach for Systems Engineers
M S Ramaiah School of Advanced Studies
17
System Engineering Process
Requirements definition System design Sub-system development System integration System installation System decommissioning System evolution
M S Ramaiah School of Advanced Studies
18
System Design Process
Partition requirements Identify sub-systems
Define sub-system interfaces Specify sub-system functionality Assign requirements to sub-systems
M S Ramaiah School of Advanced Studies
19
Vee Model of System Development
User Requirements & Concept of Operations System Demonstration & Validation
Systems Engineering Domain
System Requirements & Architecture
System Integration & Test
Component Design
Component Integration & Test
Procure, Fabricate, & Assemble Parts
Component Engineering Domain
M S Ramaiah School of Advanced Studies
20
Why Systems Engineering?
M S Ramaiah School of Advanced Studies
21
Balance of Design Effort
M S Ramaiah School of Advanced Studies
22
Risk and Effort Throughput
M S Ramaiah School of Advanced Studies
23
Time Estimate
Estimates become progressively more accurate in the project life cycle Most significant of all decisionswhether or not to start the projectis made in the beginning
M S Ramaiah School of Advanced Studies
24
Opportunity Curve
M S Ramaiah School of Advanced Studies
25
Systems Engineering Contributions
Systems Engineering brings two elements to a project that are not usually present A disciplined focus on the end product, its enabling products, and its internal and external operational environment (i.e., a System View) A consistent vision of stakeholders expectations independent of daily project demands (i.e., the Systems Purpose)
M S Ramaiah School of Advanced Studies
26
Systems Engineering in Product Development
Integrates Technical Effort Across the Development Project
Systems Engineering
Chem Engrg Mech Engrg Civil Engrg Processes
27
Systems Engineering
Maintainability Environment Producibility Reliability
Systems Engineering
Communications Computers Structures Avionics
Safety
M S Ramaiah School of Advanced Studies
SW Engrg
Functional Disciplines Technology Domains Specialty Concerns
Elec Engrg
Building Blocks of Systems Engineering
Math & Physical Sciences Qualitative modeling Quantitative modeling Physical modeling Theory of Constraints Physical Laws Management Sciences Economics Organizational Design Business Decision Analysis Operations Research Social Sciences Multi-disciplinary Teamwork Organizational Behavior Leadership
Body of Knowledge Problem definition Concept of operations System boundaries Objectives hierarchy Originating requirements Concurrent engineering System life cycle phases Integration/Qualification Architectures Functional/Logical Physical/Operational Interface Trades Concept-level Risk management Key performance parameters
Unique to Systems Engineering
M S Ramaiah School of Advanced Studies
28
Ethical Considerations
Achieving Balance Between Inherent Conflicts System Functionality and Performance Development Cost and Recurring Cost Development Schedule (Time to Market) Development Risk (Probability of Success) Business Viability and Success
System Optimization Subsystems often suboptimal to achieve best balance at system level Ultimate system purpose must prevail against conflicting considerations Long-term considerations (e.g., disposal) may drive technical decisions Customer Interface Often must act as honest broker Carries burden of educating customer on hard choices Must think ahead to the next customer and next application Must challenge all requirements
M S Ramaiah School of Advanced Studies
29
Two Perspectives on SE
SE is a way of thinking Practiced by senior Engineers with OJT Is unique to the Product/industry of the engineering firm Should be taught within other engineering disciplines Scientific foundations and body of knowledge have commonality across product/industry but are not unique to SE SE team has engineers of all disciplines
M S Ramaiah School of Advanced Studies
30
SE is a discipline of engineering Has scientific foundations that cross many other engineering disciplines Has body of knowledge separate from other disciplines Can be taught separately from other disciplines in an engineering school Separate roles exist on the SE team for a specific product
Systems Engineering as an Engineering Discipline
Scientific Foundations Qualitative modeling Data modeling Process modeling Quantitative modeling Behavioral modeling Feedback and control Utility modeling Trade-off modeling Physical modeling Prototypes for requirements Usability testing Prototypes for interface resolution Integration/qualification
Body of Knowledge Problem definition Concept of operations System boundaries Objectives hierarchy Originating requirements Concurrent engineering System life cycle phases Integration/Qualification Architectures Functional/Logical Physical/Operational Interface Trades Concept-level Risk management Key performance parameters
31
M S Ramaiah School of Advanced Studies
Waterfall Diagram (Boehm)
A series of discrete events - originally proposed for software
User Reqmts Specified in problem terms Syst. Reqmts Often specified in functional terms Basic system structural design Design Produce or buy the sub-systems or components Detailed design Manufacture Integration Acceptance
32
Architecture
Assembly, Integration and Verification by the supplier
Validation and Acceptance for operation by the user
M S Ramaiah School of Advanced Studies
System Partitioning and Integration
User Reqmnts User tests Acceptance
System Reqmnts
System tests Integration tests
Verification
Architect. design
Assembly
Sub-system Sub-systems Detailed design tests Manufacture
M S Ramaiah School of Advanced Studies
33
Implications of System Hierarchy
One mans sub-system is another mans system These two people have a common interface But not necessarily a common understanding or purpose They may have very different perspectives and priorities. Interfaces are essential elements in systems engineering Interfaces between the sub-systems within a system Interfaces between the system and its environment This forms a good part of the Requirement Specification Controlling system interfaces - the key to systems engineering But it often gets less attention than the sub-systems themselves
M S Ramaiah School of Advanced Studies
34
Why is Systems Engineering Needed ?
Definition - difficult to define the system boundary and to ensure that everyone works with the same definition Size - more than a single headful Modern systems are too big for a single person to understand and must be divided into manageable chunks Complexity - multidisciplinary technologies Systems Engineers need to deal with a variety of experts Convergence - multi-functionality is commonplace What used to be separate systems are now knit tightly together Commercial sophistication and global industries Engineers must relate to managers, accountants and financiers
M S Ramaiah School of Advanced Studies
35
Roles of Systems Engineers
Creating the right design for the right system
This involves two separate and different tasks or functions These two functions need different Systems Engineering skills
1. Design the right system - the need to keep options open
All acceptable options must be identified and evaluated Options must be kept open to compare possibilities Needs brainstorming, an open mind, a wide experience
2. Design the system right - the need to close off options
Must converge on an acceptable solution and make it work Needs attention to detail, a logical mind, a sound experience
The skill is in knowing how many options to consider
which requires deciding when and why to close off options
Both tasks need full understanding of the requirement
M S Ramaiah School of Advanced Studies
36
Who Needs Systems Engineering Education?
Systems Engineering is needed to generate the best solution to a problem The more complex the system, the greater the need and the greater the number of stakeholders and constraints The concept of Customer and Supplier domains The customer owns the problem, the supplier provides the solution A contract is the interface specification between these two domains All stakeholders are increasingly realising the need for Systems Engineering expertise Customers in order to specify appropriate system requirements Suppliers in order to design appropriate system solutions Other stakeholders in order to understand the system issues
M S Ramaiah School of Advanced Studies
37
What Systems Engineers Need to Know?
Systems Engineering is multi-disciplinary and over-arching it transcends the single subjects in both engineering and management Systems Engineers need sound knowledge of all the engineering, management and political issues that can affect their systems Engineering Systems Engineering Principles Factors Multi-Variate Optimisation System Modeling and Design Manufacturing Methods Reliability and Logistics Risk Management Information Systems Management Economic and Political Social Environment Management Methods Investment Appraisal Accounting and Budgeting Law and Contracts Communication Skills
38
M S Ramaiah School of Advanced Studies
Session Summary
Systems Engineering
Has Unique Focus
End product and system purpose Stakeholder needs and expectations Full system life cycle (Conception through Retirement)
Has Unique Approach
Integrates disciplines and technologies Balances conflicting considerations
Has Unique Methods, Tools & Models for
System analysis and simulation Assessment of performance and risk Organization and management of information and requirements Verification and validation
M S Ramaiah School of Advanced Studies
39
Session Summary
Systems Engineering an Engineering Discipline Skills and Problems Not Unique But Unique Mixture of Skills and Problems Growing SE Academic Community Houston, SMU, Texas Tech MIT, Rochester Inst. Of Tech., Stevens Inst. Of Tech. Growing Body of Knowledge Books SE Journal and Conferences Standards Students Pursue Degrees in SE Engineers Pursue Job Titles in SE Engineering Firms Pursue Engineers that Think at the System Level
M S Ramaiah School of Advanced Studies
40
Session Summary
Systems Engineering Education endeavours to Enable students to recognise all aspects of problems and Solutions Surmount barriers between different disciplines and cultures Equip people to manage and engineer major projects Successfully It can be taught at first degree and postgraduate levels But must be treated according to student experience and can only be taught in depth to practising engineers Postgraduate Systems Courses are often sponsored By companies that recognise the need for systems engineers Syllabuses are tailored to specific systems disciplines Students are encouraged (and paid) to attend
M S Ramaiah School of Advanced Studies
41
Session Summary
Elements of Systems Engineering are Embedded in All Engineering Endeavors Successes, and Failures, in Producing Complex Systems Continue to Create Advocates for the Value of Systems Engineering
M S Ramaiah School of Advanced Studies
42
