Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DSDP/MTJ/Configure Obfuscation
Use-Case Specification: Configure Obfuscator
1. Use Case Description
2. Basic Flow
- B1: User chooses to create a new Obfuscation Configuration from Obfuscation preferences page.
- B2: User fills in these attributes:
- Obfuscator location path
- Additional obfuscator parameters
- Unique configuration name
- B3: User confirms the configuration creation.
- B4: The configuration is stored in the system.
- B5: Steps B1-B3 can be repeated as many times as needed.
3. Alternate Flows
- Alternative Flow 1: Edit existing obfuscation configuration
- A1: User selects Obfuscation Configuration from the list on Obfuscation preferences page.
- A2: System shows configuration attributes.
- A3: User changes configuration attributes.
- A4: User save changed Obfuscation configuration.
- A5: System saves new configuration data.
- A6: Steps A1-A4 can be repeated as many times as needed.
- Alternative Flow 2: Remove existing obfuscation configuration
- A1: User selects an Obfuscation configuration from the obfuscation preferences page.
- A2: System shows configuration attributes.
- A3: User chooses to delete selected configuration.
- A4: System removes selected configuration.
- A5: Steps A1-A3 can be repeated as many times as needed.
4. Preconditions
4.1 Preconditions for basic flow 1
User has installed at least one Obfuscator.
Given name of obfuscation configuration is never used.
4.2 Preconditions for alternative flow 1
User has saved at least one the obfuscation configuration.
4.3 Preconditions for alternative flow 2
User has saved at least one the obfuscation configuration.
5. Postconditions
5.1 Post Conditions for basic flow 3
The new Obfuscation configuration is stored in the system and it’s ready to use.
5.2 Post Conditions for alternative flow 1
The changes in the editing Obfuscation configuration are stored in the system and it’s ready to use.
5.3 Post Conditions for alternative flow 2
Selected configuration is removed from the system. Projects which was this configuration assigned are now set up without the obfuscation task in the build process.
6. Extension Points
7. Special Requirements
8. Additional Information
Comments:
Back to main DSDP-MTJ Use Cases