Although the system has been operational for a short time, users already have submitted several requests for enhancements and noncritical changes. Should New Century use a maintenance release methodology to handle the requests? Why or why not?

What will be an ideal response?

Answers will vary. Students should explain that when a maintenance release methodology is used, all noncritical maintenance changes are collected and implemented simultaneously. A release methodology usually is cost-effective and advantageous for users because they do not have to work with a constant series of changes. Another advantage is that all changes are tested together, which reduces costs. Using a release methodology also reduces the documentation burden, because all documentation changes become effective as a package.
Students should point out that a release methodology has some potential disadvantages. For example, users typically expect a rapid response to their problems and requests, but with a release methodology, new features or upgrades are available less often.