Customs Declaration Processing System Detailed User and ...

DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS
AND USE-CASE MODELS
Ref: PHASE V
Number Description
generation of reports on historical data. If required for performance reasons, then
older data shall be periodically purged from TPS. For querying and reporting,
this purged data and the current data shall be stored in the data warehouse where
the requirements for the response time are much more relaxed.
DW-0070 For security reasons, DWS shall prevent users who only need to execute queries
and generate reports from having any access to the TPS in CDPS.
DW-0080 Ad-hoc reporting: CDPS must address the functionality for reporting, based on
selection of one or many fields found on any of the User Interfaces and must
include options for on-line and off-line generation of reports. This functionality
must be supported through the use of a versatile Report Writer that can be used
by a non-technical user.
DW-0090 CDPS shall also provide a number of predefined frequently used reports in the
customs domain.
DW-0100 CDPS shall provide the ability to maintain a library of user-defined on-line
(screen-based) and batch-printed reports with pre-stored selection parameters
that can be run without change, and/or modified as required when running a
report.
DW-0110 Reports will be available in a variety of formats: Portable Data Format (PDF),
Postscript (PS), MS Word, and MS Excel at the very least.
DW-0120 If CDPS allows a user to perform a query and view the results, then CDPS will
also allow the user to generate a report from the results, and to download the
result or the report.
DW-0130 Reports General: CDPS should have the ability to report on all data entered into
the system and should be highly flexible and user-friendly with the capacity to
restrict access to reports according to user permissions
DW-0140 Use Reports: CDPS should have the ability to display report output on the screen
along with a view of a summary. CDPS should have ability to enter parameter/s
to filter reports on one or more fields/columns together with the capability to sort
reports on one or more fields/columns.
Table 13: Data Warehouse requirements
5.2.8 Technical Architecture
CDPS must address the MCA’s requirement for an n-tier web-enabled application architecture.
With an n-tier architecture, the MCA will have the flexibility it needs to deploy its IT infrastructure
and human resources more optimally and overcome the limitations of the Client-Server
architecture. Through streamlining and consolidating its operations at the central site, the MCA IT
Department will increase its capacity to provide better service to its internal and external clientbase.
CDPS must, therefore, address and meet the following requirements regarding its technical
architecture.
Number Description
TA-0010 SOA. CDPS must be based on a Service- Oriented Architecture (SOA) to lay the
foundation for the building of a robust, extensible, reusable components-based
application architecture that is easy to maintain and support.
TA-0020 n-tier web enabled application. CDPS must be a web enabled n-tier based
application system. CDPS must be highly scalable.
TA-0030 Separation of data logic from process logic. CDPS must address the
requirement of separation of data and process logic to ensure reuse of
components and consistent application of business rules across processes in
Page 145/276