# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Cherry Blossom

# CherryBlossom -- System Req Spec (CDRL-10)

8 August, 2012

- 1
- 2
…
- 10
- 11
- 12

SECRET//20350112
Cherry Bomb Program Cherry Blossom System Requirements Specification Document
5 (U) Cherry Blossom System Test Requirements
(S) All components of the Cherry Blossom system shall be tested before being deployed. This
section enumerates system test requirements. NOTE: system test procedures are documented in
Cherry Blossom System Test Plan [CDRL 13] and Cherry Blossom System Test Procedures
[CDRL 14]; both shall be updated to reflect the new requirements contained in this document.
5.1 (U) System Testbed
(S) To support all of the necessary testing of the system, a testbed shall be created. The testbed
shall include all of the necessary equipment to simulate all components of the system. The
testbed shall include at least one of each supported Flytrap device, as well as device spares. The
testbed shall be capable of simulating multiple users connected to a Flytrap.
5.2 (U) Automated Software Unit Testing
(U) All classes, libraries, functions, etc. of software developed for the Cherry Blossom system
shall include a comprehensive unit test. A unit test framework shall be used (e.g., Junit for java
software) to automate unit testing by incorporating it into the software build.
5.3 (U) Component Level Software Testing
(U) Each component of the system (Flytrap software modules, TW software, CT software, CT
remote terminal, etc.) shall have a test plan that must be successfully completed before the
software can be deployed. The component level testing shall be as automated as possible,
although this will not be entirely possible as some components of the system involve user input
(e.g., CT remote terminal).
5.4 (U) System Level Testing
(U) A test plan shall be developed for testing all functionality of the testbed Cherry Blossom
system as a whole. Before upgrading the production (operational) system, the testbed system
shall successfully complete the test plan. The testbed system test shall be as automated as
possible, although this will not be entirely possible as some components of the system involve
user input.
(U) Testing shall be performed through multiple PoPs/proxies.
5.5 (U) Production System Testing
(U) A test plan shall be developed for testing all functionality of the production (operational)
Cherry Blossom system as a whole. After upgrading the production system, the system shall
successfully complete the test plan.
SECRET//20350112
12

- 1
- 2
…
- 10
- 11
- 12