|
BPM for Systems Engineering |
|
|
|
|
Complex systems development efforts require robust and effective Systems Engineering processes. Such systems are typically decomposed into architectural segments and, just as frequently, those segments are contracted to different organizations. While these organizations may operate in a similar manner and have the same contextual understanding of the system's requirements, the ability to manage these requirements and their changes across organizational and architectural segments can mean the difference between success and failure. When work performed on different architectural segments is done with different processes or in multiple stove-piped information systems, common problems include:
- Lack of process visibility, which translates into less accurate or missing schedule updates
- Higher overhead, needed to manage the flow and translation of information across disparate systems, divisions and/or vendors
- More rework, often as the result of human error introduced from the symptoms listed above
All of this translates to higher cost for the customer and reduced competitive advantage for the performing organization(s).
A structured approach to addressing these challenges with BPM provides:
- More realistic schedules (and associated earned value) through greater process transparency
- Reduced overhead through the integration of back-end development tools and associated repositories
- Lower production maintenance costs through more effective and cost efficient change control
- Lower cost of quality through built in process auditing capabilities
RunningFix has successfully demonstrated BPM methods and technology for complex Systems Engineering requirements change control processes including back end integration with IBM's Telelogic DOORS requirements management tool.
Have questions? Please Contact Us. |
|
Last Updated on Thursday, 05 November 2009 19:40 |