* What is implied?
* Why are we talking about this in a database class?
* Examples from history?
* Examples from contemporary society?
notes from class :
System is established to gain efficiency/output/input seeking efficiency
Goal: continuously
Common element: data
Development: farming, animal husbandry, specialization of labor, industrial revolution…assembly line…interne
Learning = Competitive Advantage:
Allows for specialization of labor
Emergence of experts
Innovation and process optimization
People become interchangeable resource
Organizations that “learn” will out-perform other organizations that do not
Jun 22, 2022 Lecture 2
Review: Organize or Die – mantra
Scrum is part of organize or die
Hierarchical →
Basic SQL:
Select
From
Where
Order by
Group by
SDLC:
Role of DBMS:
Back-end of N-tier Application
Holds data securely
Presents answers to queries = information
Allows for learning/gaining knowledge
History of database theory:
– File cabinet database → not learning
– Hierarchical database & Network database → complications (redundant data, less efficient system maintenance); corrupted
Biggest difference between is primary key and foreign key
– Relational data model: foreign keys. Less expensive to implement & maintain, less dependent on experts (first person articulated retinol database theory Edgar Codd)
– Easy to understand, able to improve and optimize business processes, easy to obtain information quickly
– Efficiency in data storage and implementation, scalability
No domain violation, Row dependency
Jun 23, 2022 Lecture 3
3-tier: front (presentation), middle (complex, more than 1 layer, 3 tiers by itself), back
SDLC: Systems Development Lifecycle
Planning → Analysis → Design → Build → Maintain
moF – Framework
ITIL – Framework
SDLC – Framework
Waterfall – construction
Lean – created by Toyota (Japanese) revolutionary of making cars (manufacturing)
Agile/scrum – software
ERD → Entity Relationship Diagram, conceptual, logical
Conceptual:
*interview people/research, investigate industry/business organization – existing data, observe processes
→ brainstorming
→ conceptual data diagram
Conceptual relation (row = tuple) = Logical entity (row= record) = Physical table
Column = attribute
Logical Design Phase:
Refining conceptual
Create ERD → ‘blueprint’
Normalization process
Validate transactions
pk/fk
For This or a Similar Paper Click Here To Order Now
