Engineering Systems of.

Slides:



Advertisements
Similar presentations
Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
Advertisements

S Y S T E M S E N G I N E E R I N G.
Lecture # 2 : Process Models
CS487 Software Engineering Omar Aldawud
Aerospace Systems Engineering
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Software Engineering General Project Management Software Requirements
ESD.83Cory R. A. Hallam1 An Introduction to Systems Engineering The Art of Managing Complexity Presented By Cory R. A. Hallam B.Eng., M.Eng., ISU SSP,
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
1 Introduction to System Engineering G. Nacouzi ME 155B.
SE 555 – Software Requirements & Specifications Introduction
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
ES305: Virtual Tools in Engineering Design: The Eng. Design Process James Carroll, Associate Professor Electrical and Computer Engineering.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Design, Implementation and Maintenance
Software System Integration
Enterprise Architecture
Effective Methods for Software and Systems Integration
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Chapter 7: The 30 elements of systems engineering
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
Rational Unified Process Fundamentals Module 4: Disciplines II.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
An Introduction to Software Architecture
Software System Engineering: A tutorial
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Instructor: Peter Clarke
Teaching material for a course in Software Project Management & Software Engineering – part II.
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Software Requirements Engineering: What, Why, Who, When, and How
2007 Introduction to System Engineering 1 ECET/CPET 491 Senior Design Project II Intro to System Engineering Reference: System Engineering Management,
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
Space Systems Engineering: Functional Analysis Module Functional Analysis Module Space Systems Engineering, version 1.0.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
1 | 2010 Lecture 1: Systems – what and why?. Covered in this lecture Systems and systems thinking Why we use Systems Engineering Systems from “cradle.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Systems Engineering Conceptual System Design. Systems Engineering and Analysis, B.S. Blanchard and W. J. Fabrycky, 3 rd edition, Prentice-Hall, 1998.
Chapter 1: Introduction to Systems Engineering April 2012.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Requirements Engineering
Smart Home Technologies
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
1 PDS MC Requirements Process March 29, 2007 (v2).
ISE Key Concepts Terminology –systems engineering: an interdisciplinary approach and means to enable the realization of successful systems. It.
Software Engineering Lecture 10: System Engineering.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
SYSE 802 John D. McGregor Module 0 Session 3 Systems Engineering QuickView.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Introduction to Project Management
OVERVIEW Impact of Modelling and simulation in Mechatronics system
Introduction to Systems Engineering
Systems Design.
Unified Modeling Language
The Systems Engineering Context
Business System Development
An Introduction to Software Architecture
Presentation transcript:

Engineering Systems of

Systems Engineering An Introduction M R Shankar

Outline What is “SE”? Why “SE”? Where it can be? How “SE”?(A big question) A Generic SE process

What is a ‘System’? Electrical Avionics Hydraulics Mechanical

What is a ‘System’? A group of components that work together for a specified purpose Components - products (hardware, software, firmware), processes, people, information, techniques, facilities, services and other support elements Together – integration of many Purpose – is achieved by implementing many functions

Emphasis on Technical systems Other Systems Natural Man made Technical Non – Technical Aircraft Missile … Economic system Societal systems … Emphasis on Technical systems

Technical Systems Human-made artifacts Result of engineering activities with the processes of engineering design Difficult to classify systems based on technology like electrical system, mechanical system Most present day systems are hybrids of simple systems of the past An indication of the need to use inter-disciplinary approach

What is “Engineering”? Knowledge of mathematical and natural sciences applied to utilize limited resources economically for the benefit of people Scientific approach Optimize resources User/customer in focus Classical Engineering focused mainly on product design

Systems Engineering (SE) SE is an interdisciplinary approach and means to enable realization of successful systems It is very quantitative including tradeoff, optimization, selection and integration of products from various engineering disciplines It is more of an engineering discipline.

Why “SE” is needed Complexity Technical Project

Wright Brothers Why “SE”? Designed, Built and Flew the world’s first powered, controlled, heavier-than-air flight

Why “SE”? ONE Chief Designer – TOTAL knowledge

“SE” is needed due to Technical complexity High Complexity Multidisciplinary Cost & Time “SE” is needed due to Technical complexity

Why “SE”? % Commitment to technology, configuration, cost etc 100 75 Cost incurred System specific knowledge 50 25 Ease of change Concept & prelim. design Detail design & development Production Use, phase-out disposal

