Module-3_Design thinking in IT Industries.pdf

DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in
RLJIT
R
L
J
I
T
1
Module-3
Design Thinking in IT
Prof. Vijay Praveen P M
Assistant Professor
Department of ME

RLJIT
R
L
J
I
T
2
Contents to be covered
Design thinking in IT industries
Design thinking to Business Process Model
Design thinking for Agile Software Development
Scenario Based Prototyping
Virtual Collaboration

RLJIT
R
L
J
I
T
3
What is IT?
• Information technology (IT) is the use of any
computers, storage, networking and other physical
devices, infrastructure and processes to create,
process, store, secure and exchange all forms of
electronic data.

RLJIT
R
L
J
I
T
4
Design thinking in IT industry
Understanding IT industry with an example
XYZ InfoTech
promises to use technology to
solve all of your problems!
IT companies - They build software to make other businesses run smoothly!
Now if I know some technology and ask a programmer to solve problems by building specific pieces of software
IT companies build or maintain software so that businesses run
more smoothly. Anyone who builds or maintains software
belongs to the IT sector.

RLJIT
R
L
J
I
T
5
Software Development Cycle (SDLC)

RLJIT
R
L
J
I
T
6
• Stage 1: Planning and Requirement Analysis
• Requirement analysis is the most important and fundamental stage in
SDLC. It is performed by the senior members of the team with inputs
from the customer, the sales department, market surveys and domain
experts in the industry. This information is then used to plan the basic
project approach and to conduct product feasibility study in the
economical, operational and technical areas.
• Planning for the quality assurance requirements and identification of
the risks associated with the project is also done in the planning stage.
The outcome of the technical feasibility study is to define the various
technical approaches that can be followed to implement the project
successfully with minimum risks.

RLJIT
R
L
J
I
T
7
• Stage 2: Defining Requirements
• Once the requirement analysis is done the next step is to clearly define and document the
product requirements and get them approved from the customer or the market analysts.
This is done through an SRS (Software Requirement Specification) document which
consists of all the product requirements to be designed and developed during the project
life cycle
• Stage 3: Designing the Product Architecture
• SRS is the reference for product architects to come out with the best architecture for
the product to be developed. Based on the requirements specified in SRS, usually more
than one design approach for the product architecture is proposed and documented in a
DDS - Design Document Specification.
• This DDS is reviewed by all the important stakeholders and based on various
parameters as risk assessment, product robustness, design modularity, budget and
time constraints, the best design approach is selected for the product

RLJIT
R
L
J
I
T
8
• Stage 4: Building or Developing the Product
• In this stage of SDLC the actual development starts and the product is built. The
programming code is generated as per DDS during this stage. If the design is
performed in a detailed and organized manner, code generation can be accomplished
without much hassle.
• Developers must follow the coding guidelines defined by their organization and
programming tools like compilers, interpreters, debuggers, etc. are used to generate
the code. Different high level programming languages such as C, C++, Pascal, Java
and PHP are used for coding. The programming language is chosen with respect to
the type of software being developed.

RLJIT
R
L
J
I
T
9
• Stage 5: Testing the Product
• This stage is usually a subset of all the stages as in the modern SDLC
models, the testing activities are mostly involved in all the stages of
SDLC.
• Stage 6: Deployment in the Market and Maintenance
• Once the product is tested and ready to be deployed it is released
formally in the appropriate market. Sometimes product deployment
happens in stages as per the business strategy of that organization. The
product may first be released in a limited segment and tested in the real
business environment (UAT- User acceptance testing).

RLJIT
R
L
J
I
T
10
Software implement Process
1.Waterfall Models (earlier)
2.Agile Methodology (present)

RLJIT
R
L
J
I
T
11
Waterfall Model
• Waterfall approach was first SDLC
Model to be used widely in Software
Engineering to ensure success of the
project.
• In "The Waterfall" approach, the whole
process of software development is
divided into separate phases.
• In this Waterfall model, typically, the
outcome of one phase acts as the input
for the next phase sequentially.

RLJIT
R
L
J
I
T
12
• The sequential phases in Waterfall model are −
• Requirement Gathering and analysis − All possible requirements of the system to
be developed are captured in this phase and documented in a requirement
specification document.
• System Design − The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system
architecture.
• Implementation − With inputs from the system design, the system is first developed
in small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.
• Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system
is tested for any faults and failures.
• Deployment of system − Once the functional and non-functional testing is done;
the product is deployed in the customer environment or released into the market.
• Maintenance − There are some issues which come up in the client environment. To
fix those issues, patches are released. Also to enhance the product some better
versions are released. Maintenance is done to deliver these changes in the customer
environment.

RLJIT
R
L
J
I
T
13
Applications
• Requirements are very well documented, clear and
fixed.
• Product definition is stable.
• Technology is understood and is not dynamic.
• There are no ambiguous requirements.
• Ample resources with required expertise are
available to support the product.
• The project is short.

RLJIT
R
L
J
I
T
14
Advantages
• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model. Each phase has
specific deliverables and a review process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well
understood.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.

RLJIT
R
L
J
I
T
15
Dis advantages
• No working software is produced until late during the life
cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a
moderate to high risk of changing. So, risk and uncertainty
is high with this process model.
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.

RLJIT
R
L
J
I
T
16
Agile Methodology
• Agile software development refers to a group of software
development methodologies based on iterative
development, where requirements and solutions evolve
through collaboration between self-organizing cross-
functional teams.
• Agile methods or Agile processes generally promote a
disciplined project management process that encourages
frequent inspection and adaptation, a leadership
philosophy that encourages teamwork, self-organization
and accountability, a set of engineering best practices
intended to allow for rapid delivery of high-quality
software, and a business approach that aligns
development with customer needs and company goals.

RLJIT
R
L
J
I
T
17
Project
management
A sprint is a short, time-boxed period when a scrum team works to
complete a set amount of work.

RLJIT
R
L
J
I
T
18

RLJIT
R
L
J
I
T
19

RLJIT
R
L
J
I
T
20
Agile Manifesto.
• Agile development refers to any development process that is
aligned with the concepts of the Agile Manifesto.
(self-organizing team is one that does not depend on or wait for a manager to assign work. Instead,
these teams find their own work and manage the associated responsibilities and timelines. .).

RLJIT
R
L
J
I
T
21

RLJIT
R
L
J
I
T
22

RLJIT
R
L
J
I
T
23
• Sustainable development means constant
production of software features during a long
lasting period. This is done without loss of
concentration within the team or a rising amount of
errors as a result of fatigue or frustration. Software
development is like running a marathon and not
100 meters sprint. You have to keep up to speed
but not run so fast that you exhaust yourself or
your team members.

RLJIT
R
L
J
I
T
24
Agile Model V/s WaterFall Model
•
•
•
•
•
•
•
•

RLJIT
R
L
J
I
T
25
•Small projects can be implemented very
quickly. For large projects, it is difficult to
estimate the development time.
•All sorts of project can be estimated and
completed.
•Error can be fixed in the middle of the
project.
•Only at the end, the whole product is tested.
If the requirement error is found or any
changes have to be made, the project has to
start from the beginning
•Development process is iterative, and the
project is executed in short (2-4) weeks
iterations. Planning is very less.
•The development process is phased, and the
phase is much bigger than iteration. Every
phase ends with the detailed description of
the next phase.
•Documentation attends less priority than
software development
•Documentation is a top priority and can even
use for training staff and upgrade the
software with another team
•Every iteration has its own testing phase. It
allows implementing regression testing every
time new functions or logic are released.
•Only after the development phase, the
testing phase is executed because separate
parts are not fully functional.

RLJIT
R
L
J
I
T
26
•In agile testing when an iteration end,
shippable features of the product is
delivered to the customer. New
features are usable right after
shipment. It is useful when you have
good contact with customers.
•All features developed are delivered
at once after the long implementation
phase.
•Testers and developers work together
•Testers work separately from
developers
•At the end of every sprint, user
acceptance is performed
•User acceptance is performed at the
end of the project.
•It requires close communication with
developers and together analyze
requirements and planning
•Developer does not involve in
requirement and planning process.
Usually, time delays between tests and
coding

RLJIT
R
L
J
I
T
27
Advantages of Agile Methodology :
1. In Agile methodology the delivery of software is unremitting(constantly).
2. The customers are satisfied because after every Sprint working feature of
the software is delivered to them.
3. Customers can have a look of the working feature which fulfilled their
expectations.
4. If the customers has any feedback or any change in the feature then it can
be accommodated in the current release of the product.
5. In Agile methodology the daily interactions are required between the
business people and the developers.
6. In this methodology attention is paid to the good design of the product.
7. Changes in the requirements are accepted even in the later stages of the
development.
8. An Agile/Scrum approach can improve organizational synergy by breaking
down organizational barriers and developing a spirit of trust and
partnership around organizational goals.

RLJIT
R
L
J
I
T
28
Dis Advantages
1.In Agile methodology the documentation is less.
2.Sometimes in Agile methodology the requirement is not
very clear hence it’s difficult to predict the expected
result.
3.Because of the ever-evolving features, there is always a
risk of the ever-lasting project.
4.For complex projects, the resource requirement and effort
are difficult to estimate

RLJIT
R
L
J
I
T
29
Design thinking and Agile methodology
30-35% or even 50% of the IT projects fail according to research
• Agile improves success rate by almost double by promoting better
collaboration and communication
• But Agile only provides way to solve problems and how can 1 decide which is
the right problem to solve
• This is where Design thinking plays a vital role
• Combining both is not an easy task and requires culture shift (new way of
thinking and doing) and one has to get accustomed to this cultural shift
• This combination value people over processes
Organizations have to allocate right people for the projects and they should
ensure cultural compatibility between teams and the way Design thinking and
Agile methodology work

RLJIT
R
L
J
I
T
30
Best practices for combining Design thinking and Agile methodology
• Invest in user research
• A clearly defined problem statement
• Build a productive team culture
• Optimal use of Design thinking

RLJIT
R
L
J
I
T
31
Advantages of Agile Development Method
used in software development in IT
Industry
Solutions are Prototyped and Results are verified
Best solutions are accepted
Before approval itself the solutions are experienced by the client
To improve user experience short iterations are possible
Small cross-functional teams
Incremental delivery is possible
Fast feedback helps the designers and developers
Continuous improvement is possible

RLJIT
R
L
J
I
T
32
Design thinking in Business Process Modelling
What is Business Process Model?
Business process management (BPM) is a way of breaking down
business processes into their most basic elements: the tasks and
activities a business carries out. BPM shows, clearly and
transparently, how a product or service transforms as it moves
through an organization's process sequence, often in near real-time.
The BPM is represented with Graphical Diagram that represent the
process Known as Business Process Modeling Notation (BPMN)

RLJIT
R
L
J
I
T
33
• Business Process Modeling Notation (BPMN) is a flow
chart method that models the steps of a planned business
process from end to end. A key to Business Process
Management, it visually depicts a detailed sequence of
business activities and information flows needed to
complete a process.

RLJIT
R
L
J
I
T
34
The BPMN Elements
• Events: A trigger that starts, modifies or completes a process
• Activity :A particular activity or task performed by a person or
system.
• Gateway : Decision point that can adjust the path based on
conditions or events

RLJIT
R
L
J
I
T
35
• Sequence flow
• Shows the order of activities to be performed.
• Message flow
• Depicts messages that flow across “pools,” or organization boundaries
such as departments.
• Association
• Shown with a dotted line, it associates text to an event, activity or
gateway.

RLJIT
R
L
J
I
T
36

RLJIT
R
L
J
I
T
37
Why Use Business Process Modeling:
Top 5 Benefits
1. Improving Efficiency – The main function of BP modeling is to improve the way the processes
are done. As a given, you’ll find different ways to improve the way the process works, which
leads to higher efficiency, productivity, output, and finally, profits.
2. Enforce Best-Practices & Standardization – If you’re running a big organization, there’s a
good chance that different teams do the same process differently. Creating the best-practice
design ensures that everyone knows how to do the process.
3. Process Agility – If BP analysis is a norm within an organization, they will eventually develop
a culture of innovation and change. By being able to constantly tweak business operations,
you’ll be able to evolve in the face of technological change.
4. Transparency – Everyone within your organization will be, more or less, aware of how your
processes work: what’s the goal, how it operates, etc. This leads to accountability; who owns
what process becomes transparent.
5. Beat the Competition – As a result of all the other benefits we’ve mentioned, you’ll be able to
beat and outlast your competition in the long-run.

RLJIT
R
L
J
I
T
38
Advantages of BPM
• Align operations with business strategy
• Improves process communication
• Increase control and consistency
• Improve operational efficiencies
• Gain competitive advantage

RLJIT
R
L
J
I
T
39
By revealing the way things are done at an organization, and comparing that with
the way things should be done, BPM highlights the dependencies and relationships
between people, process, and technology—and where those elements are ripe for
improvement.
Design thinking is also focused on improvement, but takes the end-user or
customer experience as a starting point. Fundamentally, design thinking uses
empathy to understand the way people feel about using a service or product,
including where their frustrations lie, then builds on that knowledge to create
improvements, with the ultimate goal of making customers’ lives and experiences
better and more fulfilling.

