Re: ARS as a development system

[Nicoll, Alan]

** We use Remedy to manage the maintenance and development of a very complex 5.5M LOC real time software application.  We track bugs, of course.  That was the first application built in V3 Remedy.  Now we have 39 applications and I’m adding the next one this week: Effort Tracking is moving from an Excel/Access system into Remedy.  Since we don’t have enough write license I wrote the EFT app to work using Submit for all operations. Here’s our list of applications:   AR System (bug tracking) AR Developer Console AR SW Manager Console AR Sys Subsys InJoin Form AR-Verification Build Schedule Capability CapacitiesAndLimits CCB Customer Engagement Events (Test events) SPARs (Problems from real customers) Enterprise Coherence (our print engine controller runs 8 different families of engines) ET Requests (Enterprise Tools, where I sit) Facilities Infrastructure Project Glossary Goal Hardware Asset Management (controller and printers under test) High Level Designs Invention Disclosure Job Classification LSAM (License & Software Acquisition & Management) Tools Events Messages (‘Door Open’, ‘Toner Low’, etc.) Organization Planning Tracking Issues (Management action items) Process Process Change Request Product Release Reliability Remedy Knowledge Base Service Support Smoke Test SQA Subsystems Time Clock Tool Properties Work Estimation   Why do we use Remedy for all these; because we haven’t found anything better.  The Remedy interface is intuitive and we can quickly implement changes in processes.   Alan E (Nick) Nicoll DocuSP Problem System Administrator Xerox Corporation Xerox Centre Drive, MS: ESC1-615 El Segundo, CA 90245 Phone 310 333-5081  Internal 8*823-5081 Fax 310 333-6898 [EMAIL PROTECTED]   XEROX Technology   Document Management   Consulting Services   www.xerox.com   This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you have received this email in error please delete it. Any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of Xerox Corporation. Finally, the recipient should check this email is authentic and examine it for the presence of viruses. Xerox does perform virus checks but cannot accept liability for any damage caused by any virus transmitted by this email.   __20060125_______________________This posting was submitted with HTML in it___