banner_image
 

Requirements Management

The requirements management discipline is concerned with specification of required systems behavior. In general requirements document what the software is intended to do, whereas architecture and design define how these requirements are to be implemented. System behavior may be documented at multiple levels of abstraction including business process models that define the business context in which the software is operated, to use case models that specify the interaction between actors and the system, down to very granular functional requirements.


There are three primary contexts in which requirements are important:

  • Engagement Management
  • Development
  • Governance
Requirement Management

Engagement managers evaluate requirements in the context of the triple constraint of cost, time and scope to ensure a quality product. For the development team, requirements shape the development of software; defining the content, boundaries and constraints for the software that is being developed and/or configured. The governance context is perhaps the least often discussed yet perhaps most important subject area in requirements management. It defines the ownership structure for the software requirements and hence the behavior of the system. This ownership is primarily vested in the owning business unit for the functions that are automated by the system; rather than ownership by the IT organization. The roles, responsibilities, tasks and associated deliverables for each context are elaborated in subsequent pages.

Requirement Management 2

With the paradigm shift toward business-driven architecture, our Requirements Management Group combines requirements analysis with business process modeling to capture business requirements and translate them into technology requirements. When available, industry reference models can accelerate requirements analysis and business process modeling, while ensuring design compatibility with industry standard business processes and information exchange formats. Adequate requirements analysis and business process modeling is a prerequisite for designing a system architecture that meets the business requirements.