saul108
commented
2 weeks ago updated version of Needs and derived goals that needed to be revised
professors comment for needs:
What you write under "needs": the first part of it talks about the current situation and the later part talks about what you intend to do to improve the situation. Both of these aspects should be covered elsewhere and not here. What is it that students NEED? They do not need the new system...
1.2.2 updated Needs
While there is already a platform for student’s class enrollments, there is a need for a more efficient method to enroll in classes. Students require a system that assists their needs by providing course information and enrollment in one place. There is a need for students to have a platform which holds a record of their curriculum and the courses already taken, and courses that they need to take. Considering that courses have a tendency of actively changing information, there is a need to keep notifying the students which courses can be available, full, or restricted. Additionally, some courses have requirements which are needed to be enrolled in, there is a demand for a more efficient way of showing the courses that a student can select.
professors comments for derived goals:
The secondary goal is still not a good choice. One could argue that the notification system is just in line with your primary goal. A secondary goal could, for example, be to generate the domain description in such a way that it can also be used (or at least be the basis) for instructions on how to enroll (given to new students) or even for a documentation of the enrollment process that is used by administrators. This is just an example. You could come up with your own, of course, but you can also elaborate on this...
1.4 updated Derived goals
By providing a more structured platform for students to enroll in courses, a secondary goal is to provide students with a more intuitive design which helps students with an introductory approach on how course enrollment works and what important information to look for. This can help freshmans on how to schedule classes for the semester. Another secondary goal of our platform is to help administrators to provide ease of access on course administration, as well as to implement a notification system that empowers students to access real-time updates on course availability, enrollment status changes, and waitlist notifications.
https://docs.google.com/document/d/1fm2_-xS2va0g5I8J_-kPfuVFM41GPkGdRXB2idwTLxs/edit?tab=t.0
Objective: Refine the documentation by modifying sections 1.2.2 (Needs) and 1.5 (Derived Goals) to improve clarity and focus.
Description:
Section 1.2.2 (Needs):
The first part talks about the current situation and the latter about what we intend to do to improve the situation. These things should be covered elsewhere. Here we should focus only on the specific need of the students without mentioning the new system itself.
Section 1.4 (Derived Goals):
The current secondary goal (a notification system) aligns with the primary goal. A secondary goal could, for example, be to generate the domain description in such a way that it can also be used (or at least be the basis) for instructions on how to enroll (given to new students) or even for a documentation of the enrollment process that is used by administrators.
Requirements:
Deadline: November 12, 2024 @ 4AM
Completion Criteria:
Section 1.2.2 focuses on student needs without reference to the new system. Section 1.5 contains a revised secondary goal centered on creating a reusable domain description.
Difficulty: 3
Priority: 5
Suggested asignee: @saul108