| Category |
Assignment |
Subject |
Business |
| University |
|
Module Title |
|
BBIS 5101 Assignment 3: Development and Documentation (Campus Facilities Issue Register)
| Course |
BBIS 5101 Introduction to Object Oriented Programming |
| Term |
2607 term (brief v3.4, October 2026) |
| Assessment |
Assignment 3 – individual: structured report, Visual Studio C# solution (ZIP with LocalDB files) and application demonstration |
| Weighting |
40% of final grade; 100 marks; pass mark 50/100 (C-) |
| Learning outcomes |
LO2 and LO3 |
| Due |
See Canvas LMS |
This assignment asks business information systems students to design, build, test and document a small object-oriented Windows Forms application in C# for a case company: a tertiary provider that needs a Campus Facilities Issue Register to replace manual records of faulty lighting, damaged furniture and other maintenance problems.
Learning Outcomes Assessed
- LO2: Apply software engineering principles to analyse and solve problems related to business.
- LO3: Design and implement, including testing and debugging, basic object-oriented programs as they apply to business using a contemporary programming language.
Case Briefing: Campus Facilities Issue Register
Facilities staff must be able to add, view, update and delete issues, and search or filter by location, category or status. Each issue may record: Issue ID, Location, Issue Category, Description, Date Reported, Priority (Low/Medium/High), Status (Open/In Progress/Resolved) and Reported By. Suggested business rules: location and description must not be empty; priority and status must come from the set lists; the date reported cannot be in the future. User accounts, multiple related tables, technician workflows, email notifications, scheduling, costs and dashboards are outside scope.
Minimum Application Requirements
- C# and Windows Forms (WinForms) user interface, unless written approval is given for another UI framework.
- Add, View, Edit and Delete functionality and at least one working search or filter feature.
- SQL Server LocalDB database (.mdf) with one main table, accessed using basic ADO.NET; records displayed in a DataGridView.
- At least two interacting custom C# classes (excluding Form classes) with meaningful responsibilities, demonstrating encapsulation.
- Separation of business logic from UI code where appropriate; basic input validation; at least three business rules; testing and debugging.
- Evidence in the report: screenshots of CRUD operations, validation messages and search results, plus short annotated code excerpts.
Task 1: Planning and Design Blueprint (20 marks)
- 1.1 Business purpose and functional requirements (5): business context in 5–8 sentences; feature list covering CRUD and search/filter; at least three rules written as Rule # – Field – Condition – User Message.
- 1.2 Data design (5): table of 6–10 fields with C# type, database type, required flag and example value; primary key and whether it is auto-generated.
- 1.3 Class design (5): at least two custom classes with fields, properties and key methods, plus a simple diagram and responsibilities.
- 1.4 User interface planning (5): labelled main form sketch and a control mapping table (control type, name, linked field, purpose).
Task 2: Application Implementation (50 marks)
- 2.1 Project structure and class implementation (15): private fields, properties/methods, logic kept out of the Form where appropriate.
- 2.2 Database integration (15): .mdf database, one table matching Task 1, Insert/Select/Update/Delete, DataGridView display.
- 2.3 Functional features and validation (10): all CRUD, search/filter, three validation rules enforced before SQL runs, meaningful error messages.
- 2.4 User interface and usability (10): suitable controls, naming conventions (txtName, btnAdd), clear layout, refreshed data and cleared inputs.
Task 3: Testing and Debugging (15 marks)
- 3.1 Test case table (5): at least eight cases including two valid, two invalid and one boundary test, covering CRUD, search and validation.
- 3.2 Validation and error-handling evidence (5): two or more validation screenshots and a short explanation of how rules are enforced.
- 3.3 Debugging example (5): one genuine bug in 150–250 words – the problem, its cause, how it was found and how it was fixed.
Task 4: Demonstration of Application (15 marks)
- 4.1 Application demonstration (10): launch, database connection, add, view, update, delete, search/filter and at least one validation rule.
- 4.2 Code explanation (5): main classes, encapsulation, CRUD implementation, validation and the data connection; narrated if recorded.
hfgjhf
