requirements modeling

Getting Started With A Collaboration Architecture

"So it’s January 2008 and like all good collaboration managers, you’ve
vowed that this will be the year your organization crafts a
comprehensive “Collaboration Architecture” covering tools, processes,
and policies for collaboration in your organization. Easy right?
Well………"

Complete Story at Collaboration Loop

Discussing CMS requirements, file handling, and document management

Recently, I read some good posts regarding content management systems (CMS) on a few blogs I visit almost daily.  The posts have had me thinking and reflecting in general about CMS.  However, I won't talk too much about them so you get a chance to go on and read the articles yourself.  The first post comes from OpenSourceCommunity.org and the second post from Gadgetopia.

Stoyan at OSC asks the question, "What do you think makes a good CMS?"   In the post he discusses which tasks he would like to perform in the CMS as well as what he would like to see with regards to the back-end, front-end, documentation, features, and security.  Hopefully, we'll be seeing a few more people comment on his post with what they think makes a good CMS.  We've had similar discussions here at CMSReport.com...so l am anxious to see more discussion elsewhere about CMS on a different site with a slightly different audience.

Gadgetopia's Deane Barker takes an opposite approach by not talking about what makes a good CMS, but instead focusing on what he sees CMS lack and what needs to be worked on.  Specifically, Barker discusses how file and image handling in content management really needs to be improved in CMS.

Here’s something that frustrates me in a lot of content management systems: file handling. Specifically, the inability to tightly bind a file to one or more content objects, and ensure that it lives and dies solely within the scope of those objects.

IBM developerWorks: Application architecture essentials - Requirements modeling

"Accurate and complete requirements are essential to the success of any software project. Getting this part of the architecture correct requires both people and technical skills to capture and refine the right requirements. Discover the useful skills and tools for modeling requirements, and learn how to evaluate progress in competency."

Complete Story

Syndicate content