EC

Errors Checking

After the internationstudentSD.com website have been created. Error checking of the website is imperative to ensure the website is operating successfully. There are myriad of services which are capable of checking your website for errors and finding ways of improving websites on the Internet. Some of the common mistakes web developers fail to ensure when testing a website for errors are:

HTML Validation Errors- Does the website contain hidden errors? Although you can’t see them, the search engine can detect the error, and they don’t like errors on your websites. Errors such as HTML validation can hurt your search engine ranking or make it so potential visitors can’t see your site properly.

Broken Links- Broken links are unprofessional. All website sites should be tested by a website checker to ensure the pages lead to live web pages.

Meta Tag Content- Adding Meta tags can help search engines and visitors understand your site. Meta tags make also persuade users to click on your link in the search engine result. For example, Google shows your website title and description using Meta tags.

Web Page Size- if internationstudentSD.com does not load quickly we risk losing customers. Error checking testing shows the size of your home page.

Priority & Severity

When it comes to websites testing Severity and Priority are attributes of a defect and should be provided in a website testing report. Severity of a defect is related to how severe an [website] error is. Commonly, severity is defined in terms of a financial loss, customer’s loss, and company’s reputation.

Priority of a defect is related to how quickly an error should be fixed and deployed on live servers. When a defect is of high severity, it will more than likely have a high priority. The same applies to low severity defect.

As a web developer hosting many websites, it is recommended to provide both severity and Priority when submitting an error report. Reports are normally done by a developer, but it should be reviewed the team as a whole and come up with a plan of action to mediated the error.

Technical Review

A well define website content production process is a good start. However, without a clear understanding of who is responsible for getting the process done is imperative.

Reviewing the web content may fall into:

· Subject Matter Experts

· Senior Editor

· Copywriter

· Marketing Manager

These tasks can be split across several roles. The subject experts may be asked to check if the content is accurate. The Senior Editor may check the website to ensure the content [the website] is well written, consistent with the rest of the website content.

Change Control Process

Change control is defined as a systematic approach to managing all changes made to a product or system, in our case a website. The responsibilities of site maintenance extend beyond issues of immediate operations. As stated earlier change control is something that is inevitable when creating a product from beginning to end. There are four key steps to effective change control.

1.Define the Change Request

Change Control is the process. A Change Request is the documentation used to request the actual change. Whoever owns the actual request needs to explain it in such a way that the team understands it well enough to define it.

2. Submit and Review the Change Request.

Once the Change Request is documented, it’s submitted to the project team. The process varies from the simple (a phone call or email) to the formal (team meeting). Unless the request is very simple, review the change with the full team. That meeting provides the proper venue for the request to be reviewed, and all members have a chance to ask questions and help make decisions.

3. Define Options and Create Response Document

Once the team has reviewed the Change Request, options should be defined. There should be a minimum of two. When providing the document response, always provide each option with some of the data points below as well as a team recommendation, which represents its view of the best choice.

4. Final Decision and Approval

The customer should provide a timely response. If the Change Control Response document expires, it should be re-evaluated once the customer provides feedback. If too much development has occurred to sustain the change, then that needs to be stated. If the delayed response has resulted in other impacts, they need to be communicated as soon as possible. It’s also possible that an expired response could lead to an additional review and proposal.

Whatever decision results from all this needs to be officially approved. When you define the Change Control process, be sure to include a list of sponsors, stakeholders and key decision makers who can “OK” both the process and the decision.