SoundsRight-StatusReport-Mar3(2).doc - Google Code

foreheadsobstinacySoftware and s/w Development

Aug 15, 2012 (5 years and 11 months ago)


Sounds Right

Ben Aksoy, Alex Brownell, Julie Morris, Chris Weyers

Status Report

Our instrument and vocal tuner project is on schedule so far. We haven't developed any
code yet but the Inception and Elaboration Phases have helped us define the direction and scale
of our application. We have tackled some issues, we're working to address

some current risks
and to anticipate future risks.

One of our tasks in elaboration was to establish our work breakdown schedule and update
our schedule. This was an eye opener for our team because it revealed our limited time
constraints. Getting off sc
hedule or running out of time is a risk for our team, but it can be
addressed. One way of staying ahead of our tight schedule is getting some work done over
Spring Break. Our team has been good with getting tasks done ahead of time and we think that
t will keep our heads above water during development.

An issue we have tackled is setting up a code repository. We went with Google Code for
its ease of use and its support for Subversion. This did present some minor problems since a
couple of our member
s have never used version control before. But these issues were quickly
addressed because we were able to help each other out. One issue is the convoluted commands
needed to

use SVN but we will probably

address this by using NetBeans, a Java IDE that
rts building and running Java programs, as well as SVN features all through a nice
graphical interface.

Another risk is the performance of the Java sound API. Not only do we need high quality
sound sampling for accurate frequency analysis but fast respon
se time so there is little delay
between pitch updates. The computation intensive Fourier transformation algorithm must process
the audio quickly enough since we want real
time performance. Java isn't exactly known for its
performance so we will probably f
irst develop a prototype application to make sure we can meet
our performance requirements. Once we get a functional prototype that can process the sound
input, it's downhill from there since everything else will build on top of it.