shawnmaten / cs3773project Goto Github PK

Create an Activity class and associated view that will display a list of all employees in the database. This will be a ListView and each list item can be clicked to proceed to another Activity with details and options for that employee.

Follow this tutorial. This story is finished when we have a database and can run some sample code to test it in some way to know that it's "active" and "working".

• Create a backlog to contain all the use case (stories). Assign story points to each
  story. All the stories in the backlog will be prioritized.
• Create a Taskboard to show all the tasks to be completed for each story. Create a
  task table to contain all the tasks. Show a task number, a task name, a brief
  description of each task, and the related use cases for each task in the task table.

Develop/consolidate a UML use case diagram, showing all identified use cases,
along with a brief description of the use case diagram.

Create an Activity class and associated view for the login. A user will be presented with a screen that has a username and password field with a submit button. On submission it will check against the DB and present a Toast that says success or failure.

See issue #14. Essentially the same except fewer abilities. We may use same code for issue #14 & #15.

Add methods to SQLLite classes to handle editing employee info, this may be one method with options or multiple methods.

Add method to SQLLite code to handle removing a user from the database. Must handle removing employee properly from all tables in DB and there may be additional checks for this to prevent things from failing.

Build a UML class diagram for the whole system, showing all identified classes
and their attributes and operations, all actors, relations, and multiplicities. Include
a discussion of the class diagram.

Hardcode in (either by having the DB pre-populated or having code run every time on initial launch to insert data) a master login. This will be like an admin or root user.

This is just us physically using a device or emulator and entering the correct info, which should get us a "success" message and entering incorrect info which should get us a "failure" message.

Create an Activity and corresponding view to display an individual employee's info and edit the info or delete the employee. This will be the same as the Activity / view for normal employees except that it allow the changing of employee roles and deleting an employee completely. We may use the same files for both of these and just test for who's viewing.

For each use case, build a sequence diagram for its normal scenario.

Should be pretty simple. Choose a basic template in Android Studio and set the API levels. Create the project. Run it in the emulator. Push to GitHub. Make sure everyone can pull and run it.

For each use case, give a detail description in a tabular format to include a use
case number, a meaningful use case name, the actors of who initiate and
participate in the use case, the pre/post conditions, the related requirements and
other use cases.

The TA said Dr. Niu will ask about this.