Loading ist210..

Deliverable

CONCEPTUAL version of your diagram

• With LESS detail, human readable names / connections
• Make it easier to convey to management
• Remove detail from your diagram and refine naming
• Think about how this could translate to a form / app for entry

PHYSICAL version of your diagram

• More accuracy in field names
• Which field is the relationship established on
• Use the Table style to for representing entities
• Add in proposed data types, length of values, NULL / NOT NULL?
• Create example Tuples using this diagram (Excel is fine)

Blog post

• Read and react to the article from our detour today

https://techcrunch.com/2020/08/19/coronavirus-albion-security-flaws-app/

• Questions:

• Is this intrusive or necessary?

• Would you accept this here?

• Is privacy of data more valuable than safety?

• Envision more ethical ways of solving this issue with tech?

Video

• Explain your conceptual diagram to a manager

• What do they need to care about to “sell” this solution

• Don’t explain fields, explain conceptually why these things relate together

• In your physical data model explain..

• PK and FK relationships throughout

• Attribute types. Differences in data type, justify reasoning

• Show examples tuples for each entity

Submission

• Embed your screen cast in the bottom of your blog post

• Embed your diagrams in the bottom of your blog post

• Diagrams.net allow publishing or loading as a jpg

• Submit a link to your article in #lab3-er-diagram-detail channel on Slack

• This is due by Sunday at 11:59pm