home

What Business Analysts Need to Know About the Decision Model – Part 1 of 2

by Barbara von Halle and Larry Goldberg

To appreciate the relevance of this article, RQNG readers need only consider the global economic panic of 2008. What business decisions and rules were in place to manage risk? Were they included in business requirements? Who was managing them over time? Most importantly, how do we manage them better in the future?

The good news is that the Decision Model is part of the answer. The business analyst is part of the solution.

AttachmentSize
What_Business_Analysts_Need_to_Know_About_the_Decision_Model-Part_1.pdf263.42 KB

Article Sponsored By

HP
view counter

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group