Volere Requirements Specification Template

Internal objects/entities that are connected to this business event. For
example, both events 8 and 9 would be connected to an internal object
called road. In other words there is a need within the context to
remember information about roads and that information is relevant to
events 8 and 9 (and many other events as well). It is this identification
of common internal objects that provides a link between events.
Motivation
To identify logical chunks of the system that can be used as the basis for
discovering detailed requirements. These business events also provide the
subsystems that can be used as the basis for managing detailed analysis and
design.
Example
Event List
Event Name Input & Output
1. Weather Station transmits reading Weather Station Readings (in)
2. Weather Bureau forecasts weather District weather Forecast (in)
3. Road engineers advise changed roads Changed Road (in)
4. Road Engineering installs new weather New Weather Station (in)
station
5. Road Engineering changes weather station Changed Weather Station (in)
6. Time to test Weather Stations Failed Weather Station Alert (out)
7. Truck Depot changes a truck Truck Change (in)
Amended De-icing Schedule (out)
8. Time to detect icy roads Road De-icing Schedule (out)
9. Truck treats a road Treated Road (in)
10 Truck Depot reports problem with truck Truck Breakdown (in)
Amended Gritting Schedule (out)
11. Time to monitor road gritting Untreated Road Reminder (out)
Considerations
Attempting to list the business events is a way of testing the work context.
This activity uncovers uncertainty and misunderstanding about the project
and helps with precise communications.
Volere Template V6.1 Copyright © Atlantic Systems Guild 23
This template may be copied for internal use provided copyright is acknowledged