Processes supporting the use cases Sample Clauses

Processes supporting the use cases. In this section we are going to describe the processes that take place in the Arrow system in order to perform all the necessary elaborations requested for the accomplishment of the functionalities requested in the use cases described earlier in this document. We are going to describe these processes (the communication sequence between actors and system components) using the UML sequence diagrams. Being that many of the use cases described earlier, are not independent from each other, each sequence diagram that we are going to present, may include more then one Use Case. The Arrow processes are in many cases asynchronous, that means that some of them are activated upon some particular action (Library validation, external provider asynchronous answer). The order in which the Sequence diagrams will be presented, take in consideration even this asynchronous behaviour. Sequence Diagram: Initial upload request Figure 8: The execution of initial upload request This diagram shows how the Librarian interacts with both the Arrow Frontend and the Arrow DataCentre in order to upload a request in the Arrow System. It comprises the following use cases: • UC1 - Send Requests (Librarian-Frontend) • UC8 - Upload Request (Frontend - DataCentre) The librarian can send requests either by uploading a MARC21 XML file or filling the Query Form. In case the Librarian uploads a request file containing a list of MARC21 Xml records, the Frontend checks first of all that the submitted file is valid against the MARC 21 XML schema and then for each of the records checks all the mandatory fields that must be present in order to be able to perform the arrow necessary elaboration. Upon validation completion Frontend splits the file according to the number of the MARC records it includes, and for each of these records builds a M1Q request. M1Q is build according to the message specification provided by EDItEUR for the communication between Library-Frontend (see deliverable 4.3). After the M1Q construction, Frontend invokes the web service (DataCentre: Webservice Frontend) that the Arrow DataCentre exposes in order to enable the uploading of such requests into the Arrow System. This web service validates the incoming M1Q message, enqueues it in the Arrow queue (the elaboration of the enqueued message will be explained in “Tel matching” sequence diagram) and soon after builds a M1R response that is returned to FrontEnd (according to the message specification provided by EDItEUR). Upon corre...
Sample 1
AutoNDA by SimpleDocs
Processes supporting the use cases. This section elaborates on how processes that support the use cases are handled by the TEL system. The diagrams in this section follow the notation of sequence diagrams11 of UML.
Sample 1

Related to Processes supporting the use cases

  • Paid Claims without Supporting Documentation Any Paid Claim for which Practitioner cannot produce documentation shall be considered an error and the total reimbursement received by Practitioner for such Paid Claim shall be deemed an Overpayment. Replacement sampling for Paid Claims with missing documentation is not permitted.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Supporting Documentation Upon request, the HSP will provide the LHIN with proof of the matters referred to in this Article.

  • Supporting Proof Upon the request of the Province, the Recipient will provide the Province with proof of the matters referred to in Article A2.0.

  • Supported Use Cases Subscription Services are provided for Red Hat Satellite Server, Red Hat Satellite Capsule and Red Hat Satellite Proxy Management Subscriptions only when used for their supported purposes (“Use Case”) in accordance with the terms of this Exhibit and Table 2 below.

  • Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.

  • Jointly Provided Switched Access Services 7.5.1 Jointly Provided Switched Access Service is described and governed by the FCC and state access Tariffs, Multiple Exchange Carrier Access Billing (MECAB) and Multiple Exchange Carrier Ordering and Design (MECOD) Guidelines and based on LERG routing, and is not modified by any provisions of this Agreement. Both Parties agree to comply with such guidelines. CenturyLink and CLEC agree that the originating, intermediate, and terminating LECs for switched access will cooperatively determine the Jointly Provided Switched Access arrangements in which all parties concur.

  • Procurement of Recovered Materials (1) In the performance of this contract, the Contractor shall make maximum use of products containing recovered materials that are EPA-designated items unless the product cannot be acquired

  • Internet Access to Contract and Pricing Information Access by Authorized Users to Contract terms and pricing information shall be made available and publically posted on the OGS website. To that end, OGS shall publically post the Contract Pricelist, including all subsequent changes in the Contract offerings (adds, deletes, price revisions), Contractor contact information, and the Contract terms and conditions, throughout the Contract term.

  • Initiation of TIPS Sales When a public entity initiates a purchase with Vendor, if the Member inquires verbally or in writing whether Vendor holds a TIPS Contract, it is the duty of the Vendor to verify whether the Member is seeking a TIPS purchase. Once verified, Vendor must include the TIPS Contract Number on all purchase communications and sales documents exchanged with the TIPS Member.

Time is Money Join Law Insider Premium to draft better contracts faster.