Leveraging Interoperability for Improved Project Reporting

Transcription

1 Leveraging Interoperability for Improved Project Reporting Grant Blythe Mentor Graphics September 2016 GPDIS_2016.ppt 1

2 Grant Blythe Bio Grant Blythe is a member of the Systems Engineering Products team at Mentor Graphics where he specializes in solutions for military and aerospace applications. Prior to joining Mentor Graphics, Grant spent 10 years in systems engineering roles developing both commercial and military avionics. In addition to his role at Mentor Graphics, Grant is a member of the SAE S-18 Airplane System Development Committee which publishes the ARP4754A and ARP4761 standards. Grant holds a B.S. in electrical engineering from Iowa State University and an M.B.A. from the University of Oregon. GPDIS_2016.ppt 2

3 Agenda Intro Background (GPDIS 2014 & 2015) Problem Approaches Proposed Solution Reporting Project Management Design Documentation Compliance and Auditing Next Steps GPDIS_2016.ppt 3

4 Standards Compliance has become increasingly complex resulting in Development Process Waste Transportation Waste Manually moving/importing/exporting data between multiple design tools Manually reformatting/translating data for use in multiple tools Motion Waste Staff switching & multi-tasking across several unintegrated tools Searching for data in multiple locations Waiting Waste Attempting to start tasks before inputs are ready Tasks not performed according to priority (off critical path) Over-production Waste Creating & maintaining multiple copies of the same data Defects Waste Defects introduced during non-value add activities such as moving, copying, translating data GPDIS_2016.ppt 4

5 Need for a LEAN Development Environment Current State Disjointed Erratic Variable Complex Ideal State Seamless Consistent Predictable Simple GPDIS_2016.ppt 5

6 But this is not an easy problem to solve. Past integration approaches provided limited choice and coverage Single repository Point-to-point integrations Can I really expect one vendor to provide all the functionality I need? And what about my existing tools? How can I ever upgrade one tool without breaking everything else? Past integration approaches were disruptive and slow to emerge Universal metadata standard Standard implementations How did I ever think all those vendors would be able to agree? Did I really believe that every vendor would rewrite their tools on a single framework? GPDIS_2016.ppt 6

7 OSLC Context System Design Manager (SDM) Requirements (e.g. DOORS) Product Manager Analytics Change tool (e.g. RTC) Requirements Engineer SDM Server System Relationshi ps Architecture (e.g. Rhapsody) HW Architect (e.g.dxsd) Systems Architect SW Architect (e.g. Rhapsody) Develops functional system architectur e Partition into design disciplines Data Manager (e.g. ClearCase) EE Design (e.g. Capital) Network tool (e.g. VSA) SW Design (e.g. Sourcery) EE Harness data Network AUTOSA R data C code Software GPDIS_2016.ppt 7

8 Architect & Plan your project Connect & Trace your data Analyze & Report your progress GPDIS_2016.ppt 8

9 ARCHITECT & PLAN your project GPDIS_2016.ppt 9

10 Architect & Plan your project Connect & Trace your data Analyze & Report your progress GPDIS_2016.ppt 10

11 CONNECT & TRACE your data A consistent interface allows tracing and connectivity from any tool in your environment GPDIS_2016.ppt 11

12 CONNECT & TRACE your data s and Reviewers can access preview data from dependencies and relationships without leaving the current tool 12 GPDIS_2016.ppt 12

13 Architect & Plan your project Connect & Trace your data Analyze & Report your progress GPDIS_2016.ppt 13

14 OSLC Our OSLC Solution Requirements (e.g. DOORS) Change tool (e.g. RTC) Systems Engineer Product Manager Analytics SDM Server System Relationshi ps Project Manager Architecture (e.g. Rhapsody) HW Architect (e.g.dxsd) Systems Architect SW Architect (e.g. Rhapsody) Develops functional system architectur e Partition into design disciplines Certification Lead Data Manager (e.g. ClearCase) EE EE Design (e.g. Capital) Network tool (e.g. VSA) Network SW Design (e.g. Sourcery) Software Harness data AUTOSA R data C code GPDIS_2016.ppt 14

15 Our OSLC Solution Requirements (e.g. DOORS) Change tool (e.g. RTC) Systems Engineer Product Manager Analytics Project Manager Architecture (e.g. Rhapsody) HW Architect (e.g.dxsd) Systems Architect SW Architect (e.g. Rhapsody) Develops functional system architectur e Partition into design disciplines Certification Lead Data Manager (e.g. ClearCase) EE EE Design (e.g. Capital) Network tool (e.g. VSA) Network SW Design (e.g. Sourcery) Software Harness data AUTOSA R data C code GPDIS_2016.ppt 15

16 Our OSLC Solution Systems Engineer Project Manager Systems Architect Certification Lead EE Network Software GPDIS_2016.ppt 16

17 Our Stakeholders Systems Engineer Project Manager Certification Lead Responsible for Product Design/Analysis Must author design documents and reports Responsible for project budget and schedule Must develop and report project metrics Responsible for process compliance and coordination with regulatory authorities Must generate process compliance reports and provide auditors with requested product data GPDIS_2016.ppt 17

18 Project Manager Project Managers and Team Members have live metrics on project progress 18 Your Initials, Presentation Title, Month Year GPDIS_2016.ppt 18

19 Systems Engineer Live, compiled reports eliminate the need to update documentation by hand after design changes GPDIS_2016.ppt 19

20 Certification Lead Trace reports enable reviews spanning both tools and domains GPDIS_2016.ppt 20

21 Thank you! For questions, please contact: Grant Blythe, Mentor Graphics GPDIS_2016.ppt 21