Skip to content
Snippets Groups Projects
Verified Commit d3a3be22 authored by Volker Schukai's avatar Volker Schukai :alien:
Browse files

chore: commit save point

parent db0bf9b1
No related branches found
No related tags found
No related merge requests found
Show whitespace changes
Inline Side-by-side
Showing
with 1077 additions and 1468 deletions
application/source/issues.go
+ 1
− 8
View file @ d3a3be22
......@@ -184,9 +184,8 @@ func syncTasksWithGitlab(config *Configuration) error {
return err
}
encoder.Close()
fmt.Println(filename)
text := buf.String()
text := "---\n" + buf.String() + "\n...\n"
text += pd.OriginText
info, err := os.Stat(filename)
......@@ -204,9 +203,3 @@ func syncTasksWithGitlab(config *Configuration) error {
return nil
}
//func replaceYaml(filename string, yaml *yaml.YAML) error {
// buf := new(bytes.Buffer)
// var encoder = yaml.NewEncoder(buf)
// err, pageData := collectStructureFromFiles(config.Path)
//}
development/examples/example1/1425.md
+ 59
− 80
View file @ d3a3be22
---
ID: 1425
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,25 +29,20 @@ 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),
# 8, 13, 20, 40, 100
Estimation:
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent:
# who is the source of the demand
Source: null
Created: 2022-06-18
Last Update: null
# The issues that are associated with this requirement
Issues:
- Title: null
URL: null
# the individual items as a list
Items:
- ID: null
......@@ -69,34 +56,26 @@ Items:
# 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
......@@ -105,23 +84,23 @@ Privacy:
# 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
......
development/examples/example1/144444.md
+ 57
− 77
View file @ d3a3be22
---
ID: 144444
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation:
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent:
# who is the source of the demand
Source: null
Created: 2022-06-19
Last Update: null
# The issues that are associated with this requirement
# You can add an issue by adding a new line to the list with the following format:
# - ID: <issue-id>
......@@ -83,34 +71,26 @@ Items:
# 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
......@@ -119,23 +99,23 @@ Privacy:
# 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
......
development/examples/example1/req1/1/test1.md
+ 64
− 87
View file @ d3a3be22
---
ID: ID1-1
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 13
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 2h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
Issues:
- Gitlab:
ID: 1
......@@ -60,9 +48,6 @@ Issues:
Labels:
- a
- b
# the individual items as a list
Items:
- ID: null
......@@ -76,34 +61,26 @@ Items:
# 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
......@@ -112,17 +89,14 @@ Privacy:
# 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
......@@ -130,6 +104,9 @@ Privacy:
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......
development/examples/example1/req1/1/test2.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-2
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 1h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/1/test3.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-3
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 1h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: XXX
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/1/test4.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-4
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 1h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/2/test1.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-5
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 2h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/2/test2.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-6
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 2h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/2/test3.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-7
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 2h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/2/test4.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-8
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 2h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/2/test5.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-9
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 2h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/2/test6.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-10
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 2h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/3/test1.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-11
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 3h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/3/test2.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-12
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 3h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/3/test3.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-13
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 3h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/3/test4.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-14
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 3h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/3/test5.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-15
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 3h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/3/test6.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-16
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 3h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
development/examples/example1/req1/3/test7.md
+ 56
− 76
View file @ d3a3be22
---
ID: ID1-17
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
# First and last name of the authors as a list
Author:
- 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.),
......@@ -28,7 +21,6 @@ Author:
# 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
Complexity: null
# Low, Medium, Hi
......@@ -37,20 +29,16 @@ 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),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 3h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
......@@ -64,34 +52,26 @@ Items:
# 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
......@@ -100,23 +80,23 @@ Privacy:
# 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
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment