Project Specification - Major Practical Introduction

Our project implements a student information management system. This system contains four classes: Student, Tutor and Teacher and one abstract class: Person. The system allows users to access different information according to their authority. For example, the students can only request to reset the password, but they are not able to reset the password themselves, they need to contact a higher authority, i.e. tutor or teacher to help them to reset the password. In order to build this system, the data such as people’ name, subjects' ID will be stored in the array, string and objects. In addition, Inheritance and Polymorphism can be used to avoid the repeat codes, because those three classes have a lot of common functionalities. Lastly, the whole program will be exhaustively tested by in order to ensure that there’s no bug in our system.

Try it out by docker:

docker run --rm -it akide/oop-project:latest

Build status：

Build status

Design Description

Assessment Concepts

Memory allocation from stack and the heap

Arrays: We will use serial dynamic arrays using new to add in some initial people and subject entries and allow more people and subjects to be constructed.
Strings: Strings are extensively crossing over the entire project, such as, names, attributes, properties.
Objects: Briefly – Student, Tutor, Teacher (based on people), subject and storage.

User Input and Output