1. TaskerCLI User Interface

2. FR8 User Identification TaskerCLI E-mail address E-mail: Password Password: Log in Remember me next time Authentication is optional here We could have an application logo? Creates some element of branding. Are we going to use the brand name (‘Tasker’) Or the application codename (‘TaskerCLI’)? TaskerCLI – Authentication failed Your e-mail address or password was incorrect. Please try again. ! OK Throw error dialog if credentials are incorrect

3. TaskerCLI data We have this data: Tasks(read-only) Title(read-only) Allocated team member(read-only) Start date(read-only) Expected completion date(read-only) Actual completion date?(changed by event -> on status set to ‘completed’) Status (enum)(editable by assignee) Allocated (in progress) Abandoned Completed Task elements(read-only) Textual description of a step in the task Has comment field for assigned user(editable by assignee)

4. TaskerCLI, main window after authentication TaskerCLI Design database schema 13 October 2015 4 days left ! Design UI for application 1 October 2015 3 days overdue Create QA docs 13 September 2015 Abandoned Think of an app idea 5 September 2015 Completed Task list: Tasks that are ‘allocated’ (not completed/abandoned) are on top Allocated tasks are sorted by number of days left from expected completion date Other tasks are sorted by start date Overdue tasks (past expected completion date) get a visual indicator The active task has a grey background Completed/abandoned tasks are no longer editable so are greyed out Synchronizing tasks with server… File Help Status bar communicates sync state to the user (add progress bar maybe?)

5. TaskerCLI, main window after authentication TaskerCLI Design database schema 13 October 2015 4 days left ! Design UI for application 1 October 2015 3 days overdue Create QA docs 13 September 2015 Abandoned Think of an app idea 5 September 2015 Completed Task last synced 23 seconds ago. File Help Expected completion date: 10 October 2015 Steps 1.Read requirements spec 2.Identify UI window scenarios 3.Mock up the UI windows Allocated Status: Have read requirements specifications, enquire to project client about ambiguities. No comment entered yet. Have created these: -Log in splash screen -Main window of application -Menu bar contents Synchronize with server Log out and exit Exit Comment boxes don’t fully collapse if empty Task step comment fields ‘File’ menu handles synchronisation actions The task should sync to the server at a regular interval when editing the task locally (every minute or so) and the status bar should give some sort of illusion of saving

6. TaskerCLI, changing task status TaskerCLI Design database schema 13 October 2015 4 days left ! Design UI for application 1 October 2015 3 days overdue Create QA docs 13 September 2015 Abandoned Think of an app idea 5 September 2015 Completed Task last synced 1 minute ago. File Help Expected completion date: 10 October 2015 Steps 1.Read requirements spec 2.Identify UI window scenarios 3.Mock up the UI windows Completed Status: Have read requirements specifications, enquire to project client about ambiguities. No comment entered yet. Have created these: -Log in splash screen -Main window of application -Menu bar contents

7. TaskerCLI, changing task status TaskerCLI Design database schema 13 October 2015 4 days left Design UI for application 1 October 2015 Completed Create QA docs 13 September 2015 Abandoned Think of an app idea 5 September 2015 Completed Task was just synced to server. File Help Expected completion date: 10 October 2015 Actual completion date: 13 October 2015 Steps 1.Read requirements spec 2.Identify UI window scenarios 3.Mock up the UI windows Completed Status: Have read requirements specifications, enquire to project client about ambiguities. No comment entered yet. Have created these: -Log in splash screen -Main window of application -Menu bar contents