Given a Javadoc for a project, what would be an efficient/fail-proof way of going over the javadoc without missing information/declarations/methods and so on? Is there a systematic way of going over a Javadoc file?
I was given the task of starting a project. I have an instruction pdf and Javadoc file (Java). I'm trying to figure out the best way to start without getting lost and jumping from class to class as I go over the javadoc.
I started by trying to write the whole structure, i.e create the packages, interfaces, classes and enums as described in the javadoc file.
Is there a way to verify that I have created the whole hierarchy of the javadoc? I was think I could perhaps create my own javadoc of the project I created - and see if the two javadoc match up. But this seems like quite a bit of work when the document is quite big.