Page History

...

Activities and outcomes before April 2010

Significant effort has been made and a number of business analysts were involved in the early stages of the requirements elicitation initiative. This included interviews of stakeholders within and outside the caBIG community, as depicted by step 1 in Figure 2-1 below.

...

In order to address these formalization requirements, the following two techniques and approaches were applied, as part of the subsequent analyses:

• Wiki Markupuse case levelling approach, initially proposed by A. Cockburn \ [1\] and also used within NCI, augmented with the use of UML behavioural semantics, in particular sequence and activity diagramsunmigrated-wiki-markup
• use of the ISO RM-ODP standard, in particular the Enterprise Language \ [4\] concept of community, to provide a way of formally structuring use cases, in a manner suitable for the capture of business architecture artifacts, such as roles, policies and processes

These additional elements of the requirements elicitation effort are captured in Figure 2-2 below. They will be described in the remaining of the paper, illustrated through the use of a specific requirement and several related use cases.

Figure 2-2. Requirements Analysis Roadmap for ECCF Traceability

...