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

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 operating on many repositories at the same time.

I discovere…

Working in Teams over Working as Individuals

I recentlypostedthis sketch on Twitter:

Thanks to a few mighty retweets, it gathered a lot of views (9000 impressions, whatever that means). While that's fun and all, I still felt a bit sad that such an awfully simple insight can garner much more popularity than a thorough blog post that I put some hours into.

So, rather than let Twitter get away with this, I'll steal my own content back into the blog :)

The thread went like this:

Pondering how to battle individualism in companies. For some, it is counter-intuitive that teams can be more responsive, faster and even more accountable than single individuals.

Having "teams" in place is no guarantee that team work is happening. Be wary of too large teams, "I/me/mine", personal contact details instead of team point of contact. Good team is sailing crew, not galley slaves.

Beware heroes, go-to persons, calling in favors and other shadow handling of work. Real teams make the work explicit, both requests/needs and re…

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

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 without the…