Principles of Engineering System Design Dr T Asokan

Slides:



Advertisements
Similar presentations
DECISION MODELING WITH Multi-Objective Decision Making
Advertisements

Multi-Attribute Utility Theory (MAUT)
Multi‑Criteria Decision Making
Logistics Network Configuration
S Y S T E M S E N G I N E E R I N G.
Agenda Cost Management Capital Budgeting Payback Period
National Aeronautics and Space Administration Systems Engineering (SE) Tools National Aeronautics and Space Administration Example.
© 2005 Prentice Hall6-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Assignment of Weights Other methods, besides arbitrary, for weight assignment exist There are both direct and indirect weight elicitation techniques Source:
1 Introduction to System Engineering G. Nacouzi ME 155B.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Introduction to Management Science
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
Compare and Contrast ELCC Methodologies Across CPUC Proceedings
Copyright 2012 Delmar, a part of Cengage Learning. All Rights Reserved. Chapter 3 Organization Design and Coordination.
On Fairness, Optimizing Replica Selection in Data Grids Husni Hamad E. AL-Mistarihi and Chan Huah Yong IEEE TRANSACTIONS ON PARALLEL AND DISTRIBUTED SYSTEMS,
Software Architecture Quality. Outline Importance of assessing software architecture Better predict the quality of the system to be built How to improve.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Chapter 2 - Overview of the Systems Engineering Design Process1 Aerospace Systems Engineering Chapter 2 - Overview of the Systems Engineering Design Process.
1 Enviromatics Decision support systems Decision support systems Вонр. проф. д-р Александар Маркоски Технички факултет – Битола 2008 год.
Reliability of Selection Measures. Reliability Defined The degree of dependability, consistency, or stability of scores on measures used in selection.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Principles of Engineering System Design Dr T Asokan
9-1 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Multicriteria Decision Making Chapter 9.
Multicriteria Decision Making
«Enhance of ship safety based on maintenance strategies by applying of Analytic Hierarchy Process» DAGKINIS IOANNIS, Dr. NIKITAKOS NIKITAS University of.
Presented by Johanna Lind and Anna Schurba Facility Location Planning using the Analytic Hierarchy Process Specialisation Seminar „Facility Location Planning“
Managing a Training Program Why train? Who will attend the training? What are the learning objectives? Strategies? Coverage? How will the training program.
Principles of Engineering System Design Dr T Asokan
Using Network Simulation Heung - Suk Hwang, Gyu-Sung Cho
Principles of Engineering System Design Dr T Asokan Decision Making in System Design.
Analyzing the Problem (MAVT) Y. İlker TOPCU, Ph.D twitter.com/yitopcu.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Normative Criteria for Decision Making Applying the Concepts
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
Marketing Research Aaker, Kumar, Day Seventh Edition Instructor’s Presentation Slides.
Contemporary Engineering Economics, 6 th edition Park Copyright © 2016 by Pearson Education, Inc. All Rights Reserved Choice of MARR and Capital Budgeting.
Engineering System Design
Section 10: Advanced Topics 1 M. Balakrishnan Dept. of Comp. Sci. & Engg. I.I.T. Delhi.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Policy Analysis: Frameworks and Models Stokey and Zeckhauser Ch1-3 Jenkins-Smith Ch1-3 Weimer and Vining Ch1-2.
1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.
Lecture 7 Risk Analysis CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
An overview of multi-criteria analysis techniques The main role of the techniques is to deal with the difficulties that human decision-makers have been.
Week 6 - Systems Engineering and Analysis
Principles of Engineering System Design Dr T Asokan
Principles of Engineering System Design Dr T Asokan n.
BSBPMG504A Manage Project Costs 7.1 Estimate Costs Adapted from PMBOK 4 th Edition InitiationPlanning ExecutionClose Monitor Control The process of developing.
Proprietary & confidential. © Decision Lens 2010 Decision Lens Criteria Development Session PSU ITS Pilot Gina Patel, Senior Client Decision Manager
Nov 2004Joonas Hokkanen1 Dr. Joonas Hokkanen Consulting Engineers Paavo Ristola Ltd Finland Presentation of the EU study (1997) “THE USE OF DECISION-AID.
Fuel Cell Systems Engineering, F06 Fuel Cell Systems Engineering Lecture 7 Quantitative Decision Methods.
CSE 303 – Software Design and Architecture
OPERATING SYSTEMS CS 3530 Summer 2014 Systems and Models Chapter 03.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
CONCEPT, PROCEDURES, ADVANTAGES & DISADVANTAGES Point Method of Job Evaluation By: Arthur Gonzaga.
Applied Quantitative Analysis and Practices LECTURE#17 By Dr. Osman Sadiq Paracha.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Chapter 9: Systems architecting: Principles (pt. 3) ISE 443 / ETM 543 Fall 2013.
OPERATING SYSTEMS CS 3502 Fall 2017
Decisions Under Risk and Uncertainty
Course Summary Organization: A process providing goods and services based on a set of inputs, including raw material, capital, labor and knowledge. The.
Software Requirements
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Constructive Cost Model
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Multicriteria Decision Making
Chapter 26 Estimation for Software Projects.
Presentation transcript:

Principles of Engineering System Design Dr T Asokan

INTRODUCTION TO SYSTEMS DESIGN Dr T Asokan Operational Architecture Development Contd…

Trace non-input/output requirements Internal input/output requirements System-wide requirements Trade off requirements Qualification requirements

T Asokan ED309 Apportionment method Internal input/output requirements

T Asokan ED309

Digitized passenger requests Assignment for elevator cars Elevator position and direction  The elevator system shall produce digitized passenger requests  The elevator system shall consume digitized passenger requests etc.. These I/O need to be traced to corresponding items and the functions responsible for consuming and creating the item respectively.

“The elevator system shall produce digitized passenger requests” can be traced to the function Accept passenger requests and provide feedback “The elevator system shall consume digitized passenger requests” can be traced to the function Control elevator cars.

Tracing system-wide requirements and Deriving subsystem-wide requirements System-wide requirement on Cost, Reliability, availability, durability etc. need to “allocated” among the components of the system. Example: The system shall cost Rs or less to use per month during its operation System shall employ ‘ABC’ technology How do we allocate these system wide requirements to components/sub systems is a major task.

T Asokan ED309 There are three techniques for flow down of these system-wide requirements – Apportionment, Equivalence, and Synthesis [Grady, 1993] Apportionment Method Most appropriate for cost requirements, reliability, availability, durability etc. The system-level requirement is divided or apportioned out to the systems components, not necessarily in equal increments, keeping a margin of 5-10% as risk mitigation strategy.

The apportioned reliability of components could be: Passenger interface: 0.96 ( design goal) Elevator controller:0.995 ( 0.995) Elevator compartment:0.96 ( 0.96) Elevator maintenance: 0.99 ( 0.99) The product these numbers provides margin of 0.01 for risk mitigation Derived reliability requirement: The elevator component, passenger interface, shall have a reliability of 0.96 or greater. The design goal is Example: System-wide reliability of elevator is 0.9 with design goal of 0.99

Synthesis method Used when the system-level requirement is comprised of complex contributions from the components, causing the component requirements that are flowed down from the system to be based upon some analytic model. The system-level requirement has significantly different units than the derived component requirement has. Accuracy, range, thrust, time etc.. Equivalence method Component requirement same as system requirement. System constraints are appropriate for equivalence method Example: The system shall be olive green in color

The requirement relating to the average time between the passenger making a request and being delivered to the requested floor needs to be synthesized between all the four components which provide this service. T Asokan ED309

Trace Trade-off requirements and Derive subsystem Trade-off requirements Cost, schedule, performance

T Asokan ED309

Cost, schedule, performance T Asokan ED309 Decision Analysis for design trade offs: Multiattribute Value Analysis (MVA) Analytical Hierarchy Process

Multiattribute Value Analysis (MVA) A quantitative method for aggregating a stake holders preferences over conflicting objectives to find the alternative with the highest value when all objectives are considered. 1.Define value scale for each objective 2.Quantify the relative value of improving from lower to higher level in the form of ‘value curves’ (value functions). 3.Normalise value functions 4.Exponential functions are used to approximate normalised value functions. T Asokan ED309

Normalised value function T Asokan ED309

Value weights reflect the relative value associated with increasing from the bottom to the top of each value scale. T Asokan ED309

Weightage calculation: Communication system Throughput (mbits/sec) Availability Operating life (yrs) Procurement cost 100 – 85 4 Operating cost ($/month) 1.00 – ROC Rank Order Centroid (ROC) method T Asokan ED309

RISK and PERFORMANCE ANALYSIS A risk analysis examines the ability of the divergent concepts to perform up to the needed level of performance across a wide range of performance scenarios. Addressing uncertainty and multiple objectives in the risk analysis is critical (will be discussed later under ‘decision making under uncertainty’) Performance analysis are for the purpose of discovering the range of performance that can be expected from a specific design or a set of designs that are quite similar. Mathematical modelling and simulation are often carried out. (will be discussed under ‘Modelling and simulation’) T Asokan ED309

Summary Operational Architecture Function allocation Trace system wide requirements and derive subsytem wide requirements Allocate subsystem wide requirements Apportionment method Equivalence method Synthesis method Trade off requirements and allocation Multi Attribute Value Analysis T Asokan ED309