 |
Page History
...
Figure 1 below captures key activities and deliverables produced at the stages of the Requirements Elicitation effort.
Figure 2-1. Initial Stages of the Requirements Elicitation
...
April-June 2010 activities – towards a formalization approach
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:
- Support downstream software development efforts by handing over use case descriptions in a form that is more amenable to the designers and software developers; the aim is to support traceability from requirements via development to software testing;.
- Support easier navigation of the significant body of requirements and use cases in a way similar to the existing ontology-based approaches; this is needed to better manage use case artifacts so that they can be amended more easily and in a more controlled manner, according to the new requirements of stakeholders - – or extended with completely new use cases as new business requirements arise.
- Ensure that the formalization approach is aligned with the new SAIF developments,.
In order to address these formalization requirements, the following two techniques and approaches were applied, as part of the subsequent analyses:
...
These additional elements of the requirements elicitation effort are captured in Figure 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.
Anchor
