Merlin Bar Graph: Problems, Solutions, Progress

1. Merlin Bar Graph:Problems, Solutions, Progress Status 13.09.06

2. Companies needs Getting out the right product with right quality • Main needs • Effectiveness • Efficiency • Trust • Sub-needs • Transparency • Common understanding • Consistency • Traceability • Controllability

3. Progress in collaboration item coverage

4. Progress in collaboration item coverage

5. Challenges in collaboration:A subset of the Collaboration Handbook Selected topics are addressed in the following slides Problem area Typical problems • Collaboration management • No visibility of collaborative development status beyond partner borders • No clear agreements with the suppliers • Change management • Not defined change mgmt procedures • Underestimated impact of changes • Requirements engineering • No common understanding of the requirements • Not traceable whether the product meets the requirements in collaborative development • Lack of interface management • Lack of common understanding of architecture • Architecture • Integration and testing • Sharing and maintaining the integration and testing knowledge effectively • Sharing resources efficiently, managing access, traceability and privacy • Configuration management • Uncontrolled releases • Lack of library system enabling multi-team CM • Co-operativework • No consistency in engineering tasks • Dependencies between teams not made explicit and managed

6. A sample collaborative situation (System) Integrator Release planning Requirements Acceptance Criteria Acceptance Release Testing subcontractor Test Case Development Running tests Report Component supplier Internal testing Analyzing design Code Change Build

7. Typical challenges Efficient use of resources Transparency through partnerborders (System) Integrator Traceability between the tested product and the requirements Release planning Requirements Acceptance Criteria Acceptance Release Common understanding of the requirements Testing subcontractor Test Case Development Running tests Report Consistency in engineering tasks Component supplier Internal testing Analyzing design Code Change Build

8. Collaborationmanagement Solutions • Guide to supplier selection and supplier audits • Checklist for supplier agreements • Tool chain Major problems • Selection of suppliers not done (lack of selection criteria) • No clear agreements with suppliers • No tracking of the suppliers • Not validating and accepting supplier results • Consistency between engineering tasks not managed • Visibility of collaborative development status beyond partner borders • Dependencies between teams not made explicit and managed Available Available Available

9. Requirements engineering Solutions • Tool chain Major problems • Not traceable whether the product meets the requirements in collaborative development • Lack of common understanding about the requirements • Inconsistency between requirements and further work products Available

10. Testing and Integration Major problems • Sharing of test environment and results • Sharing resources efficiently • Effective reproduction of problems • Choosing the right integration and testing strategy • Integration responsibilities not clearly assigned • Integration not centrally controlled Solutions • SkyFab • Tool chain Proven Available

11. Handbook themes – tool chain rationale • Handbook structures items, questions and solutions as encountered in operational collaborative development • Handbook shows the impact of these items, questions and solutions to the needs as uttered by the companies • The tool chain demonstrates implemented solutions to these needs addressed in terms of items, questions and solutions of the handbook

12. Main added value of the Tool Chain • Main needs • Effectiveness: • Efficiency: • Trust: • Sub-needs • Transparency: • Common understanding: • Consistency: • Traceability: • Controllability: • Requirements explicitly covered by tests, explicit and successful test execution • Supports in consistency in engineering tasks by synchronization and status overviews of successive engineering tasks • Supported by unambiguous and factual reporting • Insight and overview in total project for all involved parties • Same level of reporting to all, real-time accessibility of the same data • Real-time accessibility of the same data and changes • Coverage of engineering activities by project tasks and coverage of test cases by requirements using unique identifiers • Insight and overview in total project for all involved parties and ability to take corrective measures based on status of engineering results and tasks

13. Solution status for problems (current) Solution status for problems (year 2005) Proven Available Idea No solution • Confidentiality • Sharing and maintaining the integration and testing knowledge effectively • Lack of stated criteria for selecting suppliers • Lack of interface management • Suppliers not or not timely audited • Lack of common understanding of architecture • No detailed plan or clear agreements with suppliers • Lack of integration strategy and plan • No visibility of collaborative development status beyond partner borders • Integration responsibilities not clearly assigned • No traceability of requirements in collaborative development • Underestimated integration effort and time • Lack of knowledge and skills in integration team • Consistency between engineering tasks not manageable • Integration not centrally controlled • Lack of leveling of local and global change requests and problem reports • Sharing of same test environment not feasible • Status of test results not shared • Not defined change management procedures • Not traceable whether the product meets the requirements in collaborative development • No transparency of the collaborative engineering chain • Underestimated impact of changes to other parties work • Problems not reproducible • Lack of involvement of right people in requirements and architecture analysis and validation • Lack of skills for multiple team CM • Uncontrolled releases • No common understanding about the requirements • Lack of library system enabling multi-team CM • Not defined practices for resolution of conflicting requirements • Sharing resources efficiently, managing access, traceability and privacy • Not defined prioritization rules and practices of the requirements in case of many interest groups • Acceptance procedures of mutual deliveries not defined • Unstable requirements • Escalation mechanisms not defined • Dependencies between teams not made explicit and managed • Underestimated learning curve • Diverse RM practices between collaboration parties • Need for explicit communication underestimated