RLJIT
R
L
J
I
T
40
Benefits of Design Thinking and BPM
Working in tandem, design thinking and BPM unlock a range of powerful (and potentially
lucrative) benefits, including:
•Competitive advantage, gained through a willingness to innovate, then ‘double-down’ on ideas
that work,
•Pooling collective ease and enhancing collaboration, through building multidisciplinary teams
to focus on a single problem
•Harnessing natural empathy, leading to a better understanding of the needs and challenges of
customers
•Generating more revenue by ensuring a deeper level of customer satisfaction

RLJIT
R
L
J
I
T
41
Agile in Virtual Collaboration
Agile methodology can accept changes anytime compared to that of a waterfall method, and
hence collaboration between collocated teams eases out the agile processes. Besides coordination;
interaction, development, planning, review, retrospective sessions etc. also immensely reduce time
and effort.
Working remote or distributed is considered being competitive and is considered a fit operating
model. Some companies also provide it as a choice to its employees. Businesses want to
leverage talent round the clock, use the best talent which may not be locally available, cheap
labor by outsourcing to low cost countries, higher productivity and numerous strategic reasons.
With growing needs of working remote, it is intolerable to voice that agile methods will not work
by distributed teams. Although few trials will arise, with the help of tools and techniques moving
to a remote working environment is possible.

RLJIT
R
L
J
I
T
42
Scenario based prototyping
• Design thinking is at its best if tangible prototypes can be used to
envision new products and services. However, for complex
software systems with multiple users usually such tangible
prototypes are not feasible.
• To overcome this problem, scenario-based prototyping approach
can be proposed for designing complex software systems that is
based on models, both structural and behavioral models.
• The approach will support the stepwise and interactive
enrichment of the prototype model, the traceability between the
artefacts collected during earlier design phases and the scenarios.

RLJIT
R
L
J
I
T
43
Scenarios describe a sequence of events, illustrating the activities of one
or more people in a real-world setting. The goals are to be realistic,
detailed..

RLJIT
R
L
J
I
T
44
Revisions are must
Instead of giving the original app developed, photos
(Photoshop, illustrator or any other app) with real
scenarios (push button enabled or directing to the test
case) may be done.
Now UI experts and User experience experts come to
play and finally after many revisions the app is
presented in its original form to the customer. (Even
rolling out of Beta forms are in practice)
• Scenarios make us think about the design in detail and notice potential
problems before they happen.

RLJIT
R
L
J
I
T
45
MCQ
• Waterfall model is a _________ model.
• predictive development
• adaptive development
• progressive development
• All of these

RLJIT
R
L
J
I
T
46
• A model that is the demo implementation of the system.
• a) waterfall
• b) prototype
• c) incremental
• d) agile

RLJIT
R
L
J
I
T
47
• A stage in which individual components are integrated
and ensured that they are error-free to meet customer
requirements.
• a) Coding
• b) Testing
• c) Design
• d) Implementation

RLJIT
R
L
J
I
T
48
• A step in waterfall model that involves a meeting with the
customer to understand the requirements.
• a) Requirement Gathering
• b) SRS
• c) Implementation
• d) Customer review

RLJIT
R
L
J
I
T
49
• Methodology in which project management processes
were step-by step.
• a) Incremental
• b) Waterfall
• c) Spiral
• d) Prototyping

RLJIT
R
L
J
I
T
50
• An individual who plans and directs the work.
• a) Stakeholder
• b) Project manager
• c) Team leader
• d) Programmer

RLJIT
R
L
J
I
T
51
• Select the option that suits the Manifesto for Agile
Software Development:
• A. Working software
• B. Individuals and interactions
• C. Customer collaboration
• D. All of the above

RLJIT
R
L
J
I
T
52
• Agile Software Development is based on:
• A. Linear Development
• B. Incremental Development
• C. Both Incremental and Iterative Development
• D. Iterative Development

RLJIT
R
L
J
I
T
53
• In agile development it is more important to build
software that meets the customers’ needs today than
worry about features that might be needed in the future.
• A. True
• B. False

RLJIT
R
L
J
I
T
54
• Which of the following is delivered at the end of the
Sprint?
• A. An architectural design of the solution
• B. An increment of Done software
• C. A document containing test cases for the current sprint
• D. Wireframes designs for User Interface

RLJIT
R
L
J
I
T
55
• How is Agile planning different from the traditional
approach to planning?
• A. Agile planning places emphasis on the plan
• B. Agile planning is non iterative
• C. Agile planning places emphasis on planning and is
iterative
• D. Agile planning is done only once

