Problem Statement

The goal of IGLU is to minimize the time spent searching for items and to display
information while also providing an advanced platform for customer interaction and
advertising.
Functional Requirements
Server
User and List Information – The server must store all user and list information within
a database.
Ads – The server must also store product ads which can be linked to lists so that they
can be displayed appropriately.
Database Access – The website and IGLU devices should both be capable of
querying the database to read and write information.
Web Portal
Database access via the web – The website should be able to communicate via the
web to regional databases and web servers in order to provide a customized online
shopping experience.
Simplified User Interface – The web interface will be simple and easy to use. This
will create an environment that will be inviting and easy to use. By creating a user
experience that is desirable the ability to market and advertise will become more
effective.
Support a Minimum of 100 Connections – The database should be able to handle
at least 100 connections at a minimum. This will enable the database to support a
significant number of IGLUs simultaneously.
Optimization For Fast Response Time – The database should be optimized for
speed in order to provide an acceptable online shopping experience. In addition to
speeding up the online shopping experience the speed of the database will allow the
IGLUs to operate efficiently and support a seamless in store shopping experience.
Device
Simplified Color Graphic User Interface – The interface on the device should be
simple and inviting so that customers use the device.
802.11b support – IGLU devices must connect wirelessly to the server as customers
roam about the store.
RTOS Onboard – To provide a solid base for the user interface IGLU will need an
RTOS to handle the low level events efficiently.
Barcode Scanner capability – Barcode capabilities will allow users to quickly
remove items from the list
Rechargeable LiPo Battery and Charging Station – IGLU needs to be easily
recharged to be effective in a store environment.
Packaging – IGLU device packaging must be designed to consider everyday use this
includes:

1
 Shock Resistant – IGLU device should withstand falling on a hard surface.
Water Resistant – IGLU should also withstand having items spilt on it.
Lightweight and Compact – Devices should feel comfortable while being held.

Localization – This project will not incorporate real time localization within the store
on the IGLU devices.

With the different requirements, a conceptual solution to the problem has been created,
shown in Figure 1. This diagram represents the process of how a customer will create
their shopping list, and how the entire system will work.
Database
on
Server
Internet

802.11

In Store
Access
Point

IGLU

Store
Website

Figure1. Overall Conceptual Block Diagram

2
With the conceptual diagram of what is required to create the system, a device needs to
be designed that will work to specifications. In Figure 2, the hardware conceptual design
represents the different modules that will need to be used to create the IGLU device.

LCD and LCD

controller

Capacitive
ACR32UC3
Buttons
Barcode Module Embedded Linux

Battery and
Charger
802.11

Figure2. IGLU Conceptual Block Diagram

3
Performance Requirements
IGLU
Display
Full color
Ability to interface with microcontroller
Micro Controller
Low power consumption
External bus
Support for RTOS
Support of popular data busses (I2C, SPI, TTL, etc)
Peripherals
Ability to integrate with standard busses (I2C, SPI, TTL, etc)
Low cost
Low power consumption
Batteries
Must be rechargeable
Must have ample amount of amp hours
Web Portal
User Interface
Simplified and easy to use
Compatibility for multiple browsers
Web Server
Support for PHP
Support 100+ users at a time
Database
Data Storage
Support fast query responses
Support 100+ connections
Support queries from both IGLUs and website

Technology Survey Assessment

IGLU
Display
Character LCD
Pro - Easy-to-use interface
Pro - No external driver required
Con - No support for graphics or color
Graphic LCD
Pro - Higher flexibility

4
 Con - Creates a professional inviting interface
Con - Needs an external driver
Processor
Arm 9
Pro - Large processing capabilities
Con - High development cost
Con - High power consumption
AVR32UC3
Pro - Low power
Pro - Ample processing capabilities
Pro - Well-supported and reasonable development cost
Con - Limited availability due to early stage of production
Input Interface
Touchscreen
Pro - Higher flexibility
Con - Higher processor overhead
Con - Short life in store environment
Capacitive Buttons
Pro - Low cost
Pro - Simple processor interface
Con - Less intuitive

Web Portal
Web Server
Apache
Pro - No software or licensing cost
Pro - Compatible with multiple platforms
Pro - Support of server side languages
Con - No dedicated support

IIS
Con - Cost per license
Pro - Support of server side languages
Pro - Available support
Database
MySQL
Pro - No license fees
Pro - Enterprise class features
Pro - Support available on a subscription basis
Con - Not as widely accepted / used as other databases
SQL
Pro - Enterprise class features

5
Pro - Widely used and accepted database
Con - High cost per license
Pro - Support available on a subscription basis

