Download - Android SMIL Messenger Presented By: Alex Povkov Brad Gardner Jeremy Spitzig Santiago Jamriska
Android SMIL Messenger
Presented By:
Alex Povkov
Brad Gardner
Jeremy Spitzig
Santiago Jamriska
Introduction
This application uses the Android 1.6 Platform and later and will provide a multimedia messaging system for
users to communicate with each other, sharing pictures, videos, audio, and text-based content using messages created based on the SMIL specification.
The Team
Participant Roles Related Experience
Alex Povkov Implementation,
Development, Testing Java, Web Technologies,
Databases, XML
Jeremy Spitzig
Implementation, Development, Configuration, Testing
Java, Source control management, Databases, XML
Santiago Jamriska Documentation,
Implementation, Development, Testing
Java, MySQL databases, PHP and web development.
Brad Gardner Team Lead,
Implementation, Development, Testing
Java, Databases, Web Technologies, XML, Source control management
How does it work?
• Users can create or view messages
• Multiple media types can be added to a message
• You can preview, save or send any message
Use Cases
• We have three Actors: the Sender, the Receiver and the Server
•Both the Sender and the Receiver have the same main interaction with the application
•The server is the mediator
Implementation (GUI)
• Main Menu: Users can choose to create a new message or view stored messages
Implementation (GUI)
• Messages: In here, the user can view received messages, sent messages, and saved unsent messages.
Implementation (GUI)
• New Message: In here, users can define the layout of the message
After defining the layout, users can go on to creating the contents of the message
• Add Components: Users can choose what type of components to add to the message
• Text
• Images
• Audio Files
• Video Files
Implementation (GUI)
Implementation (GUI)
•Settings: Users can insert text, files, duration time, and a start time to the specific components
• Player: Users can preview the messages before sending them, and view the messages as they are received
Implementation (GUI)
• HTTP Sockets:Using sockets, the devices are able to communicate to a central server where they can download the message details.
• SMS Messaging:SMS (Short Message Service) will be used to notify devices that they have a new message in the central server.
Implementation (Communications)
Implementation (Detailed)
Project Task Partition
Project Management
• The Android Messenger Project was versioned and managed using Google Code hosting.
• Project Site URL: http://code.google.com/p/csc440androidproject/
Software Configuration Management
Inspection (Communications)
No
File LOC Severity Description By
1 SmilReceiver Minor Enter comments on this file Santiago2 SMSReciever Minor Enter comments on this file Santiago3 ClientHandler Minor Enter comments on this file Santiago4 CommunicationManager Minor Enter comments on this file Santiago5 MessageAction Minor Enter comments on this file Santiago6 SmilReceiver Major Change the SmilConstants to the
appropriate fileSantiago
7 ClientHandler Major Change the SmilConstants to the appropriate file
Santiago
8 ClientHandler 98 Minor “port” variable needs to be referenced with “this.”
Santiago
9 ClientHandler 62 Minor “key” variable needs to be referenced with “this.”
Santiago
10 ClientHandler 38 Minor “context” variable needs to be referenced with “this.”
Santiago
11 ClientHandler 31 Major “action” variable has to be declared private
Santiago
12 ClientHandler 33 Major “context” variable has to be declared private
Santiago
13
Deliverable Communications _____________________ Page 1 of 1 Team#2 Team members Brad Gardner, Alex Povkov, Santiago Jamriska, Jeremy Spitzig __________________________ Date 03/20/2010
Inspection (Database)
No LOC File Severity Description By
1 151 DBAdapter.java
Minor Need resource.setId(-1); for the message’s resource in some form here?
Alex
2 15-17
Message.java
Minor Useless comments? Alex
3 18-19
Message.java
Minor Unaligned with rest of code Alex
4 208 DBAdapter.java
Minor unused variable Alex
5 Minor Code formatting (use java conventions) Alex6
Deliverable Database _____________________________ Page 1 of 1 Team#2 Team members Brad Gardner, Alex Povkov, Santiago Jamriska, Jeremy Spitzig _______________________________________________ Date 03/20/2010
Inspection (SMIL)
No
File LOC Severity Description By
1 SMILMessage.java 83-167
Minor Replace hardcoded “magic strings” with symbolic constants.
Jeremy
2 SMILReader.java 77-144
Minor Replace hardcoded “magic strings” with symbolic constants.
Jeremy
3 All Files All Major More comments necessary Jeremy4 SMILMessage.java 104-
143Minor A generic function could be written for this
code accepting the serializer, tag name, a series of attributes/values, and any text which
goes inside the tag, which builds the tag.
Jeremy
5
Deliverable SMIL API ___________________________ Page 1 of 1 Team#2 Team members Brad Gardner, Alex Povkov, Santiago Jamriska, Jeremy Spitzig _______________________________ Date 03/20/2010
Inspection (User Interface)
No LOC File Severity Description By1 24,
32,38
TabsMenu.java Minor Hard coded values for tab names. Brad Gardner
2 88 SMILPlayer.java Minor Generic Exception caught Brad Gardner
3 65 SentTab.java Major Message Subject value is explicitly set Brad Gardner
4 30 MessagePosition.java
Minor ID of extras attribute explicitly set to “test” Brad Gardner
5 66 InboxTab.java Major Message Subject value is explicitly set Brad Gardner
6 69 DraftsTab.java Major Message Subject value is explicitly set Brad Gardner
7 86 FileBrowser.java
Minor ID of extras attribute explicitly set to “test” Brad Gardner
8 117 FileBrowser.java
Major Non-implemented catch block Brad Gardner
9 41 AddImage.java Minor ID of extras attribute explicitly set to “test” Brad Gardner
10 63-76
AddComponents.java
Minor Magic Numbers used Brad Gardner
11 99-115
AddComponents.java
Minor ID of extras attribute explicitly set to “test” Brad Gardner
12 43 AddAudio.java Minor ID of extras attribute explicitly set to “test” Brad Gardner
13 31 AddAudio.java Minor ID of extras attribute explicitly set to “test” Brad Gardner
30
Deliverable User Interface Page 1 of 1 Team#2 Team members Brad Gardner, Alex Povkov, Santiago Jamriska, Jeremy Spitzig Date 03/20/2010
Inspection (SRS Document)
No
Page Severity Description By
1 9 Major Move connection from add items to create message to point to decision
Santiago
2 3 Minor Extra colon character in table of contents Alex3 10 Major Preview use case should be removed and replaced by
create message implementing view messageJeremy
4 11 Major Detailed Activity diagram: view details activity should connect to decision before the add items activity
Jeremy
5 5 Minor Add XML to definitions Alex6 All Major Any android 2.0 reference should be changed to Android
1.6+Jeremy
7 5 Minor Add save/delete and other functionality into the overview description
Alex
8 All Minor “Multimedia Message” capitalization errors Jeremy9 6 Major Multimedia Message Components section should be
moved, entire section should be re-worked to flow better.Jeremy, Alex, Brad
10 7 Major Formatting of Messages and New Messages section Alex11 15 Minor Streaming multimedia Jeremy12 7 Minor Drafs description should have “and not sent” removed Jeremy13 13 Minor Add drafts feature to other requirements Santiago14 13 Minor Add two-way messaging to other requirements Brad15 12 Major Sentence needs completed, ended in mid-thought Alex16 11 Major Detailed Activity diagram: added components should
connect to decision after the add items activityJeremy
17
Deliverable _SRS Document_______________________________ Page 1 of 1 Team#2 Team members Brad Gardner, Alex Povkov, Santiago Jamriska, Jeremy Spitzig Date 03/20/2010
Team Communication
Gmail-based Communications
Team Communication
Google code and Wiki-based Communications
• All media worked perfectly on the emulator
• Communications with the server and the other emulated device worked perfectly as well
• Decided to deploy under Android 1.6
Android 1.6 Testing
• Mounted application onto Android-based phone (Running Android 1.6)
• Application worked perfectly on a single phone.
• Had a few issues in communications when using a second phone.
• Issues were resolved by tweaking the code and the server
Device Testing
Testing
Testing Models:
1. Android 2.1 Testing
2. Android 1.6 Testing
3. Device Testing
Android 2.1 Testing
• We emulated Android 2.1 for the first tests of the application
• Emulation of the video playback didn’t work
• Dropped emulator to version 1.6
Summary
We have successfully completed the requirements for this project. A fully functional Android SMIL
Messenger application has been achieved according to both the Android and SMIL component
specifications. The course objectives were also followed and successfully completed throughout the
semester.