By Topic

Why can't we implement this SDM? [systems development methodology]

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
T. Roberts ; Dept. of Manage. Inf. Syst., Univ. of Central Florida, USA

To cope with the mounting demands for large, complex information system applications, most organizations turn to a systems development methodology. SDMs are logically appealing, offering a flexible framework for the sequence of tasks needed to develop an application, as well as tools and techniques for accomplishing these tasks. By creating an engineering-like development discipline, SDMs provide explicit deliverables and consistency as information systems are built. In its intent, an SDM should reduce the risk associated with shortcuts and mistakes and ensure that quality infuses the software process. On the surface, at least, it would seem that every organization should have an SDM in place. Unfortunately, most IS organizations fail to successfully implement and utilize an SDM. The question is, why?

Published in:

IEEE Software  (Volume:16 ,  Issue: 6 )