Please rewrite this implementation plan. In a manner that does NOT read as though it is AI generated.

Re$-$write script below including:

"Activity diagram depicts how different layers of LMS would interact. Here is simple

break down below:

User Input $($GUI$)$ Controller $$ Model $$ Database

Database Updates$/$Queries $$ Model $$ Controller $$ Updated View on GUI

This diagram will help visualize the flow of data and control between layers and model

user interactions such as searching for a book or borrowing a resource. $"$

$1.$ Introduction Project Scope: The Library Management System $($LMS$)$ is in place to manage and monitor a collection of resources by a library, such as books, patrons, borrowing records, and staff. It will have functionalities such as catalog management, user registration, tracking of book borrowing and returns, and reporting. A good implementation plan delivers an overall clarity of having a roadmap on how the system will be built. This makes sure that any architecture, coding strategies, and integrations are well defined before developing. In turn, it will help guide the development process and avoid pitfalls such as inefficiency or scope creep. $2.$ Architecture Pattern Pattern Chosen: Model$-$View$-$Controller $($MVC$)$ Why Chosen: MVC separated the user interface $($View$),$ business logic $($Model$),$ and control flow $($Controller$)$ into distinct layers. It is$,$ therefore, very commonly used for applications based on Java. Hence, it would be just apt for the LMS application wherein a GUI along with other related book and user management logic and a database backend are required. How the LMS will be Generated Using This Architecture: Model: The model layer will consist of Java classes that should map the core entities like books, users, transactions, and staff members. This layer will also converse with the database to make CRUD operations for all of them. View: The view layer will involve the GUI components, created using either JavaFX or Swing, by which the user will interact with the system. Controller: He would act as the mediator between Model and View, processing inputs from view and updating models and views appropriately $.3.$ Activity Diagram Activity diagram depicts how different layers of LMS would interact. Here is simple break down below: User Input $($GUI$)$ Controller $$ Model $$ Database Database Updates$/$Queries $$ Model $$ Controller $$ Updated View on GUI This diagram will help visualize the flow of data and control between layers and model user interactions such as searching for a book or borrowing a resource. $4.$ Coding Strategy For Each Layer of the Architecture: Use classes in Java to describe entities like Book, User, Transaction, and Staff. These classes should follow object$-$oriented principles such as inheritance for common fields $-$ for example, a Person superclass for the User and Staff $-$ polymorphism for the method overloading, and generics for collections of books or transactions. The middle class that controls, LibraryController is going to connect the view with the model. This class possesses methods regarding the input from a user, such as search books in$,$ borrow books in$,$ and return book in$.$ View: The GUI will be built based on top of JavaFX or Swing, to present a friendly interface in front of users. The idea with mockups is to devise how users might interact with the system; for instance, catalog, login$,$ and book borrowing pages. Database Integration: The system will use JDBC to connect to an SQL database. Connections will be managed and SQL queries executed using a DatabaseHelper class. The database schema will include tables for books, users, transactions, and staff, with foreign key relationships between them. Review of Module $2$ SDLC Assignment Part $2$: Keep: The use of inheritance and polymorphism in the entity classes of Person, User, and Staff. Collection$-$based methods for storing books and transactions. Change: Explain database implementation using JDBC and SQL$.$ Refine GUI design with interactive elements to be accompanied by proper data validations. $5.$ Object Oriented Principles Classes and Objects: The real world objects, such as books and users, will be represented by classes. The instances of the classes will be created for each record in the system. Inheritance and Polymorphism: Person will be a superclass for User and Staff, with the common attributes such as name and contact. Polymorphism will be used to implement flexibility based on the type of user. Collections and Generics: The Java List interface and Generics will be applied in order to store lists of entities such as books, users, and transactions. This provides type$-$safe collections without writing lots of repetitive code. Exception Handling: Exception handling will be a significant role in dealing with faulty input and connection errors to the database. $6.$ GUI Design GUI Tools: JavaFX or Swing Mockup: The GUI will include functionalities such as search bar for books, registration form for users, and borrowing and returning