Ben Hyde (Chooce me Matie: get things done or it’s a flogging:) and Oliver Steele (Responsive User Interfaces and Effective People) have each written posts looking at David Allen's Getting Things Done (GTD) from a software architecture point of view. GTD means many things to many people, and I always learn something from the various viewpoints. Ben likened GTD to "a real time control system master scheduling module", while Oliver described GTD as

a really sophisticated priority queue, and a decision procedure for deciding what to execute immediately and what to place in the queue. Each item in the queue has metadata: whether it has multiple steps, whether it requires additional information, its priority, external deadlines, and the context that the item requires: people, place, time, and energy

Oliver had begun by looking at how to make a responsive user interface, and then went on to describe the application of a sophisticated GTD priority queue to user interface architecture. I really agreed with many of the ideas that Oliver talked about in his post. I found the reference to SOAR and blackboard architecture to be interesting. We are reaching the point where lots of systems need to incorporate "AI"-like functionality in them. Witness the JSR for rule-engines, as an example of this trend.