« Usability for rich internet applications | Main | Intranet is a process »

Avoiding coupling in your portal implementation

Robert Bogue has written an article about avoiding coupling in your portal implementation. To quote:

Portals, which are necessarily at the heart of an ever-changing array of programs and solutions within the organization are especially vulnerable to coupling. It starts out simple at first: the special notice that one application needs, and before long your portal projects are caught behind the schedule of a dozen other applications --- and a dozen different projects are waiting on your portal project to be revised before they can put changes into their products

Posted by jamesr on February 23, 2006 08:35 AM
Categories: Content management, Information management