All Entries Tagged With: "design"
Time Travel for Context-free Use Cases
Yes, sometimes we BA’s need to think of creative ways to help us withhold the technology and implementation detail from our requirements.
Classic Business Analysis Articles
I was sorting through some of my bookmarks and articles I’ve accumulated over time via the Web, and found that there are a few articles that I seem to refer back to time and again.
Sherlock Holmes on the Necessity of Requirements
During some time off a while back, I went to Project Gutenberg and downloaded The Adventures of Sherlock Holmes. I still haven’t read them all, but I was surprised to see the great detective speak out so strongly in favor of requirements in A Scandal in Bohemia.
Accounting for Technical Debt
Hidden costs of the “quick and dirty” solution.
Weekly Digest 08-44
Perfection in design, agile heresy, BABOK mapping, meeting humor, and Tyner Blain has a fan club!
Weekly Digest 08-42
BABOK updates, “what vs. how”, new blog subscriptions, Google Pagerank and an awesome picture.
How hard could it be to design the stop sign?
I recently stumbled upon this video, got a kick out of it and thoughts I’d share. It is basically a video parody for the process of designing the stop sign if the project were kicked off in 2008. There have definitely been times in my career as a BA where I’ve felt like the poor chap trying to design to the customers’ specs.
Oh.. and for geeks like me who saw this and then wondered when we really did get the stop sign, here’s an interesting link.
With requirements, discussions matter most
Mitigating the waterfall effect.
Economist Sowell on… Usability!
I love reading Thomas Sowell’s articles on economics and its social and political ramifications. His “Basic Economics” book broke down the basics of supply and demand as well as other economic principles in a way even I could understand! Today, however, his article was a rant on how hard today’s electronic gadgets are to use.
Design for Use and Reuse
One way IT factories can really hurt themselves and their companies is by underemphasizing, or not considering at all the notion that systems and components should be designed with “reuse” in mind.
What is reuse, or the Reuse Model?
Avoiding the “How” Trap in Requirements Authoring
One of the main challenges in drafting requirements is to state “what” the solution must entail, and not “how” the solution must be tailored. I found the excerpt below from a paper authored by Ivy Hooks very helpful.