DEPROJECT
DEPROJECT
Chandkheda, Ahmedabad
A report on
Noise Detector with Automatic Recording System
Under subject of DESIGN ENGINEERING
B.E. Semester – 3
E.C.E. Branch
Submitted by:
Name of Student – Enrollment no.
1. Dabhi Pradipbhai Mukeshbhai :230280111017
2. Dabhi Pradipkumar Maheshbhai :230280111018
3. Gohil Mitrajshinh Virbhadarasinh :230280111040
4. Khodifad Pradip Parshotambhai :230280111059
Date:
Submitted to :
L.D College of engineering
Ahmedabad-380015
Affiliated to:
Gujarat technological university
ACKNOWLEDGEMENTS
Sr.
Contents
No. Page no.
1 Introduction 1
2 Empathy Mapping 10
3 Ideation Canvas 15
3.1 People 15
3.2 Activity 15
3.3 Situation/context/location 16
3.4 Props/possible solution 16
4.1 Purpose 17
4.2 People 17
4.5 Components 18
4.7 Retain/Redesign 19
5 Prototype 20
6 Conclusion 23
CHAPTER 1 Introduction
This paper will look at how the discipline of design has evolved in the
last fifty years and how new articulations of its methodologies and
techniques can be applied to the achievement of social change. This
paper will conduct a thorough analysis of the concepts of design
thinking in order to unveil the historic evolution of this approach and
enable this research to forecast future applications and realize
recommendations to improve and foster its implementation. This
investigation will be backed up with interviews with experts in the
industry to engage in a dynamic debate that will define the reasons
and Casualties of why design methodologies are such a potentially
compelling fit to meet the requirements of the social sectors.
Nowadays in Design Framework there is not a unique definition that
analyzes the origins of design thinking and the shift in description of
design. The coexistence of several form an ‘object-centered’
discipline into the study valid and valuable interpretations of its
nature, as of the principles and practices behind the design Fraser
(2006) puts it, only shows how diverse and process leveraged into a
problem-solving activity.
Sometimes contradictory the perception of the design activity is. In
this part we
will Design from objects to an approach Traditionally Design has
dealt with objects, thus the “immersed in this material culture, and
draw design theory has revolved around them for most upon it as their
primary source of their think- of its existence despite the intentions of
theorizing. Designers have the ability both to ‘read’ to shift away from
them for the last twenty years. And ‘write’ in this culture; they
understand Flosser (1999) for example, States from which design
begins, what messages objects communicate before any activity or
physical form take place. They can create new objects which embody
takes the Search to discover opportunities beyond new messages”
(Cross 2006). The materialistic level emphasizing the etymological
origin of the words as the basis of any discipline.
Random Selection
It is quick selection will not take time.
When to do Random Selection?
Project is Less Thoughtful
For short term discussion
Methods to do Random(arbitrary) selection
Write name in chit and through in bowl then pick up the chit
Same letter for starting of their name
By enrolment number
Cards or number allocation
What happens when students select team?
One student just pretends to do work but does not. Other one
disappears day one itself and comes on final day.
Qualities to be searched
Project Organizer (who manages the entire project)
An analyzer (who can do analysis of data)
Stream wise technical Skill person (Mechanical, Electronics, Software
and etc.)
Concept Ideate (Person who visualizes the Idea a solution for the
problem)
Requirement of TEAM Formation
Teach each other
Practice communication, teamwork, project management skills
Work on higher-order assignments
Expand network & meet new people Learn readings better
(discussion groups)
Simulate real-life work environment
Why to keep a log book?
An engineering logbook is a personal/professional reference about
project learning
and results.
These records may become necessary to provide a history of the
design if there is a turnover in staff, if patent applications are made, or
in the case of legal action where the demonstration of professional
practices is necessary.
Monitor and control where you invest your time,
Learn and apply the best practices for your profession
Regularly take time to learn from successes and failures
Aeiou Summary Canvas for Noise Detector with Automatic Recording System
Environment:
• Physical: Indoor settings like offices, libraries, classrooms.
• Social: Workplaces, educational institutions.
• Cultural: Noise pollution concerns, awareness of environmental issues.
Interactions:
• User-device: Device detects noise levels, alerts user, records audio.
• Device-environment: Device monitors noise levels in the environment.
• User-environment: User becomes aware of noise pollution and can take
action.
Objects:
• Noise detector: Device that measures noise levels.
• Microphone: Records audio for analysis.
• Speaker: Plays alerts and recordings.
• Display: Shows noise levels and alerts.
• Storage: Stores recorded audio files.
Activities:
• Noise detection: Device continuously monitors noise levels.
• Alerting: Device triggers alerts when noise levels exceed threshold.
• Recording: Device records audio when alerts are triggered.
• Analysis: User can analyze recorded audio to identify noise sources.
Users:
• Office workers: Concerned about productivity and noise distractions.
• Students: Need a quiet environment for studying and learning.
• Librarians: Want to maintain a peaceful atmosphere for patrons.
• Environmentalists: Interested in reducing noise pollution.
Mind Mapping:
User:
• Office workers
• Librarians
• Teachers
• Students
• Facility managers
• Noise regulation authorities
Stakeholders
Internal:
• Development team (engineers, designers)
• Marketing and sales teams
External:
• End users (office staff, students)
• Investors
• Community organizations
Activities
• Installation: Setting up the noise detector in the environment.
• Monitoring: Continuously tracking noise levels.
• Alerting: Notifying users when noise exceeds a predefined level.
• Recording: Capturing audio when noise alerts are triggered.
• Analysis: Reviewing data and recordings for trends and actionable
insights.
• Feedback: Collecting user feedback for enhancements.
Happy Scenario:
• Setup: User easily installs the noise detector in a shared workspace.
• Detection: The device promptly alerts users when noise levels rise during
meetings.
• Recording: Automatic recordings provide clear evidence of disturbances.
• Resolution: Users present recordings to management, leading to effective
noise management solutions, improving overall productivity.
Sad Scenario:
• Setup: User struggles with complicated installation or settings
configuration.
• Detection: The device issues frequent false alarms during normal
activities, causing annoyance.
• Recording: Users find the recordings lack context or are unclear, leading
to frustration.
• Resolution: Users feel disheartened, questioning the system's value and
considering its removal.
CHAPTER 3 IDEATION CANVAS
People
• Office workersLibrarians
• Teachers
• Students
• Facility managers
• IT support staff
Activities
• Monitoring ambient noise levels
• Receiving and responding to alerts
• Reviewing recorded noise events
• Implementing sound management strategies
• Conducting training on device usage
• Analyzing noise data for trends
Situation/Context/Location
• Offices:
• Libraries:
• Classrooms:
• Public spaces:
• Events:
Props/possible/Solutins
• Hardware
• Software
• Polices
• Dising Features
CHAPTER 4 :PRODUCT DEVELOPMENT CANVAS
Purpose:
• To reduce noise pollution in environments like offices, libraries, and
classrooms, enhancing productivity and comfort.
Product Experience:
• Users receive timely alerts about excessive noise, can review recorded
incidents, and feel empowered to manage their acoustic environment
effectively.
Product Functions:
• Detects sound levels
• Sends real-time alerts
• Automatically records noise events
• Allows users to review recordings and analytics
Customer:
• Office workers, librarians, educators, students, and facility managers
seeking to maintain a quiet and productive atmosphere.
Revalidation:
• Collect user feedback on system performance, usability, and effectiveness
in reducing noise- related issues. Adapt the product based on user needs
and experiences.
Product Features:
• Real-time noise level monitoring
• Automated alerts (e.g., via app or SMS)
• Recording capability with timestamp
• User-friendly interface for accessing data
• People:
• End users (office workers, educators)
• Stakeholders (facility managers, IT support)
• Development team (engineers, designers)
Components:
• Microphone for sound detection
• Arduino board for processing
• loT module for connectivity (Wi- Fi/Bluetooth)
• Storage for recorded audio
• User interface (mobile app or web dashboard)
Reject:
• Features that complicate the user experience (e.g., overly complex
settings or configurations).
Redesign:
• Enhance alert systems based on feedback to minimize false alerts and
improve accuracy in noise detection.
CHAPTER 5:Prototype
This Noise Detector System can be used in library, office and classroom
environments to identify noisy people so that necessary action can be taken
against them.
To build this device, we need to first collect a few components.
Components Required
• Vibration motor/ Buzzer
• Bluetooth HC 05
• Sound sensor module
• Wires
• Arduino Nano
Coding
First, we will initialise the different variables in our code to store values and pin
numbers and then include the Software Serial library. After this, we will set the
Pin modes for the Arduino pins and the baud rate for Bluetooth. Following this,
we will set a loop function where we will create an ‘if condition’ that checks the
incoming number from Bluetooth. This number is used for setting the threshold
level for noise sensor. Then the loop function jumps to other function (i.e.
sensor) that collects the average sensor data (Refer Fig
Fig 2. Arduino code
for reading strings from Bluetooth.
In sensor function, we will create a ‘for loop’ that collects the sensor data until
the for loop ends (up to 160 times) and calculates the average of the collected
data. After that an ‘if condition’ checks the average, if the average value is
greater that the threshold value then it sends the value to an app that we are
going to make in next part (Refer Fig 3).
Fig 3.
Arduino code calculating noise level
App Making
We are going to use the MIT app inventor for creating our app. In the first part,
we need to create a layout and add the following components
• A list picker
• A text level
• 2 buttons
• 1 text view
• Sound recorder
• Tiny DB
• Bluetooth client
Fig 5.MIT App code blocks
Connection
Now connect all the components as illustrated below (Refer Fig 6).
Arduino Nano Components
D4 RX
D3 TX
Thank You