Jump to content

User:OseAITEC4550Spring2015

From Wikipedia, the free encyclopedia

Description

[edit]

Sign in Sheet is an app that is meant to replace the paper sign in sheet professors use to take roll call in class. Its functionality is simple: When the app first opens the professor is presented with a list view of several activities they can perform. This main activities include:

  • Set class and date

- This activity lets the professor set the course and date for the roll call.

  • Student sign in

- This activity lets students who are present sign in manually (if they don’t have and NFC tag) or scan their NFC tag.

  • Access database

- This activity is meant only for the professor and to ensure this it is hidden until after the professor scans their NFC tag with their password or enters it manually. Once granted access via password verification the professor can see all the students on the sign in sheet. The professors options with the list include: Delete single students from the list or clear the entire list.

Requirements Summary

[edit]
  • The professor’s password will be stored on a text file online. The reason being, since I want to include restful programming but don’t have access to a database online this is my next best option to ensure some sort of security.
  • Students who are using an NFC tag to sign in will need to know the format (#9000 first_Name last_Name) on how to store their information on it.
  • Students and professors will need access to an NFC writing app (there are a few available on the google play store) to be able to write their information to an NFC tag.

Screen Flow

[edit]

Demonstration

[edit]

Issues

[edit]
  • When i first created the beta version i ran into an issue using list view to display the main activities. The problem was that with list view since i had only three items in the list the was excess space left at the bottom of the screen.
  • To resolve this issue i had to create a custom adaptive class.

List of items not covered

[edit]
  • I covered every item that was in my proposal.

List of platforms/devices covered

[edit]

The app was built to work on Smart phones or Tablets with android operating system.As a result of responsive design the app looks the same on:

  • Android tablets
  • Android smart phones

Test Plan

[edit]
  • Phase one = Test each activity screen to make sure they display as designed
  • Phase two = Test design to see how it response on different screen sizes
  • Phase three = Test user inputs
  • Phase four = Test system outputs

List of 8 major concepts covered

[edit]
  • Multiple activities
  1. The entire app is made up of a series of activities.
  • Custom launcher icon
  1. At 0:00 of demo video part1A
  • List View
  1. At 0:23 of demo video part1A
  • NFC
  1. At 2:10 & 3:45 of demo video part1A
  • Database & Shared preferences to store persistent data
  1. At 2:57 of demo video part1A
  • Dialog box
  1. At 3:06 of demo video part1A
  • RESTful programming
  1. All of demo video part1B demonstrates restful programming.
  • Date picker
  1. At 1:00 of demo video part1A
  • Responsive design
  1. Demo video part 2 displays this by showing how the app looks the same on a smaller device.

Expansion topic

[edit]
  • NFC
  1. At 2:10 & 3:45 of demo video part1A

References

[edit]
  1. Credit on how to implement NFC
  2. Dr. Lutz on restful programming example.

Passwords

[edit]

Link to text file containing passwords