/ EUROPEAN COMMISSION
DIRECTORATE-GENERAL
INFORMATICS
Information systems Directorate

European Commission

e-PRIOR Use Case Specification: View Request

Date: / 7/15/2009
Version: / 0.002
Authors: / João Rodrigues Frade
Revised by: / Technical Review:
Quality Review:
Maarten Daniels
Approved by:
Public:
Reference Number:

TABLE OF CONTENTS

1. Use-Case Description

1.1. Functional Features List......

2. Flow of Events

2.1. Basic Flow

2.1.1. User submits message......

2.1.2. System checks conformance to the message schema rules......

2.1.3. System queries the message repository......

2.1.4. System builds the View Request Response......

2.2. SubFlows

2.3. Alternative Flows

2.3.1. A1: At step 2.1.4 "System builds the View Request Response" no document matches the query criteria

2.4. Exceptional Flows

2.4.1. E1: At step 2.1.1 "User submits message" the system is down......

2.4.2. E2: At step 2.1.4 "System builds the View Request Response" there is a technical error reported regarding the connection with the supplier

2.4.3. E3: At step 2.1.2 "System checks conformance to the message schema rules" XSD constraints are broken

3. Special Requirements

3.1. Interface(s) with other Systems

3.2. SecurityRequirements

3.3. Other Non Functional Features

4. Preconditions

5. Postconditions

5.1. Postcondition One

6. Additional Information

Document History

Version / Date / Comment / Modified Pages
0.001 / 01/07/2008 / Creation / All
0.002 / 15/07/2009 / Update of flow E1 and E3 / As required

e-PRIOR Use Case Specification: View RequestPage 1

1.Use-Case Description

The system supports the presentation of documents in HTML format following a request by the Backend application.

1.1.Functional Features List

Phase: Phase 1

Cross-Functional Presentation of Business Documents

2.Flow of Events

2.1.Basic Flow

In the context of this Use Case, User should be understood as a Back-Office system.

2.1.1.User submits message

  • This Use Case starts when the User submits a message to the View Request service end-point. This opens an https connection between the User and the system
  • Include Use Case “User Access” to authenticate and authorize access to the User

Note: The request message contains the request to view a single business document.

2.1.2.System checks conformance to the message schema rules

  • The system validates the message against the View Request XML Schema Design rules (i.e. data types, mandatory/ optional data elements and attributes, data elements multiplicity)

2.1.3.System queries the message repository

  • The essential parameters of the View Request request:
  • The Document Type (parameter found in the message)
  • The Document ID (parameter found in the message)

The system queries for documents:

of a specific Document Type (e.g. Invoice) and

a specific Document ID

Note: The request message XML Schema Design may contain additional information, such as the document Issue Date - this is not a problem - however this additional information will not be used by the system.

2.1.4.System builds the View Request Response

  • Based on the result of the previously mentioned query, the system builds the View Request Response. When a single document matches the previously mentioned criteria, the business document is returned in HTML format in the response

2.2.SubFlows

  • Not identified.

2.3.Alternative Flows

2.3.1.A1: At step 2.1.4 "System builds the View Request Response" no document matches the query criteria

  • No document is found in the message repository matching the previously mentioned criteria. When no document matches the previously mentioned criteria, the following information is returned on the status response:
  • A note stating that "No matches were found"
  • System responds with a Status Response to the Request
  • This closes the https connection between the User and the system
  • The Use Case Ends

2.4.Exceptional Flows

2.4.1.E1: At step 2.1.1 "User submits message" the system is down

  • The User receives a 503 Service Unavailable
  • The Use Case Ends

2.4.2.E2: At step 2.1.4 "System builds the View Request Response" there is a technical error reported regarding the connection with the supplier

  • The system detects when a supplier closes its connection. In this case the system cannot respond to the subsequent request
  • The Use Case Ends

2.4.3.E3: At step 2.1.2 "System checks conformance to the message schema rules" XSD constraints are broken

  • When broken XSD constraints are reported (1 or more), the following information is returned:
  • System submits a SOAP Fault [6]
  • This closes the https connection between the User and the system
  • The Use Case Ends
  • The Use Case Ends

3.Special Requirements

3.1.Interface(s) with other Systems

  • Backend system

3.2.SecurityRequirements

The reader should refer to chapter 1.1Functional Features List of subtype "Security"

3.3.Other Non Functional Features

4.Preconditions

There are currently no preconditions defined.

5.Postconditions

5.1.Postcondition One

Following the basic flow the system responds with a View Request Response.

6.Additional Information

None.

e-PRIOR Use Case Specification: View RequestPage 1 / 3