This information generally includes the environment of the customer, when and how the issue occurs, and all other relevant circumstances. The technician will also ensure that enough information about the problem is obtained from the customer. (2) The technician verifies that the problem is real, and not just perceived. Some applications provide built-in messaging system and automatic error reporting from exception handling blocks. (1) A customer service technician receives a telephone call, email, or other communication from a customer about a problem. "An example scenario is presented to demonstrate how a common issue tracking system would work:
#Sequence diagram online banking system visio pro
This example of bank ATM sequence diagram was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park. In the example, the Bank timeline has an X simply as an example (presumably the Bank does continue to exist)." An X on a timeline indicates that the component ceases to exist in some sense (unsure precisely how this is meant also). The narrow rectangles apparently show when a component is active (unsure precisely what "active" means). The timelines are dotted rather than solid, and the name of the component is inside a box at the head of each timeline. Presumably the same semantic issues arise, but possibly not since UML semantics are not well-defined. "A UML sequence diagram or SD is similar to an MSC but written with a different notation. This example of automated teller machine (ATM) UML sequence diagram was created on the base of figure 5 "Sequence diagram" on the webpage "Message Sequence Charts and their Ilk" from the website of the University of California Irvine (UCI) Donald Bren School of Information and Computer Sciences.