Chapter 9 • Methodologies for Custom Software Development 387business at the time of installation. IS specialists typically
hold primary responsibility for most system analysis and
all system building steps. However, the systems project
may be managed by an IS manager, a business manager,
or both.
Rapid application development (RAD) methodolo-
gies have become more important as businesses seek to
deliver high-quality applications within shorter time
frames. A RAD methodology combines the iterative de-
velopment benefits of prototyping with the quality con-
trols of the SDLC; this approach also typically relies on
JAD sessions and software automation (CASE) tools to
generate code. In recent years, there has also been a
movement to develop more “agile” development methods
based on the principles of simplicity and feedback, with
relatively small project teams. One of the characteristics
of an agile method called eXtreme Programming is an
obsession with testing code early and often, in order to
have zero defects. Another method called Scrum utilizes
many work teams and frequent meetings to coordinate
and share work experiences.
The chapter includes some guidelines for managing
the interactions between project team members when there
are off-site (including offshore) contract workers on a proj-
ect. These guidelines address managing expectations, inte-
grating off-site staff with internal IS staff, communicating
frequently, creating a centralized project management
office, beginning with pilot projects, hiring offshore legal
expertise, and securing redundant communication links.
The development of computer applications by business
employees who are not IS specialists has become common-
place. Although there can be clear benefits to having
business users develop applications, both business and IS
managers should carefully consider the characteristics of the
application to be developed, the technologies to be used, and
the skills and experience of the available user developers to
ensure that the benefits are not outweighed by the risks to the
organization for an application developed and maintained by
a non-IS specialist. User developers should also use a devel-
opment methodology that is appropriate for the specific
application, and consultation with IT professionals and
auditing personnel should be encouraged, as appropriate.Review Questions
1.Briefly describe the typical steps in the typical systems
development life cycle (SDLC) as presented in this chapter.
2.Describe the key activities performed by IS professionals in
each step of the SDLC.
3.Select three characteristics of a high-quality application sys-
tem, as shown in Figure 9.3, and provide a rationale for why
each is important.
4.Describe the importance of documentation under an SDLC
methodology.
5.Describe a distinct advantage of each of the four strategies
for implementing a new system, as shown in Figure 9.4.
6.Briefly describe the elements of a business case for a new
information systems project under the SDLC methodology.
7.Why is an accurate and complete requirements definition
especially critical when using the SDLC “waterfall” approach?
8.Briefly describe the steps of a pure prototyping methodology
as an alternative to an SDLC approach.
9.Which disadvantages of an SDLC methodology are
addressed by a prototyping approach?10.Describe two ways that a prototyping approach can be used
within the Definition phase of a traditional SDLC methodology.
11.Why are JAD techniques a key characteristic of RAD
methodologies?
12.Describe how a RAD methodology builds on the strengths of
both an SDLC methodology and prototyping.
13.Why does the use of contractors increase the complexity of
an IT project?
14.Describe the underlying principles of agile systems develop-
ment methodologies.
15.What conditions and methods improve the chances that off-
shore outsourcing of systems development will be successful?
16.Describe one application, tool, and developer characteristic that
should be assessed when evaluating whether or not a given
application should be user developed, including what you see as
the potential business risk associated with each characteristic.
17.Choose three of the Definition questions in Figure 9.16 that
the user developer should address and explain why they
could be important.Discussion Questions
1.Discuss why you think the SDLC methodology for develop-
ing application systems was widely adopted in U.S.-based
organizations by the early 1990s. Further, what has changed
to encourage other approaches to become so popular?2.IS department managers often believe that they are
responsible for making sure the requirements of the sys-
tem are properly defined, but in this chapter the business
manager’s responsibility for defining requirements is