1 / 18

Systems Engineer for Non SE

Systems Engineer for Non SE. Bill Fournier billfournier4@gmail.com 202 255 0760. Agenda. History/Value/Application Definitions Whom How-–Technical,(user) project (PM & PC) and Agreement(Contracts ), Tailoring, SpE CASE

kimberly-woods
Download Presentation

Systems Engineer for Non SE

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. Systems Engineer for Non SE Bill Fournier billfournier4@gmail.com 202 255 0760 Bill Fournier Nov 2014

  2. Agenda • History/Value/Application • Definitions • Whom • How-–Technical,(user) project (PM & PC) and Agreement(Contracts ), Tailoring, SpE • CASE • Job advertisement for SEs • Recruiters • Future • References

  3. History/Value/Application • History- SE- Products, Processes, People- use, fix • Pyramids/Greek/Romans/Ren/ British Train/ Model T/ WW I tank • WW II- too much one person to detail design • Value - % SE 10-15 knee of curve for cost and schedule control • Applicable • Government- user need document • Commercial- Marketing / focus groups • International • Services Bill Fournier

  4. Definitions I • Systems- Products, Processes and People & boundaries, Purpose • 3 SE POVs – interdisciplinary, iterative, and recursive, way of thinking, feedback loops, top down and bottom up • Requirements- Needs & technical requirements • CONOPS- plans how use system • Functions- verbs things systems must do to do mission • Physical Architecture/Design- nouns products decomposed which expected to meet requirements and their interrelationships • Implementation- Build & Code development system • Integration- put subsystems and lower together • Verification- Prove by Objective Evidence that the requirement has been met with the final configuration. TADI • Validation- Assess we meet what user needed • Test- method of assessing progress towards showing system works • Production- Make final hardware built and coded in quantity • Operation and Maintenance- use, maintain • Disposal- retire/recycle Bill Fournier

  5. Definitions II • PM- Program/Project/Product Manager • Configuration Management – Plan, ID, control, status, audit the technical baseline of system • Trade Studies- analyze alternatives trades • Technical /Design Reviews- decide if maturity worth going forward • Risk/Issues- things could go wrong / have gone wrong • TPMs- key early warning indicators of problems • Acquirer- manager the development contract for the stakeholder • Supplier- designs, builds/codes to meet contract(s) • SpE- SE like specialties with narrower focus Bill Fournier

  6. Whom • EE • IE • OR • ISE • Technical PM • Requirements Eng’g • Designers • Analyst Bill Fournier

  7. Stages • Exploratory Research • Concept • Development • Production • Utilization • Support • Retirement Bill Fournier

  8. Technical Processes (Users) • Stakeholder Req. Def. Inputs • Req. Analysis Source Documents • Arch. Design Stakeholder Needs • Implementation Project Constraints • Integration • Verification Outputs • Validation Balanced System • Operation • Maintenance • Disposal • Cross- Cutting Bill Fournier

  9. Project Processes (PM & PC) • Project Planning • Project Assessment and Control • Decision Making- Trade study • Risk & Opportunity Management- Prob. & Impact • Configuration Management • Information Management • Measurement- MOE/MOP/TPM Bill Fournier

  10. Agreement Processes • Acquisition • Supply Bill Fournier

  11. Tailoring • Cost of formality • Cost of Miss communications • Reduce theoretical overall cost Bill Fournier

  12. SpE Analysis • Logistics- RAM… • Cost effectiveness • EMI • Environmental Impact • Interoperability • LC cost • Manf. and producability • Safety & health hazard • Sustainment • Training needs • Human factors • Value Engineering Bill Fournier

  13. CASE • Computer Aided Systems Engineering • How can computers help ? Bill Fournier

  14. SE Job Advertising Table 1. Systems Engineering Roles Role Abbr. Short Name 1 RO Requirements Owner 2 SD System Designer 3 SA System Analyst 4 VV Validation/Verification Engr. 5 LO Logistics/Ops Engineer 6 G Glue Among Subsystems 7 CI Customer Interface 8 TM Technical Manager 9 IM Information Manager 10 PE Process Engineer 11 CO Coordinator 12 CA Classified Ads SE Bill Fournier

  15. Future • Software intensive • Speed of Development • Greater Specialization • Recycle Systems • Interfaces • SE even greater value Bill Fournier

  16. Processes • Technical (User) • Project (PM & PC) • Contracting (Contracts) • Tailoring (All) • SpE (SpE) Bill Fournier

  17. Related and Overlapping • ISO 9000 • Lean Six Sigma • ITIL • CMMI Bill Fournier

  18. References • INCOSE SE handbook version 3.2.2 October 2011 ( version 4 will come out in 2015) • INCOSE.org – CASE tool survey, certification, chapters • ISO/IEC 15288:2008 • DAU.edu • Linkedin my group, my TR book • Honourcode • http://www.incose.org/educationcareers/PDF/12-roles.pdf Bill Fournier

More Related