Hi there,

Are you simply investigating the system or building a new one? I've done degree level software engineering and a project based around something very similar but we actually had to build it

Anyways, i'm going to take a stab at the things you might want to consider.

Firstly, you're going to want to find out as much as possible about how the current system actually functions at a low level and a high level from here you can construct your data flow diagrams/context level diagrams to give a clear understanding of the functions. You might want to find out if the library has a membership system and how that works.

From here it would be very easy to turn them into a requirements specification. Are you doing functional/non-functional or general user requirements? From the top of my head you might have things like...

1. The system must allow members to borrow multiple books.

Note - It's important to define between the different users of the system, if you just say "user" it could be the customer/admin/staff etc.

I can help you ALOT more but really need more information on the whole project, I didn't want to write up a huge post if it's totally off the mark.

:reindeer: