An exercise in documenting current state: reddit and the decision tree In an earlier post I detailed how you can use RML models to document
If you look at the role of requirements in a business, there is obvious value: expectations and goals are managed properly, work is organized and
Introduction “Let’s be honest; someone knows how all this stuff works, right?” This is a phrase that may come up in many, many projects in
Whenever I’m in the beginning stages of working on a lengthy requirements document I like to get an idea of how the document will actually
Product Concepts are the blueprints from which our software requirements are built. They can determine large amounts of effort needed for requirements gathering, building, and
Lately I’ve been thinking to myself, “What does it mean to be a professional?” It’s a word no doubt you’ve heard thrown around, often in
When it comes to requirements “communication” is the name of the game. An analyst could crank out top-notch technical documents or business cases, but if
At the end of the first quarter of 2012 there was a slight fluttering through the wind chimes of business journals, technology news sites, Google
Requirements elicitation skills are something I most enjoy learning from my colleagues at ArgonDigital. There is a certain appeal in being able to enter a
When helping ArgonDigital clients define software requirements, one of the many models we use is the Business Data Diagram (BDD). At a high level, the
Just like how any carpenter cannot create without his hammer, the business analyst needs the right tools to ply his or her craft. Cue the
Generate and convert leads, increase revenue through ecommerce, and cut costs by automating operations.