$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Target release

22nd March 2024

Epic

CRF-138 - Getting issue details... STATUS

Document status

DRAFT

Document owner

Tahmid Rahman

Designer

Tahmid Rahman Nur Adilah Syaza Binti Mohamad Najib

Tech lead

Tahmid Rahman

Technical writers

NURLAN ALINA Nur Adilah Syaza Binti Mohamad Najib

QA

Tahmid Rahman Nur Adilah Syaza Binti Mohamad Najib

🎯 Objective

To compile all schedules/dates and show them in one page. For this first phase, we are prioritising lecturers and planning to show the following schedules/dates in APCalendar:

Phase 1:

  1. Module Exam Paper Due date

  2. Module Marking Due date

  3. Module Moderation Due date

  4. Internship Report Marking Due date

  5. Undergraduate FYP Marking Due date

  6. Postgraduate Thesis/Dissertation/Project Paper Marking Due date

\uD83D\uDDD2 Requirements

Requirement

System

User Story

Importance

Jira Issue

Notes

1

Create APCalendar for academic staff to monitor there schedule/deadline in APSpace

APSpace

Currently, the dates mentioned in the Change Description are not available in APSpace and lecturers have to either go to Moodle or ESS to see the due dates. By having this feature, it will ease all lecturers and they can see the due dates that are happening on that day, week and month

HIGH

CRF-138 - Getting issue details... STATUS

For weeks:display previous 1 week and upcoming 1 week.

For months: display previous 4 weeks and upcoming 4 weeks.

2

Module Exam Paper Due date

ESS

User should be able to view in the frontend the following data:

  • Module code

  • Intake code

  • Date is the Module Exam Paper Due date

  • isAllDay by default True

If there is available time display the following:

  • startTime by default empty string

  • endTime by default empty string

 HIGH

 

 

3

Module Marking Due date

ESS

User should be able to view in the frontend the following data:

  • Module code

  • Intake code

  • Date is the Module Exam Paper Due date

  • isAllDay by default True

If there is available time display the following:

  • startTime by default empty string

  • endTime by default empty string

HIGH

4

Module Moderation Due date

ESS

User should be able to view in the frontend the following data:

  • Module code

  • Intake code

  • Date is the Module Exam Paper Due date

  • isAllDay by default True

If there is available time display the following:

  • startTime by default empty string

  • endTime by default empty string

HIGH

5

Internship Report Marking Due date

Moodle

  • Module code

  • Intake code

  • Color hard coded = #000080

  • Date is the Internship Report Marking Due date

  • isAllDay by default True

If there is available time display the following:

  • startTime by default empty string

  • endTime by default empty string

  • Link to course or activity (whichever easier)

HIGH

Add 14 days after submission due date in Moodle

6

Undergraduate FYP Marking Due date

Moodle

  • Module code

  • Intake code

  • Color hard coded = #040bcf

  • Date is the Undergraduate FYP Marking Due date

  • isAllDay by default True

If there is available time display the following:

  • startTime by default empty string

  • endTime by default empty string

  • Link to course or activity (whichever easier)

HIGH

Add 30 days after submission due date in Moodle

7

Postgraduate Thesis/Dissertation/Project Paper Marking Due date

Moodle

  • Module code

  • Intake code

  • Color hard coded = #3c3ce6

  • Date is the Postgraduate Thesis/Dissertation/Project Paper Marking Due date

  • isAllDay by default True

If there is available time display the following:

  • startTime by default empty string

  • endTime by default empty string

  • Link to course or activity (whichever easier)

HIGH

Add 30 days after submission due date in Moodle

\uD83D\uDCCA Success metrics

Goal

Metric

Simplify user experience

Customer Satisfaction

\uD83E\uDD14 Assumptions

  1. Change in Requirements

  2. Change in Developers

\uD83C\uDFA8 User interaction and design

image-20240228-020712.png

image-20240228-020927.png

image-20240228-021526.png

image-20240228-021655.png

image-20240228-022450.png

(question) Open Questions

Question

Answer

Date Answered

(warning) Out of Scope

  • No labels