Provides doctypes to create documentation in software development projects. The focus is on documenting the architecture of the product, but it includes templates for other software development documentation requirements as well.
English and German by Default
All doctype add-ons are available in English and German language (except for the V-Modell XT add-on for which only supports German).
For more information on this topic please refer to Localization.
The Doctypes for Software Development help agile teams to document their software architecture.
Create a space and you have a basic structure, a repository, to add the relevant information for your stakeholders.
After you have created your space use the page blueprints to create documents for project constraints, requirements, views, architecture aspects (aka concepts) and many more.
The different topics are part of a document that comprise usually one wiki page. Since these pages are loosely coupled, they can be combined for different audience groups (e.g. using Tours or Volumes) easily. This makes it natural to run single source documentation principles and employ advanced features like transclusions or automatic lists. If the concepts you want to discuss are complex, you are not limited to a single page. Use the Section or other doctypes to create pages for modular content.
The Doctypes for Software Development requires the projectdoc Toolbox to be installed. The projectdoc Toolbox has a commercial license.
Please install the following add-ons on your Atlassian Confluence server:
List of Doctypes for Software Development
The following doctypes help to document your software projects.
This list can be overwhelming, but using the templates is usually quite straight forward. To get a quick overview we suggest to open the Prezi presentation (the one we mentioned on the top of the page) which groups the logically closely related document types.
Mind some basics given in How to document a Software Development Project?
For an introduction to using projectdoc doctypes and macros from the author's point of view, have a look at the following documents:
|#||Name||Short Description||Set||Documentation Type||Categories|
Document a possible option for an architecture decision. Choose this document type to describe the alternative for a decision in more detail. This is typically a subpage of an architecture decision document.
Group architecture alternatives by their type.
Document an aspect of your architecture. Something orthogonal or cross-functional like logging, exception handling or configurability.
Group architecture aspects by their type.
Document a architecture decision for an option. This is useful to state the reasons and the options that have been evaluated. Later other team members will have it easier to understand the decision.
Architecture decisions are group by their types. A commonly used decision type is 'Architecture'.
Document requirements you impose on artifacts. Artifacts are created by processes defined and used by the team. This includes assemblies created by the build process, source code artifacts or reports.
Artifact types categorize artifacts.
Describe as a Blackbox the elements of a view where only the externally visible properties are relevant.
Group blackboxes by their type.
Describe the codes that are part of the product's API.
Code types categorize codes, used in logging or exception handling.
Components are part of a view on a system. A component may refer to a enclosed element or to a complete system of its own.
Component types categorize components.
Document logical or physical groups of nodes.
Type of an environment used by the project to deploy the application or the solution.
Documents a feature of the product. The top features define the main aspects of the product.
Feature types categorize features.
Interfaces document how elements of the system communicate with elements of this and other systems.
Group interfaces by their type.
Nodes are part of environments where artifacts are deployed to.
Node types categorize nodes.
Out Items record topics that are out of the scope of the project. This is useful for project inception and for reference in the future.
Out item types categorize out items.
Project Constraints limit the options of a project.
Project constraint types categorize project constraints.
Frame the vision for a project or iteration.
Types to categorize vision statements for projects.
Properties are part of the configuration options of a system.
Property types categorize properties of products, such as parameters or configuration options.
Qualities describe desired aspects of the product.
Quality Scenarios document required qualities.
Quality scenario types categorize quality scenarios.
Documents a quality target for a product.
Group quality targets by their type.
Documents requirements of a product.
Categorization of requirements for a product.
Technical Debts track issues to be paid back.
Technical Debts are grouped by the area they address.
Document a test case of your project.
Test case types categorize test cases.
Defines a charter to run an exploratory test session.
Test charter types categorize test charters.
Document data used for test cases.
Test data types categorize test data.
Documents the results of a test session for the sponsoring stakeholders.
Test report types categorize test reports.
Defines a document to collect information during a test session.
Test session types categorize test sessions.
Defines a use case of the product.
Use case types categorize use cases.
User Characters are the actors of user stories. They include personas and extreme characters.
User character types categorize user characters.
Different views on the product help to document the system and its architecture. Typical views are building block, runtime, or deployment.
Groups the views at a system.
Describe as a Whitebox the elements of a view where only the relations of internal elements are relevant.
Group whiteboxes by their type.
The following macros are provided by this add-on.
- User Story Macro
- Renders a user story of a user story doctype.