Maintenance software processes for web 2.0 based learning management systems
As we know all software products require maintenance and support. After observing time requirements for maintenance and all needed innovations and changes I realize that cost for those activities is somewhere around half of all bugged for software product. The more years is software used and alive the more time and costs are required. Linear dependency between realized changes and costs is changing into exponential dependency as the years go. Bad and unwanted structural changes at the very beginning of software design could overcharge software maintenance. It is nothing uncommon that maintenance of poorly or wrong designed software products (for example LMS) can achieve point when cost of new development is lover than actual cost of maintenance. In this contribution is presented a proposal of effective software maintenance adverted for web 2.0 based LMS system. Our proposal exploits what should be the proper way of software design, what are the common mistakes, what are our personal experiences and finally how to gain the low cost software maintenance.