mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-24 13:24:05 -06:00
auto update
This commit is contained in:
Jet Hughes
parent
e9b21050f2
commit
1dc978bd1c
3
.obsidian/app.json
vendored
3
.obsidian/app.json
vendored
@ -1,3 +1,4 @@
|
||||
{
|
||||
"alwaysUpdateLinks": true
|
||||
"alwaysUpdateLinks": true,
|
||||
"promptDelete": false
|
||||
}
|
||||
17
.obsidian/workspace
vendored
17
.obsidian/workspace
vendored
@ -7,11 +7,8 @@
|
||||
"id": "a12701fbd6d13db8",
|
||||
"type": "leaf",
|
||||
"state": {
|
||||
"type": "markdown",
|
||||
"state": {
|
||||
"file": "content/_index.md",
|
||||
"mode": "source"
|
||||
}
|
||||
"type": "empty",
|
||||
"state": {}
|
||||
}
|
||||
}
|
||||
],
|
||||
@ -68,7 +65,6 @@
|
||||
"state": {
|
||||
"type": "backlink",
|
||||
"state": {
|
||||
"file": "content/_index.md",
|
||||
"collapseAll": false,
|
||||
"extraContext": false,
|
||||
"sortOrder": "alphabetical",
|
||||
@ -88,8 +84,13 @@
|
||||
},
|
||||
"active": "a12701fbd6d13db8",
|
||||
"lastOpenFiles": [
|
||||
"content/notes/analysis-of-recursive-algorithms.md",
|
||||
"content/notes/approches-to-systems-development.md",
|
||||
"content/_index.md",
|
||||
"content/203-human-computer-interaction.md",
|
||||
"content/notes/index.md"
|
||||
"content/notes/troubleshooting.md",
|
||||
"notes/hosting.md",
|
||||
"out/notes/201-information-systems.md",
|
||||
"content/notes/index.md",
|
||||
"content/203-human-computer-interaction.md"
|
||||
]
|
||||
}
|
||||
5
content/notes/2 UML.md
Normal file
5
content/notes/2 UML.md
Normal file
@ -0,0 +1,5 @@
|
||||
# UML
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,9 +0,0 @@
|
||||
---
|
||||
title: 2 UML
|
||||
draft: true
|
||||
---
|
||||
# UML
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,29 +1,25 @@
|
||||
---
|
||||
title: 201 Algorithms and data structures
|
||||
draft: true
|
||||
---
|
||||
# COSC201 - Algorithms and Data Structures
|
||||
## 1 Lectures
|
||||
- [Merge sort - divide and conquer](out/notes/merge-sort-divide-and-conquer.md)
|
||||
- [Lecture 8 Merge sort 2](out/notes/lecture-8-merge-sort-2.md)
|
||||
- [Lecture 9 Stacks queues and heaps](out/notes/lecture-9-stacks-queues-and-heaps.md)
|
||||
- [Lecture 10 Heaps and heap sort](out/notes/lecture-10-heaps-and-heap-sort.md)
|
||||
- [[Merge sort - divide and conquer]]
|
||||
- [[Lecture 8 Merge sort 2]]
|
||||
- [[Lecture 9 Stacks queues and heaps]]
|
||||
- [[Lecture 10 Heaps and heap sort]]
|
||||
|
||||
## 2 Notes
|
||||
### 2.1 Algorithm Complexity
|
||||
- [Big-O](out/notes/big-o.md)
|
||||
- [Big theta](out/notes/big-theta.md)
|
||||
- [Induction](out/notes/induction.md)
|
||||
- [analysis of recursive algorithms](out/notes/analysis-of-recursive-algorithms.md)
|
||||
- [[Big-O]]
|
||||
- [[Big theta]]
|
||||
- [[Induction]]
|
||||
- [[analysis of recursive algorithms]]
|
||||
|
||||
### 2.2 Algorithms
|
||||
- [Minimal spending tree](out/notes/minimal-spending-tree.md)
|
||||
- [Union Find-Disjoint set](out/notes/union-find-disjoint-set.md)
|
||||
- [[Minimal spending tree]]
|
||||
- [[Union Find-Disjoint set]]
|
||||
-
|
||||
### 2.3 Fundamental Data structures
|
||||
- [Objects](out/notes/objects.md)
|
||||
- [[Objects]]
|
||||
- Stacks queues, List/arrays
|
||||
- [Union Find-Disjoint set](out/notes/union-find-disjoint-set.md)
|
||||
- [[Union Find-Disjoint set]]
|
||||
- Graphs and networks
|
||||
- Priority queue (heap)
|
||||
- Weighted
|
||||
@ -33,7 +29,7 @@ draft: true
|
||||
- Sets (Unstructured) (no repetition allowed)
|
||||
|
||||
## 3 Assignments
|
||||
[assignment 1](out/notes/assignment-1.md)
|
||||
[[assignment 1]]
|
||||
|
||||
## 4 Information
|
||||
|
||||
51
content/notes/201 Information Systems.md
Normal file
51
content/notes/201 Information Systems.md
Normal file
@ -0,0 +1,51 @@
|
||||
# INFO 201 - Information Systems
|
||||
## 1 Lectures
|
||||
- [[Lecture 6 Business Functions and Use Cases]]
|
||||
- [[Lecture 7 Business process modelling(BPM)]]
|
||||
- [[Lecture 8 Business patterns]]
|
||||
- [[Lecture 9 Data Modelling and Normalisation]]
|
||||
- [[Lecture 10 OOP Concepts and UML]]
|
||||
- [[Lecture 11 Class diagrams]]
|
||||
|
||||
## 2 Notes
|
||||
- [[Business analyst]]
|
||||
- [[Systems analyst]]
|
||||
- [[Developer]]
|
||||
- [[Models]]
|
||||
- [[Systems development lifecycle (SDLC)]]
|
||||
- [[Agile Development]]
|
||||
- [[Predictive adaptive spectrum]]
|
||||
- [[Version Control Systems]]
|
||||
- [[Requirements elicitation]]
|
||||
|
||||
|
||||
### 2.1 Information
|
||||
|
||||
**Staff**
|
||||
|
||||
Role | Name | Email | Location | Hours
|
||||
---------|----------------|-----------------------------------------------------------------|----------|------
|
||||
Lecures | Nigel stanger | [nigel.stanger@otago.ac.nz](mailto:nigel.stanger@otago.ac.nz) | OBS 340 |
|
||||
Lectures | Daniel Costa | [danielcalencar@otago.ac.nz](mailto:danielcalencar@otago.ac.nz) | OBS 345 |
|
||||
Labs | Chris Edwards | [chris.edwards@otago.ac.nz](mailto:chris.edwards@otago.ac.nz) | OBS 328 |
|
||||
Labs | Mark George | [mark.george@otago.ac.nz](mailto:mark.george@otago.ac.nz) | OBS 332 |
|
||||
|
||||
**Resources**
|
||||
[Domain Driven Design with BDD](https://www.youtube.com/watch?v=Ju50D11EIoE)
|
||||
|
||||
**Assessment**
|
||||
Must pass at least 7 labs
|
||||
Must get total of at least 40%.
|
||||
|
||||
Grade Componentsh
|
||||
- milestone 1 - 10%
|
||||
- milestone 2 - 20%
|
||||
- milestone 3 - 20%
|
||||
- exam - 50%
|
||||
|
||||
**Course_plan**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,55 +0,0 @@
|
||||
---
|
||||
title: 201 Information Systems
|
||||
draft: true
|
||||
---
|
||||
# INFO 201 - Information Systems
|
||||
## 1 Lectures
|
||||
- [Lecture 6 Business Functions and Use Cases](out/notes/lecture-6-business-functions-and-use-cases.md)
|
||||
- [Lecture 7 Business process modelling(BPM)](out/notes/lecture-7-business-process-modellingbpm.md)
|
||||
- [Lecture 8 Business patterns](out/notes/lecture-8-business-patterns.md)
|
||||
- [Lecture 9 Data Modelling and Normalisation](out/notes/lecture-9-data-modelling-and-normalisation.md)
|
||||
- [Lecture 10 OOP Concepts and UML](out/notes/lecture-10-oop-concepts-and-uml.md)
|
||||
- [Lecture 11 Class diagrams](out/notes/lecture-11-class-diagrams.md)
|
||||
|
||||
## 2 Notes
|
||||
- [Business analyst](out/notes/business-analyst.md)
|
||||
- [Systems analyst](out/notes/systems-analyst.md)
|
||||
- [Developer](out/notes/developer.md)
|
||||
- [Models](out/notes/models.md)
|
||||
- [Systems development lifecycle (SDLC)](out/notes/systems-development-lifecycle-sdlc.md)
|
||||
- [Agile Development](out/notes/agile-development.md)
|
||||
- [Predictive adaptive spectrum](out/notes/predictive-adaptive-spectrum.md)
|
||||
- [Version Control Systems](out/notes/version-control-systems.md)
|
||||
- [Requirements elicitation](out/notes/requirements-elicitation.md)
|
||||
|
||||
|
||||
### 2.1 Information
|
||||
|
||||
**Staff**
|
||||
|
||||
Role | Name | Email | Location | Hours
|
||||
---------|----------------|-----------------------------------------------------------------|----------|------
|
||||
Lecures | Nigel stanger | [nigel.stanger@otago.ac.nz](mailto:nigel.stanger@otago.ac.nz) | OBS 340 |
|
||||
Lectures | Daniel Costa | [danielcalencar@otago.ac.nz](mailto:danielcalencar@otago.ac.nz) | OBS 345 |
|
||||
Labs | Chris Edwards | [chris.edwards@otago.ac.nz](mailto:chris.edwards@otago.ac.nz) | OBS 328 |
|
||||
Labs | Mark George | [mark.george@otago.ac.nz](mailto:mark.george@otago.ac.nz) | OBS 332 |
|
||||
|
||||
**Resources**
|
||||
[Domain Driven Design with BDD](https://www.youtube.com/watch?v=Ju50D11EIoE)
|
||||
|
||||
**Assessment**
|
||||
Must pass at least 7 labs
|
||||
Must get total of at least 40%.
|
||||
|
||||
Grade Componentsh
|
||||
- milestone 1 - 10%
|
||||
- milestone 2 - 20%
|
||||
- milestone 3 - 20%
|
||||
- exam - 50%
|
||||
|
||||
**Course_plan**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
45
content/notes/202 Software development.md
Normal file
45
content/notes/202 Software development.md
Normal file
@ -0,0 +1,45 @@
|
||||
# COSC 202 - Software development
|
||||
## 1 Lectures
|
||||
- [[Lecture 07 Unit Testing]]
|
||||
- [[Lecture 08 Debugging]]
|
||||
- [[Lecture 09 Documentation]]
|
||||
- [[Lecture 10 Continuous integration]]
|
||||
- [[Lecture 11 Continuous Integration 2]]
|
||||
|
||||
## 2 Notes
|
||||
- [[Consoles Terminals Shells]]
|
||||
- [[Git]]
|
||||
- [[Ethics]]
|
||||
- [[Branch]]
|
||||
- [[Integrated Development Environments]]
|
||||
|
||||
## 3 Project
|
||||
A non destructive image editor ANDIE
|
||||
- [[CROCS]]
|
||||
- [[Teamwork]]
|
||||
|
||||
## 4 Information
|
||||
**Staff
|
||||
- David Eyers - Lectures
|
||||
- Steven mills - Project
|
||||
- Reuben Crimp - Labs
|
||||
- Student demonstrators
|
||||
|
||||
**Contact**
|
||||
cosc202-staff@otago.ac.nz
|
||||
|
||||
**Resources**
|
||||
lab book -> https://cosc202.cspages.otago.ac.nz/lab-book/COSC202LabBook.pdf
|
||||
https://www.youtube.com/channel/UCD8yeTczadqdARzQUp29PJw
|
||||
|
||||
**Assessment**
|
||||
20% x 2 group project
|
||||
20% individual
|
||||
40% exam
|
||||
|
||||
**Course plan**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,49 +0,0 @@
|
||||
---
|
||||
title: 202 Software development
|
||||
draft: true
|
||||
---
|
||||
# COSC 202 - Software development
|
||||
## 1 Lectures
|
||||
- [Lecture 07 Unit Testing](out/notes/lecture-07-unit-testing.md)
|
||||
- [Lecture 08 Debugging](out/notes/lecture-08-debugging.md)
|
||||
- [Lecture 09 Documentation](out/notes/lecture-09-documentation.md)
|
||||
- [Lecture 10 Continuous integration](out/notes/lecture-10-continuous-integration.md)
|
||||
- [Lecture 11 Continuous Integration 2](out/notes/lecture-11-continuous-integration-2.md)
|
||||
|
||||
## 2 Notes
|
||||
- [Consoles Terminals Shells](out/notes/consoles-terminals-shells.md)
|
||||
- [Git](out/notes/git.md)
|
||||
- [Ethics](out/notes/ethics.md)
|
||||
- [Branch](out/notes/branch.md)
|
||||
- [Integrated Development Environments](out/notes/integrated-development-environments.md)
|
||||
|
||||
## 3 Project
|
||||
A non destructive image editor ANDIE
|
||||
- [CROCS](out/notes/crocs.md)
|
||||
- [Teamwork](out/notes/teamwork.md)
|
||||
|
||||
## 4 Information
|
||||
**Staff
|
||||
- David Eyers - Lectures
|
||||
- Steven mills - Project
|
||||
- Reuben Crimp - Labs
|
||||
- Student demonstrators
|
||||
|
||||
**Contact**
|
||||
cosc202-staff@otago.ac.nz
|
||||
|
||||
**Resources**
|
||||
lab book -> https://cosc202.cspages.otago.ac.nz/lab-book/COSC202LabBook.pdf
|
||||
https://www.youtube.com/channel/UCD8yeTczadqdARzQUp29PJw
|
||||
|
||||
**Assessment**
|
||||
20% x 2 group project
|
||||
20% individual
|
||||
40% exam
|
||||
|
||||
**Course plan**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
69
content/notes/203 Human-Computer interaction.md
Normal file
69
content/notes/203 Human-Computer interaction.md
Normal file
@ -0,0 +1,69 @@
|
||||
# INFO203 - Human Computer Interaction
|
||||
## 1 Notes
|
||||
### 1.1 Lectures
|
||||
- [[Lecture 7 Personas and Scenarios]]
|
||||
- [[Lecture 8 Personas and Scenarios]]
|
||||
- [[Lecture 9 Paper Protoypes, Wizard of OZ, Video Prototyping]]
|
||||
- [[Lecture 10 Design Heuristics]]
|
||||
- [[Lecture 11 Design Heuristics 2]]
|
||||
- [[Lecture 12 Design Heuristics 3]]
|
||||
|
||||
### 1.2 Videos
|
||||
- [[Heuristic Evaluation]]
|
||||
- [[Storyboards mockups, paper prototypes]]
|
||||
- [[Faking it Wizard of OZ]]
|
||||
- [[Faking it video prototyping]]
|
||||
|
||||
### 1.3 Atomic
|
||||
- [[HCI Big Picture]]
|
||||
- [[Birth of HCI]]
|
||||
- [[Prototyping]]
|
||||
- [[Evaluating designs]]
|
||||
- [[Needfinding]]
|
||||
- [[Observation]]
|
||||
- [[Interviews]]
|
||||
- [[User Experience]]
|
||||
- [[Usability]]
|
||||
- [[HCI]]
|
||||
|
||||
### 1.4 Assignments
|
||||
- [[What is Usability]]
|
||||
- [[Heuristics Evaluation Assignment]]
|
||||
- [[Assignment 3]]
|
||||
|
||||
### 1.5 Exam
|
||||
[[Possible exam questions]]
|
||||
|
||||
## 2 Information
|
||||
|
||||
**Staff**
|
||||
|
||||
Role | Name | Email | Location | Hours
|
||||
-----|------|-------|----------|------
|
||||
Lectures | Tobias Langlotz | [tobias.langlotz@otago.ac.nz](mailto:tobias.langlotz@otago.ac.nz) | OBS 713 |
|
||||
Labs | Jonatan Sutton | [sutjo752@student.otago.ac.nz](mailto:sutjo752@student.otago.ac.nz) | |
|
||||
|
||||
**Resources**
|
||||
- [Course Outline](https://blackboard.otago.ac.nz/bbcswebdav/pid-2827486-dt-content-rid-17936119_1/courses/INFO203_S1DNIE_2022/INFO203%20Course%20Outline%281%29.pdf)
|
||||
- [Stanford HCI Videos](https://blackboard.otago.ac.nz/webapps/blackboard/content/listContent.jsp?course_id=_45153_1&content_id=_2827496_1)
|
||||
- [Lectures Slides](https://blackboard.otago.ac.nz/webapps/blackboard/content/listContent.jsp?course_id=_45153_1&content_id=_2827495_1)
|
||||
- [Lab docs and assignments](https://blackboard.otago.ac.nz/webapps/blackboard/content/listContent.jsp?course_id=_45153_1&content_id=_2827497_1)
|
||||
- mark weiser "Calm technology"
|
||||
|
||||
|
||||
**Assessment**
|
||||
Total > 50%
|
||||
Exam > 40%
|
||||
|
||||
- Usability analysis 5%
|
||||
- Usability analysis 2 10%
|
||||
- Prototype 35%
|
||||
- Exam 50%
|
||||
|
||||
**Course_plan
|
||||
|
||||
![[Pasted image 20220301174404.png]]
|
||||
|
||||
![[Pasted image 20220301174411.png]]
|
||||
|
||||
|
||||
@ -1,73 +0,0 @@
|
||||
---
|
||||
title: 203 Human-Computer interaction
|
||||
draft: true
|
||||
---
|
||||
# INFO203 - Human Computer Interaction
|
||||
## 1 Notes
|
||||
### 1.1 Lectures
|
||||
- [Lecture 7 Personas and Scenarios](out/notes/lecture-7-personas-and-scenarios.md)
|
||||
- [Lecture 8 Personas and Scenarios](out/notes/lecture-8-personas-and-scenarios.md)
|
||||
- [Lecture 9 Paper Protoypes, Wizard of OZ, Video Prototyping](out/notes/lecture-9-paper-protoypes-wizard-of-oz-video-prototyping.md)
|
||||
- [Lecture 10 Design Heuristics](out/notes/lecture-10-design-heuristics.md)
|
||||
- [Lecture 11 Design Heuristics 2](out/notes/lecture-11-design-heuristics-2.md)
|
||||
- [Lecture 12 Design Heuristics 3](out/notes/lecture-12-design-heuristics-3.md)
|
||||
|
||||
### 1.2 Videos
|
||||
- [Heuristic Evaluation](out/notes/heuristic-evaluation.md)
|
||||
- [Storyboards mockups, paper prototypes](out/notes/storyboards-mockups-paper-prototypes.md)
|
||||
- [Faking it Wizard of OZ](out/notes/faking-it-wizard-of-oz.md)
|
||||
- [Faking it video prototyping](out/notes/faking-it-video-prototyping.md)
|
||||
|
||||
### 1.3 Atomic
|
||||
- [HCI Big Picture](out/notes/hci-big-picture.md)
|
||||
- [Birth of HCI](out/notes/birth-of-hci.md)
|
||||
- [Prototyping](out/notes/prototyping.md)
|
||||
- [Evaluating designs](out/notes/evaluating-designs.md)
|
||||
- [Needfinding](out/notes/needfinding.md)
|
||||
- [Observation](out/notes/observation.md)
|
||||
- [Interviews](out/notes/interviews.md)
|
||||
- [User Experience](out/notes/user-experience.md)
|
||||
- [Usability](out/notes/usability.md)
|
||||
- [HCI](out/notes/hci.md)
|
||||
|
||||
### 1.4 Assignments
|
||||
- [What is Usability](out/notes/what-is-usability.md)
|
||||
- [Heuristics Evaluation Assignment](out/notes/heuristics-evaluation-assignment.md)
|
||||
- [Assignment 3](out/notes/assignment-3.md)
|
||||
|
||||
### 1.5 Exam
|
||||
[Possible exam questions](out/notes/possible-exam-questions.md)
|
||||
|
||||
## 2 Information
|
||||
|
||||
**Staff**
|
||||
|
||||
Role | Name | Email | Location | Hours
|
||||
-----|------|-------|----------|------
|
||||
Lectures | Tobias Langlotz | [tobias.langlotz@otago.ac.nz](mailto:tobias.langlotz@otago.ac.nz) | OBS 713 |
|
||||
Labs | Jonatan Sutton | [sutjo752@student.otago.ac.nz](mailto:sutjo752@student.otago.ac.nz) | |
|
||||
|
||||
**Resources**
|
||||
- [Course Outline](https://blackboard.otago.ac.nz/bbcswebdav/pid-2827486-dt-content-rid-17936119_1/courses/INFO203_S1DNIE_2022/INFO203%20Course%20Outline%281%29.pdf)
|
||||
- [Stanford HCI Videos](https://blackboard.otago.ac.nz/webapps/blackboard/content/listContent.jsp?course_id=_45153_1&content_id=_2827496_1)
|
||||
- [Lectures Slides](https://blackboard.otago.ac.nz/webapps/blackboard/content/listContent.jsp?course_id=_45153_1&content_id=_2827495_1)
|
||||
- [Lab docs and assignments](https://blackboard.otago.ac.nz/webapps/blackboard/content/listContent.jsp?course_id=_45153_1&content_id=_2827497_1)
|
||||
- mark weiser "Calm technology"
|
||||
|
||||
|
||||
**Assessment**
|
||||
Total > 50%
|
||||
Exam > 40%
|
||||
|
||||
- Usability analysis 5%
|
||||
- Usability analysis 2 10%
|
||||
- Prototype 35%
|
||||
- Exam 50%
|
||||
|
||||
**Course_plan
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Agile Development
|
||||
draft: true
|
||||
---
|
||||
tags: review
|
||||
|
||||
---
|
||||
@ -12,13 +8,13 @@ tags: review
|
||||
|
||||
[The agile manifesto](https://www.agilealliance.org/agile101/the-agile-manifesto)
|
||||
|
||||
## 1 [SCRUM](out/notes/scrum.md)
|
||||
## 1 [[SCRUM]]
|
||||
Development is split into many short (~30 day) "sprints" of intense focus where the entire team is involved
|
||||
|
||||
## 2 [Extreme programming (XP)](out/notes/extreme-programming-xp.md)
|
||||
## 2 [[Extreme programming (XP)]]
|
||||
take current industry practices to the extreme
|
||||
|
||||
## 3 [Unified process (UP)](out/notes/unified-process-up.md)
|
||||
## 3 [[Unified process (UP)]]
|
||||
Interative and incremental architecture-centric which has four main phases
|
||||
- inception
|
||||
- elaboration
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: All the light we cannot see
|
||||
draft: true
|
||||
---
|
||||
# All the light we cannot see
|
||||
## Quotes
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Anti govt protest china
|
||||
draft: true
|
||||
---
|
||||
# Anti govt protest China
|
||||
China used facial recognition to identofy protesters
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Approches to systems development
|
||||
draft: true
|
||||
---
|
||||
# Approches to systems development
|
||||
## 1 traditional
|
||||
regardless of the approach, the conecpot of the model is import for analysis design and modelling parrasigms
|
||||
@ -1,8 +1,4 @@
|
||||
---
|
||||
title: Assignment 3
|
||||
draft: true
|
||||
---
|
||||
[203 Human-Computer interaction](out/notes/203-human-computer-interaction.md)
|
||||
[[203 Human-Computer interaction]]
|
||||
|
||||
# Assignment 3
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Behaviour Driven Development
|
||||
draft: true
|
||||
aliases: BDD
|
||||
sr-due: 2022-04-14
|
||||
sr-interval: 23
|
||||
@ -11,7 +9,7 @@ sr-ease: 292
|
||||
# Behaviour Driven Development
|
||||
Models should be created with the users needs in mind.
|
||||
Required bahaviour determines acceptance criteria
|
||||
This is called Behaviour Driven Development [BDD](None)
|
||||
This is called Behaviour Driven Development [[BDD]]
|
||||
|
||||
**Resources**
|
||||
[Domain Driven Design with BDD](https://www.youtube.com/watch?v=Ju50D11EIoE)
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Big theta
|
||||
draft: true
|
||||
sr-due: 2022-04-27
|
||||
sr-interval: 41
|
||||
sr-ease: 290
|
||||
@ -1,126 +1,122 @@
|
||||
---
|
||||
title: Birth of HCI
|
||||
draft: true
|
||||
---
|
||||
# Birth of HCI
|
||||
ENIAC (one of the first programmable, electronic computers) 1946, and the first six programmers: Kay McNulty, Betty Jennings, Betty Snyder, Marlyn Meltzer, Fran Bilas, and Ruth Lichterman
|
||||
|
||||
|
||||
![[Pasted image 20220309103217.png]]
|
||||
|
||||
|
||||
|
||||
DEC PDP-8 and TI 980 (1960’s), PDP-8 is an octal computer (switches in three-bit configurations), TI 980 is a hexadecimal machine (4-bit configuration). Not interactive
|
||||
|
||||
|
||||
![[Pasted image 20220309103249.png]]
|
||||
|
||||
|
||||
|
||||
Batch processing using punch cards, still not interactive (1950s -1970s)
|
||||
|
||||
|
||||
![[Pasted image 20220309103307.png]]
|
||||
|
||||
|
||||
|
||||
IBM System/360 (mainframe computer in the 70s), Altair 8800 (one of the first home computers)
|
||||
|
||||
|
||||
![[Pasted image 20220309103339.png]]
|
||||
|
||||
|
||||
|
||||
visicalc (Dan Bricklin 1979), and Apple II (1977)
|
||||
|
||||
|
||||
![[Pasted image 20220309103358.png]]
|
||||
|
||||
|
||||
|
||||
Sutherland, Ivan Edward (January 1963). "Sketchpad: A man-machine graphical communication system, MIT press.
|
||||
|
||||
|
||||
![[Pasted image 20220309103425.png]]
|
||||
|
||||
|
||||
|
||||
Sutherland, Ivan Edward (January 1963). "Sketchpad: A man-machine graphical communication system, MIT press.
|
||||
|
||||
|
||||
![[Pasted image 20220309103441.png]]
|
||||
|
||||
|
||||
|
||||
1968 - “The Sword of Damocles” Sutherland, Ivan Edward (1968), “A head-mounted three dimensional display”
|
||||
|
||||
|
||||
![[Pasted image 20220309103500.png]]
|
||||
|
||||
|
||||
|
||||
1968 - “The Sword of Damocles” Sutherland, Ivan Edward (1968), “A head-mounted three dimensional display”
|
||||
|
||||
|
||||
![[Pasted image 20220309103520.png]]
|
||||
|
||||
|
||||
|
||||
1968 - “The Sword of Damocles” Sutherland, Ivan Edward (1968), “A head-mounted three dimensional display”
|
||||
|
||||
|
||||
![[Pasted image 20220309103543.png]]
|
||||
|
||||
|
||||
|
||||
“The Mother of All Demos”, presented by Douglas Engelbart (1968) at (ACM/IEEE) Computer Society's Fall Joint Computer Conference See full demo: https://www.youtube.com/watch?v=yJDv-zdhzMY
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220309103603.png]]
|
||||
![[Pasted image 20220309103631.png]]
|
||||
|
||||
|
||||
|
||||
“Dynabook” Alan C. Kay. (1972), “Personal Computer for Children of All Ages”
|
||||
|
||||
|
||||
![[Pasted image 20220309103706.png]]
|
||||
|
||||
|
||||
|
||||
Apple Newton (1993) and Apple iPad (2010)
|
||||
|
||||
|
||||
![[Pasted image 20220309103724.png]]
|
||||
|
||||
|
||||
|
||||
Graphical User Interface supporting “What You See Is What You Get” (WYSIWYG), the Desktop metaphor (files, folders, etc.), Xerox Parc/Xeroc Star
|
||||
|
||||
|
||||
![[Pasted image 20220309103738.png]]
|
||||
|
||||
|
||||
|
||||
Graphical User Interface supporting “What You See Is What You Get” (WYSIWYG), the Desktop metaphor (files, folders, etc.), Xerox Parc/Xeroc Star
|
||||
|
||||
|
||||
![[Pasted image 20220309103752.png]]
|
||||
|
||||
|
||||
|
||||
1992/93 - IBM Simon First smartphone Phone, pager, calculator, address book, fax machine, and e-mail device
|
||||
|
||||
|
||||
![[Pasted image 20220309103808.png]]
|
||||
|
||||
|
||||
|
||||
Ramesh Raskar, Greg Welch, Matt Cutts, Adam Lake, Lev Stesin and Henry Fuchs (1998) "The Office of the Future : A Unified Approach to Image-Based Modeling and Spatially Immersive Displays,"
|
||||
|
||||
|
||||
![[Pasted image 20220309103853.png]]
|
||||
|
||||
|
||||
|
||||
1981 - Steve Manns’s “Wearable Computing” Start of a series of prototypes for wearable computing, cyborgs, and mediated reality (-> Google Glass) www.wearcam.org, www.eyetap.org
|
||||
|
||||
|
||||
![[Pasted image 20220309103916.png]]
|
||||
|
||||
|
||||
|
||||
Nokia N95 (2007) and Apple iPhone (2007)
|
||||
|
||||
|
||||
![[Pasted image 20220309103944.png]]
|
||||
|
||||
|
||||
|
||||
Major innovations in HCI (Myers 1998)
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220309104007.png]]
|
||||
![[Pasted image 20220309104015.png]]
|
||||
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Business Process Model and Notation
|
||||
draft: true
|
||||
aliases: BPMN
|
||||
---
|
||||
# BPMN - Business Process Model and Notation
|
||||
@ -23,5 +21,5 @@ identify the business role for each activity
|
||||
- executable if using the right infrastructure
|
||||
|
||||
### 0.3 Examples
|
||||
|
||||
|
||||
![[Pasted image 20220323113541.png]]
|
||||
![[Pasted image 20220323113643.png]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Business analyst
|
||||
draft: true
|
||||
sr-due: 2022-05-14
|
||||
sr-interval: 53
|
||||
sr-ease: 290
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Business functions
|
||||
draft: true
|
||||
---
|
||||
# Business functions
|
||||
- what the business ought to be doing
|
||||
- _not_
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Business process model
|
||||
draft: true
|
||||
---
|
||||
# 3 Business process model
|
||||
- graphical depiction fo one ormore business proccesses
|
||||
- some variant of a flowchart
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Business process
|
||||
draft: true
|
||||
---
|
||||
# Business process
|
||||
- A sequence of tasks or steps required to carry out a particular business function e.g.,:
|
||||
- pocure new assets
|
||||
3
content/notes/Cheat Sheets.md
Normal file
3
content/notes/Cheat Sheets.md
Normal file
@ -0,0 +1,3 @@
|
||||
|
||||
[[Git Cheat Sheet]]
|
||||
[[WinComposeS]]
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Combined evals
|
||||
draft: true
|
||||
---
|
||||
| Heuristic | Severity | Location | Issue | Recommendation |
|
||||
|:-------------------------------------------------------------|:---------------------------|:----------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| visibility of system status | 3 | Call | The the close window button does not leave the meeting. It pops up the small view. If the user closes this window. The user still does not leave the meeting and there is not GUI | make closing the windows prompt the user if they want to leave the meeting |
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Consoles Terminals Shells
|
||||
draft: true
|
||||
sr-due: 2022-04-10
|
||||
sr-interval: 27
|
||||
sr-ease: 270
|
||||
@ -16,8 +14,8 @@ tags: #review
|
||||
- console is the device: -> terminal is program inside that device
|
||||
- terminal -> text input output environment (can be remote)
|
||||
- windows terminal
|
||||
- [shell](out/notes/shell.md) -> program which the terminal/console sends input to which sends command to the OS
|
||||
- [unix shell](out/notes/unix-shell.md)
|
||||
- [[shell]] -> program which the terminal/console sends input to which sends command to the OS
|
||||
- [[unix shell]]
|
||||
- powershell
|
||||
- cmd
|
||||
- bash, fish, zsh, ksh, sh, tsch
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Continuous Integration
|
||||
draft: true
|
||||
---
|
||||
# Continuous Integration
|
||||
## 1 What is it
|
||||
continuous --> is always happening
|
||||
0
content/notes/Daily notes.md
Normal file
0
content/notes/Daily notes.md
Normal file
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Dependencies among attributes
|
||||
draft: true
|
||||
---
|
||||
# 2 Dependencies among attributes
|
||||
### 0.1 Functional Depenencies (FDs)
|
||||
For any given value of attribute A there is _exactly one_ associated value of attribute B, then A _functionally determines_ B (loosely)
|
||||
@ -90,7 +86,7 @@ if for any given value of attribute A there is a _set_ of associated values of a
|
||||
#### 0.4.1 Examples
|
||||
|
||||
|
||||
[Normalisation](out/notes/normalisation.md)
|
||||
[[Normalisation]]
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Domain Driven Design
|
||||
draft: true
|
||||
aliases: DDD
|
||||
sr-due: 2022-04-12
|
||||
sr-interval: 19
|
||||
@ -1,10 +1,8 @@
|
||||
---
|
||||
title: Entity Relationship Diagrams
|
||||
draft: true
|
||||
aliases: ERD, ERDs
|
||||
---
|
||||
# Entity Relationship Diagrams
|
||||
|
||||
![[Pasted image 20220328165256.png]]
|
||||
|
||||
cardinality
|
||||
identifying vs non identifying relationship
|
||||
@ -14,33 +12,33 @@ labels are important - but not always needed
|
||||
associative entity => changes many to many relationship with additional relationship
|
||||
|
||||
## 1 subtypes
|
||||
|
||||
|
||||
![[Pasted image 20220328165640.png]]
|
||||
![[Pasted image 20220328165656.png]]
|
||||
|
||||
uses:
|
||||
- model mutual exclusivity
|
||||
- better for modelling not for implementation
|
||||
|
||||
## 2 parallel relationship
|
||||
|
||||
![[Pasted image 20220328165851.png]]
|
||||
|
||||
could model as separate relationships via staff subtypes
|
||||
not very common
|
||||
|
||||
|
||||
![[Pasted image 20220328165944.png]]
|
||||
also an example of recursive many-to-many relationships
|
||||
|
||||
## 3 recursive relationship
|
||||
labels are critical
|
||||
usually 1:M can be 1:1 or M:M
|
||||
|
||||
![[Pasted image 20220328200337.png]]
|
||||
|
||||
## 4 dealing with data history
|
||||
|
||||
![[Pasted image 20220328200434.png]]
|
||||
|
||||
could be many to many relationships:
|
||||
could be many to many relationships:![[Pasted image 20220328200517.png]]
|
||||
|
||||
so associative relationship: 
|
||||
so associative relationship: ![[Pasted image 20220328200536.png]]
|
||||
|
||||
|
||||
what do we require:
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Evaluating designs
|
||||
draft: true
|
||||
sr-due: 2022-04-07
|
||||
sr-interval: 10
|
||||
sr-ease: 210
|
||||
@ -45,7 +43,7 @@ tags: #review
|
||||
|
||||
# Evaluating-designs
|
||||
Why to evaluate using 'outside' people:
|
||||
- how do we know if a [prototype](out/notes/prototyping.md) is good
|
||||
- how do we know if a [[Prototyping|prototype]] is good
|
||||
- designer/developers are not 'fresh' -> they already have experience with the product
|
||||
- designer/developers don't know what real users will do
|
||||
|
||||
@ -135,16 +133,16 @@ Why to evaluate using 'outside' people:
|
||||
+ easy to compare different products
|
||||
- responder bias
|
||||
- Not accurate representation of real product
|
||||
* e.g., 
|
||||
* e.g., ![[Pasted image 20220316130318.png]]
|
||||
* Focus groups
|
||||
* gathering groups of people to discuss an interface
|
||||
* group setting can help or hinder
|
||||
|
||||
### Feedback from experts
|
||||
- [Peer critique](None)
|
||||
- [Dogfooding](None)
|
||||
- [[Peer critique]]
|
||||
- [[Dogfooding]]
|
||||
- Using tools yourself
|
||||
- [Heuristic Evaluation](out/notes/heuristic-evaluation.md)
|
||||
- [[Heuristic Evaluation]]
|
||||
- structured feedback
|
||||
|
||||
### Comparative experiments
|
||||
@ -159,17 +157,17 @@ Why to evaluate using 'outside' people:
|
||||
- observe what people do in the actual evironment
|
||||
- usually more long term
|
||||
- find things not present in short term studies
|
||||
- [Observation](out/notes/observation.md)
|
||||
- [[Observation]]
|
||||
|
||||
### Simulation and formal models
|
||||
- more mathmatical quantitative
|
||||
- useful if you have a theory to test
|
||||
- often used for input techniques
|
||||
- can test multiple alternatives quickly
|
||||
- typically simulation is used in conjugtion with [monte carlo optimisation](None)
|
||||
- typically simulation is used in conjugtion with [[monte carlo optimisation]]
|
||||
|
||||
## Query techniques
|
||||
- [Interviews](out/notes/interviews.md)
|
||||
- [[Interviews]]
|
||||
- questionnaires
|
||||
- less flexible
|
||||
- larger samples possible
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Extreme programming (XP)
|
||||
draft: true
|
||||
sr-due: 2022-04-08
|
||||
sr-interval: 17
|
||||
sr-ease: 250
|
||||
@ -34,4 +32,4 @@ communication, simplicity, feedback, courage.
|
||||
- Coding standards -> follow industry standards for code
|
||||
|
||||
##### Three ring project approach
|
||||
|
||||
![[Pasted image 20220308134047.png]]
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Faking it Wizard of OZ
|
||||
draft: true
|
||||
---
|
||||
# Faking it Wizard of OZ
|
||||
|
||||
making interactive app quickly with minimal code
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Faking it video prototyping
|
||||
draft: true
|
||||
---
|
||||
# Video prototyping
|
||||
|
||||
## 1 benefits
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Git Cheat Sheet
|
||||
draft: true
|
||||
---
|
||||
#CheatSheet
|
||||
# Git Cheat Sheet
|
||||
#### 0.1.1 Commands
|
||||
@ -38,7 +34,7 @@ draft: true
|
||||
|
||||
#### 0.1.2 Terms
|
||||
- Head -> most recent commit on Current branch
|
||||
-[Branch](out/notes/branch.md) -> Split current dev path into two to work on e.g., a bug or a feature
|
||||
-[[Branch]] -> Split current dev path into two to work on e.g., a bug or a feature
|
||||
- Repository -> Where the codebase/file are stored ^3b3a5d
|
||||
- Contains meta-data about the previous vesions etc
|
||||
- Merge commit -> commits which are derived from multiple parent commits
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: HCI Big Picture
|
||||
draft: true
|
||||
sr-due: 2022-04-11
|
||||
sr-interval: 28
|
||||
sr-ease: 270
|
||||
@ -12,7 +10,7 @@ tags: #review
|
||||
|
||||
>HCI is the cycle of design, implementation, evaluation of user interfaces
|
||||
|
||||
|
||||
![[Pasted image 20220301175640.png|300]]
|
||||
|
||||
>"fail fast so you can succeed sooner"
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Heuristic Evaluation
|
||||
draft: true
|
||||
---
|
||||
# Heuristic evaluation
|
||||
>"Heuristics are strategies derived from previous experiences with similar problems"
|
||||
jacob nielsen and rolf molich
|
||||
@ -13,7 +9,7 @@ different evaluators will find different problems
|
||||
evaluators only communicate afterwaards
|
||||
findings are aggregated at the end
|
||||
|
||||
|
||||
![[Pasted image 20220322102933.png]]
|
||||
|
||||
## 1 when?
|
||||
- as part of need finding -> use experts to critique existing solutions
|
||||
@ -103,7 +99,7 @@ value to alternate methods
|
||||
^ find dfferent issues
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220316101636.png]]
|
||||
|
||||
|
||||
### 2.4 Extra tips how to individual
|
||||
@ -1,10 +1,6 @@
|
||||
---
|
||||
title: Heuristics Evaluation Assignment
|
||||
draft: true
|
||||
---
|
||||
[Jet - Ohyay](out/notes/jet-ohyay.md)
|
||||
[Jet -Discord](out/notes/jet-discord.md)
|
||||
[Combined evals](out/notes/combined-evals.md)
|
||||
[[Jet - Ohyay]]
|
||||
[[Jet -Discord]]
|
||||
[[Combined evals]]
|
||||
# Skype Heuristic Evaluation
|
||||
Jet Hughes 9474308
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: How is safe enough for autonomous vehicles
|
||||
draft: true
|
||||
---
|
||||
# Case study 3 Autonomous vehicles
|
||||
- How safe is safe enough?
|
||||
- its impossible to be perfect
|
||||
@ -13,4 +9,4 @@ Not driving youself massively reduces reaction time
|
||||
Allow user to set ethical bias of their vehicles AI
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220310114053.png]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Integrated Development Environments
|
||||
draft: true
|
||||
aliases: IDE, IDEs, Integrated Development Environment, Integrated Development Environments
|
||||
sr-due: 2022-04-28
|
||||
sr-interval: 36
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Jet - Ohyay
|
||||
draft: true
|
||||
---
|
||||
# ohyay
|
||||
| Heuristic | Severity | Location | Description | Recommendation |
|
||||
|-|-|-|-|-|
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Jet -Discord
|
||||
draft: true
|
||||
---
|
||||
# Discord
|
||||
| Heuristic | Severity | Location | Description | Recommendation |
|
||||
|-|-|-|-|-|
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 07 Unit Testing
|
||||
draft: true
|
||||
sr-due: 2022-04-29
|
||||
sr-interval: 26
|
||||
sr-ease: 270
|
||||
@ -18,17 +16,17 @@ sr-ease: 270
|
||||
|
||||
# Lecture 07 Unit Testing
|
||||
|
||||
### 0.1 [Testing](out/notes/testing.md)
|
||||
### 0.1 [[Testing]]
|
||||
1. why is testing needed
|
||||
|
||||
2. what are three types of testing
|
||||
|
||||
3. what are some limitations of testing
|
||||
|
||||
### 0.2 [Test driven development](out/notes/test-driven-development.md)
|
||||
### 0.2 [[Test driven development]]
|
||||
1. what is testing driven development
|
||||
|
||||
### 0.3 [Unit testing](out/notes/unit-testing.md)
|
||||
### 0.3 [[Unit testing]]
|
||||
1. Breifly describe unit testing
|
||||
|
||||
2. What is a testing environment. Why is it useful
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 08 Debugging
|
||||
draft: true
|
||||
sr-due: 2022-04-09
|
||||
sr-interval: 8
|
||||
sr-ease: 250
|
||||
@ -14,7 +12,7 @@ sr-ease: 250
|
||||
4. debug symbols
|
||||
5. debugger operations
|
||||
6. breakpoint and watch points
|
||||
7. why technical faults are not always your fault 
|
||||
7. why technical faults are not always your fault ![[Pasted image 20220329142230.png]]
|
||||
|
||||
# Lecture 8 debugging
|
||||
[Debugging](out/notes/debugging.md)
|
||||
[[Debugging]]
|
||||
@ -1,10 +1,8 @@
|
||||
---
|
||||
title: Lecture 09 Documentation
|
||||
draft: true
|
||||
sr-due: 2022-04-08
|
||||
sr-interval: 8
|
||||
sr-ease: 250
|
||||
---
|
||||
#review
|
||||
# Lecture 09 Documentation
|
||||
[Documentation](out/notes/documentation.md)
|
||||
[[Documentation]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 10 Continuous integration
|
||||
draft: true
|
||||
sr-due: 2022-04-11
|
||||
sr-interval: 8
|
||||
sr-ease: 250
|
||||
@ -19,4 +17,4 @@ sr-ease: 250
|
||||
|
||||
|
||||
# Lecture 10
|
||||
[Continuous Integration](out/notes/continuous-integration.md)
|
||||
[[Continuous Integration]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 10 Design Heuristics
|
||||
draft: true
|
||||
sr-due: 2022-04-13
|
||||
sr-interval: 10
|
||||
sr-ease: 250
|
||||
@ -11,15 +9,15 @@ sr-ease: 250
|
||||
# Lecture 10 Prototyping and Design Heuristics
|
||||
|
||||
## 1 Wizard of OZ
|
||||
[Faking it Wizard of OZ](out/notes/faking-it-wizard-of-oz.md)
|
||||
[[Faking it Wizard of OZ]]
|
||||
simulating machine behavior with human operators
|
||||
|
||||
## 2 Video prototyping
|
||||
[Faking it video prototyping](out/notes/faking-it-video-prototyping.md)
|
||||
[[Faking it video prototyping]]
|
||||
|
||||
## 3 Creating and comparing alternatives
|
||||
create multiple ideas in parallel rather than one after the other
|
||||
|
||||
|
||||
![[Pasted image 20220330105813.png]]
|
||||
![[Pasted image 20220330110050.png]]
|
||||
|
||||
## 4 Design heuristics
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 10 Heaps and heap sort
|
||||
draft: true
|
||||
sr-due: 2022-04-08
|
||||
sr-interval: 3
|
||||
sr-ease: 250
|
||||
@ -10,7 +8,7 @@ sr-ease: 250
|
||||
---
|
||||
# Lecture 10 Heaps and heap sort
|
||||
## 1 Overview
|
||||
[Heap](out/notes/heap.md)
|
||||
[[Heap]]
|
||||
|
||||
## 2 Operations
|
||||
### 2.1 Add element
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 10 OOP Concepts and UML
|
||||
draft: true
|
||||
sr-due: 2022-04-10
|
||||
sr-interval: 7
|
||||
sr-ease: 250
|
||||
@ -13,9 +11,9 @@ sr-ease: 250
|
||||
3. give an example of how difference UML diagram types can be linked when modelling a system
|
||||
|
||||
# Lecture 10 OOP concepts and UML
|
||||
[Objects](out/notes/objects.md)
|
||||
[[Objects]]
|
||||
|
||||
[2 UML](out/notes/2-uml.md)
|
||||
[[2 UML]]
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 11 Class diagrams
|
||||
draft: true
|
||||
sr-due: 2022-04-08
|
||||
sr-interval: 3
|
||||
sr-ease: 250
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 11 Continuous Integration 2
|
||||
draft: true
|
||||
sr-due: 2022-04-07
|
||||
sr-interval: 3
|
||||
sr-ease: 250
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 11 Design Heuristics 2
|
||||
draft: true
|
||||
sr-due: 2022-04-08
|
||||
sr-interval: 3
|
||||
sr-ease: 250
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 12 Design Heuristics 3
|
||||
draft: true
|
||||
sr-due: 2022-04-15
|
||||
sr-interval: 9
|
||||
sr-ease: 270
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 6 Business Functions and Use Cases
|
||||
draft: true
|
||||
sr-due: 2022-05-04
|
||||
sr-interval: 30
|
||||
sr-ease: 250
|
||||
@ -11,17 +9,17 @@ https://blackboard.otago.ac.nz/bbcswebdav/pid-2884153-dt-content-rid-18204846_1/
|
||||
|
||||
----
|
||||
# Lecture 06 - Business functions and use cases
|
||||
[Approches to systems development](out/notes/approches-to-systems-development.md)
|
||||
[[Approches to systems development]]
|
||||
1. What are the two main approaches to systems development and how do they differ
|
||||
|
||||
[Business functions](out/notes/business-functions.md)
|
||||
[[Business functions]]
|
||||
2. What are business functions
|
||||
|
||||
3. What is a use case
|
||||
|
||||
4. What is a use case diagram used for
|
||||
|
||||
[Use case diagrams](out/notes/use-case-diagrams.md)
|
||||
[[Use case diagrams]]
|
||||
|
||||
|
||||
- dependencies
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 7 Business process modelling(BPM)
|
||||
draft: true
|
||||
aliases: BPMN
|
||||
sr-due: 2022-04-25
|
||||
sr-interval: 24
|
||||
@ -15,7 +13,7 @@ learn about commonly used business process modelling notations
|
||||
understand the elemeents of a UML activity diagram
|
||||
|
||||
1. What is a business process
|
||||
- [Business process](out/notes/business-process.md)
|
||||
- [Business process model](out/notes/business-process-model.md)
|
||||
- [Business Process Model and Notation](out/notes/business-process-model-and-notation.md)
|
||||
- [UML](out/notes/uml.md)
|
||||
- [[Business process]]
|
||||
- [[Business process model]]
|
||||
- [[Business Process Model and Notation]]
|
||||
- [[UML]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 7 Personas and Scenarios
|
||||
draft: true
|
||||
sr-due: 2022-04-21
|
||||
sr-interval: 20
|
||||
sr-ease: 250
|
||||
@ -10,7 +8,7 @@ sr-ease: 250
|
||||
|
||||
---
|
||||
# Lecture 7 Heuristic Evaluation
|
||||
[Heuristic Evaluation](out/notes/heuristic-evaluation.md)
|
||||
[[Heuristic Evaluation]]
|
||||
|
||||
## 1 Review Questions
|
||||
2. Briefly describe the high level process of a heuristic evaluation
|
||||
8
content/notes/Lecture 8 Business patterns.md
Normal file
8
content/notes/Lecture 8 Business patterns.md
Normal file
@ -0,0 +1,8 @@
|
||||
---
|
||||
sr-due: 2022-04-07
|
||||
sr-interval: 7
|
||||
sr-ease: 250
|
||||
---
|
||||
#review
|
||||
# Lecture 8 Business Patterns
|
||||
[[Entity Relationship Diagrams]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 8 Merge sort 2
|
||||
draft: true
|
||||
sr-due: 2022-04-06
|
||||
sr-interval: 8
|
||||
sr-ease: 270
|
||||
@ -99,7 +97,7 @@ inside inner is call to merge which is ϴ(blocksize)
|
||||
$n$ is the numbe of elemetns in a
|
||||
outer loop is executed
|
||||
|
||||
|
||||
![[Pasted image 20220329114859.png#invert]]
|
||||
|
||||
### 2.2 improvments
|
||||
some arrays have sections that are already sorted
|
||||
17
content/notes/Lecture 8 Personas and Scenarios.md
Normal file
17
content/notes/Lecture 8 Personas and Scenarios.md
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
sr-due: 2022-04-05
|
||||
sr-interval: 8
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
#review
|
||||
# Lecture 08 Personas and scenarios
|
||||
|
||||
[[Personas and Scenario]]
|
||||
[[Storyboards mockups, prototypes]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
17
content/notes/Lecture 9 Data Modelling and Normalisation.md
Normal file
17
content/notes/Lecture 9 Data Modelling and Normalisation.md
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
number headings: auto, first-level 2, max 6, 1.1
|
||||
sr-due: 2022-04-10
|
||||
sr-interval: 7
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
#review
|
||||
|
||||
---
|
||||
# Lecture 9 Data Modelling and Normalisation
|
||||
|
||||
[[Redundancy and Anomalies]]
|
||||
|
||||
[[Dependencies among attributes]]
|
||||
|
||||
[[Normalisation]]
|
||||
@ -0,0 +1,32 @@
|
||||
---
|
||||
sr-due: 2022-04-08
|
||||
sr-interval: 7
|
||||
sr-ease: 270
|
||||
---
|
||||
#review
|
||||
___
|
||||
|
||||
# Lecture 9 Paper prototypes, Wizard of OZ, Video prototyping
|
||||
|
||||
[[Faking it video prototyping]]
|
||||
[[Faking it Wizard of OZ]]
|
||||
[[Storyboards mockups, paper prototypes]]
|
||||
|
||||
## 1 Paper prototypes
|
||||
used for exploring design in early stage
|
||||
- brainstorming
|
||||
- e.g.,![[Pasted image 20220329102144.png]]
|
||||
- refinement of design and communicating ideas
|
||||
- e.g., ![[Pasted image 20220329102358.png]] ![[Pasted image 20220329102549.png]] ![[Pasted image 20220329102735.png]]
|
||||
- evaluating interfaces
|
||||
|
||||
### 1.1 examples of prev 203 work
|
||||
![[Pasted image 20220329102855.png]]
|
||||
|
||||
|
||||
## 2 Digital prototypes
|
||||
|
||||
### 2.1 past 203
|
||||
![[Pasted image 20220329104459.png]]
|
||||
![[Pasted image 20220329104612.png]]
|
||||
![[Pasted image 20220329104617.png]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Lecture 9 Stacks queues and heaps
|
||||
draft: true
|
||||
sr-due: 2022-04-14
|
||||
sr-interval: 11
|
||||
sr-ease: 250
|
||||
@ -15,8 +13,8 @@ what is the difference between and stack and a queue?
|
||||
|
||||
how is a priority queue different from regular queue?
|
||||
|
||||
[Stacks and queues](out/notes/stacks-and-queues.md)
|
||||
[[Stacks and queues]]
|
||||
|
||||
[Priority queue](out/notes/priority-queue.md)
|
||||
[[Priority queue]]
|
||||
|
||||
[Heap](out/notes/heap.md)
|
||||
[[Heap]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Merge sort - divide and conquer
|
||||
draft: true
|
||||
sr-due: 2022-04-26
|
||||
sr-interval: 23
|
||||
sr-ease: 250
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Minimal spending tree
|
||||
draft: true
|
||||
---
|
||||
# Minimal Spending tree
|
||||
Algorithm to connect up every part of the network to every other part of the network at minimal possible cost. Where the cost of connecting each pair is known.
|
||||
|
||||
@ -1,14 +1,10 @@
|
||||
---
|
||||
title: Personas and Scenario
|
||||
draft: true
|
||||
---
|
||||
# Personas
|
||||
THe goals of a personas is their expectation of an end condition
|
||||
- not features, functions, taskss, activities
|
||||
|
||||
A tool to documnet who the users are.
|
||||
- what are they trying to accomplish
|
||||
- 
|
||||
- ![[Pasted image 20220323100944.png]]
|
||||
|
||||
a methodology to identofy and think about our users and how they use the software.
|
||||
we want to avoid not thinking about the users
|
||||
@ -37,8 +33,8 @@ Why they want to accomplish end goals /long term desires/self-image
|
||||
- skills
|
||||
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220323102054.png]]
|
||||
![[Pasted image 20220323102200.png]]
|
||||
|
||||
### Persona types
|
||||
- Primary persona ⇒ **Only one per interface**
|
||||
@ -58,6 +54,6 @@ Why they want to accomplish end goals /long term desires/self-image
|
||||
> concise, narrative description of one or more personas using a product to achieve one or more specific goals
|
||||
|
||||
have a good story to tell
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220323103237.png]]
|
||||
![[Pasted image 20220323103420.png]]
|
||||
![[Pasted image 20220323103428.png]]
|
||||
@ -1,5 +1 @@
|
||||
---
|
||||
title: Possible exam questions
|
||||
draft: true
|
||||
---
|
||||
give example of quantitative measure of ussability -> # of errors, time to complete a task, questionnaire with scales
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Predictive adaptive spectrum
|
||||
draft: true
|
||||
sr-due: 2022-04-18
|
||||
sr-interval: 27
|
||||
sr-ease: 252
|
||||
@ -38,9 +36,9 @@ tags: #review
|
||||
|
||||
#### waterfall
|
||||
- "water fall" -assumes phases are completed sequentially (no overlap or iteration)
|
||||
|
||||
![[Pasted image 20220308131314.png|500]]
|
||||
- modified water fall - slightly less rigid verision of "waterfall" which allows some overlap
|
||||
|
||||
![[Pasted image 20220308131532.png|500]]
|
||||
|
||||
|
||||
## Adaptive
|
||||
@ -49,7 +47,7 @@ tags: #review
|
||||
- high techinal risk
|
||||
|
||||
e.g.,
|
||||
|
||||
![[Pasted image 20220308132052.png|500]]
|
||||
|
||||
#### Iterations
|
||||
"micro projects"
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Priority queue
|
||||
draft: true
|
||||
---
|
||||
# Priority queue
|
||||
- A dynamic linear data type that supports addition and removal on entrie
|
||||
- each entry hase a value and a priority (key)
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Redundancy and Anomalies
|
||||
draft: true
|
||||
---
|
||||
# 1 Redundancy and Anomalies
|
||||
### 0.1 Redundancy
|
||||
when values are stored repetitively in database relations
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Requirements elicitation
|
||||
draft: true
|
||||
sr-due: 2022-04-15
|
||||
sr-interval: 24
|
||||
sr-ease: 274
|
||||
@ -25,44 +23,44 @@ information need for performance of operations -> _what info do you use, what in
|
||||
|
||||
Be careful to find a balance between review of the old system and discovery of new requirements
|
||||
|
||||
## Use of [Models](out/notes/models.md)
|
||||
## Use of [[Models]]
|
||||
- Models are the primary output of requirements phase
|
||||
- learn more by modelling domain from new perspectives
|
||||
- abstraction reduces complexxity
|
||||
- need to document details
|
||||
- to remember stuff
|
||||
- for future maintenance/enhancement
|
||||
- used to communicate with [stakeholders](out/notes/stakeholders.md) and other devs
|
||||
- used to communicate with [[stakeholders]] and other devs
|
||||
|
||||
## Methods
|
||||
- Review existing material
|
||||
- get inital understanding
|
||||
- use as guidelines for [Interviews](out/notes/interviews.md) etc.
|
||||
- use as guidelines for [[Interviews]] etc.
|
||||
- be cautious of existing material
|
||||
- e.g.,
|
||||
- internal -> traning modules, job descriptions, forms, mission statement etc
|
||||
- external -> trade publication, best practives, standards etc.
|
||||
- 
|
||||
- [Interviews](out/notes/interviews.md)
|
||||
- ![[Pasted image 20220315132940.png]]
|
||||
- [[Interviews]]
|
||||
- e.g.,
|
||||
- 
|
||||
- 
|
||||
- [Observation](out/notes/observation.md)
|
||||
- ![[Pasted image 20220315133134.png]]
|
||||
- ![[Pasted image 20220315133326.png]]
|
||||
- [[Observation]]
|
||||
- beware observaion bias
|
||||
- document using workflow diagrams
|
||||
- not necessary to observe all processes at same level of detail
|
||||
- e.g., Apprentice [Needfinding](out/notes/needfinding.md#^4453ee)
|
||||
- [Prototyping](out/notes/prototyping.md)
|
||||
- e.g., Apprentice [[Needfinding#^4453ee]]
|
||||
- [[Prototyping]]
|
||||
- to test and evolve concepts
|
||||
- to evaluate "look and feel"
|
||||
- focus of accomplishing single objective
|
||||
- built quickly using [IDE](out/notes/integrated-development-environments.md) (drag and drop features etc) and/or RAD frameworks
|
||||
- [Questionnaire](None)
|
||||
- built quickly using [[Integrated Development Environments|IDE]] (drag and drop features etc) and/or RAD frameworks
|
||||
- [[Questionnaire]]
|
||||
- Limited information can be gained
|
||||
- Inital insight into business
|
||||
- not suited for gathering detail information
|
||||
- focus of closed-ended questions with simple direct answers
|
||||
- e.g., 
|
||||
- e.g., ![[Pasted image 20220315134147.png]]
|
||||
- Research existing vendor solutions
|
||||
- take advantage of existing tools/software
|
||||
- can avoid mistakes and save time and money
|
||||
@ -80,9 +78,9 @@ Be careful to find a balance between review of the old system and discovery of n
|
||||
- review of models based on findings
|
||||
- PM responsible for system quality
|
||||
- schedule review after doc creation
|
||||
- review conducted by experienced analyst and [stakeholders](out/notes/stakeholders.md), presented by analyst
|
||||
- review conducted by experienced analyst and [[stakeholders]], presented by analyst
|
||||
|
||||
## Use in [Agile Development](out/notes/agile-development.md)
|
||||
## Use in [[Agile Development]]
|
||||
reqs should be decoupled
|
||||
- as inpependent as possible
|
||||
- id which reqs to inplement not to implement them
|
||||
0
content/notes/Simulated Annealing.md
Normal file
0
content/notes/Simulated Annealing.md
Normal file
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Stacks and queues
|
||||
draft: true
|
||||
---
|
||||
# Stacks and queues
|
||||
Dynamic linear data types (interface)
|
||||
- an abstraction of a collection of data organised "in a line" which supprts addition of new elements and the removal of (some) old elements
|
||||
@ -1,10 +1,6 @@
|
||||
---
|
||||
title: Storyboards mockups, paper prototypes
|
||||
draft: true
|
||||
---
|
||||
# Storyboard mockups prototypes
|
||||
|
||||
Fidelity will increase over time.
|
||||
Fidelity will increase over time.![[Pasted image 20220329090249.png]]
|
||||
|
||||
## Storyboarding
|
||||
focus on the **task**
|
||||
@ -32,12 +28,12 @@ use timelimits ≈10 mins
|
||||
- helps get stakeholders onthe same page
|
||||
|
||||
### Examples
|
||||
|
||||
![[Pasted image 20220329090341.png]]
|
||||
|
||||
|
||||
## Paper prototyping
|
||||
mockup of UI on computer
|
||||
|
||||
![[Pasted image 20220329090827.png]]
|
||||
|
||||
### tips
|
||||
- store materials in one place
|
||||
@ -52,4 +48,4 @@ mockup of UI on computer
|
||||
|
||||
|
||||
## Digital mockups
|
||||
|
||||
![[Pasted image 20220329091417.png]]
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Storyboards mockups, prototypes
|
||||
draft: true
|
||||
---
|
||||
# Storyboards mockups, prototypes
|
||||
## 1 storyboards
|
||||
mockup of user scenarios
|
||||
@ -14,9 +10,9 @@ a good storyboard should tell a story
|
||||
short and concise
|
||||
low fidelity
|
||||
not about pretty picures. ⇒ about communicating ideas
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220323104205.png]]
|
||||
![[Pasted image 20220323104240.png]]
|
||||
![[Pasted image 20220323104453.png]]
|
||||
|
||||
## 2 pros
|
||||
+ holistic focus ⇒ helps emphasoze how an interface accopmlishes a task
|
||||
@ -25,18 +21,18 @@ not about pretty picures. ⇒ about communicating ideas
|
||||
|
||||
## 3 Tips
|
||||
tell a story
|
||||
|
||||
![[Pasted image 20220323104649.png]]
|
||||
- base it off the scenario
|
||||
|
||||
play with the angle/perspectives
|
||||
|
||||
|
||||
![[Pasted image 20220323104748.png]]
|
||||
![[Pasted image 20220323104900.png]]
|
||||
|
||||
simplify and develop vocabulary/you own style
|
||||
|
||||
![[Pasted image 20220323104937.png]]
|
||||
|
||||
using tracing and templates
|
||||
|
||||
![[Pasted image 20220323105040.png]]
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Systems analyst
|
||||
draft: true
|
||||
sr-due: 2022-05-18
|
||||
sr-interval: 50
|
||||
sr-ease: 310
|
||||
@ -24,4 +22,4 @@ sr-ease: 310
|
||||
- good understanding of business
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220301172014.png]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Systems development lifecycle (SDLC)
|
||||
draft: true
|
||||
sr-due: 2022-04-13
|
||||
sr-interval: 28
|
||||
sr-ease: 270
|
||||
@ -15,21 +13,21 @@ bpr can be used in the analysis phase to simplify the processes relevant to the
|
||||
|
||||
|
||||
---
|
||||
|
||||
![[Pasted image 20220301172155.png]]
|
||||
# SDLC
|
||||
Provides overall framework for managing the systems
|
||||
There are many methodologies to help guide us through this cycle
|
||||
Each methodology sits on the [Predictive adaptive spectrum](out/notes/predictive-adaptive-spectrum.md)
|
||||
A very common methodology at the moment is [Agile Development](out/notes/agile-development.md)
|
||||
Each methodology sits on the [[Predictive adaptive spectrum]]
|
||||
A very common methodology at the moment is [[Agile Development]]
|
||||
|
||||
## Phases
|
||||
### Analysis
|
||||
^2d7976
|
||||
- Lots of communication with [Stakeholders](out/notes/stakeholders.md)
|
||||
- Lots of communication with [[Stakeholders]]
|
||||
- Gather detailed information
|
||||
- define system requirements
|
||||
- prioritise requirements (what is risky, what brings value to business) -> increase proability of success
|
||||
- develop UI dialogs ([Prototyping](out/notes/prototyping.md) where the user can interact with the system)
|
||||
- develop UI dialogs ([[Prototyping]] where the user can interact with the system)
|
||||
- evaluate requirments
|
||||
- review reccomendations with management
|
||||
|
||||
@ -46,8 +44,8 @@ sys analyst may find opportunites to improve processes
|
||||
simpler business processes -> simpler requirements -> simpler system
|
||||
|
||||
## Requirements
|
||||
- [Requirements](out/notes/requirements.md)
|
||||
- [Requirements elicitation](out/notes/requirements-elicitation.md)
|
||||
- [[Requirements]]
|
||||
- [[Requirements elicitation]]
|
||||
- Something the system should do
|
||||
- Some constraint the system should have
|
||||
- Can be functional or non functional
|
||||
@ -57,7 +55,7 @@ simpler business processes -> simpler requirements -> simpler system
|
||||
- different terminology
|
||||
- change focus on people
|
||||
- change speed of development
|
||||
- [Prototyping](out/notes/prototyping.md)
|
||||
- [[Prototyping]]
|
||||
- Rapid application development (RAD)
|
||||
|
||||
## Failure
|
||||
@ -67,15 +65,15 @@ main goal: Avoid project failure
|
||||
- cost overruns
|
||||
- sw quality issues
|
||||
- missed deadlines
|
||||
- unhappy [stakeholders](out/notes/stakeholders.md)
|
||||
- unhappy [[stakeholders]]
|
||||
|
||||
Suprisingly very common with large projects
|
||||
|
||||
reasons for fail:
|
||||
|
||||
|
||||
![[Pasted image 20220301172507.png|300]]
|
||||
![[Pasted image 20220310160839.png|300]]
|
||||
|
||||
|
||||
**coding rarely causes problems**
|
||||
|
||||
![[Pasted image 20220310161009.png|300]]
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Test driven development
|
||||
draft: true
|
||||
---
|
||||
# Test driven development
|
||||
tests are developed before the code
|
||||
are a spec of what the code should do
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Unified process (UP)
|
||||
draft: true
|
||||
sr-due: 2022-04-11
|
||||
sr-interval: 20
|
||||
sr-ease: 250
|
||||
@ -29,9 +27,9 @@ four phase life cycle
|
||||
- construction
|
||||
- transition
|
||||
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220308132944.png]]
|
||||
![[Pasted image 20220308133325.png]]
|
||||
![[Pasted image 20220322172120.png]]
|
||||
|
||||
##### best practices
|
||||
- develop iteratively
|
||||
@ -64,11 +62,11 @@ that keep you on track and that can be reversed if necessary.
|
||||
- Model with a purpose — to understand and communicate.
|
||||
- Build multiple models — look at problems from different
|
||||
perspectives.
|
||||
- Build high-quality models and get feedback — from [stakeholders](out/notes/stakeholders.md), other developers.
|
||||
- Build high-quality models and get feedback — from [[stakeholders]], other developers.
|
||||
- Focus on content, not representation — always focus on stakeholder needs; informal hand-drawn models are often fine.
|
||||
- Communicate and learn from each other.
|
||||
- Know your models and how to use them.
|
||||
- Adapt to specific project needs.
|
||||
- Maximise stakeholder ROI.
|
||||
|
||||
|
||||
![[Pasted image 20220308132628.png]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Union Find-Disjoint set
|
||||
draft: true
|
||||
sr-due: 2022-04-17
|
||||
sr-interval: 30
|
||||
sr-ease: 270
|
||||
@ -157,10 +155,10 @@ since the time for $Find$ is big-$\theta$ of the rank of the representative foun
|
||||
^we used $O$ not $\theta$ because we dont know that the worst case will always occur.
|
||||
If could happen that the sequence of Union operations does not create a rank that is as big as i could be
|
||||
|
||||
^this is an example of a semi-formal proof by [Induction](out/notes/induction.md)
|
||||
^this is an example of a semi-formal proof by [[Induction]]
|
||||
|
||||
### 3.4 UF 4
|
||||
Change find so it implements [path compression](None) to "flatten" the chains
|
||||
Change find so it implements [[path compression]] to "flatten" the chains
|
||||
|
||||
```java
|
||||
if (x != reps[x]) {
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Unit testing
|
||||
draft: true
|
||||
---
|
||||
# Unit testing
|
||||
- divide code into units ⇒ test those units
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Use case diagrams
|
||||
draft: true
|
||||
---
|
||||
# Use case diagrams
|
||||
- specifies the participants (actors) and the relationships between them
|
||||
- high level view of what a system does (not how) and who uses it
|
||||
@ -26,7 +22,7 @@ draft: true
|
||||
### 2.1 Actor
|
||||
- roles that people have when interacting with the system
|
||||
- external systems or hardware that are essential to system operation
|
||||
|
||||
![[Pasted image 20220320224458.png]]
|
||||
|
||||
### 2.2 Use case
|
||||
- discrete unit of system functionality
|
||||
@ -34,13 +30,13 @@ draft: true
|
||||
- can be abstract or focused
|
||||
- say nothing about flow or behaviour
|
||||
- map to ⇒ menu items, forms, reports, etc
|
||||
|
||||
![[Pasted image 20220320224329.png]]
|
||||
|
||||
### 2.3 Association
|
||||
- relationship (interaction) between actor and use casel
|
||||
- actor can be associated with more than one use case
|
||||
- use case can be associated with more than one actor
|
||||
- 
|
||||
- ![[Pasted image 20220320224618.png]]
|
||||
|
||||
### 2.4 Specialisation/generalisation
|
||||
- actors and use cases can be orgainsed into special/general hierachies
|
||||
@ -48,7 +44,7 @@ draft: true
|
||||
- same for use cases
|
||||
- mutually exclusive
|
||||
- similar to inheritance
|
||||
|
||||
![[Pasted image 20220320224736.png]]
|
||||
|
||||
### 2.5 Dependency
|
||||
- occur between use cases
|
||||
@ -57,24 +53,24 @@ draft: true
|
||||
- one case requires the behaviour of another
|
||||
- read in direction of arrow
|
||||
- indicate opportunities for reuse of functionality
|
||||
|
||||
![[Pasted image 20220320224908.png]]
|
||||
|
||||
#### 2.5.1 Extends dependency
|
||||
- use cases can have optional, subordinate tasks
|
||||
- useful with specialised actors
|
||||
|
||||
![[Pasted image 20220320225018.png]]
|
||||
|
||||
|
||||
#### 2.5.2 Includes dependency
|
||||
- use cases that have mandatory, subordinate tasks
|
||||
- does not indicate sequence, only that they must happen
|
||||
|
||||
![[Pasted image 20220320225129.png]]
|
||||
|
||||
#### 2.5.3 Requires dependency
|
||||
- mandatory, _independent_ tasks, that must be completed first
|
||||
- forces sequence
|
||||
- use sparingly
|
||||
|
||||
![[Pasted image 20220320225301.png]]
|
||||
|
||||
## 3 development of use case diagrams
|
||||
organise related use case diagrms itno use case model
|
||||
@ -99,7 +95,7 @@ identify actors ⇒ identify use cases ⇒ detail use cases
|
||||
create scenario ⇒ generalise scenario ⇒ organise use case model
|
||||
|
||||
## 4 Examples
|
||||
|
||||
|
||||
|
||||
|
||||
![[Pasted image 20220320225922.png|300]]
|
||||
![[Pasted image 20220320225932.png|300]]
|
||||
![[Pasted image 20220320230001.png|300]]
|
||||
![[Pasted image 20220320230009.png|300]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: User Experience
|
||||
draft: true
|
||||
sr-due: 2022-05-01
|
||||
sr-interval: 37
|
||||
sr-ease: 290
|
||||
@ -14,5 +12,5 @@ sr-ease: 290
|
||||
|
||||
Marketing, branding, etc.
|
||||
|
||||
|
||||
![[Pasted image 20220302103456.png|1/2]]
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Version Control Systems
|
||||
draft: true
|
||||
sr-due: 2022-04-30
|
||||
sr-interval: 39
|
||||
sr-ease: 270
|
||||
@ -19,7 +17,7 @@ resources: https://www.youtube.com/watch?v=Yc8sCSeMhi4
|
||||
|
||||
# VCSs
|
||||
VCSs (version control systems) Are systems to keep track of changes to a set of files
|
||||
E.g., [Git](out/notes/git.md)
|
||||
E.g., [[Git]]
|
||||
|
||||
## 1 Goals
|
||||
- allow collaboration
|
||||
@ -30,7 +28,7 @@ E.g., [Git](out/notes/git.md)
|
||||
- not restrict workflow
|
||||
|
||||
## 2 Terms
|
||||
[Git Cheat Sheet](out/notes/git-cheat-sheet.md)
|
||||
[[Git Cheat Sheet]]
|
||||
|
||||
## 3 Discipline
|
||||
- Pull/Push Regularly
|
||||
@ -92,4 +90,4 @@ many copies of a project's source code files needed:
|
||||
- developing new features
|
||||
- reviewing code changes
|
||||
- managing releases of sofware products
|
||||
- using [Git](out/notes/git.md)
|
||||
- using [[Git]]
|
||||
@ -1,22 +1,18 @@
|
||||
---
|
||||
title: What is Usability
|
||||
draft: true
|
||||
---
|
||||
Jet Hughes 9474308
|
||||
|
||||
|
||||
## 1.1 Blackboard
|
||||
|
||||
![[Pasted image 20220317125811.png|300]]
|
||||
The first example of bad usability is in blackboard. Blackboard is a "web based virtual learning environment and learning management system". The issue occurs with the menu in the top right (shown below) when the window in which the user is viewing the page is smaller (either on a mobile device or a shrunk down desktop Browser).
|
||||
|
||||
|
||||
![[Pasted image 20220310211739.png|300]]
|
||||
|
||||
The issue is that the menu gets hidden behind the main page when the window is smaller (shown below)
|
||||
This means that when the user is using black board in a small browser window, they are unable to navigate between their courses in the intended way. This is an example of bad usability because it prevents the user from being able to use the product for its intended purpose. It is not effective, efficient nor satisfactory.
|
||||
|
||||
|
||||
## 1.2 Sky go
|
||||
|
||||
![[Pasted image 20220310212758.png|150]]
|
||||
|
||||
The second example is an issue with the web application sky go. Sky go is a television streaming service. It allows users to watch on demand or live Sky TV with just an internet connection. There is a usability issue with the sign in screen on desktop browsers, which may also affect mobile and other platforms. In particular, with the error messages. On some plans, users are only allowed to use the account on one device at a time. When logging in, if another user is already signed in on another device, the login will fail. In such an event, the error message displayed alerts the user that their username or password are incorrect, not that another user is logged in.
|
||||
|
||||
@ -24,14 +20,14 @@ This is an example of bad usability due to uninformative error messages. In this
|
||||
|
||||
|
||||
## 1.3 Udisc
|
||||
|
||||
![[Pasted image 20220317145732.png|150]]
|
||||
My third example is of the Mobile App Udisc. Udisc is a disc golf scoring app. The problem with this app occurs when in the "select players" phase of creating a new round scorecard. The user can choose to add existing players, or they can create a new player using the icon in the top right of the page. The issue is that after adding a new player and returning to the select players screen, the new player is not visible. To make the new player visible, the user somehow reload the page, without a reload button. One way is to switch from the 'frequent' tab to the 'recent' or the 'all' tab. This will reload the page and the added player will appear in all tabs.
|
||||
|
||||
It was hard to show this with just screenshots, so I recorded a GIF and uploaded to Imgur [https://i.imgur.com/VuXshdZ.gif](https://i.imgur.com/VuXshdZ.gif)
|
||||
|
||||
|
||||
## 1.4 Epomaker
|
||||
|
||||
![[Pasted image 20220315113752.png|300]]
|
||||
My final example of bad usability is the Epomaker website. This is a mechanical keyboard ecommerce site. On loading the create an account page, a cookies pop obscured behind the floating 'rewards' button appears. The final line of the message and the bottom left portion of the pop-up is not visible. When I saw this, I thought there might be an option to configure my cookie settings hidden behind the floating button. I didn't want to allow the site to use cookie's that weren't strictly necessary. So I just ignored the pop-up and finished creating my account while the pop-up was obscuring the bottom left of the page. This is bad usability because the pop blocked me from being able to create an account as easily as I could have.
|
||||
|
||||
|
||||
@ -39,9 +35,9 @@ My final example of bad usability is the Epomaker website. This is a mechanical
|
||||
Finally I have an example of a web app that is usable, but has a bad user experience. This app is NZ Herald. Upon loading the page, the user is faced with a screen that is at least 75% advertisements. The app still has good usability as the user can easily scroll down which hides most of the ads, so there are only the strips on the sides. However, the initial loading page is crammed full of advertisements. This bombardment of ads makes the site appear unprofessional, and untrustworthy, despite the "website of the year" stub. This degradation of trust contributes to a bad user experience, despite the overall usability.
|
||||
|
||||
On entry:
|
||||
|
||||
|
||||
![[Pasted image 20220318141434.png|300]]
|
||||
![[Pasted image 20220318141839.png|300]]
|
||||
|
||||
|
||||
After scrolling down
|
||||
|
||||
![[Pasted image 20220318144803.png|300]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: analysis of recursive algorithms
|
||||
draft: true
|
||||
aliases: Proof by induction, induction
|
||||
sr-due: 2022-05-02
|
||||
sr-interval: 29
|
||||
@ -38,7 +36,7 @@ ___
|
||||
- inductive approach is esential for understanding time-complexity of resursive algorithms
|
||||
|
||||
## 2 Proof by induction
|
||||
[Induction](out/notes/induction.md)
|
||||
[[Induction]]
|
||||
Find a (positive integer) _parameter_ that gets smaller in all recursive calls
|
||||
Prove inductively that "for all values of the parameter, the result computed is correct"
|
||||
To do that:
|
||||
@ -47,7 +45,7 @@ To do that:
|
||||
|
||||
## 3 Examples
|
||||
### 3.1 Quicksort
|
||||
[divide and conquer](None) algorithm
|
||||
[[divide and conquer]] algorithm
|
||||
sorts a range in an array (a group of elements between some lower index, $lo$ inclusive and some upper index $hi$ exclusive) as follows:
|
||||
- If length of range $(hi - lo)$ is at most 1 -> do nothing
|
||||
- otherwise, choose a pivot p (e.g., the element at $lo$) and:
|
||||
@ -1,11 +1,7 @@
|
||||
---
|
||||
title: assignment 1
|
||||
draft: true
|
||||
---
|
||||
# COSC201 Assignment 1: Counting the seas
|
||||
|
||||
## 1 Due : 11:59 p.m. Friday, April 1, 2022
|
||||
[9474308Hughes](None)
|
||||
[[9474308Hughes]]
|
||||
## 2 Introduction
|
||||
|
||||
Imagine a square world consisting of cells each of which is either land or water. A
|
||||
@ -17,12 +13,12 @@ distinct bodies of water there are on each of them.
|
||||
Here’s a world that you discovered recently – its dimensions are 8 × 8 and it has only
|
||||
14 land cells.
|
||||
|
||||
|
||||
![[Pasted image 20220314221111.png]]
|
||||
|
||||
Obviously, in this world there is only one giant sea. On the other hand, another world
|
||||
with a 10 × 10 grid was also recently discovered:
|
||||
|
||||
|
||||
![[Pasted image 20220314221121.png]]
|
||||
|
||||
This world is dominated by land, and there are 10 seas. You may disagree, and think
|
||||
there are 15 seas, but water cells are considered to be part of the same sea if they meet
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Big-O
|
||||
draft: true
|
||||
sr-due: 2022-06-01
|
||||
sr-interval: 62
|
||||
sr-ease: 271
|
||||
|
||||
@ -1,6 +1,2 @@
|
||||
---
|
||||
title: Books
|
||||
draft: true
|
||||
---
|
||||
# Books
|
||||
[All the light we cannot see](out/notes/all-the-light-we-cannot-see.md)
|
||||
[[All the light we cannot see]]
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Branch
|
||||
draft: true
|
||||
sr-due: 2022-04-10
|
||||
sr-interval: 13
|
||||
sr-ease: 210
|
||||
|
||||
@ -1,7 +0,0 @@
|
||||
---
|
||||
title: Cheat Sheets
|
||||
draft: true
|
||||
---
|
||||
|
||||
[Git Cheat Sheet](out/notes/git-cheat-sheet.md)
|
||||
[WinComposeS](out/notes/wincomposes.md)
|
||||
@ -1,9 +1,5 @@
|
||||
---
|
||||
title: CROCS
|
||||
draft: true
|
||||
---
|
||||
# CROCS - Communist republic of computer science
|
||||
 
|
||||
![[Pasted image 20220311100212.png]] ![[Pasted image 20220311100213.png]]
|
||||
|
||||
## TODO
|
||||
- [ ] Setup gitlab
|
||||
|
||||
@ -1,4 +0,0 @@
|
||||
---
|
||||
title: Daily notes
|
||||
draft: true
|
||||
---
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Debugging
|
||||
draft: true
|
||||
---
|
||||
# Debugging
|
||||
removing technical faults
|
||||
isolaing and remove technical faults
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
---
|
||||
title: Developer
|
||||
draft: true
|
||||
sr-due: 2022-05-13
|
||||
sr-interval: 46
|
||||
sr-ease: 290
|
||||
@ -9,7 +7,7 @@ tags: #review
|
||||
|
||||
---
|
||||
# Developer
|
||||
|
||||
![[Pasted image 20220301172040.png]]
|
||||
|
||||
## Role
|
||||
- translate technical specs into code
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: Documentation
|
||||
draft: true
|
||||
---
|
||||
# Documentation
|
||||
## 1 Who, what where
|
||||
- Audience
|
||||
|
||||
@ -1,16 +1,12 @@
|
||||
---
|
||||
title: Ethics
|
||||
draft: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
coded biases doco
|
||||
# Ethics
|
||||
## 1 Case studies
|
||||
1. [facial recognition in US riots 2021-01-06](out/notes/facial-recognition-in-us-riots-2021-01-06.md)
|
||||
2. [Anti govt protest china](out/notes/anti-govt-protest-china.md)
|
||||
3. [How is safe enough for autonomous vehicles](out/notes/how-is-safe-enough-for-autonomous-vehicles.md)
|
||||
1. [[facial recognition in US riots 2021-01-06]]
|
||||
2. [[Anti govt protest china]]
|
||||
3. [[How is safe enough for autonomous vehicles]]
|
||||
|
||||
### 1.1 Differences 1 vs 2
|
||||
Govt vs vigilante
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
title: facial recognition in US riots 2021-01-06
|
||||
draft: true
|
||||
---
|
||||
# Capital riots face recognition
|
||||
capital riots occured on 2021-01-06
|
||||
|
||||
@ -1,10 +1,6 @@
|
||||
---
|
||||
title: Finance
|
||||
draft: true
|
||||
---
|
||||
# Finance
|
||||
## Trading
|
||||
[Options](out/notes/options.md)
|
||||
[[Options]]
|
||||
|
||||
## Tech
|
||||
[Blockchain](None)
|
||||
[[Blockchain]]
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user