6
Detailed Functional Block Diagram
By comparing the different technologies that can complete this problem, many different
components have been chosen to implement this system. In Figure 3, a detailed
functional block diagram has been constructed to show the early stages of the device
schematic.
Input from
Charge
Tabs
LTC1731-4.2
4.2V
6V Lithium C/x
UBP001
Charger
Battery
LTC3548 / LiPo 4.2v 1.7Ah
LT1307
Switching 5V Internal
Supply Antenna
3.3V
5V

SPI
802.11 Module
Trace
Buttons

AD7142
AT32UC3 Capacitive
Barcode TTL
512KB ROM Touch
Module
Controller
I2C
3.3V
Data Bus

S1D13A04
Display Driver+ RGB+Timing
80K VRAM AM320240L
3.4"
TFT LCD
320x240
32MB
SRAM

Figure3. IGLU Functional Block Diagram

7
Project Timeline
After a series of phases, activities, and tasks have been defined, a project timeline needs
to be constructed. For this timeline, a Gantt chart shown in Figure 4 has been generated
to represent the different phases of the project.

Figure 4: Project Phases Gantt Chart

With this figure, the project is planned to start January 1st and concluded at the end of
April. The seven bars represent the research, design, procurement, implementation,
testing, documentation, and business model phases.

To further expand this project timeline, each of these phases can be broken down into
activities. In Figure 5, each phase is broken into three main activities: database, software,
and hardware. In a future document, a critical path will be calculated, and this will path
will mainly involve the hardware activities.

Figure 5: Project Activities Gantt Chart

8
The business model section spans the entire length of the project, as shown in Figure
6.

Figure 6: Project Activities Gantt Chart

9
Deliverables
As the project progresses and sections of the system are finalized, deliverables can be
generated in order to present to the stakeholders. By completing the deliverables, shown
in Figure 4, the team will be adding additional value to the product.

Figure 4: Deliverables Timeline

Device Schematic – 1/26/08

The schematic includes all hardware components and describes the hardware architecture
at the component level, including all connections between components.
Website User Manual – 2/15/08
The website user manual will provide step by step instructions for the user (shopper), and
cover account creation, account management, list creation, and list management.

10
Database Manual – 2/15/08
This manual provides technical instructions for the grocer. The database manual will
cover requirements, setup, management and maintenance guides for the database. This
document will aid the store in setting up the IGLU system.

Final PCB – 2/15/08

The final PCB means that we have the prototype board completed and the software can
now be developed on the final prototype.
Final Test Plan – 2/20/08
The final test plan will provide an outline for testing all features of the IGLU device to
ensure proper functionality. This document will provide a measure of quality control for
the project.
Troubleshooting Guide – 3/13/08
This document provides a methodology for debugging issues that may arise during the
lifetime of the unit. This will cover user errors, software errors, and hardware issues.
Code Listing – 4/7/08
This document will cover all of the code running on the IGLU and signifies the
completion of the IGLU firmware.
Device Specification Sheet 4/7/08
This document will provide a listing of the results of the device testing. This will also list
the final values for the operating parameters and requirements for the device.
Business Plan – 4/9/08
The business plan sets forth our plan to bring IGLU to the market. This includes our
supply chain, marketing analysis, product support plans, and sales model.
Final Product Documentation – 5/6/08
This document incorporates all of the generated documentation to support the product
and business plan.
Final Demonstration – 5/6/08
After completion of the project a working demonstration will be provided to the
stakeholders, which will demonstrate the projects capabilities.

11
Milestones
Throughout the project, the team will achieve a series of milestones, shown in Figure 5.
These milestones will mark significant achievements through the project, and will allow
for further progress on the project.

Figure 5: Milestones Timeline

Procurement of Components – When we purchase all necessary components, we will be

beginning the transition from the design phase to the implementation phase.
Placement of OS on Development Board – Once we get the OS onto our development
board, it will be easy for us to begin writing the actual code for our GUI and user input.
Server and Database Completed – With the database accessible by the user and the
IGLU, we can begin the transition from design to implementation and testing.
Construction of Business Model – Once our business scope has been defined, we can
begin to add value to our device, and prepare for possible sales.
Schematic Designed – With our first revision of our schematic, we can begin
functionality testing and purchasing PCB’s.
Successful Testing of Peripherals on uC – Since we can now access and utilize the
information from our peripherals, it will indicate the transition to implementation.
Design Review/Mid-Term Presentations – Our technical advisor will have a chance to
critique our current device, and we can alter future plans accordingly.

12
Graphical User Interface Completed – With the user interface finally completed, we will
be making the transition from implementation to testing and documentation.
Working IGLU Packaged and Completed – Our device now meets all functional
requirements, and is ready to be tested and prepared for final presentation.
Database Access by IGLU – The IGLU now works seamlessly as a system, which ends
our testing phase and begins the documentation phase and final presentation.
Final Functional Presentation Completed – Our device has been demonstrated for the
sponsor and advisor and has been signed off as completed. The device can now begin
incubation phase of E4.

13