Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • oss/utilities/requirements-manager
1 result
Show changes
Commits on Source (2)
Hide whitespace changes
Inline Side-by-side
Showing
with 976 additions and 1059 deletions
.envrc 0 → 100644
View file @ 0c922939
source_url "https://raw.githubusercontent.com/cachix/devenv/d1f7b48e35e6dee421cfd0f51481d17f77586997/direnvrc" "sha256-YBzqskFZxmNb3kYVoKD9ZixoPXJh1C9ZvTLGFRkauZ0="
use devenv
\ No newline at end of file
.gitignore
View file @ 0c922939
/deployment/build/
\ No newline at end of file
/deployment/build/
# Devenv
.devenv*
devenv.local.nix
# direnv
.direnv
# pre-commit
.pre-commit-config.yaml
# Devenv
.attach_pid*
/build/
dist
result
.task/
.goreleaser.yml
Taskfile.yaml
.gitlab-ci.yml 0 → 100644
View file @ 0c922939
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
image: docker-registry.schukai.com:443/nixos-ci-devenv:latest
#services:
# - docker:dind
variables:
NIXOS_VERSION: "23.11"
NIXPKGS_ALLOW_UNFREE: "1"
NIXPKGS_ALLOW_INSECURE: "1"
#DOCKER_DRIVER: overlay2
stages:
- tag
- release
# if you want to debug the ci pipeline, uncomment the following lines
#debug:
# tags:
# - nixos
# stage: tag
# script:
# - export
tag-it:
tags:
- nixos
stage: tag
script:
- devenv shell tag-version
rules:
- if: '$CI_COMMIT_TAG'
when: never
- if: '$CI_COMMIT_TAG_MESSAGE =~ /DO_RELEASE/'
when: never
- if: '$CI_COMMIT_MESSAGE =~ /Bump version/'
when: never
- when: on_success
release:
tags:
- nixos
stage: release
rules:
- if: '$CI_COMMIT_TAG_MESSAGE =~ /DO_RELEASE/'
when: on_success
- when: never
variables:
# Disable shallow cloning so that goreleaser can diff between tags to
GIT_DEPTH: 0
script:
- devenv shell deploy-app
#- cd source; goreleaser release --clean
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
.idea/.gitignore
View file @ 0c922939
......@@ -6,3 +6,5 @@
# Datasource local storage ignored files
/dataSources/
/dataSources.local.xml
# GitHub Copilot persisted chat sessions
/copilot/chatSessions
.idea/watcherTasks.xml
View file @ 0c922939
......@@ -25,7 +25,7 @@
<env name="PATH" value="$GoBinDirs$" />
</envs>
</TaskOptions>
<TaskOptions isEnabled="true">
<TaskOptions isEnabled="false">
<option name="arguments" value="-w $FilePath$" />
<option name="checkSyntaxErrors" value="true" />
<option name="description" />
......
README.md
View file @ 0c922939
......@@ -16,7 +16,7 @@ chmod u+x reqman
Or here in a command:
```bash
wget -O ~/.local/bin/reqman http://download.schukai.com/tools/reqman/reqman-$( uname -s | tr [:upper:] [:lower:])-$(echo `uname -m | sed s/aarch64/arm64/ | sed s/x86_64/amd64/`) && chmod u+x ~/.local/bin/reqman
wget -O ~/.local/bin/reqman http://download.schukai.com/tools/reqman/reqman-$( uname -s | tr [:upper:] [:lower:])-$(echo `uname -m | sed s/aarch64/arm64/ | sed s/x86_64/amd64/`) && chmod u+x ~/.local/bin/reqman
```
## Commands
......@@ -25,7 +25,7 @@ wget -O ~/.local/bin/reqman http://download.schukai.com/tools/reqman/reqman-$( u
The date format for the output can be specified with the parameter `--date-format`.
All confirguration values can also be specified in a configuration file.
All confirguration values can also be specified in a configuration file.
The configuration file can be specified with the `--config` parameter.
If no path is specified, the configuration file `config.yaml` is first searched for in the working directory.
......@@ -86,13 +86,13 @@ You can use a complete directory or a subdirectory as the path.
### Output of the tasks
Tasks are used to document open points in the document itself.
Tasks are used to document open points in the document itself.
For example, if a description is still missing or a picture needs to be added.
A task can be defined by the notation `- [ ] task` or `- [] 2022-12-13 task with due date`.
Completed tasks should at best be deleted from the document.
Completed tasks should at best be deleted from the document.
However, they can also be set as completed by writing `[x] 2022-12-13 done task`.
example:
......@@ -100,7 +100,7 @@ example:
```md
- [ ] task 1
- [ ] tast 2
- [x] 2022-12-13 task 3 with due date
- [x] 2022-12-13 task 3 with due date
```
The call is as follows:
......@@ -111,31 +111,30 @@ reqman tasks print --path=examples/
The output is then of the type:
| AUFGABE | BIS | ERLEDIGT | DATEI |
|----------------------|------------|----------|---------|
| AUFGABE | BIS | ERLEDIGT | DATEI |
| -------------------- | ---------- | -------- | ------- |
| task 1 | — | — | file.md |
| tast 2 | — | — | file.md |
| task 3 with due date | 2022-12-13 | ✓ | file.md |
### Output of the items
```bash
reqman requirements print --path examples/ --column ID --column Title
reqman requirements print --path examples/ --column ID --column Title
```
The output is then of the type:
| ID | TITEL |
| ---- | ---------------- |
| A1 | My requirement |
| ID | TITEL |
| --- | -------------- |
| A1 | My requirement |
More columns can be added with `--column`.
### Output of privacy
```bash
reqman privacy print --path=example/
reqman privacy print --path=example/
```
### Output of requirements
......@@ -147,13 +146,13 @@ reqman requirements print --path=example/ --column=ID --column=
The output is then of the type:
| ID | GRUPPE | NAME | TYP | BESCHREIBUNG | BIS | ERLEDIGT | AM | VON | DATEI |
| -------------------- | -------- | -------------------------- | ------ | -------------- | ------------ | ---------- | ------------ | ----- | ---------------------- |
| 23423-Beistellung1 | A1 | Beistellung eines Bildes | Bild | Großes Logo | 2022-12-12 | ✓ | 2022-12-01 | Me | ./req1/002/002-01.md |
| ------------------ | ------ | ------------------------ | ---- | ------------ | ---------- | -------- | ---------- | --- | -------------------- |
| 23423-Beistellung1 | A1 | Beistellung eines Bildes | Bild | Großes Logo | 2022-12-12 | ✓ | 2022-12-01 | Me | ./req1/002/002-01.md |
### Output changelog
```bash
reqman changelog print --path=example/
reqman changelog print --path=example/
```
The output is then of the type:
......@@ -172,50 +171,50 @@ The output is then of the type:
### Output report
```
requirements report --grouped-by ID
requirements report --grouped-by ID
```
This command produces two tables:
| Anforderung | Gesch | TIME SPENT |
| ------------- | ------- | --------- |
| ID1 | 40 | 1 |
| ID2 | 40 | 1 |
| ID3 | 40 | 1 |
| ID4 | 40 | 1 |
| ID5 | 40 | 2 |
| ID6 | 40 | 2 |
| ID7 | 40 | 2 |
| ID8 | 40 | 2 |
| ID9 | 40 | 2 |
| ID10 | 40 | 2 |
| ID11 | 40 | 3 |
| ID12 | 40 | 3 |
| ID13 | 40 | 3 |
| ID14 | 40 | 3 |
| ID15 | 40 | 3 |
| ID16 | 40 | 3 |
| ID17 | 40 | 3 |
| ID18 | 40 | 4 |
| ID19 | 40 | 4 |
| ID20 | 40 | 4 |
| ID21 | 40 | 4 |
| ID22 | 40 | 5 |
| ID23 | 40 | 5 |
| ID24 | 40 | 6 |
| ID25 | 40 | 6 |
1) Groups all estimates and adds up the estimate and the booked times. This allows you to see how much time you have
| ----------- | ----- | ---------- |
| ID1 | 40 | 1 |
| ID2 | 40 | 1 |
| ID3 | 40 | 1 |
| ID4 | 40 | 1 |
| ID5 | 40 | 2 |
| ID6 | 40 | 2 |
| ID7 | 40 | 2 |
| ID8 | 40 | 2 |
| ID9 | 40 | 2 |
| ID10 | 40 | 2 |
| ID11 | 40 | 3 |
| ID12 | 40 | 3 |
| ID13 | 40 | 3 |
| ID14 | 40 | 3 |
| ID15 | 40 | 3 |
| ID16 | 40 | 3 |
| ID17 | 40 | 3 |
| ID18 | 40 | 4 |
| ID19 | 40 | 4 |
| ID20 | 40 | 4 |
| ID21 | 40 | 4 |
| ID22 | 40 | 5 |
| ID23 | 40 | 5 |
| ID24 | 40 | 6 |
| ID25 | 40 | 6 |
1. Groups all estimates and adds up the estimate and the booked times. This allows you to see how much time you have
spent.
| KEY | PLANNED VALUE | TIME SPENT | RATIO |
| :---- | --------------- | ------------ | ------- |
| :-- | ------------- | ---------- | ----- |
| ID1 | 1000 | 75h0m0s | 7.50 |
2) This table shows for each plan value the hours needed, the mean, the variance and the standard deviation.
2. This table shows for each plan value the hours needed, the mean, the variance and the standard deviation.
| PLAN VALUE | TIME SPENT | MEAN | VARIANCE | STANDARD DEVIATION |
| ------------ | ------------ | ------ | ---------- | -------------------- |
| ---------- | ---------- | ---- | -------- | ------------------ |
| 40 | 75h0m0s | 3.00 | 2.08 | 1.44 |
On average, we needed 3 hours in the example.
......@@ -231,24 +230,24 @@ So, what decision can we derive? If a new requirement is estimated at
You can synchronize the issues of a document with a GitLab server.
```bash
reqman gitlab sync --path=example/
```bash
reqman gitlab sync --path=example/
```
If no ID is defined in the document, an issue is created,
```yaml
issues:
- gitlab:
title: "Issue 1"
- gitlab:
title: "Issue 1"
```
otherwise, the data is updated.
```yaml
issues:
- gitlab:
id: 1
- gitlab:
id: 1
```
## Structure
......@@ -280,24 +279,24 @@ If the PDF function is used, LaTeX commands can also be included in the text. Fo
## YAML
| | `>` | `│` | | `"` | `'` | `>-` | `>+` | `│-` | `│+` |
|-----------------------------------|---------|--------|-----|------|-----|-------|--------|--------|--------|
| **Spaces/newlines converted as:** | | | | | | | | | |
| Trailing space → | \_ | \_ | | | | \_ | \_ | \_ | \_ |
| Leading space → | \\n\_ | \\n\_ | | | | \\n\_ | \\n\_ | \\n\_ | \\n\_ |
| Single newline → | \_ | \\n | \_ | \_ | \_ | \_ | \_ | \\n | \\n |
| Double newline → | \\n | \\n\\n | \\n | \\n | \\n | \\n | \\n | \\n\\n | \\n\\n |
| Final newline → | \\n | \\n | | | | | \\n | | \\n |
| Final double newline → | | | | | | | \\n\\n | | \\n\\n |
| **How to create a literal:** | | | | | | | | | |
| Single quote | ' | ' | ' | ' | '' | ' | ' | ' | ' |
| Double quote | " | " | " | \\" | " | " | " | " | " |
| Backslash | \\ | \\ | \\ | \\\\ | \\ | \\ | \\ | \\ | \\ |
| **Other features** | | | | | | | | | |
| In-line newlines with `\n` | 🚫 | 🚫 | 🚫 | ✅ | 🚫 | 🚫 | 🚫 | 🚫 | 🚫 |
| Spaceless newlines with `\` | 🚫 | 🚫 | 🚫 | ✅ | 🚫 | 🚫 | 🚫 | 🚫 | 🚫 |
| `#` or `:` in value | ✅ | ✅ | 🚫 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Can start on same line as key | 🚫 | 🚫 | ✅ | ✅ | ✅ | 🚫 | 🚫 | 🚫 | 🚫 |
| | `>` | `│` | | `"` | `'` | `>-` | `>+` | `│-` | `│+` |
| --------------------------------- | ----- | ------ | --- | ---- | --- | ----- | ------ | ------ | ------ |
| **Spaces/newlines converted as:** | | | | | | | | | |
| Trailing space → | \_ | \_ | | | | \_ | \_ | \_ | \_ |
| Leading space → | \\n\_ | \\n\_ | | | | \\n\_ | \\n\_ | \\n\_ | \\n\_ |
| Single newline → | \_ | \\n | \_ | \_ | \_ | \_ | \_ | \\n | \\n |
| Double newline → | \\n | \\n\\n | \\n | \\n | \\n | \\n | \\n | \\n\\n | \\n\\n |
| Final newline → | \\n | \\n | | | | | \\n | | \\n |
| Final double newline → | | | | | | | \\n\\n | | \\n\\n |
| **How to create a literal:** | | | | | | | | | |
| Single quote | ' | ' | ' | ' | '' | ' | ' | ' | ' |
| Double quote | " | " | " | \\" | " | " | " | " | " |
| Backslash | \\ | \\ | \\ | \\\\ | \\ | \\ | \\ | \\ | \\ |
| **Other features** | | | | | | | | | |
| In-line newlines with `\n` | 🚫 | 🚫 | 🚫 | ✅ | 🚫 | 🚫 | 🚫 | 🚫 | 🚫 |
| Spaceless newlines with `\` | 🚫 | 🚫 | 🚫 | ✅ | 🚫 | 🚫 | 🚫 | 🚫 | 🚫 |
| `#` or `:` in value | ✅ | ✅ | 🚫 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Can start on same line as key | 🚫 | 🚫 | ✅ | ✅ | ✅ | 🚫 | 🚫 | 🚫 | 🚫 |
`│ -> |`
......@@ -308,7 +307,7 @@ depending on the type. The following table provides information about the indivi
The format can be looked up in the first column of the table below.
| Layout | Java notation | C notation | Notes |
| ------------------ | --------------- | ------------ | ---------- |
| ---------------- | ------------- | ---------- | -------- |
| 2006-01-02 | yyyy-MM-dd | %F | ISO 8601 |
| 20060102 | yyyyMMdd | %Y%m%d | ISO 8601 |
| January 02, 2006 | MMMM dd, yyyy | %B %d, %Y | |
......@@ -328,15 +327,14 @@ The format can be looked up in the first column of the table below.
Individual LaTeX commands can be looked up here:
* [tug.ctan.org/info/latex-refsheet/LaTeX_RefSheet.pdf](http://tug.ctan.org/info/latex-refsheet/LaTeX_RefSheet.pdf)
* [www.uni-frankfurt.de/53485609/latexsheet.pdf](https://www.uni-frankfurt.de/53485609/latexsheet.pdf)
* [www.latex4ei.de/downloads/LaTeX_CheatSheet.pdf](https://www.latex4ei.de/downloads/LaTeX_CheatSheet.pdf)
* [download.schukai.com/tools/reqman/](http://download.schukai.com/tools/reqman/)
- [tug.ctan.org/info/latex-refsheet/LaTeX_RefSheet.pdf](http://tug.ctan.org/info/latex-refsheet/LaTeX_RefSheet.pdf)
- [www.uni-frankfurt.de/53485609/latexsheet.pdf](https://www.uni-frankfurt.de/53485609/latexsheet.pdf)
- [www.latex4ei.de/downloads/LaTeX_CheatSheet.pdf](https://www.latex4ei.de/downloads/LaTeX_CheatSheet.pdf)
- [download.schukai.com/tools/reqman/](http://download.schukai.com/tools/reqman/)
## Change Log
- Version 1.0
- Bug fixes
- Bug fixes
- Added support for `gitlab sync` command
- initial release
\ No newline at end of file
- initial release
application/web/index.html deleted 100644 → 0
View file @ 22c572c9
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/css/bootstrap.min.css" rel="stylesheet"
integrity="sha384-EVSTQN3/azprG1Anm3QDgpJLIm9Nao0Yz1ztcQTwFspd3yD65VohhpuuCOmLASjC" crossorigin="anonymous">
<style>
body {
background-color: #ffffff;
}
</style>
<title>Download Portal schukai GmbH</title>
</head>
<body>
<div class="d-flex flex-column align-items-center justify-content-center"
style="height:100vh;">
<div class="text-center">
<a href="https://www.schukai.com" class="text-decoration-none text-white text-decoration"><img
src="https://cdn.alvine.io/image/logo/schukai-rot.svg" width="300px"></a>
<br>
<div class="card mt-5">
<div class="card-header">
ReqMan
</div>
<ul class="list-group">
<li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-386">reqman-linux-386</a></li>
<li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-amd64">reqman-linux-amd64</a></li>
<li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-arm">reqman-linux-arm</a></li>
<li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-arm64">reqman-linux-arm64</a></li>
<li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-windows">reqman-windows</a></li>
</ul>
</div>
<p class="mt-5">
<a href="https://about.schukai.com/de/impressum/" class="text-decoration-none text-decoration"
style="color:#c10000">Imprint</a></p>
</div>
</div>
<!--
<div class="d-flex flex-column align-items-center justify-content-center"
style="height:100vh;">
<div class="d-block">
<div><img src="signet.svg" height="10%"></div>
<div>
</div>
</div>
</div>
<div class="text-center mb-2 fixed-bottom">
<div class="row">
<div class="col">
</div>
</div>
</div> -->
<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/js/bootstrap.bundle.min.js"
integrity="sha384-MrcW6ZMFYlzcLA8Nl+NtUVF0sA7MsXsP1UyJoMp4YLEuNSfAP+JcXn/tWtIaxVXM"
crossorigin="anonymous"></script>
</body>
</html>
deployment/scripts deleted 100644 → 0
View file @ 22c572c9
deployment/upload.sh deleted 100644 → 0
View file @ 22c572c9
#!/bin/bash
# shellcheck shell=bash
$(command -v aws) s3 ls --recursive s3://doc.alvine.io/de/ --region eu-central-1 > "$(THIS_DIR)s3-temp/inventory.txt"
\ No newline at end of file
development/examples/example1/1425.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation:
# The time required for this requirement
......@@ -41,66 +41,62 @@ Created: 2022-06-18
Last Update: null
# The issues that are associated with this requirement
Issues:
- Title: null
URL: null
- Title: null
URL: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -108,38 +104,34 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
{{ if .Purposes }}**{{ .Purposes }}** {{ end }}**({{ .ID }})**
{{ if .Purposes }}**{{ .Purposes }}** {{ end }}**({{ .ID }})**
{{ if .Description }} {{ .Description }}
{{ end }}
| | |
| | |
|-----------------------|----------------------------|
| Category | {{ .Category }} |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/144444.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation:
# The time required for this requirement
......@@ -42,7 +42,7 @@ Last Update: null
# The issues that are associated with this requirement
# You can add an issue by adding a new line to the list with the following format:
# - ID: <issue-id>
#
#
# if the issue is not yet in the project, you can add it by using the following format:
# Only the Title is required.
# - GitlabIntern:
......@@ -53,69 +53,65 @@ Last Update: null
# - Assignee: <issue-assignee>
# - Milestone: <issue-milestone>
# - Labels: <issue-labels>
#
#
# Issues:
# - GitlabIntern:
# - ID: <issue-id>
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -123,38 +119,34 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
{{ if .Purposes }}**{{ .Purposes }}** {{ end }}**({{ .ID }})**
{{ if .Purposes }}**{{ .Purposes }}** {{ end }}**({{ .ID }})**
{{ if .Description }} {{ .Description }}
{{ end }}
| | |
| | |
|-----------------------|----------------------------|
| Category | {{ .Category }} |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/req1/1/test1.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 13
# The time required for this requirement
......@@ -41,88 +41,87 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
Issues:
- Gitlab:
ID: 1
Title: demo
Status: closed
Labels:
- bug
- enhancement
- feature
URL: https://gitlab.schukai.com/oss/utilities/requirements-manager/-/issues/1
- Gitlab:
ID: 47
Title: Test 15
Description: |-
Lorem Ipsum Lila Rot
Blau1 Lila Rot Blau2
```
a=4
```
Status: closed
Labels:
- bug
- bugfix
URL: https://gitlab.schukai.com/oss/utilities/requirements-manager/-/issues/47
- Gitlab:
ID: 1
Title: demo
Status: closed
Labels:
- bug
- enhancement
- feature
URL: https://gitlab.schukai.com/oss/utilities/requirements-manager/-/issues/1
- Gitlab:
ID: 47
Title: Test 15
Description: |-
Lorem Ipsum Lila Rot
Blau1 Lila Rot Blau2
```
a=4
```
Status: closed
Labels:
- bug
- bugfix
URL: https://gitlab.schukai.com/oss/utilities/requirements-manager/-/issues/47
...
### {{ .Title }} - {{ .ID }}
Lorem isum dolor[^1] sit ametp, consttrapsile,ssddi dnu tiee icagrem numy emd teonpo inirvoiunt mutrlaor e dloedao b mtergna aliquyamerat sed diam volupt ua. At ,vero eos eaccusam et justo du dlores et ea rbu. Ste clita kasd gubet re, noe takiata santus est Loreme ipms. orem ipsumr gdnolor iat amet, mconsteturoc sadpscingeir, sdili etats o muam nnumy eirmo tempr ssnidu ut labeetdogna aloquym ierat, sed d ilamvoledu ptdmua. oero oeos edsa et jso diuov dolnotres eteoar re buoeema rilam. Ste clita kasd gubegt ren, o seat takimar vtAtactus ccutmtLotoempsumdlositam et. Lorempsum olor st aet, cotnsetetur sadipcing elirtr, sd dnm nonum emodmr i nidnaes t lr io oeretd adgna aliquyamea lrcartpvtu iloeimda uind mapeo dou ts A,te slro o reo ur abu ts suLoje tyeaimesca e oeoevts .utuovmai ds tr ea rebum. tetS clt kaidasu berggnre, onse a tkimataa sactns uste Lreoms ipum dol osrtai etm.
Lorem isum dolor[^1] sit ametp, consttrapsile,ssddi dnu tiee icagrem numy emd teonpo inirvoiunt mutrlaor e dloedao b mtergna aliquyamerat sed diam volupt ua. At ,vero eos eaccusam et justo du dlores et ea rbu. Ste clita kasd gubet re, noe takiata santus est Loreme ipms. orem ipsumr gdnolor iat amet, mconsteturoc sadpscingeir, sdili etats o muam nnumy eirmo tempr ssnidu ut labeetdogna aloquym ierat, sed d ilamvoledu ptdmua. oero oeos edsa et jso diuov dolnotres eteoar re buoeema rilam. Ste clita kasd gubegt ren, o seat takimar vtAtactus ccutmtLotoempsumdlositam et. Lorempsum olor st aet, cotnsetetur sadipcing elirtr, sd dnm nonum emodmr i nidnaes t lr io oeretd adgna aliquyamea lrcartpvtu iloeimda uind mapeo dou ts A,te slro o reo ur abu ts suLoje tyeaimesca e oeoevts .utuovmai ds tr ea rebum. tetS clt kaidasu berggnre, onse a tkimataa sactns uste Lreoms ipum dol osrtai etm.
[^1]: Das ist eine Fussnote
......@@ -131,12 +130,13 @@ Lorem isum dolor[^1] sit ametp, consttrapsile,ssddi dnu tiee icagrem numy emd t
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
......@@ -144,6 +144,7 @@ Lorem isum dolor[^1] sit ametp, consttrapsile,ssddi dnu tiee icagrem numy emd t
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
......@@ -151,17 +152,16 @@ Lorem isum dolor[^1] sit ametp, consttrapsile,ssddi dnu tiee icagrem numy emd t
{{ if .Description }} {{ .Description }}
{{ end }}
| | |
| | |
|-----------------------|----------------------------|
| Category | {{ .Category }} |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
## Level 2
test
......@@ -178,4 +178,4 @@ test
test
@todo das ist ein todo
\ No newline at end of file
@todo das ist ein todo
development/examples/example1/req1/1/test2.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/req1/1/test3.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: XXX
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: XXX
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/req1/1/test4.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/req1/2/test1.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/req1/2/test2.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/req1/2/test3.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/req1/2/test4.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
development/examples/example1/req1/2/test5.md
View file @ 0c922939
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}