Dear BA experts,
Happy Boxing Day!
I would like to ask if anyone has approached system* requirements gathering and documentation, from a 'capability centric' perspective, and any comments/ advise would be greatly appreciated.
A bit of background context for my question:
1. The Requirements deliverable will be used firstly for Procurement (forming a basis for contractual Statement(s) of Work), but further on to guide and define the scope of systems delivery/implementation.
2. Due to the sector-wide nature of my organization, the 'Enterprise' within which these capabilities will operate is wide-ranging & heterogenous, furthermore is not expected to achieve much process alignment or standardization.
3 'Best practice' processes within this industry (Healthcare) are evolving and thus ideally the requirements will support processes/use cases which have yet to be stabilized.
Given this context of requirements development, the suggestion is to describe the desired Solution Requirements in 'capability terms', anticipating a severely limited ability to document & validate against target Business Processes / Use Cases due to factors 2 & 3 above.
Questions:
1. Although I foresee that we will be able to generate a decent description of the proposed system capabilities, what can I do to ensure 'Completeness' and 'Correctness' against the (as of yet undefined) Context of Use?
2. Are there any considerations as to the actual documentation style/form for capability based requirements? [Our default form of requirements capture would be in inventorised 'Requirement Statements' using structured sentences]. I am open to alternative methods to describe system capabilities, as long as it can be captured in a conceptual & product-agnostic manner.
* Note; the word 'system' is used here primarily to denote that the primary target of the requirements will eventually be an IT system (not process or org changes). Neverthless It is intended that the requirements remain focussed on the business' functional & data needs and less concerned with detailing a specific system design.