You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

projectdoc Toolbox

The fifth chapter of the arc42 Template with information on the local building blocks, and their dependencies and relationships.

ID
swad-section
Docsubtype
swad-section-building-block-view
Set
Categories
Tags

Provides a static decomposition of the system into building blocks and the relationships between them.

This is the fifth chapter of the arc42 Template.

Properties

The document type swad-section provides the following properties:

 

Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.

Docsubtype

The subtype of the document type identifies the document instance within its swad-section doctype.

Sections

Description

Provide an overview over the information on this document. Readers may decide on this description if the document contains relevant information to them.

Summary

Provide a summary of the documents structure and key points. This is an informative abstract typically of about 100 to 200 words.

Local Building Blocks

List the root building blocks of your system.

More help to document quality goals in this overview is found on arc42 on GitHub.

Using projectdoc

 

The toplevel building blocks may be documented with View or Component documents. From there you may drill deeper iterating with Blackbox and Whitebox views. You may also consider to connect the building blocks with the view documents that show the context of the system (see System Scope and Context).

Use the Transclude Documents Macro to transclude from these view documents according to the information needs of your stakeholders.

Dependencies and Relationships

Explain the dependencies and relationships of the listed building blocks.

Using projectdoc

 

This is a free text section. You may have a separate Section for each dependency or relationship and list them here. The list may contain references using the Display Table Macro or you may transclude the relevant part for your audience with the Transclude Documents Macro.

If the dependencies and relationships to explain are only a few with a limited amount of text, you may simply employ the Section Macro and create some subsections.

Notes

These are internal notes that are usually not exported and only visible to team members with write access.

But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.

 

The text of notes sections is also indexed.

References

For a document the references section contains pointers to resources that prove the statements of the document.

Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.

 

For further information please refer to References and Resources.

Resources

The resources section provides references to further information to the topic of the document.

This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.

 

For further information please refer to References and Resources.

References

The text in the expand boxes is transcluded from the arc42 GitHub project where the arc42 Template is maintained by the original authors and supporters.

arc42 is owned by Dr. Peter Hruschka & Dr. Gernot Starke.

  • No labels