Jason P commented to my May 8th entry that a model is not a requirement. I disagree. One of the changes that I would like to see in our industry is a broader use of the word requirement. A requirement can be represented as a sentence, or a symbol on a diagram, or both. For example: Jason says that requirements are derived from models. If I build a data model using an entity relationship diagram, I would not translate those “needs” (requirements) into a textual description (unless the business stakeholders demanded it). The fact that the business needs are represented in a diagram rather than a sentence does not make them any less needed.
I think that it is limiting for us to only use the requirement when we are talking about an English sentence that starts with the words “The system shall . . . “. I would like every artifact that we document to communicate a business stakeholers needs/requests/wishes to be considered a requirement.
- Selecting a Vendor Package (COTS) - June 7, 2010
- When do you learn the business? - April 6, 2010
- Free podcast on Application Modernization - March 15, 2010
- IIBA and Business Rules Community 2010 Conference - January 11, 2010
- BAs NEED management support - December 4, 2009
- WIBADD is really Great!! - October 22, 2009
- Why status reports? - September 25, 2009
- BA Interns - July 20, 2009
- Who performs business analysis work in your organization? - June 26, 2009
- User Stories - April 14, 2009