| 1.2.3 |
Systems that conform to the Framework Architecture needs to be able to exchange information in a manner that permits a given geographic location to be understood by all parties. |
Communications Requirement |
Systems shall exchange geographical location information according to international standards |
Data Object (Information Object) |
The information that the systems exchange must comply with ISO 19115 and ISO/TC 211 |
| 1.2.4 |
Systems that conform to the Framework Architecture needs to be able to exchange information in a manner that permits road and traffic conditions to be understood by all parties. |
Communications Requirement |
Systems shall exchange road and traffic conditions information according to international standards |
Data Object (Information Object) |
The information that the systems exchange must comply with ISO 14819 |
| 1.2.5 |
Systems that conform to the Framework Architecture shall needs to be able to incidents, their severity and reference their locations in a standard way. |
Communications Requirement |
Systems shall exchange incident information according to international standards |
Data Object (Information Object) |
The information that the systems exchange must comply with IEEE 1512 |
| 1.2.8 |
Systems that conform to the Framework Architecture needs to be able to provide coherent and consistent advice to all drivers affected by an incident or congestion. |
Communications Requirement |
Systems shall exchange road and traffic conditions information according to international standards |
Data Object (Information Object) |
The information that the systems exchange must comply with ISO 14819 |
| 1.3.1 |
Systems that conform to the Framework Architecture needs to be able to provide facilities that accommodate the needs of disabled and elderly persons, when relevant. |
Physical Requirement |
Devices shall be accessible for disabled and elderly persons, information should be delivered via alternative mediums such as sound / tactile |
Component |
The access device must be within reach of persons with wheelchair, the status of the access attempt (access granted / denied) must be announced via voice |
| 1.6.7 |
Systems upgraded to conform to the Framework Architecture, and providing the same services, needs to be able to produce financial benefit to their owners. |
Organizational Requirement |
Users of the service shall be subject to monthly / yearly subscription |
Agreement |
Service Usage Contract |
| 1.3.2 |
Systems that conform to the Framework Architecture needs to be able to provide facilities to enable data about the travel network to be entered and updated. |
Functional Requirement |
The system shall be able to provide following facility:(1) the ability to enter data about the travel network(2) the ability to update information when a change occurs |
Low Level Function |
|
| 1.3.7 |
Systems developed from the Framework Architecture needs to be able to use a digital map which contains the necessary additional data, e.g. speed limits, curvature of corners, (bus) lanes, traffic signals. |
Functional Requirement |
The system shall be able to provide following facility: (1) the ability to use digital maps(2) the ability to provide additional data (speed limits, traffic signals etc.) |
Low Level Function |
|
| 1.10.2 |
Systems that conform to the Framework Architecture needs to be able to monitor each safetyrelated component (including software), warn the user in case of problems, and disable it, or reduce it to a safe state. |
Functional Requirement |
The system shall be able to provide following facility: (1) the ability to monitor and diagnose its own components(2) the ability to warn user in case of problems(3) the ability to disable or reduce service |
Low Level Function |
|
There are some User Needs which are not related to any function but nevertheless should be taken into consideration while building the services. These user needs have implications on the physical view, communications view or organizational view.
There is a gap in FRAME regarding these User Needs, there is no mechanism specified on how these User Needs will effect the sub-set architectures or the systems to be produced.
Therefore it might be practical to introduce the use of High Level Requirements. User Needs would be tied to those requirements and in turn these requirements will state how the systems should be built or the actors should behave.
Below are some examples on how this may be applied
related excel spreadsheet
This issue is also related to issue #40 ,
If we are going to handle the High Level Requirements as described above, the Functional Requirements have to be taken out of the Low Level Function and assigned to another object called High Level Functional Requirement.