NAME: | Yvette Colomb | ||
PROJECT TITLE: | Possible Android Permission Security Flaw with Google APIs | ||
WEEK NO: | 12 | DATE: 29 Jan 2018 | |
PLANNING | |||
MILESTONE: | PLANNED: | ACTUAL: | COMMENT: |
Continue Research project into the future | After exams | TBA | |
Complete seminar | 29/1/2018 | 27/1/2018 | |
TASKS | |||
DESCRIPTION: | DATE: | ACTION/RESULTS: | FINISHED (Y/N) |
Record presentation | Mon – Fri | Already done | Y |
Upload presentation to YouTube | Done | Done 27/1/2018 | Y |
Publish project report | Mon | Automatically scheduled | Y |
Update project report | Mon – Fri | Y | |
ISSUES | |||
DESCRIPTION | DATE | ACTION/RESULTS | FINISHED (Y/N) |
Difficulty of squeeze in timeframe | Juggled tasks to meet deadline, saved by slack in project timeline | Y |
All posts by Yvette Colomb
Weekly Progress Report 11
NAME: | Yvette Colomb | ||
PROJECT TITLE: | Possible Android Permission Security Flaw with Google APIs | ||
WEEK NO: | 11 | DATE: 22 Jan 2018 | |
PLANNING | |||
MILESTONE: | PLANNED: | ACTUAL: | COMMENT: |
Study week 11 topic | Mon | Mon | all good |
Research in background | any | Nil | No time, will have to wait until after exams. |
Work on Presentation | Daily | running behind | Finished 27/1/2018 |
TASKS | |||
DESCRIPTION: | DATE: | ACTION/RESULTS: | FINISHED (Y/N) |
Attend chat | Mon | Watch recording | Y |
Read topic notes | Mon | Y | |
Watch topic lecture | Mon | Y | |
Complete presentation | Daily | working on it | Y |
Publish project report | Mon | Automatically scheduled | Y |
Update project report | Mon – Fri | Y | |
ISSUES | |||
DESCRIPTION | DATE | ACTION/RESULTS | FINISHED (Y/N) |
Time frame squeeze | 27/1/2018 | Still balancing tasks to meet deadlines, following illness. | Y |
Weekly Progress Report 10
NAME: | Yvette Colomb | ||
PROJECT TITLE: | Possible Android Permission Security Flaw with Google APIs | ||
WEEK NO: | 10 | DATE: 15 Jan 2018 | |
PLANNING | |||
MILESTONE: | PLANNED: | ACTUAL: | COMMENT: |
Study week 10 topic | Mon | Mon | all good |
Research in background | Nil | Nil | issues |
Online quiz | Done | Done early | Not as good as hoped. |
Work on presentation | Running late | Not done | |
TASKS | |||
DESCRIPTION: | DATE: | ACTION/RESULTS: | FINISHED (Y/N) |
Attend chat | Mon | Listen recording | Y |
Read topic notes | Mon | Y | |
Watch topic lecture | Mon | Y | |
Study for quiz | Before quiz | Not effective | Y |
Complete quiz | 8/1/2018 | done 8/1/2018 | Y |
Publish project report | Mon | Automatically scheduled | Y |
Update project report | Mon – Fri | Y | |
ISSUES | |||
DESCRIPTION | DATE | ACTION/RESULTS | FINISHED (Y/N) |
Recovering from time squeeze due to illness | Juggling tasks between subjects. Keeping on top of deadlines.
Accepting lower grades, as in risk analysis. |
N |
Weekly Progress Report 9
NAME: | Yvette Colomb | ||
PROJECT TITLE: | Possible Android Permission Security Flaw with Google APIs | ||
WEEK NO: | 9 | DATE: 08 Jan 2018 | |
PLANNING | |||
MILESTONE: | PLANNED: | ACTUAL: | COMMENT: |
Study week 9 topic | Mon | Mon | all good |
Research in background | any | daily | Delayed |
TASKS | |||
DESCRIPTION: | DATE: | ACTION/RESULTS: | FINISHED (Y/N) |
Attend chat | Mon | Listen recording | Y |
Read topic notes | Mon | Y | |
Watch topic lecture | Mon | Y | |
Publish project report | Mon | Automatically scheduled | Y |
Update project report | Mon – Fri | Y | |
ISSUES | |||
DESCRIPTION | DATE | ACTION/RESULTS | FINISHED (Y/N) |
Running late due to illness and recovery | Had allowed provision for this in slack. | N |
Weekly Progress Report 8
NAME: | Yvette Colomb | ||
PROJECT TITLE: | Possible Android Permission Security Flaw with Google APIs | ||
WEEK NO: | 8 | DATE: 01 Jan 2018 | |
PLANNING | |||
MILESTONE: | PLANNED: | ACTUAL: | COMMENT: |
Study week 8 topic | Mon | Mon | all good |
Complete Annotated bibliography | Mon | Late | see issue |
Research in background | any | Late | see issue |
TASKS | |||
DESCRIPTION: | DATE: | ACTION/RESULTS: | FINISHED (Y/N) |
Attend chat | Mon | No | N |
Read topic notes | Mon | No | N |
Watch topic lecture | Mon | No | N |
Finish summaries | Sun | N | |
Finish evaluations | Sun, Mon | N | |
Publish project report | Mon | Automatically scheduled | Y |
Update project report | Mon – Fri | Late | Y |
ISSUES | |||
DESCRIPTION | DATE | ACTION/RESULTS | FINISHED (Y/N) |
Sickness prevented work. | 2/1/2018 | special consideration | Y |
Weekly Progress Report 7
NAME: | Yvette Colomb | ||
PROJECT TITLE: | Possible Android Permission Security Flaw with Google APIs | ||
WEEK NO: | 7 | DATE: 25 Dec 2017 | |
PLANNING | |||
MILESTONE: | PLANNED: | ACTUAL: | COMMENT: |
Break | Until 27th December | ||
Choose references for annotated bibliography | Dec 28, 2017 | Dec 28, 2017 | No issues, highly organised process. |
TASKS | |||
DESCRIPTION: | DATE: | ACTION/RESULTS: | FINISHED (Y/N) |
Shortlist references | Dec 28, 2017 | done | Y |
Gather full text | Dec 28, 2017 | done/ using library proxy | Y |
Read References | Dec 28, 2017 | done | Y |
Choose references | Dec 28, 2017 | done | Y |
Publish project report | Mon | Automatically scheduled | Y |
Update project report | Mon – Fri | done | Y |
ISSUES | |||
DESCRIPTION | DATE | ACTION/RESULTS | FINISHED (Y/N) |
No issues |
Weekly Progress Report 6
No issues
NAME: | Yvette Colomb | ||
PROJECT TITLE: | Possible Android Permission Security Flaw with Google APIs | ||
WEEK NO: | 6 | DATE: 18 Dec 2017 | |
PLANNING | |||
MILESTONE: | PLANNED: | ACTUAL: | COMMENT: |
Break | until 27th December | done | |
Weekly Progress Report 5
NAME: | Yvette Colomb | ||
PROJECT TITLE: | Possible Android Permission Security Flaw with Google APIs | ||
WEEK NO: | 5 | DATE: 11 Dec 2017 | |
PLANNING | |||
MILESTONE: | PLANNED: | ACTUAL: | COMMENT: |
Complete 4 Annotated Bibliography items | Mon – Tues | delayed | Have another assessment due for another subject, need to delay |
Study week 5 topic | Mon | Mon | all good |
TASKS | |||
DESCRIPTION: | DATE: | ACTION/RESULTS: | FINISHED (Y/N) |
Attend chat | Mon | Listened Tues | Y |
Read topic notes | Mon | Y | Y |
Watch topic lecture | Mon | Y | Y |
Select 4 sources | Mon | Selected 4 sources | Y |
Write up annotations | Mon – Fri | behind | N |
Publish project report | Mon | Automatically scheduled | Y |
Update project report | Mon – Fri | Y | |
ISSUES | |||
DESCRIPTION | DATE | ACTION/RESULTS | FINISHED (Y/N) |
No issues |
Checklist
Is the capstone topic area appropriate?
The capstone topic area is appropriate. It is about the latest in Android applications and concerns security, which is also a growing area of interest.
Has the Project Blog been setup?
Yes.
Has there been sufficient justification of the choice of the topic?
The justification is discovering an area of weakness within the Google APIs that can assist in circumventing dangerous permission. This is relevant to todays technologies and for the future.
Is there enough scope for a sufficiently deep/complex analysis?
There’s considerable research in the areas of Android security and permissions. The greatest challenge is creating a program to hack these security measures.
Is the scope appropriate for what might be reasonably expected in the capstone project subject?
The scope is appropriate, it is a professional level topic. It is too long to complete the research within the time frame of the subject. This is no issue, as the project closure section of the syllabus can be presented as a final project report for that time period.