Single Window Systems
In the OIC Member States
23
strategies. The user and functional requirements of the Single Window are commonly defined
using a Business process analysis (BPA).
The BPA includes an inventory of the laws and regulations and administrative decisions
covering the current state of formalities, and leads to the mapping of the AS-IS business
processes and their legal and regulatory requirements. The BPA is than taken one step further
to business process simplification and re-engineering through which the TO-BE business
processes of the future SW system are defined. This leads to the drafting of IT Functional
Requirements
15
and specifications, and IT technical requirements
16
and specifications.
The functional requirements and specifications are always developed in-house. If the IT
development is outsourced, the vendor may develop the technical requirements and
specifications. In this case, the vendor also revises the user and functional requirements and
proposes the technical specifications and requirements.
At this stage, the project management team should determine the project cost estimation,
meaning the detailed allocation of project funds to specific components and activities.
Required legal and regulatory changes also need to be identified and planned.
Development and Deployment
The development and deployment phase entails the sourcing of infrastructure, the
development, production, and test
17
of the IT system, and the training of staff and users.
Individual developers or development teams produce the outputs of the development phase,
according to the Project Implementation Plan and the Quality Assurance plan. Different
elements of this phase may be outsourced to a third party, but the Single Window project team
ensures overall coordination, oversight and quality assurance. Usually the infrastructure
components and services are outsourced separately; i.e. if the development of the IT system is
outsourced, the vendor is responsible for the IT project development.
The development of the system evolves in different releases. Each release is an intermediate
stage, which are tested and updated, and ultimately lead to the production
18
of the overall
system.
15
The IT functional requirements define specific functionalities of the SW system.
16
The IT technical requirements refer to the technical aspects of the system, such as performance-related issues, reliability
issues, and availability issues. These types of requirements are often called quality of service (QoS) requirements, service-
level requirements or non-functional requirements
(http://agilemodeling.com/artifacts/technicalRequirement.htm)17
Testing is a physical (meaning hardware) and a logical setup (operating system, database, tested application and services,
running environment, browser, etc.) of the environment used to perform the testing of the SW software application.
Depending on the testing phases that are performed, more than one SW environment could be foreseen. The testing
environment should be able to measure and test the capacity such as availability and performance SW requirements.
18
Production is the deployment environment where the software applications go live and become accessible by the business
or other users, and interface with other production back-end systems




