Blueprint 2010 features
Bluepring 2010 continues the movement of requirements management tools into the requirements modeling/definition space.
“Requirements have always been the bane of software development throughout the years, there’s no end of statistics that point to requirements as the weak link in software development projects,” said Higgins.
Typically, requirements authors will resort to legal-type text documents, “one of the poorest forms of communicating,” according to Higgins. That is complicated by distributed teams with members of different cultures and backgrounds, he added.
Among the new functionality is a business process diagramming capability so requirements authors can understand the business processes they are trying to automate in the software they are building. “We can sketch up business processes very quickly, very easily, to make sure everybody is on the same page,” said Higgins.
Another feature tracks changes so users can compare two versions of sets of requirements, and automatically output that into document form “as if someone had authored those documents manually,” he said.
Read more at www.itworldcanada.com
