Workshop 7
End of the Line: production site migration and maintenance:
In-house hosting: In house hosting refers to the criterion in which the organisation use their self owned resources to host a website, which may include their own server room and all other equipments. This involves a heavy amount of capital investment.
Outsource-hosting:
As an alternative to the capital intensive nature of enterprise content solutions, outsource hosting offers a lower cost alternative to both smaller and larger organizations that want the power of smart portal technology, yet cannot justify the manpower or budget resources to maintain it in-house.
Cloud hosting:
Website hosted on a cloud hosting operates on clustered servers where online operations are not limited to a single server. By handling security, load balance and hardware resources virtually; the website has access to the processing power of a number of servers that are distributed in real time. (Jerry, 2009)
Implementation: After customer consent toward the application the implementation part is initiated in which the developer actually code the application. And various test, risk management functions are added into.
Maintenance Plan: It refers to the modification of a software product after delivery to correct faults, to improve proformance and add other attributes. This may include the migration process which would require the support of the in-house IT team. Both the maintenance and in-house IT team work together to bring the system up and running with best results.
The key software maintenance issues are both managerial and technical. Key management issues are: alignment with customer priorities, staffing, which organization does maintenance, estimating costs. Key technical issues are: limited understanding, impact testing, and maintainability measurement. The 4 types of maintenance according to ISO/IEC 14764:
Corrective maintenance: Reactive modification of a software product performed after delivery to correct discovered problems.
Adaptive maintenance: Modification of a software product performed after delivery to keep a software product usable in a changed or changing environment.
Perfective maintenance: Modification of a software product after delivery to improve performance or maintainability.
Preventive maintenance: Modification of a software product after delivery to detect and correct latent faults in the software product before them become effective faults.
Monday, May 25, 2009
Subscribe to:
Post Comments (Atom)


No comments:
Post a Comment