1 / 21

Course Overview

EMIS 8340. Systems Engineering Tool—applying tools to engineering systems. Course Overview. Mark E. Sampson. BS CE (BYU) MS SE (USC) 30 yrs experience in CAE business (EE, SE) GE, TI, TD Tech, EDS, UGS, Siemens,…

mbarnhart
Download Presentation

Course Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMIS 8340 Systems Engineering Tool—applying tools to engineering systems Course Overview Mark E. Sampson

  2. BS CE (BYU) MS SE (USC) • 30 yrs experience in CAE business (EE, SE) • GE, TI, TD Tech, EDS, UGS, Siemens,… • Consultant at: Northrop, CIA, NSA, NASA, Seagate, AT&T, P&G, GM, Renault, HP, Intel, Oceaneering, Batelle, IAI, Siemens, Honeywell, Boeing, DoD, DOE, Rolls Royce, Volvo, FMC, Ford,… • INCOSE Tech Board 10+ years • Born on my front lawn in Las Vegas Instructor • Professor Mark E. Sampson • Office: 469.855.1461 • Cell: 469.855.1461 • Fax: 435.635.2072 • Email: msampson@smu.edu mark.sampson@siemens.com • Mail: EMIS Department PO Box 750123 Dallas, TX 75275-0123 • EMIS Dept: Tammy Sherwood Phone: 214.768.1100 Fax: 214.768.1112 • Website: http://engr.smu.edu/~msampson/ • Blackboard: http://cms2.systems.smu.edu/

  3. EMIS 8340 Course Description Computerized tools capture and deliver Systems Engineering (SE) information throughout the product development life cycle—the most common being Word™, Excel™, and Powerpoint™. This course moves beyond the Office Suite to survey the many tools that can be applied by SE across the entire lifecycle from inception to disposal. The best way to learn applications is to apply them to SE problems, so, we’ll start at the beginning by applying tools on scope/needs evaluation, moving into requirements analysis, down to functional and physical allocation, into optimization, wrapping up with test validation/verification and product management. A variety of SE tools are available to use during this course, you will identify and apply tools as you move through the lifecycle of your product--the end result is an understanding of what tools, methods, and techniques can be applied, to what part of the process, and how to use them.

  4. EMIS 8340 Course Objectives ..to a man with only a hammer, everything looks like a nail. Unknown During my days in systems engineering tool support, I received a call from one systems engineer informing me that he had run out of cells in his spreadsheet and wanted to know how to get more cells for his analysis. Having never heard of anyone ever running out of cells in a spreadsheet, I had to see what he was doing…he was using his spreadsheet to hold coordinate information from a flight test and using the plotting package to find anomalies in the data…

  5. EMIS 8340 Course Objectives…continued …to provide you,the SE, a toolkit of tools to apply to your craft. Whole courses are taught on individual topics/process steps we will cover. Our goal is to explore how tools are applied to these topics/processes so you apply the right tool to the job. • Tools include methods, techniques, and automated tools. • Course includes exposing students to a variety of tools through hands on use and tool application demonstrations. • Understanding of what tools to apply and how to apply them to SE problems. • Since the same tools are used throughout the life cycle--know when to use them. • Leave the course with a tool kit that can be applied through out your SE career (rather than applying a hammer to everything…)

  6. What’s needed for the course We will use SE Tools during this course. Assignments/Team projects will be using tools… • You can bring your own, use your own, write your own, company provided or otherwise • Google Drive will be the web-based collaboration environment for student use—you’ll receive an invitation to your SMU email account …you will need web access for homework

  7. What’s needed for the course…continued Lots of tools will be covered during this course. There will be a number of demonstrations (~2 per class) Some of the tools will be available, others will not. …we want to expose you to the tools that will be useful to you as SE’s.

  8. Course Textbook No Text Book No standard reference to the wide range of SE tools/methods covered during this course. Reference Book: INCOSE Systems Engineering Handbook any version. Documents a standard development process that includes tools to apply, data passed between process steps, and recommended approaches. Through-out this course you will see references to the handbook. Available at INCOSE.org in the members section for INCOSE members at http://66.34.135.97/membersonly2004/sehandbook/se_hdbk_v2a.pdf Not a member? You can contact INCOSE and join or sign up as a student for $10 and get access to it (rules for student membership may apply…) If your company is a INCOSE CAB Member, as a company employee you have access to an electronic version (old versions are also available in various online libraries)

  9. Graduate Course Requirements • Homework 20% Research/presentations on tools & applications:10% for tool contributions, 10% for tools application case study • Term paper 30% Tool application paper & present • Project 40% Team based product development experience supported by tools • Final Exam 10% Short paragraph responses

  10. Tool Contributions (10%) …contribution of tools that can be applied to SE (with 5 minute presentation on SE tool, method, or application to educate other class members). Each student is required to deliver two tools during this course—1 to the class in presentation form with application, the other emailed to the professor

  11. Tool Contributions…example A Design Structure Matrix (DSM) is a matrix representation of a system/project. The matrix lists all subsystems/activities and the corresponding information exchange and dependency patterns. Activity C relies on information from activities A and B and delivers information to activities D, E, F, and G—feed forward Feedback is indicated in red…I provides information needed for G. This means G, may haverework based on newinformation receivedfrom I You want to avoid these in process design. See www.dsmweb.org

  12. Tool Application Case Study (10%) …real-world example of SE problems & how tools could be used to address them (brief presentation on the subject) Each student is required to deliver one (1) during this course. Examples: • Deep Water Horizon/FMEA tools • Spacex launch/Reliability tools • Ford Edsel/Requirement tools • Toyota Stuck Accelerators/CAPA tools

  13. Tool Application Paper (30%) …applying tools to your job (a standard term paper describing a SE tool application in your job, hobby, social life,…) Each student is required to deliver one (1) during this course.

  14. Parent Child Tool Application Term Paper Example#1 Applying SE tools to raising your kids Parent Perceived Intelligence Child Age Age

  15. Tool Application Term Paper Example #2 Rigid-Cable optimization using Linear Programming

  16. Tools Project & Presentation (40%) …working as a team with tools towards a defined objective (includes: assignment specs, trade studies, and presentation/debrief about the problems, what tools were used, how they were used, results,…) During the first class, teams will define a simple problem they wish to address (…a product to be redesigned, a new product idea, current job related issue, …) We will use this problem throughout the course—with each class building on the previous to walk through the SE process supported by SE tools.

  17. Some bad/good product/project ideas… Samsung HomePad Refrigerator (2005)… Samsung TV… What problem do you have with your TV?

  18. Tools Project Example Redesigned Paint Can • Problems with current paint cans • Market research/requirements gathering • Cost/Benefit • Legacy systems—logistics, application,… • Regulatory--Recycling • Alternatives • Storage • Ergonomics • Supply chain

  19. Course Schedule Five, one-day classes Saturday 8:00 AM – 5:00 PM Location: Virtual via Wimba • Aug. 16 Class #1: Before Requirements • Sep. 13 Class #2: Requirements • Oct. 11 Class #3: Functions & Architecture • Nov. 8 Class #4: Optimization • Dec. 6 Class #5: Program Mgmt Project presentations/Final Exam during Class #5 Please visit www.smu.edu for the official calendar.

  20. Assignments - Submission Guidelines • Use our class collaboration environment—post your assignments and… • Email assignments as attachment. Indicate Course & Assignment Number in the ‘Subject’ line as follows… From: Joe Student To: Mark Sampson Attachment:Name_SE12_Termpaper.doc Subject: EMIS 8340 SE12 – Term Paper

  21. Assignments - Submission Guidelines, continued • MS Word, Excel and PowerPoint are the preferred file type for attachments… (PDF is also acceptable) • Naming Convention: name_011414_assignment.doc • Do not send zipped files to my .ugs address (they get knocked off by my firewall). You can send .zip files to my home email address: mesampson@infowest.com • These files may be printed, so please do not make the print area larger than 8.5” X 11”.

More Related