This is such a common "issue" so to say. 

Unfortunately at a "line by line of code" (in this instance, fields, AL, 
filters..) it is easy to "get lost" in the total view of the scenario.

This is where "best practice" is that the "customizer" has a "Delta change 
document" which states more or less the following:

* Business Case: <Enhancement/Bug Fix/Process Change/...>
* OoTB Functionality: <xxx>
* Change To Functionality: <xxx>
* Change Details: <Fields, permissions, AL, Filters, escalations, guides, bla>

Of course, this is "Perfect World", which makes everyone's lives so much 
easier, especially when upgrading a system :)

Now in "Real World" where the "Feet hit the street", you are at the correct 
starting place, by obtaining the delta. Now your mission is to "field by 
field", "process by process (workflow)" generate the above mentioned "Change 
Implementation Specifications"...

You didn't mention what "tool" you used to obtain the delta, but I know that 
the Panacea tools are good at documenting the "Process Actions" for the 
workflow (decision trees, if-else logic, etc). But again, just because 
something was "added / changed" does not give the business requirements / 
business logic about it.

I wish you luck in your endeavor!

Thanks-n-advance; 
HDT Platform Incident / Problem Manager & Architect 
Robert Molenda 

________________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of SUBSCRIBE arslist Anonymous
Sent: Friday, June 29, 2007 9:57 AM
To: [email protected]
Subject: Gap Analysis helpdesk

** I have to do a gap analysis between help desk 6.3, and a customized help 
desk 6.3.  I have a migrated report showing which fields/forms/active links, 
etc are equal, unequal and not found.  Is there somewhere a procedure or info 
that can guide me through it?

Thanks!
________________________________________
AOL now offers free email to everyone. Find out more about what's free from AOL 
at AOL.com.
__20060125_______________________This posting was submitted with HTML in it___ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to