Customs Declaration Processing System Detailed User and ...

DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS
AND USE-CASE MODELS
Ref: PHASE V
- Where information is exchanged electronically, the Accounting management system sub-application will
send via the Guarantee management sub-application a response message to the trader indicating that
duties cannot be deferred due to insufficient credit. The trader would normally be able to submit a
request for information concerning the deferred account balance or a statement of the account.
- When the duty becomes payable, the total amounts owed by each approved trader together with their
bank account details (account number, branch sort code, etc.) should be transferred to the relevant bank.
The question of agreement between Macedonian customs authorities and the banks on the information
exchange standard and the medium (EDI, Internet, etc.) will need to be addressed. International standard
messages designed for use in the EDI environment are available for the transmission of payment
information.
5. TECHNICAL REQUIREMENTS
5.1 Introduction of concept and architecture
The logical architecture of CDPS is with multiple tiers. It requires no client installation thus
reducing the total cost of ownership. Such architecture works in various application scenarios and
deployment patterns. Consequently, the same CDPS application can be deployed in different
environments such as production, testing, training and conformance testing environments. We
recommend the use of a Centralised data repository. Recommended multi-tier logical architecture
offers the following benefits: Logically organized code; Easier maintenance; Better reuse of code;
Better team development experience; Higher clarity in coding; Manageability and maintainability;
Works in various application scenarios and deployment patterns; Decoupled Presentation and
Business Logic facilitating scalability; Separate interface and business logic components allowing
manageable and maintainable interfaces with external entities; The business logic in the Business
Tier can be wrapped in a number of web services and thus made available to external clients;
Addresses security considerations from the start and in-depth.
More details on the proposed technical architecture can be found in the document “Customs Declaration
Processing System: Functional and Technical Architecture”.
Requirements related to the Common Domain are of lower priority compared to the requirements related to
the National and External Domain. Implementation of the Common Domain requirements can be postponed
until prior to the accession of Macedonia to EU.
5.2 General Technical Requirements
This section provides an overview of the general technical requirements that have to be met by
every software application which is part of CDPS.
5.2.1 Networking Requirements
This chapter provides the networking requirements for the CDPS whether it is developed,
customised or a combination of both.
Number Description
NR-0000 The communication network(s) has to be sized by MCA and CDPS vendor to
ensure the communication between HQ and BCOs and to meet the national
performance requirements.
NR-0001 The connection between the External Domain and the CDPS is recommended to
be a direct connection (e.g. through direct line), or to use strong encryption and
authentication mechanism e.g. VPN through IPSec.
Page 134/276