Skip to main content

Disposition

A gave me some input on how to disposition the thesis

State of art. Describe the existing systems. Theory.

I've found an increasing amount of WCMS (as you can see on my links), and a lot of these are based on open source, particularly php, but I believe java will soon catch up (http://theserverside.com/news/thread.tss?thread_id=33163).

Also note in the discussion between KM and CM, the CMS fall into categories like Groupware, e-Learning, Portals and Wiki. These are classical KM IT-tools, but still the KM protectors have a belief that CM is nothing but the treatment of data and information. Au contraire (*sp), but we've found our own word for that: Content Repository, and about everyone who are dealing with CMS these days are very excited about the coming Content Repository standards and implementations, either you're talking about WedDAV or Jackrabbit.

Also bring in discussion on the work of others on the subject. Write down summaries of the articles and books I read.

The requirements, the users. How we gather requirements for the WCMS.


In P, we recently had a customer session digging out the requirements from our users. We're applying a lightwheight form of the Scrum methodology, which is a lightweight variant of XP, which is again supposed to be one of the lighter, big-M Methodologies.

The point being is that we model/assign requirements as "User Stories" (written by the customer, max 3 sentences, describes a function in the system) instead of classical Use Cases. We scrambled together about 50 user stories, most of which can be applied by all our different customers, the rest are very customer specific.

Example of customer specific functionality is NAAF, where a professor up in Trondheim feeds pollen-data into the CMS so that is published NAAF's webpages (in a much more readable view), and syndicated to a set of subscribers through email.

The User Stories will lead to Acceptance Tests, which will together with software architecture make up the Unit Tests. Also bring in discussion on the work of others on the subject. Write down summaries of the articles and books I read.When we have solved the Unit Tests, hopefully the Acceptance Tests will also run successfully, and then the product will be complete. Unfortunately, by that time, 10 new User Stories have emerged. The key here is to have a component architecture which makes it easy to integrate new functionality as components.

Prototype. Design.
Appfuse, Jackrabbit, content repository JSR-170, portlets JSR-168, JSF and the middle-tier made flesh&bone oughta do it!

Use of CMS. Validate the system. Metrics.
Now this is trickier biz. As we are an external organization we have no say in how our customers measure the inward improvement in workflow and document process. We should however supply the customers with some tools and methods for doing this. Perhaps some surveys now on how publishing and web editing is done, and how much manpower is spent.

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration

Joining eyeo: A Year in Review

It's been well over a year since I  joined eyeo . And 'tis the season for yearly reviews, so... It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling. Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes: How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies wit

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams. If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming.  Since these tools are for gamers, they have to be fast (low latency) light (as not to steal CPU-cycles from heavy games graphics)  moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak , Ventrilo , more recently the massively grown Discord , and finally Mumble , which is the open-source alternative of the gang. A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSp