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
.
TWiki
>
Main Web
>
PlmHome
>
PlmScenarios
>
PlmScenariosSiemens
(16 Mar 2010,
RainerE
)
(raw view)
In today’s product development, different engineering teams traditionally use independent tools that are specialized to engineering domains (mechanical, electrical/control, electronics, software).While the specialization of these tools has been proven locally efficient, it however contributes to fragmented results in Enterprise processes such as Requirement, Configuration and Change/Issue Management. The proposal of a federated (virtual) system that orchestrates local engineering processes, connects related artifacts and consolidate results would certainly improve that situation especially in the software development area where Change is a constant feature. Among others, the following areas of improvement can be considered, while preserving existing software engineering environments: * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Configuration/Change\Issue Management</span> * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Software change/issue management and Product change/issue management workflows integration </span> * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Software change implementation to be Product change impact analysis driven</span> * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Software change resulting artifacts integration to Product lifecycle management structures and related part revisions (artifacts: test results, binaries/firmware, interdependencies,…)</span> * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Management of software changes/Issues, tests in context of Product options & variants and requirements</span> * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Requirement Management</span> * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Interaction of the Issue tracking system (product and discipline level) and the requirements management system(s)</span> * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Interaction of the issue tracking and the requirements management systems with the test management system(s)</span> * <span style="font-size: 11pt; font-family: 'Calibri','sans-serif'">Interaction of the issue tracking, requirements and test management systems with the help desk systems (e.g. CRM)</span> All connections shall be implemented with light weight, loose coupling methods, but also allow transition to full detail origination of the artifacts. -- Main.RainerE - 15 Mar 2010
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 16 Mar 2010 - 08:47:53 -
RainerE
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
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