ISYS2120: Data and Information Management

University of Sydney 2025 S2
In Progress
logo
DBMS
RelationalModel
SQL
Normalization
Transactions
Security
OLAP

Intro to conceptual, logical, and physical database design with emphasis on integrity constraints and normalization; querying and updating data with SQL; application use of a relational DBMS; transaction management; plus an overview of data warehousing and OLAP.

Learning Outcomes

  • DBMS concepts & roles: Understand what a DBMS is, how it differs from other ways to store/share data, its role in organisations, and typical DBMS tasks.
  • Relational model fundamentals: Relate relational data to real-world facts (and vice versa), and know the benefits and limitations of the relational approach.
  • SQL with integrity: Work with data in an RDBMS: read table definitions and integrity constraints; extract and modify information using SQL queries.
  • Schema design & normalization: Design a suitable schema from a domain: build a conceptual model, produce a relational schema with constraints, apply normalization to evaluate or improve it.
  • Apps & architecture: Explain how application software uses a relational DBMS and compare basic architectural alternatives for data-driven applications.
  • Security & privacy controls: Understand goals, threats, and protection techniques: SQL views, access control, integrity constraints, and stored procedures.
  • Internals for performance: Grasp DBMS implementation concepts affecting quality/performance, including query processing, index structures, and transactions.
  • Theory ↔ Platforms: Connect general database concepts to both abstract theory and details of specific software platforms.
  • Teamwork: Work effectively in teams with members whose skills and interests differ.

Takeaways

This course significantly reshaped the way I think about data as a system rather than just a resource. Through learning conceptual, logical, and physical database design, I developed the ability to translate complex real-world domains into structured data models and to reason about how facts, entities, and relationships should be represented to support long-term correctness and scalability. Working with SQL in the presence of integrity constraints helped me understand how databases actively enforce business rules, rather than simply storing information, while normalization provided a rigorous framework for evaluating and improving schema quality. Beyond schema design, the course deepened my understanding of how applications interact with relational DBMSs, including architectural trade-offs, transaction management, concurrency, and recovery, which clarified why certain design decisions have major implications for reliability and performance. Topics such as security, access control, and privacy further highlighted the importance of designing data systems that are not only functional but also trustworthy and resilient. Finally, the exposure to database internals, data warehousing, and OLAP connected foundational theory with modern analytical and enterprise platforms, giving me a more holistic perspective on how operational databases, analytical systems, and downstream data and AI applications fit together in practice.