Scribd
Upload
88 views2 pages

Chapter 5 System Development and Program Change Activities PT 7

This document contains discussion questions and responses about system development life cycle (SDLC) activities. It discusses why software projects often underestimate costs and time requirements, especially in training, hardware delivery, debugging, and data conversion. It emphasizes the importance of top management support during implementation to provide resources and signal the system's importance. It also gives an example of how an easier account balance inquiry system increased demand beyond original estimates by making the service more convenient and private.

Uploaded by

Hiraya Manawari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
88 views2 pages

Chapter 5 System Development and Program Change Activities PT 7

This document contains discussion questions and responses about system development life cycle (SDLC) activities. It discusses why software projects often underestimate costs and time requirements, especially in training, hardware delivery, debugging, and data conversion. It emphasizes the importance of top management support during implementation to provide resources and signal the system's importance. It also gives an example of how an easier account balance inquiry system increased demand beyond original estimates by making the service more convenient and private.

Uploaded by

Hiraya Manawari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Chapter 5 System Development and Program Change Activities

Discussion Questions

6. Most firms underestimate the cost and time requirements of the SDLC by as much as 50
percent. Why do you think this occurs? In what stages do you think the underestimates are
most dramatic?
Response: Firms typically understate the implementation time. One reason is due to overly
optimistic estimates of employee training time. Another reason is that hardware does not arrive
on time. Debugging programs is another area where time is often underestimated. Data
conversion from the old system to the new system often takes more time than expected. Further,
systems that were rushed in the systems analysis stage may need more maintenance due to
demands by unhappy users.
7. A lack of support by top management has led to the downfall of many new systems
projects during the implementation phase. Why do you think management support is so
important?
Response: Top management must provide a clear message that the system is important and
also support it with adequate financial resources. If top management does not send a signal that a
system is important, employees (future users of the systems) who are already busy with their
assigned duties may not understand the importance of their input into the new system. They may
view the interviews and questions as a nuisance that disrupts their work. Top management needs
to send the message that the systems requirements analysis is important and compensate for
overtime if necessary. If the employees do not fully cooperate, the system may not be
appropriately designed. Glitches in the system will become apparent in the implementation phase.
Further, the implementation of systems typically employees’ work to increase temporarily as they
learn the new system. Top management needs to be supportive (perhaps in terms of
compensation).
8. Many new systems projects grossly underestimate transaction volumes simply because
they do not take into account how the new, improved system can actually increase demand.
Explain how this can happen, and give an example.
Response: A system that is easier to access and provides information easily may generate
more inquiries than the old system. Take for example the account balance inquiry systems offered
by most credit card companies. The old method of account balance inquiry by a cardholder
involved a conversation between the cardholder and an account representative. The account
representative would ask the cardholder questions and then give the information to the
cardholder. Many companies provided this service only during certain hours. The new systems
allow account balance inquiries 24 hours a day, and no human representative is involved. The
customer uses the telephone keypad as an input device and can obtain account balance
information very rapidly and conveniently. The demand for this service has increased as a result
of its greater convenience and greater privacy.
9. Compare and contrast the structured design approach and the object-oriented
approach. Which do you believe is most beneficial? Why?
Response: The structured approach develops each new system from scratch from the top
down. Object-oriented design builds systems from the bottom up through the assembly of
reusable modules. A top-down approach is advantageous in that the system is designed around
the needs of top management; on the other hand, reusable modules are beneficial for quick
development of new systems. A hybrid system where modules can be redesigned when necessary
or used without redesign when appropriate combines the best of both approaches.
10. Do you think legal feasibility is an issue for a system that incorporates the use of
machines to sell lottery tickets?
Response: The legal concern has to do with the illegal selling of tickets to minors;
however, some states have such machines.

You might also like