The Selection Tool provides support for a user to select a consistent sub-set of the FRAME Architecture (Functional View), and then to create one or more Physical Views of this sub-set.
The Selection Tool comprises TWO parts
Part 1 – The Tool itself
FRAME_Selection_Tool-setup – vPQR.zip – extract the exe file, execute it and follow the normal Windows Installer instructions.
Download 2.9MB (zip file)
Part 2 – The Database
FRAME_DB_vXYZ_ST….mdb where XYZ is the version number of the FRAME Architecture and this should be same as for the Browsing Tool.
Download 1.2MB (zip file)
NOTE – any execution of the Selection Tool will make changes to this database and so you are recommended to keep an unused “read only” copy in case you need to start again.
The Selection Tool should run on any PC with Windows XP, Windows Vista, Windows 7, Windows 8 or Windows 10.
If MS Access is not installed then you will need the “Access Database Engine” from here.
Using the Selection Tool
A new User Manual for this version of the Selection Tool is available, which provides brief explanations on how to use all the features.
Download 1MB (pdf file)
A more detailed Reference Manual on how to use the Selection Tool is also available. Whilst this was written for the previous version, most of its contents are still valid – but it is no longer complete. In particular, it contains a description on how to add extra elements to the FRAME Architecture database that are required for a specific deployment – this is not in the User Manual.
Download 6MB (pdf file)
The following is an overview of how the Selection Tool is intended to be used.
When creating a bespoke ITS Architecture from the FRAME Architecture the architecture team needs to select a sub-set of the FRAME Architecture and, possibly, add some extra functionality that us not currently present. This process is supported by the FRAME Selection Tool which contains a database with all the elements of the FRAME Architecture, and to which more can be added. This is illustrated in the following figure.
Use of the FRAME Selection Tool
The Tool does not perform any selections automatically, but it does support the architecture team in its use of the methodology in the following ways.
- The team selects those User Needs that reflect the Stakeholder Aspirations.
- The tool will then guide the architecture team to those parts of the Functional View that help to satisfy those User Needs.
- The FRAME Architecture does not claim to satisfy every possible ITS User Need, and in some circumstances it may be necessary to add extra User Needs and Functional View elements to the Selection Tool data base.
- Since the mapping from User Needs to Functions is not an exact science, the tool will probably report some logical inconsistencies after the first pass (e.g. a data flow with only the function at one end selected). The team can then select further elements, or deselect some of those already selected, until there are no logical consistency errors, and they are satisfied that their selection fully represents the Functional View needed to satisfy the Stakeholder Aspirations.
- Once a Functional View is considered acceptable, it can be used as the basis for one or more Physical Views. The architecture team does this by allocating functions and data stores to individual sub-systems, and to modules within them if required. Modules are used to partition the functionality in sub-systems so that, for example, the functionality for traffic management can be separated from that for parking management.
- Once a Physical View has been completed one of the reports available from the Selection Tool can be used to provide the starting point for an analysis of the Physical Data Flows. This leads to the creation of the Communications View, which shows the characteristics of the links required between each of the sub-systems and modules, plus those with the Terminators.
- An Organisational View can also be created from a Functional View.
- The Tool permits more than one Physical and/or Organisational View to be created from a Functional View so that the advantages and disadvantages of different component configurations, physical locations and deployment scenarios can be explored.
Thus, although the Selection Tool does not have any intelligence to make decisions on behalf of the architecture team, it does perform much of the detailed work of recording all the decisions taken by them. Experience has shown that it is not normally necessary to produce a Data Flow Diagram of the Function View since all the information required to produce a Physical View is held within the data base.