Professional Documents
Culture Documents
CORRECTIVE MAINTENANCE
Fixing or correcting problems with the system. Refers to problems that were not identified during the implementation phase. The changed information system should be tested and the change is documented. It is carried out in three steps:Verification of repair action
CONTINUE
Examples of corrective maintenance are:
Enhance the system when it is lack of a user-required feature
Product redesign
ADAPTIVE MAINTENANCE
Modification or changes made to the software to accommodate new user requirements. Adds enhancements to an operational system-new features, increased capability, or changes that improve efficiency or maintainability. Examples of adaptive maintenance are:
New product offering A change in the way fixed assets are depreciated Updating software to up to date. A modification of calculation in payroll software caused by changes. New legal reporting requirement
PERFECTIVE MAINTENANCE
Making enhancements to improve:
Processing performance.
Interface usability. Improving softwares efficiency or modifying the software to fit more. Precisely to the needs of the user and organizational needs. Improving system efficiency and enhancing documentation. Improve system reliability by preventing potential system errors or failures.
Hardware
Install faster CPU/replace with newer computer. Increase hard disk space to meet needs.
Modify or change input/output devices to speed data entry/output. Replace older CD-ROM drives with the latest models.
PREVENTIVE MAINTENANCE
Taking steps in advance to reduce the risk of a serious problem. Maintaining system documentation and managing all aspects of security, including contingency planning. Examples of preventive maintenance are:
. .
Resetting a persons password. Replacing servers when they become obsolete. Performing a backup. Recharging batteries.
Good documentation
PLANNING
SCHEDULING
REPORTING
There are three types of report: Variance, status and resource allocation reports.
Question 7 Some asked the question why not just build a system in whatever way seems to be quick and easy. Explain THREE (3) reasons why it is important to use system development methodologies when building a system.
2. Help developers in planning, managing, controlling and evaluating the system projects
The developers also should choose the appropriate model that suits their environment and requirements Eg Waterfall Model
3. Helps in assessing, reducing and managing risk involved in system development project. Organization may implement some risk management process thorough the phases and stages available in the system development methodology that it had chosen Example during analysis and design stages