Data for Computer Sciences
Data and software engineering cover how real applications store information and how teams build them reliably. Databases introduce the relational model, SQL, normalisation and transactions. Software engineering adds version control, requirements, testing, design and the processes used to deliver code that others can maintain. Both turn algorithm knowledge into working products.
Stage: Data and Theory · Part of the Computer Science roadmap · Last reviewed 19 November 2026
What to learn in Data
- Design a normalised relational schema with primary and foreign keys
- Write SQL queries with joins, grouping and filtering
- Explain what the ACID properties guarantee in a transaction
- Use Git branches and pull requests to collaborate on code
- Write unit tests that check a function's behaviour and edge cases
Data interview questions
What is database normalisation and why do it?
Normalisation organises tables to reduce redundancy and update anomalies, by moving repeated facts into separate tables linked by keys. Following forms such as 1NF, 2NF and 3NF means each fact is stored once, so edits stay consistent. Some systems denormalise later for read speed.
What does ACID stand for in databases?
Atomicity means a transaction happens fully or not at all. Consistency means it moves the database between valid states. Isolation means concurrent transactions do not see each other's partial work. Durability means committed data survives crashes. Together they make transactions safe to rely on.
Where Data fits in the Computer Science roadmap
Data belongs to the Data and Theory stage (intermediate level), which takes about 53 hours. Higher-level ideas.
Other units in this stage
Back to the full Computer Science roadmap