This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
Today, different engineering disciplines in the product lifecycle (mechanical, electrical, software engineering) typically have independent systems to track issues, requirements, defects and other tasks. Moving everything to one single system is very costly and the universal system would not be as tightly integrated with the working level processes of the different disciplines. A federated (virtual) system which connects the artifacts in the currently existing (real) systems would help to improve: Traceability, Reporting, Automation in the Product and Application Lifecycle Management (PLM / ALM).
Among others the following areas can be considered:
- Interaction of Issues of an overall product issue tracking system with the discipline level issues tracking systems
- Interaction of the Issue tracking system (product and discipline level) and the requirements management system(s)
- Interaction of the issue tracking and the requirements management systems with the test management system(s)
- Interaction of the issue tracking, requirements and test management systems with the help desk systems (e.g. CRM)
Topic revision: r1 - 15 Mar 2010 - 17:32:20 - RainerE
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Main|
|
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback