Welcome to the Development Wiki Demo
This Wiki demonstrates the collaboration tools used by Riksof during any software development project. It provides a single platform for our customers and engineers to share project related information. As a software product develops, the Wiki provides a wealth of information pertaining to the requirements, design, APIs and general information about the product. This Wiki also provides a historical perspective to look back and see why certain decisions were taken.
In the following sections we detail the individual components of this website and the services they provide. You may chose to review the site in the order given below, or skip to those sections that interest you.
Every page on this website is a Wiki, which can be edited as required. Editing wiki text is easy, using any web browser and a simple formatting system, rather than more complex markup languages like HTML. More information on creating new pages, editing and formatting them can be found here: TracWiki.
This link will take you to another section of the website. You can always return to this page by clicking on the Wiki link in the menu bar above.
The Wiki comes with search capabilities that allow you to search the whole website for any particular information.
Note: You must have access to Wiki for creating and editing content.
Table of content
- Ticket System: The ticketing systems allows us to manage all activities related to a project. Each task in a project is associated with a ticket, which may be assigned to an individual or a group. Tickets have priorities, can be associated with milestones and release versions. Each ticket maintains a history of communication related to that task. All code changes made for a ticket, reference the ticket.
- Roadmap: Roadmap defines a set of milestones and provides a snapshot of the current status of each milestone. Each milestone is associated with a set of tickets. The progress of a milestone is determined by the number of tickets completed when compared with the total number of tickets.
- Timeline: The Timeline section provides a history of recent activities on this project. Each entry in the time line may have links to source code changes, changes on the wiki or changes to the ticketing system.
- Project Scheduling: We have integrated Trac's ticketing system with Taskjuggler to provide additional reports. Each project has a calendar, a summary of all tasks as well as weekly reports to determine current project status when compared to the planned schedule.
- Browse Source: For all software projects, Subversion is used as the version control system. Browse Source shows the structure and content of files on the Subversion server. The exact structure of a repository varies based on the requirements of a project. Usually, trunk is the main development branch.
- Testing Framework: We use JUnit and CUnit testing framworks for appropriately sized project.
- Automated Builds: We use Cruise Control for providing continuous builds for projects that need this facility.
- Code Documentation: We use well defined coding standards that allow code documentation to be generated using PHP Doc, Java Doc or Doxygen.