The document discusses digital literacy and data modeling. It begins with announcements about completing exercises and signing up for Lynda.com. It then discusses the importance of understanding computer code and data in today's digital world. Various data modeling concepts are introduced like normalization, relationships between tables, and the three normal forms. The goal of normalization is to reduce data anomalies and ensure data integrity. Examples are provided to illustrate the transition from an un-normalized table to first, second, and third normal form through eliminating redundant and unrelated data.

1. BSYS 2060 Lecture 2 – Data Literacy & Data Modeling

2. Agenda
• Announcements
• Digital Literacy
• Data Modeling
• Relationship Types
• Example

3. Bring headphones to all labs from here on in!
Source: CC by 2.0, http://www.flickr.com/photos/bobjudge/3569973941/

4. https://zenportfolios.ca/bcit-bsys-2060-2012/week-0/

5. http://www.lynda.com/

7. Announcements
• If you didn’t already do the “Week 0” exercise, you
should do ASAP!
• Sign up for Lynda.com ASAP
– $21.67 US for duration of semester
– Videos to watch will be assigned shortly after today’s
lecture
– Bring your headphones to all future labs!
• Join the BSYS 2060 group on zenportfolios.ca if you
didn’t already
– Upload an avatar if you didn’t already
– We will start using this online group more in the weeks to
come, especially for the project

8. If you didn’t do this already…
Go to zenportfolios.ca, log-in, click on Groups, search for 2060
Then join the BSYS-2060-2012 group

9. Digital Literacy

10. http://www.nytimes.com/2012/03/28/technology/for-an-edge-on-the-internet-computer-code-gains-a-following.html?pagewanted=all

11. “Inasmuch as you need to know how to read
English, you need to have some
understanding of the code that builds the
Web,” said Sarah Henry, 39, an investment
manager who lives in Wayne, Pa. “It is
fundamental to the way the world is
organized and the way people think about
things these days.”

12. We live in an information age where data is king.

13. Data often most valuable asset of a company
e.g. Aeroplan worth more than Air Canada

14. We live in a data mash-up world.

16. WordPress that uses open source Twitter API / Integration
MySQL database back-end

17. Take control of your data. Best thing is to buy your own domain name
and build your own site and web presence there.
http://jacobjpope.com

18. Where does data belong?

19. Diaspora The average middle aged person has their data spread out over
A 1000 different database locations
Many “fly by
Self-hosted night” Web 2.0
Website apps
containing all
your data
You control You don’t
completely control the
data at all
Not so easy... convenient
Trend is towards you controlling your data

24. Who owns data?

26. Building a database for an organization?

27. What is the organization’s mission?

28. What is the project’s mission?

29. What data is required to make good
decisions or for other reporting needs?

30. What data is currently being collected?

31. How is the data collected being used?

32. What data should be collected?

33. What are the main data entities?
These will become your tables

34. What are the required fields and field data types?

35. What are the relationships between the tables?

36. Select your tools?
e.g. MS Access, MS SQL, MySQL, Oracle
What is being used now if anything?

37. Be careful of
the hammer!
To a hammer, everything
looks like a nail. If you
only know MS Access,
you may see always see
MS Access as the solution
even when it’s not. If you
only know MS Excel, it
seems like the perfect
choice!
Source:
http://www.flickr.com/photos/fixersphotos/3199566032/

38. Normalization
A brief introduction to the first three
forms...

39. “Normalization”
• In the field of relational database design,
normalization is a systematic way of ensuring
that a database structure is suitable for
general-purpose querying and free of certain
undesirable characteristics—insertion, update,
and deletion anomalies—that could lead to a
loss of data integrity.
Codd, E.F. The Relational Model for Database Management: Version 2. Addison-Wesley (1990), p. 271

41. “...insertion, update, and deletion
anomalies...”
Until a Course Code is assigned to this record, it can not
be inserted in the table

42. “...insertion, update, and deletion
anomalies...”
An edit made to one record may not be made to ALL
records for the same employee

43. “...insertion, update, and deletion
anomalies...”
If the Course Code is deleted the information for the
Faculty Member will be lost.

44. Three Normal Forms
• 1NF
– Eliminate repeating groups
– No redundant data
• 2NF
– Eliminate independent data
– All fields depend on Primary Key
• 3NF
– Eliminate dependency on non-key fields
– Fields do not depend on each other

45. Un-Normalized Table (i.e. Excel)

46. First Normal Form (1NF)
0NF – “un-normalized”
1NF

47. Second Normal Form (2NF)
1NF
2NF

48. Third Normal Form (3NF)
2NF
3NF