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

2. 2 Companies needs Main needs –E–Effectiveness –E–Efficiency –T–Trust Sub-needs –T–Transparency –C–Common understanding –C–Consistency –T–Traceability –C–Controllability

3. 3 Progress in collaboration item coverage

4. 4

5. 5 Challenges in collaboration: A subset of the Collaboration Handbook 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 Architecture Lack of interface management Lack of common understanding of 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-operative work No consistency in engineering tasks Dependencies between teams not made explicit and managed Problem area Typical problems

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

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

8. 8 Collaboration management 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

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