Enrol to start learning
Reading is open to everyone. Enrolling is free, and it is what unlocks the audio lessons, practice tests and progress tracking.
2.4.3. Hands-on Implementation
Interactive Audio Lesson
Unlock the classroom podcast
The transcript is above and free to read. A free account plays the conversation back.
Create a free account
Today, we will begin drafting our personas. Remember, a persona includes a name, photo, demographics, goals, pain points, and a quote. Let's start by asking: What are the key components of a persona?
I think it should have someone's background and what they want from the product.
Yeah, and we should include their challenges too!
Exactly! Including the pain points helps us understand the user better. Can anyone think of a quote we might include?
Maybe a quote that shows their frustration with an existing solution?
Great idea! Always think of the user’s perspective. Let’s move on to drafting our personas individually.
Unlock the classroom podcast
The transcript is above and free to read. A free account plays the conversation back.
Create a free account
Now that you have your personas drafted, let’s discuss requirements. Who can tell me the difference between functional and non-functional requirements?
Functional requirements are what the system must do, like features, while non-functional are things like performance and security.
Exactly! When you write these requirements, be sure to tie them back to your research findings. What might be an example of a functional requirement?
A requirement could be that the app must allow users to create an account.
And it should also mention the security measures to protect user data!
Well done! Ensure you have at least eight functional requirements backed by evidence from your research.
Unlock the classroom podcast
The transcript is above and free to read. A free account plays the conversation back.
Create a free accountNow, let's focus on the peer review process. Why is it important to exchange drafts with your partner?
It helps us get an outsider's perspective on our work.
And they might notice things we missed or suggest improvements!
Exactly! Remember to use constructive feedback. What are some areas to focus on when reviewing?
Clarity and whether the requirements are measurable.
Correct! After your reviews, you should iterate on your drafts to improve them.
Unlock the classroom podcast
The transcript is above and free to read. A free account plays the conversation back.
Create a free accountFinally, let’s talk about the Traceability Matrix. Who can explain its purpose?
Isn't it used to link requirements back to our research data?
Exactly! It ensures that every requirement is justified by evidence. How do we create this matrix?
We should list our requirements on one side and the corresponding data points from our research on the other.
Correct! This helps in tracking the validity of your design decisions. Make sure to keep this updated as you refine your documents.
Overview
Short Summary
This section focuses on the practical draft and creation of a design specification, emphasizing collaboration and iterative improvement.
Medium Summary
Hands-on implementation is a critical phase of creating a design specification where students draft essential sections, collaborate with peers for feedback, and ensure that elements like personas and requirements are well linked to research evidence. It highlights the importance of documentation and adaptability in the design process.
Detailed Summary
Hands-on Implementation
In this section, students engage in practical exercises to draft the key components of a design specification. The focus is on creating detailed personas and requirements sections, with an emphasis on peer collaboration and iterative feedback. The process begins with individual drafting, followed by a systematic review where students exchange their drafts with partners. This encourages critical thinking and adaptability as students identify areas needing clarity or additional evidence, fostering a collaborative learning environment. The section also introduces the Traceability Matrix, a tool essential for linking requirements to specific data points from research findings.
Key Concepts
Core takeaways and short definitions to help you quickly recall the key ideas from this section.
Iterative Drafting: The process of continuously revising work based on feedback.
Peer Review: The practice of evaluating others' work to provide constructive criticism.
Traceability Matrix: A documentation tool linking requirements to research data.
Examples
Step-by-step examples to apply the section's ideas and test your understanding.
When drafting a persona, a student might create 'Priya', a 17-year-old with a busy schedule who struggles with managing events, which includes her typical frustrations detailed in a quote.
A functional requirement example could be: 'The app must allow users to sign up for events via a digital platform within a minute.'
Memory Aids
Interactive tools to help you remember key concepts