The software for both the Android and computer applications were written in Java. The Android application uses the public Bluetooth APIs in order to make the connection between the phones and BlueBeats. The computer application uses the Bluecove Bluetooth APIs in order to make the connection between the computer and BlueBeats. Both applications contain the same options for the user and follow the same layout in order to increase the usability of both applications for the user. Additionally, both applications hide a lot of the complex Bluetooth functionality from users so that they just have to select devices they want to add to their personal list and then select a device from their list that they want to connect to.

The hardware consists of a WT-32 BlueGiga chip that is used to communicate with the microcontroller board in order to play and receive audio. The design for the microcontroller board was created using the Eagle software. The microcontroller board and the WT-32 chip is placed inside an enclosure that keeps all of the hardware out of sight and keeps all of the delicate parts of the circuit board properly contained. The enclosure for the hardware is 2.6 inches by 2.5 inches and it has holes for the buttons, LED lights, and the audio jack. There are 3 LED lights that include one for power, one for bluetooth connection, and one if the battery needs charging. The four buttons consists of play/pause, next song, volume up, and volume down.

Our team decided to further develop our project into a company after graduating. Since the team consists of only technical students, we had to learn the business side of our project on our own. We were able to see a glimpse of the business aspect through the resources that Cal Poly provides. The resources that were the most useful were the Center for Innovation and Entrepreneurship (CIE) and the Student Startup Assistance Team (SSAT). We were given useful information about the basic process of starting a company, and how to setup a vision that the company could follow. We were also able to draft a provisional patent application from the resources that we received through the CIE.

The original estimated cost for the BlueBeats was based on two main items for development, the Arduino Uno ($30) and Bluetooth chip WT-32 ($60), which is turns out to be around $90. The final cost for our senior project was $732.74 with the hardware development cost being $252.44. The most expensive part of our senior project was creating five BlueBeats devices using the 3D prototype printer and our own circuit board. At the end of our project, each BlueBeats device cost was cut down to a cost of $96.06.

Normally these people will only meet when others bring them together or they are thrown together on a project. DSIC aims to preempt the person discovery process by allowing a way for people to post ideas, events, and other collaborations in a single place that can then be searched by other users.

The system utilizes postings, user profiles, and a tagging system to connect users together. The purpose of the system is not to replace other collaboration and information systems completely, but to help reduce the noise that they create and give users more control over their content consumption.

The scope of this project seems wide and the number of users is vast. The system is purposefully generalized in order to try and better connect people and solve several problems at once; DSIC is believed to be able to address several issues the users have with current systems.

The final application, named coffee_shop, ended up not meeting my expectations. Having spent most of my education developing applications for the internet, instead of the desktop, I ran into pitfalls which, if this had been an internet application, wouldn't have been as problematic.

1. Introduction: Malware in the World Today. Begins with a definition of terms, examination of the types of malware, research into historical pieces of malicious code, a detailed analysis of the attackers, why malware is so prevalent, and why it is so hard to defend against. This section finishes with a comparison of reasons to create and not to create malware.
2. Background: "Good" Pieces of Malware. Examination of what makes malware effective. Analysis of the existing CVSS standard and proposal of the alternative VIPERS classification system. This is followed by a justification of the VIPERS system utilizing a comparison between the digital and information ecosystems. The justification for the alternative classification system is strengthened by the need to recognize stealth and subtlety within malware. This section finishes with an examination of the proposed Plaguebringer worm, as well as an ethical justification of why it was not created.
3. Implementation: A VIPER Examined. A small sample exploit, analyzed according to the VIPERS system.