Requirements Model/Specification
Hi there,
This is more of a question geared towards specification and design.
If your still here... read on...
I am involved in writing my first large piece of software (im in the real world now) and im having a few issues defining my requirements model. I am basically building re-usable, extensible database abstraction layer that builds upon JDBC for our specific needs.
The problem Im having is how do I define the use cases for this implementation. Im having trouble identifying the actors involved and the subsequent use cases. For instance... it would be easy to specify a use case "Add a new client" if i was building the whole application but im only one of many now. This particular package is more of a middleware component than anything else. Therefore external entities are more difficult to identify, and therefore design. I have to apply full lifecycle methodology to this one package.
Any seasoned professional willing to give advice to me would be very welcome.
Any good reading or reference material would also be excellent. (Speaking of which, anyone interested in component software, an excellent new book has just been released by Szyperski - Component Software - Beyond Object-Oriented Programming.)
Kind Regards,
Simon
