Draft - Library vs Custom Collections in a Backend Feature
Authoring skeleton - backend focus (CS113 backend collections)
Three short topics
- Trace a backend feature and list the collections it uses.
- Library structure vs from-scratch implementation: when each is justified.
- Document the choice and its cost.
PBL context
Extend a project work queue or service feature and document where a library structure was used versus implemented.
Backend layers to author
- Trace the existing feature and name each collection and why.
- Use a collection API to extend it.
- Implement and test one selected structure from scratch.
- Write a short justification with operation counts.
Evidence checklist to author
Same tests pass against the library and custom versions; students explain one trade-off using counted operations, not timing.
Publication checklist
Complete examples, a CodeRunner exercise, and tests before removing the draft/hide flags, enabling submissions, or confirming the course and week.
Code Runner Challenge
Authoring draft - backend collection choice exercise is not ready
View IPYNB Source
// CODE_RUNNER: Authoring draft - backend collection choice exercise is not ready
public class CollectionChoiceDraft {
public static void main(String[] args) {
throw new UnsupportedOperationException("Draft: author the trace, extension, and tests before publication.");
}
}
CollectionChoiceDraft.main(null);
Lines: 1
Characters: 0
Output
Click "Run" in code control panel to see output ...