About | HeinOnline Law Journal Library | HeinOnline Law Journal Library | HeinOnline
LOG IN
LOG IN

132203 1 (1987-01-01)

handle is hein.gao/gaobaduyw0001 and id is 1 raw text is: / - - ,- r. RISK AND CONTROL OF THE SOFTWARE MAINTENANCE PROCESS y.Frdrick Gallgos, CISA, CDE S.Gnra Accounting Office The increased demand for new or improved com- puter information systems application has created a number of problems for the DP professional, the users, an,; management. Staff and budget con- straints limit the ability of DP managers to respond to this demand. Antiquated or poorly designed sys- tems have created severe maintenance and perfor- mance problems, leaving little time to develop new applications or improve existing systems. Thus, the risk and control of maintaining the software is an important goal, an institutional goal toward which all must work, In response to this goal, the National Bureau of Standards issued its Federal Information Process- ing Standards Publication Number 106, entitled Guideline on Software Maintenance. The Guideline provides general guidance for managing software maintenance. It does an excellent job of com- municating that improvements in the area of soft- ware maintenance will come primarily as a result of the software maintenance policies, standards, procedures, and techniques instituted and enfoirced by management. Controlling the software maintenance process is an institutional goal, which management, users, and DP professionals must collaboratively work toward. Controls involve how well they work together in per- forming the software maintenance process illustrat- ed in Figure A. Everything that is done to software affects its 12 * Quality Data Processing quality. Thus, measures should be established to aid in determining which category of changes are likely to degrade software quality, especially impact to the FIGURE A THE SOFTWARE MAINTENANCE PROCESS 1. Determination of need for change 2. Submission of change request 3. Requirements analysis 4. Approval rejection of change request 5. Scheduling of task 6. Design analysis 7. Design review 8. Code changes and debugging 9. Review of proposed code changes 10. Testing 11. Update documentation 12. Standards audit 13 User acceptance 14. Postinstallation review of changes and their impact on the system 15. Completion of task user. The primary purpose of change control is to assure the continued smooth functioning of the application and its orderly evolution. Examples of such controls are described in Figure B. .......... m

What Is HeinOnline?

HeinOnline is a subscription-based resource containing thousands of academic and legal journals from inception; complete coverage of government documents such as U.S. Statutes at Large, U.S. Code, Federal Register, Code of Federal Regulations, U.S. Reports, and much more. Documents are image-based, fully searchable PDFs with the authority of print combined with the accessibility of a user-friendly and powerful database. For more information, request a quote or trial for your organization below.



Contact us for annual subscription options:

Contact Us

Already a HeinOnline Subscriber?

Log In

profiles profiles most