Date: Fri, 29 Mar 2024 02:43:56 +0100 (CET) Message-ID: <571120904.17609.1711676636940@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17608_522625962.1711676636940" ------=_Part_17608_522625962.1711676636940 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Systems are part of envir= onments where products are deployed to.
Systems are part of environments where products are deployed to.= span>
Systems are configuration items.
The document type it-system provides the following properties:<= /p>
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.
Systems may be composed. This is a reference to the superordinate system= .
The value is typically automatically provided by the parent document.
Specify the type of the system to organize them.
Use the IT System T= ype to define types of systems.
Specify the lifecy= cle phase this system is currently in.
Since 3.3
Since version 3.3 the Name List Macro selects on lifecycle phases that belong t=
o the lifecycle S=
ystem Lifecycle
.
If this does not suite your use case, please update the Where parameter = accordingly.
Specify the version of the application.
Provide the application identifying part of the URI. Is usually appended= to the URI of the system this system is installed to.
Specify the uniform resource identifier (URI) to the system.
This information may be used by the Access Information doctype.
Provide the logical location for the system.
Specify where the system is located.
List documentation assets provided for this system.
List software assets thi= s system depends on.
List assets this system = depends on.
Add links to services= a> this system depends on. Services will be rendered within a document sect= ion.
Add links to systems this system depends on. Systems will be rendered wi= thin a document section.
List configurat= ion items this system depends on to be operational.
Reference the organization that sells the system.
Reference the contact person of the vendor organization to access more i= nformation on the system or related information.
Reference the organization that runs the system.
Reference the contact person of the administration in case of technical = problems.
List of remote information repositories related to the system.
Describe the system.
This section provides subsections to list information on dependencies.= p>
The tables are automatically populated with references provided as value= s to properties. So typically this section is not edited manually. New depe= ndencies are added as a value to the respective property.
List and describe the interfaces provided by this system.
Describe the installation procedure of the system. Use a subsection for = each step. This way you can add screen shots or console output to make thin= gs very easy. Adding this information is hard on lists. If the installation= process is long and complicated, add a checklist or topic as a child docum= ent and refer to it from here. In case the installation is automated, just = help the user to launch the installation process.
Describe the typical or recommended configuration of the system. Again, = use subsections for the individual steps. If the configuration process is l= ong and complicated, add a checklist or topic as a child document and refer= to it from here.
An automatic list of work instructions relevant for running or working w= ith this system.
List of deployments conducted for this system.
If there is a document of type Access Information, this information is automatically r= endered in this section by transclusion.
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.