Skip to content

Latest commit

 

History

History
107 lines (72 loc) · 13.7 KB

File metadata and controls

107 lines (72 loc) · 13.7 KB

Q: Do tutors have a set schedule that doesn't change from week to week?
A: Yes, tutors set a schedule at the beginning of each term and work the same hours in the tutoring center between weeks 2 or 3 to the week before finals. Tutors can work during finals week if they choose.

Q: You include "service alerts" as a part of real-time availability. Can you provide examples of when service alerts would be needed?
A: Sure, there are times when tutors are running late or take a sick day and busy times when tutors stay past their normal work hours. When availability changes from regularly posted times, we want students to easily find that information.

Q: When you mention normal work hours, are you referring to tutors that are present in the tutoring center?
A: Yes, we currently offer no online tutoring so our tutors are only working in the center.

Q: You want a quick response time for scheduling requests. Is there a time window you consider "quick"?
A: There is no time requirement, we just want something faster than our current process. We want to expedite the process with an online feature that somehow alerts tutors when requests are made. There could possibly be a priority feature for last minute requests but we will let your team decide if that makes sense from a design standpoint.

Q: Should there be any restrictions on appointment requests, such as needing to book 24 hours in advance? What about cancellation policies or missed appointments?
A: 24 hours might be too long because students have last minute needs. There should be a reasonable window that is longer than a few hours but not quite an entire day. Cancellation requests should be requested within a wider window but can be done at any time leading up the appointment. We do think it would be a good idea to somehow track whether a student attends the online session. And perhaps revoke the ability to make an appointment for the remainder of the term if a number of sessions are missed without proper cancellation.

Q: If a student has an appointment with a tutor who can't make the originally scheduled time slot, should the student be notified about a "service alert"? How should they be notified?
A: Tutors should also have a way to cancel appointments, and this could go through the same system as students. However, there is no punishment for tutors that need to cancel.

Q: Will notifications for certain "service alerts", including appointment confirmations, be sent through email or a similar service?
A: The simplest route would be messaging and alerts send to the registered email. We would love to see a messaging system within the application, simply for the convenience, but would be satisfied with either implementation, as long as something exists.

Q: Should tutoring requests be a specified amount of time 30 minutes, 1 hour?
A: Realistically, a session would likely be at least 30 minutes long. Maybe sessions can be booked in 30 minute increments. The entire time does not need to be used and there is no penalization for only taking some of the session time.

Q: Can online sessions be scheduled during times the tutor is in the tutoring center?
A: We feel this would complicate things and make it unfair for students that just want to drop-in. At this time, online sessions should only be available when a tutor is out of the tutoring center. Let's leave open the possibility of taking a different approach here.

Q: Should there be real time updates on the current status of a tutor? E.g a tutor is offline, online or currently helping a student?
A: We think this could be a helpful feature.

Q: During an active time slot that a tutor isn't working with another student, will there be an option for drop in tutoring via text, audio or video chat if a tutor is online?
A: As we stated earlier, online sessions should not be scheduled during times a tutor is in the center. However, we don't oppose an online "drop-in" feature where students can ask a quick question. This would tie in with the feature you mentioned previously. This is something to note in a FAQ, that drop-ins are on a limited basis and scheduled sessions are recommended, as students in the tutoring center would take precedence.

Q: How advanced an interface do you want for online tutoring? Should we implement chat, video, audio? Is there screen sharing capability or some way to share documents?
A: An ideal interface would have a way for students and tutors to share documents to make sessions flow easily. We like the interface used on Chegg.com, where tutors use a virtual whiteboard, or chat via text, audio or video. However, we are primarily focused on the virtual whiteboard and chat via text at this time. We would also like language filtering to ensure no one abuses the system.

Q: Can you tell us more about tutor time sheets? How is this information used?
A: Currently, our tutors track their work hours on paper. We would like to move this online. Online session time should be logged automatically and we don't want tutors to edit these times. Other hours can be entered manually or based on current scheduling.

Q: You mentioned analyzing session information for professors. Can you elaborate?
A: We want tutors to keep a record of classes tutored and general information that was covered during sessions. This can provide valuable insight to faculty in terms of seeing student needs and considering those needs in course design.

Q: How do you want tutors to record session information? Should this be manual input?
A: We will let your team decide on the best approach here. Classes tutored could be chosen from a list of options, but it might be best to allow manual input for topics covered, since needs would vary and may be specific. The length of sessions should be automatically generated.

Q: Do you need us to store additional information like chat logs?
A: We don't want any information aside from session length, class tutored, and a short descriptor of what was covered. We want to grant students and tutors privacy so that everyone is comfortable in their interactions.

Q: How would you like us to analyze the results for professors? Are you thinking graphs? And we noticed you mentioned predictive analysis.
A: Data should be displayed on visually appealing graphs and be generated quickly and easily. We don't want to open up a page in the browser or redirect the user every time a new graph is chosen. Because it takes time to gather useful data, we would like a system that can recognize patterns and predict future student needs.

Q: Is there a specific way you want to display data? Should it be searchable by class? School term? Week? Etc?
A: There should be some sorting going on. We would like professors to see term-specific data but they should also be able to see all data, or a time window of data, to analyze long-term trends. They should definitely be able to view data by class name and I think data by day and week is implied, so we're not sure if that needs to be a specific feature.

Q: It sounds like tutors also assist in grading. Can you tell us what you would like to see in a professor-grading request feature?
A: In person, a professor and tutor should have already connected so that a tutor knows grading will be expected. And professors have to grant the tutor access to the course material they are grading of course. In the application, we would like a simple feature where professors can request grading and a messaging or comment feature to elaborate on other needs such as preferred finish by date or things the tutor should know.

Q: Should there be any restrictions on how many grading assignments can be given at one time?
A: Good question, we didn't consider that! It might be a good idea to somehow let the professor know how many grading tasks are currently assigned to a tutor so that no tutor is overwhelmed. This would also help in dividing work evenly when there are multiple tutors to choose from. And maybe there should be some type of confirmation that everything was received on both sides of the communication.

Q: Can you elaborate on the additional student resources for the application?
A: A weighted grade calculator, an overall GPA calculator, and a calculator that determines what grade is needed on the final based on current grade and exam weight.

Q: Let's discuss the login features. First, who needs login capabilities?
A: Students, tutors, professors, and administrators.

Q: Which features are accessible without logging in?
A: All visitors can view real-time tutoring availability, FAQs about the application, and use calculators and other bonus resources. Anything that requires tracking will require registration and logging in.

Q: Who is allowed to register?
A: Anyone with a valid WOU email can register. The registration process should validate this information. We are dealing with student information here, so we need your team to make security a top priority. Passwords should be secure and not stored "as-is". We also don't think you should use V-numbers. An email should be enough and you can assign IDs as needed within the system.

Q: You said that an email should be enough. Do you want us to require other information such as name or student standing for registration? Should we ask for any information that could be used to generate insights for professors?
A: First and last name, WOU email, password and password confirmation should be required. Maybe a security measure to protect against bots. Now that you mention it, knowing which grade levels use the site might be useful information. Perhaps you could include voluntary sections. Things like major and whether the student is a transfer. But it should be very clear that information is voluntary and not required for registration. The information should also not be attributed to a specific student on graphs. It should just be put into a "pool" of information. At no time, anywhere in our system, should an elevated user be able to see which specific student used which service. Address privacy concerns in a FAQ. Collected data is only meant to improve the system and CSD program,

Q: Since WOU emails stay active when a student graduates or leaves WOU, will someone registering as a student need to be currently enrolled at WOU? If so, how will we verify their enrollment? How will we determine their enrollment has expired?
A: Student year, such as freshman, sophomore, and so on, could be a part of the registration process and once a student passes senior status, their account can be removed from the system or marked as inactive or graduated. Should a student return to WOU after that time, they would need to register again.

Q: Which features--for students--require logging in by the student?
A: Scheduling and canceling appointments, participating in online tutoring, any messaging within the application, and storing information generated by calculators.

Q: Which features--for tutors--require logging in by the tutor?
A: All features built specifically for the tutor require logging in.

Q: From our understanding, a tutor is a student--should this require separate logins?
A: That isn't necessary.

Q: Which features--for professors--require logging in by the professor?
A: All features built specifically for the professor require logging in.

Q: What is the administrator role and what privileges are granted to this role?
A: The administrator role will be the administrator in the department, and perhaps other high-level positions. We don't anticipate this role belonging to more than 1 or 2 people. An administrator should be able to view, but not edit online session information; view, but not edit time sheets; view how many grading tasks are assigned to a tutor but not details such as messaging--we also don't want an admin to see private messages. The admin can also view graphed data that is available to professors. This role is more of an oversight role. They could also have the ability to alter availability if a tutor is unable.

Q: Will tutors, professors, and admins go through the same registration portal as students?
A: No, the registration process and login in feature should be separate for students and elevated users. It's okay if they are presented on the same page, but there should be a safeguard to protect against students accessing elevated permissions. We could give elevated users special credentials in person if that helps.

Q: Do you have a vision in mind for how this should look? What do you see when you open the homepage?
A: We want a modern, simple style. Try to incorporate WOU colors. The homepage should display current tutoring schedules and service alerts for that day. It should be obvious how to register and login. We don't want a busy homepage so other features should be linked and easy to navigate. We want a FAQs section that is easy to find so that students know exactly how to use the system.

Q: Just to confirm, every service is free of charge?
A: Yes, student services are 100% free. State this somewhere on the application.

Q: Do you plan to expand this application beyond the computer science department?
A: Our current focus is on this department only and we want to tailor the app to CS needs. However, we don't want this designed in a way that completely closes the door to other departments. We think our ideas so far leave the door open.

Q: Is there anything else you want us to know before we get started?
A: I think that is enough information to get your team going. We would be happy seeing these features implemented but will be in touch if we think of anything else. We also really like the name Beyond the Tutor and would like a custom logo on the home page.