1 Requirements

An informal requirements set for Moo in OZ. Note that these are in no particular order. They are anchored for reference in those parts of the design document that relate to them.

1. multiple muds can be joined together transparently
2. ability to make as many changes on the fly as possible
3. maximum simplicity for building and coding
4. not too slow or too memory-hoggy
5. number of connections limited only by physical issues (bandwidth, memory, etc)
6. robust access control, within the MOZ, of objects, of internal code, of objects characteristics, of processes, etc.
7. ability to handle various (spoken) languages
8. high potentiol for user enjoyment
9. fault tolerance
10. ease of debugging
11. user can see general information, including class code, about objects in the MOZ
12. ease of testing
13. ease of modification on the part of new admin, programmers, and builders