33:I[196793,["/_next/static/chunks/2vo-_evnc94jh.js?dpl=nogit-1790409415","/_next/static/chunks/2mu6-wo6ccpi3.js?dpl=nogit-1790409415","/_next/static/chunks/2epfhfe5im7r6.js?dpl=nogit-1790409415","/_next/static/chunks/1ew75_i487l-5.js?dpl=nogit-1790409415","/_next/static/chunks/0p4rexedanx97.js?dpl=nogit-1790409415","/_next/static/chunks/0u008gt6051u7.js?dpl=nogit-1790409415","/_next/static/chunks/1odwrcl12kfnl.js?dpl=nogit-1790409415","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1790409415","/_next/static/chunks/3lf9kdvvybemj.js?dpl=nogit-1790409415","/_next/static/chunks/2hyw6fyf3iqeh.js?dpl=nogit-1790409415","/_next/static/chunks/03q735zs9dbpu.js?dpl=nogit-1790409415","/_next/static/chunks/3r5hh4t0jf4es.js?dpl=nogit-1790409415","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1790409415","/_next/static/chunks/1h4wccj42vygd.js?dpl=nogit-1790409415","/_next/static/chunks/12xoy6h_w_le6.js?dpl=nogit-1790409415","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1790409415","/_next/static/chunks/3ht89vb0p09bm.js?dpl=nogit-1790409415","/_next/static/chunks/3ocoqwe4aht_u.js?dpl=nogit-1790409415","/_next/static/chunks/32qmkt01ta8b2.js?dpl=nogit-1790409415","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1790409415","/_next/static/chunks/3ao1re0xmmur_.js?dpl=nogit-1790409415","/_next/static/chunks/3xa2z7fbv2riw.js?dpl=nogit-1790409415","/_next/static/chunks/14kf-an-d2n-e.js?dpl=nogit-1790409415","/_next/static/chunks/381o-754ev9ia.js?dpl=nogit-1790409415","/_next/static/chunks/2tr2cll18vqv3.js?dpl=nogit-1790409415","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1790409415","/_next/static/chunks/3kom3ps_bn2q6.js?dpl=nogit-1790409415","/_next/static/chunks/1x_yxljsdq0vl.js?dpl=nogit-1790409415","/_next/static/chunks/1xkpwfqqdrdio.js?dpl=nogit-1790409415","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1790409415","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1790409415","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1790409415","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1790409415","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1790409415","/_next/static/chunks/440m38krgocdi.js?dpl=nogit-1790409415","/_next/static/chunks/2p6gbbs6zvfpy.js?dpl=nogit-1790409415","/_next/static/chunks/172wsar4r7zzx.js?dpl=nogit-1790409415","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1790409415","/_next/static/chunks/0di_sdt4e6ot_.js?dpl=nogit-1790409415","/_next/static/chunks/1pp_uf_jx5j9r.js?dpl=nogit-1790409415","/_next/static/chunks/1s6j_7_p0ugo9.js?dpl=nogit-1790409415","/_next/static/chunks/2vg15qyptj-oc.js?dpl=nogit-1790409415","/_next/static/chunks/2b6r02yb2zswo.js?dpl=nogit-1790409415","/_next/static/chunks/12mv6p8rwcl5o.js?dpl=nogit-1790409415","/_next/static/chunks/422ba61wql3d7.js?dpl=nogit-1790409415","/_next/static/chunks/0d2u5k628p_lw.js?dpl=nogit-1790409415","/_next/static/chunks/34ux0fo6f-rm8.js?dpl=nogit-1790409415","/_next/static/chunks/3h4suq-9gmzwh.js?dpl=nogit-1790409415","/_next/static/chunks/0rt2_go1it43r.js?dpl=nogit-1790409415","/_next/static/chunks/0v5zhouho0zlq.js?dpl=nogit-1790409415","/_next/static/chunks/1gtlwpzgzi12z.js?dpl=nogit-1790409415","/_next/static/chunks/2zwoemojbdlmi.js?dpl=nogit-1790409415","/_next/static/chunks/2y341-r8ncizo.js?dpl=nogit-1790409415","/_next/static/chunks/3jzaxe43n3e1e.js?dpl=nogit-1790409415","/_next/static/chunks/22z8pa0ys3w4l.js?dpl=nogit-1790409415","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1790409415","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1790409415","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1790409415","/_next/static/chunks/1__39-dgg7p8-.js?dpl=nogit-1790409415","/_next/static/chunks/0pdzmybpnr872.js?dpl=nogit-1790409415","/_next/static/chunks/1zt4k83kx3bkw.js?dpl=nogit-1790409415","/_next/static/chunks/200x0be4hbjpj.js?dpl=nogit-1790409415","/_next/static/chunks/35bn8r0ao86_s.js?dpl=nogit-1790409415","/_next/static/chunks/3wqp-h5xnebw9.js?dpl=nogit-1790409415","/_next/static/chunks/120-bka6zq5lp.js?dpl=nogit-1790409415","/_next/static/chunks/30dopbgd1dkf9.js?dpl=nogit-1790409415","/_next/static/chunks/43ajf4ofaeu5y.js?dpl=nogit-1790409415"],"Gingerbread"] 35:I[647935,["/_next/static/chunks/2vo-_evnc94jh.js?dpl=nogit-1790409415","/_next/static/chunks/2mu6-wo6ccpi3.js?dpl=nogit-1790409415","/_next/static/chunks/2epfhfe5im7r6.js?dpl=nogit-1790409415","/_next/static/chunks/1ew75_i487l-5.js?dpl=nogit-1790409415","/_next/static/chunks/0p4rexedanx97.js?dpl=nogit-1790409415","/_next/static/chunks/0u008gt6051u7.js?dpl=nogit-1790409415","/_next/static/chunks/1odwrcl12kfnl.js?dpl=nogit-1790409415","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1790409415","/_next/static/chunks/3lf9kdvvybemj.js?dpl=nogit-1790409415","/_next/static/chunks/2hyw6fyf3iqeh.js?dpl=nogit-1790409415","/_next/static/chunks/03q735zs9dbpu.js?dpl=nogit-1790409415","/_next/static/chunks/3r5hh4t0jf4es.js?dpl=nogit-1790409415","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1790409415","/_next/static/chunks/1h4wccj42vygd.js?dpl=nogit-1790409415","/_next/static/chunks/12xoy6h_w_le6.js?dpl=nogit-1790409415","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1790409415","/_next/static/chunks/3ht89vb0p09bm.js?dpl=nogit-1790409415","/_next/static/chunks/3ocoqwe4aht_u.js?dpl=nogit-1790409415","/_next/static/chunks/32qmkt01ta8b2.js?dpl=nogit-1790409415","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1790409415","/_next/static/chunks/3ao1re0xmmur_.js?dpl=nogit-1790409415","/_next/static/chunks/3xa2z7fbv2riw.js?dpl=nogit-1790409415","/_next/static/chunks/14kf-an-d2n-e.js?dpl=nogit-1790409415","/_next/static/chunks/381o-754ev9ia.js?dpl=nogit-1790409415","/_next/static/chunks/2tr2cll18vqv3.js?dpl=nogit-1790409415","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1790409415","/_next/static/chunks/3kom3ps_bn2q6.js?dpl=nogit-1790409415","/_next/static/chunks/1x_yxljsdq0vl.js?dpl=nogit-1790409415","/_next/static/chunks/1xkpwfqqdrdio.js?dpl=nogit-1790409415","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1790409415","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1790409415","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1790409415","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1790409415","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1790409415","/_next/static/chunks/440m38krgocdi.js?dpl=nogit-1790409415","/_next/static/chunks/2p6gbbs6zvfpy.js?dpl=nogit-1790409415","/_next/static/chunks/172wsar4r7zzx.js?dpl=nogit-1790409415","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1790409415","/_next/static/chunks/0di_sdt4e6ot_.js?dpl=nogit-1790409415","/_next/static/chunks/1pp_uf_jx5j9r.js?dpl=nogit-1790409415","/_next/static/chunks/1s6j_7_p0ugo9.js?dpl=nogit-1790409415","/_next/static/chunks/2vg15qyptj-oc.js?dpl=nogit-1790409415","/_next/static/chunks/2b6r02yb2zswo.js?dpl=nogit-1790409415","/_next/static/chunks/12mv6p8rwcl5o.js?dpl=nogit-1790409415","/_next/static/chunks/422ba61wql3d7.js?dpl=nogit-1790409415","/_next/static/chunks/0d2u5k628p_lw.js?dpl=nogit-1790409415","/_next/static/chunks/34ux0fo6f-rm8.js?dpl=nogit-1790409415","/_next/static/chunks/3h4suq-9gmzwh.js?dpl=nogit-1790409415","/_next/static/chunks/0rt2_go1it43r.js?dpl=nogit-1790409415","/_next/static/chunks/0v5zhouho0zlq.js?dpl=nogit-1790409415","/_next/static/chunks/1gtlwpzgzi12z.js?dpl=nogit-1790409415","/_next/static/chunks/2zwoemojbdlmi.js?dpl=nogit-1790409415","/_next/static/chunks/2y341-r8ncizo.js?dpl=nogit-1790409415","/_next/static/chunks/3jzaxe43n3e1e.js?dpl=nogit-1790409415","/_next/static/chunks/22z8pa0ys3w4l.js?dpl=nogit-1790409415","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1790409415","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1790409415","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1790409415","/_next/static/chunks/1__39-dgg7p8-.js?dpl=nogit-1790409415","/_next/static/chunks/0pdzmybpnr872.js?dpl=nogit-1790409415","/_next/static/chunks/1zt4k83kx3bkw.js?dpl=nogit-1790409415","/_next/static/chunks/200x0be4hbjpj.js?dpl=nogit-1790409415","/_next/static/chunks/35bn8r0ao86_s.js?dpl=nogit-1790409415","/_next/static/chunks/3wqp-h5xnebw9.js?dpl=nogit-1790409415","/_next/static/chunks/120-bka6zq5lp.js?dpl=nogit-1790409415","/_next/static/chunks/30dopbgd1dkf9.js?dpl=nogit-1790409415","/_next/static/chunks/43ajf4ofaeu5y.js?dpl=nogit-1790409415"],"RecordResourceResume"] 36:I[830476,["/_next/static/chunks/2vo-_evnc94jh.js?dpl=nogit-1790409415","/_next/static/chunks/2mu6-wo6ccpi3.js?dpl=nogit-1790409415","/_next/static/chunks/2epfhfe5im7r6.js?dpl=nogit-1790409415","/_next/static/chunks/1ew75_i487l-5.js?dpl=nogit-1790409415","/_next/static/chunks/0p4rexedanx97.js?dpl=nogit-1790409415","/_next/static/chunks/0u008gt6051u7.js?dpl=nogit-1790409415","/_next/static/chunks/1odwrcl12kfnl.js?dpl=nogit-1790409415","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1790409415","/_next/static/chunks/3lf9kdvvybemj.js?dpl=nogit-1790409415","/_next/static/chunks/2hyw6fyf3iqeh.js?dpl=nogit-1790409415","/_next/static/chunks/03q735zs9dbpu.js?dpl=nogit-1790409415","/_next/static/chunks/3r5hh4t0jf4es.js?dpl=nogit-1790409415","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1790409415","/_next/static/chunks/1h4wccj42vygd.js?dpl=nogit-1790409415","/_next/static/chunks/12xoy6h_w_le6.js?dpl=nogit-1790409415","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1790409415","/_next/static/chunks/3ht89vb0p09bm.js?dpl=nogit-1790409415","/_next/static/chunks/3ocoqwe4aht_u.js?dpl=nogit-1790409415","/_next/static/chunks/32qmkt01ta8b2.js?dpl=nogit-1790409415","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1790409415","/_next/static/chunks/3ao1re0xmmur_.js?dpl=nogit-1790409415","/_next/static/chunks/3xa2z7fbv2riw.js?dpl=nogit-1790409415","/_next/static/chunks/14kf-an-d2n-e.js?dpl=nogit-1790409415","/_next/static/chunks/381o-754ev9ia.js?dpl=nogit-1790409415","/_next/static/chunks/2tr2cll18vqv3.js?dpl=nogit-1790409415","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1790409415","/_next/static/chunks/3kom3ps_bn2q6.js?dpl=nogit-1790409415","/_next/static/chunks/1x_yxljsdq0vl.js?dpl=nogit-1790409415","/_next/static/chunks/1xkpwfqqdrdio.js?dpl=nogit-1790409415","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1790409415","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1790409415","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1790409415","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1790409415","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1790409415","/_next/static/chunks/440m38krgocdi.js?dpl=nogit-1790409415","/_next/static/chunks/2p6gbbs6zvfpy.js?dpl=nogit-1790409415","/_next/static/chunks/172wsar4r7zzx.js?dpl=nogit-1790409415","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1790409415","/_next/static/chunks/0di_sdt4e6ot_.js?dpl=nogit-1790409415","/_next/static/chunks/1pp_uf_jx5j9r.js?dpl=nogit-1790409415","/_next/static/chunks/1s6j_7_p0ugo9.js?dpl=nogit-1790409415","/_next/static/chunks/2vg15qyptj-oc.js?dpl=nogit-1790409415","/_next/static/chunks/2b6r02yb2zswo.js?dpl=nogit-1790409415","/_next/static/chunks/12mv6p8rwcl5o.js?dpl=nogit-1790409415","/_next/static/chunks/422ba61wql3d7.js?dpl=nogit-1790409415","/_next/static/chunks/0d2u5k628p_lw.js?dpl=nogit-1790409415","/_next/static/chunks/34ux0fo6f-rm8.js?dpl=nogit-1790409415","/_next/static/chunks/3h4suq-9gmzwh.js?dpl=nogit-1790409415","/_next/static/chunks/0rt2_go1it43r.js?dpl=nogit-1790409415","/_next/static/chunks/0v5zhouho0zlq.js?dpl=nogit-1790409415","/_next/static/chunks/1gtlwpzgzi12z.js?dpl=nogit-1790409415","/_next/static/chunks/2zwoemojbdlmi.js?dpl=nogit-1790409415","/_next/static/chunks/2y341-r8ncizo.js?dpl=nogit-1790409415","/_next/static/chunks/3jzaxe43n3e1e.js?dpl=nogit-1790409415","/_next/static/chunks/22z8pa0ys3w4l.js?dpl=nogit-1790409415","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1790409415","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1790409415","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1790409415","/_next/static/chunks/1__39-dgg7p8-.js?dpl=nogit-1790409415","/_next/static/chunks/0pdzmybpnr872.js?dpl=nogit-1790409415","/_next/static/chunks/1zt4k83kx3bkw.js?dpl=nogit-1790409415","/_next/static/chunks/200x0be4hbjpj.js?dpl=nogit-1790409415","/_next/static/chunks/35bn8r0ao86_s.js?dpl=nogit-1790409415","/_next/static/chunks/3wqp-h5xnebw9.js?dpl=nogit-1790409415","/_next/static/chunks/120-bka6zq5lp.js?dpl=nogit-1790409415","/_next/static/chunks/30dopbgd1dkf9.js?dpl=nogit-1790409415","/_next/static/chunks/43ajf4ofaeu5y.js?dpl=nogit-1790409415"],"FlashcardAccessBranch"] 37:I[315438,["/_next/static/chunks/2vo-_evnc94jh.js?dpl=nogit-1790409415","/_next/static/chunks/2mu6-wo6ccpi3.js?dpl=nogit-1790409415","/_next/static/chunks/2epfhfe5im7r6.js?dpl=nogit-1790409415","/_next/static/chunks/1ew75_i487l-5.js?dpl=nogit-1790409415","/_next/static/chunks/0p4rexedanx97.js?dpl=nogit-1790409415","/_next/static/chunks/0u008gt6051u7.js?dpl=nogit-1790409415","/_next/static/chunks/1odwrcl12kfnl.js?dpl=nogit-1790409415","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1790409415","/_next/static/chunks/3lf9kdvvybemj.js?dpl=nogit-1790409415","/_next/static/chunks/2hyw6fyf3iqeh.js?dpl=nogit-1790409415","/_next/static/chunks/03q735zs9dbpu.js?dpl=nogit-1790409415","/_next/static/chunks/3r5hh4t0jf4es.js?dpl=nogit-1790409415","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1790409415","/_next/static/chunks/1h4wccj42vygd.js?dpl=nogit-1790409415","/_next/static/chunks/12xoy6h_w_le6.js?dpl=nogit-1790409415","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1790409415","/_next/static/chunks/3ht89vb0p09bm.js?dpl=nogit-1790409415","/_next/static/chunks/3ocoqwe4aht_u.js?dpl=nogit-1790409415","/_next/static/chunks/32qmkt01ta8b2.js?dpl=nogit-1790409415","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1790409415","/_next/static/chunks/3ao1re0xmmur_.js?dpl=nogit-1790409415","/_next/static/chunks/3xa2z7fbv2riw.js?dpl=nogit-1790409415","/_next/static/chunks/14kf-an-d2n-e.js?dpl=nogit-1790409415","/_next/static/chunks/381o-754ev9ia.js?dpl=nogit-1790409415","/_next/static/chunks/2tr2cll18vqv3.js?dpl=nogit-1790409415","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1790409415","/_next/static/chunks/3kom3ps_bn2q6.js?dpl=nogit-1790409415","/_next/static/chunks/1x_yxljsdq0vl.js?dpl=nogit-1790409415","/_next/static/chunks/1xkpwfqqdrdio.js?dpl=nogit-1790409415","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1790409415","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1790409415","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1790409415","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1790409415","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1790409415","/_next/static/chunks/440m38krgocdi.js?dpl=nogit-1790409415","/_next/static/chunks/2p6gbbs6zvfpy.js?dpl=nogit-1790409415","/_next/static/chunks/172wsar4r7zzx.js?dpl=nogit-1790409415","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1790409415","/_next/static/chunks/0di_sdt4e6ot_.js?dpl=nogit-1790409415","/_next/static/chunks/1pp_uf_jx5j9r.js?dpl=nogit-1790409415","/_next/static/chunks/1s6j_7_p0ugo9.js?dpl=nogit-1790409415","/_next/static/chunks/2vg15qyptj-oc.js?dpl=nogit-1790409415","/_next/static/chunks/2b6r02yb2zswo.js?dpl=nogit-1790409415","/_next/static/chunks/12mv6p8rwcl5o.js?dpl=nogit-1790409415","/_next/static/chunks/422ba61wql3d7.js?dpl=nogit-1790409415","/_next/static/chunks/0d2u5k628p_lw.js?dpl=nogit-1790409415","/_next/static/chunks/34ux0fo6f-rm8.js?dpl=nogit-1790409415","/_next/static/chunks/3h4suq-9gmzwh.js?dpl=nogit-1790409415","/_next/static/chunks/0rt2_go1it43r.js?dpl=nogit-1790409415","/_next/static/chunks/0v5zhouho0zlq.js?dpl=nogit-1790409415","/_next/static/chunks/1gtlwpzgzi12z.js?dpl=nogit-1790409415","/_next/static/chunks/2zwoemojbdlmi.js?dpl=nogit-1790409415","/_next/static/chunks/2y341-r8ncizo.js?dpl=nogit-1790409415","/_next/static/chunks/3jzaxe43n3e1e.js?dpl=nogit-1790409415","/_next/static/chunks/22z8pa0ys3w4l.js?dpl=nogit-1790409415","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1790409415","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1790409415","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1790409415","/_next/static/chunks/1__39-dgg7p8-.js?dpl=nogit-1790409415","/_next/static/chunks/0pdzmybpnr872.js?dpl=nogit-1790409415","/_next/static/chunks/1zt4k83kx3bkw.js?dpl=nogit-1790409415","/_next/static/chunks/200x0be4hbjpj.js?dpl=nogit-1790409415","/_next/static/chunks/35bn8r0ao86_s.js?dpl=nogit-1790409415","/_next/static/chunks/3wqp-h5xnebw9.js?dpl=nogit-1790409415","/_next/static/chunks/120-bka6zq5lp.js?dpl=nogit-1790409415","/_next/static/chunks/30dopbgd1dkf9.js?dpl=nogit-1790409415","/_next/static/chunks/43ajf4ofaeu5y.js?dpl=nogit-1790409415"],"TopicFlashcardRunner"] 24:[["$","$L33",null,{"feature":"flashcards"}],"$L34",["$","$L35",null,{"href":"/a-level/computer-science/aqa/programming-paradigms/flashcards","label":"Programming paradigms","subjectCode":"a_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":"763315c9-d467-485c-84b0-c0f8f9e30d4e","title":"Programming paradigms Flashcards","topicId":"07bd522b-9fb0-5af3-b83f-8432744d903d","topicSlug":"programming-paradigms","cards":[{"id":"687faca6-a528-4033-9a9f-0cbff6bb6b34","cardType":"basic","points":1,"front":"Which paradigm organises a program as procedures or subroutines that carry out tasks?","back":"Procedural programming.","mcqOptions":[{"text":"Procedural programming.","correct":true,"explanation":"Procedural programming structures a program as a series of procedures or subroutines, with each one containing instructions that perform a particular task."},{"text":"Functional programming.","correct":false,"explanation":"Functional programming organises computation around functions and avoids changing state where possible. Procedural programming is the paradigm based on procedures or subroutines that carry out tasks."},{"text":"Declarative programming.","correct":false,"explanation":"Declarative programming describes the required result rather than a sequence of task-performing routines. Procedural programming explicitly organises instructions into procedures or subroutines."},{"text":"Object-oriented programming.","correct":false,"explanation":"Object-oriented programming centres on objects containing data and operations, not task-based procedures. Procedural programming organises a program as procedures or subroutines."}]},{"id":"efe31d27-62a0-4578-b8fc-6df12b96baee","cardType":"basic","points":1,"front":"Which paradigm organises a program around objects that combine data and operations?","back":"Object-oriented programming.","mcqOptions":[{"text":"Object-oriented programming.","correct":true,"explanation":"Object-oriented programming structures software around objects, each of which encapsulates data in attributes and associated operations in methods."},{"text":"Procedural programming.","correct":false,"explanation":"Procedural programming organises instructions into procedures that perform tasks. Object-oriented programming instead structures a program around objects that encapsulate related data and operations."},{"text":"Event-driven programming.","correct":false,"explanation":"Event-driven programming determines program flow through events and handlers. Object-oriented programming is specifically the paradigm that combines data and operations within objects."},{"text":"Functional programming.","correct":false,"explanation":"Functional programming builds computation from functions, often limiting state changes. Object-oriented programming combines related data and operations inside objects."}]},{"id":"b594a1a1-b3a5-49da-a6e3-de3aa6c23e25","cardType":"cloze","points":null,"front":"Procedural programming asks what [ ] must happen; object-oriented programming asks what [ ] exist.","back":"Procedural programming asks what steps must happen; object-oriented programming asks what objects exist.","mcqOptions":[{"text":"Procedural programming asks what steps must happen; object-oriented programming asks what objects exist.","correct":true,"explanation":"Procedural programming models the sequence of steps needed to solve a problem, while object-oriented programming models the objects and responsibilities present in the system."},{"text":"Procedural programming asks what objects must happen; object-oriented programming asks what steps exist.","correct":false,"explanation":"This reverses the two perspectives and makes the nouns fit the wrong questions. Procedural design focuses on steps, whereas object-oriented design identifies objects."},{"text":"Procedural programming asks what decisions must happen; object-oriented programming asks what objects exist.","correct":false,"explanation":"Selection decisions may form part of a procedure, but they are not its overall organising focus. Procedural programming asks what steps must happen; object-oriented programming identifies objects."},{"text":"Procedural programming asks what steps must happen; object-oriented programming asks what functions exist.","correct":false,"explanation":"Functions or methods may provide operations, but they are not the central organising entities in object-oriented programming. The paradigm asks what objects exist."}]},{"id":"3b92ed09-234b-4bc4-94a9-93e15eb4255d","cardType":"basic","points":1,"front":"Which control structure runs instructions one after another?","back":"Sequence.","mcqOptions":[{"text":"Sequence.","correct":true,"explanation":"Sequence executes instructions consecutively in the order in which they appear, without choosing between branches or repeatedly looping over them."},{"text":"Selection.","correct":false,"explanation":"Selection chooses between alternative paths according to a condition. Sequence is the structure that executes instructions consecutively in their stated order."},{"text":"Iteration.","correct":false,"explanation":"Iteration repeats a block of instructions while a condition holds or for a set number of times. Sequence runs instructions once, one after another."},{"text":"Recursion.","correct":false,"explanation":"Recursion occurs when a subroutine calls itself, usually with a smaller problem. Sequence is the control structure for running instructions one after another."}]},{"id":"39eaf18a-d46a-4d31-9147-01a1951f8f60","cardType":"basic","points":1,"front":"Which control structure makes a choice, such as IF ... THEN ... ELSE?","back":"Selection.","mcqOptions":[{"text":"Selection.","correct":true,"explanation":"Selection evaluates a condition and chooses between alternative paths, such as executing either the THEN branch or the ELSE branch of an IF statement."},{"text":"Iteration.","correct":false,"explanation":"Iteration repeats instructions using a loop rather than choosing between alternatives. Selection uses a condition, such as IF, to determine which branch runs."},{"text":"Sequence.","correct":false,"explanation":"Sequence runs instructions consecutively without branching. Selection evaluates a condition and chooses an appropriate path, as in IF ... THEN ... ELSE."},{"text":"Recursion.","correct":false,"explanation":"Recursion involves a subroutine calling itself and is not the general structure for making a choice. IF ... THEN ... ELSE demonstrates selection."}]},{"id":"24d3ff85-db02-4a2b-aded-3bf6f622a1d2","cardType":"basic","points":1,"front":"Which control structure repeats instructions, such as WHILE or FOR?","back":"Iteration.","mcqOptions":[{"text":"Iteration.","correct":true,"explanation":"Iteration repeatedly executes a block of instructions, either while a condition is satisfied or for a specified number of repetitions."},{"text":"Sequence.","correct":false,"explanation":"Sequence executes instructions once in their stated order. Iteration repeats instructions through loop constructs such as WHILE and FOR."},{"text":"Selection.","correct":false,"explanation":"Selection chooses between alternative branches after evaluating a condition. Iteration is the structure that repeats instructions using WHILE, FOR or similar loops."},{"text":"Recursion.","correct":false,"explanation":"Recursion repeats work through a subroutine calling itself, but WHILE and FOR are loop constructs. Their general control structure is iteration."}]},{"id":"ee1a6a76-73a2-453e-9085-ae3f1caaab5e","cardType":"basic","points":3,"front":"How do top-down design and stepwise refinement differ?","back":"

Top-down design: break the whole problem into subtasks.
Stepwise refinement: add detail until implementable.

","mcqOptions":[{"text":"

Top-down design: break the whole problem into subtasks.
Stepwise refinement: add detail until implementable.

","correct":true,"explanation":"Top-down design initially decomposes the overall problem into smaller subtasks. Stepwise refinement then develops those tasks through increasing levels of detail until they can be implemented."},{"text":"

Top-down design: add detail until implementable.
Stepwise refinement: break the whole problem into subtasks.

","correct":false,"explanation":"This swaps the definitions. Top-down design decomposes the whole problem into subtasks, while stepwise refinement progressively adds enough detail for implementation."},{"text":"

Top-down design: identify the order instructions execute.
Stepwise refinement: test each completed module separately.

","correct":false,"explanation":"Execution order and module testing are development concerns, not these design definitions. Top-down design creates subtasks, and stepwise refinement adds implementation detail."},{"text":"

Top-down design: divide data into classes and objects.
Stepwise refinement: add inheritance between classes.

","correct":false,"explanation":"This confuses general program design with object-oriented modelling. Top-down design decomposes a problem into subtasks, while stepwise refinement expands those subtasks in greater detail."}]},{"id":"aeb7a043-7955-4e14-b03f-a94c63751f88","cardType":"cloze","points":null,"front":"A hierarchy chart shows program [ ] into modules, not execution [ ].","back":"A hierarchy chart shows program decomposition into modules, not execution order.","mcqOptions":[{"text":"A hierarchy chart shows program decomposition into modules, not execution order.","correct":true,"explanation":"A hierarchy chart represents how a program is decomposed into modules and submodules. It shows structural relationships rather than the chronological order of execution."},{"text":"A hierarchy chart shows program composition into modules, not execution order.","correct":false,"explanation":"Composition suggests assembling components rather than breaking a problem down. A hierarchy chart represents decomposition into modules, while still not showing their execution order."},{"text":"A hierarchy chart shows program decomposition into modules, not execution output.","correct":false,"explanation":"The first term is correct, but the contrast is mistaken. Hierarchy charts show decomposition into modules rather than the order in which instructions or modules execute."},{"text":"A hierarchy chart shows program iteration into modules, not execution sequence.","correct":false,"explanation":"Iteration means repetition and cannot describe dividing a program into modules. A hierarchy chart shows program decomposition, and the omitted execution property is order."}]},{"id":"3406a06d-d93b-452d-98a9-1d76723d5f5f","cardType":"basic","points":2,"front":"What should a hierarchy chart avoid showing?","back":"Flowchart details, such as decisions, loops or running order.","mcqOptions":[{"text":"Flowchart details, such as decisions, loops or running order.","correct":true,"explanation":"A hierarchy chart represents program decomposition and relationships between modules. Decisions, loops and execution sequence belong in flowcharts or program code, not in the hierarchy chart."},{"text":"Module details, such as names, parameters or return values.","correct":false,"explanation":"Module names and interfaces are useful features of a hierarchy chart, so they should not generally be avoided. The chart should instead omit flowchart details such as decisions, loops and running order."},{"text":"Structural details, such as modules, subroutines or relationships.","correct":false,"explanation":"Modules, subroutines and their relationships are precisely what a hierarchy chart is intended to communicate. It should avoid flowchart details such as decisions, loops and running order."},{"text":"Decomposition details, such as levels, components or subcomponents.","correct":false,"explanation":"Decomposition into components and subcomponents is the main purpose of a hierarchy chart. Flowchart details such as decisions, loops and running order are what should be excluded."}]},{"id":"8ebf1c23-9f01-40a5-b56c-c7cc0b8dfa18","cardType":"cloze","points":null,"front":"A class is a [ ]; an object is an individual [ ] of a class.","back":"A class is a template; an object is an individual instance of a class.","mcqOptions":[{"text":"A class is a template; an object is an individual instance of a class.","correct":true,"explanation":"A class defines the attributes and methods that its objects will have, so it acts as a template. Each object created from it is a particular instance."},{"text":"A class is a method; an object is an individual attribute of a class.","correct":false,"explanation":"Methods are behaviours and attributes are stored properties within a class; neither describes the class-object relationship. A class is a template, and an object is an instance of it."},{"text":"A class is a template; an object is an individual method of a class.","correct":false,"explanation":"Although a class is correctly described as a template, a method is a behaviour defined by the class, not an object. An object is an individual instance of the class."},{"text":"A class is a variable; an object is an individual template of a class.","correct":false,"explanation":"This reverses and confuses the roles: a class is not an ordinary variable, and an object is not a template. The class is the template and the object is an instance."}]},{"id":"b5b3c015-0e00-460c-bb4e-7ae20a9af28d","cardType":"basic","points":1,"front":"What does a constructor do when an object is created?","back":"It sets up the new object.","mcqOptions":[{"text":"It sets up the new object.","correct":true,"explanation":"A constructor runs when an object is created, setting its initial state by assigning starting attribute values and performing any other required initialisation."},{"text":"It deletes the existing object.","correct":false,"explanation":"Deleting or cleaning up an object is associated with a destructor or memory management, not a constructor. A constructor sets up and initialises a newly created object."},{"text":"It copies the entire class.","correct":false,"explanation":"Creating an object does not duplicate the class definition. The constructor sets up the new object, usually by initialising the attributes belonging to that particular instance."},{"text":"It hides the object’s methods.","correct":false,"explanation":"Method visibility is controlled by access specifiers such as private or public, not by the constructor. The constructor’s role is to set up the new object."}]},{"id":"6f2a48e8-b143-426b-8333-1615791be0ca","cardType":"cloze","points":null,"front":"A reference variable does not contain the whole object directly; it [ ] the object.","back":"A reference variable does not contain the whole object directly; it refers to the object.","mcqOptions":[{"text":"refers to","correct":true,"explanation":"A reference variable stores a reference that identifies or leads to an object rather than storing the complete object value directly, so it refers to that object."},{"text":"contains","correct":false,"explanation":"This confuses a reference with the object’s stored data. A reference variable does not contain the whole object; it refers to the object held elsewhere in memory."},{"text":"copies","correct":false,"explanation":"Assigning an object reference normally copies the reference, not the complete object. The variable therefore refers to the existing object rather than copying all of its data."},{"text":"creates","correct":false,"explanation":"Object creation is performed by instantiation, usually involving a constructor. A reference variable can identify an existing object, so it refers to the object rather than creating it."}]},{"id":"41f1823b-4425-43ae-ada7-351ec2cc9b71","cardType":"basic","points":2,"front":"Why keep object attributes private and update them through public methods?","back":"To protect object state from accidental invalid changes.","mcqOptions":[{"text":"To protect object state from accidental invalid changes.","correct":true,"explanation":"Private attributes support encapsulation by preventing unrestricted external updates. Public methods can validate changes and preserve the rules that keep the object’s state valid."},{"text":"To protect object methods from being called by subclasses.","correct":false,"explanation":"Private attributes are primarily used to control changes to stored state, not to prevent subclass method calls. Public update methods validate changes and protect the object from invalid states."},{"text":"To protect object code from being executed more than once.","correct":false,"explanation":"Access control does not limit how many times object code may run. Keeping attributes private protects object state by requiring updates to pass through controlled, validating public methods."},{"text":"To protect object names from being reused by other classes.","correct":false,"explanation":"Different classes can legitimately reuse attribute and method names without private access preventing it. Privacy instead protects object state from accidental invalid changes made by external code."}]},{"id":"567450d0-6ea6-4656-8920-a9ef3cb5f629","cardType":"cloze","points":null,"front":"Access specifiers: [ ] is accessible inside the class and subclasses; [ ] is accessible from outside the class.","back":"Access specifiers: protected is accessible inside the class and subclasses; public is accessible from outside the class.","mcqOptions":[{"text":"Access specifiers: protected is accessible inside the class and subclasses; public is accessible from outside the class.","correct":true,"explanation":"Protected members are available within their defining class and inherited subclasses, while public members are part of the externally accessible interface and can be used outside the class."},{"text":"Access specifiers: private is accessible inside the class and subclasses; public is accessible from outside the class.","correct":false,"explanation":"Private members are normally restricted to the defining class, not directly available to subclasses. Protected provides class-and-subclass access, while public allows access from outside the class."},{"text":"Access specifiers: protected is accessible inside the class and subclasses; private is accessible from outside the class.","correct":false,"explanation":"The protected description is accurate, but private members are not accessible from general external code. Public is the access specifier used for members available outside the class."},{"text":"Access specifiers: private is accessible inside the class and subclasses; protected is accessible from outside the class.","correct":false,"explanation":"This extends both access levels too far: private is limited to the defining class, and protected is not generally public. Protected includes subclasses, while public permits outside access."}]},{"id":"473db018-c812-4bca-84a6-a247966ffc52","cardType":"basic","points":1,"front":"What can a subclass do through inheritance?","back":"Reuse and extend superclass attributes and methods.","mcqOptions":[{"text":"Reuse and extend superclass attributes and methods.","correct":true,"explanation":"Inheritance gives a subclass the accessible attributes and methods of its superclass. The subclass can reuse them and add or override features to specialise its behaviour."},{"text":"Reuse and replace superclass objects and constructors.","correct":false,"explanation":"A subclass does not inherit and replace the superclass’s existing objects, and constructor inheritance depends on the language. It primarily reuses and extends superclass attributes and methods."},{"text":"Reuse and delete superclass classes and instances.","correct":false,"explanation":"Inheritance does not allow a subclass to delete its superclass or the superclass’s instances. It allows the subclass to reuse and extend accessible attributes and methods."},{"text":"Reuse and conceal superclass parameters and variables.","correct":false,"explanation":"Concealing parameters and variables is not the defining purpose of inheritance. A subclass inherits accessible attributes and methods, which it can reuse, extend or sometimes override."}]},{"id":"92ff2804-fad7-4c1e-b885-dfd246e3cc4f","cardType":"basic","points":3,"front":"How does aggregation differ from composition in object lifetime?","back":"

Aggregation: contained object can exist independently.
Composition: contained object's lifetime is tightly bound.

","mcqOptions":[{"text":"

Aggregation: contained object can exist independently.
Composition: contained object's lifetime is tightly bound.

","correct":true,"explanation":"Aggregation represents a weak whole-part relationship in which the part can survive separately. Composition represents strong ownership, so the contained object’s lifetime is tied to its container."},{"text":"

Aggregation: contained object's lifetime is tightly bound.
Composition: contained object can exist independently.

","correct":false,"explanation":"This reverses the two lifetime relationships. In aggregation, the contained object can exist independently; in composition, strong ownership means its lifetime is tightly bound to the container."},{"text":"

Aggregation: contained object cannot exist independently.
Composition: contained object's lifetime is loosely linked.

","correct":false,"explanation":"This assigns strong dependence to aggregation and weak dependence to composition. Aggregated objects can exist independently, whereas composed objects have lifetimes tightly bound to their container."},{"text":"

Aggregation: contained object is destroyed with its container.
Composition: contained object always outlives its container.

","correct":false,"explanation":"Destruction with the container characterises composition rather than aggregation, while a composed part does not necessarily outlive its owner. Aggregated objects can exist independently; composed lifetimes are tightly bound."}]},{"id":"ece00a4a-275b-4c24-9f9b-72f3873e8a07","cardType":"basic","points":2,"front":"In polymorphism, what decides which overridden method runs?","back":"The actual object receiving the call at runtime.","mcqOptions":[{"text":"The actual object receiving the call at runtime.","correct":true,"explanation":"Dynamic dispatch selects the overridden implementation belonging to the object that actually receives the call, even when the variable referring to it has a superclass type."},{"text":"The declared type of the variable at compile time.","correct":false,"explanation":"Confusing the reference type with the object type ignores dynamic dispatch. The actual object receiving the call at runtime determines which overridden method implementation runs."},{"text":"The class in which the method was first defined.","correct":false,"explanation":"The original defining class does not always supply the executed implementation because subclasses may override it. Runtime dispatch uses the actual receiving object’s class."},{"text":"The number of parameters supplied with the call.","correct":false,"explanation":"Parameter number helps select between overloaded methods, not overridden implementations. For overriding, the actual object receiving the call at runtime determines which version runs."}]},{"id":"722be264-e87c-4494-b862-90e0b5ed4181","cardType":"cloze","points":null,"front":"Overriding occurs when a subclass provides its own version of a [ ].","back":"Overriding occurs when a subclass provides its own version of a superclass method.","mcqOptions":[{"text":"superclass method","correct":true,"explanation":"A subclass overrides a superclass method by supplying a new implementation with the appropriate matching signature, allowing runtime polymorphism to select the subclass version."},{"text":"subclass attribute","correct":false,"explanation":"Attributes are hidden or redeclared rather than overridden in the polymorphic sense. Overriding occurs when a subclass supplies its own version of a superclass method."},{"text":"constructor method","correct":false,"explanation":"Constructors initialise new objects and are not inherited and overridden like ordinary instance methods. The required term is superclass method, whose implementation the subclass replaces."},{"text":"private attribute","correct":false,"explanation":"A private attribute is encapsulated state, not behaviour that a subclass can override. The blank requires superclass method, because overriding replaces inherited method behaviour."}]},{"id":"c89870a0-ab03-4475-adc7-95eb9130b11e","cardType":"basic","points":3,"front":"Match these OOP method types to their role: abstract, virtual, static.","back":"

Abstract: declared without full implementation.
Virtual: designed so subclasses can override it.
Static: belongs to the class, not an object.

","mcqOptions":[{"text":"

Abstract: declared without full implementation.
Virtual: designed so subclasses can override it.
Static: belongs to the class, not an object.

","correct":true,"explanation":"These roles distinguish incomplete abstract declarations, dynamically overridable virtual methods, and static methods associated with the class itself rather than any particular instance."},{"text":"

Abstract: belongs to the class, not an object.
Virtual: declared without full implementation.
Static: designed so subclasses can override it.

","correct":false,"explanation":"This rotates the three definitions. Abstract methods lack full implementation, virtual methods are intended for overriding, and static methods belong to the class rather than an object."},{"text":"

Abstract: designed so subclasses can override it.
Virtual: belongs to the class, not an object.
Static: declared without full implementation.

","correct":false,"explanation":"This confuses overridability with class membership. Abstract methods lack full implementation, virtual methods support overriding, and static methods are associated with the class."},{"text":"

Abstract: declared with a complete implementation.
Virtual: cannot be overridden by subclasses.
Static: belongs to a particular object.

","correct":false,"explanation":"Each relationship is reversed. Abstract methods lack full implementation, virtual methods are designed for subclass overriding, and static methods belong to the class rather than instances."}]},{"id":"5a86df37-d5c5-46fa-8d32-87fcaf51f40b","cardType":"basic","points":2,"front":"Why is composition often more flexible than inheritance?","back":"It avoids rigid class hierarchies by building objects from other objects.","mcqOptions":[{"text":"It avoids rigid class hierarchies by building objects from other objects.","correct":true,"explanation":"Composition combines interchangeable component objects instead of fixing behaviour through an inheritance tree, making responsibilities easier to replace, rearrange or extend independently."},{"text":"It creates deeper class hierarchies by building subclasses from parent classes.","correct":false,"explanation":"Deeper inheritance hierarchies increase structural coupling rather than flexibility. Composition is flexible because it avoids rigid class hierarchies by assembling objects from other objects."},{"text":"It removes all object dependencies by preventing objects from using other objects.","correct":false,"explanation":"Composition does not eliminate dependencies; it deliberately connects collaborating objects. Its flexibility comes from avoiding rigid class hierarchies and allowing component objects to be replaced."},{"text":"It guarantees faster program execution by storing every method in one class.","correct":false,"explanation":"Composition is a design-flexibility technique, not a guarantee of execution speed. It builds objects from other objects to avoid rigid and tightly coupled inheritance hierarchies."}]},{"id":"72445e91-eb29-4ba2-affc-db041d2bfa8d","cardType":"basic","points":2,"front":"Where should likely-changing code be put under “encapsulate what varies”?","back":"Behind a stable method or class boundary.","mcqOptions":[{"text":"Behind a stable method or class boundary.","correct":true,"explanation":"A stable interface isolates changeable implementation details, so code using the method or class can remain unchanged when the variable behaviour is modified."},{"text":"Inside a shared global variable or constant.","correct":false,"explanation":"Global state exposes changeable details and increases coupling rather than encapsulating them. Likely-changing code should sit behind a stable method or class boundary."},{"text":"Within the main program entry point.","correct":false,"explanation":"Placing variable behaviour in the entry point mixes responsibilities and makes changes harder to isolate. It belongs behind a stable method or class boundary."},{"text":"Across several dependent methods and class definitions.","correct":false,"explanation":"Spreading likely-changing behaviour across dependent components makes each change affect more code. Encapsulation instead places it behind one stable method or class boundary."}]},{"id":"8e61e836-9439-4ef3-ba6d-c2cb05d5e5bb","cardType":"cloze","points":null,"front":"In a UML class box, the top compartment contains the [ ]; the middle contains [ ]; the bottom contains methods.","back":"In a UML class box, the top compartment contains the class name; the middle contains attributes; the bottom contains methods.","mcqOptions":[{"text":"In a UML class box, the top compartment contains the class name; the middle contains attributes; the bottom contains methods.","correct":true,"explanation":"The standard three-compartment UML class notation places the class identity first, its stored data second, and its available operations in the bottom compartment."},{"text":"In a UML class box, the top compartment contains the attributes; the middle contains class name; the bottom contains methods.","correct":false,"explanation":"This swaps the first two compartments. Standard UML places the class name at the top, attributes in the middle, and methods at the bottom."},{"text":"In a UML class box, the top compartment contains the class name; the middle contains methods; the bottom contains methods.","correct":false,"explanation":"This duplicates methods and omits the class’s data. The top compartment contains the class name, while the middle contains attributes and the bottom contains methods."},{"text":"In a UML class box, the top compartment contains the object name; the middle contains parameters; the bottom contains methods.","correct":false,"explanation":"This confuses a class diagram with object and parameter notation. A class box places the class name at the top and attributes in the middle."}]},{"id":"3398c682-25c2-4d33-81f5-445f3909bc3f","cardType":"basic","points":3,"front":"What are the UML access symbols for public, private and protected?","back":"

+: public
-: private
#: protected

","mcqOptions":[{"text":"

+: public
-: private
#: protected

","correct":true,"explanation":"UML prefixes public members with +, private members with -, and protected members with #, providing a compact representation of each member’s visibility."},{"text":"

+: private
-: public
#: protected

","correct":false,"explanation":"This reverses public and private visibility. In UML, + marks public members, - marks private members, and # marks protected members."},{"text":"

+: public
-: protected
#: private

","correct":false,"explanation":"This swaps private and protected notation. UML uses + for public access, - for private access, and # for protected access."},{"text":"

+: protected
-: private
#: public

","correct":false,"explanation":"This confuses the public and protected symbols. The UML convention is + for public, - for private, and # for protected visibility."}]},{"id":"461f345b-6403-443f-925b-d49b002cb4ec","cardType":"basic","points":3,"front":"How are aggregation and composition shown in UML, and where is the diamond placed?","back":"

White diamond: aggregation.
Black diamond: composition.
Diamond goes at the whole end.

","mcqOptions":[{"text":"

White diamond: aggregation.
Black diamond: composition.
Diamond goes at the whole end.

","correct":true,"explanation":"UML uses an unfilled diamond for the weaker aggregation relationship and a filled diamond for composition, placing either diamond beside the containing whole."},{"text":"

Black diamond: aggregation.
White diamond: composition.
Diamond goes at the whole end.

","correct":false,"explanation":"This reverses the diamond fills. Aggregation uses a white diamond, composition uses a black diamond, and the diamond is placed at the whole end."},{"text":"

White diamond: aggregation.
Black diamond: composition.
Diamond goes at the part end.

","correct":false,"explanation":"The relationship colours are right, but the endpoint is reversed. UML places the aggregation or composition diamond at the whole, not the component part."},{"text":"

White triangle: aggregation.
Black triangle: composition.
Triangle goes at the whole end.

","correct":false,"explanation":"Triangles are associated with generalisation arrows, not whole-part relationships. Aggregation uses a white diamond and composition a black diamond, both at the whole end."}]}]}],"examCountdown":{"examDate":"2027-06-07","paperLabel":"Paper 1"},"heading":"Programming paradigms","title":"Programming paradigms Flashcards","topbar":{"backHref":"/a-level/computer-science/aqa/flashcards"},"topicSidebar":"$L38"}]}],"topicId":"07bd522b-9fb0-5af3-b83f-8432744d903d","walled":"$L39"}],"$L3a","$L3b"]