Is there a way of working out systemd dependencies for a service you're creating?

This is possibly a silly question but other than a few common options / educated guesses / knowing the entire kernel/systemd inside-out is there some way of determining what dependencies and in what order a piece of code should have defined when making it a systemd service? For example; I have a piece of code that uses the serial port, uinput, and sockets - I've found that I need to include this in the service: [Unit] BindsTo=dev-serial0.device After=dev-serial0.device So that the serial port is available to it when it starts - But I can't for example find if there's a service or other dependency for uinput that I might need to include. So - is there a list of services/names somewhere or a command you can run that shows what a particular executable is depending on?