Reflection sheet containing the journal 141, Lecture notes of Information Systems

This sheet helped me a lot with the journal as I was a bit confused, let me know if this helps!

Typology: Lecture notes

2021/2022

Uploaded on 08/08/2023

julian-mccarthy
julian-mccarthy 🇳🇿

2 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Analysis and Design Project – Reflection Journal
(2022.T2 INFO141 System Analysis, 11%)
Task
Having completed your analysis & design journey, you must now reflect on the experience. When doing so, you
should consider the different concepts and techniques of the phases and how they fit together: from your
empathising (stakeholders, gathering information, empathy mapping, POV); to your defining (problem
determination, causal mapping and five whys, and problem statement); to your ideation (from preparation with your
ways of questions, to generating ideas, to narrowing down to which idea(s) to focus on); to your prototyping (how
you decided what to prototype, choosing how to prototype, to building the prototype) to testing (your test plan and
your experience in executing it); to your requirements determination (mapping requirements, deciding on a walking
skeleton, writing user stories and acceptance criteria).
This must be done over three areas: the good, the bad, and the ugly:
The good refers to describing things that went well, and/or exciting discoveries that were made.
The bad refers to things that did not go so well, and lessons you learned that you would adopt in another
cycle of design thinking, and how you can improve going forward.
The ugly refers to where you should describe things that should never have happened, where you can
discuss how and why they occurred. Consider what you are doing or will do to turn the ugly into something
beautiful.
Note. The bad is what didn't go as planned or problems that surfaced when you worked on your project.
The ugly is a complete “failure” – the things that you should never do in this project.
In each of these areas you should consider:
The relevance of the learning experience reflected in relation to the your, and the course’s, learning goals
(i.e., application of analysis and design concepts, techniques, and processes to the project).
oYour reflection should not simply repeat what the readings or course instructors said (e.g.,
copying or paraphrasing statements from slides without relating to your project). You must put
your reflections in the context of your project.
An analysis of how the experience contributed to your understanding of self, and design thinking and agile
system analysis concepts.
oYou should move beyond a simple description of the analysis & design process, and critically
assess analysis & design concepts, techniques, or processes.
oYou can give specific examples. But keep it brief and focus on how and why the specific
experience matters in the project (from the good, the bad, or the ugly perspective).
oYou consider your experiences across the application of different concepts or techniques and
reflect on how these concepts/techniques work together or against each other. Those experiences
can also be discussed in relation to what has been taught.
Self-criticism where you question your own biases, stereotypes, preconceptions, and/or assumptions
during the analysis & design process, defining new modes of thinking as a result. Self-criticism is the
highest level of reflection. It implies the transformation of perspectives.
Condition: This is an individual assignment. You must submit it, in a PDF format, via Blackboard
Due Date: before 5.00pm, Friday 28th October
pf3

Partial preview of the text

Download Reflection sheet containing the journal 141 and more Lecture notes Information Systems in PDF only on Docsity!

Analysis and Design Project – Reflection Journal

(2022.T2 INFO141 System Analysis, 11%)

Task

Having completed your analysis & design journey, you must now reflect on the experience. When doing so, you should consider the different concepts and techniques of the phases and how they fit together: from your empathising (stakeholders, gathering information, empathy mapping, POV); to your defining (problem determination, causal mapping and five whys, and problem statement); to your ideation (from preparation with your ways of questions, to generating ideas, to narrowing down to which idea(s) to focus on); to your prototyping (how you decided what to prototype, choosing how to prototype, to building the prototype) to testing (your test plan and your experience in executing it); to your requirements determination (mapping requirements, deciding on a walking skeleton, writing user stories and acceptance criteria). This must be done over three areas: the good , the bad , and the ugly :  The good refers to describing things that went well, and/or exciting discoveries that were made.  The bad refers to things that did not go so well, and lessons you learned that you would adopt in another cycle of design thinking, and how you can improve going forward.  The ugly refers to where you should describe things that should never have happened, where you can discuss how and why they occurred. Consider what you are doing or will do to turn the ugly into something beautiful. Note. The bad is what didn't go as planned or problems that surfaced when you worked on your project. The ugly is a complete “failure” – the things that you should never do in this project. In each of these areas you should consider:  The relevance of the learning experience reflected in relation to the your, and the course’s, learning goals (i.e., application of analysis and design concepts, techniques, and processes to the project). o Your reflection should not simply repeat what the readings or course instructors said (e.g., copying or paraphrasing statements from slides without relating to your project). You must put your reflections in the context of your project.  An analysis of how the experience contributed to your understanding of self, and design thinking and agile system analysis concepts. o You should move beyond a simple description of the analysis & design process, and critically assess analysis & design concepts, techniques, or processes. o You can give specific examples. But keep it brief and focus on how and why the specific experience matters in the project (from the good, the bad, or the ugly perspective). o You consider your experiences across the application of different concepts or techniques and reflect on how these concepts/techniques work together or against each other. Those experiences can also be discussed in relation to what has been taught.  Self-criticism where you question your own biases, stereotypes, preconceptions, and/or assumptions during the analysis & design process, defining new modes of thinking as a result. Self-criticism is the highest level of reflection. It implies the transformation of perspectives. Condition: This is an individual assignment. You must submit it, in a PDF format, via Blackboard Due Date: before 5.00pm, Friday 28th^ October

The word limit is up to 1200 words. Please refer to the rubric to see how you will be evaluated.

The Good

Describe things that went well and/or exciting discoveries

(up to 400 words)

The Bad

Describe things that did not go so well, lessons learned, and how you can look for improvements

(up to 400 words)

The Ugly

Describe things that should have never happened, and discuss how and why they occurred

(up to 400 words)