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.

Popular posts from this blog

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…

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…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

The Best Log Viewer Ever

This is what it looks like when I want to have a look through the logfile, to see what a user did on one of our machines one day:


Read the whole story about how it works on the Viaboxx Systems blog (and upvote on DZone!).

Microsoft ups their Git efforts another notch

This week Microsoft announced first class Git support embedded in the coming version of Visual Studio.

Now, it's not completely shocking. We could have seen it coming since Microsoft started offering Git repos on CodePlex, and more recently offering a Git client for TFS. In any case, these are some big news. Scott Hanselman weighs on some features and some more background here.

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…