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
Select Git revision
  • master
  • 0.1.0
  • 0.1.1
3 results

Target

Select target project
  • oss/utilities/requirements-manager
1 result
Select Git revision
  • master
  • 0.1.0
  • 0.1.1
3 results
Show changes
Expand all Hide whitespace changes
Inline Side-by-side
Showing
with 1913 additions and 1282 deletions
development/examples/example1/req1/2/test6.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/3/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/3/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/3/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/3/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/3/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 }}
development/examples/example1/req1/3/test6.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/3/test7.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/4/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/4/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/4/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 }}
devenv.lock 0 → 100644
View file @ 0c922939
This diff is collapsed.
devenv.nix 0 → 100644
View file @ 0c922939
This diff is collapsed.
devenv.yaml 0 → 100644
View file @ 0c922939
inputs:
nixpkgs:
url: github:nixos/nixpkgs/nixos-23.11
version:
url: git+https://gitlab.schukai.com/oss/utilities/version.git
flake: true
flake.lock 0 → 100644
View file @ 0c922939
{
"nodes": {
"nixpkgs": {
"locked": {
"lastModified": 1710695816,
"narHash": "sha256-3Eh7fhEID17pv9ZxrPwCLfqXnYP006RKzSs0JptsN84=",
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "614b4613980a522ba49f0d194531beddbb7220d3",
"type": "github"
},
"original": {
"id": "nixpkgs",
"ref": "nixos-23.11",
"type": "indirect"
}
},
"root": {
"inputs": {
"nixpkgs": "nixpkgs"
}
}
},
"root": "root",
"version": 7
}