The Microsoft Access databases are the basic repository for ARC-IT definition. These databases are the source for the architecture content and website products. For the experienced architecture and database user, these databases provide the most flexible and powerful way to access ARC-IT content. Using the databases, one can generate queries and reports that extract a specific subset of the architecture and manipulate the data to tailor it for a particular application. Of course, care must be taken since it is also easy to generate invalid results without some background in the architecture definition and the underlying relational database design.
Compressed images of ARC-IT databases are at your disposal. Select links below to download and save the zip file onto your hard disk or other writeable media. Execute the file by double clicking on it and then save the databases (".accdb" files) on your hard disk or other writeable media. Once uncompressed and on your hard disk, Microsoft Access (or any other database system capable of importing the ACCDB format) may be used to open the databases.
The ARC-IT databases are:
|Communications||Defines all the communications protocols and related standards that have been identified to date for each of the ARC-IT interfaces.||10/29/2018|
|Enterprise||Defines the enterprise objects, resources, and coordination between the objects along with their connection to the Physical View components.||8/21/2018|
|Functional||Defines all the processes, data flows, and data stores in the ARC-IT Functional View. This also includes traceability for each process to the Requirements.||10/8/2018|
|Glossary||Defines all the Acronyms and Terms used on this website.||9/28/2017|
|Physical||Defines all physical objects, functional objects, interconnects, and information flows in the Physical View and their connection with the Functional View components.||10/9/2018|
|Planning||Defines the planning goals, objectives, and performance measures and their relationship to the service packages.||12/3/2018|
|Requirements||Defines the user needs for each service package and the functional requirements that support each need.||12/28/2017|
|Security||Defines the confidentiality, integrity, and availability analysis for each information flow triple. Defines device security classes and assigns these to each physical object, per service package.||9/26/2018|
|Service Packages||Defines the service packages and their relationship to the physical objects, functional objects, and information flows in the Physical View.||1/15/2018|