in compliance with applicable laws and regulations 2.3–Engineering Controls: Strict limits should be placed on each phase of data processing lifecycle engaged by the software under development, including: Limiting Collection; Collecting by Fair and Lawful Means; Collecting from Third Parties; Limiting Uses and Disclosures; Limiting Retention; Disposal, Destruction; and Redaction and where they apply to privacy functional requirements and risks. SHALL include software retirement plan from a privacy viewpoint 3. Privacy Embedded into Design 3.1–Holistic and Integrative: Privacy commitments must be embedded in holistic and integrative ways. 3.2–Systematic and Auditable: A systematic approach should be adopted that relies upon accepted standards and process frameworks, and is amenable to external review. 3.3–Review and Assess: Detailed privacy impact and risk assessments should be used as a for design decisions. 3.4–Human-Proof: The privacy risks should be demonstrably minimized and not increase through operation, misconfiguration, or error. The OASIS PMRM Privacy Use Case Template RECOMMENDED for identifying and documenting privacy requirements. SHALL contain description of business model showing traceability of personal data flows for any data collected through new software services under development. SHALL include identification of privacy design principles SHALL contain a privacy architecture SHALL describe privacy UI/UX design SHALL define privacy metrics SHALL include human checklists for software engineering artifacts SHALL include privacy review reports (either in reviewed documents or in separate report) 4. Full Functionality: Positive Sum, not Zero-Sum 4.1–No Loss of Functionality: Embedding privacy adds to the desired functionality of a given technology, process or network architecture. 4.2-Accommodate Legitimate Objectives: All interests and objectives must be documented, desired functions articulated, metrics agreed, and trade-offs rejected, when engineering software solutions. 4.3–Practical and Demonstrable Results: Optimized outcomes treat privacy-as-a-functional requirement (see section XXX), i.e. functional software requirements and privacy requirements should be considered together, with no loss of functionality. SHALL show tests for meeting privacy objectives, in terms of the operation and effectiveness of implemented privacy controls or services.
project members and relevant stakeholders. 6.2–Open to Review: The design and operation of software systems should demonstrably satisfy the strongest privacy laws, contracts, policies and industry norms (as required). 6.3–Open to Emulation: The design and operation of information technologies and systems should be open to scrutiny, improvement, praise, and emulation by others. and other stakeholders for data collection, use, disclosure, and/or elsewhere as applicable SHALL describe any measurements incorporated in the software, or monitoring software, or otherwise to measure the usage and effectiveness of provided privacy options and controls, and to ensure continuous improvement. SHALL describe placement of privacy settings, privacy controls, privacy policy(ies), and accessibility, prominence, clarity, and intended effectiveness. 7. Respect for User Privacy 7.1–Anticipate and Inform: Software should be designed with user/data subject privacy interests in mind, and convey privacy attributes (where relevant) in a timely, useful, and effective way. 7.2–Support Data Subject Input and Direction: Technologies, operations and networks should allow users/data subjects to express privacy preferences and controls in a persistent and effective way. 7.3–Encourage Direct User/Subject Access: Software systems should be designed to provide data subjects direct access to data held about them, and an account of uses and disclosures. SHALL describe user privacy options (including access), controls, user privacy preferences/settings, UI/UX supports, and user-centric privacy model. SHALL describe notice, consent, and other privacy interactions at the EARLIEST possible point in a data transaction exchange with a user/data subject or her/his automated agent(s) or device(s).