Main Page

From PDune

Jump to: navigation, search

Contents

Features

We're getting very far towards a full quality management system! We've finished the baselines for the following modules. They are functional, but we appreciate your input to improve the current features so that they become even more useful:

  • 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.
  • Customer management. A crude tool to manage customer details. It currently accepts helpdesk emails and you can create issues directly from those emails without copying and pasting results. This module does need some good additions to become more useful.
  • 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 :).
  • User management. User management is concerned with managing logins for users, changing their logins and access permissions. This is also where users get assigned to projects. If a user is not an admin, that user will only have access to releases, project information, issues, tasks and timesheet entries that relate to those assigned projects.
  • Document management. An innovative module allows you to write your documentation of the project in Dune itself. The benefit is that changes to paragraphs of the requirements or the design may trigger notification messages to those people that are subscribed to the related issue of that paragraph. Having your documents in the database has some benefits:
  1. latest version is always accessible and not on someone's machine
  2. Automatically backed up along with other data
  3. Relationships of document elements with other entities in your system;
  4. No viruses;
  5. No need for costly office software;
  6. Requirements traceability.


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

Automation in software quality

Project Dune was started in 2003 by Gerard Toonstra with the following objectives:

  • P rovide better project control
  • R educe the cost of software development
  • I mprove the quality of developed software
  • M ake the software free (GPL)
  • E nable better statistics and reports
  • D ocument approaches and insights in quality. Make those insights available to the general public

primed (adj.)

  • First in excellence, quality, or value.
  • First in degree or rank; chief.
  • First or early in time, order, or sequence.

also

  • To make ready; prepare: guard dogs primed for attack.
  • To prepare (a gun or mine) for firing by inserting a charge of gunpowder or a primer.
  • To prepare for operation, as by pouring water into a pump or gasoline into a carburetor.
  • To prepare (a surface) for painting by covering with size, primer, or an undercoat.
  • To inform or instruct beforehand; coach.

(source: The American Heritage® Dictionary of the English Language, Fourth Edition. Retrieved September 01, 2007, from Dictionary.com website: [1])

To realize these objectives and show our commitment to a better understanding of software quality, we do the following:

The documentation is also available under the Creative Commons Attribution 3.0 License. That means you are free to use that work as a starting point for your own quality plan, or to use it to refine your own plans, as long as you give attribution to the authors.


Registered users can contribute to this wiki and can edit pages that are not specific to Project Dune.


Rationale

This section applies to the software only. We think there are huge effort benefits (and thus cost) in project management when you guide development better and automate some of the daunting administration tasks that come along with software development. An intelligent project management environment wins back precious development time and should improve motivation. The project aims for a single accessible system for your timesheets, issues, documents, estimates, tasks and customer information, a single repository and tool where all this information is interlinked so that you don't need to maintain your own spreadsheets any longer. This gives you real-time information when you need it and will eventually allow you to make better project (and organizational) decisions.


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 must be made available publically as well. The source code for each official release can always be downloaded from the SourceForge website, where the project is hosted. Source Forge also offers a Browse Source option, where you can look at source files without downloading the whole project. 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. Complete snapshots of the source code are also available for download.

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. The source code as a package are available there as well.

Direct Download Link

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 wish to see only a single file for reference:

Browse SVN


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.

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

Here you can read what users and customers are saying about us.


Documentation

The following project documentation, specific to running the software, is available:

If you really want to get your hands dirty, we also provide the details of the schema online:

Database schema


Roadmap

Our Roadmap


How To Contribute

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

For developers, we have a special area on our wiki that explains our development process. See our Development guide for some basic information about the architecture. A special area on this wiki has a lot more information with regards to our Processes and Practices.

Current Contributors

Past Contributors


General Quality Information

The General Quality Information is hosted on this wiki and is an initiative to document consolidated knowledge. Let's start from the main page of that area and consider your contributions. You can find instructions here for making your contributions on this wiki, as the editor can be a bit tricky in the beginning. This wiki is an installation of MediaWiki, which has instructions for editing available on the internet.

Gwat 21:49, 2 September 2007 (CDT)

Retrieved from "http://projectdune.org/Main_Page"
Personal tools