[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: PbD-SE WD 04 Revision 3 Section 1
Further requests for clarification and comments to address TC’s edits and comments in Section 1:
Stuart: Page 5, please can you explain why we may need to clarify “ beyond user/data subject preferences”?
Jonathan: I intend to add text and an edited diagram to illustrate how the Privacy by Design Use Case Template can be adapted for agile methodology and user stories. So the “however” is not needed. I have suggested to John that we can rename it to the Privacy Use Template so that agile methodologists do not feel that the PbD-SE spec is not applicable to them.
John: We may leave a few further details about the PMRM to Section 5 without loss to the PbD-SE introduction. I left in the PMRM reference as normative as you correctly stated that the PbD-SE WD asserts that Privacy Use Template is RECOMMENDED for embedding privacy requirements in a Privacy Use Case or User Story, then the Normative designation for PMRM is appropriate as the accessible Privacy Use Template is based on the more comprehensive PMRM methodology.
Fred: I added goals in section 1 but also left in requirements as software engineers interests in this document are for privacy requirements and the documentation required by PbD.
Sander and Colin: There are normative references to section 5 in Table 4.1. e.g. to the Privacy Use Template that provides documentation in itself. There will be more explicit linking of software engineering documentation, or spec asks for “equivalent” documentation across Sections 3, 4, and 5.
Attachment:
pbd-se-v1_0-wd04 R3 - Section 1.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]