Hi everyone,

Today, I will discuss the difficulties and mistakes I made on a project that stretched me to the maximum and gave me priceless insight into design patterns and software development.

Within the field of software development, design patterns are essential for producing scalable and maintainable code. We dug deep into these patterns last semester in a demanding course called Our Ow Food Ordering System. This project required more than simply code; it also required comprehension and practical application of software development concepts. I will thus talk about my trip, the difficulties I encountered, and—most importantly—the mistake we made that nearly caused our project and hard work to fail.

The Project Summary

Our task was to ensure that our project included five or more design patterns, each of which offered a unique benefit to the system. We choose to make use of the Decorator, Observer, Singleton, Composite, and Prototype patterns.

The system we built had these key components:

Login Form: Users can log in to access the system.

Dashboard: After logging in, there is a dashboard that provides an overview of the system, and has our food collection.

Food Collection: Users can see a collection of dishes, and select what they want to order.

Order Confirmation: The system would calculate the total price, allowing users to confirm their order, which will stored in the database.

The main task was about the patterns we implemented all the patterns on form and made a lot of classes for each category also we used interface classes It was the most difficult project I have ever created and the most difficult course for me i never faced this much difficulty in any project but somehow we managed to complete the project and at the end, we were so happy that finally we successfully created it.

The Difficulties

This was the most challenging project I have ever worked on. Several classes had to be created for each category to implement these design principles, and flexibility could only be ensured by using interfaces effectively. The course material itself was exceedingly difficult; each step required careful planning and close study.

The Blunder

But come the day of evaluation when we presented our project to our sir he said to leave the UI and just come to the patterns we presented him the patterns we used, he was like no this is not what I said we were like? he said you implemented those patterns in the forms but I want these patterns in class not in forms the good thing was that we also used those patterns in class but commented on those, for those who are unfamiliar with a comment, it's like when you don't want that particular part to e executed you comment that part so we comment that patterns in class we told him so he said but we have no time for that you guys didn't make a project this doesn't even call a project.

And you know the worst part is that implementing patterns on the form was so much more difficult instead in classes and we successfully implemented those patterns in classes but we were worried about how to implement these in forms. Sir himself agrees that it is more difficult than why don't say that to implement on the form then somehow he said you guys have the best image in the class you have the best performance I know you guys worked hard on this project so I will just pass your project and I got 11.5 out of 15 we were so disappointed.