DICT 311: Application Programming 311

Lecturer: Dr. Olalekan Samuel Ogunleye

Moderator: Dr Blessings Maoneke

Total Marks: 100

Due Date: May 19th, 2025

Instructions

1. This is not a group assignment project and not an individual project.

2. You are required to conduct further research to be able to perform the task of this
assignment accordingly. However, plagiarism is not allowed in any form. Your code
will be subjected to a plagiarism check. All the group members will be awarded zero if
it is found that they have plagiarised.
3. This assignment could be time-consuming and require dedicated effort. You only have
5 days to work on this project. It is about building a simple functional system while
incorporating the fundamental knowledge and understanding of the Android Kotlin
framework.
4. You must add a plagiarism declaration to your submission, where you will declare that
your submission is not plagiarized. You must sign the declaration.
5. The project deadline is sacrosanct. This deadline will not be extended.
6. This project will contribute 17.5%, tests and other formative assessments will
contribute 33.5%, and the examination will carry 50% toward the final Mark.
Therefore, you are advised to take the project seriously.
7. Project documentation of not less than two pages should accompany the submission.
This should be submitted online.
8. You will not need to present this assignment. However, a short video of how your
system works is needed.
9. Should you require further clarification on this assignment, a physical class is required
and can be scheduled.
Project Brief
As an enterprise software developer, you just joined Dudu and Masuku (D&M) Software
Development Company. The University of Mpumalanga has contracted your company to
manage the institution's information system implementation. In your first task on your first day
of work in your company, you are required to develop a simple Task Management System that
the institution's students can use to manage their simple daily tasks. You are required to develop
a simple Task Management App using Android and Kotlin. The app should allow users to add,
display, and delete tasks. The application should incorporate object-oriented programming,
event handling, networking, and multimedia features.
The table below Highlights what must be developed based on the above brief.
1.1) Project Setup and UI Design (10)
- Design a basic UI in Android Kotlin with:
- An EditText for entering tasks.
- A RecyclerView for displaying tasks.
- A Button to add new tasks.
- A Button to delete completed tasks.
1.2) Implementing an Object-Oriented Approach (15)
- Create a Task class with properties (title, description, and completion status).
- Implement a TaskManager class that manages task storage and retrieval.
- Use a ViewModel for data persistence
1.3) Implementing Event Handling in Android (15)
- Add a click event listener to handle task addition.
- Add an event listener for marking a task as completed.
- Implement a long-press listener to delete tasks.
1.4) Basic Graphics and Multimedia Support (15)
- Add an image next to each task to indicate completion status.
- Play a notification sound when a task is added.
- Display a toast message when a task is deleted.
1.5) Developing a Network-Supported Feature (15)
- Implement AsyncTask or Kotlin Coroutines to fetch task suggestions from an
API.
- Use HttpURLConnection or Retrofit to send a request and display the
response.
1.6) Sending Emails and SMS Notifications (15)
- Implement a feature to send an email when a task is overdue.
- Implement a feature to send an SMS reminder for incomplete tasks. (4)
1.7) Implementing Database Features (15)
- Store tasks using the Room Database for persistence. (3)
- Implement Dark Mode support for the app. (3)
- Add a search bar to filter tasks by title. (3)
Assignment Rubric

Your Project assignments will be graded according to the following Rubric.

Focus Area Description Marks

Completeness This score will be 30%
determined by the result of
running a series of automated
tests on your code. The tests
check whether your code
implements the tasks you are
asked to implement in the
project and, thus, are a good
measure of how complete
your code is. You can run
these tests yourself and,
therefore, know your
Completeness score before
you submit your assignment.
Correctness This score encompasses 25%
issues with your code that,
while not explicitly captured
by the tests, could lead to
incorrect behaviour (or
simply neglect to implement
something you were told to
implement). I will usually
provide hints on what is
being looked out for in this
rubric component. Please
note that this rubric section
will never re-penalize you
for a failure already captured
by the tests. So, if your code
fails to implement something
we told you to implement,
but the tests already capture
that, we would not re-
penalize you here.
Design This score will be 25%
determined by "qualities,
many of which are
intangible, that don't have to
do with (and exist to some
extent independently of) the
correct operation of your
code." For example, you will
have to decompose your
code into multiple functions,
where that decomposition is
 up to you. Whether your
decomposition makes sense
and is well-designed will be
evaluated in this score.
Style The following will be looked 20%
at generally in awarding the
marks:

Documenting functions:
Every function you write
must document what the
function performs and what
it is doing.

Clarity: Your code must be

easy to read and understand.
This is a fairly subjective
aspect, but common
deductions for lack of clarity
include using variables
without descriptive names,
writing convoluted code that
would be easier to
understand with more code
comments, using magic
numbers, etc.
Total 100%
Note that submitting broken code (i.e., code with syntax errors or, generally, code that
cannot be run) will receive an automatic 40-Marks penalty (out of 100 possible points).
Please note that if your code is so broken that it cannot work with a few simple fixes, it
will not get graded, and you will receive a zero on the project assignment.