home

Business Modeling

A sub-set of the requirements discipline that deals with the specific techniques, conventions and challenges faced in modeling business processes and information requirements.

Assessing the Impact of Poor Requirements on Companies

This report presents the findings from surveys of over 100 companies and presents definitive findings on the importance and impact of business requirements on enterprise success with technology projects. The survey focused on larger companies and included an average project size of about $3 million.

This white paper is one of three extracts of the study: Business Analysis Benchmark, the Impact of Business Analysts on North American Business, and Technology Projects. This volume focuses on the cost to organizations for using poor business requirements, and the impact that excellence in business requirements can have on time, budget, and overall project success rates.

Diagnosing Requirements Failure

By: Keith Ellis

This report presents the findings from surveys of over 100 companies and presents definitive findings on the importance and impact of business requirements on enterprise success with technology projects. The survey focused on larger companies and included an average project size of about $3 million.

This white paper is one of three extracts of the study: Business Analysis Benchmark, the Impact of Business Analysts on North American Business, and Technology Projects. This volume focuses on uncovering why businesses fail to do a good job on business requirements.

Executive Guide to Business and Software Requirements

By: Keith Ellis

This paper is designed as an executive briefing on the issues surrounding getting business and software requirements right. The white paper is structured so that each page is its own 'mini-white-paper' but each is also part of a total look at better structuring requirements documents, processes and content completeness.

Click here to view a list of IAG Consulting's Whitepapers

    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