The following is a summary of how the requirements in section 3.8 will be met by the design.
The development will be divided into two phases:
User Guardian will be built with a homepage and web based navigation to the separate parts of the system. These screens should be clear to navigate for the user. A map of the navigation screens will be created to assist in the design. If time permits feedback from the focus group on the clarity of the design could be undertaken.
A UML database diagram will list the tables required for the SoD sections of the system, as this a fairly complex activity. This UML diagram will form the design for the backend database of the system.
The prototype user data will be created in Excel CSV files, based on the table structures set out in the database UML diagram. The Excel list can then be imported quickly into the database for testing.
The Users of the Application
The requirements highlighted the compliance user as the main user of the prototype version of User Guardian. An Agile user story will be used to describe how the prototype version will work, with a narrative and goal.
The user story will be important in the second phase of the development after the PoC database has been completed.
Functions to Develop - Inside the Project Scope
A UML activity diagram and class diagram will be used to describe the objects to include in the programming of the tool. A more Agile approach will then be taken on how these objects will be coded to work with each other as the project evolves. The UML will act as a framework of items to include in the development, and forms the basis of the first PoC phase of the development.
To further support the Agile approach in the second development phase each screen of User Guardian will be visually mocked-up to provide the navigation map and describe the purpose of each section of the system and how the user would interact with it.