Date: Thu, 28 Mar 2024 11:47:20 +0100 (CET) Message-ID: <1785373656.17361.1711622840577@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17360_2111464185.1711622840577" ------=_Part_17360_2111464185.1711622840577 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Different views on the pr= oduct help to document the system and its architecture. Typical views are b= uilding block, runtime, or deployment.
Different views on your product he= lp to document the system and its architecture. Typical views are building = block, runtime, or deployment. You may define you own types of views to mee= t your documentation requirements.
The document type view 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 Propert= ies.
Ty= pes allow to group views. A project demands its own definition of types via= the View Type Doctype.
Defines the level of this view in the containment hierarchy of views.
Consider to use the Le= vel Macro to calculate this information based on the location of this d= ocument within the hierachy of view documents.
Provide context information to understand the view documentation.
Describe what the view is all abo= ut. May include a diagram to visualize what this section describes.<= /span>
Add a tabular description of the elements of the view.= span>
A complex view may be subdivided into smaller views.
Views that are related to this view. You may reference a deployment vi= ew for a view on the building blocks here.
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 informat= ion. 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 supp= ressing the representation by a CSS style. Therefore consider this as a con= venience for the reader, not as a security tool.
The text of notes sections is also indexed.
For a document the references section contains pointers to resources tha= t prove the statements of the document.
Often these proofs are not easily distinguishable from further informati= on. In this case you may want to skip the reference section in favour for t= he resource list.
For further information please refer to References and 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 info= rmation in the team's information systems. Anything the reader of the resou= rce might want to know, may be listed here.
For further information please refer to References and Resources.
Components are often= detailed by view documents.
Architecture a= spects are often used together with view documents to describe componen= ts.