"An example scenario is presented to demonstrate how a common issue tracking system would work:
(1) A customer service technician receives a telephone call, email, or other communication from a customer about a problem. Some applications provide built-in messaging system and automatic error reporting from exception handling blocks.
(2) The technician verifies that the problem is real, and not just perceived. The technician will also ensure that enough information about the problem is obtained from the customer. This information generally includes the environment of the customer, when and how the issue occurs, and all other relevant circumstances.
(3) The technician creates the issue in the system, entering all relevant data, as provided by the customer.
(4) As work is done on that issue, the system is updated with new data by the technician. Any attempt at fixing the problem should be noted in the issue system. Ticket status most likely will be changed from open to pending.
(5) After the issue has been fully addressed, it is marked as resolved in the issue tracking system.
If the problem is not fully resolved, the ticket will be reopened once the technician receives new information from the customer. A Run Book Automation process that implements best practices for these workflows and increases IT personnel effectiveness is becoming very common." [Issue tracking system. Wikipedia]
The UML sequence diagram example "Ticket processing system" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
(1) A customer service technician receives a telephone call, email, or other communication from a customer about a problem. Some applications provide built-in messaging system and automatic error reporting from exception handling blocks.
(2) The technician verifies that the problem is real, and not just perceived. The technician will also ensure that enough information about the problem is obtained from the customer. This information generally includes the environment of the customer, when and how the issue occurs, and all other relevant circumstances.
(3) The technician creates the issue in the system, entering all relevant data, as provided by the customer.
(4) As work is done on that issue, the system is updated with new data by the technician. Any attempt at fixing the problem should be noted in the issue system. Ticket status most likely will be changed from open to pending.
(5) After the issue has been fully addressed, it is marked as resolved in the issue tracking system.
If the problem is not fully resolved, the ticket will be reopened once the technician receives new information from the customer. A Run Book Automation process that implements best practices for these workflows and increases IT personnel effectiveness is becoming very common." [Issue tracking system. Wikipedia]
The UML sequence diagram example "Ticket processing system" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
Process Flowchart
ConceptDraw is Professional business process mapping software for making process flow diagram, workflow diagram, general flowcharts and technical illustrations for business documents. It is includes rich examples, templates, process flowchart symbols. ConceptDraw flowchart maker allows you to easier create a process flowchart. Use a variety of drawing tools, smart connectors, flowchart symbols and shape libraries to create flowcharts of complex processes, process flow diagrams, procedures and information exchange.- UML sequence diagram - Ticket processing system | UML sequence ...
- UML Sequence Diagram Example. SVG Vectored UML Diagrams ...
- Trouble ticket system - BPMN 2.0 diagram | UML use case diagram ...
- Activity Network Diagram Method | Trouble ticket system - BPMN 2.0 ...
- Design elements - UML use case diagrams | UML Sequence ...
- Process Flowchart | Credit Card Processing System UML Diagram ...
- Uml Diagrams Of Image Processing
- UML Activity Diagram
- BPMN 2.0 | Logistics - Choreography BPMN 2.0 diagram | Trouble ...
- Credit Card Processing System UML Diagram | UML in 10 mins ...
- How to Create a BPMN Diagram Using ConceptDraw PRO | Cab ...
- UML Tool & UML Diagram Examples | UML Component Diagram ...
- Diagramming Software for Design UML Collaboration Diagrams ...
- UML Component Diagram Example - Online Shopping ...
- UML Component Diagram | Diagramming Software for Design UML ...
- UML component diagram - Credit card agency | Rapid UML | Rapid ...
- UML Diagrams with ConceptDraw PRO | UML Diagram | Software ...
- UML Component Diagram Example - Online Shopping | UML ...
- Credit Card Processing System UML Diagram | UML in 10 mins ...
- UML activity diagram - Cash withdrawal from ATM | UML Activity ...
- ERD | Entity Relationship Diagrams, ERD Software for Mac and Win
- Flowchart | Basic Flowchart Symbols and Meaning
- Flowchart | Flowchart Design - Symbols, Shapes, Stencils and Icons
- Flowchart | Flow Chart Symbols
- Electrical | Electrical Drawing - Wiring and Circuits Schematics
- Flowchart | Common Flowchart Symbols
- Flowchart | Common Flowchart Symbols