Customs Declaration Processing System Detailed User and ...

DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS
AND USE-CASE MODELS
Ref: PHASE V
Number
Description
available via email.
If the achieved response times from the Help desk are higher than the maximum
allowed response times, then the monthly fee paid for the Help Desk will be
reduced accordingly.
Table 26: Outsourcing of application hosting requirements.
6. PHASING/MILESTONES FOR THE CDPS PROJECT
6.2 Introduction of the stages
6.2.1 Phase plan
The project lifecycle consists of the phases described in the following table.
Phase name Number of iterations Duration
Inception 1 20 days
Elaboration 2 160 days
Construction 5 260 days
Transition 2 60 days
Details are can be obtained from Annex 2 of this document (see Chapter 8).
6.2.2 Phase objectives
The table bellow explains every phase.
Phase name
Inception
Elaboration
Description
The inception phase is of significance primarily for new
development efforts, in which there are significant business
and requirements risks which must be addressed before the
project can proceed. For projects focused on enhancements to
an existing system, the inception phase is more brief, but is
still focused on ensuring that the project is both worth doing
and possible to do. This phase is more oriented to the product
provider because MCA already decided to replace the existing
Asycuda system with a new one. During the phase the product
provider will estimate the risk, calculate its benefits, define
project scope and objectives and a final decision will be made
for participating in the project. The functional boundaries of
the system are ready and will be provide to the product
provider.
During this phase the User and Technical Requirements, Usecase
Model, and Software Architecture documents provided
by “Technical Assistance for Drafting Technical and User
Requirement for the Customs Administration” project will be
further elaborated. Every single detail of the system will be
defined and the system’s Functional Specification will be
prepared based upon the User Requirements document. The
database model and source code design model will be
Page 164/276