When I read a chapter 8 “Software Maintenance: Enhancing
Legacy Software Using Refactoring and Agile Methods” of Engineering
Long-Lasting Software, I totally agreed with Maintainability. It says that
there are four important points of maintainability. Those points are important for creating a better product than before. The book says following
categories:
- Corrective maintenance is to fix defect and bug.
- Perfective maintenance is to expand the function of software for new customer.
- Adaptive maintenance is a process under the system is set to adapt the change inside or system environment.
- Preventive maintenance is to improve structure of function for the future.
The purposes of those kinds of maintenances are to improve a
product. I think that all of those categories of maintenances are so important.
When I read it, I associated contents of those four categories of maintenances
with my previous job. I was engineer and fix machines that makes display for
phone, television, and any other device that needs a display. The machines were
doing the same mistakes a lot and after 2 hours I fixed the machines, they
would do the same mistakes again and again. If we did correct maintenance for
them, it would be working better. In my case, we need Adaptive maintenance and
Preventive maintenance.

Nicely formatted post Yoshi. I'd say you're generally getting some of the ideas of maintaining software, and it's great that you're linking the concepts with the work that you did on screen displays, however the key aspects of this chapter are about software maintenance, and I wonder if there aren't some fundamental differences. This chapter matches to the "Typo" coding homework from EdX which I made optional, but that would be the key thing to do to really grasp what this chapter is about ...
ReplyDelete