As I mentioned earlier, one group has claimed it stood up Help Desk using VB (and a 3rd party web tool) in 8 man months. See below for my take on this approach/ (based on some VB noodling over the past 2 weeks)
________________________________ From: Axton <axton.gr...@gmail.com> To: arslist@ARSLIST.ORG Sent: Wednesday, November 14, 2012 1:38 PM Subject: Re: Mirgration from Remedy to other Platforms ** Sounds like a rewrite. Spec your effort on what writing it from scratch would cost. Consider requirements gathering, design sessions, development, testing of various sorts (pen testing, performance testing, unit testing, end user testing, stress testing, etc.), deployment, procurement of hardware and software, data migration, transition efforts, etc. If you are going to write an app that looks and acts like Remedy, why not just stay on Remedy? You need to leverage the benefits and design paradigms of whatever framework you move to. Also, I would not start with the technology selection. Outline the requirements and user stories, then make a product/architecture selection based on those requirements. Axton Grams On Wed, Nov 14, 2012 at 4:42 AM, Misi Mladoniczky <m...@rrr.se> wrote: Hi, > >You are listing programming languages. > >This means that you have build your own version of the AR Server to start >with in order to bring the exact same functionality. > >The more you strip out of the functionality, the less monumental the >project will be. > >You might also pop the form data into Excel worksheets and get some manner >of functionality... > > Best Regards - Misi, RRR AB, http://rrr.se > > >> I am doing a cost analysis for my client to determine how feasible it is >> to migrate custom applications (non-ITIL) written using Remedy to other >> platforms (like Microsoft .Net, Java, etc.) We are currently using >> 7.6.04. >> >> Are there any third party tools currently available to do this? >> Has anyone attempted do to this? If so, any recommendations on how to do >> it or reasons why not to? >> >> Any help/feedback would be appreciated... >> >> Thanks, >> Bruce Wilson >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at http://www.arslist.org/ >> attend wwrug12 http://www.wwrug12.com/ ARSList: "Where the Answers Are" >> > >_______________________________________________________________________________ >UNSUBSCRIBE or access ARSlist Archives at http://www.arslist.org/ >attend wwrug12 http://www.wwrug12.com/ ARSList: "Where the Answers Are" > _attend WWRUG12 http://www.wwrug.com/ ARSlist: "Where the Answers Are"_ Web site: http://www.visualwebgui.com/Gizmox/CaseStudies/tabid/358/articleType/ArticleView/articleId/505/Help-Desk-Ticketing-System-completed-in-only-8-months-with-1-developer.aspx (1) This type of Help Desk tool makes use of the Visual Basic (ASP.Net3.5) (VB) package, with the addition of a third party tool, http://www.visualwebgui.com/ (2) There is no published VB canned package available for Help Desk use; it is stated (see above WebSite) that such a system can be developed in 8 man-months (Golden West Newsgroups). (With assistance from a Windows forms expert). No support would be available for such a system from a third party. (3) EVALUATION: As demonstrated above, a Visual Basic programmer could stand up a working version of a Ticketing System (Incident management) in six months or less. Visual Basic lends itself to rapid development of such a system. Maintenance: A reasonably experienced Visual Basic programmer would have no difficulty in making changes to a well-documented Production system. (4) Development of the standard features: Feature Details (Compared to BMC Remedy as standard) ‘Files’ (Remedy) The tickets for a Form are stored in a Database table. VB facilitates the use of Oracle, Microsoft SqlServer, and Access. It is also convenient, as with Remedy, to store the structure of a Form, and Archive, in Database Tables. Creation of these three types of Files is automated. Fields Field properties would be listed with Right Click on the field, and then entered or modified; these would include ‘ReadOnly’, Permissions etc. Alternatively in Design mode, Fields (for each Permission group) could be assigned (or programmatically assigned) to Read-Only; or Not Visible; in one simple list selection. (Useful for those using the Default View only, and modifying it programmatically) How come Remedy didn't think of this? A variety of VB Pull-down lists is available, covering all Remedy-type lists. Tables VB’s DataGridView provides all the features of a Remedy ‘Table’; The Table is automatically loaded by a ‘TableAdapter’ which is generated on selection of the Database (see above) Active Links (AL) The events triggering an AL are already provided in VB – Form events.. Open, Submit, etc. Field events: Change; Lose Focus; etc. Event handlers would be constructed, using SHADOW and/or OVERLOAD keywords. ACTIONS are straightforward, making use of VB subroutines. These would include PUSH fields or tickets to another FORM; retrieve fields or records from another FORM; etc. Filters, Escalations Similar to the above Email A third-party e-mail engine would be used. Reports Crystal Reports would be suitable; alternatively a VB front-end would permit the User to select (or choose a stored Report) Date Range, AND/OR conditions, and Phrase-Matching, and provide the Result in EXCEL format, for example. This approach is more user-friendly than Remedy reporting. Data import The ‘Files’ are standard Database files (e.g. Oracle or SqlServer) – no special format is involved as with Remedy files, etc. Thus importing from large Data source makes use of the standard procedures laid out for the particular Database. This goes for the usual Validation, Duplication checks, etc. as well. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
