a.WU_Dashboardwill include all functional requirement for students, teachers and teaching assistants for lesson plan and delivery. It will also contain support staff that handles service support.

b.Wynyard University classify their staff as academic and professional staff. Academic staff are involved with the teaching delivery of a course while professional staff are responsible for the other services and support of WU_Dashboard. Three categories of user include student, academic staff and professional staff.

c.WU_Dashboard aims to improve and incorporate the new requirements for academic staff and students. It will also include requirement for professional staff at Wynyard University. Professional staff support the business processes of student admission, enrolment and completion in each semester. This is done in theWU_Dashboard. Canvas staff and other non-teaching staff (NTS) are professional staff for WU_Dashboard.

d.WU_Dashboardwill be compatible with all operation systems for devices inclusive of handheld hardware. WU_Admission, WU_Register and WU_Enrol will have seamless connectivity with WU_Dashboard.

e.Access onto Canvas via WU_Dashboardwill be a multi-tier access control list (ACL). Current roles in Canvas are list below:

f.Add-ons functions include: Chatbot, live webinars, video chats, online breakout room and online assessment modules. These are part of the functions and are available to students and/or staff.Requests of add-ons are handled by Canvas staff except for assessment module.

g.New roles required: Canvas staff, Non-teaching staff (NTS). Additional roles need to be added. NTS create courses on WU_Dashboard. Access coordinator can manage user accounts for all courses.

h.Academic staff will be populated onto each confirmed course by the access coordinator. Additional teaching staff can be added at any time. Students are populated automatically via WU_Enrol. No students can be added manually. Once a student enrols via WU_Enrol, he/she will be added onto WU_Dashboard overnight.

i.Courses arecreated by a NTS once a course is confirmed in WU_Register. Each course will have a default template that can be customised by academic staff.

j.WU_Dashboardwill have the capability for users to customise their profile. Some profiles are editable (e.g. preferred name, contact number, pictures) while some information isnon-editable (e.g. programme, legal name, academic transcript, concessions applied).

k.Teachers and teaching support have full access to all functions in WU_Dashboard. Only Teachers can submit final grade. Teaching assistant does not have access to delete content.

l.WU_Dashboardwill incorporate Chatbots to answer simple questions that are commonly asked by students. It is powered by rules and artificial intelligence (AI) with a knowledge base for course content. Students will have access to the Chatbots 24/7, from any location,via all types of hardware.Chatbots are pre-loaded at the start of each semester by a Canvas staff. The knowledge base is continuously added via AI technology.The knowledge base isbuilt by both academic and professional staff.

m.Video chats can be requested by students or academic staff and a notification will be issued with a code for all parties required to join the chat.

n.Virtual breakout rooms are also a new feature for students to request within a course. This is available to both students and teaching staff. Breakout rooms can be requested instantaneously with recording and live caption capabilities. A log will be recorded on the IDs of participants and time used.

o.Teaching staff can create online assessments via WU_Dashboard. Assessments can either be supervised or unsupervised.

p.Live events and webinars are new services to be added on WU_Dashboard. These services are only available for teaching staff. Live events and webinars scheduling will need to be requested and confirmed before the events can be advertised. Event codes will be issued once confirmation is received. Date, time and duration will need to be provided for each request.

q.Recordings of all teaching events (e.g. lectures, tutorials, webinars) will be available automatically. There is a 5 Gb limitation of each file.Notification is sent to access coordinator after each recording is published.

r.Each course will be archived at the end of each semester by NTS. This is done after all final grades are submitted and verified. Courses can be reactivated to allow referencing and observation for new upcoming semesters.New courses can import content from an archived course.

s.WU_Dashboardwill be available on all standard web browsers, portable handheld devices and tablets.

t.Customization: students and teaching staffcan personalisetheir dashboard on WU_Dashboard. Personalisation can be by selecting from the library of themes, options of colours as well as selecting favourites. All active courses will be displayed on each student and teaching staff profile.

u.WU_Dashboard will have calendar, reminder, and quick links available for personalisation. Users can set appointments, reminders for their learning and teaching requirements. (e.g. test dates, webinar sessions, assignment due dates etc).

v.My_Notes is a feature for studentsto create study notes.Thisfeatureis assessable bystudentsonly. This feature supports multiple file typesand allow sharing of files for group study.

w.A search engine is also built into allow all users to search using keywordsfor courses they have access to within WU_Dashboard. This feature is needed to allow forimprovement in building up knowledge basesand information management for each user and course.

x.All courses and files will be automatically backed up every 12 hours. Virus scans of all files will be done daily. This requirement is to offer reliability, sustainability, and security of the existing and new features.

TASKS 1. Requirements Definition Report (20 marks) You are required to prepare a requirements definition report by: a. Re-writing the system requirements (above) to meet the requirements definition format. b. Re-organise the re-written system requirements into functional and non-functional requirements.

FORMAT

1. Requirements Definition Report

Functional Requirements:

1.

1.1

2.

2.1

.

3.

3.1

4 Others?

4.1

5.

5.1

Non-functional Requirements:

1. Operational / Usability?

1.1

2. Performance?

2.1

3. Security?

3.1

4. Cultural and Political?

4.1