On Wednesday evening, February 15th, Joe Shideler and I will be presenting at a special combined meeting of IEEE Computer Society, Austin Chapter and Austin Software Process Improvement Network (A-SPIN). The title of our presentation is Beyond The System Shall – A Journey From Good to Great Requirements. This is the event that was originally scheduled back in December but was cancelled due to Austin’s blizzard of 2005. Here is the overview:
Today, only a small percent of IT projects succeed while the rest significantly under perform or fail outright. ArgonDigital will begin the presentation by delving into the statistics behind this statement and then move on to discuss how poor software requirements are a primary reason. The presenters will explore the root causes behind the problem and then provide suggestions as to how companies can improve the situation. A key insight is the notion that requirements engineering will never be a one-size-fits-all discipline. Success requires that companies not only find the right people and give them the appropriate resources, but also allow them to develop and apply a varied set of tools for meeting disparate software requirements challenges. Of these tools, perhaps none are more important than the set of models that can drive completeness and clarity into software requirements specifications. The presentation will close with an overview of these models including examples of use cases, state diagrams, decision trees, and others.If you have been enjoying the Requirements Models blog entries that Joe has been posting, here is your opportunity to see him discuss the first two models in person (model1, model2) while also getting an introduction to some of the other models he will be writing about over the coming months.
We will be starting at 6:30 and ArgonDigital will be providing pizza and a door prize.
More information and directions to the event can be found here.
See you there!
Using Agile Principles in Workflow Automation Organizations that implement workflow automation solutions typically attempt to automate the entire end-to-end workflow in one big deployment. This