Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Satellite Systems: Requirements Management (Part 2)
Satellite systems are a reality of the corporate information systems landscape. The request to include and integrate such systems into a larger business and application framework must ideally be governed by a requirements management process that addresses accountability, architecture and analysis. Here are some aspects to consider:
Accountability: Assign strong functional ownership at an end-state business function-level
Establish clear accountability for requirements each time you get hit up with a request to include an additional system. Don’t name an owner for the satellite system alone (e.g. the group/person requesting it!). Instead, aim for an owner/caretaker identified at a higher, business function-level that is clearly functionally accountable at a business unit or function level.
It is imperative to have strong functional domain owner responsible for the end-state business solution as opposed to spawning individual fiefdoms, which can lead to multiple owners and drivers for each of the sub-systems being tagged on. That said, establishing this kind of accountability is not always easy in a corporate environment. Issues of command, control and power are bound to come into play. While you’d not want to attempt addressing these within the scope of the project, do ensure that you walk away with the one key requirement for accountability: A …
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"You're talking to someone who really understands rock music." - Tipper Gore |