1.) Overall dashboard, menu and navigation:
This page is the “landing page” for the users once he signs-in to the application. It should define the overall “look and feel” for the application.
Apart from the overall navigation menu (which will be used on all pages) it contains a dashboard view that gives the user an “at-a-glance” overview about all the data and important actions. Furthermore, it should contain a quicklink functionality for common tasks.
The detailed requirements are described in the chapter "2.2 Dashboard, menu and navigation" in the attached requirement specification.
Apart from the overall look & feel we would like you to spend a lot of thoughts on how to present the data the best way. We specify what kind of data we would like to see but it is up to you to choose the appropriate UI-elements, chart types, gauges, widgets, etc. in order to visually present the data in the best way. You can even combine dataset specified separately into the one element if you feel it makes sense. Let your creativity flow!
IMPORTANT UPDATE 31st of August:
In the requirement specification for the dashboard the financial chart has a very prominent position due to the fact that it is mentioned first and that an example chart is provided. However, information about the milestones and tasks is equally (if not more) important. Please consider this in your design proposal. Hence, the financial chart is an essential part of the dashboard but should attract less attention than the information that actually requires action from the user..
2.) Add contract dialogue
A new contract is added through the new contract dialogue as described in detail in chapter “2.3.3 Use Case – Add contract”. Please design a beautiful and user-friendly form/wizard for this task.
3.) Contract list view
The contract list view provides a list view on all contracts in the system. It is described in detail in chapter “2.3.2 Use Case – Contract list view” in the attached requirement specification. Please design the page with the list view (and feel free to add any other relevant elements or information you might think might be useful).
IMPORTANT: Chapter “2.7 General functional requirements” contains some overall requirements valid for all pages. Please make sure to incorporate these requirements into your design proposals.