Highlighted text? Practice this concept. Highlighted passages and figures open related questions.
Practice related questions (1)Progress & bookmarks
Current section
1-3 Maintenance and Disposal Process
p. 270
Practice this section 1 linked exam question with default filters
Progress
Not marked complete
Related questions in this lesson 2
Adaptive maintenance2p. 270 · PDF 274
1 - 3 Maintenance and Disposal Process
1-3-1 Maintenance Process
The maintenance process provides high-cost-performance support for delivered systems and software products. In maintenance, modifications and improvements are carried out while the safety of systems (or software products) is maintained, in response to the occurrence of problems, requests for functional expansion, improvements, and others. In implementing maintenance, maintenance requirements and maintenance frameworks are to be defined, and maintenance agreements are to be concluded, in consideration of both the requests on the part of the party receiving maintenance and the costs and feasibility on the part of the party providing the maintenance.
[Activities of maintenance process] (i) Preparations for initiating the maintenance process (ii) Assessment of issues, and analysis of changes (iii) Implementation of changes (iv) Maintenance review and/or acceptance (v) Support for operational testing and migration
(1) Preparations for initiating the maintenance process
Five tasks are executed in preparations for initiating the maintenance process.
p. 271 · PDF 275
(i) Transfer of deliverables necessary for maintenance
Deliverables necessary for maintenance are to be transferred, including code and databases, design documents, qualification test plans / test results, the acquirer’s acceptance confirmation document, documents concerning current business operations and system operations, and the system migration procedures / migration framework for the new operational environment. (ii) Development of a plan and procedures
A maintenance plan and procedures are to be developed, documented, and executed. (iii) Establishment of problem management procedures
Procedures are to be established for receiving, recording, and tracking problem reports and modification requests from users, and for providing feedback to users. (iv) Management of change activities Configuration management (i.e., defining configuration items and managing information) is to be implemented for managing modifications to the systems (or software products). (v) Development of documents for maintenance
Transferred deliverables are to be identified, and documents for maintenance are to be created as necessary.
In “(ii) Development of a plan and procedures,” a maintenance plan is established in consideration of how maintenance is to be implemented, the type and form of maintenance, implementation methods, points for caution, and other factors. Typical types and forms of maintenance include the following.
- • Preventive maintenance
This is implemented with a maintenance plan prepared in advance, to prevent the occurrence of faults and others. Since it allows planned securing of maintenance staff members, it enables efficient maintenance. - • Daily maintenance
This is maintenance in which the equipment that composes systems is monitored on a daily basis. - • Scheduled maintenance
This is performed periodically. - • Corrective maintenance
This is implemented when faults or abnormal situations occur. Unlike preventive maintenance, it is not scheduled in advance. Because of this, it is difficult to secure maintenance staff, and therefore, it is recommended to put emergency maintenance
p. 272 · PDF 276
staff in regular posts.
- • Non-scheduled maintenance
This is performed when conditions appear that differ from normal operation. - • Emergency maintenance
This is performed for the purpose of restoration after the occurrence of a fault. - • Software maintenance
This is maintenance for the purpose of improving the software configuration items that compose software products or systems (e.g., changes and improvements in programs, changes in documents). By contrast, maintenance of the whole system, including software maintenance and hardware maintenance for the purpose of improving the hardware configuration item (e.g., increasing the hard disk information storage capacity), is called system maintenance. - • Corrective maintenance
This is maintenance (e.g., changes in programs) that is implemented to resolve problems (i.e., items that do not fulfill system requirements) that are discovered after system delivery. - • Adaptive maintenance
This is maintenance (e.g., improvement of programs) that is implemented to resolve issues that occur because of the changes in the environment after system delivery. · 2 questions - • Perfective maintenance
This is maintenance (e.g., improvement of programs) that is performed after system delivery to improve performance and others of the delivered systems (or software products). - • On-site maintenance
This is implemented through on-site visits by maintenance staff members. On the other hand, remote maintenance is performed from a remote location without on-site visits by using WOL (Wake On LAN) and others to boot computers over a LAN.
Since continually securing dedicated maintenance staff members is costly, external contracting (i.e., outsourcing) of maintenance work and others are also to be considered.
(2) Assessment of issues and analysis of modifications
Five tasks are executed in assessment of issues and analysis of modifications.
(i) Analysis of problem reports and modification requests
The effects of problems reports and modification requests on the system and on
p. 273 · PDF 277
related systems are analyzed, in terms of type (e.g., correction, improvements, prevention), scope (e.g., size of modification, cost involved, period to modify), and severity (e.g., performance, safety). (ii) Reproduction or verification of problems
Problems are to be confirmed through reproduction or verification. (iii) Preparation of options for implementation of modifications
On the basis of the analysis, options are to be developed for the implementation of modification. (iv) Documentation
Problems, modification requests, analysis results, and options for implementation are to be documented. (v) Approval of modification proposals
Approval is to be obtained for the selected modification options, as specified in the contract.
(3) Implementation of modifications
Two tasks are executed in implementation of modifications.
(i) Analysis and determination of modification portions
Analysis of modifications is performed, and the system (or software) and related documents to be modified, and the content of modifications (e.g., functional additions, performance improvements, correction of problems), are determined and documented. (ii) Implementation of modifications
Modifications are implemented. Modification tasks are implemented according to the system development process and the software implementation process. Depending on the object and content of modifications, the planning process and the requirements definition process may also be used. – The requirements and evaluation criteria of maintenance testing to verify modifications are to be determined and documented. In addition to testing to confirm whether the modified portions accurately fulfill modification requirements, maintenance testing includes regression testing to verify that there are no effects on unmodified portions. – Reverse engineering to analyze and derive the specifications of in-service systems (or software products) is to be performed as required.
When modifications consist of the correction of problems, implementation of preventive
p. 274 · PDF 278
measures against recurrence of problems is also to be considered. In order to prevent recurrence of problems, the root causes of the problems are to be identified through specific cause analysis, and others, and the possibility of the occurrence of similar problems is to be considered. Depending on the results of consideration, improvement of the systems (or software products), revision of manuals, and others are to be implemented. When prevention of the recurrence of problems is deemed difficult, life cycle evaluation must be performed, with disposal also taken into consideration.
(4) Maintenance review and/or acceptance
Three tasks are executed in maintenance review and/or acceptance.
(i) Review of the modified system
A review is to be conducted in order to confirm the integrity of the modified system. (ii) Approval of completion
Approval is to be obtained regarding the satisfactory completion of modifications. (iii) Updating of documents for maintenance
Documentation for maintenance is to be updated as required.
(5) Support for operational testing and migration
Two tasks are executed in support for operational testing and migration.
(i) Support for implementation of operational testing
Prior to the release of a system (or software product), the operator is to take the lead in supporting the implementation of operational testing to verify whether there are any problems in the production environment. (ii) Support for migration
The migration of a system (or software product) to the production environment is to be supported. The general migration procedures for the system (or software product) are as follows:
1) Documentation and verification of the migration plan
2) Notification of migration plans and others to all concerned parties
3) Parallel operation of the old and new environments, and disposal of the old system
4) Notification of migration to all concerned parties
5) Migration evaluation (i.e., verification and review of migration results)
p. 275 · PDF 279
6) Maintenance of old environment-related data, and assurance of security
Section progress
Original chapter exercises
Original chapter exercises →New FE Textbook Vol.2 · First Edition, April 2015