swapnanildutta / student-database

This is the project I made during my 10th standard examination (ICSE) in Java.

Student-Database

The following project is a menu driven database system which can store student records and perform frequently used manipulation commands. Basic CRUD functionality is programmed into main.java file, and the student.java file houses the definition of the student class, which is used to create instances of student records in the database. This project was made by me for submission in the final assessment of Class 10th (ICSE).

About JAVA

Java is a powerful general-purpose programming language. It is used to develop desktop and mobile applications, big data processing, embedded systems, and so on. According to Oracle, the company that owns Java, Java runs on 3 billion devices worldwide, which makes Java one of the most popular programming languages.

Workflow

The main.java file initially prints a menu with 8 different options to perform the mentioned operations/queries on the database. This is followed by a switch case code, which handles the input by the user and executes the appropriate block of code. You must be familiar with OOPs concepts and basic JAVA programming in order to be able to work on this repository.

Suggestions

Appliance of Observer design pattern

Appliance of Factory Method design pattern

Thank you.

student-database's Issues

A design suggestion

Hello, nice to meet you.
I am doing a task regarding the use of design patterns and I stumble upon your project. While I was analyzing it I could notice that you were performing several iterations with the use of a for loop and although within the implementation that you are giving it is correct, I think that to suggest that if you use the Iterator design pattern it does not represent any harm, since, you can in the same way, go through the collection but do not expose the representations of the objects(list, stack, tree, etc.).The good thing about using this design is that more collections can be added as the system grows and it will not suffer any damage!

Next I attach a UML diagram with a design that follows this pattern.

I hope this suggestion is taken positively and if it is found to be wrong in any way I apologize in advance, as I am just gaining knowledge about design patterns and their structure.
I hope you have a great day. Thank you

Update README

Another design suggestion

Observer design pattern

Observer is a behavioral design pattern that lets you define a subscription mechanism to notify multiple objects about any events that happen to the object they’re observing.
https://refactoring.guru/design-patterns/observer

Suggestion

I noticed that in your program you delete or change the state of an object, so this may come in handy for your repository

Regards

Thanks for paying attention.

Yet another design suggestion

Suggestion

I think for better abstraction of the program, you should split some Students variables into new classes like Records for example.
And make use of creational pattern designs that lets you be clear on how you would create your objects and later on their usage.

Factory Method design pattern

Factory Method is a creational design pattern that provides an interface for creating objects in a superclass, but allows subclasses to alter the type of objects that will be created.
https://refactoring.guru/design-patterns/factory-method

Suggestion - UML Diagram

In this suggestion, I added some additional classes to explain a little better my suggestion. The great property that the factory method has is that makes the code easier to refactor or support.

Regards

Thanks for paying attention. Keep up the great work!

Update README.md