Commit 2887f0bb authored by Cornelius Schumacher's avatar Cornelius Schumacher
Browse files

Create application documents from template

parent bc108fda
# Annex 1: Information and compliance with the criteria
## Submitter Info
### Applicant
### Distributor (label user)
### Brand / trade name
### Product designation
### Product description
## Minimum system requirements
### Minimum processor architecture incl. generation
### Minimum local working memory required (MByte)
### Minimum local permanent storage required (MByte)
### Requirements for other software
### The required external services that are not available on the reference system
### The required additional hardware
## Hardware utilisation and electrical power consumption in idle mode
### Average processor utilisation in idle mode (%)
### Average working memory utilization in idle mode (Mbyte)
### Average permanent storage utilization in idle mode (MByte/s)
### Average bandwidth utilization for network access in idle mode (Mbit/s) (only contains the additional load, not the percentage share of the base load)
### Average electrical power consumption (net) (W)
## Hardware utilisation and energy demand when running a standard usage scenario
### Processor utilisation (%*s)
### Working memory utilisation (MByte*s)
### Permanent storage utilisation (reading and writing) (MByte/s*s
### Volume of data transferred for network access (Mbit/s*s)
### Average energy demand (net) (Wh)
## 3.1.2.1: Backward compatibility
### Calendar year
# Annex 2: Measurement
Info collected in spreadsheet file
## Details of the analysed product
### Product
### Version
### Manufacturer
### Software class (architecture)
## Measurement information
### Date of the measurement
### Details of the person who performed the measurement
#### Name
#### Mail
#### Other
### Institute ###
#### Designation
#### Address
#### Website
#### Other
### Notes
## Technical details of the measurement
### Measuring instrument
### Sampling frequency
### Length of the scenario
### Sample size
## Information on the reference system
### Reference system year (see Award Criteria, Annex D)
### Model
### Processor
### Cores
### Clock speed
### RAM
### Hard disk (SSD / HDD)
### Graphics card
### Network
### Cache
### Mainboard
### Operating system
## Information on the software stack (measuring system)
### Information
## Standard use case scenario
### Info
#### Software (Name)
#### Produktgruppe (z.B. Textverarbeitung)
#### Stand (Datum)
#### Bezeichnung
#### Autoren 
#### Softwareklasse
#### SUT
#### Lastgenerator
#### Prerequisites
#### Procedure
#### At the end of the measurement
# Annex 4: Data formats
## 3.1.3.1: Data formats
### Requirements
* Disclosure of data formats
* Submitting the manuals or technical data sheets in which the data formats are documented **_or_**
* Providing examples of other software products (from other suppliers) that can process these data formats **_or_**
* Stating the data formats and assigning them to an open standard.
### Documentation of data formats
# Annex 5: Open standards
## 3.1.3.2: Transparency of the software product
### Requirement
* The APIs should correspond to open standards.
## Documentation
*Interface documentation, permalink to the software source code on a source code management platform, software licences or similar*
# Annex 6: Product information
## 3.1.3.3: Continuity of the software product
### Requirements
* Security updates must be provided free of charge
* Security updates for the labelled product for at least 5 years after the end of sale
* The user must be given the option of whether to install only security updates or also other (e.g. functional) updates.
### Product information in which fullfilement of requirements is documented
## 3.1.3.4: Uninstallability
### Requirement
* Residue-free uninstallability of the software
### Product information in which fullfilement of requirements is documented
## 3.1.3.5: Offline capability
### Requirement
* The functionality and availability of the software must not be negatively influenced by external factors, such as the availability of a licence server.
### Product information in which fullfilement of requirements is documented
## 3.1.3.6: Modularity
### Requirements
* Information on how individual modules of the software product can be deactivated during the installation process.
* Information on the extent to which individual modules of the software product (especially those that do not belong to the functions of the software product such as tracking, etc.) can be deactivated during the use of the software product.
### Product information in which fullfilement of requirements is documented
## 3.1.3.8: Documentation of the software product, licence conditions and terms of use
### Requirement
Information about the software product both publicly and also in combination with the product itself:
a) Description of the processes for installing and uninstalling the software
b) Description of the data import and export processes
c) Information on reducing the use of resources
d) Information on the licensing terms and terms of use to enable, where relevant, the legally compliant further development of the software product
e) Information on software support
f) Information on the handling of data, in the sense of existing data protection laws
g) Information on data security, data collection and data transmission
### Product information in which fullfilement of requirements is documented
## 3.2.1: Requirements for the further development and update of the product
### Requirement
If the product is changed (e.g. through updates), it must be ensure that the software product still complies with all of the criteria.
### Product information in which fullfilement of requirements is documented
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment