ardapekis / cs2340 Goto Github PK

This is an individual Android app homework problem. You will need to setup for development environment for Android development, then download the M3 resources zip file. Then, follow the instructions on the class wiki.

Decide which usability evaluation we will implement (heuristic evaluation, cognitive walk-through, or think-aloud protocol analysis) and flesh out the details

The M2 project zip file is available on t-square. Then, create an "original" branch to hold the initial project. The repo should then be uploaded to github.

Create UI Flow Diagram for M6

Allow users to specify a date range when looking at the list of reports

Create a pin on a map for every report
Allow users to select pins on a map to bring up a detailed report

Instructions from the wiki:

1. Create an opening or welcome screen which has options for Login and Registration. You may have some other method of differentiating login and registration, if you do not want an opening screen.
2. If someone selects Login, then you should display a way to enter the user name and password.
3. If someone requests login, you should check for the correct user name and password. For this first milestone, you may have a hard coded user with name "user" and password "pass" to check against.
4. If the login matches user name / password then go to your application. Otherwise, notify of the bad login attempt.
5. Canceling the login (press Cancel or going back a screen for example) will close out the login attempt , but no information is recorded and the application does not start up. Note here you are not explicitly required to have a cancel button, just a way to back out of the login.
6. Once in the application, there should be a way to logout. After logging out, the application should return to the welcome / opening page.

Analyze the application (using Intelli-J Lint) to ensure proper documentation and formatting

Brainstorm user stories to get an idea of what features are essential for our app. Then, each team member should pick one to elaborate on. See wiki for instructions. Make sure user stories follow required criteria.

Follow instructions in class wiki.

Figure out what a context diagram is, then make one.

Follow the instructions in the wiki for the M2 individual section. Make sure you are working on the master branch. Person numbers will be assigned alphabetically, check the team wiki page for an alphabetical list of team members. Then push your code to the Github repo. (If the code on Github changed in the meantime, you will need to pull first.) Finally, complete the build section of M2.

Create an input screen for new reports and add reports to the ones from the .csv

Create List View (Welcome Screen) and Detail View for M6

Create class (or method) to parse .csv for List and Detail Views for M6

Create individual UML sequence diagrams

Write individual case studies

Individuals need to create Who's Who pages for themselves.
Everyone should go to the team wiki page and fill in their own details.

Write individual contracts for methods within the application

Meet the other team and exchange code for review

NOW EXTRA CREDIT

Create individual Robustness Diagrams for M6

Allow users to view a graph of all reports in a date range

M2 will require collaboration via Github. All team members will need to have Github accounts.

Save data between app startups (including registered users and new reports not from the original .csv)

Draw up the UML class diagram

Write an individual JUnit test for a non-trivial method in the application

Write a usability report for the other team's application detailing at least three concerns

Review the application's code as a team and write the required forms (Summary Report, Issue Log, Typo List, etc.)

The actual Android project for our app will be created and this repo will be set up for the actual project.

Everyone needs to get together to fill out the team charter.
Charter discussion will happen in Clough Rm 246 at 10AM.