Return & Report

Final Project Presentation

Return & Report was an idea that came to life by recognizing a real need amongst my own, real-world, experiences. As I serve and participate in local groups, boards and councils affiliated with The Church of Jesus Christ of Latter-day Saints, I realized that our group did not have a standard for project planning, tracking and various other leadership responsibilities.

As I've spent the last few years being a big supporter of the new Gospel Living (Circles) App, I thought it could use some new integrations. So, Return & Report is a project management application that is focused on integrating into the already existing Circles and other Church authenticated sites.

Our test case assumes that a user has already created an account, however the queries to create a user are still included, for representational purposes.

As you go through the inter-active UI you'll see that it is focused around a mobile application, however the screens have been widened to also include the appropriate CRUD statements.

UI Index:

You'll start at the login page, and then you can simply follow the form application through to:

login ->
start planning a project ->
add new project form ->
view project/ add tasks ->
create and assign project tasks ->
view project and available tasks ...
- From there you can choose to edit the newly created task, or edit the parent project, or continue to add more tasks ->
If you click on the top header "Return & Report" you'll get a view of all projects that this user belongs to/ has access to ->
from there you can click the < nav arrow and be taken up one layer to where you can view all of the circle groups that the user is a part of.

Design Rationale:

The rationale for the design was based on the already exisiting UI elements, from within the production Circles App. Beyond that, I wanted to show that a single user can belong to multiple Circles Groups, and each group can have multiple project workspaces, and then within each project there can be several tasks. The tasks can be assigned to someone who becomes the task "owner". The tasks also integrate a status, which could be expounded upon in a production application, for now it is represented within the UI by a green/yellow/red circle. The status is a working table that is referenced when a user selects one of the circle status markers, then the task would use an

UPDATE

to add the foreign table id as a reference to the project task.

UI Prototype:

Wire Frames

Final Project

CIT 225 Database Design & Dev

Menu

UI Prototype:

Inclusions:

Test Case:

Wire Frame Walk Thru

ERD

Reflect: