Sale!
Placeholder

Provision of coursework information within SIS

10,000 3,000

Topic Description

Summary
This project aims to aid the provision of coursework information, from the perspective of both
staff and students, within SIS (the School Information System), at the University of Leeds’
School of Computing. Students will consequently be able to view a personalised coursework
timetable, and thus easily determine their own schedule, and effectively plan their time.
The project has produced a web-based system, which extends SIS, to enable staff to
manage their module’s coursework schedule, and to allow students to view a personalised
coursework timetable. The system also allows coursework administrators to manage the
coursework schedule for all modules, and determine which coursework assignments have
not been marked on time. Students have the additional option of viewing their coursework
marks using the system.
Possible future enhancements have been identified, including the ability to identify peak
coursework loads, and allocate postgraduate students to coursework marking.

Contents
1. Introduction 1
1.1. Statement of the problem 1
1.2. Background research 1
1.3. Methodologies 2
1.4. Project plan 3
2. Objective 4
2.1. Main objectives 4
2.2. Minimum requirements 4
2.3. Additional requirements 5
3. Analysis 6
3.1. Requirements gathering 6
3.1.1. Similar projects 6
3.1.2. Current system 6
3.1.3. Further interviews 7
3.1.4. Overview of SIS 9
3.2. User requirements 9
3.3. Tools 10
3.4. Data protection 11
4. Design 12
4.1. Existing system 12
4.2. Database design 12
4.2.1. Entity relationships 12
4.2.2. Existing SIS tables 14
4.2.3. Attributes 14
4.2.4. Table design 15
4.2.5. Normalisation 16
4.2.6. Data integrity 16
4.3. Interface design 17
4.3.1. State transition diagram 17
4.3.2. HCI 18
4.3.3. Prototyping 18
5. Initial Implementation 21
5.1. Database 21
5.2. Interface 22
5.2.1. HCI 23
IV
5.2.2. Security 24
5.2.3. Welcome screen 24
5.2.4. Student 24
5.2.5. Staff / Administrator 26
5.2.6. Assumptions 29
5.3. System review 30
6. Additional Implementation 31
6.1. Evaluation of additional requirements 31
6.2. Database 31
6.3. Interface 32
6.3.1. Student 32
6.3.2. Staff / Administrator 34
6.3.3. Administrator 34
7. Testing 36
7.1. Unit testing / Combined module testing 36
7.2. System testing 37
7.3. User acceptance testing 38
7.3.1. Main stakeholder review 38
7.3.2. Other user reviews 40
7.4. General website testing 41
7.5. Testing summary 42
8. Evaluation 43
8.1. Original objectives 43
8.2. Usability evaluation 43
8.2.1. Effectiveness 44
8.2.2. Efficiency 45
8.2.3. Satisfaction 45
8.3. Development methodology / language evaluation 46
8.4 Old system 46
8.5 Evaluation summary 47
9. Future Enhancements / Conclusion 48
9.1. ‘Could have’ requirements 48
9.2. Further enhancements 48
9.2.1. Student 48
9.2.2. Staff / Administrator 49
9.2.3. General 50
9.3. Conclusion 50
V
References 51
Appendix A – Personal Reflection 55
Appendix B – Initial Project Plan 57
Appendix C – Revised Project Plan 58
Appendix D – State Transition Diagram – Initial Implementation 59
Appendix E – State Transition Diagram – Additional Implementation 60
Appendix F – Final database schema 61
Appendix G – Sample code from timetable function 62
Appendix H – Sample code from validation function 63
Appendix I – Update due date SQL query 64
Appendix J – Ranking of ‘could have’ requirements 65
Appendix K – Sample code from coursework marks function 66
Appendix L – Overdue coursework SQL query 67
Appendix M – Sample Test Plan 68
Appendix N – Testing / Evaluation Tasks 70
Appendix O – Satisfaction evaluation

PROJECT SAMPLE/DEPARTMENTS

REVIEW OUR SERVICES

SEE FAQ