Website Maintenance Planning
The maintenance plan comprises of events done weekly, quarterly and yearly as follows:
Weekly
- Updating the website to reflect the currents and upcoming events
- Uploading additional features as needed such as online payment systems, social feeds, etc.
- Uploading articles, feedback and recommendations from satisfied clients.
- Regular updates of the company’s information. Examples include; new destination packages, discounts and offers, peak and non-peak seasons, etc.
Quarterly
- Link updates: Some links to external sources, for instance, references may become broken or cease to exist. Updating the links means deleting such links or replacing them with new ones.
- Website review: This involves utilizing feedback and statistics in identifying client’s preferences and updating the web pages in a manner to improve the user’s experience.
Yearly
- Content review: This involves assessing the content on every web page to determine the relevance of the website regarding current events and modifying the web pages accordingly.
- Scheduling: this involves construction of timetables for intended technical reviews to assess the technological aspects of the website. e.g. incorporation of online payment systems.
- Section review: this involves an assessment of main section contents to determine whether to do away with them or add new sections.
- Data collection: The database should have a data collection mechanism to collect user statistics, such as user ratings, to guide in the appraisal of the website.
Form processing Solution
The form processing solution is a product from “net46.net” domain. The form processing solution allows users to type their feedback on the display area and post them for the website administrator’s review. Once posted, the website forwards the contents to the administrator’s company email address who then shares the contents with the management team for action.
Testing Details
Tracking the outcomes: The hosting and execution process in the course of website for the first time usually generates multiple errors. This case was no different. As such, I devised a method by organizing and categorizing the errors depending on the type. Through such means, it was easy to deal with the errors depending on their nature e.g. runtime errors that occurred during the execution, and compilation errors that resulted due to code mismatch.
Test Environment: The test environment comprised of two different work areas; one with the actual files and the other with a backup copy just in case something went wrong.
Usability Testing: The usability tests involved conducting tests using several criteria. Such criteria include; ease of navigation through the web pages, clarity of the web pages so as not to confuse the user, and consistency of the website from one web page to another. The consistency of the web pages in terms of font, uniform links and uniform backgrounds enabled the website to remain neutral while at the same time easing the navigation process from page to page.
HTML verification: this is the language that communicates between the web-server and the website. I used validator.w3.org to validate the HTML codes for all web pages since it was cumbersome to go through all of them manually. For all errors noted, I manually rectified the HTML code.
Load Testing: After hosting the website, I tested the functionality of the web pages. From such, I was able to get the first-hand experience of the website just like a normal user. The simplicity of the website coupled with its brevity rendered a remarkable user experience with minimal load time on the hosted website.User Acceptance Testing: This involves testing the website to ensure the complete functionality of all websites. Simply put, the website achieves the intended objective. For the case in question, the website provided the relevant information to the intended users.
Security Testing: The website being a sample of an education website hosted on a free platform, the main feature of security was the use of strong passwords.
References
Porrill, D. (n.d.). Constructing an Effective Maintenance Plan. Retrieved December 3, 2014, from http://www.reliableplant.com/Read/338/effective-maintenance-plan
Testing Your Web Application - A Quick 10 Step Guide. (n.d.). Retrieved December 3, 2014, from http://www.adminitrack.com/articles/testingyourwebapps.aspx
Thatcher, J. (2002). Constructing accessible web sites. Birmingham, U.K.: Glasshaus.
Weiss, A. (1997). The Web authoring desk reference. Indianapolis, IN: Hayden Books.
