Business Requirements
Business requirements - an extract from B.R.D. for HSS023:
Functional Requirements
Platform Needs
|
ID |
Requirement |
Priority |
|
1.1 |
Location where Rep contact data (including photo) can be viewed at any time by students. |
MH |
|
1.1.2 |
Reps contact data (including photo) can be edited by Reps and TO. |
MH |
|
1.2 |
Interactive platform where reps can view student comments, and students can communicate with each other (Student forum). |
MH |
|
1.2.1 |
Students can make public comments which can be read and responded to by all students in their Rep forum. |
MH |
|
1.2.2 |
Students can respond to comments by Reps or other students. |
MH |
|
1.3 |
Important Rep communications cause notifications. |
SH |
|
1.3.1 |
TO member can push notifications (i.e. SSLC notes). |
SH |
|
1.4 |
As students’ progress, group name is updated (Year 3 -> Year 4). |
SH |
|
1.5 |
Access by TO is restricted, cannot view student discussions. |
SH |
|
1.6 |
Student data is protected so as to comply with GDPR. |
MH |
User Stories
The following user stories are from the view point of the various user groups and should be seen as supporting the above requirements.
Students
- As a Student I need to be able to see who my reps are, what their contact information is, and what they look like so that I can contact them with my feedback at any time.
- As a Student I need to have the option to make my feedback comments visible to other students so that we can have a constructive dialogue and enrich our feedback.
- As a Student I need to have a user friendly interface where I can view other student’s comments, like or vote on them, and participate in the community feedback so that even if I don’t personally provide feedback, I can see that actions are being taken.
- As a Student I need this platform to be easily accessible and not through a medium like Facebook so that I am not forced to create a Facebook account in order to participate in the feedback community.
- As a Student I need to receive some communication after the SSLC or other feedback mechanism has been engaged so that I can appreciate how my feedback has been acted upon.
- As a Student I want to be able to continue to engage in the feedback cycle after the SSLC or other feedback mechanism has been engaged so that feedback is fully optimised, and a sense of community is established.
- As a Student I want my feedback not to be seen by University staff so that all students can feel comfortable sharing their honest opinions.
It should be noted that if a student is taking a course outside their programme and wishes to raise an issue regarding this external course they still raise this with their course programme rep. It is then the responsibility of the Programme Rep to raise the issue with the external course programme rep so that it can be addressed.
Programme Representatives
- As a Rep I need to have a place where I can engage with students to hear their feedback and discussions so that I can better represent them to the University.
- As a Rep I need this system to be under the University of Edinburgh so that I do not have to create a social media account to perform my role.
- As a Rep I need to be able to make modifications to contact information or class information so that I can be best positioned to receive and respond to feedback in order to perform my role.
- As a Rep I want the ability to push notifications to students when an important event or piece of information is being released so that no one misses out on key deadlines for feedback.
- As a Rep I want the ability to post outside links to polls or surveys so that I can diversify the ways I collect feedback.
Support Staff
- As Staff I need to be able to make initial edits to the platform when reps are added or removed so that the correct Reps are allocated.
- As Staff I need to have administrative rights on the platform so that there is a reliable site management mechanism in place.
Non-Functional Requirements
Security
|
Ref |
Security |
Requirement |
Priority |
|
1.1 |
Authentication |
EASE or ADFS Authentication to be used. |
SH |
|
1.2 |
Authentication |
If not EASE or ADFS, must be highly password secured. |
MH |
|
1.3 |
Authorisation Levels |
Admin – read/write access to application’s administrative functionality and to all data Owner – read/write access to all data functionality but no admin permission Support – Can edit basic data and communication methods, but can’t view public discussions. |
MH |
Availability/Business Continuity
|
Ref |
Availability/Business Continuity |
Requirement |
Priority |
|
2.1 |
Solution should be available 24/7 |
99.7% availability including planned maintenance |
MH |
|
2.2 |
In the event of a failure the system must be designed to be recoverable in less than 1 working day with minimal data loss |
Recovery in less than 1 working day from time of failure with no loss of completed transactional data |
SH |
Conformance with Browsers, Operating Systems and Mobile Devices
The solution should be supported by the minimum set of web browsers and operating systems as identified by Information Services. Details of supported web browsers can be found by clicking on the following link: