Single Window Systems
In the OIC Member States
22
Functional Requirements
18
and specifications, and IT technical requirements
19
and
specifications.
The functional requirements and specifications are always developed in-house, but the technical
requirements and specifications may be developed by the vendor, if the IT development is
outsourced. In case of outsourcing, the vendor 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. Necessary
legal and regulatory changes also need to be identified and planned.
Development and Deployment
The development and deployment phase entails sourcing of infrastructure, development,
production, and test
20
and training. The outputs of the development phase are produced by
individual developers r development teams, which execute the Project Implementation Plan and
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
21
of the overall
system.
Post implementation: Closure of the Project
The deployment of the Single Window closes with the acceptance activities that include internal
and external testing, validation process, and conformance testing. Conformance testing provides
for last-minute corrections (minor bug fixes) of the Single Window. The findings of these
activities are entered in the Final Acceptance document. A large number of documents and
specifications, such as the source code design, or the internal user’s manual are finalised and
handed over to the Single Window operator.
18
The IT functional requirements define specific functionalities of the SW system.
19
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)20
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 SWsoftware 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.
21
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