Simple guide to help you on your web-dev journey
View the Project on GitHub KeaCluster/bookstoreAPI-spring-guide
In this section, we’ll delve into understanding the basic requirements for our bookshop system. This will range from its basic functionality, to the database and an overall description of the system to better understand its purpose and requirements.
We are designing a system for managing a bookshop’s book renting service. The bookstore system should run in a web-application, one which we’ll not delve into where due to the small scale and time available. However, note that the system will respond to the requests from that application.
Additionally, we could argue that since its called a bookshop the name might imply the user be able to buy or shop books. But we’ll focus solely on the book renting functionality for simplicity’s, since thats the reason we’re here in the first place and our primary goal.
The core entities of the system are rather simple and plain:
M:N relationshipAs for the relationships, at this point we recommend having a solid grasp of basic relational database structure, and how entities communicate and relate to each other.
Everything we do here could be documented through a third-party tool but for simplicity, we’ll just stick to simple comments alongside this guide. We do however recommend you take your own notes along the way.
Now that we have an idea of our system’s requirements, we can talk about the different stages we’ll need to go through.
We’ll have to go through several stages in order to completely release this “project”. However please note that the resulting project is not production ready and will have to go through several security phases and sections to make sure it can be considered a real application.