10 Golden Questions for Concept Exploration & Development Dr. Dan C. Surber (317) 306-4114.

Slides:



Advertisements
Similar presentations
PRODUCTION AND OPERATIONS MANAGEMENT
Advertisements

Business Plan: 3D Additive Manufacturing Technologies, Co. – 3-DAMTM
Medical Device Software Development
S Y S T E M S E N G I N E E R I N G.
©Silberschatz, Korth and Sudarshan4.1Database System Concepts Lecture-1 Database system,CSE-313, P.B. Dr. M. A. Kashem Associate. Professor. CSE, DUET,
 Project Title: Sustainable Manufacturing Metrics Accurately Define and Reflect Sustainable Values  Project Team: Academia, Industry, NGO  Goal Statement:
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
CS 545 Software Systems Design Project Presentation Format Lecture Created by Dan Benson Computer Science Lectures © D. Benson, 2002.
Class 6: Chapter 4 : Product/Process Innovation
Project Status Update R10004: OS/OA Low Energy Printing Mechanical Engineers: Dean Culver Shawn Hoskins Derek Meinke Tim Salter.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
IV&V Facility Model-based Design Verification IVV Annual Workshop September, 2009 Tom Hempler.
Copyright © 2014 McGraw-Hill Higher Education. All rights reserved. CHAPTER 4 Product/Process Innovation McGraw-Hill/Irwin.
BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS By Leigh Watton Friday 27th July 2001.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
The Software Development Life Cycle: An Overview
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Quality and Innovation in Product and Process Design.
CLEANROOM SOFTWARE ENGINEERING.
Chapter 1 Overview of Database Concepts Oracle 10g: SQL
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
An Online Knowledge Base for Sustainable Military Facilities & Infrastructure Dr. Annie R. Pearce, Branch Head Sustainable Facilities & Infrastructure.
ACS 560 – SOFTWARE ENGINEERING Course Accomplishment Summary Shilpashree K.S Fall 2010 Purdue University – Fort Wayne Instructor – Dr. John Tanik.
Engineering System Design
Lecture 2 An Overview of Relational Database IST 318 – DB Admin.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Requirements Engineering ments_analysis.
Michael deLamare Requirements Management Program Functions R-9.
 All companies have to adapt to change  Driving forces that affect an industry environment:  External Forces + New Competitive Change = Change in an.
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
Lecture 7: Requirements Engineering
1 A Training and Curriculum Development Partnership for Automated Manufacturing Jess Lee Niebuhr Anoka-Ramsey Community College
Requirement Handling
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Your Business Name Business Plan. 1.1 Product Overview.
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
© 2013, published by Flat World Knowledge Chapter 10 Understanding Software: A Primer for Managers 10-1.
CSE 303 – Software Design and Architecture
1 Margaret Christison Head of Product Data Standards Product Information Standards Defence Logistics 2004.
Product/Process Innovation CHAPTER FOUR McGraw-Hill/Irwin Copyright © 2011 by the McGraw-Hill Companies, Inc. All rights reserved.
The Second Annual Medical Device Regulatory, Reimbursement and Compliance Congress Presented by J. Glenn George Thursday, March 29, 2007 Day II – Track.
Requirements Engineering ments_analysis.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Software Engineering Lecture 10: System Engineering.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Failure Modes, Effects and Criticality Analysis
Concepts of Engineering Module 2 Test Review. Review Questions Design problems are broken down into sub- problems because smaller problems must be solved.
1 ME Spring 2013 Introduction to Systems Engineering Session 3 Dr. Dan C. Surber, ESEP © Copyright 2013.
Technical External Management Requirements Technology Complexity Interfaces Reliability / Performance Quality Planning Controlling Funding / Resources.
Chapter 13 Logistics and Channel Management.
Process engineering Quality controls.
Session 10 Dr. Dan C. Surber, ESEP
Session 2 Dr. Dan C. Surber, ESEP
Introduction To DBMS.
An Overview of Engineering Design
Design of Operations.
Software Verification and Validation
Authors: Maria de Fatima Mattiello-Francisco Ana Maria Ambrosio
Introduction to New Product Development (Specifications)
FMEA PROCESS FLOW Causes/ failure mechanisms Product definition
Session 5b Dr. Dan C. Surber, ESEP
A B C Solution Analysis Technology Maturation & Risk Reduction
Raytheon Parts Management
Exploring Application Lifecycle Management and Its Role in PLM
Presented By: Daniel J. Brown, CQA
Chapter 13 Logistics and Channel Management.
An Overview of Engineering Design
System architecture, Def.
Presentation transcript:

10 Golden Questions for Concept Exploration & Development Dr. Dan C. Surber (317)

Overview Definitions 10 Golden Questions Apply to Audience Examples Summary Q & A

Definitions Concept Exploration CONOPS Systems Engineering Life Cycle System, Product, Component Concurrent Engineering Failure Modes and Effects Analysis (FMEA)

10 Golden Questions 1.Who are the SYSTEM stakeholders? 2.What are the goals/objectives/constraints? a)User/Maintainer/Sustainer 1)Operations, Support. 2)Mission scenarios. 3)Production, sustainment, supply chain. 4)Life cycle needs for growth/improvement (P 3 I) b)Enterprise stakeholder goals, objectives and constraints? 3.What is the market for this SYSTEM? a.Where? b.When? c.Why? d.How funded?

10 Golden Questions 4.What are the external constraints the SYSTEM must satisfy? 5.What is the operating and support concept for the SYSTEM ? a.Major states, modes, transitions b.Environments 1)Operating & Maintaining 2)Storage & Shipping/Transportation c.Measures of Effectiveness d.Life Cycle Cost & Cost of Ownership

10 Golden Questions 6.What is the SYSTEM architecture context? a.People b.Facilities c.Support equipment (tools & testers) d.Manufacturing process capabilities e.Training 7.What are the man-machine interface criteria to be satisfied by the SYSTEM ? a.Operators & Maintainers b.Market unique standards (ISO, ANSI, etc.)

10 Golden Questions 8.What are the SYSTEM attributes? a.Four (4) types of requirements: 1)Performance 2)Environmental 3)Interface 4)Design Constraints b.Format of requirements: 1)Value, Relation, Units 2)Method of Verification (IADTS) 9.What are the SYSTEM functions (behaviors) that will satisfy the SYSTEM attributes?

10 Golden Questions 10.What happens if the SYSTEM fails to satisfy or perform as defined by 1-9? a.Potential effects of failure (qualitative, worst case) 1)Severity 2)Likelihood of occurrence b.What should be done to control or mitigate the potential for those SYSTEM failures? 1)Design 2)Manufacturing 3)Training 4)Usage limitations or advisories Questions 1-10 an be repeated using PRODUCT or COMPONENT.

Examples from the Audience!!

Summary Customers often want more than they will tell us. Ask questions to find out what is most important. Think of the life cycle, the user & those who must support and sustain the system: –Product Development –Products in-service Systems have several layers in their architectures, think it through from multiple perspectives. Ask what if it fails to ?! Often!!!!