DOCSLIB.ORG

Ticketing Systems Engineer Gustavo Ramírez Siles [email protected]

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ticketing Systems Engineer Gustavo Ramírez Siles Gramirez@Idsca.Com Ticketing systems Engineer Gustavo Ramírez Siles [email protected] Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team IDSCA Support Development Team 2 Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team 1. Introduction 1.1. Problem It is required to migrate to a flexible ticketing system better than the current one, which can be easily to maintain; open source and can provide an easy way to follow and track issues through tickets. 1.2. Abstract The following document is intended to provide an alternative choice for a helpdesk and development ticketing system for ADSCA technical support department The document has the following sections: 1.3. Ticket systems This section contains the analysis of each ticket system studied. In each subsection it will contain: Summary; Software/Hardware requirements; features; screenshot; advantages and disadvantages of the ticket system been analyzed with screenshots where is needed. 1.4. Discarded systems This section has a list of system that was not included in the analysis and the reason why. 1.5. Conclusions and recommendations In this section will be a result analysis of the tickets studied 3 Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team Index 1. Introduction ......................................................................................................... 3 1.1. Problem ..................................................................................................................... 3 1.2. Abstract ..................................................................................................................... 3 1.3. Ticket systems ........................................................................................................... 3 1.4. Discarded systems ..................................................................................................... 3 1.5. Conclusions and recommendations ........................................................................... 3 Index ...................................................................................................................... 4 2. Ticket Systems .................................................................................................... 5 2.1. OS Ticket .................................................................................................................. 5 2.2. OTRS (Open source Ticket Request System) ........................................................... 7 2.3. RT – Request Tracker ............................................................................................... 9 3. Discarded systems ...................................................................................................... 12 3.1. SysAid ..................................................................................................................... 12 3.2. Mantis ..................................................................................................................... 12 3.3. Bugzilla ................................................................................................................... 12 4. Conclusions and recommendations .................................................................. 13 4.1. Conclusions ............................................................................................................. 13 4.2. Recommendations ................................................................................................... 13 4 Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team 2. Ticket Systems 2.1. OS Ticket 2.1.1. Summary osTicket is a widely-used open source support ticket system. Integrates inquiries created via email and web-based forms into a simple easy to use multi-user web interface. Easily manage, organize and archive all your support requests and responses in one place while providing your clients with accountability and responsiveness they deserve. osTicket is an attractive alternative to higher-cost and complex customer support systems; simple, lightweight, reliable, open source, and easy to setup and use. Site: http://osticket.com/ Demo page: http://www.ostickethacks.com/demo/ Download code: http://osticket.com/dl/osticket_1.6.0.tar.gz 2.1.2. Software/ Hardware Requirements • PHP 4.3+ • MySQL 4.4+ 2.1.3. Features • Inquiries created via email, phone and web-based forms into a simple easy-to-use multi-user web interface • Easy to use • Organize and archives help request • Light weight • Open Source 2.1.4. Screenshots 5 Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team Figure Nº1: Admin interface Figure Nº 2: Inserting a ticket More screenshots can be found at http://osticket.com/tour/. 2.1.5. Advantages/Disadvantages 2.1.5.1 Advantages • Easy to use • Easy to maintain • Lightweight • Assign tickets to a staff and/or department. 2.1.5.2. Disavantages • Escalation functionality is not directly included, even if it has notifications on overdue (http://osticket.com/forums/showthread.php?t=1975) I didn´t find an automatic re assign ticket feature on overdue tickets. • Following up is not that simple as supposed. Check this other example too: http://www.osticket.com/forums/showthread.php?p=13104. 6 Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team 2.2. OTRS (Open source Ticket Request System) 2.2.1 Summary OTRS is an Open source Ticket Request System with features to manage customer telephone calls and e-mails. The system is built to allow your support, sales, pre-sales, billing, internal IT, helpdesk, etc. department to react quickly to inbound inquiries. Receive 5.000 e-mails a day and still be able to handle them Site: http://otrs.org/index/ Demo page: http://otrs.org/demo/ Source code: http://otrs.org/source/ 2.2.2. Software / Hardware requirements. • GNU • Tested on Linux, Solaris, AIX, FreeBSD, OpenBSD, Mac OS 10.x and Windows. • Mysql • Perl based. 2.2.3. Features • Escalation • Reports and search by different criteria’s • Group’s permissions 2.2.4. Screenshots 7 Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team Figure Nº3: Admin / Agent interface Figure Nº 4: Customer Company tickets. Other screenshots can be found at http://otrs.org/screenshot/. 2.2.5 Advantage/disadvantages 2.2.5.1. Advantages • Easy to use • Widely tested means stability. 2.2.5.2. Disavantages • Depends on Perl knowledge. Still they have a good documentation on that. 8 Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team 2.3. RT – Request Tracker 2.3.1. Summary RT is an open source issue tracking and workflow platform which enables a group of people to intelligently and efficiently manage tasks, issues, and requests submitted by a community of users. It is widely used as an helpdesk system. The RT platform has been under development since 1996, and is used by systems administrators, customer support staffs, IT managers, developers and marketing departments at thousands of sites around the world. Written in obJect-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers. RT manages key tasks such as the identification, prioritization, assignment, resolution and notification required by enterprise-critical applications including proJect management, help desk, NOC ticketing, CRM and software development. RT is used by Fortune 100 companies, government agencies, educational institutions, and development organizations worldwide. Site: http://www.bestpractical.com/index.html Demo Page: Download code: http://download.bestpractical.com/pub/rt/release/rt-3.8.7.tar.gz Signature: http://download.bestpractical.com/pub/rt/release/rt-3.8.7.tar.gz.sig 2.3.2. Software/ Hardware Requirements 2.3.3. Features Track critical data o It's easy to submit, assign, prioritize, search, escalate, and report on issues. o RT keeps track of each ticket's full history and metadata to help your organization better retain knowledge and analyze trends. o RT can track multiple proJects for multiple teams within a single installation. o RT tracks critical system metadata, including time spent per action, due dates, and estimated time to completion. o It's easy to record private comments that are not available to end-users. o RT's web interface comes complete with an intuitive "iterative" search interface that allows end users to construct complex queries by pointing and clicking within their web browsers. o Users can save and edit queries later, using their browser's "bookmarks" feature. • Convenient for end users. For instance, RT provides a simple, self-service interface that allows end users to view their own active and resolved tickets online 9 Engineer Gustavo Ramírez Siles [email protected] IDSCA Support Development Team Easy to customize Security o RT has a built-in access control system that lets administrators grant user, group, and role-based rights to users. o Users can be made members of groups for the purpose of access control. These groups are hierarchical, making it easy for administrators to manage access to the system. o Rights can be granted globally or only to specific parts of your RT system. o Users can be allowed the right to delegate rights that they have been granted. o RT can use your web server's existing authentication system or its own internal password database to grant or deny users' access to RT. Easy to install
Load more

Recommended publications
  • Debian Developer's Reference Version 12.0, Released on 2021-09-01
    Debian Developer’s Reference Release 12.0 Developer’s Reference Team 2021-09-01 CONTENTS 1 Scope of This Document 3 2 Applying to Become a Member5 2.1 Getting started..............................................5 2.2 Debian mentors and sponsors......................................6 2.3 Registering as a Debian member.....................................6 3 Debian Developer's Duties 9 3.1 Package Maintainer's Duties.......................................9 3.1.1 Work towards the next stable release............................9 3.1.2 Maintain packages in stable .................................9 3.1.3 Manage release-critical bugs.................................. 10 3.1.4 Coordination with upstream developers............................ 10 3.2 Administrative Duties.......................................... 10 3.2.1 Maintaining your Debian information............................. 11 3.2.2 Maintaining your public key.................................. 11 3.2.3 Voting.............................................. 11 3.2.4 Going on vacation gracefully.................................. 12 3.2.5 Retiring............................................. 12 3.2.6 Returning after retirement................................... 13 4 Resources for Debian Members 15 4.1 Mailing lists............................................... 15 4.1.1 Basic rules for use....................................... 15 4.1.2 Core development mailing lists................................. 15 4.1.3 Special lists........................................... 16 4.1.4 Requesting new
    [Show full text]
  • Automated IT Service Fault Diagnosis Based on Event Correlation Techniques
    Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Dissertation an der Fakultat¨ fur¨ Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universitat¨ Munchen¨ vorgelegt von Andreas Hanemann Tag der Einreichung: 22. Mai 2007 1. Berichterstatter: Professor Dr. Heinz-Gerd Hegering, Ludwig-Maximilians-Universit¨at M¨unchen 2. Berichterstatterin: Professor Dr. Gabrijela Dreo Rodosek, Universit¨at der Bundeswehr M¨unchen Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Dissertation an der Fakultat¨ fur¨ Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universitat¨ Munchen¨ vorgelegt von Andreas Hanemann Tag der Einreichung: 22. Mai 2007 Tag der m¨undlichen Pr¨ufung: 19. Juli 2007 1. Berichterstatter: Professor Dr. Heinz-Gerd Hegering, Ludwig-Maximilians-Universit¨at M¨unchen 2. Berichterstatterin: Professor Dr. Gabrijela Dreo Rodosek, Universit¨at der Bundeswehr M¨unchen Acknowledgments This thesis has been written as part of my work as a researcher at the Leib- niz Supercomputing Center (Leibniz-Rechenzentrum, LRZ) of the Bavarian Academy of Sciences and Humanities which was funded by the German Re- search Network (DFN-Verein) as well as in cooperation with the research group of Prof. Dr. Heinz-Gerd Hegering. Apart from the LRZ, this research group called MNM-Team (Munich Network Management Team) is located at the University of Munich (LMU), the Munich University of Technology (TUM) and the University of Federal Armed Forces in Munich. At first, I would like to thank my doctoral advisor Prof. Dr. Heinz-Gerd Hegering for his constant support and helpful advice during the whole prepa- ration time of this thesis. I would also like to express my special gratefulness to my second advisor, Prof.
    [Show full text]
  • Github Essentials.Pdf
    [ 1 ] GitHub Essentials Unleash the power of collaborative workflow development using GitHub, one step at a time Achilleas Pipinellis BIRMINGHAM - MUMBAI GitHub Essentials Copyright © 2015 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: September 2015 Production reference: 1280915 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78355-371-6 www.packtpub.com Credits Author Copy Editor Achilleas Pipinellis Trishya Hajare Reviewer Project Coordinator Umesh Ram Sharma Shweta H Birwatkar Commissioning Editor Proofreader Dipika Gaonkar Safis Editng Acquisition Editor Indexer Nikhil Karkal Hemangini Bari Content Development Editor Production Coordinator Sumeet Sawant Nitesh Thakur Technical Editor Cover Work Saurabh Malhotra Nitesh Thakur About the Author Achilleas Pipinellis is an open source enthusiast and tries to get involved in as many projects as possible.
    [Show full text]
  • Ticketing Systems with RT
    Ticketing Systems with RT Network Startup Resource Center www.nsrc.org These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (http://creativecommons.org/licenses/by-nc/4.0/) Typical Support Scenario • Lots of email traffic requesting help, request for services, etc • Archived as text without classification • Very difficult to find current status or problem history • Sometimes problems were forgotten or never resolved • Difficult for another person to follow up on a problem that someone else started dealing with Why Ticketing Systems? Ticketing Systems Why are they important? • Track all events, failures and issues • Focal point for help desk communication Use it to track all communications • Both internal and external Events originating from the outside: • customer complaints Events originating from the inside: • System outages (direct or indirect) • Planned maintenance, upgrades, etc. Ticketing Systems (Contd.) • Use a ticket system to follow cases, including communication between the support staff • Each case is considered a ticket • Each ticket has a ticket number • Each ticket goes through a similar life cycle: • New – Open – … – Resolved Help Request with Tickets Request Tracker / Trac RT • Heavily used worldwide • Can be customized to your location • Somewhat difficult to install and configure • Handles large-scale operations • A hybrid including wiki & project management features • Web-only ticket system works well but not robust as RT • Often used for ”trac”king group projects.
    [Show full text]
  • OTRS Asterisk PBX Integration Module PIM V2.0.0B Administrator's
    OTRS Asterisk PBX Integration Module PIM v2.0.0b Administrator's Guide 2019 © IP-LAB.RU Contents Introduction .................................................................................................................................................. 3 Preparing Asterisk PBX for integration with OTRS ........................................................................................ 4 Install the PIM package on the OTRS server ................................................................................................. 5 Configuring the PIMv2.0.0b module ............................................................................................................. 6 Definition of "Tracking number" ................................................................................................................... 8 Setting agent extensions ............................................................................................................................... 9 Assign agent extensions to the "Tracking Number" ................................................................................... 10 Customer User identification ...................................................................................................................... 11 CallerID modification ................................................................................................................................... 11 Starting the service ....................................................................................................................................
    [Show full text]
  • Onapp Admin Guide
    2.0 Admin Guide 2.0 Admin Guide Contents 0. About This Guide ............................................................................................... 5 1. OnApp Overview ................................................................................................ 6 1.1 Servers ................................................................................................................... 6 1.2 Networks ................................................................................................................ 7 1.3 Templates .............................................................................................................. 8 1.4 Virtual Machines .................................................................................................... 8 1.5 Scalability .............................................................................................................. 8 1.6 Availability and Reliability .................................................................................... 8 1.7 Security .................................................................................................................. 9 1.8 API and Integration ............................................................................................... 9 2. OnApp Hardware & Software Requirements ................................................. 10 2.1 Hypervisor Servers ............................................................................................. 10 2.2 Control Panel Server ..........................................................................................
    [Show full text]
  • Ticketing Systems with RT
    Ticketing Systems with RT Network Startup Resource Center www.nsrc.org These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (http://creativecommons.org/licenses/by-nc/4.0/) Typical Support Scenario • Lots of email traffic requesting help, request for services, etc • Archived as text without classification • Very difficult to find current status or problem history • Sometimes problems were forgotten or never resolved • Difficult for another person to follow up on a problem that someone else started dealing with Why Ticketing Systems? Ticketing Systems Why are they important? • Track all events, failures and issues • Focal point for help desk communication Use it to track all communications • Both internal and external Events originating from the outside: • customer complaints Events originating from the inside: • System outages (direct or indirect) • Planned maintenance, upgrades, etc. Ticketing Systems (Contd.) • Use a ticket system to follow cases, including communication between the support staff • Each case is considered a ticket • Each ticket has a ticket number • Each ticket goes through a similar life cycle: • New – Open – … – Resolved Help Request with Tickets Request Tracker / Trac RT • Heavily used worldwide • Can be customized to your location • Somewhat difficult to install and configure • Handles large-scale operations Request Tracker More Features (Marketing): • Multiple search options: free text (simple) search, query builder, and advanced • Full text search on message histories • Full custom field support for any data you need to track • Charts interface for visualizing ticket data • Custom dashboards with key ticket information • Schedule dashboards to be emailed to you or your co-workers • Knowledge base • Fine-grained rights and permissions • Provides a REST API for integrations • Automatic notifications based on message or other ticket updates • RSS feeds of ticket activity based on any arbitrary search • Email digests of activity by day, week, month, etc.
    [Show full text]
  • Curl Github Pull Request Status
    Curl Github Pull Request Status Xylotomous and whitewashed Gill train his Constance prejudges braids heliotropically. Blood-red and snider Owen prelude her randies equipped or contravene forgetfully. Erastian and laggardly Mugsy outstripped while self-devoted Garcia advocate her psychopomp autobiographically and grudge fourthly. Speed with many times as soon as usual. Options in bitrise, and have curl github pull request status from standard git. For R older than 32 the curl package is required as remotes falls back to. That needs authentication from the command line using curl. Configure Pod Initialization Kubernetes. The smaller order type you can take significant time code coverage badge in de zorg? CURL defaults to displaying the wise it retrieves to the standard output specified on the. Wordpress Docker Github. Github status checks jenkins Children Pool Protection. When you haven't pull commit push over your Git repository for some text you whose face from an error. Accessing GitHub's REST API with CURL Info Support Blog. Welcome to clarify it detect, deploy on market order status request can be fixed documentation. CURL with one possess the most basic tools that allow me send requests to APIs. Bower install jquery macbower error status code of git. Api of github api to apply the curl github pull request status from your repository would be polled frequently use the old resting order to? Web proxy github May 04 2012 An HTTP proxy is similar and why be used for it same. Title for pull and then report for review comments on github, both orders or just described is open a status.
    [Show full text]
  • Estudos Preliminares
    IGOR BESSA MENEZE PODER JUDICIÁRIO S JOSE MARIO VIANA JUSTIÇA DO TRABALHO BARBOSA JUNIOR LENIVIA TRIBUNAL REGIONAL DO TRABALHO DA 7ª REGIÃO DE CASTRO E SILVA MENDES FRANCISC O JONATHAN SECRETARIA DE TECNOLOGIA DA INFORMAÇÃO E COMUNICAÇÃO REBOUCAS MAIA Estudos Preliminares Contratação de Suporte Técnico, incluindo atualizações evolutivas e corretivas, para a ferramenta Atlassian Jira e Plugins eazyBI Reports and Charts e Git Integration. Estudos Preliminares - Contratação de Suporte Técnico, incluindo atualizações evolutivas e corretivas, para a ferramenta Atlassian Jira e Plugins eazyBI Reports and Charts e Git Integration. 1 PODER JUDICIÁRIO JUSTIÇA DO TRABALHO TRIBUNAL REGIONAL DO TRABALHO DA 7ª REGIÃO SECRETARIA DE TECNOLOGIA DA INFORMAÇÃO E COMUNICAÇÃO Sumário ANÁLISE DE VIABILIDADE DA CONTRATAÇÃO (Art.14) 4 Contextualização 4 Definição e Especificação dos Requisitos da Demanda (Art. 14, I) 5 Requisitos de Negócio 5 Requisitos Técnicos 6 Requisitos Temporais 6 Soluções Disponíveis no Mercado de TIC (Art. 14, I, a) 7 Contratações Públicas Similares (Art. 14, I, b) 10 Outras Soluções Disponíveis (Art. 14, II, a) 11 Portal do Software Público Brasileiro (Art. 14, II, b) 11 Alternativa no Mercado de TIC (Art. 14, II, c) 12 Modelo Nacional de Interoperabilidade – MNI (Art. 14, II, d) 12 Infraestrutura de Chaves Públicas Brasileira – ICP-Brasil (Art. 14, II, e) 12 Modelo de Requisitos Moreq-Jus (Art. 14, II, f) 12 Análise Comparativa dos Custos das Soluções (Art. 14, III) 12 Escolha e Justificativa da Solução (Art. 14, IV) 15 Descrição da Solução (Art. 14, IV,a) 21 Alinhamento da Solução (Art. 14, IV, b) 22 Benefícios Esperados (Art. 14, IV, c) 22 Relação entre a Demanda Prevista e a Contratada (Art.
    [Show full text]
  • Install Perl Modules
    How to install OTRS (Open Source Trouble Ticket System) on Ubuntu 16.04 Prerequisites Ubuntu 16.04. Min 2GB of Memory. Root privileges. Step 1 - Install Apache and PostgreSQL In this first step, we will install the Apache web server and PostgreSQL. We will use the latest versions from the Ubuntu repository. Login to your Ubuntu server with SSH: ssh [email protected] Update Ubuntu repository. sudo apt-get update Install Apache2 and a PostgreSQL with the apt: sudo apt-get install -y apache2 libapache2-mod-perl2 postgresql Then make sure that Apache and PostgreSQL are running by checking the server port. netstat -plntu You will see port 80 is used by apache, and port 5432 used by PostgreSQL database. Step 2 - Install Perl Modules OTRS is based on Perl, so we need to install some Perl modules that are required by OTRS. Install perl modules for OTRS with this apt command: sudo apt-get install -y libapache2-mod-perl2 libdbd-pg-perl libnet-dns-perl libnet-ldap-perl libio-socket-ssl-perl libpdf-api2-perl libsoap-lite-perl libgd-text-perl libgd-graph-perl libapache- dbi-perl libarchive-zip-perl libcrypt-eksblowfish-perl libcrypt-ssleay-perl libencode-hanextra- perl libjson-xs-perl libmail-imapclient-perl libtemplate-perl libtemplate-perl libtext-csv-xs-perl libxml-libxml-perl libxml-libxslt-perl libpdf-api2-simple-perl libyaml-libyaml-perl When the installation is finished, we need to activate the Perl module for apache, then restart the apache service. a2enmod perl systemctl restart apache2 Next, check the apache module is loaded with the command below: apachectl -M | sort And you will see perl_module under 'Loaded Modules' section.
    [Show full text]
  • OTRS 3.1 - Admin Manual OTRS 3.1 - Admin Manual Copyright © 2003-2012 OTRS AG
    OTRS 3.1 - Admin Manual OTRS 3.1 - Admin Manual Copyright © 2003-2012 OTRS AG René Bakker, Stefan Bedorf, Michiel Beijen, Shawn Beasley, Hauke Böttcher, Jens Bothe, Udo Bretz, Martin Edenhofer, Carlos Javier García, Martin Gruner, Manuel Hecht, Christopher Kuhn, André Mindermann, Marc Nilius, Elva María Novoa, Henning Oschwald, Martha Elia Pascual, Thomas Raith, Carlos Fernando Rodríguez, Stefan Rother, Burchard Steinbild, Daniel Zamorano. This work is copyrighted by OTRS AG. You may copy it in whole or in part as long as the copies retain this copyright statement. The source code of this document can be found at source.otrs.org [http://source.otrs.org/viewvc.cgi/doc-admin/]. UNIX is a registered trademark of X/Open Company Limited. Linux is a registered trademark of Linus Torvalds. MS-DOS, Windows, Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows 2003, Windows Vista and Windows 7 are registered trademarks of Microsoft Corporation. Other trademarks and registered trademarks are: SUSE and YaST of SUSE Linux GmbH, Red Hat and Fedora are registered trademarks of Red Hat, Inc. Mandrake is a registered trademark of MandrakeSoft, SA. Debian is a registered trademark of Software in the Public Interest, Inc. MySQL and the MySQL Logo are registered trademarks of Oracle Corporation and/or its affiliates. All trade names are used without the guarantee for their free use and are possibly registered trade marks. OTRS AG essentially follows the notations of the manufacturers. Other products mentioned in this manual may be trademarks of the respective manufacturer. Table of Contents Preface .......................................................................................................................... xii 1. Trouble Ticket Systems - The Basics ...........................................................................
    [Show full text]
  • Primera Fase Del Proyecto De Creación De Una Herramienta De Ticketing Web Ibermática Multi-Cliente Y Parametrizable
    Máster en Software Libre Trabajo Final de Máster Creación Plan de Proyecto herramienta de ticketing Análisis Comparativo Autor: Juan A. de Haro / [email protected] Tutor de prácticas: Corinne Dufraisse / [email protected] Responsable técnico Ibermática: Xavier Tejero / [email protected] Creación Plan de Proyecto herramienta de ticketing. Análisis comparativo. Índice de contenidos 1.- Estudio de viabilidad.......................................................................................................................4 1.1 Alcance del proyecto de Creación plan de proyecto herramienta de ticketing .........................4 1.2 Estudio de la situación actual.....................................................................................................5 1.3 Definición de requisitos del sistema..........................................................................................5 1.3.1 Requerimientos..................................................................................................................6 1.3.2 Funcionalidades.................................................................................................................6 1.3.3 Arquitectura........................................................................................................................8 1.3.4 Perfiles de usuarios............................................................................................................9 1.3.5 Información de tareas.......................................................................................................11
    [Show full text]