Transcript ppt

Mobile Photo
James Anderson, Dustin Duran,
Trevor Hamilton, Ahror Rahmedov,
Vivek Rajkumar, Matthew Renzelmann
Overview
Mobile Photo
LCA elements for the Mobile
Client
Matthew Renzelmann, Dustin Duran
Operational Concepts



Designed for Nokia Series 60 phones
utilizing J2ME MIDP 2.0
Allows picture taking, local image
storage, and the uploading of images
to the server
Features accessible through
navigational menus
System Requirements

Install the mobile client using a
standard installation procedure


Account establishment through web
client


.Jar file deployment
One time setup on the phone
Navigational simplicity
Navigation – Implementation Overview
Navigation
 Main three options
 Take Pix
 Pix Gallery
 Settings
Navigation – Take Pix
 Viewfinder displays updating view from camera
 To take a picture:
 Press the “fire” button
 Select capture from the Options menu
 Once captured, the user may:
 Send the image to the server
 Save the image
 Discard the image
Navigation – View Pix
 User may view stored images by browsing
through a list
 Selecting a name displays the image
 The user may then select the following
options:
 Send Image to server
 Delete Image
 Rename Image
 Cancel
Navigation – Settings
 Settings include:
 Username
 Password
 Server address
 These options are entered during
installation but may be changed from this
screen
Architecture – Overview
Architecture



Developed with Sun ONE Studio Mobile with
Nokia Series 60 emulator
J2ME with MIDP 2.0
Modular design extendible to other cellular
phone manufacturers


MobileServerConnection Interface for
server/client connection
Camera functionality not vender dependent

Implemented entirely in J2ME
Mobile Photo
LCA elements for the Web Client
Vivek Rajkumar, James Anderson
Operational Concepts


The web client is the interface that the
user uses to access the pictures
uploaded by the mobile client.
The web client is targeted at all parties
that consume MobilePhoto, as it is
where they will be able to access the
photos they upload
Sample Actions available



Organizing uploaded images
Downloading of images
Public/Private displaying of images
System Requirements

We plan to implement these core
features for the web client:

a registration page where the user will be
able to:



create their own user account
specify personal information
configure their own preferences
Sys Reqs [continued]
o
a login page that would let:

registered users login using their username
and password where:



a cookie would be created to track what user is
currently logged in (and a session variable would
initiated)
new users to register
registered or unregistered users browse
publicly viewable photos (sorted by user)
Sys Reqs [cont]
o
a dynamically created page for each user
that will allow interactions specific to that
user’s needs (once the user has logged
in) that will contain:

one sidebar frame that will let the user:
o
o
change folder (from a list of existing folders in
the form of a drop-down menu)
view thumbnails of all the images in the current
folder (each thumbnail would be clickable so
that the image would be displayed full-size on
the second frame)
Sys Reqs: dynamic main
user page [cont]

one main frame that would:
o
o
display the currently selected image full-size
present the user with a list of options specific to
that image such as:

allowing the user to change the name of the
image

allowing the user to change the visibility of the
image

allowing the user to change the location (folder)
of the image

allowing the user to save the image locally on
their own machine
Sys Reqs [cont]

ability to set certain image folder
attributes such as:


name
visibility (e.g. folder is available publicly vs.
private usage)
Information such as current name, number of
images, and current visibility will also be
presented in some sort of table format to the
user.
Sys Reqs [cont]

ability to send particular images or sets of
images to be printed at some print shop


for the scope of this project, only one print
shop will be supported initially
publicly viewable pages indexed by
username (given that the particular
username has publicly viewable
images/folders)
Sys Reqs [cont]
o
options to change personal information
and preferences

•
ability to change password
ability to change user-specific parameters
such as:

o
personal name, address, contact information
(phone number, email address), location of print
shop
a help (or FAQ) link
SiteMap
SiteMap
Responsibilities
This group will be primarily responsible
for writing the scripts that will generate
the webpage and act as the interface
from the user to their images on the
server. This will be a substantial part of
the project, and assistance will be
needed from the other two groups as
they complete their portions of the
project.
Projected Timeline


May 1 [Done] – Specify the capabilities of
the website.
May 14 [In progress] – Implement at least
a basic interface so that we can test the
other aspects of the project. User
authentication and folder management
need not be implemented yet. With luck,
have the web-pages implemented, just
not all the functionality of them active.
Projected Timeline [cont]


May 26 – All functions should be active.
Debugging should be occurring with all
aspects of project. Project will be
evaluated at this point for “gold plating”
that can be snipped off if necessary.
June 2 – Project should go gold and ship
to all interested parties.
Database Specs and
Architecture for Mobile Photo
Trevor Hamilton
Ahror Rahmedov
Database specs

Four main entities of the Mobile Photo
System represented as the main
tables
1)
2)
3)
4)

Users
Photos
Photo Shops
Print Processes
There are other supporting tables
Specs [cont] Supporting tables

PrintProcessPix


Sizes


Flexibility to add more attribute values
Attributes


Photo sizes
PhotoAttributes


Stores print processes ever initiated
Attribute names and types
PhotoShopUserAccounts

Individual user accounts with photo shops
Database architecture


Hosted by UW CSE servers
Backend


Microsoft IIS/SQL database server
Front end

ASP.NET built in functions to query and
change the Microsoft SQL database
Database Architecture [cont]

Development Environment



Microsoft .NET tools
Compatibility ensured by using the
same vendor tools for front and
backend
Proven industry standard architecture
Timeline





Web service interface and database
architecture specification – May 1
Implement basic functional database – May
7 (tables, relationships, triggers, queries)
Fully implemented and functional database
– May 14
Fully implemented web services – May 21
At least one online Photo Shop service
functioning – May 25