Task 3 Three-Week Assessment Instructions
Student Details
| Item | Response |
|---|---|
| Name | |
| Class | |
| Date | |
| Database/List name |
Assessment Conditions
| Item | Details |
|---|---|
| Course | Year 12 Computer Science General |
| Unit | Unit 3 - Developing computer-based systems and producing spreadsheet and database solutions |
| Assessment type | Practical test |
| Weighting | 7.5% |
| Raw mark | 50 |
| Assessment window | Term 2 Weeks 5-7 database lesson sequence |
| Final submission | End of Week 3 as directed in the LMS |
| Tool | Microsoft Lists in a web browser |
Task 3 is assessed through the three database lesson weeks. There is no separate one-day assessment after the sequence. You must submit your own final database evidence. Your teacher may teach skills, run checkpoints and clarify instructions, but they cannot build the database for you or make final design decisions for you.
Three-Week Assessment Plan
| Week | Assessment focus | Required checkpoint |
|---|---|---|
| Week 1 | Database foundation | Microsoft List, fields, data types, LoanID, sample records |
| Week 2 | Database outputs and interface | Query views, report views, form/interface evidence |
| Week 3 | Documentation and submission | Evidence document, Excel export, share link, final checklist |
Scenario
The King's College needs a simple database to track equipment loans. Staff lend items such as laptops, chargers, cameras, microphones, cables, adapters and tripods to students. Staff need to know:
- who borrowed each item
- when it was borrowed
- when it is due back
- whether it has been returned
- what condition the item was in
- whether any item needs follow-up
Your task is to build and document a single-table database solution for this scenario.
Part A: Create the Database
Create one Microsoft List named:
Task 3 Equipment Loans - Firstname Lastname
This one Microsoft List is your single database table.
Your database must include at least 10 suitable fields. You may use the suggested fields below or closely equivalent fields.
| Field name | Required? | Suggested Microsoft Lists column type | Purpose |
|---|---|---|---|
| LoanID | Yes | Single line of text | Unique identifier for each loan record |
| ItemName | Yes | Single line of text | Name of the equipment item |
| Category | Yes | Choice | Type of equipment |
| BorrowerName | Yes | Single line of text | Person borrowing the item |
| YearLevel | Yes | Choice or Number | Year group of borrower |
| DateBorrowed | Yes | Date and time | Date the item was borrowed |
| DueDate | Yes | Date and time | Date the item should be returned |
| Returned | Yes | Yes/No | Whether the item has been returned |
| DateReturned | No | Date and time | Return date if returned |
| ConditionOut | Yes | Choice | Condition when borrowed |
| ConditionIn | No | Choice | Condition when returned |
| ReplacementCost | No | Currency | Approximate replacement cost |
| Notes | No | Multiple lines of text | Extra information or follow-up notes |
Part B: Use a Primary Key Equivalent
Use LoanID as the primary key equivalent.
It must be:
- required
- unique
- stable
- easy to read
Recommended format:
LOAN-001, LOAN-002, LOAN-003
If the option to enforce unique values is not available in your Microsoft Lists settings, keep all LoanID values unique and explain this in your documentation.
Part C: Enter Sample Records
Enter at least 12 realistic equipment loan records.
Your records must include:
- returned and unreturned loans
- at least two overdue loans
- at least one damaged item or follow-up item
- a mix of equipment categories
- consistent category and condition values
Part D: Create Query Views
Create at least 4 saved query views. A query view is a saved view that filters, sorts, groups or selects records to answer a useful question.
Recommended views:
| View name | Required logic |
|---|---|
| Current Loans | Shows items where Returned is No |
| Overdue Loans | Shows unreturned items where DueDate is before today |
| Year 12 Loans | Shows loans for Year 12 borrowers |
| Loans by Category | Groups or filters loans by equipment category |
| Damaged or Follow Up | Shows damaged items or records needing follow-up |
Part E: Complete Microsoft Lists View Evidence
Complete the Microsoft Lists view evidence item provided with this assessment.
You will need to show that your saved views work as database queries by using:
- filters
- sorting
- grouping
- selected visible columns
- clear view names
The view evidence is marked inside the Query Views and Microsoft Lists View Evidence criterion.
Part F: Create Report Views
Create at least 2 report-style views. A report view should be readable for a staff member and suitable for screenshot, print or PDF evidence.
Recommended report views:
| Report view | Required design focus |
|---|---|
| Weekly Loan Summary | Shows key fields, grouped or sorted so staff can review current loans |
| Replacement Cost Review | Shows damaged, expensive or follow-up items with useful fields visible |
Part G: Improve the Visual Interface
Your database should be usable for a staff member.
Evidence may include:
- clear database/list name
- meaningful view names
- logical column order
- important columns visible in each view
- hidden unnecessary columns in report views
- a logical new/edit item form
- choice fields that reduce inconsistent typing
Part H: Complete Database Documentation
Complete the Task 3 Database Documentation Template.
Your documentation must explain:
- database purpose
- intended users
- table/list structure
- data dictionary
- primary key choice
- form design
- query views
- report views
- visual interface choices
- testing, limitations and improvements
Final LMS Submission
Submit the following three items through the LMS:
CSCGT_Task3_2026_Surname_FirstName_Evidence.docxCSCGT_Task3_2026_Surname_FirstName_DataExport.xlsx- Microsoft Lists share link pasted into the LMS submission comment box
Your evidence document must show:
- Microsoft List/database structure
LoanIDfield and unique values- sample records
- data entry form
- 4 query views
- Microsoft Lists view evidence response
- 2 report views
- completed database documentation
- final checklist
Your Excel export must show your submitted records and field names. Your share link must remain available to your teacher until marking and any moderation checks are complete.
Final Quality Check
Before submitting, check that a teacher can see what you built without needing you to explain it verbally.
- Field names are clear.
- Data types are suitable.
LoanIDvalues are unique.- Saved views are actually saved.
- Report views are readable.
- Documentation describes your actual database, not just definitions.
- Evidence document, Excel export and LMS share link have all been submitted.