https://wiki.kram.nz/index.php?action=history&feed=atom&title=Talk%3ASE250%3AHTTB%3AWIP%3ATrade-offsTalk:SE250:HTTB:WIP:Trade-offs - Revision history2026-06-04T15:13:43ZRevision history for this page on the wikiMediaWiki 1.45.3https://wiki.kram.nz/index.php?title=Talk:SE250:HTTB:WIP:Trade-offs&diff=13782&oldid=prevMark: 7 revision(s)2008-11-03T10:43:35Z<p>7 revision(s)</p>
<p><b>New page</b></p><div>==General Direction==<br />
'''Notes from John's lecture on the HTTB Specific to Trade-offs''' (A combination of my own notes and from [[SE250:May_26]])<br />
<There is no one “best” data structure to use <br />
Hashing generally is a good bet<br />
Use of cache<br />
○ Data too big can screw over the memory<br />
· Keep data contiguous in memory<br />
· Sometimes not so clear cut<br />
○ Linked lists vs array based lists (with short list)<br />
§ LL<br />
□ Memory overhead ie storing of next position<br />
§ Array<br />
□ More time taken for putting at a particular position especially when having to realloc<br />
· Searching<br />
○ State based search<br />
§ Naïve methods<br />
□ Breadth-first, depth-first<br />
¨ Brute force becomes exponential <br />
§ Smarter methods<br />
□ Knowing about your problem with direction and more programming cost<br />
· Bother to sort out data for things such as Lists<br />
· Memory trade offs<br />
· 50:1 for use of main memory ? (must have been a distracted for a second to get what this was on about --[[User:Jhor053|Jhor053]] 20:29, 5 June 2008 (NZST))<br />
· Have a Trade-off table<br />
○ Use of Big O notation and theory<br />
· Is it worth keeping the data sorted?<br />
○ Ie taking time to insert takes longer<br />
○ But getting data takes far less longer<br />
· Ignore metrics<br />
· Bit more condensed<br />
· Look at macro vs. micro level<br />
<br />
'''Notes from John's lecture on the HTTB Generally''' (A combination of my own notes and from [[SE250:May_26]])<br />
· Expecting 10 hours a week (that leaves 4 hours for HTTB and study)<br />
· Not compared to last years and dont copy from Last years one too<br />
· 15% to mark<br />
· Show Done in depth <br />
· To a polished level<br />
· Too much for the notes<br />
○ Tight and concise<br />
○ Visual and discussions in screen casts<br />
○ Concentrate on the screencasts (John more interested in these and recommended these)<br />
· Finished by (lectures end of 6th) the 6th June officially due to study for exams<br />
○ Can do during weekend of 7-8th June<br />
· Send off a summary of your HTTB submissions (to Johns email?)<br />
· Marked before exam on 26th of June<br />
· A lot of the material was from outside of lectures<br />
○ A little beyond is fine<br />
○ But easy to over do which is too much<br />
○ Be careful<br />
· A member of the class Suggested to consider basing it the HTTB on the labs and John Agreed this is good idea<br />
<br />
==What to have for sections?==</div>Mark