5.2 Proof of Concept Database Build

The Proof of Concept (PoC) was carried out on a standard PC running Access 2010. Please see the downloads section at the bottom of this page for the working Access database file used in the development.

Development Methodology

The PoC used the Waterfall model of development. With this in mind the database was built using the design set out in the database diagram in section 4.1.2 https://sites.google.com/site/userguardian1/4-design/4-3-database-diagram and the class diagram in section 4.1.4 https://sites.google.com/site/userguardian1/4-design/4-1-5-class-diagram.

Test Data

The test data was manually created in Excel for import into the database as CSV files. The CSV's contain a header row to set up the column names within the tables. The actual CSV used files have been uploaded to this page.

How the Design Fits the Implementation

The following table (Table 21) shows the breakdown of a subset of tables translated from the design to the Access Database version. This process was created for all the tables.

Table 21 - Database Implementation Table Summary

Query Creation

The query parts of the system in Figure 31 work by joining tables/information together. In the Access version this was done for operations of "Assigning roles to users" and "Creation of Toxic". These activities in the production system would be performed by the user, the queries would operate in the background to create new tables for the reporting.

This is shown in the Class diagram where these activities are listed as "ToxicList" and "Business User Groups" and precede the reports output. These operations would be carried out as the user interacts with the system as described in the activity diagram in section 4.1.3.

Figure 31 - Assigning the Users to Business Roles and Creating the Role Based Toxic Access Combinations

The Reports Output

The final part of the PoC is to produce the compliance report "Reports Output" based on the product from the two queries/table creations. This was done by joining the information between the two queries as shown in Figure 32.

Figure 32 - Report Showing Where User Access Are Breaching Compliance