 |
Page History
| Scrollbar |
|---|
| Page info | ||||
|---|---|---|---|---|
|
...
| Anchor | ||||
|---|---|---|---|---|
|
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 the fig 1 below.
As a result, a large number of requirements (100+) were identified and documented (see step 2a in fig 1 below) in the following NCI wikipages:
https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Initiatives_Requirements_Master_List
Each requirement was also translated into a use case, documented as narrative text but structured in a tabular form, according to the NCI template (step 2b).
Subsequently, a further analysis was needed to categorize these requirements. An initial analysis suggested structuring use cases in several stories, namely: domain user stories, forms stories, metadata specialist stories and developer stories (step 3). This were documented at:
https://wiki.nci.nih.gov/display/seminfra/User+Story+Draft
In addition, a user story matrix was produced showing this categorization in a tabular form, while also providing references to initial candidate services used to support each story. These candidate services are documented in the infrastructure category of the NCI Enterprise Services periodic table.
The Figure 1 captures key activities and deliverables produced at the stage of the Requirements Elicitation effort.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The sheer number of requirements, variety in use cases and the number of different users and systems to be developed to support these have highlighted the need to investigate formalization approaches. In particular, this was needed to:
...
