July 21, 2008
One of the best practices that ITIL brings to the party within Incident (case) Management is prioritization. ITIL calls out 3 separate attributes: impact, urgency, and priority. Impact: the measure of how business critical it is. Urgency: a necessary speed of resolving an incident. Priority: formulated from the combination of impact and urgency. Some formulate it as Priority = Urgency + Impact. Others use Priority = Urgency * Impact. They key difference that ITIL presents with the concept of Priority versus the classic usage of Severity is that severity alone does not provide enough context for Prioritization. The urgency factor needs to be added to severity in order to provide an accurate understanding of how to prioritize activity. Example of a priority coding system Impact, Urgency, and Priority within Dovetail Within Dovetail (and Clarify/Amdocs), Severity and Priority…
Impact, Urgency, and Priority of a case
July 21, 2008
One of the best practices that ITIL brings to the party within Incident (case) Management is prioritization. ITIL calls out 3 separate attributes: impact, urgency, and priority. Impact: the measure of how business critical it is. Urgency: a necessary speed of resolving an incident. Priority: formulated from the combination of impact and urgency. Some formulate it as Priority = Urgency + Impact. Others use Priority = Urgency * Impact. They key difference that ITIL presents with the concept of Priority versus the classic usage of Severity is that severity alone does not provide enough context for Prioritization. The urgency factor needs to be added to severity in order to provide an accurate understanding of how to prioritize activity. Example of a priority coding system Impact, Urgency, and Priority within Dovetail Within Dovetail (and Clarify/Amdocs), Severity and Priority…
July 16, 2008
We are starting to use WatiN to automate the testing of a web application. So far it is working pretty well. One of the things I found confusing was handling confirmation alerts like this: Pop-ups like this need to be handled by Watin. The code for handling this looks like this. //setup a handler with Watin var confirmDialogHandler = new ConfirmDialogHandler(); browser.DialogWatcher.Add(confirmDialogHandler); //click the button that causes a confirmation pop-up browser.Element("buttonId").ClickNoWait(); //Clickon the ok button of the confirmation window. confirmDialogHandler.WaitUntilExists(); confirmDialogHandler.OKButton.Click(); browser.WaitForComplete(); //You may want to test that the message is correct. //cleanup browser.DialogWatcher.RemoveAll(confirmDialogHandler); There is a lot of setup and teardown for the simply clicking a button. Using some .Net 3.5 goodness I created an extension method to make this a little more terse. //usage Browser.OkButtonClickedOnConfirmDialog(ClickOnUnMarkMasterButton); //could use a lambda but this utilty method…
July 11, 2008
I came across this code today, and it took me a second to figure out what it was doing: strSortOrder = document.getElementById("ad").options[document.getElementById("ad").selectedIndex].value; To break it down, it locates a Select control on the page (FindElementById), finds the element again and gets its selected value's index (selectedIndex), and sets the variable to the value of the option at the specified index (options[index].value). There is a jQuery plugin that really simplifies this process. Using jquery.selectboxes.js, the code now is as simple as this: strSortOrder = $("#ad").selectedValues(); This code now does the same thing, but it is also easy to read, and understand. It shortened from 86 characters to 26, and now requires no explanation. There are many different cases where jQuery can simplify the code.