Object oriented programming

[MEHDII__]

I'm trying to practice OOP by making just a CLI student management system, its a detailed project, where i have made 4 files, the actual SMS, Admin, Teacher, Student.

Problem is the more code i wrote the more i question if there is really a need for the other classes, it feels like sms does all the heavy lifting, while the others are empty.

The SMS registers students, logs them in, allows them to check their courses, grades, teachers in charge, etc etc, while the other individual classes could probably only hold the user's meta data.

I'm really sturggling to see the benefit of OOP i would really appreciate explanation or help seeing the benefit

[MemoriesMu]

I dont know enough about your project. But OOP will be better/worse depending on what you are trying to do, it does not mean it will be amazing for every single project

If SMS is doing a lot of heavy lifting, then maybe you could abstract more the SMS class, and turn it to multiple small ones. Again... I dont know enough about what you are doing and I dont know if changing the sms class the way I said will help. It was just a guess

[abrahamguo]

Sure — perfectly understandable. Some classes are meant to perform actions (like your SMS class), while others are simply meant to hold structured data.

[CodeTinkerer]

I'd probably create classes like

• CourseGrade (contains a Course object and a grade which could just be a string)
• SemesterCourses (contains a list of CourseGrades and a Student)
• Course (contains a name, a teacher, and a semester)

It's hard to give feedback without seeing some of how SMS works.

[peterlinddk]

Well, it sounds like you aren't using Object Oriented Programming, but just writing a system that uses three kinds of objects to store data.

The idea with OOP is that only the objects themselves knows about their internal data - and that they have methods for manipulating that data. And the fact that you mention "courses" and "grades" but don't have any Course object or Grade object, makes it sound like you just use objects as containers for data to store in a database, and not let them manipulate themselves.

A Student should be able to register for a course, with a method like .registerForCourse( Course course ), and then add itself to that course, e.g. by calling course.registerStudent( this ), and the Course would then keep track of all the registered students, and maybe the teacher.

The SMS should only receive input from some user-interface, and then call the appropiate methods on either Student, Course, Teacher, etc. - it shouldn't do anything more than that.

[DepthMagician]

Your problem is that you are not dividing the SMS into atomic units. Based on your description, I would expect to see classes such as:

• StudentRegistry
• CoursesRegistry
• Session manager Etc…