Scribd
Upload
215 views

Design Thinking in Information Technology

This document discusses design thinking in information technology. It provides an overview of the traditional software development life cycle including requirements, analysis, design, coding, testing, and maintenance. It then discusses how design thinking can be applied to agile software development through short iterations, prototyping solutions, gaining fast feedback, and allowing for continuous improvement. The key principles of agile development including values from the Agile Manifesto are also summarized.

Uploaded by

srinivas gangishetti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
215 views

Design Thinking in Information Technology

This document discusses design thinking in information technology. It provides an overview of the traditional software development life cycle including requirements, analysis, design, coding, testing, and maintenance. It then discusses how design thinking can be applied to agile software development through short iterations, prototyping solutions, gaining fast feedback, and allowing for continuous improvement. The key principles of agile development including values from the Agile Manifesto are also summarized.

Uploaded by

srinivas gangishetti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Design Thinking

in
Information Technology

1
UNIT – IV
Design Thinking in Information Technology
TOPICS to be covered :
1. Introduction
2. Design Thinking for agile software development

3. Design Thinking in Business process model

4. Virtual collaboration
5. Multi user and Multi account interaction

6. Need for communication

7. TILES toolkit

8. Cloud implementation
1.Introduction
Software Development Process in IT Industry
1.Requirements

Application requirements or Software specification 

Scope definition of the entire project

Planning for the quality assurance requirements

Definition of anticipated issues, opportunities

Recognition of the risks involved

Timeline definition
2.Analysis
• Analysis of the project’s Feasibility study

‍
There are main five types of feasibilities checks:
• Economic

• Legal

• Operation

• Technical

• Schedule
• 3.Design
There are two types of design documents that are developed:

High-Level Design (HLD)

•Brief description of each module and its functionality

•Dependencies between modules

•Database tables & their main elements 

•Architecture diagrams

•Technology details

Low-Level Design(LLD)

•Functional modules logic

•Detailed database tables

•Complete interface detail

•Complete modules input and outputs


4.Coding

• The next phase is coding itself - the longest phase of the


software development life cycle. 

Peculiarities of the phase:

• Developers should follow some predefined coding


guidelines.

• The whole development is divided into tasks for specific


modules development.
5.Testing
The process is the following:

• QA team finds some issues;

• QA team sends them to the development team;

• Dev Team fixes the issues;

• QA team rechecks the functionality.

Once the software is developed and fully tested, the final deployments
process is launched. 

QA team checks the software on the production environment.


6.Maintanance

• After the release, the application continues its


cycle following 3 possible ways:

• Bug fixing

• Software upgrade

• Enhancement with new features


• Advantages of using design thinking in IT industry

• The solutions are prototyped.


• The results are verified.
• The best solutions are accepted.
• The solutions are experienced by the client before approval.
• Short iterations are possible to improve the user experience.
• Small cross-functional teams.
• Incremental delivery is possible.
• Fast feedback helps the designers and developers.
• Continuous improvement is possible.
Agile Software Development
Agile means to move quickly & easily
Agile methodology provides us with a framework where
continuous improvements happen at different stages of
the software development life cycle
Agile methodology sprung from the buzz word “continuous
delivery,” which was only a dream in traditional models of
software development like Waterfall, V- shape model, etc.
Increment Vs Iterative Vs Agile
• Each increment in the incremental approach builds a complete feature
of the software, while in iterative, it builds small portions of all the
features.
• An agile approach combines the incremental and iterative approach
by building a small portion of each feature, one by one, and then
both gradually adding features and increasing their completeness.
Agile Manifesto and Principles

Agile Manifesto or Agile Values

Individuals and Interactions Over process and tools

Working Software Over Comprehensive documentation

Customer Collaboration Over Contract Negotiation

Responding to Change Over Following a plan


Agile Manifesto 12 Principles
Agile Manifesto 12 Principles
Agile Manifesto 12 Principles
Agile Manifesto 12 Principles
Agile Manifesto 12 Principles
• Steps in Agile Development Process
Advantages of Agile developments

• Shorter development cycles


• Wider market windows
• Early customer feedback
• Continuous improvement
• Enhanced Quality 
• Better Customer Experience 
• Transparency
• Early & Predictable Delivery 
• Ease of doing transactions 
• Continuous Engagement 

You might also like