Module 3designthinkinginitindustries 220331065107

R
Module-3
L
Design Thinking in IT J
Prof. Vijay Praveen P M I

Assistant Professor
Department of ME T
RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

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

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

Design thinking in IT industry
R
Understanding IT industry with an example
I
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 T
IT companies build or maintain software so that businesses run
more smoothly. Anyone who builds or maintains software
belongs to the IT sector. 4

R
Software Development Cycle (SDLC)
L

R
• Stage 1: Planning and Requirement Analysis L

• 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 J
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. I
• Planning for the quality assurance requirements and identification of
the risks associated with the project is also done in the planning stage. T
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. 6

R
• 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. L
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 J
• 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 I
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 T
parameters as risk assessment, product robustness, design modularity, budget and
time constraints, the best design approach is selected for the product
7

R
• Stage 4: Building or Developing the Product L

• 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 J
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 I
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. T

R
• Stage 5: Testing the Product
• This stage is usually a subset of all the stages as in the modern SDLC L
models, the testing activities are mostly involved in all the stages of
SDLC. J
• 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
I
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 T
business environment (UAT- User acceptance testing).

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

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

• The sequential phases in Waterfall model are −
R
• 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. L
• 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. J
• 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 I
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. T
• 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
12
environment.
R
Applications
L
• Requirements are very well documented, clear and
fixed. J
• Product definition is stable.
• Technology is understood and is not dynamic. I
• There are no ambiguous requirements.
• Ample resources with required expertise are T
available to support the product.
• The project is short. 13

Advantages R
• Simple and easy to understand and use L

• 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. J
• Works well for smaller projects where requirements are very well
understood.
• Clearly defined stages. I
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented. T
14

R
Dis advantages
L
• No working software is produced until late during the life
cycle.
• High amounts of risk and uncertainty. J
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects. I
• 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. T
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.
15

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

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

R
18

R
19

Agile Manifesto. R
• Agile development refers to any development process that is
aligned with the concepts of the Agile Manifesto.
L
J
(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. .).
I
20

R
21

R
22

R
L
• Sustainable development means constant
production of software features during a long J
lasting period. This is done without loss of
concentration within the team or a rising amount of I
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 T
but not run so fast that you exhaust yourself or
your team members. 23

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

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

R
•In agile testing when an iteration end,
shippable features of the product is
delivered to the customer. New
•All features developed are delivered L
at once after the long implementation
features are usable right after
phase.
shipment. It is useful when you have
good contact with customers. J
•Testers work separately from
•Testers and developers work together
developers I
•At the end of every sprint, user •User acceptance is performed at the
acceptance is performed end of the project.
•Developer does not involve in
T
•It requires close communication with
requirement and planning process.
developers and together analyze
Usually, time delays between tests and
requirements and planning 26
coding
Advantages of Agile Methodology : R
1. In Agile methodology the delivery of software is unremitting(constantly).
2. The customers are satisfied because after every Sprint working feature of L
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
J
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. I
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. T
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. 27

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

R
Design thinking and Agile methodology
30-35% or even 50% of the IT projects fail according to research L

• 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 J
the right problem to solve
• This is where Design thinking plays a vital role I
• 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
T
Organizations have to allocate right people for the projects and they should
ensure cultural compatibility between teams and the way Design thinking and 29
Agile methodology work
R
Best practices for combining Design thinking and Agile methodology
L
• Invest in user research
J
• A clearly defined problem statement
• Build a productive team culture I
• Optimal use of Design thinking
T
30

R
Advantages of Agile Development Method
used in software development in IT
Industry
L
Solutions are Prototyped and Results are verified
Best solutions are accepted J

Before approval itself the solutions are experienced by the client
To improve user experience short iterations are possible I

Small cross-functional teams
Incremental delivery is possible T

Fast feedback helps the designers and developers
Continuous improvement is possible

31

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

process Known as Business Process Modeling Notation (BPMN)
32

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

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

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

R
36

Why Use Business Process Modeling: R
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 L
leads to higher efficiency, productivity, output, and finally, profits.
2. Enforce Best-Practices & Standardization – If you’re running a big organization, there’s a J

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,
I
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 T
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.
37

R
Advantages of BPM L
• Align operations with business strategy J

• Improves process communication
• Increase control and consistency I
• Improve operational efficiencies
• Gain competitive advantage
T
38

R
By revealing the way things are done at an organization, and comparing that with
L
the way things should be done, BPM highlights the dependencies and relationships
between people, process, and technology—and where those elements are ripe for J
improvement.
Design thinking is also focused on improvement, but takes the end-user orI
customer experience as a starting point. Fundamentally, design thinking uses
empathy to understand the way people feel about using a service or product,T
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. 39

R
Benefits of Design Thinking and BPM L
Working in tandem, design thinking and BPM unlock a range of powerful (and potentially
lucrative) benefits, including: J
•Competitive advantage, gained through a willingness to innovate, then ‘double-down’ on ideas
that work, I
•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 ofT
customers
•Generating more revenue by ensuring a deeper level of customer satisfaction
40

R
Agile in Virtual Collaboration
Agile methodology can accept changes anytime compared to that of a waterfall method, and L
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. J
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 toI
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.
T
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.
41

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

R
Scenario based prototyping L

Revisions are must
Instead of giving the original app developed, photos

(Photoshop, illustrator or any other app) with real
J
scenarios (push button enabled or directing to the test
case) may be done.
I
Now UI experts and User experience experts come to
play and finally after many revisions the app is
T
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 44
problems before they happen.
R
MCQ
L
• Waterfall model is a _________ model.
• predictive development J
• adaptive development
• progressive development I
• All of these
T
45

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

R
L
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
J
c) A rectangle
d) An Rhombus I
66

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

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

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

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

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

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

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

R
J
Thank You
I
74

Module 3designthinkinginitindustries 220331065107

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Module 3designthinkinginitindustries 220331065107

Uploaded by

Copyright:

Available Formats

R

Prof. Vijay Praveen P M I

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

• Stage 1: Planning and Requirement Analysis L

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

• Stage 4: Building or Developing the Product L

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

1.Waterfall Models (earlier) J

2.Agile Methodology (present) I

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

• Simple and easy to understand and use L

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

30-35% or even 50% of the IT projects fail according to research L

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

Best solutions are accepted J

To improve user experience short iterations are possible I

Incremental delivery is possible T

Continuous improvement is possible

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

The BPM is represented with Graphical Diagram that represent the T

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

2. Enforce Best-Practices & Standardization – If you’re running a big organization, there’s a J

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

• Align operations with business strategy J

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

Scenario based prototyping L

Instead of giving the original app developed, photos

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in

RLJIT DEPARTMENT OF MECHANICAL ENGINEERING www.rljit.in