1 / 8

Top Five List for Systems Engineering

Top Five List for Systems Engineering. Presented by: Francis Peter Management Sciences, Inc. INTRO:. What are the Top 5 most important elements in Systems Engineering and Analysis? Some Ideas: Requirements Interfaces Functions What are your top elements?. Architecture

linda-bush
Télécharger la présentation

Top Five List for Systems Engineering

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. Top Five ListforSystems Engineering Presented by:Francis Peter Management Sciences, Inc. Francis Peter

  2. INTRO: • What are the Top 5 most important elements in Systems Engineering and Analysis? • Some Ideas: • Requirements • Interfaces • Functions • What are your top elements? • Architecture • Configuration Management Francis Peter

  3. #5 Requirements • Sources: Customer, your domain knowledge, analyses, etc. • Decomposition: tiered specifications, allocation, traceability, etc. • Requirements Domain: • Known Knowns • Known Unknowns • Unknown Knowns • Unknown Unknowns Francis Peter

  4. #4 Stakeholders • Who has a stake in how the system is designed and built? • Customer (contracting and/or technical agency) • End User Community • Your company, management, and design team • Test and Evaluation community • AFOTEC, OPTEVFOR, Army? Francis Peter

  5. #3 Baselines • Provide a specific project view at various points in the development process • Functional • Allocated • Should be integrated with the Configuration Management process • Should be traceable between baselines • Product • Physical Francis Peter

  6. #2 Know Thy Boundaries • Things break at interface points • Physically and functionally • Detailed control of functional boundaries guarantee nothing left out, nothing “doubled” • Detailed control of interfaces mean functions communication and work on both sides • Use FMEA to optimize boundary choices • Break each interface with no data/bad data • Determine effects on system and mitigation required Francis Peter

  7. #1CONTEXT • Every system is part of a larger system • How does your system fit into this larger system? • What interfaces exist between your system and the larger system? How are they defined? • Is your system completely defined within this context? • What environmental constraints are imposed on your system? Francis Peter

  8. 5 Pillars of System Engineering • Requirements • Functions • Components • Interfaces • Context Or the Five Legged Stool Francis Peter

More Related