This is the last part of our software design which describes how we do the maintenance work to ensure our social network can run in long term purpose.

Software Maintenance

The maintenance step keeps our software up to date with environment changes or user requirement. During the earlier phase, we’ve make sure we do everything in a systematic way so that the maintenance work can run smoothly. We keep records of changes made throughout the process so that every member of our group can keep track of what have been done by each other. By doing this, we can prevent the difficulties to trace the process through which software is created.

Besides, we have added comment in the codes so that every member can understand the code better, and every time when some new code has added, we make sure we make comment on it and state down who have made the changes so that there will be no confusion when different codes are combined together.

Structured Maintenance

We have design codes to be changed easily. To do this, we’ve separated codes with different functionalities into different parts, and record down their functions so that they will be easier when we need to refer to specific function. When changes need to made on that specific part, it can then be easily edited by evaluating of design documentation, modify it, review and at last recode it. This will minimize the length of code to change during maintenance and reduce effort needed and some more increase the overall quality of our software.

Above is our structured maintenance request flow chart. By proper records and documentation of codes, we can do the maintenance part efficiently.

Maintenance Activities

Corrective maintenance

This part includes diagnosis and correction of errors. When there’s error found during the testing phase or error report from user, we will analyze the error and make specific changes on it to make sure the social network runs better.

Adaptive Maintenance

This part includes modification to properly interface with changing environments. When we found that there’s some display problem of our social network software when running under different browser, we tried to find out the problem and then modify the codes so that it will display correctly even though different web browser is used.

Perfective Maintenance

This part includes implementing of new system requirements after system is successful. Since our social network software is still new, we did not any new system requirements, but the structure of codes we writes is in a way such that implementing of new function is easy to be done. This ensures the usability of codes for longer period.