Recent Changes - Search:


Course Info

2012 Class Notes

2012 Students

Student Groups


2009 Students

Student Groups


2006 Class

2006 Faculty

2006 Evaluations

Lecture Notes

2006 Students

Student HWs

API Groups

Student Groups


Wiki Docs

edit SideBar


Group Members:
Ramya Srinatha
Naiem Sleiman
Fedny Francois

The Variable Matrix for our product is attached: Variable Matrix

We are meeting around 3 - 4 times a week; most of the time before class starts and on Skype during weekends.

The First 3 weeks of March:

Our goal first was to convince the VC that we are able to design such product. So we need to patent our product and write a Patent Publication Document. Links for Sample Patents:
In order to write such publication we had to make an intensive research on how to create video glasses. After we had an idea about video glasses we are able to divide our product into three parts:

1) OS: Software to manage our product's Application
2) SenseBoard: For capturing, analyzing, and interpreting finger and hand movements and translating them into text, data, and other input for our product. (The references link :
3) CyberDisplay: Using Kopen's Cyberdisplay because those displays are the world's only transmissive LCDs that use high-quality single-crystal silicon transistors. (
We are planning to allow communication between the OS, SenseBoard and Cyberdisplay on eyeglasses. However, another stuff we are looking at to help us to design our product are: Spy Glasses, LCD Display Module, Video Receivers, Olympus Eye-Trek(TM) video glasses, and Vuzix products.
Other Links:

Presentation Day:

You can check the video of our product at :

First week of April:

Start designing our product using the UML: How to draw use cases, sequence diagrams and class diagram? As well we started to identify the type of customers, how the users will interact with our product and an optimal size for our product to fit most sizes of people. Searching for other companies that have designed video glasses. Google just announced its augmented reality glasses, and also we found the following companies:
1) Zetronix: They designed an HD Virual galsses
2)Prober Industrial: They also designed video eye wear
3)Kindyelec Company


Requirements specification for OS:

The Operating System for eVision (known as e-OS) is responsible for managing the hardware, which is the sensor board & the camera projector, and all applications that will be available / downloaded. The specific requirements for e-OS are divided into functional; and non functional requirements.
i.Functional Requirements:
The e-OS supports the eVision hardware and its applications as well itís responsible for multitasking and security of the software. The user should be able to communicate with the OS through applications. A successful communication allows the user to efficiently run the applications through the sense board. We can compare this to the Mobile OS that has the feature of touch screen but in eVision the OS will offer interaction to the projected screen through the sense board. Also, the e-OS should be able to recognize the projected camera. Moreover, e-OS will be responsible for offering a friendly user interface. The main purpose behind this functionality is not making our product complicated; we want users to find it easy to interact with. Any user who has used a computer, tablet, or smart phone will find eVisionís interface very familiar. In addition, the e-OS will be able to update the applications and the OS itself. In order to allow updates the e-OS should be able to have networking functions. Those functions are Wi-Fi connectivity and Bluetooth connectivity.
ii. Non-Functional Requirements:
After specifying the functional requirements of e-OS, now we can try to draw some of the non functional requirements. First, we could consider how much e-OS would consume energy (battery). Second, if e-OS is failing or showing error messages, the user should be able to reboot or check for upgrades. Third, e-OS will be an open source OS that promotes free redistribution and access to an end product's design and implementation details. Also, the price that will cost to develop e-OS will depend on how big the development team is, but definitely we considered the price as a non functional requirement here.

Use Case Diagram

UC1 Eyeglasses Apps

UC2 Projector







Final Report: eVision

Final Presentation: Final Presentation

Edit - History - Print - Recent Changes - Search
Page last modified on May 14, 2012, at 06:59 AM