Eight Privacy Principles – from OECD

All people/companies must know these eight privacy principles

PART TWO. BASIC PRINCIPLES OF NATIONAL APPLICATION

Collection Limitation Principle

7. There should be limits to the collection of personal data and any such data should be obtained by lawful and fair means and, where appropriate, with the knowledge or consent of the data subject.

Data Quality Principle

8. Personal data should be relevant to the purposes for which they are to be used, and, to the extent necessary for those purposes, should be accurate, complete and kept up-to-date.

Purpose Specification Principle

9. The purposes for which personal data are collected should be specified not later than at the time of data collection and the subsequent use limited to the fulfilment of those purposes or such others as are not incompatible with those purposes and as are specified on each occasion of change of purpose.

Use Limitation Principle

10. Personal data should not be disclosed, made available or otherwise used for purposes other than those specified in accordance with Paragraph 9 except:

  • a) with the consent of the data subject; or
  • b) by the authority of law.

Security Safeguards Principle

11. Personal data should be protected by reasonable security safeguards against such risks as loss or unauthorised access, destruction, use, modification or disclosure of data.

Openness Principle

12. There should be a general policy of openness about developments, practices and policies with respect to personal data. Means should be readily available of establishing the existence and nature of personal data, and the main purposes of their use, as well as the identity and usual residence of the data controller.

Individual Participation Principle

13. An individual should have the right:

  • a) to obtain from a data controller, or otherwise, confirmation of whether or not the data controller has data relating to him;
  • b) to have communicated to him, data relating to him within a reasonable time;
    at a charge, if any, that is not excessive;
    in a reasonable manner; and
    in a form that is readily intelligible to him;
  • c) to be given reasons if a request made under subparagraphs(a) and (b) is denied, and to be able to challenge such denial; and
  • d) to challenge data relating to him and, if the challenge is successful to have the data erased, rectified, completed or amended.

Accountability Principle

14. A data controller should be accountable for complying with measures which give effect to the principles stated above.

—————————————————–

Above text was copy pasted from http://www.oecd.org/internet/ieconomy/oecdguidelinesontheprotectionofprivacyandtransborderflowsofpersonaldata.htm#guidelines

http://oecdprivacy.org/

http://en.wikipedia.org/wiki/Organisation_for_Economic_Co-operation_and_Development

The Organisation for Economic Co-operation and Development (OECD)

Mind Map

I love mind map to solve many problems.

Today’s Problem: How to see test coverage and test plan in glance?
Answer: Use Mind Map.

http://www.bettertesting.co.uk/content/?p=956

http://www.bettertesting.co.uk/content/?p=253

http://www.xmind.net/download/win/

 

http://freemind.sourceforge.net/wiki/index.php/Main_Page

 

-o-

 

How to build new project from scratch?

Problem Statement: How to build new project from scratch?

Step 1: Get all functional / Non-Functional Requirements.

Step 2: Identify components, communication flows, Users, …etc

Step 3: Prepare number of total requirements, assign numbers and do estimations

This helps to plan for budget, resources, infrastructure, ….etc

Step 4: Define the road map and identify phases to deliver it.

Step 5: Identify Risks and prepare risk management plan.

-o-
This is applicable for both software / non-software projects.

References:

http://www.successfulprojects.com

Road Map Planning: http://www.onedesk.com

Requirements Management: http://products.optimizory.com/rmsis