1 Assignment Information

2 Introduction

NOTE: read the whole assignment brief first before implementing it contains very important information

In this assignment you will be tasked with building an interactive database about GPUs (Graphics Processing Units) and the features they support. You will be expected to use a NoSQL type database as storage for this system. Your application must be capable of the following

• Add in a GPU with a series of features.
• Edit a currently existing GPU and its features.
• Be able to choose a set of supporting features and figure out which GPUs support them.

Your application will be similar to the format found at http://vulkan. gpuinfo.org/listreports.php

If you click on any of the GPUs listed here it will bring you to another page. The information we are interested in here is listed under the features tab. You are required to map six features of a GPU which are the following: geometryShader, tesselationShader, shaderInt16, sparseBinding, textureCompressionETC2, and vertexPipelineStoresAndAtomics. Each GPU stored should contain the information for these six properties.

When a GPU is added a user should be able to click a series of checkboxes (or similar) to enable or disable features. When an add button is clicked there should be no duplicate names in the database or preexisting objects in the database for that GPU.

The score for your application will depend on:

1. How fully featured, complete, and robust your code is. Along with howwell your UI is thought out (80%)
2. How well documented is your code

5 Coding Brackets

1. Bracket 1
   • Get the shell of the application with login/logout working
   • Generate a model that will store the information of a GPU: name, manufacturer, date issued.
   • Add the six properties listed in the introduction to the model of a GPU.
   • the GPU name should be the key for each GPU in the database.
2. Bracket 2
   • Build a UI form that will enable the user to add a GPU and all its information.
   • When the form is submitted the GPU should be added to the database.
3. Bracket 3 Prevent the overwriting of an object that is already in the database. Bracket Failure if object overwritten
   • Display a list of GPUs that are currently in the database by name only.
4. Bracket 4
   • Make the GPU name list a set of hyperlinks.
   • When a GPU name is clicked it should go to a seperate page showing the information and features for that GPU Bracket Failure if not on a seperate page
5. Bracket 5
   • Enable editing of a GPU in the database. The form or editing a GPU should be prepopulated with the existing information of the GPU in the database.
   • Editing must be done on a different page Bracket failure if not on a seperate page
6. Bracket 6
   • Enable the user to select the features to query by using checkboxes (or similar)
   • enable querying of the database using a boolean combination of user selected features.
7. Bracket 7 Add in a form that permits the user to choose two GPUs for comparison purposes.
   • When the comparison is triggered a seperate page should be displayed

Bracket Failure if not seperate page

• The feature by feature comparison of both GPUs should be shown on the seperate page.

8. Bracket 8
   • UI design: well thought out UI that is easy and intuitive to use.