Unit 2 DT Ii
Unit 2 DT Ii
Greater Noida
Unit:2
Course Details
(Ex: B Tech V Sem)
CO2 Generate innovate ideas using design thinking tools and K3,K4
converge to feasible idea for breakthrough solution
CO3 Implement storytelling for persuasive articulation K3
Design Thinking
PO1
CO.K PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO12
1
ACSE0503.1 3 3 3 3 2 - - - 2 2 - 3
ACSE0503.2 3 3 3 3 2 2 - 1 1 1 - 3
ACSE0503.3 3 3 2 3 3 2 - 2 1 1 2 3
ACSE0503.4 3 3 3 3 2 2 - 2 2 1 3 3
ACSE0503.5 2 2 2 2 2 2 - 2 1 1 1 2
Average 2.8 2.8 2.6 2.8 2.2 1.6 - 1.8 1.4 1.2 1.2 2.8
PEO3: Exhibit professional ethics and moral values with good leadership
qualities and effective interpersonal skills.
B TECH
(SEM-V) THEORY EXAMINATION 20__-20__
COMPILER DESIGN
Time: 3 Hours Total
Marks: 100
Note: 1. Attempt all Sections. If require any missing data; then choose
suitably.
SECTION A
1.Q.No.
Attempt all questions in brief.
Question Marks 2 xCO10 =
20
1 2
2 2
. .
10 2
SECTION B
2. Attempt any three of the following: 3 x 10 = 30
1 10
2 10
01/20/2025 Dr. Rashmi Mishra Unit II 14
Prerequisite and Recap
https://careerfoundry.com/en/blog/ux-design/what-is-design-thinking-everything-
you-need-to-know-to-get-started/
https://www.youtube.com/watch?v=-ySx-S5FcCI
Refine and narrow down to the best idea, 10-100-1000gm, QBL, Design Tools for
Convergence – SWOT Analysis for 1000gm discussion. In-class activity for 10-100-
1000gm & QBL
• In the Ideation stage, design thinkers spark off ideas — in the form of
questions and solutions — through creative and curious activities such as
Brainstorms and Worst Possible Idea.
• “Ideation is the mode of the design process in which you concentrate on idea
generation. Mentally it represents a process of “going wide” in terms of
concepts and outcomes. Ideation provides both the fuel and also the source
material for building prototypes and getting innovative solutions into the
hands of your users.”
There are hundreds of ideation methods. Some methods are merely renamed or
slightly adapted versions of more foundational techniques. Here you’ll get a brief
SWOT analysis involves making lists – but so much more, too! When you
begin to write one list (say, Strengths), the thought process and research that
you'll go through will prompt ideas for the other lists (Weaknesses,
Opportunities or Threats). And if you compare these lists side by side, you
will likely notice connections and contradictions, which you'll want to
highlight and explore.
• SWOT Analysis matrix:
Strengths Weaknesses
What do you do well? What could you improve?
What unique resources can you Where do you have fewer
draw on? resources than others?
What do others see as your What are others likely to see as
strengths? weaknesses?
Opportunities Threats
What opportunities are open to What threats could harm you?
you? What is your competition doing?
What trends could you take What threats do your weaknesses
advantage of? expose to you?
How can you turn your strengths
into opportunities?
Strengths
• Strengths are things that your organization does particularly well, or in a
way that distinguishes you from your competitors. Think about the
advantages your organization has over other organizations. These might be
the motivation of your staff, access to certain materials, or a strong set of
manufacturing processes.
• What unique or lowest-cost resources can you draw upon that others can't?
Identify and analyze your organization's Unique Selling Proposition (USP),
and add this to the Strengths section.
Weaknesses
• Once again, imagine (or find out) how other people in your
market see you. Do they notice weaknesses that you tend to be
blind to? Take time to examine how and why your competitors
are doing better than you. What are you lacking?
Opportunities
• Opportunities are openings or chances for something positive to
happen, but you'll need to claim them for yourself!
• They usually arise from situations outside your organization, and
require an eye to what might happen in the future. They might arise as
developments in the market you serve, or in the technology you use.
Being able to spot and exploit opportunities can make a huge
difference to your organization's ability to compete and take the lead
in your market.
• Think about good opportunities that you can exploit immediately.
These don't need to be game-changers: even small advantages can
increase your organization's competitiveness. What interesting market
trends are you aware of, large or small, which could have an impact?
• You should also watch out for changes in government policy related
to your field. And changes in social patterns, population profiles, and
lifestyles can all throw
01/20/2025 Dr. up interesting
Rashmi Mishra opportunities.
Unit I 44
I
How to Write a SWOT Analysis
Threats
• Threats include anything that can negatively affect your business from the
outside, such as supply-chain problems, shifts in market requirements, or a
shortage of recruits. It's vital to anticipate threats and to take action against
them before you become a victim of them and your growth stalls.
• Think about the obstacles you face in getting your product to market and
selling. You may notice that quality standards or specifications for your
products are changing, and that you'll need to change those products if you're
to stay in the lead. Evolving technology is an ever-present threat, as well as an
opportunity!
• Always consider what your competitors are doing, and whether you should be
changing your organization's emphasis to meet the challenge. But remember
that what they're doing might not be the right thing for you to do. So, avoid
copying them without knowing how it will improve your position.
• Be sure to explore whether your organization is especially exposed to external
challenges. Do you have bad debt or cash-flow problems, for example, that
could make you vulnerable to even small changes in your market? This is the
kind of threat that can seriously damage your business, so be alert.
01/20/2025 Dr. Rashmi Mishra Unit I 45
I
A SWOT Analysis Example
Imagine this scenario: a small start-up consultancy wants a clear picture of its current
situation, to decide on a future strategy for growth. The team gathers, and draws up the
SWOT Analysis:
Strengths Weaknesses
What do you do well? What could you improve?
What unique resources can you Where do you have fewer
draw on? resources than others?
What do others see as your What are others likely to see as
strengths? weaknesses?
Opportunities
Threats
What opportunities are open to you?
What threats could harm you?
What trends could you take advantage
What is your competition doing?
of?
What threats do your weaknesses
How can you turn your strengths into
expose to you?
opportunities?
direction.
• Prototypes can take many forms, and just about the only thing in
common the various forms have is that they are all tangible forms of
your ideas.
01/20/2025 Dr. Rashmi Mishra Unit I 50
I
Prototyping in design thinking
The need for prototyping: A good and early prototype serves three core
functions:
1. It takes ideas from the abstract to the concrete, giving them the much-needed
body and soul
2. A prototype helps get the buy-in from your team members, senior managers and
customers, as at least one of the possible outcomes.
3. Prototyping makes it possible to seek feedback and avenues of improvement
more objectively and readily.
One of the masters of the prototyping mindset was Thomas Edison, who famously
quipped, ‘None of my inventions came by accident. I see a worthwhile need to be
met and I make trial after trial until it comes. What it boils down to is one percent
inspiration and ninety-nine percent perspiration.’
Sketches
While sketches are often considered to not be technically prototypes, they can be
extremely helpful for making decisions, mostly because they are incredibly easy to
create and even easier to discard. We don’t need any artistic skill to sketch well, so this
is a great tool for designers and non-designers alike.
Pros of sketches
• They are extremely cheap and fast to create. As such, you can sketch out a large
number of ideas in a short amount of time.
• You can do it anywhere: with pen and paper or digitally on your smartphone,
tablet or desktop computer.
• They are disposable, so you won’t get attached to sketches that turn out to be bad
ideas.
Cons of sketches
• Sketches lack detail and are ambiguous by design. As such, you cannot use
sketches to convey complex interactions of an app.
• Sketches are almost never of high enough fidelity to be useful with people outside
of the team, since they rarely have the context to understand what the sketch is
meant to convey.
• Sketches are not very helpful in convergent processes where you want to select a
few best ideas—other forms of prototypes, such as paper prototypes or wireframes,
are more helpful.
Paper Prototypes
• Paper prototype sketching templates can help you speed up your process.
However, you don’t need them and simple sketches on blank sheets of paper
will work just as well.
• You don’t even need to use a ruler—however, you should ensure your paper
prototypes are neat and legible, of course.
• Test your paper prototypes on users. Play-act with them to let them know what
happens when they click on a certain button, for instance.
Mock-Ups
Mock-ups are dummies that simulate the user interface of an executable program,
sometimes even functions. This makes it possible to test the planned solution before
developing it completely.
• Mock-ups should feel realistic so that testers and customers can provide specific
feedback and ask specific questions. User tests with mock-ups increase the quality
and user-friendliness of the developed program already before its first completion.
How to do it?
• Define which components of the idea should be represented.
• Decide on an implementation form (paper, mock-up tool).
• First design the frame components.
• Then move on to designing the more specific components.
01/20/2025 Dr. Rashmi Mishra Unit I 65
I
Tools for prototyping
• When promising ideas have already been further developed and they result
in a consistent concept.
• To test whether this solution is visually feasible and clear for the user. The
program.
Pseudo-code is "language" where you can write all of your coding logic
• There are projects that are so massive that if you don't take the time to
code. When you write some pseudo-code, it gives you a chance to really
think through potential issues. You're able to look at pure logic and
• Writing pseudo-code before you start typing real code will also help you
finish your projects faster.
• Think of it as a blueprint.
• The best part is that pseudo-code doesn't depend on any programming
language. That logic you just wrote out can be taken by anyone and
translated into their language of choice. It gives you the freedom to reuse
and improve the architecture of the application that you're building.
• One of the more subtle uses of pseudo-code is to share it with other people.
• Another great feature is that you can write pseudo-code in any format you
like.
Interaction flows:
Flowcharts are diagrams of user flows and tasks in processes. Designers use
these versatile tools to visualize the interactions in designs and present easy-
to-understand maps of designs to stakeholders. They connect labeled,
standardized symbols with lines to show everything users might do in
interactive contexts.
Designers use flowcharts mainly to plot how users move through an
interface, such as an app, to achieve their goals.
• Present to stakeholders:
Internal stakeholders can examine flowcharts whenever you
need approval/buy-in before you can proceed to prototyping.
External stakeholders (e.g., clients) can understand your
project’s scale and scope
01/20/2025 Dr. Rashmi Mishra Unit I 70
I
Napkin Pitch
an idea or concept. Using this style to describe your ideas or strategy for a
new concept can ensure that the description stays simple and short.
• The napkin pitch provides a simple, consistent format for summarizing and
• For a given concept, the napkin pitch describes the target stakeholders, their
unmet need, and why your offering creates novel value for them; the
elements you will make, buy, and partner for; the channels you will use; and
• Imagine you’ve got a brilliant business idea and all your close ones liked it
and encouraged you to try. Can you be sure they did so not only because
they didn’t want to hurt you and break your relations? Before investing
every single penny into developing a full-feature solution, you need to
check your hypothesis with a broader, not-biased audience.
• You can do this by creating a minimal version of your product with core
features that address the primary customer’s problem you’re going to
solve.
• The main purpose of an MVP is to test the essence of the product idea,
analyze users’ feedback, and create a full product version based on the
insights.
01/20/2025 Dr. Rashmi Mishra Unit I 74
I
Minimum Viable Product
In the B2B world, the experts say that it’s not an MVP until you can’t sell it. The
picture below perfectly illustrates a proper MVP approach.
• The keyword here is “value”. Vague word “viable” means that the
product actually solves the user’s problem. And if after testing we find
out that it is not viable enough, we start it all over. That is why
“minimal” is important: the less investment we make in the beginning,
the easier it is to discard the failed product and build a new one.
When you need to solve a problem, you can grow your team’s creative capacity by
focusing on three core design thinking principles, or the 3 E’s: empathy, expansive
thinking, and experimentation.
Empathy
• It’s great to create an innovative product or service. It’s not so great to build one
that’s useless to people. That’s why your users should be your No. 1 focus. When
you can empathize with them and take inspiration from their needs, feelings, and
motivations, your team can create meaningful solutions to actual problems.
Expansive thinking
• Expansive thinking, also known as brainstorming, is all about creating multiple
ways to solve a problem or improve a situation. Instead of trying to think of one
perfect solution, think about reframing your problem or looking at it from all
conceivable angles to get several possible solutions. It’s OK that most of the ideas
your team comes up with won’t end up working.
• To begin your brainstorm, try challenging your team to come up with ideas that
aren’t just 10% better than the status quo but 10X better. Basically, thinking big —
like, really big — can give you radical new ideas.
Experimentation
• Once you have a list of ideas, you’ll need to start learning which ideas work and
which ones don’t — fast. This is where you begin experimentation or building
prototypes.
• In the prototyping phase, you’ll build an early-stage version of your idea and test it
out on a small group to see what actually works. Then, gather data to decide if it
makes the most sense to move your idea forward, kill it, or tweak it.
• Decide based on the project how you’d like to prototype. For example, you can test
a product internally before releasing it to the public, or release a new service in beta
to get feedback from people outside the company before a wide release.
Example: The debate was about the best color for the toolbar on the webpage. The
design team was fond of a particular shade of blue while the product manager was
advocating for a greener hue. Both parties had strong opinions about their choice. Who
gets to decide? Was the choice right? And does it really matter anyway?
• Decisions like this are often made based on diplomacy, authority, or opinion. The
debate recounted above is an often retold tale from Google, and the story has
endured because the team eventually tested 41 gradations of blue to see which users
preferred. Why?
• It’s about more than usability or user experience. Whether or not a design choice
leads to clicks can have an impact on a revenue stream. Companies like Google
know the importance of conducting experimentations like A/B testing to determine
the right approach with data—not an opinion or a guess.
• Whether the goal is to improve a landing page or a call-to-action button, A/B
testing is the best way to help UX teams and marketers make incremental changes
over time. A well-designed A/B test will help the team decide between two buttons,
two fonts,
• A/B tests tell us what’s not working, and what is successful, rather than merely
what has the potential for success. In short, the results from A/B tests can lead to
informed decisions based on data, and not just opinions.
• Once your prototype is approved, it goes to the final end-user, your customer.
Learning Launch is the tool wherein your test product is launched in the market for
a quick experiment.
• In contrast to a new product launch, this test is conducted solely for gathering data.
• As a design thinking tool, Learning Launch can be difficult to navigate through.
After all, liking your product does not mean one will buy it.
• Money is dear to all, and the real challenge lies in convincing the customer to part
with it willingly to buy your product. While one may say that’s the job of
advertising and marketing, the first step towards initiating the process of willful
buying happens through this stage.
• The most critical aspect of this tool is that unlike traditional analysis and case
studies that happen over a long period, this approach works for short periods.
• Since there is no perfect algorithm to achieve the perfect product, design thinking
uses this tool to learn along the way.
• For example, post-lockdown, the French government’s initiative to make the
country green, sustainable and inclusive translated into making 650-km bicycle
lanes throughout the territory. It was an urban planning project that worked along
the learning launch process to see what works best
• A learning launch is a carefully designed experiment or prototype designed to test
the key underlying value-generating assumptions of a potential new-growth
initiative.
• The purpose of a learning launch is to learn. If you learn valuable information, the
learning launch is a success, whether the particular idea is validated or not.
• There are lots of different ways of making a decision and choosing your approach
can be just as difficult as making the decision itself!
• Sometimes you have to take charge, and decide what to do on your own, but you
don't want to appear autocratic to your team (particularly in situations where you
need their input). At other times it's better to make a decision based on the group
consensus, but this can use up precious time and resources. So how do you decide
which approach is best?
• Every manager needs to be able to make good decisions. It can also help you to
determine the most effective means of reaching a decision.
• The framework poses seven "yes/no" questions, which you need to answer to find
the best decision-making process for your situation.
• As you answer each of the questions, you work your way through a decision tree
until you arrive at a code (A1, A2, C1, C2, or G2). This code identifies the best
decision-making process for you and your team.
• When people say “shift left” today, they may retain a bit of that waterfall thinking,
and see a static “beginning” for a new software project.
• By “shift right”, people mean that they aren’t going to just throw the feature over
the wall to ops when it deploys, they’re going to monitor, observe, analyze log data,
and “test in production.”
The shift left is a concept from the test strategy and the QA.
• Value Proposition Design allows you to map products and services against
customer gains and pains to create new value propositions or improve existing
ones.
• Value Proposition Design is a visual tool, a template that consists of two sides —
the value map (left-hand side below) and the customer profile (right-hand side).
Using this tool, you can identify how your products and services provide gains and
‘pain relief’ for your customers.
• Start on the right-hand side, by listing all the customer needs (including the
problems they're trying to solve and the duties they perform) under the
customer job(s). In customer pains, list the things that make it difficult for
your customer to get their ‘jobs’ done. Finally, in customer gains jot down
all the customer’s benefits and desires.
• Then on the left-hand side, list all the products and services on which your
value proposition is built. In the pain relievers section, write down all the
ways your products and services address the customer’s pains. And finally,
write in how your products/services create customer gains.
• Value Proposition Design can be used to help you create new value
propositions or improve existing ones. It’s a great way to nail down your
value proposition, see any gaps and ensure you’re delivering true value to
your customers.
• In terms of digital projects, Value Proposition Design can help deliver user-
centric projects, and helps you create value for your customers and
prospects.
https://www.coursera.org/lecture/uva-darden-design-thinking-innovation/the-ibm-story-iq0kE
https://www.coursera.org/lecture/uva-darden-design-thinking-
innovation/the-meyouhealth-story-part-i-what-is-W6tTs
https://www.coursera.org/lecture/uva-darden-design-thinking-
innovation/the-meyouhealth-story-part-ii-what-if-YSBV7
https://nptel.ac.in/courses/110106124
https://youtu.be/AamBSYPJlcA
https://www.coursera.org/learn/uva-darden-design-thinking-innovation
1. Define prototyping.
2. Explain the tools used in prototyping.
3. Discuss the importance of garnering user feedback for revisiting
Brainstormed ideas
4. Explain any two decision Making Tools and Approaches.
5. Briefly discuss SWOT analysis.
6. Explain three laws of design thinking.
7. Write short note on: (1) physical mockups and (2) storyboards
8. Explain the 10-100-1000gm & QBL law.
9. Discuss the rules of brainstorming.
10. Explain the 5 steps of design thinking.
https://www.independent.co.uk/news/world/americas/starbucks-barista-learns-sign-lang
uage-to-
talk-to-deaf-customer-a6890606.html
https://www.interaction-design.org/literature/topics/prototyping#:~:text=Prototyping
%20is%20an%20experimental%20process,can%20release%20the%20right
%20products.
https://www.uxmatters.com/mt/archives/2019/01/prototyping-user-experience.php
https://uxdesign.cc/prototyping-what-can-a-team-learn-5db78d7da912
https://qpsoftware.net/blog/pros-and-cons-prototyping-complex-projects
Thank You