Go to start of metadata
- Created by Robert Reiner on 20. Dec 2017
projectdoc Toolbox
Doctype Index
List of all doctypes.
| Name | Short Description | Parent |
|---|---|---|
| Introduction and Goals | The first chapter of the arc42 Template with information on requirements, quality goals, and stakeholders. | arc42 Template |
| Architecture Constraints | The second chapter of the arc42 Template with information on constraints and conventions. | arc42 Template |
| System Scope and Context | The third chapter of the arc42 Template with information on context and external interfaces. | arc42 Template |
| Solution Strategy | The fourth chapter of the arc42 Template explains the solution idea. | arc42 Template |
| Building Block View | The fifth chapter of the arc42 Template with information on the local building blocks, and their dependencies and relationships. | arc42 Template |
| Runtime View | The sixth chapter of the arc42 Template with runtime information about the architecture. | arc42 Template |
| Deployment View | The seventh chapter of the arc42 Template with information about how the system is deployed. | arc42 Template |
| Cross-cutting Concepts | The eighth chapter of the arc42 Template with conceptional information about the system. | arc42 Template |
| Design Decisions | The ninth chapter of the arc42 Template that explains the architecture decisions that led to the system. | arc42 Template |
| Quality Requirements | The tenth chapter of the arc42 Template that lists scenarios to systematically evaluate the architecture against the quality requirements. | arc42 Template |
| Risks and Technical Debts | The eleventh chapter of the arc42 Template lists risks and technical debt. | arc42 Template |
| Glossary | The last chapter of the arc42 Template lists terms of the domain and explains them. | arc42 Template |
| Access Information | Credentials for development systems where the password is known to all who have access to the Confluence wiki. | Doctypes for Service Management |
| Access Information Type | Type-specific category for access information. | Doctypes for Service Management |
| Alternative | This documents a possible option for a decision. Choose this document type to describe the alternative for a decision in more detail. This is typically a subpage of a decision document. | Doctypes for Project Management |
| Alternative Type | Group your alternatives by a self-defined type. | Doctypes for Project Management |
| Announcement | Announcements are a way to communicate an important piece of information with your team. | Doctypes for Agile Planning |
| Annual Vision | Describe your vision for one year. You plan will help you stay focussed to accomplish your goals. | projectdoc Developer Diaries |
| Annual Vision Type | Categories for annual visions. | projectdoc Developer Diaries |
| App | Document your app for your users and customers. | |
| App Component | Provide more detailed information about a component of a tool. | |
| App Component Type | Document the purpose and usage of the components of this type. | |
| App Extension | Document your extension for your users and customers. | |
| App Extension Type | Document the purpose and usage of the extension of this type. | |
| App Macro | Document the purpose and usage of the macro. | |
| App Macro Type | Document the purpose and usage of the macros of this type. | |
| App Parameter | A parameter is a configuration option. Parameter exist on different layers. Wizard and macro parameters are configuration options. Use | |
| App Parameter Type | Document the purpose and usage of the app parameters of this type. | |
| App Platform | Document a platform for apps. | |
| App Platform Type | Document the purpose and usage of the platforms of this type. | |
| App Service | Document a service provided by an app. | |
| App Service Type | Document the purpose and usage of the app services of this type. | |
| App Tool | Document a tool provided by an app. | |
| App Tool Type | Document the purpose and usage of the app tools of this type. | |
| App Type | Document the purpose and usage of the apps of this type. | |
| Application | Applications provided functions required by services. Applications may be hosted on one or more systems. | Doctypes for Service Management |
| Application Type | Type-specific category for applications. | Doctypes for Service Management |
| arc42 Template | The blueprint of the arc42 Template creates a tree of pages in the Confluence space. | |
| Architecture Alternative | 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. | Doctypes for Software Development |
| Architecture Alternative Type | Group architecture alternatives by their type. | Doctypes for Software Development |
| Architecture Aspect | Document an aspect of your architecture. Something orthogonal or cross-functional like logging, exception handling or configurability. | Doctypes for Software Development |
| Architecture Aspect Type | Group architecture aspects by their type. | Doctypes for Software Development |
| Architecture Decision | 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. | Doctypes for Software Development |
| Architecture Decision Type | Architecture decisions are group by their types. A commonly used decision type is 'Architecture'. | Doctypes for Software Development |
| Artifact | 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. | Doctypes for Software Development |
| Artifact Type | Artifact types categorize artifacts. | Doctypes for Software Development |
| Asset | Explain an asset of your work. Add this document to a day in your diary. | projectdoc Developer Diaries |
| Asset Type | Categories for assets. | projectdoc Developer Diaries |
| Association | Associates two documents. | |
| Association Type | Categorize associations by a type. | |
| Assumption | Document assumptions to assess risks and opportunities for the project. | Doctypes for Risk Management |
| Assumption | Assumptions document what you think about your product, customers, and partners. Once you start identifying assumptions, it will become clearer what other beliefs you hold about how you plan to build, design, distribute, and create value with your product. Making assumptions explicit allows to publish them and discuss them with other stakeholders. | |
| Assumption Resolution | Assumptions can be resolved in different ways. Define what each resolution implies. | |
| Assumption Resolution Type | Type-specific category for assumption resolutions. | |
| Assumption Type | Assumptions are grouped by their type. | Doctypes for Risk Management |
| Assumption Type | Type-specific category for assumptions. | |
| Blackbox | Describe as a Blackbox the elements of a view where only the externally visible properties are relevant. | |
| Blackbox Type | Group blackboxes by their type. | Doctypes for Software Development |
| Blank Document | The blank template simply provides a minimal integration with projectdoc features. It is a quick starting point to use projectdoc. | Doctypes |
| Bookmarklet Editor | The bookmarklets editor is a simple page that allows teams to create their bookmarklets more easily. It also provides access to some standard bookmarklets provided for the projectdoc Toolbox. | Bookmarklets Extension |
| Category | Categories allow to set document instance of different doctypes in a hierarchy. | |
| Category Type | Categorize categories by a type. | |
| Change | Document a single change to configuration items or assets. | |
| Change Severity | Add an severity to classify changes. | Doctypes for Service Management |
| Change Status | Add a status to categorize changes. | Doctypes for Service Management |
| Change Theme | Add a theme to group changes. | Doctypes for Service Management |
| Change Type | Type-specific category for changes. | Doctypes for Service Management |
| Charter | Describes an information need and use this description as a basis to create and maintain a document. | |
| Charter Type | Categorize charters by a type. | |
| Cheat | A brief solution to a problem. | projectdoc Developer Diaries |
| Cheat Type | Categories for cheats. | projectdoc Developer Diaries |
| Check-in | Document the result of a OKR check-in. | |
| Check-in Type | Type-specific category for OKR check-ins. | |
| Checklist | Checklists allow to run manual tasks in a defined manner. It guides the user of the checklist through a process and helping to not forget a step. | Doctypes for Teamwork |
| Checklist Type | Categorize checklists by type. | Doctypes for Teamwork |
| Code | Describe the codes that are part of the product's API. | Doctypes for Software Development |
| Code Type | Code types categorize codes, used in logging or exception handling. | Doctypes for Software Development |
| Component | 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. | Doctypes for Software Development |
| Component Type | Component types categorize components. | Doctypes for Software Development |
| Configuration Item | Configuration items (CIs) may be (sub-)systems or components. Whatever may change and needs to be tracked may be documented as a CI. | Doctypes for Service Management |
| Configuration Item Status | Signals the status of an IT system, application, or a configuration item. | Doctypes for Service Management |
| Configuration Item Type | Type-specific category for configuration items. | Doctypes for Service Management |
| Cycle | Add cycles to group cycle phases. | |
| Cycle Phase | Cycle phases define phases that are bound to a cycle, such as lifecycles or iterations. | |
| Data Type | Document a data type for properties and codes. | |
| Data Type Type | Data type types categorize data types. | Doctypes for Software Development |
| Dataset | Datasets are used as the input and output of processes. | Doctypes for Service Management |
| Dataset Type | Type-specific category for datasets. | Doctypes for Service Management |
| Day | Store relevant information discovered today in your developer diary. | projectdoc Developer Diaries |
| Day Type | Categories for days. | projectdoc Developer Diaries |
| Decision | Document a 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. | Doctypes for Project Management |
| Decision Type | Group your decisions by a self-defined type. | Doctypes for Project Management |
| Deployment | Deployments provide information about updates on services and systems to users. | Doctypes for Service Management |
| Deployment Record | Record a deployment to a IT system. | Doctypes for Service Management |
| Deployment Record Type | Type-specific category for deployment records. | Doctypes for Service Management |
| Deployment Type | Type-specific category for deployments. | Doctypes for Service Management |
| Diary | The homepage of a developer's daily diary pages. Consider to add your diary to your personal space! | projectdoc Developer Diaries |
| Diary Type | Categories for diaries. | projectdoc Developer Diaries |
| Doctype | Document the usage of a doctype for your users. | |
| Doctype Type | Document the purpose and usage of the doctypes of this type. | |
| Document Property | Document the usage of a document property for your users. | |
| Document Property Type | Document the purpose and usage of the properties of this type. | |
| Document Section | Document the usage of a document section for your users. | |
| Document Section | Document the purpose and usage of the sections of this type. | |
| Environment | Document logical or physical groups of nodes. | Doctypes for Software Development |
| Environment Type | Type of an environment used by the project to deploy the application or the solution. | Doctypes for Software Development |
| Event | Associated an event with a day. A event is a collection of associated information for your later reference. Information may further be organized by subject, tags, categories, and audience. | projectdoc Developer Diaries |
| Event Type | Categories for events. | projectdoc Developer Diaries |
| Excerpt | Excerpts are abstracts of information found in a resource, such as a book. If you want to go into more detail for a given resource, there may be multiple excerpts as subpages of the resource document. | |
| Excerpt Type | Categorize excerpts by a type. | |
| Experience Level | Defines the context through which readers acquire skills. The level sets the expectation on the author's techniques to teach. | |
| Experience Level Type | Categorize experience levels by a type. | |
| FAQ | FAQs help to record an answer to a frequently asked question concerning the project, the product, the system or the process. | |
| FAQ Type | Categorize FAQs by a type. | |
| Feature | Documents a feature of the product. The top features define the main aspects of the product. | Doctypes for Software Development |
| Feature Type | Feature types categorize features. | Doctypes for Software Development |
| Generic | Generic Documents provide information where no other doctype matches. | |
| Generic Type | Categorize generic documents by a type. | |
| Glossary Item | Glossary items are part of the domain glossary for the project. Glossaries support the team to use terms of the domain consistently in conversations and documentation. | |
| Glossary Item Type | Categorize glossary items by a type. | |
| How | Describe how the impact will be pursued. | |
| How Type | Type-specific category for hows. | |
| Hypothesis | Write your problem hypothesis. This is the hypothesis that you will either validate or (probably) come back and revise. | |
| Hypothesis Status | Type-specific category for hypotheses based on status. | |
| Hypothesis Status Type | Type-specific category for hypothesis status. | |
| Hypothesis Type | Type-specific category for hypotheses. | |
| Impact | Publish an impact you want to achieve. Share this information with your colleagues. | |
| Impact Map | Publish impacts you want to achieve. Share this information with your colleagues. | |
| Impact Map Type | Type-specific category for impact maps. | |
| Impact Type | Type-specific category for impacts. | |
| Improvement | Improvement proposals help to start the conversation within the team for process improvements. | Doctypes for Agile Planning |
| Interface | Interfaces document how elements of the system communicate with elements of this and other systems. | |
| Interface Type | Group interfaces by their type. | Doctypes for Software Development |
| IT Activity | IT Activities define activities for processes. | Doctypes for Service Management |
| IT Activity Type | Type-specific category for IT activities. | Doctypes for Service Management |
| IT Asset | IT Assets define assets required or produced by processes. | Doctypes for Service Management |
| IT Asset Type | Type-specific category for IT assets. | Doctypes for Service Management |
| IT Function | Functions are specialized organizational units to support business processes. | |
| IT Function Type | Type-specific category for IT functions. | Doctypes for Service Management |
| IT Procedure | IT Procedures define procedures for processes. | Doctypes for Service Management |
| IT Procedure Type | Type-specific category for IT procedures. | Doctypes for Service Management |
| IT Process | Processes organize activities to create a defined business value. | Doctypes for Service Management |
| IT Process Type | Type-specific category for IT processes. | Doctypes for Service Management |
| IT Service | IT Services provide business relevant services for customers. | Doctypes for Service Management |
| IT Service Classification | Classifiers to categorize services. | Doctypes for Service Management |
| IT Service Classification Type | Type-specific classification for IT services. | Doctypes for Service Management |
| IT Service Status | Signals the status of an IT Service. | Doctypes for Service Management |
| IT Service Type | Type-specific category for IT services. | Doctypes for Service Management |
| IT System | Systems are part of environments where products are deployed to. | Doctypes for Service Management |
| IT System Type | Systems are categorized by their type. These types may be quite concrete since systems by nature reference a hard- or software system usually by their IP address or DNS name. Therefore a system type may be 'Artifact Repository' or 'Virtual Server. And types may build hierarchies. | Doctypes for Service Management |
| Iteration | Document an Iteration that may be linked from JIRA. Allows the team to set the goal and add notes relevant to a particular iteration. | Doctypes for Agile Planning |
| Key Result | Publish key results to achieve in order to pursue an objective to share with your colleagues. | |
| Key Result Type | Type-specific category for key results. | |
| Lifecycle | Add lifecycles to group lifecycle phases. | Doctypes for Service Management |
| Lifecycle Phase | Lifecycle phases define phases that are bound to a lifecycle. | Doctypes for Service Management |
| Location | Locations provide information about the whereabouts of assets, configuration items, and systems. | Doctypes for Service Management |
| Location Type | Type-specific category for locations. | Doctypes for Service Management |
| Media Type | Resources are identified by their media type. This may be the MIME type, but also a human readable string, that identifies the syntactic format. | |
| Media Type Type | Categorize media types by their type. | |
| Metadata | Metadata documents provide tables of simple key/value pairs. This information can be used as an aspect or as additional space properties to be available for reference on your wiki. | |
| Metadata Type | Categorize metadata documents by a type. | |
| Minutes | Record the action items of a meeting. | Doctypes for Project Management |
| Minutes Type | Group your minutes by a self-defined type. | Doctypes for Project Management |
| Mission Statement | Define a mission for your company or product. | |
| Mission Statement Type | Type-specific category for mission statements. | Doctypes for Business Strategy |
| Module | A documentation module is a fragment which is usually transcluded by other documents. The lifetime of a module document is independent of the lifetimes of the documents that reference it. | |
| Module Type | Categorization of document modules for single sourcing. | |
| Month | Plan and run a retrospective for your month of work. | projectdoc Developer Diaries |
| Month Type | Categories for months. | projectdoc Developer Diaries |
| Node | Nodes are part of environments where artifacts are deployed to. | Doctypes for Software Development |
| Node Type | Node types categorize nodes. | Doctypes for Software Development |
| Objective | Publish an objective to share with your colleagues. | |
| Objective Type | Type-specific category for objectives. | |
| OKR Priority | Category to organize strategic themes, objectives, and key results. | |
| Open Issue | Open issues document what the team needs to know to proceed. | Doctypes for Project Management |
| Open Issue Severity | Open issues are grouped by the severity of their impact on the project. | Doctypes for Project Management |
| Open Issue Status | Open issues are grouped by the status. | Doctypes for Project Management |
| Open Issue Type | Group your open issues by a self-defined type. | Doctypes for Project Management |
| Opportunity | Document and track identified opportunities for the project. | Doctypes for Risk Management |
| Opportunity Type | Opportunities are grouped by their type. | Doctypes for Risk Management |
| Organization | Information about organizations that take a part in the project. You may collect common information here for all persons that belong to an organization, such as address or homepage. | |
| Organization Type | Categorize organizations by a type. | |
| Out Item | 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. | Doctypes for Software Development |
| Out Item Type | Out item types categorize out items. | Doctypes for Software Development |
| Outcome | Products used by customers intend to make a change. This change is called outcome. | |
| Outcome Type | Type-specific category for outcomes. | |
| Output | The output is the artifact created to be employed by user for a specific outcome and - on the long run - may make an impact. | |
| Output Type | Type-specific category for outputs. | |
| Page Blueprint | Document the purpose and usage of a page blueprint. | |
| Page Blueprint Type | Document the purpose and usage of the page blueprints of this type. | |
| Pattern | Patterns provide solutions for problems in a given context. Patterns are usefull in multiple areas such as design, architecture, documentation, or process. | Doctypes for Teamwork |
| Pattern Domain | Patterns are divided into different domains to group patterns. | Doctypes for Teamwork |
| Pattern Type | Categorize patterns by type. | Doctypes for Teamwork |
| Person | Provides information about a person. This includes contact information (important if the person is relevant for the team) or information about the competences (if the person is an author about a topic relevant for the project). | |
| Person Type | Categorize persons by a type. | |
| Problem | Document problems as a means to communicate the details and to use the information for reviews and retrospections. | Doctypes for Risk Management |
| Problem Type | Problems are grouped by their type. | Doctypes for Risk Management |
| Process Impact | Impacts define how the results of processes affect the world. | Doctypes for Service Management |
| Process Impact Type | Type-specific category for impacts. | Doctypes for Service Management |
| Process Outcome | Outcomes define the results of processes. | Doctypes for Service Management |
| Process Outcome Type | Type-specific category for outcomes. | Doctypes for Service Management |
| Product Backlog | Product Backlogs are means to collect user stories. | Doctypes for Agile Planning |
| Profile | Profiles provide views on documents via delegation. | |
| Profile Type | Categorize profiles by a type. | |
| Project Constraint | Project Constraints limit the options of a project. | Doctypes for Software Development |
| Project Constraint Type | Project constraint types categorize project constraints. | Doctypes for Software Development |
| Project Rule | Project Rules are defined by the team to enhance the collaboration and to define project standards. | Doctypes for Teamwork |
| Project Rule Type | Categorize project rules by type. | Doctypes for Teamwork |
| Project Vision | Frame the vision for a project or iteration. | Doctypes for Software Development |
| Project Vision Type | Types to categorize vision statements for projects. | Doctypes for Software Development |
| Property | Properties are part of the configuration options of a system. | Doctypes for Software Development |
| Property Type | Property types categorize properties of products, such as parameters or configuration options. | Doctypes for Software Development |
| Quality | Qualities describe desired aspects of the product. | Doctypes for Software Development |
| Quality Scenario | Quality Scenarios document required qualities. | Doctypes for Software Development |
| Quality Scenario Type | Quality scenario types categorize quality scenarios. | Doctypes for Software Development |
| Quality Target | Documents a quality target for a product. | Doctypes for Software Development |
| Quality Target Type | Group quality targets by their type. | Doctypes for Software Development |
| Quote | Quotes relevant for the project. Allows to store the content and metadata to the quote. | |
| Quote Type | Categorize quotes by a type. | |
| Relation | Organizes glossary items. | |
| Relation Type | Categorize relations by a type. | |
| Release | Releases document the changes that are applied to a published version of a service. | Doctypes for Service Management |
| Release Note | Document changes provided by a release of a product. | Doctypes for Project Management |
| Release Note Type | Group your release notes by a self-defined type. | Doctypes for Project Management |
| Release Type | Type-specific category for releases. | Doctypes for Service Management |
| Report | Reports document what the team has decided or done. This is a generic document. | Doctypes for Project Management |
| Report Type | Group your reports by a self-defined type. | Doctypes for Project Management |
| Requirement | Documents requirements of a product. | Doctypes for Software Development |
| Requirement Type | Categorization of requirements for a product. | Doctypes for Software Development |
| Resource | Resources are books, webpages, videocasts relevant for the project. Add important information to your project about resources that lie outside the control of your team. | |
| Resource Type | Resources are identified by their type. This is not the MIME type, but human readable string, that identifies the semantic, rather than the syntactic format. | |
| Retrospective | Record the discussion of the team about their last iteration. | Doctypes for Agile Planning |
| Review | Plan and run your review meeting. | Doctypes for Agile Planning |
| Review Act | A single act to show on the review. Use this only if you have a lot to show or you want to reference the review results later. Often a simple numerated list is sufficient. | Doctypes for Agile Planning |
| Risk | Document and track identified risks for the project. | Doctypes for Risk Management |
| Risk Action | Document actions to prevent or reduce the negative impact on exceptions on a project. | Doctypes for Risk Management |
| Risk Action Type | Risk actions are grouped by their type. | Doctypes for Risk Management |
| Risk Phase | Risks are grouped by the phase of their impact on the project. | Doctypes for Risk Management |
| Risk Probability | Risks are grouped by the probability of having impact on the project. | Doctypes for Risk Management |
| Risk Severity | Risks are grouped by the severity of their impact on the project. | Doctypes for Risk Management |
| Risk Target | Document targets of risks. | Doctypes for Risk Management |
| Risk Target Type | Risk tagets are grouped by their type. | Doctypes for Risk Management |
| Risk Type | Risks are grouped by their type. | Doctypes for Risk Management |
| Role | Defines a role with its responsibilities, tasks and requirements. Roles are incorporated by stakeholders who take interest in the project. The are also used to define the audience for documents. | |
| Role Type | Categorize roles by a type. | |
| Section | Sections of a document are typically part of a document. But the size of sections may vary. To support a team to write collaboratively on the documentation, a larger document may be subdivided into external section documents. | |
| Section Type | Categorize sections by a type. | |
| Service Announcement | Announcements communicate with stakeholders information about a service. | Doctypes for Service Management |
| Service Announcement Type | Type-specific category for service announcements. | Doctypes for Service Management |
| Service Level | Describe a service level for a service. | |
| Service Level Agreement | Provide information about a service level agreement (SLA). | |
| Service Level Agreement Type | Type-specific category for service level agreements. | Doctypes for Service Management |
| Service Level Requirement | Describe a requirement in terms of a service level. | |
| Service Level Requirement Type | Type-specific category for service level requirements. | Doctypes for Service Management |
| Service Level Type | Type-specific category for service levels. | Doctypes for Service Management |
| Space Blueprint | Document the purpose and usage of a space blueprint. | |
| Space Blueprint Type | Document the purpose and usage of the space blueprints of this type. | |
| Space Index | Compile other documents, yet space indices are themselves projectdoc documents. So they can be tagged and grouped. | |
| Space Index Type | Categorize space indexes by a type. | |
| Space Property | Space properties hold metadata of a space. They may be inherited by delegate spaces. | |
| Space Property Type | Document the purpose and usage of the space properties of this type. | |
| Stakeholder | A party that takes interest in a project. The stakeholder is either a real person, an organization or group, or represents a class of individuals, groups or organizations. | |
| Stakeholder Type | Categorize stakeholders by a type. | |
| Step | Describes a single step of an activity. A step is a generic document that is associated with a document that describes a process. It may be a test log or a howto. | |
| Step Type | Categorize steps by a type. | |
| Strategic Theme | Publish a strategic theme to group objectives and to share them with your colleagues. | |
| Strategic Theme Type | Type-specific category for strategic themes. | |
| Strategy | Defines a strategy for an organization or product. | |
| Strategy Type | Type-specific category for strategies. | Doctypes for Business Strategy |
| Subject | Subject documents allow to set document instance of different doctypes in a common context. | |
| Subject Type | Categorize subjects by a type. | |
| SWOT | Work on strengths, weaknesses, opportunities, and threats. | |
| SWOT Type | Type-specific category for SWOTs. | Doctypes for Business Strategy |
| Tag | Document the semantics of a tag. May also be used to document Confluence labels. | |
| Tag Type | Categorize tags by a type. | |
| Team Process | Document processes defined and used by the team. | Doctypes for Teamwork |
| Team Process Type | Categorize team processes by type. | Doctypes for Teamwork |
| Technical Debt | Technical Debts track issues to be paid back. | Doctypes for Software Development |
| Technical Debt Type | Technical Debts are grouped by the area they address. | Doctypes for Software Development |
| Test Case | Document a test case of your project. | Doctypes for Software Development |
| Test Case Type | Test case types categorize test cases. | Doctypes for Software Development |
| Test Charter | Defines a charter to run an exploratory test session. | Doctypes for Software Development |
| Test Charter Type | Test charter types categorize test charters. | Doctypes for Software Development |
| Test Data | Document data used for test cases. | Doctypes for Software Development |
| Test Data Type | Test data types categorize test data. | Doctypes for Software Development |
| Test Report | Documents the results of a test session for the sponsoring stakeholders. | Doctypes for Software Development |
| Test Report Type | Test report types categorize test reports. | Doctypes for Software Development |
| Test Session | Defines a document to collect information during a test session. | Doctypes for Software Development |
| Test Session Type | Test session types categorize test sessions. | Doctypes for Software Development |
| Todo | Add a todo note to your developer diary. | projectdoc Developer Diaries |
| Todo Type | Categories for todos. | projectdoc Developer Diaries |
| Tool | Document tools used by the team. Add information about how to fetch, install and best practices using it. | Doctypes for Teamwork |
| Tool Type | Categorize tools by type. | Doctypes for Teamwork |
| Topic | A description of a given topic. A topic may describing or explaining a concept, a task to accomplish or a reference. There are a couple of topic types that set the expectations for the reader. Instances of the topic doctype usually have independent lifetimes from any referencing documents. | |
| Topic Type | A topic type is a semantic type of the topic. It helps to set the expectations of potential readers. | |
| Tour | Guided tours through existing information. This allows to aggregate topics for a given question or audience, thus providing a view on a topic. | |
| Trigger | Triggers define signals for activities and processes. | Doctypes for Service Management |
| Trigger Type | Type-specific category for triggers. | Doctypes for Service Management |
| Use Case | Defines a use case of the product. | Doctypes for Software Development |
| Use Case Type | Use case types categorize use cases. | Doctypes for Software Development |
| User Character | User Characters are the actors of user stories. They include personas and extreme characters. | Doctypes for Software Development |
| User Character Type | User character types categorize user characters. | Doctypes for Software Development |
| User Story | User Stories document a requirement of a stakeholder with a specific business goal. It also provides an acceptance test. It is a representation of a unit of work. | Doctypes for Agile Planning |
| Version | Document a version of a product or service. | |
| Version Type | Categorize versions by a type. | |
| View | Different views on the product help to document the system and its architecture. Typical views are building block, runtime, or deployment. | Doctypes for Software Development |
| View Type | Groups the views at a system. | Doctypes for Software Development |
| Vision | Describe your vision for your career. | projectdoc Developer Diaries |
| Vision Statement | Define the vision for your organization or product. | |
| Vision Statement Type | Type-specific category for vision statements. | Doctypes for Business Strategy |
| Vision Type | Categories for visions. | projectdoc Developer Diaries |
| Week | Plan and run a retrospective for your week of work. | projectdoc Developer Diaries |
| Week Type | Categories for weeks. | projectdoc Developer Diaries |
| What | Describe the (high-level) deliverables (aka outcomes and outputs) required to achieve the impact. | |
| What Type | Type-specific category for whats. | |
| Whitebox | Describe as a Whitebox the elements of a view where only the relations of internal elements are relevant. | |
| Whitebox Type | Group whiteboxes by their type. | Doctypes for Software Development |
| Who | Describe who is involved in the impact. List the stakeholders that will support the impact. There may be stakeholders who will work against it. Also specify the stakeholders taking advantage or taking disadvantage even if they do not have power to influence the outcome. | |
| Who Type | Type-specific category for whos. | |
| Why | Describe why this impact is useful for your business. State the problem to be solved. | |
| Why Type | Type-specific category for whys. | |
| Work Instruction | Work Instructions define procedures for processes. Provide the most detailed information here how tasks are to be executed. This includes best practices. | Doctypes for Service Management |
| Work Instruction Type | Type-specific category for work instructions. | Doctypes for Service Management |
| Wrap-up | Track what you have achieved and the reasons why. Check what you have learned and find areas where you can improve. | |
| Wrap-up Type | Type-specific category for OKR wrap-ups. | |
| Year | Create a year in your Diary. | projectdoc Developer Diaries |
| Year Type | Categories for years. | projectdoc Developer Diaries |
Need more Info?
More information on doctype:
Index Views for Doctypes
Related Information
Related information in your wiki:
- Doctype Types
- Apps
- Extensions
- Page Blueprints
- No labels
