VSS ties into Remedy, although it's not an ideal solution.  ARS 7.5 has a 
built-in source control feature.  As Peter said, use Change Management for all 
of your documentation and you'll be able to track it in the future.

Study the CMMI: http://www.sei.cmu.edu/cmmi/

http://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration


Jennifer Meyer
Remedy Technical Support Specialist
State of North Carolina
Office of Information Technology Services
Service Delivery Division ITSM & ITAM Services
Office: 919-754-6543
ITS Service Desk: 919-754-6000
[email protected]<mailto:[email protected]>
http://its.state.nc.us<http://its.state.nc.us/>

E-mail correspondence to and from this address may be subject to the North 
Carolina Public Records Law and may be disclosed to third parties only by an 
authorized State Official.
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Lammey, Peter A.
Sent: Tuesday, October 19, 2010 4:13 PM
To: [email protected]
Subject: Possibly spam: Re: Documenting Remedy customizations and source control

**
I prefer to track all coding releases either in change requests but also 
organize all impacted forms and workflow into a Packing list.
If it fields, then the packing list has the form so then in my change request I 
would write in what fields are actually impacted.
Thanks
Peter Lammey
ESPN IT Packaging and Automation
860-766-4761

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Andrew Yacenda
Sent: Tuesday, October 19, 2010 3:48 PM
To: [email protected]
Subject: Documenting Remedy customizations and source control

**

We are in the midst of an internal audit of our Remedy application.  We are 
looking at findings for inadequate documentation of Remedy customizations and 
"coding standards", as well as for not using software source control tools.  I 
am curious how other groups address these things, and whether it is different 
for large changes (form creation, lots of workflow, project level) versus small 
(couple of fields or workflow objects)?

Thanks.

Andrew Yacenda
Remedy Administrator / Developer
[cid:[email protected]]
817-525-7463 (w) | 214-621-0823 (m)
[email protected]<mailto:[email protected]>


________________________________
Privileged and Confidential. This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain 
privileged or confidential information. If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail. 
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.
_attend WWRUG10 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers 
Are"_
________________________________
Please consider the environment before printing this e-mail.
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

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

<<inline: image001.gif>>

Reply via email to