ME Curriculum Workshop Systems Engineering Discussion Rich Granger August 3, 2012.

Slides:



Advertisements
Similar presentations
Principles of Systems Engineering. Historical Perspective Industry identified a knowledge gap Lockheed pursued MJSP(MN Job Skills Partnership) and investigated.
Advertisements

Final Report Document. Format Title Page Executive Summary Table of Contents Introduction Mission Statement Main PDS items Brief justification of the.
BNAD 301 Global and Financial Economics & Strategies.
1 CS 425 / CS 625 Software Engineering Fall 2007 Course Syllabus August 27, 2007.
Systems Analysis and Design for Electronic Commerce, Networked Business Processes, and Virtual Enterprises Walt Scacchi, Ph.D. GSM 271 and FEMBA 271 Spring.
Process ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.
Programming Competitions as a Basis for an Algorithms and Data Structures Course John Paxton Montana State University CCSC - NW Friday, October 12, 2007.
Administrative Issues ICS 151 Fall 2007 Instructor: Eli Bozorgzadeh.
CIS 310 Management Information Systems Course Overview Guthrie, Summer 2014.
Course Introduction (Lecture #1) ENGR 107 – Intro to Engineering The slides included herein were taken from the materials accompanying Engineering Fundamentals.
INCOSE 1 st reactions. One other area that struck me has the sheer number of levels of proficiency—in ours we are going with 5 and the first one is limited.
…improves student performance! “I use the LearnSmart modules within Connect Management to get students familiar with the material and engaged with the.
Business Marketing Overview of Course Dr. Dawne Martin Calvin 201 B – 107 next week Office telephone: Office.
Computer Network Fundamentals CNT4007C
Courses - programme Courses Description Syllabus Exercises in groups Differences between project course (PE) and study course (SE) Start of exercise.
Workshop Notes Course development: Free and Open Software Development.
Computer Networks CEN 5501C Spring, 2008 Ye Xia (Pronounced as “Yeh Siah”)
TEL581. Outline “Divide and Conquer” Potential Topic Areas Teams Schedule Grading Benefits Assistance Lecture Slides Lab Assignment Homework Assignment.
ECEN 301Discussion #1 – Syllabus1 All Sections MWF 1:00 – 1:50 PM 256 CB Lecture: MW Recitation: F Labs: M or Th Instructor: Prof. David Long Office: CB.
Fall 2015 Course Syllabus Instructor: Sergiu Dascalu Department of Computer Science and Engineering August 25,
Software Engineering Management Lecture 1 The Software Process.
Software Specification and Design Sirisin Kongsilp & James Brucker.
1 November 7, 2002 ELECTRICAL & COMPUTER ENGINEERING DEPARTMENT November 7, 2002 EE CURRICULAR REVISION.
Facility Planning and Material Handling. Today’s Agenda Information on syllabus Office hours Text Grading Exams & Homework Class format Introductory lecture.
Improvement Guide Workshops Chapters 1-14 Suggested Workshops for participants who are applying the Improvement Guide to Projects.
Course Overview Stephen M. Thebaut, Ph.D. University of Florida Software Engineering Foundations.
Senior Design II proposal A step-by-Step review. What is Senior Design?  Senior Design is a sequence of two courses during two consecutive semesters.
10/06/04Model, PBL-skills and supervision1 Thursday the 10 th of June: training of PBL 09.00:Coherence between projects and courses (LPJ) 09.30: Co-operation.
Final Exam Review Session 14 LBSC 790 / INFM 718B Building the Human-Computer Interface.
Design of a Typical Course s c h o o l s o f e n g I n e e r I n g S. D. Rajan Professor of Civil Engineering Professor of Aerospace and Mechanical Engineering.
CSE Senior Design II Day 1: Getting Organized Spring 2015 Instructor: Manfred Huber.
CS Welcome to CS 5383, Topics in Software Assurance, Toward Zero-defect Programming Spring 2007.
Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
Course Instructor Professor Clark J. Radcliffe Office hours: MWF 11:30-12: EB ME 481.
Computer Networks CNT5106C
CSE Senior Design II Day 1: Getting Organized Spring 2012 Instructor: Mike O’Dell.
CSE Senior Design II Day 1: Getting Organized Spring 2016 Instructor: Mike O’Dell.
CIT 341: IT Project Management. Objectives Understand the main concepts of project management Understand how Projects are Delivered within Budget Learn.
CSE Wireless and Adhoc networks Instructor: Ayman Alharbi Computer Engineering Dept. (Head of dept. ) Why ?
Course Overview Stephen M. Thebaut, Ph.D. University of Florida Software Engineering.
Day 1: Getting Organized Spring 2014
Mr. Bruhnke, San Pedro High School, Room 223;
MMW 15 TA: Kyle Knabb Week 1.
IE 8580 Module 1: Course Preliminaries
Calculus I – Course Syllabus
Software Engineering Management
Computer Networks CNT5106C
It’s called “wifi”! Source: Somewhere on the Internet!
Autonomous Cyber-Physical Systems: Course Introduction
AP computer science PRINCIPLES
BSA 502 Competitive Success/snaptutorial.com
EE 435 Spring Lecture 1 Course Outline.
Day 1: Getting Organized Fall 2011
Day 1: Getting Organized Fall 2012
Regional Architecture Development for Intelligent Transportation
Physics I Class 01 Introduction & 1D Motion.
EECE 310 Software Engineering
Day 1: Getting Organized Summer 2012
Day 1: Getting Organized Fall 2013
Practical Software Engineering
Day 1: Getting Organized Spring 2013
NASA ESMD Systems Engineering Workshop
CS 425 / CS 625 Software Engineering
Administrative Issues
MIS 5302 Managing Technology and Systems Week 2
Day 1: Getting Organized Spring 2011
Administrative Issues
Homework Reading Machine Projects Labs
Folsom High School Class: AP Psychology Grade: 11th & 12th
Student Titles Workshop
Presentation transcript:

ME Curriculum Workshop Systems Engineering Discussion Rich Granger August 3, 2012

Systems Engineering Technical Topic Areas Systems Engineering Principles & Strategies Requirements Definition and Management Concept & Architecture Development Design Specifications & Verification Plans Risk Management Validation & Verification System Integration & Interfaces System Deployment & Life Cycle Support Sources: –The Center for Systems Management (CSM), engineering.htmlhttp:// engineering.html –“Systems Engineering Concepts”, Air Force Center for Systems Engineering,

Systems Engineering Concept Illustrations Source:

Systems Engineering Concept Illustrations Source:

Systems Engineering Existing Course Option Course Title: –ISE 5820: Systems Thinking in Engineering & Design Course Description: –Concepts and heuristics in systems thinking and complex systems analysis and how these concepts apply to engineering and design projects. Course Goals: –Basic principles of systems thinking and complex systems –How to apply systems of systems concepts to large scale projects –Basic concepts for modeling adaptive, co-evolving & self organizing systems –Systems thinking concepts to analyze safety issues in complex systems –Steps in human systems integration –Basic steps to manage complexity and avoid creeping complexity Additional Details: –14 weeks, 3.0 credits, 3 hr lectures, open to undergrad (Rank 4) and grads –Grading: Homework & class participation 20%, Exercises 50%, Exams 30%

Systems Engineering Additional Course Options New elective course or “Module” during May session –1 week of 2 credit hour course (5 lectures, M-F, 90 minutes each) –4 weeks of 1 credit hour course (12 lectures, M/W/F, 90 minutes each) Content could be drawn from several sources: –ISE 5820 course material –Case studies (open-source and/or purchased), e.g. Air Force Center for Systems Engineering at WPAFB, Center for Systems Management (CSM) –Case studies developed by faculty/lecturer (potential for NSF funding?) Course format concepts: –Use the case study method to organize course topics; similar method could be used for other topics (e.g. project management, ethics). –Student teams are presented with narrative description of open-ended situation with supporting data, and are asked to develop a recommended solution, applying principles from textbook and lectures. –Students would form teams and present solutions to the class. –After student presentations, instructor (and case author, if available) could discuss the actual solution, possibly as panel discussion.

Systems Engineering Course Structure Example Session # Lecture Topics (60 minutes) Case Study Presentations (30 min) 1 Systems Engineering Principles & Strategies Requirements Definition and Management Systems Engineering Process (Instructor-Led) 2 Concept & Architecture Development Design Specifications & Verification Plans Requirements Definition (Student Group 1) 3 Risk Management Validation & Verification Design Specs & Verification Plans (Student Group 2) 4 System Integration & Interfaces System Deployment & Life Cycle Support Risk Management, Validation & Verification (Student Group 3) 5 None (allocate 30 minutes for each student group presentation) Final Case Presentations (Student Groups 1, 2, and 3) Turn in written report (individual or group -- TBD)