Resources
Location:
Failed Automation: Focusing on Requirements as a Key Systemic Cause

Failed Automation: Focusing on Requirements as a Key Systemic Cause

Title:Failed Automation: Focusing on Requirements as a Key Systemic Cause (ID: E08_47537)
Author(s):Bruce Maas (University of Wisconsin-Milwaukee)
Topics:Administrative Systems, EDUCAUSE 2008, EDUCAUSE2008, Enterprise Systems, Implementation, Software Maintenance and Management, Systems Implementation
Origin:EDUCAUSE Annual Conferences (10/30/2008)
Type:Presentations and Seminars
Abstract:

A new practice has evolved over the past four years, and it promises to radically improve success and cost of software implementations. The International Institute of Business Analysis has developed a body of knowledge that promises to lower costs and risks through up-front investment in a disciplined requirements gathering process.

View this resource:
Requirements version compatible with publishing copyright
 |  |  |  |  |  | 
  • 801 reads
Bookmark/Search this page with:
   del.icio.us   Digg   Google   Yahoo   Technorati Stumbleupon Facebook Twitter

 
© Copyright 1999-2009 EDUCAUSE
  Unless otherwise noted, EDUCAUSE holds the copyright on all materials published by the association, whether in print or electronic form. In certain cases the work remains the intellectual property of the individual author(s) (see Special Circumstances). Content from conference speeches, presentations, blogs, wikis and feeds reflect the opinions of the author, and not necessarily those of EDUCAUSE or its members.