Development Architecture blog is designed for developers who have some troubles in their code.
This blog will be mainly on web development, though many of it's posts can be used also on software design.
I wish you nothing but the best,
Privacy and security issues in terms of ownership of data
Privacy and/or security
issues are inherent in large databases. Who owns the data about a particular
person: medical, credit, personal, financial, consumer information, etc.?
Support your position.
database is specialized to manage and handle data in a computer application
system. Data can be stored in many forms, like text, symbols, digital, images,
graphics, and even sound. Various sectors like government, public security,
finance, medical, energy, business, taxation, transportation, social,
education, corporate and other sectors have formed their own databases application
systems to store large amounts of information in the database, to handle and
use, in order to lead the society into this information era. With the advance
in internet applications, databases have a greater role to play (Ji 2011).
further goes on to say that while development of these database applications
systems has brought about social development and progress, it has also created
issues of security and privacy of the stored data. The potential safety hazards
for large databases are great, owing to their universality. One example is a
hospital database where illegal invasion leads to stealing of numerous
patients’ private information.
the question is who owns this data? Who is responsible for it? Data ownershipmeans both possession of and
responsibility for the data. Ownership refers to power and control both. (Loshlin
2001).Telling the consumer that he "owns" his corporate data is very
dangerous. If he tries to exercise his "rights" of ownership it could
have disastrous repercussions on the enterprise and its data. The term
"stewardship" is a better term to explain this. It involves a broader
responsibility and here where the user must consider the consequences of changing
"his" data (Scofield 1998).
about medical data? Who owns it? There was never a doubt when it was about
paper records. It was mainly the clinicians and insurers who owned the medical
records. But with the development of electronic health information, it becomes
problematic. The law gives patients the rights of privacy and access to their
own records but federal and state laws do not give property rights to patients.
Patients do not have the right to solely possess or destroy their original records
(Hall & Schulman 2009)
the enforcement of laws like Health Insurance Portability and Accountability
Act (HIPAA) and requirements of Sarbanes Oxley (SOX) auditors, organizations
are beginning to realize the importance of securing their data properly .First
of all, the data is classified into private, company confidential, company
restricted,and public. This
classification of data is done by the owner. Here the owner is the director or
head of the organization. For a financial organization it may be the CFO.
data owner is responsible for setting up a policy so that only authorized
people can access and see the data. The data owner must also determine who has
access to the data; how the data should be kept secure, for how long the data
must be retained, what the appropriate disposal methods are, and whether the
data should be encrypted.(Woodbury
is a complicating issue. What information should remain private, and in what
situations? Consider credit information. When someone applies for a credit card
it is considered private information, although in order to receive that credit,
a credit bureau is consulted. At that point, the fact that the credit card
application has been taken is now added to the credit record.
says that appropriate data ownership and data classification are key elements
in an organization’s security policy. Without these, it will be difficult to
implement a security policy. An organization, be it finance, medical, credit,
or consumer related, will not be able to meet the regulatory and internal
requirements regarding access control for its data, without this.
·Hall, M.A. and Schulman, K.A. (2009). Ownership of
Medical Information. The Journal of the
American Medical Association, 301 (12), p. 1282-1284.
·Ji, J. (2011). Security
Issues with Databases [Online]. Available at:
Protecting personal data can be overwhelming, but it is not impossible. There are highly secure tools both online and offline to protect personal data. Shielding personal data can be logical, highly secure as well as inexpensive. Protecting Personal Data Offline Physically lock your financial records and personal documents in a safe place in your home. Purchase an inexpensive fire-proof safe that can be stored in a secure closet, built in your floor or wall. A good fireproof safe costs from $100 to $3000 (Sears, 2013). Protect your wallet and or purse in a desk drawer at work. Limit what you carry when you go out. Never keep your social security card in your wallet; lock it up. When filling out forms in the workplace, the doctor’s office, or your child’s school ask how your information will be safeguarded. If you do not have to fill out every little detail of your life, leave that portion blank. Ask for the consequences of not providing specific information. Shr
Behavior Driven Development, Test Driven Development, and Everything Between What is TDD (Test Driven Development) Test Driven Development was introduced by Kent Beck, in 2003. This followed the concepts of Extreme Programming, introduced in 1999 with a development experiment done by both IBM and Microsoft. The purpose of the Test Driven Development is to make sure code is clear, tested, and as redundant as possible, by making sure the tests are written first, and code is being added to "fill the blanks". Every code iteration needs to pass all tests (may those be unit tests, integration tests, data integrity tests, or UI tests). Writing the tests first allow us to see what fails, how, and allow us to visualize the structure of our code, by making sure each test is performed to test a specific, extremely defined sub-section of a feature. Let's assume a "BasicMaths" class, to perform simple mathematics operations. [TestClass] public class Uni