Collecting requirements from business processes
Ah, the sweet sounds of success. I got the opportunity, this week, to collect a list of requirements for a…
Ship It!
It’s been a while since I was blogging regularly. The reason: I was in a ship cycle. As we approached…
Software Reflects The Process That Creates It
Of all the ‘laws of software’ that I subscribe to, this one is one of the most fundamental, and unwavering. …
Using the PMO to measure the behavior of the customer
There are a great many products on the market these days that provide information about a set of projects. The…
The business value of elegant design
In my last post, I highlighted the design process, suggesting that designers and architects should consider using creativity, in addition…
Non-Functional Requirements: the "All-Other" classification
I’ve seen various taxonomies of requirements. Like all taxonomies, any set of requirement types exists to classify or partition requirements…
Understanding Governance as Decision Rights
Todd Biske, whom I respect for his writings on SOA, seemed to miss the mark in his recent blog post…
Clarifying the Use Case
A Use case is a cool thing. A little too cool. The term has been occasionally misused, and in some…
Using Business Process Models as the source for software requirements
Requirements elicitation is a critical, yet under-appreciated, activity. A core capability of business analysts, the ability to get the customers…
Preventing Ownerless Activities — the "Blame the Computer" process modeling antipattern – part 2
In a prior post, I described a process modeling antipattern which I called “Blame the Computer.” The feedback helped me…