Specification Requirements T2S GUI. 08 th December 2011 ECB - 4CB

Transcription

1 08 th December 2011 ECB - 4CB

2 1. Technical Description Architecture/Infrastructure Web-based GUI supported by browsers and versions Other software requirements and related versions /N Not clear Standard browser Java/Java-Script latest version Export functionalities Supported by MS Excel (CSV) Print functionalities Print-friendly layout Versioning concept / Rollout Procedure N Web-Based GUI in the T2 SSP- Environment: no dedicated procedure Access via Internet via NSP (VAN) and direct lines Secured sites (https) List of IP ports to be opened Not clear Definition Network Provider HTTPS will be used for communication between Web- Browser and T2S-Webserver 2 Standard: HTTPS Port 443, HTTP Port 80

3 1. Technical Description Data Model /N Reference to related database attribute UHB Display information; definition of data format to be displayed on field level Options to customize display of data field or layout of GUI N UHB Data field (default) values and descriptions UHB Display/resolution aspects including a concept what should happen if e.g. in one column values with different decimals to be displayed Help functionality Not foreseen At minimum 1024x768 3

4 2. Functional Aspects /N Navigation concept UHB Search function concept Flow diagram (analogue the BPD) for creation, modification and delete Describe display only, mandatory field and optional field within the different screens parts and subsequent child windows Display of context sensitive information, e.g. when selecting an account number or a BIC code the entity to whom the account, BIC, etc. belongs should be displayed Description of the layout and the according field specifications 4-Eyes principle vw. 2-Eyes-Principle (verification of the data entry) N N Already explained in former UHB UHB possibly Styleguide Already explained in former 4

5 Fulfilment of DIN-EN-ISO 9241 Norm for the GUI like ergonomic aspects 2. Functional Aspects /N Data base attributes/data base type UHB Error and help function (serial or final display) UHB Error message list UHB Copy functions or options to setup favourites to ease work/setup Definition when validations of data entry take place in the GUI Definitions of back-end validations for functionalities which exist only U2A (in the GUI) Audit Panel/concept (user-id, action, timestamp) statistics on user level N One-click functionality Conceptual view of development Conceptual view of development Already explained in former 5

6 3. User Administration Authorisation Concept (group concept vs. single setup, access rights, roles and list of U2A privileges, etc.) Profiles Login procedure (user name and password or token requirements) Cycles for new password Password conventions etc. User settings (language German / English, display of date, time etc.) /N N N Already explained in former Already explained in former Depends on Third Party Software that is evaluated at present. Only English, T2S time 6

7 4. Performance Aspects In line with the URD and service level agreements (SLA) agreed during the negotiations for A2A messages it is proposed to support a GUI performance rate of 95% < 3sec. /N N Not usability SLA Performance reporting approach N Not usability SLA 7

8 5. Legal Aspects /N Declaration of any open source elements No declaration necessary Additional licenses requirements, if needed Not necessary Usage Agreement (object of agreement, delivery, scope of the right of use etc.) N should be in the contract T2S- CSD (eg that PC used to connect to T2S must be protected against virus attack, against open access etc.) 8

9 6. Pricing /N Reporting costs N Not usability Query costs N Not usability Inquiry costs N Not usability Charging modalities N Not usability Statistics per user per CSD N Not usability In general: examples of pricing for GUI pricing elements can be found in Schedule 7 of the Framework Agreement 9