!!! Core Applications

! [d3web-Core|d3web-Core]
The reasoning engine and persistence components for problem-solving knowledge including decision trees, (heuristic) rules, set-covering models and diagnostic flowcharts ([LGPL|http://www.gnu.de/documents/lgpl.de.html] with commercial extensions).\\
[more...|d3web-Core]


! [KnowWE] (Knowledge Wiki Environment)

As the successor of KnowME the system KnowWE (Knowledge Wiki Environment) offeres a web-based wiki front-end for the knowledge acquisition and supports the collaborative engineering of knowledge at different formalization levels ([LGPL|http://www.gnu.de/documents/lgpl.de.html] with commercial extensions). \\
[more...|KnowWE]

! Dialog Applications

* __ProKEt__: Prototyping of knowledge-based dialog systems ([LGPL|http://www.gnu.de/documents/lgpl.de.html]).
* __[Mobile-App]__: Application allowing to use d3web problem solving knowledge in a stand alone application (free for use for non-commercial applications).
* __[Droid3web-App]__: Application allowing to use d3web problem solving knowledge on your mobile device (free for use for non-commercial applications).

! Knowledge Engineering Tools

* __[KnowledgeBaseBook]__: Generates a DocBook XML file of an executable d3web knowledge base, i.e., the knowledge base book. The DocBook XML can be used for further transformations. The application produces a PDF printout (commercial application).
* __WUMPS__: Knowledge acquisition based on Office documents ([LGPL|http://www.gnu.de/documents/lgpl.de.html]).
* __[KnowWE-Headless-App]__: An version of KnowWE without the normally underlying web server. It can be used to produced d3web knowledge bases from wiki pages in a batch process ([LGPL|http://www.gnu.de/documents/lgpl.de.html]).
* __[Testing-App]__: Allows to continuously run specified tests on a d3web knowledge base in development (commercial application).

!!! Modules (under construction)
 
Modules are the different parts of the main products and applications 

!Complex modules
* [Module TimeDB]
* [Module CostBenefit]
* [Module Rdf2Go]
* [Module DiaFlux]

%%Todo
Licenses 
* add articles for the different licenses and link them
* d3web-KnowWE-Releases contain all used licenses...
@user: Albrecht Striffler  
%




%%Todo
Module-Plugin implementation
* Jenkins-Plugin to upload Plugin/Module information
** [https://wiki.jenkins-ci.org/display/JENKINS/Extend+Jenkins]
** SVN: https://svn.jenkins-ci.org/
** Download jenkins war and add to tomcat
** Get hello world plugin and import into new workspace
** Plugin execution not covered by lifecycle configuration does not matter, it is just ugly
** Maven install hello world plugin
** Copy hello-world.jar to WEB-INF\lib
** Copy hello-world.hpi to WEB-INF\plugins
** Start tomcat/jenkins
** Hello world plugin will be available as post step option
** Start implementing new plugin to upload build data to d3web.de page as a attachment
** [Some additional code snipplets on how to upload files to a KnowWE Action|Upload a file to KnowWE]
** Provide information needed for module pages

@user: Alex Legler
%

%%Todo
Module-Plugin implementation
* Design ontologie about module information. We want for example the following information per module:
** What maven modules / svn projects are part of this module (will be defined on the module page with turtle markup)
** What projects are not in any complex/aggregated module
** What are the last x changes to any project of a module
** What is the heat of the module (changes/day in the last month?)
** What are the test stats for the module
** General stats, if possible? LoC, Classes, BuildNumber
** Authors (people who created modules, changed them)
** More interesting stuff?
* Write KnowWE-Plugin to add data provided by Jenkins-Plugin to the rdf2go model.
* If there is time: Write KnowWE-Plugin to render module information from rdf2go model in a nicer way. If there is no time: Use default SparqlRenderer
@user: Sebastian Furth
%

!Product Ontology

* [Product Ontology]
* [CIConnector] (includes some DEMO-SPARQLs)

%%tags
Overview
%

!Quality assessment of the modules:
%%Table 
| no | Not officially included, experimental demo
| alpha | Basic functions included, API to be considered as unstable documentation partly available/not available mostly untested
| beta | All functions are included documentation available functionality tested on unit level
| release | All functions are included documentation available functionality tested on system level (integration tests) internal processes fully applied (issue management, development process)
%