Abstract
In this paper, a diagrammatic representation of the main processes occurring in Requirements Engineering has been introduced. Adopted style has been derived by the notorious London Tube Map: it allows practitioners, academics and all stakeholders to fully appreciate the complex set of iterations as they occur during any software development project.
Some benefits have been discussed: non technical stakeholders can be provided with a simple and yet effective tool to communicate among each other; requirements engineers and analysts can easily track their activities; academics can use the map for teaching purposes as well as to remind themselves what practical help they can provide against the expected outcomes RE community would look for.
Potential developments of the map are its transformation into a system integrator, in order to facilitate practitioners in managing the fragmentation of the discipline; and the possibility of the map to become a virtual “gate” to any knowledge repository which emerges within any development project.
Some benefits have been discussed: non technical stakeholders can be provided with a simple and yet effective tool to communicate among each other; requirements engineers and analysts can easily track their activities; academics can use the map for teaching purposes as well as to remind themselves what practical help they can provide against the expected outcomes RE community would look for.
Potential developments of the map are its transformation into a system integrator, in order to facilitate practitioners in managing the fragmentation of the discipline; and the possibility of the map to become a virtual “gate” to any knowledge repository which emerges within any development project.
| Original language | English |
|---|---|
| Article number | 8 |
| Pages (from-to) | 35-40 |
| Number of pages | 6 |
| Journal | InterJRI - computer science and networking |
| Volume | 2 |
| Issue number | 1 |
| Publication status | Published - 2010 |