U bekijkt een oudere versie van deze pagina. Terug naar de laatste versie.
Technical Documentation: verschil tussen versies
(Translation EN) (Label: bewerking met nieuwe wikitekstmodus) |
(Label: bewerking met nieuwe wikitekstmodus) |
BlueSpice is the platform for technical documentation.
External technical documentation | Internal technical documentation | ||
---|---|---|---|
- | Documentation ensures that the product can be safely and properly commissioned, used, maintained and possibly disposed of.
The external documentation is usually created by technical writers and usually translated into the language of each user. Examples of external technical documentation: |
It serves the internal archiving of all product-relevant documents and the obligation to prove compliance with all legal requirements. It can span the entire product lifecycle, from product planning through development, market launch and product monitoring to product discontinuation. Typical components of an internal documentation are: | - |
|
|
Example Pages[bewerken | brontekst bewerken]
You can get a first impression of these possibilities by lookint at the following examples:
BlueSpice is the platform for technical documentation. {| class="wikitable" |+ Wiki as a tool for technical documentation !External technical documentation !Internal technical documentation | - | - |Documentation ensures that the product can be safely and properly commissioned, used, maintained and possibly disposed of. The external documentation is usually created by technical writers and usually translated into the language of each user. Examples of external technical documentation: | It serves the internal archiving of all product-relevant documents and the obligation to prove compliance with all legal requirements. It can span the entire product lifecycle, from product planning through development, market launch and product monitoring to product discontinuation. Typical components of an internal documentation are: | - | width = "50%" | * operating instructions * installation and assembly instructions * service instructions, maintenance and repair instructions * software manuals, user guide and online help * project documentation * product documentation and datasheets * safety instructions / occupational safety * product videos, tutorials, etc. | * specifications * requirements specifications * calculation notes * test reports * risk assessments / risk analyzes * technical drawings * exploded * documents of construction and production, * evidence of quality assurance measures, * disposal. |} <br /> ==Example Pages== You can get a first impression of these possibilities by lookint at the following examples: *[[Electric Pallet Truck Alligator]] *[[Caustic soda]] *[[Coffeemaker]]
Regel 5: | Regel 5: | ||
!External technical documentation | !External technical documentation | ||
!Internal technical documentation | !Internal technical documentation | ||
− | | - | + | |- |
− | | Documentation ensures that the product can be safely and properly commissioned, used, maintained and possibly disposed of. | + | |Documentation ensures that the product can be safely and properly commissioned, used, maintained and possibly disposed of. |
The external documentation is usually created by technical writers and usually translated into the language of each user. Examples of external technical documentation: | The external documentation is usually created by technical writers and usually translated into the language of each user. Examples of external technical documentation: | ||
− | | It serves the internal archiving of all product-relevant documents and the obligation to prove compliance with all legal requirements. It can span the entire product lifecycle, from product planning through development, market launch and product monitoring to product discontinuation. Typical components of an internal documentation are: | + | |It serves the internal archiving of all product-relevant documents and the obligation to prove compliance with all legal requirements. It can span the entire product lifecycle, from product planning through development, market launch and product monitoring to product discontinuation. Typical components of an internal documentation are: |
− | | - | + | |- |
| width = "50%" | | | width = "50%" | | ||
* operating instructions | * operating instructions |