Project needs

At the introduction it was established through the objectives section that the API would be made based on a requirements specification, but before focusing on the web and game side. What does a software project of this type needs to have? lets sum up its needs

##Loose coupling

All the components forming this project must be able to change, so other people can test a specific library without having to compromise with a whole gaming framework. Loose coupling means that each of the system components has, or makes use of, little or no knowledge of the definitions of other separate components. This has to be met by always programming to an interface. The only immutable parts of the API will be its basic modules interfaces.

##Open to changes

This is going to be an open source project intended to be not just used by the user but modified by him so it has to have a maintainable code base. This will be achieved by setting a naming convention for all modules, methods and variables in the project and the use of documentation.

##Robustness

The change of a component of the game cannot make the other pieces fall even through and error. Robustness in software is defined as the ability of a computer system to cope with errors during execution so error handling and testing are crucial to the development of the library.