Update README.md

Author: DoubleLSun

README.md

@@ -4,14 +4,17 @@ This is a graded coursework assignment for our Object-Oriented Application Devel
 Developed in Java (Eclipse 2023).
 
 ## Challenges and Areas for improvement
-During the pre-planning and implementation phase, our project suffers many hurdles like lack of efficiency, productivity due to factors like:
-* Imbalance in task distribution and limited participation from other team members, causing us to fall behind schedule which is detrimental to the quality of the application.
-* Compromisation on the GUI design, due to unfamliarity with the Library toolkits (Swing, AWT) and a narrow time frame, the end product ended up becoming less polished.
-* Our error testing and bug catching covers only the main functionalities, and input checking, therefore there can be unintended behaviours.
-* Leadership failure, the scope of the project was to originally a terminal based system, which I felt would be the perfect opportunity to apply newly learned toolkits and transition it into a GUI based system. What we fail to predict is that the learning curve to implement the tools were too much for my team, which demoralized my team. As a result, I ended up refactoring and implementing the majority of the application myself within a short development window.
-
-Lessons:
-* I recognize the importance of aligning technical direction with the team's capabilities to ensure more balanced contributions and sustainable workload distribution
+During the pre-planning and implementation phases, our team encountered several challenges that impacted both development efficiency and the final quality of the application:
+* **Imbalanced task distribution and limited participation** from some team members led to delays and an increased burden on a single developer, which affected our ability to meet deadlines and polish the final product.
+* The **GUI design suffered** due to the team’s limited familiarity with Java Swing and AWT. With a steep learning curve and a tight time frame, we had to prioritize functionality over aesthetics, resulting in a user interface that is functional but lacks polish.
+* Our **error handling and bug testing** primarily covered core functionalities and basic input validation. As such, some edge cases and unintended behaviors may still occur.
+* A **key leadership oversight** was the decision to expand the scope from a terminal-based system to a full GUI application. While the intention was to apply our newly learned toolkit in a meaningful way, I underestimated the difficulty of transitioning to GUI development for team members unfamiliar with Swing. This mismatch in skill level led to a drop in morale and ultimately resulted in me taking on most of the implementation and refactoring work myself within a compressed timeline.
+
+## Lessons Learned
+This experience highlighted the importance of:
+* Aligning technical direction with the current capabilities of the team,
+* Setting realistic scope based on available time and resources,
+* Ensuring balanced workload distribution to maintain motivation and engagement.
 
 ## Main Functionalities
 Librarian Authority: