cityofaustin/atd-moped

Design Entity Relationship Diagram

Closed this issue · 1 comments

We will create a high-level entity relationship diagram based on initial user interviews, scoped requirements, and the Access DB schema.

Migrated to atd-data-tech #1552

Developed first analysis for checking how often certain data entities are mentioned between Interim Project Database schema and user interviews....not meant to be exhaustive but I figure if an entity isn't mentioned more than once, it's either being referred to by a different name (in which case we can collapse) or perhaps it's specific enough to a workgroup but not necessary for another workgroup: https://docs.google.com/spreadsheets/d/1pDVF6z5tHdtHFqhFTnvROf9FkSgabZbpQxgn53hKz-4/edit?usp=sharing