RLJIT
R
L
J
I
T
56
• In agile development it is more important to build
software that meets the customers’ needs today than
worry about features that might be needed in the future.
• a) True
• b) False

RLJIT
R
L
J
I
T
57
• How is Agile planning different from the traditional
approach to planning?
• A. Agile planning is done only once
• B. Agile planning is non iterative
• C. Agile planning places emphasis on the plan
• D. Agile planning places emphasis on planning and is
iterative

RLJIT
R
L
J
I
T
58
• What is BPMN stands for?
• Business Process Modelling and Notations
• Business Product Modelling and Notations
• Business Process Manufacturing and Notations

RLJIT
R
L
J
I
T
59
• 1.Which best describes Business Process Model and
Notation (BPMN)?
• An emerging business process model introduced in Visio
2013
• An industry specific representation of a business process
• A standard for graphical representation of business
processes

RLJIT
R
L
J
I
T
60
• Which of the following best describes a business model?
• a) Typically a graphical depiction of the essential business
process information.
• b)A sequence of business activities.
• c)An evaluation of potential business process
improvements.
• d)None of the above.

RLJIT
R
L
J
I
T
61
• Business models provide value in all of the following areas
except which one?
• a)Employee performance appraisal
• b)Managing complexity
• c)Specifying systems requirements
• d)Eliciting requirements for new systems
•

RLJIT
R
L
J
I
T
62
• Which of the following best describes the purpose of an
activity model?
• a)Describes the sequence of workflow in a business
process.
• b)Creates a blueprint to support the collection of process
information.
• c)Depicts data structures.
• d)None of the above

RLJIT
R
L
J
I
T
63
• Which of the following best describes the purpose of an
event in a BPMN activity diagram?
• a) Shows where the work takes place.
• b) Describes the sequence of workflow.
• c) Affects the flow of the business process.
• d) Controls branching and merging.

RLJIT
R
L
J
I
T
64
• Which of the following symbols depicts an intermediate
event?
• a) An arrow
• b) A circle with a double with a double line and filled
inside
• c) A rectangle
• d) A circle with a wide single line perimeter

RLJIT
R
L
J
I
T
65
• Which of the following symbols depicts an activity?
• a) An arrow
• b) A circle with a double with a double line and filled
inside
• c) A rectangle
• d) A circle with a wide single line perimeter

RLJIT
R
L
J
I
T
66
Which of the following symbols depicts an Decision making?
a) An arrow
b) A circle with a double with a double line and filled inside
c) A rectangle
d) An Rhombus

RLJIT
R
L
J
I
T
67
• 2) Design Thinking combines
• Creative and critical thinking
• Speaking and reading
• Neither of the above
3)The only important thing about design is how it relates to
• Product
• People
• Thinking
• money

RLJIT
R
L
J
I
T
68
• People-centered design is not about how a pr0duct works on the inside
or looks on the outside, rather it is about
• How the product functions and its measurements
• How the product behaves and is use in the real world
• Both of the above
• None of the above
• A Designer needs to consider human when designing a product
• History
• Names
• Eror
• None of the above

RLJIT
R
L
J
I
T
69
• Design Thinking requires a designer to
• Design immediately with a prejudice
• Think out of the box
• Dress with etiquette
• Have good communication skills

RLJIT
R
L
J
I
T
70
• Research tor design involves
• Research of people
• Smart business development
• A thesis about design
• Opportunities for reducing prices
• Research of existing body of knowledge
• Technology enhancements

RLJIT
R
L
J
I
T
71
• Who is the recommended group that you should test out
the prototypes with?
• target customers
• People in your team
• Professional designers
• Experts

RLJIT
R
L
J
I
T
72
• Select the appropriate methods from below that are used
in people-centered design
• Problem discovery
• Researching the user and then analyzing the data
• Defining and finalizing the solutions during the initial
phase
• Thinking about the flaws of the generated ideas during
the initial phase

RLJIT
R
L
J
I
T
73
• What should not be done during brainstorming?
• Evaluate in the beginning
• Force participation
• Ask judging question
• All of the above
• Which type of prototype demonstrate the look and feel of the product
• Proof of concept
• Industrial design prototypes
• Alpha prototypes
• Beta prototypes

RLJIT
R
L
J
I
T
74
Thank You

Module-3_Design thinking in IT Industries.pdf

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Module-3_Design thinking in IT Industries.pdf

Similar to Module-3_Design thinking in IT Industries.pdf (20)

Recently uploaded

Recently uploaded (20)

Module-3_Design thinking in IT Industries.pdf