1 / 1

Developing High-Quality Components in CrypTool 2.0: From Initial to Release Phase

In the development lifecycle of CrypTool 2.0, three key phases—Initial, Experimental, and Release—guide the creation and integration of components. During the Initial Phase, developers focus on establishing core functionality within the CrypPluginsExperimental directory. The Experimental Phase emphasizes achieving the highest quality standards, where components undergo rigorous testing, ensuring no compiling errors disrupt the Nightly Build. Finally, the Release Phase solidifies the components for public use. Developers must collaborate effectively, focusing on bug fixes and user support.

erik
Télécharger la présentation

Developing High-Quality Components in CrypTool 2.0: From Initial to Release Phase

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 1. Initial Phase 2. Experimental Phase 3. Release Phase Your components are in: CrypPluginsExperimental Your components are in: CrypPluginsExperimental Your components are in: CrypPlugins Your templates are in: Templates/Experimental Your templates are in: Templates/Experimental Your templates are in: Templates/*(where they belong) You do not! Check in the Public Solution („CrypTool 2.0.sln“-file) A core developer (or you by permission) put your components into the „Public Solution“ („CrypTool 2.0.sln“-file) A core developer (or you by permission) moved your components and templates out of the experimental folders You do not have (but should) care about compilung errors and missing files You have to care about compiling errors and missing files A core developer put your components and templates into the „Nightly Build“ („Core Solution“) In this phase you develop the main functionality of your Cryptool 2.0 components. You already develop tests, the first strcuture of the online help, and first templates. In this phase your components and templates should reach the „best level of quality“. You test intensively and fix all bugs you find. In this phase, your components „are visible“ to all other developers. Compiling errors affect other developers. You developed the online help and (if possibile and feasible) an unit test. In this phase your components and templates should have the „best level of quality“. You tested intensively and fixed all bugs you found. In this phase, your components „are visible“ to all Cryptool 2.0 „Nightly Build“ users. Compiling errors affect other developers and crash the „Nightly Build“. Runtime errors affect users.

More Related