33:I[196793,["/_next/static/chunks/1xyh1u_ku6jw-.js?dpl=nogit-1791882788","/_next/static/chunks/2_6olli-sutu3.js?dpl=nogit-1791882788","/_next/static/chunks/1qp4g--o6-1vf.js?dpl=nogit-1791882788","/_next/static/chunks/0psy-n5us57a4.js?dpl=nogit-1791882788","/_next/static/chunks/3mz725-y91ph6.js?dpl=nogit-1791882788","/_next/static/chunks/2x_dbpl3b_l2r.js?dpl=nogit-1791882788","/_next/static/chunks/0nojijad0occ8.js?dpl=nogit-1791882788","/_next/static/chunks/19ua1o9n5v3ho.js?dpl=nogit-1791882788","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1791882788","/_next/static/chunks/3yfg2hrj9oxbd.js?dpl=nogit-1791882788","/_next/static/chunks/35s1d7gs3nyqk.js?dpl=nogit-1791882788","/_next/static/chunks/38w1x0vrld4-w.js?dpl=nogit-1791882788","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1791882788","/_next/static/chunks/3kzt2piec6aoa.js?dpl=nogit-1791882788","/_next/static/chunks/2lsi6eli88uwt.js?dpl=nogit-1791882788","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1791882788","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1791882788","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1791882788","/_next/static/chunks/36r9y5g_s4k64.js?dpl=nogit-1791882788","/_next/static/chunks/40lyu17d590zu.js?dpl=nogit-1791882788","/_next/static/chunks/2g-t2n9ahs3tn.js?dpl=nogit-1791882788","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1791882788","/_next/static/chunks/44w2c3xxfw4wd.js?dpl=nogit-1791882788","/_next/static/chunks/16jtsbm2g52s0.js?dpl=nogit-1791882788","/_next/static/chunks/05mo4k9k-ry1n.js?dpl=nogit-1791882788","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1791882788","/_next/static/chunks/2eanemqjnv2vr.js?dpl=nogit-1791882788","/_next/static/chunks/2f3ohq_f1uov2.js?dpl=nogit-1791882788","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1791882788","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1791882788","/_next/static/chunks/0qeo40bqomvxa.js?dpl=nogit-1791882788","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1791882788","/_next/static/chunks/1coblm1-go81_.js?dpl=nogit-1791882788","/_next/static/chunks/27ftpb6yvr6lz.js?dpl=nogit-1791882788","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1791882788","/_next/static/chunks/1o4x0l2qh0ta-.js?dpl=nogit-1791882788","/_next/static/chunks/3it1o0ex-l5qz.js?dpl=nogit-1791882788","/_next/static/chunks/2gqripb6ybmw9.js?dpl=nogit-1791882788","/_next/static/chunks/2l63yczi1z2qz.js?dpl=nogit-1791882788","/_next/static/chunks/075i0tnxt4not.js?dpl=nogit-1791882788","/_next/static/chunks/1eyu-5752jh17.js?dpl=nogit-1791882788","/_next/static/chunks/1of_-ow2iz1cj.js?dpl=nogit-1791882788","/_next/static/chunks/3ybwgs28on6c8.js?dpl=nogit-1791882788","/_next/static/chunks/13gj59kzq50t_.js?dpl=nogit-1791882788","/_next/static/chunks/1986062z5zb0v.js?dpl=nogit-1791882788","/_next/static/chunks/0uitbylhcd4am.js?dpl=nogit-1791882788","/_next/static/chunks/0wv8cpdr6cvhr.js?dpl=nogit-1791882788","/_next/static/chunks/06b61oz__qen3.js?dpl=nogit-1791882788","/_next/static/chunks/0a4x2f2g83l7b.js?dpl=nogit-1791882788","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1791882788","/_next/static/chunks/3q5gc8lbwr4b4.js?dpl=nogit-1791882788","/_next/static/chunks/0dspbdeiizrn3.js?dpl=nogit-1791882788","/_next/static/chunks/2yss1g0cimuwe.js?dpl=nogit-1791882788","/_next/static/chunks/0e7v08pdxbxe2.js?dpl=nogit-1791882788","/_next/static/chunks/36nndwkz7iik3.js?dpl=nogit-1791882788","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1791882788","/_next/static/chunks/2fnth9-t6i7kd.js?dpl=nogit-1791882788","/_next/static/chunks/24srd-xd1m5z8.js?dpl=nogit-1791882788","/_next/static/chunks/0a57o9qvnv-nb.js?dpl=nogit-1791882788","/_next/static/chunks/41hx021qkamew.js?dpl=nogit-1791882788","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1791882788"],"Gingerbread"] 35:I[647935,["/_next/static/chunks/1xyh1u_ku6jw-.js?dpl=nogit-1791882788","/_next/static/chunks/2_6olli-sutu3.js?dpl=nogit-1791882788","/_next/static/chunks/1qp4g--o6-1vf.js?dpl=nogit-1791882788","/_next/static/chunks/0psy-n5us57a4.js?dpl=nogit-1791882788","/_next/static/chunks/3mz725-y91ph6.js?dpl=nogit-1791882788","/_next/static/chunks/2x_dbpl3b_l2r.js?dpl=nogit-1791882788","/_next/static/chunks/0nojijad0occ8.js?dpl=nogit-1791882788","/_next/static/chunks/19ua1o9n5v3ho.js?dpl=nogit-1791882788","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1791882788","/_next/static/chunks/3yfg2hrj9oxbd.js?dpl=nogit-1791882788","/_next/static/chunks/35s1d7gs3nyqk.js?dpl=nogit-1791882788","/_next/static/chunks/38w1x0vrld4-w.js?dpl=nogit-1791882788","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1791882788","/_next/static/chunks/3kzt2piec6aoa.js?dpl=nogit-1791882788","/_next/static/chunks/2lsi6eli88uwt.js?dpl=nogit-1791882788","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1791882788","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1791882788","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1791882788","/_next/static/chunks/36r9y5g_s4k64.js?dpl=nogit-1791882788","/_next/static/chunks/40lyu17d590zu.js?dpl=nogit-1791882788","/_next/static/chunks/2g-t2n9ahs3tn.js?dpl=nogit-1791882788","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1791882788","/_next/static/chunks/44w2c3xxfw4wd.js?dpl=nogit-1791882788","/_next/static/chunks/16jtsbm2g52s0.js?dpl=nogit-1791882788","/_next/static/chunks/05mo4k9k-ry1n.js?dpl=nogit-1791882788","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1791882788","/_next/static/chunks/2eanemqjnv2vr.js?dpl=nogit-1791882788","/_next/static/chunks/2f3ohq_f1uov2.js?dpl=nogit-1791882788","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1791882788","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1791882788","/_next/static/chunks/0qeo40bqomvxa.js?dpl=nogit-1791882788","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1791882788","/_next/static/chunks/1coblm1-go81_.js?dpl=nogit-1791882788","/_next/static/chunks/27ftpb6yvr6lz.js?dpl=nogit-1791882788","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1791882788","/_next/static/chunks/1o4x0l2qh0ta-.js?dpl=nogit-1791882788","/_next/static/chunks/3it1o0ex-l5qz.js?dpl=nogit-1791882788","/_next/static/chunks/2gqripb6ybmw9.js?dpl=nogit-1791882788","/_next/static/chunks/2l63yczi1z2qz.js?dpl=nogit-1791882788","/_next/static/chunks/075i0tnxt4not.js?dpl=nogit-1791882788","/_next/static/chunks/1eyu-5752jh17.js?dpl=nogit-1791882788","/_next/static/chunks/1of_-ow2iz1cj.js?dpl=nogit-1791882788","/_next/static/chunks/3ybwgs28on6c8.js?dpl=nogit-1791882788","/_next/static/chunks/13gj59kzq50t_.js?dpl=nogit-1791882788","/_next/static/chunks/1986062z5zb0v.js?dpl=nogit-1791882788","/_next/static/chunks/0uitbylhcd4am.js?dpl=nogit-1791882788","/_next/static/chunks/0wv8cpdr6cvhr.js?dpl=nogit-1791882788","/_next/static/chunks/06b61oz__qen3.js?dpl=nogit-1791882788","/_next/static/chunks/0a4x2f2g83l7b.js?dpl=nogit-1791882788","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1791882788","/_next/static/chunks/3q5gc8lbwr4b4.js?dpl=nogit-1791882788","/_next/static/chunks/0dspbdeiizrn3.js?dpl=nogit-1791882788","/_next/static/chunks/2yss1g0cimuwe.js?dpl=nogit-1791882788","/_next/static/chunks/0e7v08pdxbxe2.js?dpl=nogit-1791882788","/_next/static/chunks/36nndwkz7iik3.js?dpl=nogit-1791882788","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1791882788","/_next/static/chunks/2fnth9-t6i7kd.js?dpl=nogit-1791882788","/_next/static/chunks/24srd-xd1m5z8.js?dpl=nogit-1791882788","/_next/static/chunks/0a57o9qvnv-nb.js?dpl=nogit-1791882788","/_next/static/chunks/41hx021qkamew.js?dpl=nogit-1791882788","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1791882788"],"RecordResourceResume"] 36:I[830476,["/_next/static/chunks/1xyh1u_ku6jw-.js?dpl=nogit-1791882788","/_next/static/chunks/2_6olli-sutu3.js?dpl=nogit-1791882788","/_next/static/chunks/1qp4g--o6-1vf.js?dpl=nogit-1791882788","/_next/static/chunks/0psy-n5us57a4.js?dpl=nogit-1791882788","/_next/static/chunks/3mz725-y91ph6.js?dpl=nogit-1791882788","/_next/static/chunks/2x_dbpl3b_l2r.js?dpl=nogit-1791882788","/_next/static/chunks/0nojijad0occ8.js?dpl=nogit-1791882788","/_next/static/chunks/19ua1o9n5v3ho.js?dpl=nogit-1791882788","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1791882788","/_next/static/chunks/3yfg2hrj9oxbd.js?dpl=nogit-1791882788","/_next/static/chunks/35s1d7gs3nyqk.js?dpl=nogit-1791882788","/_next/static/chunks/38w1x0vrld4-w.js?dpl=nogit-1791882788","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1791882788","/_next/static/chunks/3kzt2piec6aoa.js?dpl=nogit-1791882788","/_next/static/chunks/2lsi6eli88uwt.js?dpl=nogit-1791882788","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1791882788","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1791882788","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1791882788","/_next/static/chunks/36r9y5g_s4k64.js?dpl=nogit-1791882788","/_next/static/chunks/40lyu17d590zu.js?dpl=nogit-1791882788","/_next/static/chunks/2g-t2n9ahs3tn.js?dpl=nogit-1791882788","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1791882788","/_next/static/chunks/44w2c3xxfw4wd.js?dpl=nogit-1791882788","/_next/static/chunks/16jtsbm2g52s0.js?dpl=nogit-1791882788","/_next/static/chunks/05mo4k9k-ry1n.js?dpl=nogit-1791882788","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1791882788","/_next/static/chunks/2eanemqjnv2vr.js?dpl=nogit-1791882788","/_next/static/chunks/2f3ohq_f1uov2.js?dpl=nogit-1791882788","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1791882788","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1791882788","/_next/static/chunks/0qeo40bqomvxa.js?dpl=nogit-1791882788","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1791882788","/_next/static/chunks/1coblm1-go81_.js?dpl=nogit-1791882788","/_next/static/chunks/27ftpb6yvr6lz.js?dpl=nogit-1791882788","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1791882788","/_next/static/chunks/1o4x0l2qh0ta-.js?dpl=nogit-1791882788","/_next/static/chunks/3it1o0ex-l5qz.js?dpl=nogit-1791882788","/_next/static/chunks/2gqripb6ybmw9.js?dpl=nogit-1791882788","/_next/static/chunks/2l63yczi1z2qz.js?dpl=nogit-1791882788","/_next/static/chunks/075i0tnxt4not.js?dpl=nogit-1791882788","/_next/static/chunks/1eyu-5752jh17.js?dpl=nogit-1791882788","/_next/static/chunks/1of_-ow2iz1cj.js?dpl=nogit-1791882788","/_next/static/chunks/3ybwgs28on6c8.js?dpl=nogit-1791882788","/_next/static/chunks/13gj59kzq50t_.js?dpl=nogit-1791882788","/_next/static/chunks/1986062z5zb0v.js?dpl=nogit-1791882788","/_next/static/chunks/0uitbylhcd4am.js?dpl=nogit-1791882788","/_next/static/chunks/0wv8cpdr6cvhr.js?dpl=nogit-1791882788","/_next/static/chunks/06b61oz__qen3.js?dpl=nogit-1791882788","/_next/static/chunks/0a4x2f2g83l7b.js?dpl=nogit-1791882788","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1791882788","/_next/static/chunks/3q5gc8lbwr4b4.js?dpl=nogit-1791882788","/_next/static/chunks/0dspbdeiizrn3.js?dpl=nogit-1791882788","/_next/static/chunks/2yss1g0cimuwe.js?dpl=nogit-1791882788","/_next/static/chunks/0e7v08pdxbxe2.js?dpl=nogit-1791882788","/_next/static/chunks/36nndwkz7iik3.js?dpl=nogit-1791882788","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1791882788","/_next/static/chunks/2fnth9-t6i7kd.js?dpl=nogit-1791882788","/_next/static/chunks/24srd-xd1m5z8.js?dpl=nogit-1791882788","/_next/static/chunks/0a57o9qvnv-nb.js?dpl=nogit-1791882788","/_next/static/chunks/41hx021qkamew.js?dpl=nogit-1791882788","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1791882788"],"FlashcardAccessBranch"] 37:I[315438,["/_next/static/chunks/1xyh1u_ku6jw-.js?dpl=nogit-1791882788","/_next/static/chunks/2_6olli-sutu3.js?dpl=nogit-1791882788","/_next/static/chunks/1qp4g--o6-1vf.js?dpl=nogit-1791882788","/_next/static/chunks/0psy-n5us57a4.js?dpl=nogit-1791882788","/_next/static/chunks/3mz725-y91ph6.js?dpl=nogit-1791882788","/_next/static/chunks/2x_dbpl3b_l2r.js?dpl=nogit-1791882788","/_next/static/chunks/0nojijad0occ8.js?dpl=nogit-1791882788","/_next/static/chunks/19ua1o9n5v3ho.js?dpl=nogit-1791882788","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1791882788","/_next/static/chunks/3yfg2hrj9oxbd.js?dpl=nogit-1791882788","/_next/static/chunks/35s1d7gs3nyqk.js?dpl=nogit-1791882788","/_next/static/chunks/38w1x0vrld4-w.js?dpl=nogit-1791882788","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1791882788","/_next/static/chunks/3kzt2piec6aoa.js?dpl=nogit-1791882788","/_next/static/chunks/2lsi6eli88uwt.js?dpl=nogit-1791882788","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1791882788","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1791882788","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1791882788","/_next/static/chunks/36r9y5g_s4k64.js?dpl=nogit-1791882788","/_next/static/chunks/40lyu17d590zu.js?dpl=nogit-1791882788","/_next/static/chunks/2g-t2n9ahs3tn.js?dpl=nogit-1791882788","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1791882788","/_next/static/chunks/44w2c3xxfw4wd.js?dpl=nogit-1791882788","/_next/static/chunks/16jtsbm2g52s0.js?dpl=nogit-1791882788","/_next/static/chunks/05mo4k9k-ry1n.js?dpl=nogit-1791882788","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1791882788","/_next/static/chunks/2eanemqjnv2vr.js?dpl=nogit-1791882788","/_next/static/chunks/2f3ohq_f1uov2.js?dpl=nogit-1791882788","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1791882788","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1791882788","/_next/static/chunks/0qeo40bqomvxa.js?dpl=nogit-1791882788","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1791882788","/_next/static/chunks/1coblm1-go81_.js?dpl=nogit-1791882788","/_next/static/chunks/27ftpb6yvr6lz.js?dpl=nogit-1791882788","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1791882788","/_next/static/chunks/1o4x0l2qh0ta-.js?dpl=nogit-1791882788","/_next/static/chunks/3it1o0ex-l5qz.js?dpl=nogit-1791882788","/_next/static/chunks/2gqripb6ybmw9.js?dpl=nogit-1791882788","/_next/static/chunks/2l63yczi1z2qz.js?dpl=nogit-1791882788","/_next/static/chunks/075i0tnxt4not.js?dpl=nogit-1791882788","/_next/static/chunks/1eyu-5752jh17.js?dpl=nogit-1791882788","/_next/static/chunks/1of_-ow2iz1cj.js?dpl=nogit-1791882788","/_next/static/chunks/3ybwgs28on6c8.js?dpl=nogit-1791882788","/_next/static/chunks/13gj59kzq50t_.js?dpl=nogit-1791882788","/_next/static/chunks/1986062z5zb0v.js?dpl=nogit-1791882788","/_next/static/chunks/0uitbylhcd4am.js?dpl=nogit-1791882788","/_next/static/chunks/0wv8cpdr6cvhr.js?dpl=nogit-1791882788","/_next/static/chunks/06b61oz__qen3.js?dpl=nogit-1791882788","/_next/static/chunks/0a4x2f2g83l7b.js?dpl=nogit-1791882788","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1791882788","/_next/static/chunks/3q5gc8lbwr4b4.js?dpl=nogit-1791882788","/_next/static/chunks/0dspbdeiizrn3.js?dpl=nogit-1791882788","/_next/static/chunks/2yss1g0cimuwe.js?dpl=nogit-1791882788","/_next/static/chunks/0e7v08pdxbxe2.js?dpl=nogit-1791882788","/_next/static/chunks/36nndwkz7iik3.js?dpl=nogit-1791882788","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1791882788","/_next/static/chunks/2fnth9-t6i7kd.js?dpl=nogit-1791882788","/_next/static/chunks/24srd-xd1m5z8.js?dpl=nogit-1791882788","/_next/static/chunks/0a57o9qvnv-nb.js?dpl=nogit-1791882788","/_next/static/chunks/41hx021qkamew.js?dpl=nogit-1791882788","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1791882788"],"TopicFlashcardRunner"] 25:[["$","$L33",null,{"feature":"flashcards"}],"$L34",["$","$L35",null,{"href":"/as-level/computer-science/aqa/as-conceptual-data-models-and-entity-relationship-modelling/flashcards","label":"Conceptual data models and entity relationship modelling","subjectCode":"as_level_computer_science__aqa","surface":"flashcards"}],["$","$L36",null,{"runner":["$","div",null,{"className":"min-h-0 flex-1 overflow-hidden bg-background","children":["$","$L37",null,{"decks":[{"id":"69e76f4d-474a-4ffc-bf44-ca923295f3b4","title":"Conceptual data models and entity relationship modelling Flashcards","topicId":"50f5c890-6ec2-5caa-80d7-09ef6e76650e","topicSlug":"as-conceptual-data-models-and-entity-relationship-modelling","cards":[{"id":"94e3eeba-eab4-4a57-a0d5-8ec8c76b5ecc","cardType":"cloze","points":null,"front":"Data requirements describe what data a system must store and the [ ] that connect that data.","back":"Data requirements describe what data a system must store and the rules that connect that data.","mcqOptions":[{"text":"rules","correct":true,"explanation":"Rules specify constraints and relationships governing how stored data items connect, such as which student may enrol on which course."},{"text":"formats","correct":false,"explanation":"Formats describe how values are represented, not how different data items connect. The correct term is rules because data requirements include constraints governing connections."},{"text":"locations","correct":false,"explanation":"Storage locations concern physical implementation rather than connections between data. The correct term is rules because these define how related data may be associated."},{"text":"volumes","correct":false,"explanation":"Data volumes indicate how much information a system handles, not what connects it. The correct term is rules because constraints govern associations between data."}]},{"id":"a3e86aea-c752-43a5-9f8c-c04941bb503a","cardType":"cloze","points":null,"front":"At the requirements stage, you work out what the data [ ], not how it is [ ].","back":"At the requirements stage, you work out what the data means, not how it is implemented.","mcqOptions":[{"text":"At the requirements stage, you work out what the data means, not how it is implemented.","correct":true,"explanation":"Requirements analysis establishes the meaning and purpose of the data independently of technical decisions about databases, tables, files or storage structures."},{"text":"At the requirements stage, you work out what the data looks like, not how it is implemented.","correct":false,"explanation":"This confuses meaning with presentation. At the requirements stage, analysts determine what the data means, while decisions about how it is implemented come later."},{"text":"At the requirements stage, you work out what the data means, not how it is displayed.","correct":false,"explanation":"Display is only one interface concern, whereas implementation includes the complete technical data structure. Requirements establish what data means, not how it is implemented."},{"text":"At the requirements stage, you work out what the data controls, not how it is displayed.","correct":false,"explanation":"This substitutes system behaviour and interface design for data modelling. The requirements stage determines what the data means, rather than how it is implemented."}]},{"id":"d864c903-7c0e-4288-b4c8-9a41ab80f15e","cardType":"cloze","points":null,"front":"A conceptual data model describes important real-world [ ], their properties and their [ ].","back":"A conceptual data model describes important real-world things, their properties and their relationships.","mcqOptions":[{"text":"A conceptual data model describes important real-world things, their properties and their relationships.","correct":true,"explanation":"A conceptual model represents real-world things as entities, records their properties as attributes and shows the relationships connecting those entities."},{"text":"A conceptual data model describes important real-world tables, their properties and their relationships.","correct":false,"explanation":"Tables belong to relational implementation rather than the real-world conceptual view. A conceptual model describes things, their properties and the relationships between them."},{"text":"A conceptual data model describes important real-world things, their properties and their data types.","correct":false,"explanation":"Data types specify how attribute values are represented, not how entities are connected. A conceptual model describes things, their properties and their relationships."},{"text":"A conceptual data model describes important real-world files, their properties and their indexes.","correct":false,"explanation":"Files and indexes are physical storage concepts introduced during implementation. A conceptual model instead describes real-world things, their properties and their relationships."}]},{"id":"60eb3842-8a4d-49d9-b973-a741131ddaa3","cardType":"basic","points":1,"front":"In STUDENT(StudentID, Forename, Surname), what does underlining StudentID show?","back":"It is the entity identifier.","mcqOptions":[{"text":"It is the entity identifier.","correct":true,"explanation":"Underlining StudentID marks the attribute used to distinguish each STUDENT instance uniquely, so StudentID is the entity identifier."},{"text":"It is the entity type.","correct":false,"explanation":"STUDENT is the entity type, not the underlined attribute. Underlining StudentID shows that it is the entity identifier used to distinguish instances."},{"text":"It is the relationship.","correct":false,"explanation":"A relationship associates instances of entity types and is not represented by underlining an attribute. StudentID is underlined because it is the entity identifier."},{"text":"It is the derived attribute.","correct":false,"explanation":"A derived attribute is calculated from other data, which underlining does not indicate here. StudentID is underlined to show that it is the entity identifier."}]},{"id":"63535c63-81ce-489b-87eb-8a034bbe8be7","cardType":"basic","points":1,"front":"In STUDENT(StudentID, Forename, Surname), what are Forename and Surname?","back":"They are attributes.","mcqOptions":[{"text":"They are attributes.","correct":true,"explanation":"Forename and Surname describe properties of each STUDENT instance, so they are attributes belonging to the STUDENT entity type."},{"text":"They are entity identifiers.","correct":false,"explanation":"This mistakes descriptive fields for values that uniquely identify instances. StudentID is the entity identifier, while Forename and Surname are attributes."},{"text":"They are entity types.","correct":false,"explanation":"STUDENT is the entity type because it represents a category of real-world things. Forename and Surname describe each student, so they are attributes."},{"text":"They are relationships.","correct":false,"explanation":"Relationships connect instances of different entity types, whereas Forename and Surname simply describe a student. They are therefore attributes of STUDENT."}]},{"id":"19a04c97-b515-4baf-bda0-ebcc2a49fcf8","cardType":"basic","points":1,"front":"What property must an entity identifier have for each instance?","back":"It must be unique.","mcqOptions":[{"text":"It must be unique.","correct":true,"explanation":"An entity identifier must have a different value for every instance so that each individual entity can be distinguished unambiguously."},{"text":"It must be numeric.","correct":false,"explanation":"Identifiers may contain text, numbers or a combination, so being numeric is unnecessary. They must be unique so that each instance can be distinguished."},{"text":"It must be short.","correct":false,"explanation":"Short identifiers may be convenient, but length does not determine whether they identify instances reliably. An entity identifier must be unique for every instance."},{"text":"It must be sequential.","correct":false,"explanation":"Sequential values are one possible identifier design, but gaps or unordered values do not prevent identification. The essential property is uniqueness across instances."}]},{"id":"2ca41e8d-7843-428f-acb5-bbea9bd05ced","cardType":"cloze","points":null,"front":"A [ ] identifier uses more than one attribute together.","back":"A composite identifier uses more than one attribute together.","mcqOptions":[{"text":"composite","correct":true,"explanation":"A composite identifier combines two or more attributes whose values together uniquely distinguish each instance, even when either attribute alone is insufficient."},{"text":"simple","correct":false,"explanation":"A simple identifier consists of only one attribute. An identifier formed by combining more than one attribute is called composite."},{"text":"foreign","correct":false,"explanation":"A foreign key references an identifier belonging to another relation; it is not defined by attribute count. Multiple attributes used together form a composite identifier."},{"text":"derived","correct":false,"explanation":"Derived describes a value calculated from other data, not an identifier containing several attributes. The correct term for a multi-attribute identifier is composite."}]},{"id":"b11286f1-29f9-48dc-bbf5-f811fe916e3d","cardType":"basic","points":1,"front":"Why can StudentName fail as a unique identifier?","back":"Two students can have the same name.","mcqOptions":[{"text":"Two students can have the same name.","correct":true,"explanation":"Names are not guaranteed to be unique because unrelated students may share an identical name, so StudentName cannot reliably distinguish every student instance."},{"text":"Two students can have the same surname.","correct":false,"explanation":"Sharing only a surname does not necessarily produce identical StudentName values because forenames may differ. StudentName fails because two students can have the same name."},{"text":"Two students can have the same StudentID.","correct":false,"explanation":"StudentID should be assigned uniquely, so duplicate StudentID values indicate invalid data rather than a weakness of StudentName. The problem is that students can share the same name."},{"text":"Two students can have the different names.","correct":false,"explanation":"Different names allow students to be distinguished and therefore do not explain the failure. StudentName is unreliable because two students can have the same name."}]},{"id":"5b934535-c2ba-4ce4-abf6-ffa5a5d76291","cardType":"basic","points":1,"front":"Why can StudentName fail as a stable identifier?","back":"A person’s name can change.","mcqOptions":[{"text":"A person’s name can change.","correct":true,"explanation":"Names can change, for example after marriage or adoption, so they do not reliably identify the same person over time. A stable identifier should remain consistent."},{"text":"A person’s name can be too short.","correct":false,"explanation":"Name length does not make StudentName unstable; short names can still identify people. The real problem is that a person’s name can change, so it may not remain consistent."},{"text":"A person’s name can be case-sensitive.","correct":false,"explanation":"Capitalisation can be standardised by the system and does not inherently prevent a name identifying someone. StudentName fails as a stable identifier because a person’s name can change."},{"text":"A person’s name can be numeric.","correct":false,"explanation":"A name does not need to be numeric to act as an identifier, although it is unsuitable here for another reason. A person’s name can change, making it unstable."}]},{"id":"985a3c39-4fdf-4d35-ba0a-2197f2482dae","cardType":"basic","points":1,"front":"What makes SerialNumber suitable as an INSTRUMENT identifier?","back":"It is unique to each physical instrument.","mcqOptions":[{"text":"It is unique to each physical instrument.","correct":true,"explanation":"Each physical instrument receives its own serial number, so the value distinguishes it from every other instrument. Uniqueness is essential for a reliable identifier."},{"text":"It is identical for every physical instrument.","correct":false,"explanation":"If every instrument had the same serial number, the value could not distinguish individual instruments. A suitable identifier is unique to each physical instrument."},{"text":"It is chosen by the current owner.","correct":false,"explanation":"Ownership can change, and owners do not normally define an instrument’s serial number. SerialNumber is suitable because it is unique to each physical instrument."},{"text":"It is based on the instrument’s colour.","correct":false,"explanation":"Colour is not a guaranteed or sufficiently distinguishing property for instruments. SerialNumber is suitable because it provides a unique value for each physical instrument."}]},{"id":"ff9facd4-ec8c-4c69-9496-0824e60f96a8","cardType":"cloze","points":null,"front":"Cardinality describes how [ ] of one entity can be linked to another.","back":"Cardinality describes how many instances of one entity can be linked to another.","mcqOptions":[{"text":"many instances","correct":true,"explanation":"Cardinality records how many instances of one entity may be associated with instances of another entity, such as one customer linked to many orders."},{"text":"many attributes","correct":false,"explanation":"Attributes describe properties of entities, not the number of entity occurrences connected by a relationship. Cardinality describes how many instances can be linked."},{"text":"many databases","correct":false,"explanation":"Cardinality concerns relationships between entity instances within a data model, not the number of databases involved. The missing term is “many instances”."},{"text":"many identifiers","correct":false,"explanation":"Identifiers distinguish individual entity instances but do not describe relationship counts. Cardinality describes how many instances of one entity can be linked to another."}]},{"id":"a49d007d-5c50-4099-b3d2-befb02847544","cardType":"basic","points":1,"front":"How should you decide the cardinality between two entities?","back":"Ask the link question in both directions.","mcqOptions":[{"text":"Ask the link question in both directions.","correct":true,"explanation":"Checking the relationship from each entity’s perspective reveals both sides of the cardinality, such as one customer having many orders while each order has one customer."},{"text":"Ask the link question in one direction.","correct":false,"explanation":"One direction gives only half of the relationship and can miss whether the reverse side is one or many. The link question must be asked in both directions."},{"text":"Compare the number of attributes.","correct":false,"explanation":"The number of attributes describes entity structure, not how entity instances are related. Cardinality is decided by asking the link question in both directions."},{"text":"Count the number of primary keys.","correct":false,"explanation":"Primary keys identify entities and do not determine how many instances can be associated. Both directions of the link question are needed to establish cardinality."}]},{"id":"523afc92-1c91-4298-a583-341a761d1e6a","cardType":"basic","points":1,"front":"A customer can place many orders, and each order has one customer. What cardinality is this?","back":"One-to-many.","mcqOptions":[{"text":"One-to-many.","correct":true,"explanation":"One customer can place many orders, while each individual order belongs to one customer. That combination is a one-to-many relationship from Customer to Order."},{"text":"One-to-one.","correct":false,"explanation":"One-to-one would mean each customer has only one order and each order has one customer. Here, a customer can place many orders, so the relationship is one-to-many."},{"text":"Many-to-one.","correct":false,"explanation":"Many-to-one describes the relationship when viewed from orders to customers, but the stated entity order is customer to order. A customer can place many orders: one-to-many."},{"text":"Many-to-many.","correct":false,"explanation":"Many-to-many would require each order to have multiple customers as well as each customer having multiple orders. Each order has one customer, making this one-to-many."}]},{"id":"fc08b44c-3913-4a08-9ffd-0710fa28f2a5","cardType":"basic","points":1,"front":"An order contains many products, and a product appears in many orders. What cardinality is this?","back":"Many-to-many.","mcqOptions":[{"text":"Many-to-many.","correct":true,"explanation":"An order can contain many products, and each product can appear in many orders. Since both sides can have multiple related instances, the cardinality is many-to-many."},{"text":"One-to-many.","correct":false,"explanation":"One-to-many would mean one side has only a single related instance. Here, both orders and products can have many relationships, so the cardinality is many-to-many."},{"text":"One-to-one.","correct":false,"explanation":"One-to-one would allow only one product per order and one order per product. The description allows multiple products and multiple orders, giving many-to-many cardinality."},{"text":"Many-to-one.","correct":false,"explanation":"Many-to-one permits multiple instances on only one side. In this relationship, both an order and a product can be associated with many instances, so it is many-to-many."}]},{"id":"f8f15c91-5a53-4c85-be39-952664837a13","cardType":"basic","points":1,"front":"What entity type represents a relationship that has its own attributes?","back":"An associative or linking entity.","mcqOptions":[{"text":"An associative or linking entity.","correct":true,"explanation":"An associative or linking entity represents the relationship as an entity in its own right, allowing attributes that describe that relationship to be stored."},{"text":"A weak or dependent entity.","correct":false,"explanation":"A weak or dependent entity relies on another entity for identification or existence, which is a different concept. A relationship with its own attributes uses an associative or linking entity."},{"text":"A parent or supertype entity.","correct":false,"explanation":"A parent or supertype entity represents inheritance and shared attributes, not a relationship with its own attributes. That relationship is represented by an associative or linking entity."},{"text":"A child or subtype entity.","correct":false,"explanation":"A child or subtype entity is a specialised version of another entity in an inheritance structure. It does not specifically represent a relationship with attributes."}]},{"id":"726dc3b8-8a23-4e7f-8f9b-7a0b9ebd85bf","cardType":"basic","points":2,"front":"Why does Quantity belong on ORDERLINE rather than PRODUCT?","back":"A product can have different quantities in different orders.","mcqOptions":[{"text":"A product can have different quantities in different orders.","correct":true,"explanation":"Quantity depends on the particular product-order combination, not on the product alone. ORDERLINE represents that combination, so it is the correct place for Quantity."},{"text":"A product can have different prices in different orders.","correct":false,"explanation":"Different prices could justify storing a price on ORDERLINE, but they do not explain Quantity. Quantity belongs there because it can differ for the same product in different orders."},{"text":"A product can have different discounts in different orders.","correct":false,"explanation":"Discounts may vary between orders, but that is a separate attribute from Quantity. Quantity belongs on ORDERLINE because it depends on the specific product-order combination."},{"text":"A product can have different names in different orders.","correct":false,"explanation":"A product’s name normally describes the product itself and is not the reason Quantity is stored on ORDERLINE. Quantity varies between different orders for the same product."}]},{"id":"172a5135-7dcb-4b8f-8e1a-53cf321734cc","cardType":"basic","points":1,"front":"In a typical ERD, what do lines between entities represent?","back":"Relationships between entities.","mcqOptions":[{"text":"Relationships between entities.","correct":true,"explanation":"A line connects two entities to show an association between them, such as a STUDENT enrolling on a COURSE. Labels and cardinalities can provide further details about that relationship."},{"text":"Attributes belonging to entities.","correct":false,"explanation":"Attributes are properties such as StudentID or Name and are normally shown inside or attached to an entity. Lines between entities represent relationships, not attributes."},{"text":"Primary keys shared by entities.","correct":false,"explanation":"Primary keys uniquely identify entity instances and are shown as attributes, often underlined. A line between entities represents a relationship, even when keys later implement it."},{"text":"Records stored within entities.","correct":false,"explanation":"Records are individual instances of an entity, such as one particular student, and are not represented by connecting lines. Lines show relationships between entity types."}]},{"id":"88f01e48-d25c-4d12-8d30-6a1a57edc5f1","cardType":"basic","points":2,"front":"Why does EnrolDate belong on ENROLMENT rather than STUDENT or COURSE?","back":"It describes a particular student-course enrolment.","mcqOptions":[{"text":"It describes a particular student-course enrolment.","correct":true,"explanation":"EnrolDate depends on the combination of a particular student and a particular course. It therefore describes the ENROLMENT relationship rather than either entity independently."},{"text":"It describes a student independently of any course.","correct":false,"explanation":"Placing EnrolDate on STUDENT would incorrectly suggest that each student has one enrolment date overall. The date actually belongs to a particular student-course enrolment."},{"text":"It describes a course independently of any student.","correct":false,"explanation":"Placing EnrolDate on COURSE would incorrectly give a course one shared enrolment date. Different students may enrol on that course on different dates, so it belongs on ENROLMENT."},{"text":"It describes the date on which a course was created.","correct":false,"explanation":"This confuses a student's enrolment date with a course creation date. EnrolDate records when a particular student enrolled on a particular course, so it belongs on ENROLMENT."}]},{"id":"fb23682f-b8af-4471-b0ff-5864e31bc150","cardType":"cloze","points":null,"front":"ENROLMENT(StudentID, CourseID, EnrolDate) assumes a student can enrol on a course [ ].","back":"ENROLMENT(StudentID, CourseID, EnrolDate) assumes a student can enrol on a course only once.","mcqOptions":[{"text":"only once","correct":true,"explanation":"StudentID and CourseID together form the identifying key, so each student-course combination can appear only once. Supporting retakes would require an additional distinguishing attribute."},{"text":"more than once","correct":false,"explanation":"A composite key of StudentID and CourseID prevents duplicate student-course combinations, so it cannot represent multiple attempts. The design assumes the student enrols on that course only once."},{"text":"exactly twice","correct":false,"explanation":"Nothing in this composite key creates two permitted occurrences. It makes each StudentID-CourseID pair unique, meaning the model assumes enrolment on a given course only once."},{"text":"an unlimited number of times","correct":false,"explanation":"Unlimited repeat enrolments would produce duplicate StudentID-CourseID key values, which are not allowed. The stated schema therefore assumes each student can enrol on each course only once."}]},{"id":"691f78cd-f9f1-40ce-a1df-c87774cceca4","cardType":"basic","points":2,"front":"If students can retake the same course, why is StudentID + CourseID insufficient for ENROLMENT?","back":"The same student-course pair could occur more than once.","mcqOptions":[{"text":"The same student-course pair could occur more than once.","correct":true,"explanation":"A retake creates another enrolment for the same student and course, producing the same composite key. An attempt number, enrolment date, or separate EnrolmentID is needed to distinguish occurrences."},{"text":"The same student-course pair would always be unique.","correct":false,"explanation":"This is true only when retakes are prohibited. If retakes are allowed, the same student-course combination can recur, so StudentID and CourseID alone cannot uniquely identify every enrolment."},{"text":"Each course can contain more than one student.","correct":false,"explanation":"Multiple students on one course do not duplicate the composite key because their StudentIDs differ. The problem arises when the same student-course pair occurs again during a retake."},{"text":"Each student can enrol on more than one course.","correct":false,"explanation":"Enrolling on different courses produces different CourseID values, so the composite key remains unique. It becomes insufficient when the same student retakes the same course."}]},{"id":"6ce06401-c0d6-426d-9eaf-f7d7f5364222","cardType":"basic","points":2,"front":"Why model COPY separately from BOOK in the library example?","back":"A book can have several physical copies.","mcqOptions":[{"text":"A book can have several physical copies.","correct":true,"explanation":"BOOK represents shared bibliographic information, while COPY represents each physical item. Separate COPY entities allow every copy to have its own identifier, status, and loan history."},{"text":"A copy can contain several different books.","correct":false,"explanation":"A physical copy is one instance of one book, not a container for multiple titles. COPY is modelled separately because one BOOK can have several physical copies."},{"text":"Every book has exactly one physical copy.","correct":false,"explanation":"Libraries commonly hold multiple copies of the same title, so a one-to-one assumption is unsuitable. COPY is separate because one BOOK may correspond to several physical items."},{"text":"Books and copies have identical identifiers.","correct":false,"explanation":"A BookID identifies the title or edition, while a CopyID identifies one physical item. Separate modelling is needed because several copies can share the same book details."}]},{"id":"4b8f893b-2630-491f-a308-86f65e22de74","cardType":"basic","points":1,"front":"In the library model, where should DateBorrowed and DueDate be stored?","back":"On LOAN.","mcqOptions":[{"text":"On LOAN.","correct":true,"explanation":"DateBorrowed and DueDate describe a particular borrowing transaction between a member and a copy. They therefore belong on LOAN, where each borrowing is recorded separately."},{"text":"On MEMBER.","correct":false,"explanation":"Storing these dates on MEMBER would allow only one borrowing period per member and would not identify the borrowed copy. They belong on the relevant LOAN record."},{"text":"On COPY.","correct":false,"explanation":"Storing the dates on COPY would retain only one borrowing period and overwrite its previous loan history. Each set of dates belongs on a separate LOAN record."},{"text":"On BOOK.","correct":false,"explanation":"BOOK describes a title, not a particular borrowing or even a particular physical copy. DateBorrowed and DueDate describe an individual transaction, so they belong on LOAN."}]},{"id":"40cf0250-6895-40cd-a0e0-7fc230cb6c51","cardType":"basic","points":2,"front":"How does the library model allow the same member to borrow the same copy twice?","back":"Create separate LOAN records for each borrowing.","mcqOptions":[{"text":"Create separate LOAN records for each borrowing.","correct":true,"explanation":"Each borrowing is represented by its own LOAN instance, with separate dates and identifying information. The same member-copy combination can therefore appear in distinct loan transactions."},{"text":"Update the existing LOAN record with the new dates.","correct":false,"explanation":"Overwriting the existing record would erase the first borrowing and lose the loan history. A separate LOAN record must be created for every new borrowing."},{"text":"Create separate COPY records for each borrowing.","correct":false,"explanation":"A new borrowing does not create a new physical copy, so duplicating COPY would misrepresent the library's stock. Separate LOAN records should represent the two transactions."},{"text":"Create separate MEMBER records for each borrowing.","correct":false,"explanation":"The person remains the same member, so duplicating MEMBER would create false identities and repeated personal data. Each borrowing should instead have a separate LOAN record."}]}]}],"examCountdown":{"examDate":"2027-05-11","paperLabel":"Paper 1"},"heading":"Conceptual data models and entity relationship modelling","title":"Conceptual data models and entity relationship modelling Flashcards","topbar":{"backHref":"/as-level/computer-science/aqa/flashcards"},"topicSidebar":"$L38"}]}],"topicId":"50f5c890-6ec2-5caa-80d7-09ef6e76650e","walled":"$L39"}],"$L3a","$L3b"]