Project Dune:Software Modules

From PDune

Jump to: navigation, search

Contents

Features

We're nicely underway towards a full project/quality management system:

  • Issue management. Manages your software development issues. You can link other entities like customers, releases and issues themselves to them.
  • Project and release management. Manages your projects and releases. The releases contain scope statements that document the scope of that release. The scope statement also maintains ballpark estimates that can be useful for the "Release Effort Verification" report.
  • Inspection tool. This is an online module where you can execute inspections from your browser. The inspection data is stored in the database. That way, we can develop interesting reports at later time to improve your development efficiency.
  • SCRUM task management. With this module you can manage your tasks in the browser. It's organized in a SCRUM-like manner. You choose a project and then you organize your tasks around that. Tasks are associated with issues, which are associated with releases. This way, you can keep things organized.
  • Timesheet management. This is the next step after tasks are done. Users can register their time in Project Dune as well. If you use the timesheet module correctly, you can output a report that verifies your time spent in timesheets, against detailed estimates of the tasks that you set up, against the ballpark estimates in the scope statements. Those verifications may be handy to improve your ballpark estimates in the future and become more aggressive (or correct, depending on the outcome of your project :).
  • Document management. An innovative module allows you to write your documentation of the project in Dune itself. Doing this on the web, has several benefits.
  • Estimate management. Estimates are produced by the Cocomo II estimation model. They can be copied to produce different estimations on the same work. The outcome of these estimates can be used as input later when the release and scope statements are defined.
  • Test management. Test cases are written from the browser and added to a project. A test run is created and the results of the tests are recorded in the browser. Project Dune makes it a lot easier to open new issues or reopen existing ones. Test reports are auto-generated on-the-fly if so desired.

For detailed feature information, see full list of features and screenshots.


License

The software is available under the GPL license. That does not mean that you cannot use the software in house, link with it in-house or not use it in-house. Please see this page that clarifies your Rights and Restrictions.

Since we make binaries available to the general public under this license, the source code are publically available as well.

All articles on this wiki are licensed under the Creative Commons Attribution 3.0 License. The only exception are very specific project guides (user guide, development guide). Where the license is different, it is explicitly stated. We believe this license to be most appropriate for the project and it is the most liberal license available. Please do not violate the license. It only requires you to give credit to the authors of the original documentation.

This license lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of licenses offered, in terms of what others can do with your works licensed under Attribution.

Attribution: You let others copy, distribute, display, and perform your copyrighted work — and derivative works based upon it — but only if they give credit the way you request.


Downloads

The latest version from the Dune project can always be downloaded from the SourceForge website, where the project is hosted. Pay specific attention to the release notes for each release. It includes the specific changes for that distribution and may have an impact on your deployment.

Source Code

The source code for each official release can always be downloaded from the SourceForge website, where the project is hosted.

Here are the instructions for checking out the latest versions of the source code files using Subversion. Note that the state of the source code repository is not always in a stable state due to ongoing tasks. Changes to the repository are frequent.

A single package with a complete snapshot of the source code are also there available for download as well.

The source code can also be downloaded from the trunk directly. That will get you the latest version: 

svn co https://pdune.svn.sourceforge.net/svnroot/pdune pdune

Or, if you only wish to look at a single file for reference, SourceForge also offers a Browse SVN Source option, where you can look at source files without downloading the whole project.


Support

We prefer if you use the Project Dune Forums. You'll need to register with an account there, but you get access to the quality forums and you can monitor certain topics of your interest. Please consider contributing to the forums with the knowledge you gather from the project.

Please contact Project Dune for more information if you require more specific commercial support. You can also use this email if you have specific requirements.

You can also read what users and customers are saying about us.


Documentation

Specific documentation to running the software:


If you really want to get your hands dirty, we also provide internal project documentation:

Roadmap

The roadmap for a project defines the strategy of the project. It is based on the project's mission. The roadmap is meant to guide decisions to be taken in the project and as a means of communication to the user's community on the directions of the project. The roadmap is a living document that will see future iterations.


How To Contribute

Contribution can be done in a number of ways and is key to the project's survival. Please make sure you read our approaches to project management to make your contributions more efficient. The pages describes also how to raise bugs, how to submit patches and will give you insight how we are internally organized.


We give credit to our current & past contributors

Retrieved from "http://www.projectdune.org/Project_Dune:Software_Modules"
Personal tools