Capturing Documents Service System Use Cases

Assumption

l Capturing document module runs as a windows service. All the references come from the configuration file.

l Capturing Document Service is used by Receipt manager and QwikSign.

l Capturing Document Service works with the core system (a third-part application). The core system includes the workstations and the core server. Capturing Document Service runs on the workstations or a separate computer.

l The veryPDF (a third-part application) is used to generate a PDF document from PCL or PostScript now. Other converters may be used in this service in future.

Process

The chart below introduced how the Printer Capturing Service works:

Figure 1

Use Cases

Use Case 1. Set the configuration of service

Context of Use: Administrator needs to modify the configuration file of Capturing Document Service

Primary Actor: Administrator

Level: User

Precondition:

Trigger:

Minimal Guarantee: Nothing in the system is changed

Success Guarantee: The configuration file is modified and saved.

Main Success Scenario:

1. Primary actor opens the configuration file using Notepad or other applications, and inputs the information below:

² The ports which Capturing Document Service listens on. (e.g. 9100, 515.) The system has ability to support multiple ports.

² Two distinct folders: one is for QwikSign, and anther is for Receipt Manager.

² PCL->PDF converter.

² PS->PDF converter.

2. Primary actor saves the modification, and restarts the Capturing Document Service to load the new configuration.

Extensions:

Use Case 2. Logs

Logs should be written into a txt file. It’s same to ERM’s.

Use Case 3. Print capture

Context of Use: The print stream should be captured and converted into a document.

Primary Actor: Core server

Level: User

Precondition: Capturing Document Service is installed on the workstation.

Trigger:

Minimal Guarantee: Nothing in the system is changed

Success Guarantee: A PDF or TXT file is generated.

Main Success Scenario:

1. Capturing Document Service runs on a workstation, and listens on the ports of this workstation.

3. The print stream is received and identified.

4. If the stream is PS or PCL, a converter (e.g. veryPDF) is called to generate a PDF file.

5. This PDF file is put into a predefined folder.

Extensions:

6a. If the capture stream isn’t PS or PCL, it’s converted to a txt file and saved to the Receipt Manager folder.

Use Case 4. Print capture over port 9100 in a separate computer

Context of Use: The print stream should be captured and converted into a document.

Primary Actor: Core server

Level: User

Precondition: Capturing Document Service is installed on a separate with multiple IP addresses. In the core system each workstation is set to print to a different IP address.

Trigger:

Minimal Guarantee: Nothing in the system is changed.

Success Guarantee: A file is generated.

Main Success Scenario:

1. Capturing Document Service runs on a separate computer, and runs as a terminal service. A session of Capturing Document Service listens on the port 9100 of an IP address.

2. A workstation sends a print request to the core server. The core server prints to a predefined IP address of the computer over port 9100.

3. The print stream is received and identified.

4. If the stream is PS or PCL, a converter (e.g. veryPDF) is called to generate a PDF file.

5. This PDF file is put into a predefined folder.

Extensions:

6a. If the capture stream isn’t PS or PCL, it’s converted to a txt file and saved to the Receipt Manager folder.

Use Case 5. Print capture over port 515 in a separate computer

Context of Use: The print stream should be captured and converted into a document.

Primary Actor: Core server

Level: User

Precondition: Capturing Document Service is installed on a separate computer.

Trigger:

Minimal Guarantee: Nothing in the system is changed.

Success Guarantee: A file is generated.

Main Success Scenario:

1. Capturing Document Service runs on a separate computer and listens on the port 515.

2. A workstation sends a print request to the core server. The core server prints to this computer over port 515.

3. The print stream is received and identified.

4. If the stream is PS or PCL, a converter (e.g. veryPDF) is called to generate a PDF file.

5. This PDF file is put into a predefined folder.

Extensions:

6a. If the capture stream isn’t PS or PCL, it’s converted to a txt file and saved to the Receipt Manager folder.