Embedded Files
12/7 Evaluation Process and Finishing Touches
12/7 Evaluation Process and Finishing Touches
We are ready to present our group project and are finishing the evaluation process for the web application. One major aspect of the evaluation plan that took time to figure out was how we would conduct our study.
The sample size we could gather was six participants, so a between group study would not be feasible. A within group study would also be difficult to conduct because the users have very different experiences with physical therapy and using technology; therefore, it is difficult to find a tool to compare all or even one of our use cases to among all the participants. We concluded that a qualitative oral interview would be best. We would ask participants about what they typically do for their physical therapy routine and compare their previous experiences with out web application.
11/30 Preparing for our final presentation
11/30 Preparing for our final presentation
So far our team has...
Completed the the landing page, as well as login/logout/register and user session features.
Completed the first use case, 'doing a physical therapy session' . The user can create a routine with various exercises and follow along on the application.
Created a counter to track how many times the user completes a physical therapy session. We plan on further developing the progress dashboard and possibly including a calendar that display when and how often the user records a physical therapy session.
Created a forum for users to communicate with one another within the application. We plan on further developing this to provide more fluid and organized communication between users.
We are currently working on implementing a live group video session via Zoom. This week we intend to begin conducting evaluations, completing our final project report, as well as our demo video for our final presentation.
11/23 Building the web application
11/23 Building the web application
We are currently working on implementing many of the functions in our use cases for the web application
Progress summary
Create a progress counter to track the number of physical therapy sessions completed to motivate the user.
Group physical therapy session
We intend to allow the user to create, view, register, and delete a group physical therapy session
For the prototype we will not implement our own web conferencing, but prompt the user to insert their own web conference link
Forum
The forum will allow users to talk with one another and schedule group physical therapy sessions
Forget password
In case the user forgets their password, they can reset it
11/16 Account management and our first use case
11/16 Account management and our first use case
We are working on our first user case: doing a physical therapy session. Kelley has laid out the structure for our exercise database and the design for the exercise session. Peirong has organized the user database and how data will be stored for each user session. She has also set up the functions for the log in, sign up, and log out pages. Natalie has finished the home page, which contains an 'about us' section, and displays the Volere shells we created for our project. She has also designed the log in and sign up pages.
Tomorrow, we plan on meeting again to focus on completing this use case together as soon as we can. By the end of this week, we plan on finalizing the process of doing a physical therapy session, and begin the progress dashboard use case.
11/9: Learning new tools
11/9: Learning new tools
This week took the time to learn how to new tools that would help us build a web application. We used Miguel Grinberg's blog and Codemy's tutorial on how to use Python with the Flask microframework. The blog does a very thorough explanation on how to construct a simple application structure as well as account management. Codemy has a good explanation on how to implement CRUD (create, read, update, and delete) functions for a database within the web application.
We also improved the design of the data model to include classes beyond the User class.
Link to the blog: https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-i-hello-world
Link to Codemy videos: https://www.youtube.com/watch?v=hbDRTZarMUw&t=708s
11/2: We found Figma!
11/2: We found Figma!
We've began concretely designing and building our Physical Therapy website, particularly focusing on the home page, login/signup, and the major use case of "doing a PT session." To do this, we found a very helpful software called Figma that allows all of us to collaborate on the same project file. There we can construct several interface designs which can then be directly converted to HTML & CSS and published online. We expect that we'll have to refine this automatically-generated code, especially when it comes to implementing database functionality, but nevertheless this will definitely help save us time and spare us some tedious coding.
We also decided on some style guidelines so as to keep our application consistent throughout. Notably, we opted to use the font "Open Sans" and are implementing a turquoise/blue color scheme (see below). These styles will give our web app a modern, professional, and energizing feel. The color scheme also helps with usability because it is shaded on a gradient so people who are color blind can view more easily.
We met over Zoom on Thursday, Saturday, and Sunday to plan and get feedback from each other. Apart from our meetings, we have been working asynchronously with Natalie focusing on the home page, Peirong working on the signup/login and incorporating database functionality for that, and Kelley designing the screens directly related to doing a PT session.
10/27: Assignment 8
10/27: Assignment 8
Below are the major details of our implementation plan, pulled from Assignment 8:
Development Environment
Development Tools
Web Development IDEs we use: Visual Studio, Sublime, Dreamweaver
Hardware
Our personal laptops: Mac laptop, Dell laptop
Programming Languages
HTML, CSS, JavaScript (jQuery), Flask microframework (uses Python), SQL
Version Control Tool
Github: this will also allow us to easily share our code with each other
Main Tasks for Development
Database
e has specifically taken a databases course (CSC261)
We will need a database for PT exercises, PT routines (specific list of PT exercises), and completed PT sessions (an instance of completing a specific PT routine)
Front-end
All of us will contribute to frontend
We will create a working design guidelines document to keep the feel of the app consistent throughout screens
Kelley and Natalie can make visual assets and graphics using Adobe Illustrator
Back-end
Natalie and Kelley will specialize in back-end since they are both taking a Web Programming course (CSC210)
We will likely publish our app using the UR Digital Scholar FTP service
Testing:
Unit Test: 11/7
Integrated Test: 11/13
Weekly Timeline
Our weekly timeline is updated on our shared Google Calendar which is posted on the 'Calendar' page of this site.
Three Main Use Cases
Doing a PT session
Viewing one's progress
Social interaction with other users
Page updated
Report abuse