No limit to the type of information stored:
...the freedom to store any type of information ( text, images, multimedia, application files etc).
No Limit to the how information is manipulated:
...the freedom to manipulate this stored information in any way they chose ( editing, copying pasting etc.).
Related information should be stored together (Encapsulation).
...related information should be stored in a single area. This reduces the chances of "losing" critical data.
Collaboration: Users want to collaborate on their projects.
...simultaneous access to information. However, users do not want their changes to be overwritten by others.
Users want to work anywhere, anytime:
... to work on projects when "offline", disconnected from the Network.
When ready, users want their work to be synchronized with other users:
... to be able to send and receive updates from master databases at any time.
Security: Users want to protect their information.
... specified users only should be able to read or edit restricted material.
Internet Access:
...this functionality should be available on the web, when using a generic browser.
Communication: Users want to be in communication with each other.
...users want to communicate via Email; They want to schedule meetings. They want to know who is available.
Development: The Design of the database should be stored in the database itself.
When the database design is stored as data, then any changes made to the design will immediately be copied when the database is synchronized with other copies. In this way the implementation of design changes is automatic and does not involve application support personnel. ( Compare this to the usual case in which executable code must be consistently distributed to all users when the design changes )
These requirements are easily stated.
However, Building an integrated development platform that provides this functionality is a daunting task.
These requirements describe a platform for the development of flexible, collaborative systems.