goodViberations: UI Specification

Introduction

The UI, described in this document, is used to render the data to the end user. The UI facilitates the user's interaction (CRUD) with the data. The actual work of creating new data, retrieving data, updating data, deleting data, and ensuring data integrity is specified in Functionality.html.

The data structures used in this app are described in DataLayer.html

This document lists the activities in the app, the widgets present in each activity.

Activity design

All the activity classes should be in the package com.j3t.dataentryapp.ui.activities
The activities wanted in this app are as follows:

Level 1 Activity

• MainActivity:Welcome Activity, level 1 activity
  1. open store, button
  2. create new store, button
  3. clear existing store, button
  4. import/export store, button
  5. about, button
  6. help, button

Level 2 Activities

• OpenStoreActivity:Open Store Activity, level 2 activity
  1. password, text field
  2. memorable date, text field
  3. open store button, button
  4. change store password, button
• CreateNewStoreActivity:Create New Store Activity, level 2 activity
  1. password, text field
  2. memorable date, text field
  3. confirm password, text field
  4. confirm memorable date, text field
  5. create store, button
• ChangeStorePasswordActivity:Change Store Password Activity, level 2 activity
  1. new password, text field
  2. new memorable date, text field
  3. confirm new password, text field
  4. confirm new memorable date<, text field/li>
  5. save changes, button
• ImportExportStoreActivity:Import/Export Store Activity, level 2 activity
  1. import store, button
  2. export store, button
• AboutActivity:About Activity, level 2 activity
  1. about text, html text
  2. copyright, text
  3. date, text
  4. build number, text
• HelpActivity:Help Activity, level 2 activity
  1. help text, html resource

Level 3 Activities

• ListEntriesActivity:List Entries Activity, level 3 activity
  1. Vertically scrolling list of single line text entries
  2. new entry, button
  3. exit, button

Level 4 Activities

• ViewEntryActivity:View Entry Activity, level 4 activity
  
  1. entry name, text
  2. creation date and time, text
  3. last modified date and time, text
  4. notes, multiline text
  5. password, text
  6. list of detail fields, vertical list of single line text entries
  7. delete, button
  8. edit, button
  9. exit, button
• AddEntryActivity:Add Entry Activity, level 4 activity
  
  1. entry name, text field
  2. creation date and time, text
  3. last modified date and time, text
  4. notes, multiline text area
  5. password, text field
  6. list of detail fields, vertical list of single line text field entries
  7. delete field, button
  8. add field, button
  9. save, button
  10. cancel, button
• DeleteEntryActivity:Delete Entry Activity, level 4 activity
  
  1. entry name, text field
  2. confirm delete, button
  3. cancel, button
• EditEntryActivity:Edit Entry Activity, level 4 activity
  
  1. entry name, text field
  2. creation date and time, text
  3. last modified date and time, text
  4. notes, multiline text area
  5. password, text field
  6. list of detail fields, vertical list of single line text field entries
  7. delete field, button
  8. add field, button
  9. save, button
  10. cancel, button
• SearchEntriesActivity:Search Entries Activity, level 4 activity
  
  1. entry name, text field
  2. search, button
  3. cancel, button

Misc. definitions

Some terms used in this project are defined below:

Entry

An entry is defined to be a set of text fields, each field has a name and a value. Some fields are unique to an entry type, some are common to all entries. Some field values reflect a data type, and so have a syntax associated with them. For example, email must be a valur email address syntax, url must be a valid http url syntax, name starts with an uppercase.