Last updated: September 2026 · Reviewed by the Punjab Assignment Help programming team · Reading time: 10 minutes
Quick answer: BBIS 5101 Introduction to Object-Oriented Programming, Assignment 2 ("Solution Planning & AI-Assisted Pair Programming"), asks you and your partner to keep a Pair Programming and AI-Assisted Development Log throughout the assignment. The completed log goes in your report's appendix. It must show at least one session in each of three working modes (Individual + AI, Human–human, Human–human–AI), rotation of driver and navigator roles, and every key decision where an AI suggestion was accepted, modified or rejected, with the reason.
BBIS 5101 Assignment 2 key facts
| Item | Detail |
|---|---|
| Paper | BBIS 5101 Introduction to Object-Oriented Programming (Bachelor of Business Information Systems, New Zealand) |
| Assessment | Assignment 2: Solution Planning & AI-Assisted Pair Programming |
| Format | Pair work (Student A and Student B), with the development log in the report appendix |
| Log columns | Date/Session · Task/Feature · Working Mode · Student A Role/Contribution · Student B Role/Contribution · AI Use · Key Decision/Outcome |
| Minimum evidence | 1× Individual + AI, 1× Human–human, 1× Human–human–AI, role rotation, AI accept/modify/reject decisions |
The three working modes explained
| Mode | What happens | Best used for |
|---|---|---|
| Individual + AI | Each student works alone and may use an AI assistant to explore an initial solution | Understanding the problem, drafting a first class design or pseudocode, learning syntax |
| Human–human | Both students work together without AI. One is driver (types), the other navigator (reviews, thinks ahead, spots bugs) | Agreeing the final design, writing core logic, debugging by reasoning |
| Human–human–AI | Driver and navigator work together and ask AI to review, explain or refine. The humans make every final decision | Code review, testing ideas, refactoring, explaining error messages |
Answer hint: a sample completed log
This is an illustrative example for a simple OOP task (a library-loan system). Build your own log from your actual sessions.
| Session | Task / Feature | Mode | Student A | Student B | AI use | Key decision / outcome |
|---|---|---|---|---|---|---|
| S1 – Week 1 | Analyse brief, identify classes | Individual + AI | Drafted nouns/verbs list, asked AI to explain composition vs inheritance | Drafted own class list separately | Concept explanation only | Compared both lists and kept the Book, Member and Loan classes |
| S2 – Week 1 | Class diagram and pseudocode | Human–human | Driver: drew UML in draw.io | Navigator: checked multiplicities against the brief | None | Decided Loan links Member and Book (1 Member → many Loans) |
| S3 – Week 2 | Implement Book and Member classes | Human–human | Navigator: reviewed encapsulation | Driver: wrote constructors, getters and setters | None | Made fields private and added validation in setters |
| S4 – Week 2 | Loan logic and due-date calculation | Human–human–AI | Driver | Navigator | Asked AI to review the method for edge cases | Modified: accepted the null-check idea, rejected AI's use of an external library (beyond paper scope) |
| S5 – Week 3 | Testing and refactoring | Human–human–AI | Navigator: wrote test cases | Driver: ran tests and fixed failures | AI explained an exception message | Accepted the explanation, fixed the loop boundary error ourselves |
Notice: roles swap between sessions (A drives in S2 and S4, B drives in S3 and S5), all three modes appear, and every AI interaction records what was asked and what the pair decided.
How to write strong "Key Decision" entries
Weak: "Used AI to fix code." Strong: "AI suggested replacing our for loop with a stream. Rejected, because we had not covered streams in class and the navigator could not explain it. We kept the loop and added a comment." Markers want to see that you understood and controlled the AI output.
Use this formula: AI suggestion → Decision (Accepted / Modified / Rejected) → Reason → Result.
Solution planning hints (the rest of Assignment 2)
- Problem analysis: restate the requirements in your own words and list inputs, processes and outputs.
- Class design: identify classes from nouns and methods from verbs. Apply encapsulation (private fields), constructors, and inheritance only when there is a real "is-a" relationship.
- UML class diagram: show attributes (with types), methods, visibility (+ / −) and relationships with multiplicities.
- Pseudocode or flowcharts: plan each method's logic before coding (sequence, selection, iteration).
- Proof of concept: a small working program that tests the riskiest part of your design.
- Test plan: a table of test case, input, expected result, actual result and pass/fail, including edge cases (empty input, negative numbers, duplicates).
Common mistakes that lose marks
- Filling in the log the night before submission. It should be completed throughout, with realistic dates.
- Only one student ever acts as the driver.
- No Human–human session at all (both students used AI every time).
- AI column says "yes" with no detail of prompt purpose or outcome.
- Submitting AI-generated code neither student can explain in a follow-up interview.
Struggling with OOP concepts or your class diagram?
Our programming tutors support BBIS students in Auckland and across New Zealand with classes, objects, inheritance, UML and debugging, so you can explain every line of your own code.
WhatsApp "BBIS5101" for a free log checklist Get a free quote
BBIS 5101 Assignment 2 answer hints, sample log and solution planning help
Students often search for BBIS 5101 Assignment 2 answers or a BBIS 5101 sample log. There is no single correct answer to copy, because the log must record your own pair sessions, and markers compare it with your code and your viva or interview. What does exist is a correct pattern. The answer hints above, the sample library-loan log and the Key Decision formula show that pattern. Follow it with your real sessions and you will meet every completion requirement.
Quick recap of the answer hints: log at least one session per working mode, swap driver and navigator every session, record each AI prompt and whether you accepted, modified or rejected the suggestion, and attach the log to the appendix of your Assignment 2 report.
Where can I find BBIS 5101 Assignment 2 answers?
There is no official answer sheet, because each pair logs its own sessions. Use the answer hints and sample log on this page as a model, then record your real sessions. Our tutors can review your draft log and class design before submission.
Is there a BBIS 5101 pair programming log example?
Yes. The sample log above shows five sessions across all three working modes with driver and navigator rotation and accept/modify/reject AI decisions. Treat it as a format guide only.
Can I get BBIS 5101 help in Auckland or online?
Yes. Punjab Assignment Help offers one-to-one online programming tutoring for BBIS students in Auckland and across New Zealand, covering classes, inheritance, UML and debugging.
Frequently asked questions
What is the difference between the driver and the navigator in pair programming?
The driver controls the keyboard and writes the code. The navigator reviews each line, thinks about the overall design, spots errors and suggests next steps. Pairs should swap roles regularly.
What are the three working modes in the BBIS 5101 log?
Individual + AI (each student works alone with optional AI help), Human–human (both students together, no AI) and Human–human–AI (both students together, using AI to review or explain while keeping final decisions).
How do I record AI use in the development log?
For each session, note what you asked the AI and why, then record whether you accepted, modified or rejected its suggestion and the reason.
Where does the completed log go?
In the appendix of your Assignment 2 report.
How many sessions do I need?
At least one session in each of the three modes, with driver and navigator roles rotating between both students. More sessions give stronger evidence of collaboration.
Related help
Academic integrity note: the sample log is illustrative only. Your log must honestly record your own sessions, and your use of AI must follow your institution's policy.