Thursday, February 19, 2015

Facebook Stetho debugging tool

http://thenextweb.com/facebook/2015/02/18/facebook-releases-stetho-powerful-debugging-tool-android/

Wednesday, February 18, 2015

Wednesday, February 11, 2015

ITIL - Relationship between Incident Management, Problem Management and Change Management...

This is a published article from ComputerEconomics.com by Robert Boyd. 

The article source is here: http://www.computereconomics.com/article.cfm?id=1074

I reproduce a part of it below. 


  • At TIME = 0, an External Event is detected by the Incident Management process. This could be as simple as a customer calling to say that service is unavailable or it could be an automated alert from a system monitoring device.
          
    The incident owner logs and classifies this as incident i2. Then, the incident owner tries to match i2 to known errors, work-arounds, or temporary fixes, but cannot find a match in the database.
     
  • At TIME = 1, the incident owner dispatches a problem request to the Problem Management process anticipating a work-around, temporary fix, or other assistance. In doing so, the incident owner has prompted the creation of Problem p2.
     
  • At TIME = 2, the problem owner of p2 returns the expected temporary fix to the incident owner of i2.  Note that both i2 and p2 are active and exist simultaneously. The incident owner for i2 applies the temporary fix.
     
  • In this case, the work-around requires a change request.  So, at Time = 3, the incident owner for i2 initiates change request, c2. 
  • The change request c2 is applied successfully, and at TIME = 4, c2 is closed. Note that for a while i2, p2 and c2 all exist simultaneously.
     
  • Because c2 was successful, the incident owner for i2 can now confirm that the incident is resolved. At TIME = 5, i2 is closed. However, p2 remains active while the problem owner searches for a permanent fix. The problem owner for p2 would be responsible for implementing the permanent fix and initiating any necessary change requests.