Ensures FINAL PRODUCT Fully Meets All User Requirements Why SE (cont..) More systematic way of development Better control of System Development incl. management of risk, changes, configuration Traceability at all levels Operational & supportability aspects Effectiveness Analysis Risk management Operational - Maintainability, Availability, Safety etc Ensures FINAL PRODUCT Fully Meets All User Requirements

Where “SE”? All levels Organization level – for a project Full fledged SE Subsystem level We aim at this level!! Individual level Systems thinking

Systems Engineering (SE) Emphasis on Top-down approach Interdisciplinary approach Effort on more complete definition of system requirements Life cycle engineering approach

Emphasis in SE Top-down approach Interdisciplinary approach Look at system from top Decide inputs/outputs taking into account the supersystem Decide subsystems … down to lower levels Interdisciplinary approach Analytical approach is inadequate Capture the interactions between disciplines Exploit the synergism of these interactions

Emphasis in SE More complete definition of needs Complete definition of needs facilitates verification of system performance Minimize surprises at later stages Life cycle engineering approach Initial approach was Design cycle Later with Design for Manufacture (DFM) approach Manufacturing cycle also included Present thinking is to consider three life cycles i.e. Design, Manufacturing and Supportability concurrently Leading to Concurrent Engineering (CE)

Life-cycle engineering approach Development phase Utilization phase Product use Phase out and Disposal Conceptual & Preliminary Design Detail Design & Development Production and/or Construction NEED Design Manufacturing Configuration Design Manufacturing Operations Manufacture Product support and maintenance Product support configuration design and development Deployment

Product life cycle Identification of need Research Input Conceptual design System concept Preliminary Design Subsystem design Detailed Design & Development Component design Production/Construction Development phasing Utilization & Support Phase-out and Disposal

Systems Engineering process Basic steps Define system objectives (user’s needs) Establish performance requirements (requirements analysis) Establish functionality (functional analysis) Evolve design and operation concepts (design synthesis) Select a baseline (thro’ trade-off studies) Verify the baseline meets requirements Iterate the process through lower level trades (decomposition)

R V D Requirements analysis Functional analysis INPUT Design Synthesis System Analysis & Control OUTPUT Concept studies System studies Prelim. Design Detailed Design

Detailed design & Development System analysis and control Conceptual design Preliminary design Detailed design & Development Requirement analysis Functional analysis Design Synthesis System analysis and control Development phasing System Engineering Management Development Production Deployment Operation Support Training Verification Disposal System Engineering process Life cycle approach This interaction shows how to apply SE process to develop systems in life cycle approach

Aids to SE Management Development phasing Lifecycle planning Baselines Functional baseline Allocated baseline (‘Design to’ specs.) Product baseline (‘Build to’ specs.) Drawing inputs from all the life cycle activities for various development phases Development phasing Baselines Lifecycle planning System Engineering Management System Engineering process Integrated approach Life cycle approach Integrated team from Systems engineering and discipline specialists

SE process overview

SE process mapped to Life cycle

What we have seen What is a System What is Systems Engineering Why Systems Engineering is needed? Life cycle engineering approach leading to Concurrent Engineering Product cycle & development phasing Steps in System engineering process

I will stop here… We will move forward… Ref: INCOSE SE handbook DSMC – SE mgmt guide Systems Engineering & Analysis – Blanchard & Fabrycky

Baselines Functional baseline : Allocated baseline : Top level (system) functions, performance & interfaces. System level technical description Allocated baseline : System requirements flowed down to items below Item performance specification, interface definitions, process description and drawings ‘Design to’ specifications Product baseline : Defining system from top to bottom in terms of physical entities ‘Build to’ specifications

System classification Natural & manmade systems River system, Bridges Physical & conceptual systems Airline system, economic system Open & closed systems Chemical equilibrium in closed vessel, business organization Static & Dynamic systems Bridge, Aircraft

What is a system? A group of components that work together for a specified purpose e.g. Aircraft Purpose is achieved by implementing many functions System is made up of components, attributes and relationships Components are the operating parts consisting of input, process and output e.g. Wing Components may be structural, flow or operating Attributes are the properties that characterize the system e.g. Lift generated Relationships are links between components and attributes The purposeful action by system is its function.