We had an email discussion in the office the other day about the term “Requirements Engineering” and I began thinking about most of the research I have read on the
Requirements are often touted as the foundation of a good software project. I agree that without good requirements, you will find it very difficult to build the right solution. What,
I’ve recently had many opportunities to think about software adoption and the many factors that affect it, from both the product management side and the end-user side.In all cases, the
I feel very strongly that the more complex your business process is, the more well-defined your requirements must be. The analysis of these requirements also becomes more and more important
Requirements are constraints on the creativity of creative people. That sounds harsh, but it is true. Business owners and those that finance software projects don’t want just any system built
Data dictionaries have been around for quite a long time. I have a book on analysis that was written in 1979 that covers them in great detail. Unfortunately, most of
My latest requirements model discussion centers around a tool that we developed at ArgonDigital for a very large and complicated web-based application a few years ago. These tables can be
This is post number two in my continuing series of requirements model discussions. You can view my first post here. This time around, I’d like to discuss decision tree diagrams.
As Anthony C. said in an earlier blog post, requirements models are a great way to discover missing requirements in your software system. Without a good model, you have no
Don’t miss out on this opportunity
and request a conversation today!
