I am working with clients using an extension of UML to model content structures, ontology/taxonomy, and metadata structure. UML is a good representation to use when communicating with software companies since many have expertise in interpreting these diagrams. There are already standards in place for representing workflows and other architecture components in UML.
Email me directly if you'd like to see an example or two. Shortly, I will be posting (at no charge) a Visio plug-in that represents these extensions to UML. It will be available at the web site listed below (shameless plug). Regards, Jason Kinner Dynamic Digital Media, LLC http://www.dynamicdigitalmedia.com > Date: Thu, 16 Jan 2003 08:49:59 +1100 > To: [EMAIL PROTECTED] > From: James Robertson <[EMAIL PROTECTED]> > Subject: [cms-list] Best practices for specifying information models? > > Hi all, > > I was talking with a client yesterday who is > starting out on a big project to select a > big CMS. > > Now, he is looking at the best way of specifying > "information model" details, to be included in > the CMS tender. > > By information model, he is referring to details > such as: > > * Information architecture (site design, etc) > * Metadata requirements > * Content types > * Workflows > * Enterprise information repositories > * Single-source publishing and content reuse > requirements > * User information (identities, security, etc) > > The idea is to provide vendors with sufficient > information to understand what the specific > business requirements are. -- http://cms-list.org/ more signal, less noise.
