This is a course work when I was a freshman in the university. I'm in a group of four, our task is to build a library system in 3 weeks. By that time, we only learned basdic C language, no any frame, no any concepts about "frontend" and "backend". But intuitively, we devide our work to "frontend" and "backend".I'm in charge of the "backend" with a nother classmate. After weeks of hardworking, we built the library system with 3000 lines of code and got the best grade in the class.
By using basic C language, we creat an interface in the terminal, use keyboard as input. Each time the system launched, it read the file in the disk and store it in the RAM, while the system is exit(through the instruction in terminal), it write the data from RAM to the disk. Since by that time, what we have learned is just basic C language. This is the best we can do by using basic C language. And since the IDE we used by that time is completly outdated (VC6), it may have some bugs running in the vscode. Also the "project" is kind weak of showing the skills that I have. But i think that this 3000-line code could more or less shows that I'm capable for teamwork and "get things done" , as well as continous learning(too many bugs that we have encountred, and what can help us is just the Google.)
now let's see what the library system looks like. My teammates built the interface in Chinese, and because this interface is showed in the terminal, It take efforts to align all the icon. Simply translate all the Chinese in to English will destroy the interface's design. So I choose to leave with it and explain the features of the library system.
Overall, we built this system as if it will be used in the real life. We added all the features that we can come up with. The Administrator can add books or delete books from the inventory, also Administrator can check all the record of borrowed book, or revise the book information. The user can search the book they might want (supports fuzzy search), borrow book, return book, and check their profile to see how many books they have borrow and when should they return them. we set up a mechanism that each user can have three borrowed books at most, and each book have to be returned in one month. if a user have overdue book, they can not borrow new books until the user return the overdue book.
Now, let's launch the main.exe
1-register,2-login,0-exit
login interface
1.user login,2.adimn login, 3. login as a temporary visitor
By the way, we manage to detect the illegal input since some illegal input may crash the system. And when you put something wrong(for instance:wrong password):
"account or password wrong"
"Try again?(Y/N)"
user interface
- book search
- borrow
- return
- personal profile
- logout
book search interface
- search by book name
- search by category
- search by author
- search by publisher
- return
let's search by book name and type"math"
the result shows:
beside the number,the book name, category, publisher and author, it also shows howmany books the library have and howmany is available now. to borrow the book, the procedure is about the same. just enter the number shows in the interface.
personal profile
it shows howmany book you have borrowed and when should you return them.