Docstoc

Software Reqs Specification 1.9

Document Sample
Software Reqs Specification 1.9 Powered By Docstoc
					                                                      Formatted: Book Title, Font: 36 pt, Not Bold

               MOBILE SMIL                            Formatted Table




                                                      Formatted: Book Title, Font: 24 pt
     SOFTWARE REQUIREMENTS SPECIFICATION

                                                      Formatted: Font: 30 pt, Bold

Mobile SMIL                                           Formatted: Left, Space After: 0 pt


                      Version    1.95
                  Last updated   3/21/20103/21/2010   Formatted: Space After: 0 pt, Line spacing:
                                                      single

Software Requirements Specification                   Formatted: Font: 22 pt
                                                      Formatted: Left

                                                      Formatted: Left


                  CSC 440/540 Spring 2010             Formatted: Font: 12 pt
         Jason Daniels    Formatted: Font: 14 pt



Team 6   Ben Bedinghaus   Formatted: Font: 16 pt
                          Formatted: Right, Right: 0.11", Space After:
         Ryan Ware        0 pt, Line spacing: single
                          Formatted Table
Table of Contents
                                                                                                                                                                    Formatted: Normal


1 Document Information ............................................................................................................................ 64
   1.1 Prepared By ....................................................................................................................................... 64
   1.2 Document Responsibilities................................................................................................................ 64
   1.3 Revision History ................................................................................................................................ 64
2 Introduction ............................................................................................................................................. 86
   2.1 Purpose ............................................................................................................................................. 86
   2.2 Scope ................................................................................................................................................. 86
   2.3 Definitions, Acronyms, Abbreviations............................................................................................... 86
   2.4 References ........................................................................................................................................ 86
   2.5 Overview ........................................................................................................................................... 86
3 Overall Description................................................................................................................................... 97
   3.1 Product Perspective .......................................................................................................................... 97
   3.2 Product Functions ............................................................................................................................. 97
   3.3 User Characteristics .......................................................................................................................... 97
   3.4 General Constraints .......................................................................................................................... 97
   3.5 Assumptions and Dependencies ....................................................................................................... 97
4 Specific Requirements............................................................................................................................ 108
   4.1 External Interface Requirements .................................................................................................... 108
       4.1.1 User Interfaces ......................................................................................................................... 108
       4.1.2 Hardware Interfaces .............................................................................................................. 1210
       4.1.3 Software Interfaces ................................................................................................................ 1210
       4.1.4 Communication Interfaces ..................................................................................................... 1310
   4.2 Functional Requirements .............................................................................................................. 1411
       4.2.1 Overall Activity Diagram ........................................................................................................ 1411
       4.2.2 Use Case Diagram .................................................................................................................. 1512
   4.3 Performance Requirements .......................................................................................................... 2416
   4.4 Design Constraints ........................................................................................................................ 2416
   4.5 Software System Attributes .......................................................................................................... 2416
   4.6 Other Requirements ..................................................................................................................... 2416
5 Project Management ........................................................................................................................... 2517
   5.1 Project Estimation ......................................................................................................................... 2517
   5.2 Risk Assessment ............................................................................................................................ 2517
6 Future System Improvements .............................................................................................................. 2618
7 Appendix .............................................................................................................................................. 2719
   7.1 Task Partition ................................................................................................................................ 2719
   7.2 Work Schedule .............................................................................................................................. 2820
   7.3 Meeting Agenda & Minutes .......................................................................................................... 2921
   7.4 Communication Records ............................................................................................................... 4234
   7.5 Software Configuration Management .......................................................................................... 5446
Document Information ..................................................................................................................................                Formatted: Font: (Default) +Body, 11 pt

   Prepared By .................................................................................................................................................
   Document Responsibilities..........................................................................................................................
   Revision History ..........................................................................................................................................
Introduction .................................................................................................................................................. 5      Formatted: Font: (Default) +Body, 11 pt

   Purpose ..................................................................................................................................................... 5
   Scope ......................................................................................................................................................... 5
   Definitions, Acronyms, Abbreviations ...................................................................................................... 5
   References ................................................................................................................................................ 5
   Overview ................................................................................................................................................... 5
Overall Description....................................................................................................................................... 6           Formatted: Font: (Default) +Body, 11 pt

   Product Perspective .................................................................................................................................. 6
   Product Functions ..................................................................................................................................... 6
   User Characteristics .................................................................................................................................. 6
   General Constraints .................................................................................................................................. 6
   Assumptions and Dependencies ............................................................................................................... 6
Specific Requirements .................................................................................................................................. 7             Formatted: Font: (Default) +Body, 11 pt

   External Interface Requirements .............................................................................................................. 7
       User Interfaces ...................................................................................................................................... 7
       Hardware Interfaces ............................................................................................................................. 7
       Software Interfaces ............................................................................................................................... 7
       Communication Interfaces .................................................................................................................... 7
   Functional Requirements .......................................................................................................................... 7
       Overall Activity Diagram ....................................................................................................................... 7
       Use Case Diagram ................................................................................................................................. 7
       Detailed Activity Diagram ..................................................................................................................... 7
   Performance Requirements ...................................................................................................................... 7
   Design Constraints .................................................................................................................................... 7
   Software System Attributes ...................................................................................................................... 7
   Other Requirements ................................................................................................................................. 7
Project Management.................................................................................................................................... 9            Formatted: Font: (Default) +Body, 11 pt

   Project Estimation ..................................................................................................................................... 9
   Risk Assessment ........................................................................................................................................ 9
Future System Improvements ................................................................................................................... 10                   Formatted: Font: (Default) +Body, 11 pt

Appendix ..................................................................................................................................................... 11   Formatted: Font: (Default) +Body, 11 pt

   Task Partition .......................................................................................................................................... 11
   Work Schedule ........................................................................................................................................ 11
   Meeting Agenda & Minutes .................................................................................................................... 11
   Communication Records ......................................................................................................................... 11
   Software Configuration Management .................................................................................................... 11
No table of contents entries found.
                                                                                                    Formatted: Heading 1, Left

1 Document Information


1.1 Prepared By
Ryan Ware, Jason Daniels, Ben Bedinghaus

1.2 Document Responsibilities
 Name                 Sections

 Jason Daniels        External Interface Requirements
                      Communication Records
                      Software Configuration Management
 Ben Bedinghaus       Introduction
                      Overall Description
                      Project Management
                      Work Schedule
 Ryan Ware            Functional Requirements
                      Meeting Agenda & Minutes
                      Performance Requirements
                      Design Constraints
                      Software System Attributes
                      Other Requirements
                      Future System Improvements
                                                                                                    Formatted: Left


1.3 Revision History
 Name                 Date           Reason For Changes                                   Version

 Ryan Ware            2/10/2010      Created document – headers, table of contents.       0.1
 Ryan Ware            2/14/2010      Added revision history, document responsibilities.   0.2
 Jason Daniels        2/21/2010      Added External Interface Requirements,               0.3
                                     Communication Records.
 Ryan Ware            2/21/2010      Added use case & detailed activity diagrams,         0.4
                                     meeting agendas & minutes, updated task partition.
 Jason Daniels        2/22/2010      Updated Communication Records                        0.5       Formatted Table

 Ben Bedinghaus       2/22/2010      Updated Introduction and Overall Description         0.6       Formatted Table

 Jason Daniels        2/26/2010      Updated Communication Records and corrected          0.7       Formatted Table

                                     tacking with Interface.
Ryan Ware        3/01/2010   Added Overall Activity Diagram, Performance          0.8   Formatted Table

                             Requirements, Software System Attributes, and
                             updated Meeting Agendas & Minutes.
Jason Daniels    3/14/2010   Added screen shots to interface description.         0.9
Jason Daniels    3/20/2010   Appended new email messages.                         1.0   Formatted Table

Ryan Ware        3/20/2010   Revised all Use Case and Activity diagrams, added    1.1   Formatted Table

                             Design Constraints, added Future System
                             Improvements.
Ben Bedinghaus   3/21/2010   Updated project management and work schedule         1.2   Formatted Table

Jason Daniels    3/21/2010   Edited Interface                                     1.3   Formatted Table

Ben Bedinghaus   3/21/2010   Updated Overall Description and Introduction         1.4   Formatted Table

Ryan Ware        3/21/2010   Updated document responsibilities and Player         1.5   Formatted Table

                             activity diagram.
Jason Daniels    3/21/2010   Updated screen shots, added Software                 1.6   Formatted Table

                             Configuration Management
Ben Bedinghaus   3/21/2010   Update spelling mistakes and also Acronyms section   1.7   Formatted Table

Jason Daniels    4/18/2010   Added header numbers.                                1.8
Jason Daniels    4/18/10     Updated title page, corrected interface section      1.9
                                                                                        Formatted: Left
                                                                                                    Formatted: Heading 1, Left

2 Introduction


2.1 Purpose
     The purpose of this project is to create an embedded multimedia messaging system. It will      Formatted: Indent: Left: 0.5"
     allow users to compose, send, play and browse for messages.

2.2 Scope
     The project will allow users to create, modify and save messages. It will also allow them to   Formatted: Indent: Left: 0.5"
     preview, send and receive messages. Received messages can also be viewed. This project will
     implement a subset of the SMIL. The application will only be available on Google Android
     phones that are using the operating system 2.0 or higher.

2.3 Definitions, Acronyms, Abbreviations
     SMIL – Synchronized Multimedia Integration Language                                            Formatted: Indent: First line: 0.5", Space
     XML – Extensible Markup Language                                                               After: 0 pt, Line spacing: single

     API – Application Programming Interface
     SDK – Software Development Kit
     ADT – Android Development Tools
     UML – Unified Modeling Language
     SRS – Software Requirements Specification
                                                                                                    Formatted: Indent: First line: 0.5", Line
                                                                                                    spacing: single
2.4 References
     N/A                                                                                            Formatted: Indent: First line: 0.5"


2.5 Overview
                                                                                                    Formatted: Heading 2, Left, Indent: Left:
     There will be three parts composer, player and browser. It will allow
     users to send the messages and receive them.Purpose


     Scope


     Definitions, Acronyms, Abbreviations


     References


     Overview
                                                                                                          Formatted: Heading 1, Left

3 Overall Description


3.1 Product Perspective
      The product is a standalone piece of software. This product will be interfaced through a cell       Formatted: Indent: Left: 0.5"
      phone utilizing touch screen and a keyboard. It will also be a phone running the Android
      operating system 2.0 or higher.

3.2 Product Functions
      This product will allow for three different views. The user will be allowed to compose, play, and   Formatted: Indent: Left: 0.5"
      browse messages. Send and receive will be apart from those other groups.

3.3 User Characteristics
      Users will be familiar with the Google Android phones. They will understand how the                 Formatted: Indent: Left: 0.5"
      applications are built by default. They will have both touch screen and keyboards available.

3.4 General Constraints
      This product will only be available for the Google Android phones. Also, this product will also     Formatted: Indent: Left: 0.5"
      rely on a web server and a database in order send and receive messages. In order for full
      functionality the application must have access to the internet via the phone. The phone will also
      need to have an SD sd card.

3.5 Assumptions and Dependencies
      It is assumed that the application will be used within the service of the cell phone carrier so     Formatted: Indent: Left: 0.5"
      there is access to the data.

Product Perspective                                                                                       Formatted: Heading 2, Left




Product Functions


User Characteristics


General Constraints


Assumptions and Dependencies
                                                                                                          Formatted: Heading 1, Left

4 Specific Requirements


4.1 External Interface Requirements


4.1.1 User Interfaces
       The user interface will be a series of screens (in android terms, activities) that will provide    Formatted: Left, Indent: Left: 0.5"
       appropriate UI views to controll the application. Such UI views include buttons, lists, dialogs,
       text boxes, menues, and drag-and-drop elements. Overall navigation will be delegated from a
       home screen and from there spawn off to other activities. Below are various screen shots:r




        Icon of the application                                                                           Formatted: No underline, Font color: Auto
                                                                                                          Formatted Table



                                           Home screen                       Browser                      Formatted: No underline, Font color: Auto
                                                                                                          Formatted: No underline, Font color: Auto




                                                                             Player menu                  Formatted: No underline, Font color: Auto
        Browser selection dialog           Player
                                                                                                          Formatted: No underline, Font color: Auto
                                                                                                          Formatted: No underline, Font color: Auto
Composer                Composer menu                  Composer remove dialog   Formatted: No underline, Font color: Auto
                                                                                Formatted: No underline, Font color: Auto
                                                                                Formatted: No underline, Font color: Auto




Composer add resource   Composer resource properties   Composer positioning     Formatted: No underline, Font color: Auto
                                                                                Formatted: No underline, Font color: Auto
                                                                                Formatted: No underline, Font color: Auto




Composer sizing         Composer region edit menu      Composer gerneral        Formatted: No underline, Font color: Auto
                                                       properties               Formatted: No underline, Font color: Auto
                                                                                Formatted: No underline, Font color: Auto
        Composer text editor                                                                                 Formatted: No underline, Font color: Auto
                                                                                                             Formatted: Left, Indent: Left: 0.5"


4.1.2 Hardware Interfaces                                                                                    Formatted: Heading 3, Left
             The main hardware interface will be a mobile phone with Google’s Android operating              Formatted: Indent: Left: 1"
             system. Not all Android phones are identical, but most will include a 320x480 display
             resolution, a touch screen, sound output, and an input method.

                                                                                                             Formatted: Left, Indent: Left: 1"


        The main hardware interface will be a mobile phone with Google’s Android operating system.           Formatted: Left, Indent: Left: 0.5"
        Not all Android phones are identical, but most will include a 320x480 display resolution, a touch
        screen, sound output, and an input method.

4.1.3 Software Interfaces                                                                                    Formatted: Heading 3, Left
        All android phones run off a Linux kernel which runs the Dalvik viertual machine. In short, the      Formatted: Left, Indent: Left: 0.5"
        Dalvik viertual machine is a light-weight virtual machine that reads translated java byte-code.
        Therefore, the SMIL application will be written in Java using Android APIs.

        Furthermore, the physical look of the interfacace will consist of three of major activities for
        browsing, composing, and playing a SMIL. Navigation will primarily work through a home screen
        which has options for the user to navigate to either the browser or composer. From those
        activities options will be given to play a SMIL. Lastly each acttitivity will provide proper
        navigation to other activities.

        4.1.4 All Android phones run off a Linux kernel which runs the Dalvik virtual machine. In short,     Formatted: Left, Indent: Left: 0.5"
        the Dalvik virtual machine is a light-weight Java virtual machine. Therefore, the SMIL application
        will be written in Java using Android API.

        Furthermore, the physical look of the interface will be primarily a tab-layout, with a full screen
        view for the player. The various tabs include a SMIL player, a SMIL manager, and a SMIL
        composer.
Communication Interfaces                                                                              Formatted: Heading 3, Left
     With the hardware being a mobile phone communication will take place on various wireless         Formatted: Left, Indent: Left: 0.5"
     network carriers. In more detail, users will have the ability to send and receive SMILs and
     synchronization will be managed by implementing the Android Sync Adapter.

       With the hardware being a mobile phone, communication will take place on various wireless
       network carriers. In more detail, users will have the ability to send and receive SMILs and
       synchronization will be managed through a background service. The service will query a MySQL
       database for any new messages to the phones id number (the phones phone number).

                                                                                                      Formatted: Indent: Left: 0.5"


                                                                                                      Formatted: Left
4.2 Functional Requirements                                                                  Formatted: Heading 2, Left

4.2.1

Overall Activity Diagram



                                                                                             Formatted: Left
                                                                                             Field Code Changed

                                       Start Home
                                         Activity



  Start Manager                                                             Start Composer
                   Press Browse...                       Press Create New
     Activity                                                                   Activity




                                     Close application
4.2.2 Use Case Diagram   Formatted: Heading 3, Left
                          Use Case Diagram



                                         Player


                   Play View

   Stop file                                                             Sender / Receiver

                                     Play file
               <<includes>>


  Parse XML                                              <<extends>>
                                                                                      Manage View
                  <<includes>>

                                                                       Browse files
                                                                                                               Receive file
               Compose View                      <<extends>>
                                                                                  <<includes>>

                                                                       <<extends>>

                                                                                                 Send file
Preview file
                     Edit file

                                                                        Select file          <<includes>>
                                 <<includes>>
                                                                                                             <<includes>>


                                                 Generate XML
                                                                                             Package media
                                                                         <<includes>>
                                                 <<includes>>




                                                                        <<includes>>
                                                 Create new file                                         Save file




       Composer
                                                                                                                                    Formatted: Normal
                                                                                                                                    Field Code Changed




                                         Player


                         Player

   Stop file                                                               Sender / Receiver

                                                 Play file
                     Pause file

                                                             <<extends>>
                                                                                     Manage View
                  <<includes>>      <<includes>>

                                                                           Browse files
                                                                                                                     Receive file
                    Composer
                                                                                          <<includes>>

                       Parse XML                                           <<extends>>
                                                 <<extends>>
Preview file
                  <<includes>>                    <<includes>>
                                                                                                         Send file

                                                                                                                <<includes>>
                                                                                                     <<includes>>
                  Edit file                                                 Select file
                              <<includes>>

                                             Generate XML
                                                                                                     Package media
                                  <<includes>>                                 <<includes>>



                                                                  <<includes>>
                       Create new file                                                                               Save file




       Composer
4.2.3 Detailed Activity Diagrams
                                                                                                                              Field Code Changed

                                               Play SMIL
         Composer                                             Player                                       Inbox/Manage


                                                                                           File Not Open



                                                                                                           Select SMIL File




                                                                 File Open



                                    Display Static
                                        SMIL



                                                                          Press Open

                                   Close


                                                      Press
                                                                          Press Send                       Send SMIL file
                                                      Play


                                                                                           Stop SMIL
                                                                                                           Select SMIL File
                                                     Display Static
                                                         SMIL


                                                              Press
                                   Play SMIL                  Pause                          Press
                                                                                             Open

                                                           Press Play
         Load file in
                                                                 Press Edit
         Composer




                                   Stop SMIL                                  Press Stop
                                                                                          Formatted: Left

                Play SMIL
Composer                    Player                                     Inbox/Manage




                                                       File Not Open   Select SMIL File



                            File Open



                          Display Static
                              SMIL




           Close Player                                                Press Browse


                           Press Play




                Play SMIL                         Press Browse



                                                     Stop SMIL         Select SMIL File


                                     Press Stop

                Stop SMIL
                            Compose SMIL
Player                                     Composer                                      Manager




                  Create new                                  Do not create new




          Load blank SMIL                                                         Select SMIL file.




                                      Display SMIL
                                                            Send



                                                                     Not saved

Preview         View

            Finished Editing
                                                                                       Saved
                                                     Save          Save
                                         Modify



                                                                                       Send
                                        Edit File


                               Do not want to save



           Want to save



               Save                      Close
                                                                                                                               Formatted: Normal
                                                                                                                               Field Code Changed
                                         Compose SMIL
       Player                                           Composer                                                  Manager




                     Display General
                                               Create New                                         Browse
                     Properties Form


                    Display Add New
                                                                                                           Select SMIL file.
                     Resource Form


                    Display Resource
                                                 Done                                 Parse XML
                    Properties Form



                                                 Display list of
                                                  resources


                    Delete Resource
Done                                         Delete                             Send                          Send file


          Preview           Preview
                                                                   Save                 Save
                                              Edit
                    Display Resource
                                                           Edit General
                    Properties Form                   Close Properties

                                                                                 Display General
                                                                                 Properties Form

                                                                          Not saved
                                      Done / Cancel


                         Position
                                                                                 Prompt to Save
                                                      Saved
                    Display Resource
                    Positioning Screen

                                                                          No
                                                                                        Yes


                                                                                        Save
                            SMIL Manager
Composer                                 Player                            Inbox/Manage




                   Sent                                     Saved



                                    Recieved




               Display sent      Display recieved      Display saved




Edit SMIL   Edit                                                    Play     Play SMIL


                          Send                      Close




                    Send SMIL
                                                                                                Formatted: Normal
                                                                                                Field Code Changed
                              Manage SMILs
Composer                                     Manager                                Player

                                       Query web server
                                         for new files




                                        Download new
                                        files to SD card




                                       Find SMIL files on
                                            SD card




                                       Display list of files



                                          Click on file

                                                                       Press Play   Play file
Load file into
                 Press Edit
 Composer
                                                               Close

                                          Press Send


                                       Display Send File
                                             form




                              Press
                              Cancel


                                          Press Send



                                            Send file
4.3 Performance Requirements
     User input functionality, such as the stopping of SMIL files or opening the file browser, must be    Formatted: Left, Indent: Left: 0.5"
     responsive and handled in a dedicated thread outside of the playback of SMIL files. The
     management (timing) of the playback of SMIL files must be kept isolated in its own thread, with
     audio and video resources also managed within their own threads. This will help ensure
     playback remains unobstructed on time, starting and stopping media resources at the
     appropriate intervals. Pinging the web server for availability of new SMIL files, and saving
     (generating) SMIL files, must not take more than a couple of seconds to maintain acceptable
     responsiveness.

4.4 Design Constraints                                                                                    Formatted: Heading 2, Left

     As this is a mobile application we must keep in mind the relatively limited resources available.     Formatted: Left, Indent: Left: 0.5"
     We are not able to start many threads at once without a significant performance hit. We must
     be careful that, for instance, the thread querying the web server for new messages does not
     interfere with the responsiveness of the UI or the player. We also must design our user interface
     to accommodate the limited screen resolution (480x320 pixels typical) of mobile screens.

4.5 Software System Attributes                                                                            Formatted: Heading 2, Left

     An Internet connection, either through a cellular data network or WiFi (on supported phones), is     Formatted: Left, Indent: Left: 0.5"
     required for transmitting and receiving SMIL files via the web server. For all other functionality
     of the app, no Internet or cellular connection is required. The app uses resources only when it is
     explicitly opened by the user; it makes no use of any background processes after the app is
     closed.

4.6 Other Requirements                                                                                    Formatted: Heading 2, Left

     The application must notify the user of new SMIL files received by querying a web server that        Formatted: Left, Indent: Left: 0.5"
     we will design. This is a Java servlet that accepts requests from the mobile application to make
     database queries against a MySQL database we will also setup. The database will contain
     references to the packaged SMIL files (which contain the XML file and media files) on the web
     server, and the recipient / sender phone numbers. A thread checking for new files will run in the
     background and, when found, will download them to the SD card. An SD card is required for the
     use of this application.
                                                                                                      Formatted: Heading 1, Left

5 Project Management


5.1 Project Estimation
     This project will take 12 weeks to complete.                                                     Formatted: Indent: First line: 0.5"


                                                                                                      Formatted: Left


5.2 Risk Assessment
     The risks of this project include the lack of knowledge on the subject. Since it is a new        Formatted: Left, Indent: Left: 0.5"
     technology that none have worked with previously there is going to be a learning curve for the
     members of the team. This risk will be offset by the fact that Google has used Java to
     implement its API for the phone. Most of the team is currently knowledgeable on Java
     development.
                                                                                                    Formatted: Heading 1, Left

6 Future System Improvements
    Securing the database and accompanying web application that contains access to users’ sent      Formatted: Left, Indent: Left: 0.5"
    SMIL files would be a good future improvement. Currently there is no method of security
    implemented. Also various functionality could be added, such as fast-forwarding/rewinding the
    playback of SMIL files or a more fleshed out Send/Receive function.
                                                                            Formatted: Heading 1, Left

7 Appendix


7.1 Task Partition
Name                 Task

Jason Daniels        Tabbed UI
                     Audio playback
                     Video playback
                     SMIL Player
Ben Bedinghaus       Text file reading
                     Web server application and database for send/receive
                     ManagerFile browser
Ryan Ware            XML pParser & generator
                     XML Generator
                     Image displaying
                     SMIL Composer
                                                                            Formatted: Left
7.2 Work Schedule
                    Field Code Changed
7.3 Meeting Agenda & Minutes                                                                         Formatted: Heading 2, Left




                                         Meeting Agenda

   Date: 1/12/2010                                     Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                  Timekeeper: Jason Daniels
   Location: ST 250                                    Minute Taker: Ryan Ware



1. Objective
   Decide on first steps for project – team member roles, choice of language and framework to use,
   and first tasks.

2. Status (allocated time: 0 minutes)
   (No action items to report on)

3. Discussion (allocated time: 25 minutes)
   3.1. Team member skills or specialties
   3.2. Team member roles
   3.3. What language/framework and IDE to use for project 1?
   3.4. What can we accomplish in the first week?

4. Wrap Up (allocated time: 5 minutes)
   4.1. Assign first action items


                                         Meeting Minutes

   Date: 1/12/2010                                     Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                  Timekeeper: Jason Daniels
   Location: ST 250                                    Minute Taker: Ryan Ware



5. Objective
   Decide on first steps for project – team member roles, choice of language and framework to use,
   and first tasks.

6. Status
   (No action items to report on)
7. Discussion
   7.1. All team members are proficient with Java. Ben has experience with C# and Microsoft
        development products. Jason has experience with iPhone development. Ryan has J2EE and
        JDBC experience. Ryan and Jason are familiar with the Eclipse IDE. No one has experience with
        J2ME or Android development.
   7.2. All team members will be implementers and testers of the code. We all agree these roles come
        with any development position. In addition Ben Bedinghaus will be the Team Leader, Jason
        Daniels will be the Configuration Manager, and Ryan Ware will be the Liaison.
   7.3. What language/framework and IDE to use for project 1?
        Proposals: 1) J2ME with Eclipse 2) Google Android with Eclipse
        Resolution: We chose the Google Android SDK. None of us are familiar with it, but feel it will
        provide better tools than J2ME for making a quality application, and it shouldn’t be difficult to
        pick up with our existing Java knowledge. We will also use the Eclipse IDE and the
        corresponding Android Development Tools (ADT) plugin.
   7.4. In the first week we can set up our development environments, set up a Subversion repository,
        establish a good method of communication, and become familiar with the Android API.

8. Wrap Up
   8.1. Action items
       8.1.1.For: Ben, Jason, Ryan
             Set up development environments (Android SDK, Eclipse, ADT plugin, Subclipse plugin).
       8.1.2.For: Ben, Jason, Ryan
             Become familiar with the Android API. Try tutorials, read documentation, etc.
       8.1.3.For: Ryan
             Acquire a Subversion server for use with Subclipse plugin.
       8.1.4.For: Ben
             Send Google Wave invites to Ryan and Jason for use as primary communication tool.


                                          Meeting Agenda

   Date: 1/19/2010                                       Primary facilitator: Ben Bedinghaus
   Time: 8:00-9:00 PM                                    Timekeeper: Jason Daniels
   Location: ST 250                                      Minute Taker: Ryan Ware



9. Objective
   Correct any development environment setup issues, preliminary interface design, discuss additional
   research analysis tasks.

10. Status (allocated time: 10 minutes)
    10.1.       Everyone report on status of development environment setup.
    10.2.       Ryan report on status of Subversion server.
    10.3.       Ben report on status of Google Wave invites.

11. Discussion (allocated time: 45 minutes)
    11.1.       How do we want to design the interface?
    11.2.       What additional technical research needs to be done?

12. Wrap Up (allocated time: 5 minutes)
    12.1.      Assign technical research tasks.
    12.2.      Assign requirements/design document tasks based upon class lecture.


                                          Meeting Minutes

   Date: 1/19/2010                                        Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                     Timekeeper: Jason Daniels
   Location: ST 250                                       Minute Taker: Ryan Ware



13. Objective
    Correct any development environment setup issues, preliminary interface design, discuss additional
    research analysis tasks.

14. Status
    14.1.       Everyone set up their Eclipse Android development environment without issues.
    14.2.       Ryan set up the Google Code Subversion server and everyone has connected to it
         successfully.
    14.3.       Ben sent out Google Wave invites and everyone has joined and begun using it.

15. Discussion
    15.1.        Preliminary interface design decisions are to use a tabbed view for the home screen.
         Three tabs will be Player, Editor, and Inbox. Upon loading the application it will default to one
         of the tabbed views, such as the Player view, which allows for the playback of SMIL files loaded
         from a built-in file browser. The Editor tab allows for the creation of new SMIL files or the
         editing of existing files, previewing files, and saving them to the file system. The Inbox tab
         allows you to view SMIL files that others have sent to your phone, as well as select files to send
         to others’ phones. The rough structure of each view’s interface was outlined to give us a
         general idea of what we’re shooting for, but they are subject to change as deemed necessary.
    15.2.        We have determined that additional technical research needs to be done on the
         following topics: general Android API fundamentals, multithreading techniques, MMS or other
         methods of transferring multimedia files across phones, parsing and generating XML files, and
         playing video files within Android. These research tasks will be divided among us, and then
         shared with the team so we all become knowledgeable in these areas.

16. Wrap Up
    16.1.        Action items
        16.1.1. For: Ryan
              Research Android XML parsing and teach Ben & Jason. Develop a simple parser.
        16.1.2. For: Jason
              Research Android API fundamentals and teach Ryan & Ben.
        16.1.3. For: Ben
              Research Android multithreading techniques and teach Jason & Ryan.
        16.1.4. For: Ben
              Install Microsoft Project on laptop.


                                          Meeting Agenda

   Date: 1/26/2010                                        Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                     Timekeeper: Jason Daniels
   Location: ST 250                                       Minute Taker: Ryan Ware



17. Objective
    Review results of technical research tasks, continue interface design discussions, break up first
    development tasks.

18. Status (allocated time: 10 minutes)
    18.1.        Ryan report on XML parsing research and progress of XML parser prototype.
    18.2.        Jason report on Android API research.
    18.3.        Ben report on multithreading research.

19. Discussion (allocated time: 15 minutes)
    19.1.       What development tasks can we divide up and work on this week?
    19.2.       Discuss topic of class lecture and any resulting tasks (possible UML diagram).

20. Wrap Up (allocated time: 5 minutes)
    20.1.      Assign development tasks.
    20.2.      Assign requirements/design document tasks based upon class lecture.


                                          Meeting Minutes
   Date: 1/26/2010                                        Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                     Timekeeper: Jason Daniels
   Location: ST 250                                       Minute Taker: Ryan Ware



21. Objective
    Review results of technical research tasks, continue interface design discussions, break up first
    development tasks.

22. Status
    22.1.       Ryan was able to construct a working XML parser prototype.
    22.2.       Jason reported on Android API research.
    22.3.       Ben reported on Java multithreading research.

23. Discussion
    23.1.        We’ve decided to investigate how to display the various media types in Android for use
         in our Player (text, image, audio, and video). We have divided up the research/preliminary
         development tasks as outlined in our action items in section 4.
    23.2.        We will begin designing use case diagrams at our next team meeting this week, as well
         as update the project plan.

24. Wrap Up
    24.1.        Action items
        24.1.1. For: Ryan
              Finish prototype of XML parser, develop prototype of image displayer.
        24.1.2. For: Jason
              Develop tabbed view layout and prototype audio player.
        24.1.3. For: Ben
              Develop prototype text file reader and video player.
        24.1.4. For: Everyone
              Research methods of timing playback of media files for Player.


                                          Meeting Agenda

   Date: 2/02/2010                                        Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                     Timekeeper: Jason Daniels
   Location: ST 250                                       Minute Taker: Ryan Ware
25. Objective
    Review development tasks and project plan progress, discuss use cases and UML diagram
    construction.

26. Status (allocated time: 10 minutes)
    26.1.        Ryan report on status of XML parser and how to display image.
    26.2.        Jason report on tabbed view development, how to play audio file.
    26.3.        Ben report on text file reader and how to play video file.

27. Discussion (allocated time: 15 minutes)
    27.1.       What methods of timing the playback of media objects are available?
    27.2.       Discuss getting started on use cases and a UML diagram.
    27.3.       Do we need to alter our project plan?

28. Wrap Up (allocated time: 5 minutes)
    28.1.      Determine when we can work on use cases and UML diagram.


                                         Meeting Minutes

   Date: 2/02/2010                                       Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                    Timekeeper: Jason Daniels
   Location: ST 250                                      Minute Taker: Ryan Ware



29. Objective
    Review development tasks and project plan progress, discuss use cases and UML diagram
    construction.

30. Status
    30.1.       Ryan was unable to fix PriorityQueue sorting bug in the XML parser, will work on this
         further at a later date. Ryan was able to successfully display a JPG image in Android.
    30.2.       Jason created a tabbed view in Android for us to use as the shell of our app. Jason was
         unable to test audio playback yet.
    30.3.       Ben researched reading text files in Android, but was unable to successfully play a video
         yet.

31. Discussion
    31.1.       We discussed methods of possibly timing the playback of media files for our Player. We
         did not see any code examples, but theoretically speaking we have decided to use a thread that
         checks the two PriorityQueues within the SmilFile object every second, incrementing its count
         since the thread began. If the count matches the start or end time of any SmilResource object
         in the queues, we will begin or stop the playback of that media object. Playback of each object
         should be handled in a separate thread. The exact mechanics of this have yet to be determined.
    31.2.        We created a rough sketch of our use case diagram, using three actors that use the
         three systems within our app – Player, Composer, and Inbox/File Manager.
    31.3.        We’ve decided the next step to take is to work on the design document, more
         specifically the activity diagram (after the first draft of the use case diagram is done). We will
         likely be working on this together at our next team meeting.

32. Wrap Up
    32.1.       Action items
        32.1.1. For: Ryan
              Begin constructing design document. Continue work on XML parser.
        32.1.2. For: Jason
              Construct first draft of use case diagram. Develop prototype audio player.
        32.1.3. For: Ben
              Develop prototype video player.


                                          Meeting Agenda

   Date: 2/09/2010                                        Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                     Timekeeper: Jason Daniels
   Location: ST 250                                       Minute Taker: Ryan Ware



33. Objective
    Review use case diagrams and activity diagrams. Make modifications as necessary. Report on
    development progress (audio and video playback). Determine next steps.

34. Status (allocated time: 10 minutes)
    34.1.        Ryan show Player activity diagram and beginnings of SRS Word document.
    34.2.        Jason show use case diagrams and Inbox activity diagram. Report on how to play audio
         files.
    34.3.        Ben report on how to play video files.

35. Discussion (allocated time: 15 minutes)
    35.1.       Review activity and use case diagrams. Are modifications necessary at this point? If so,
         determine who is responsible for making changes.
    35.2.       Review progress against Project Plan. Are we on track? Make any changes as needed.
    35.3.      Determine next steps. Should we dive into development, or do we need to work more
         on documentation first?

36. Wrap Up (allocated time: 5 minutes)
    36.1.      Based on progress of our use case and activity diagrams, and SRS document, we need to
         determine what the best next steps are (development efforts or more documentation).


                                          Meeting Minutes

   Date: 2/14/2010 (change due to class cancellation)     Primary facilitator: Ryan Ware
   Time: 2:00-4:00 PM                                     Timekeeper: Ben Bedinghaus
   Location: Ryan’s home                                  Minute Taker: Jason Daniels



37. Objective
    Review use case diagrams and activity diagrams. Make modifications as necessary. Report on
    development progress (audio and video playback). Determine next steps.

38. Status
    38.1.        Ryan finished the Player activity diagram and template for SRS document. Both are
         shared online.
    38.2.        Jason was able to successfully play audio files, with controls. Also finished the Manager
         activity diagram and it is shared online. Use case diagrams are not complete.
    38.3.        Ben did not make progress on playing video files.

39. Discussion
    39.1.       We reviewed our activity diagrams and decided Ryan will add swim lanes and
         consolidate the diagrams into our SRS document. Ryan will also be creating the use cases and
         adding to the SRS document.
    39.2.       We divided up the SRS document by section and determined who is responsible for
         each. Jason will handle External Interface Requirements, Communication Records, and
         Software Configuration Management. Ben will handle Introduction, Overall Description, and
         Project Management. Ryan will handle Functional Requirements, Meeting Agenda & Minutes,
         Performance Requirements, Design Constraints, and Software System Attributes.
    39.3.       We discussed development goals for our prototype, first draft versions of the Player and
         Composer. We talked about what the best method of structuring the playback of items would
         be. We will discuss this further in class during Tuesday’s meeting.

40. Wrap Up
    40.1.       Action items (next meeting is in 2 days, on Tuesday. Further action items to be assigned
         then)
        40.1.1. For: All
              Brainstorm methods of structuring our media playback. We will discuss these options on
              Tuesday and begin prototyping this week.
        40.1.2. For: Ryan
              Update activity diagrams / SRS document.
        40.1.3. For: Ben
              Continue work on video playback.


                                          Meeting Agenda

   Date: 2/16/2010                                       Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                    Timekeeper: Jason Daniels
   Location: ST 250                                      Minute Taker: Ryan Ware



41. Objective
    Determine the best structure for our media playback piece so we can begin prototyping. Discuss any
    updates we have made to our SRS document, and those we should make sooner versus later.

42. Status (allocated time: 10 minutes)
    42.1.        Everyone report on how they would structure the media playback portion.
    42.2.        Ryan report on updated activity diagrams and use case diagrams.
    42.3.        Ben report on how to play video files.

43. Discussion (allocated time: 15 minutes)
    43.1.       Discuss media playback options. How should the objects be structured? What is the best
         method of handling this task in Android?
    43.2.       Discuss which sections of the SRS document we can finish this week.

44. Wrap Up (allocated time: 5 minutes)
    44.1.      Assign prototyping tasks for Player.
    44.2.      Assign first SRS sections to complete.


                                         Meeting Minutes

   Date: 2/21/2010 (change due to class cancellation)    Primary facilitator: Ryan Ware
   Time: 2:00-5:00 PM                                    Timekeeper: Ben Bedinghaus
   Location: Ryan’s home                                 Minute Taker: Jason Daniels
45. Objective
    Determine the best structure for our media playback piece so we can begin prototyping. Discuss any
    updates we have made to our SRS document, and those we should make sooner versus later.

46. Status
    46.1.      Discussed structure of media playback briefly, but no one felt strongly about a particular
         implementation.
    46.2.      Ryan modified the activity diagrams and will place in SRS document.
    46.3.      No progress on video playback. Task has been reassigned (see Discussion).

47. Discussion
    47.1.       We did not discuss the structure of media playback for long, as we had planned. Instead
         we focused on other topics.
    47.2.       We reviewed changes to the SRS document – such as Jason’s addition of the External
         Interface Requirements. Discussed which changes will be made next – Ryan will add activity and
         use case diagrams, meeting minutes & agendas next. Document is on Google Code, discussed
         method handling changes to the document.
    47.3.       We broke up the development tasks. Jason is responsible for the Player portion, which
         makes use of the already-developed XML parser, and times media object playback. Ryan is
         responsible for the Composer portion, which includes the XML generator and allows for
         creation of files. Ben is responsible for the Manager portion, which includes a file browser and a
         web server for handling transmission of files between devices. We believe this to be the best
         way of splitting up the development work. When we meet we have the opportunity to get
         input and help from other team members.

48. Wrap Up
    48.1.        Action items
        48.1.1. For: Jason
              Begin development of first draft of Player, which can play and stop each resource type one
              at a time.
        48.1.2. For: Ryan
              Begin development of first draft of Composer, which utilizes an XML generator to translate
              a hard-coded SmilDataSet object into a valid SMIL XML document.
        48.1.3. For: Ben
              Begin development of first draft of Manager, which will display a list of files on the SD card
              and return the selected file name.
        48.1.4. For: All
              Update sections of SRS document that we are responsible for.


                                           Meeting Agenda
   Date: 2/23/2010                                    Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                 Timekeeper: Jason Daniels
   Location: ST 250                                   Minute Taker: Ryan Ware



49. Objective
    Review preliminary development progress and discuss any issues. Review any updates to SRS
    document. Ask professor questions about SRS document sections. Ensure everyone is on track for
    first draft of their portion by next meeting.

50. Status (allocated time: 10 minutes)
    50.1.        Jason report on status of Player first draft.
    50.2.        Ryan report on status of Composer first draft.
    50.3.        Ben report on status of Manager first draft.
    50.4.        Everyone report on any updates made to SRS document.

51. Discussion (allocated time: 15 minutes)
    51.1.       Discuss development progress.
    51.2.       Discuss any updates to SRS document.
    51.3.       Ask professor any questions we have about SRS document sections.

52. Wrap Up (allocated time: 5 minutes)
    52.1.      Continue with development tasks.
    52.2.      Continue with SRS updates.
    52.2.                                                                                            Formatted: Outline numbered + Level: 2 +
                                                                                                     Numbering Style: 1, 2, 3, … + Start at: 1 +
                                                                                                     Alignment: Left + Aligned at: 0.25" + Indent
                                                                                                     at: 0.55"
                                       Meeting Minutes

   Date: 2/23/2010                                    Primary facilitator: Ben Bedinghaus
   Time: 8:00-8:30 PM                                 Timekeeper: Jason Daniels
   Location: ST 250                                   Minute Taker: Ryan Ware



53. Objective
    Review preliminary development progress and discuss any issues. Review any updates to SRS
    document. Ask professor questions about SRS document sections. Ensure everyone is on track for
    first draft of their portion by next meeting.

54. Status
    54.1.       Jason has enabled video playback, although the Android emulator does not play videos
         back frame-by-frame.
    54.2.       Ben added Introduction and Overall Description to SRS.
    54.3.       Jason updated Communication Records in SRS.
    54.4.       Ryan added use case & activity diagrams, meeting agendas & minutes to SRS.

55. Discussion
    55.1.        Jason showed Ben and Ryan the basic layout of our Activities and Intents, and how we
         can utilize them for the three pieces of our app (Player, Composer and, Manager).
    55.2.        Ryan asked professor for explanation of Software System Attributes and Overall Activity
         Diagram sections of SRS. Ryan will work on completing these sections next.
    55.3.        No one has made significant development progress yet.

56. Wrap Up
    56.1.        Action items
        56.1.1. For: Jason
              Continue development of first draft of Player, which can play and stop each resource type
              one at a time.
        56.1.2. For: Ryan
              Continue development of first draft of Composer, which utilizes an XML generator to
              translate a hard-coded SmilDataSet object into a valid SMIL XML document.
        56.1.3. For: Ben
              Continue development of first draft of Manager, which will display a list of files on the SD
              card and return the selected file name.
        56.1.4. Ben
              Update Project Plan and send to professor.
        56.1.5. For: All
              Update sections of SRS document that we are responsible for.
                                                                                                             Formatted: Left


                                          Meeting Agenda

   Date: 3/02/2010                                        Primary facilitator: Ben Bedinghaus
   Time: 8:30-9:00 PM                                     Timekeeper: Jason Daniels
   Location: ST 250                                       Minute Taker: Ryan Ware



57. Objective
    Review progress of first draft prototypes of Player, Composer, and Manager and determine goals for
    2nd draft prototypes. Review additions to SRS document. Review progress against Project Plan.
58. Status (allocated time: 10 minutes)
    58.1.        Jason report on status of Player first draft.
    58.2.        Ryan report on status of Composer first draft.
    58.3.        Ben report on status of Manager first draft.
    58.4.        Everyone report on any updates made to SRS document.

59. Discussion (allocated time: 15 minutes)
    59.1.       Discuss development progress. Any issues? Is everyone complete?
    59.2.       Discuss any updates to SRS document.
    59.3.       Determine the next goals for our 2nd draft prototypes.

60. Wrap Up (allocated time: 5 minutes)
    60.1.      Assign new development goals.
    60.2.      Continue with SRS updates.
                                                                                  Formatted: Left
7.4 Communication Records                                                                                            Formatted: Heading 2, Left




Android & Subversion
6 messages



Ryan Ware <rware88@gmail.com>                                                        Tue, Jan 12, 2010 at 11:41 PM

To: bbed04@gmail.com, Jason Daniels <jasonbdaniels@gmail.com>


  I got Android working in Eclipse, it's not hard just follow these instructions:
  http://developer.android.com/sdk/index.html

  I also set up our project on Google Code so we can use their Subversion server. The project is at
  http://code.google.com/p/mobile-smil/

  To get Subclipse (the Subversion Eclipse plugin) working, add it like the ADT (Android) but use
  http://subclipse.tigris.org/update_1.6.x as the location URL.

  The repository URL is https://mobile-smil.googlecode.com/svn

  Let me know if you guys have any problems.




Ben Bedinghaus <bbed04@gmail.com>                                                     Wed, Jan 13, 2010 at 1:36 PM

To: Ryan Ware <rware88@gmail.com>

Cc: Jason Daniels <jasonbdaniels@gmail.com>


  Thanks for the info. Should I get eclipse for the EE or the regular java developers version? Does it even
  matter? Also did you guys get the invite to wave yet? My other friend i sent it to over the weekend had it last
  night.

  [Quoted text hidden]


  --
  Benjamin Bedinghaus
  bbed04@gmail.com
Ben Bedinghaus <bbed04@gmail.com>                                                       Wed, Jan 13, 2010 at 1:44 PM

To: Ryan Ware <rware88@gmail.com>

Cc: Jason Daniels <jasonbdaniels@gmail.com>


  I created a new wave, with the info Ryan sent, for when you both end up getting the invite. I will add you both
  to the wave so you can see it when you get the invite and activate it. Shoot me an email when you get wave
  so I can add you as quickly as possible. We can also post documents in wave so we can put some of the
  documents we need right there. I played around with it some last night with another friend and it seems like
  this is a great collaboration tool. It also tracks the history of the wave to see all of the changes made. This will
  be extremely valuable. Also we can use wave as a chat and other things too.

  I also added a schedule wave.

  Ben

  [Quoted text hidden]




Jason Daniels <jasonbdaniels@gmail.com>                                                Wed, Jan 13, 2010 at 11:25 PM

To: Ryan Ware <rware88@gmail.com>

Cc: bbed04@gmail.com


  Whats the password for the repository?




Ryan Ware <rware88@gmail.com>                                                            Thu, Jan 14, 2010 at 8:42 AM

To: Jason Daniels <jasonbdaniels@gmail.com>

Cc: bbed04@gmail.com


  If I click on the Source tab of our Google Code project, it lets me generate a password. I don't know if a
  password I generate will work for your gmail account name, so see if you're able to generate one.

  [Quoted text hidden]




Jason Daniels <jasonbdaniels@gmail.com>                                                 Thu, Jan 14, 2010 at 10:20 AM
To: Ryan Ware <rware88@gmail.com>


 I finally figured it out, the user name is your gmail user name, and the password is the generated one.

 Also if you haven't noticed already I've imported the hello world app to see how it was all done. Let me know
 you guys can checkout alright and run.




CSC 440 Team6: Meeting Minutes 2
1 message

Ryan Ware <rware88@gmail.com>                                              Wed, Jan 20, 2010 at 2:13 PM
To: haow1@nku.edu
Cc: Ben Bedinghaus <bbed04@gmail.com>, Jason Daniels <jasonbdaniels@gmail.com>

 Attached are team 6 meeting minutes from 1/19.

 Thanks,
 Ryan Ware



      1.19 Meeting Minutes.docx
      14K

CSC 440 Team6: Project Plan
1 message



Ben Bedinghaus <bbed04@gmail.com>                                                    Sun, Jan 24, 2010 at 5:23 PM

To: haow1@nku.edu, Jason Daniels <jasonbdaniels@gmail.com>, Ryan Ware <rware88@gmail.com>


 Here is the plan.

 --
 Benjamin Bedinghaus
 bbed04@gmail.com




      mobile_smil.mpp
      190K
CSC 440 Team6: Meeting Agenda 3
1 message

Ryan Ware <rware88@gmail.com>                                               Sun, Jan 24, 2010 at 5:48 PM
To: haow1@nku.edu
Cc: Jason Daniels <jasonbdaniels@gmail.com>, Ben Bedinghaus <bbed04@gmail.com>

  Attached is the team 6 meeting agenda for 1/26.

  Thanks,
  Ryan Ware



       1.26 Meeting Agenda.docx
       13K

CSC 440 Team6: Meeting Minutes 3
1 message

Ryan Ware <rware88@gmail.com>                                              Tue, Jan 26, 2010 at 10:50 PM
To: haow1@nku.edu
Cc: Ben Bedinghaus <bbed04@gmail.com>, Jason Daniels <jasonbdaniels@gmail.com>

  Attached are team 6 meeting minutes from 1/26.

  Thanks,
  Ryan Ware



       1.26 Meeting Minutes.docx
       13K



CSC 440 Team6: Meeting Agenda 4
1 message

Ryan Ware <rware88@gmail.com>                                               Sun, Jan 31, 2010 at 9:14 PM
To: haow1@nku.edu
Cc: Jason Daniels <jasonbdaniels@gmail.com>, Ben Bedinghaus <bbed04@gmail.com>

  Attached is team 6 meeting agenda for 2/02.

  Thanks,
  Ryan Ware



       2.02 Meeting Agenda.docx
       13K
CSC 440 Team6: Meeting Minutes 4
1 message

Ryan Ware <rware88@gmail.com>                                               Wed, Feb 3, 2010 at 3:18 PM
To: haow1@nku.edu
Cc: Ben Bedinghaus <bbed04@gmail.com>, Jason Daniels <jasonbdaniels@gmail.com>

  Attached are team 6 meeting minutes for 2/02.

  Thanks,
  Ryan Ware



       2.02 Meeting Minutes.docx
       14K

CSC 440 Team6: Meeting Agenda 5
1 message

Ryan Ware <rware88@gmail.com>                                                Sun, Feb 7, 2010 at 4:40 PM
To: haow1@nku.edu
Cc: Jason Daniels <jasonbdaniels@gmail.com>, Ben Bedinghaus <bbed04@gmail.com>

  Attached is team 6 meeting agenda for 2/09.

  Thanks,
  Ryan Ware



       2.09 Meeting Agenda.docx
       13K

Player Activity Diagram.vsd
1 message



rware88@gmail.com <rware88@gmail.com>                                        Sun, Feb 7, 2010 at 11:05 PM

To: jasonbdaniels@gmail.com


               I've shared Player Activity Diagram.vsd

  Message from rware88@gmail.com:

  Let's all put our activity diagrams and other documents on Google Docs
     Click to open:

    Player Activity Diagram.vsd

     Google Docs makes it easy to create, store and share online documents, spreadsheets and
     presentations.




    CSC 440 Team6: Meeting Minutes 5
    1 message

    Ryan Ware <rware88@gmail.com>                                             Mon, Feb 15, 2010 at 11:32 AM
    To: haow1@nku.edu
    Cc: Jason Daniels <jasonbdaniels@gmail.com>, Ben Bedinghaus <bbed04@gmail.com>

     Attached are team 6 meeting minutes from 2/14 (rescheduled on account of class cancellation).

     Thanks,
     Ryan Ware



          2.09 Meeting Minutes.docx
          14K

    CSC 440 Team6: Meeting Agenda 6
    1 message

    Ryan Ware <rware88@gmail.com>                                             Mon, Feb 15, 2010 at 11:33 AM
    To: haow1@nku.edu
    Cc: Jason Daniels <jasonbdaniels@gmail.com>, Ben Bedinghaus <bbed04@gmail.com>

     Attached is team 6 meeting agenda for 2/16.

     Thanks,
     Ryan Ware



          2.16 Meeting Agenda.docx
          13K
     Android Examples
     1 message

     Jason Daniels <danielsj3@nku.edu>                                              Sun, Feb 21, 2010 at 9:10 PM
     To: Ryan Ware <rware88@gmail.com>, bbed04@gmail.com
    Check out the API demos that are in the Android SDK folder. There are tons of sample applications that
    will help for just about any application.

    The path for the demos should be <You Android SDK path>\platforms\<choose any OS
    folder>\samples\ApiDemos. Just create a new Android project from that source path.


    Jason



  SRS on Google code issues..
  1 message

  Ryan Ware <rware88@gmail.com>                                         Sun, Feb 21, 2010 at 10:44 PM
  To: Jason Daniels <jasonbdaniels@gmail.com>, Ben Bedinghaus <bbed04@gmail.com>

    So I tried updating the SRS document on Google Code but then when I pulled it back down to make sure it
    worked, it was an old version... I don't know what's up with that, but to prevent future issues I suggest we
    not overwrite the existing SRS document anymore and instead upload a new version any time we make
    changes.

    For instance if you look in our downloads section now you'll see a "Software Reqs Specification 0.4" which
    is the latest one I uploaded. The next person to change it should rename their file to 0.5 before uploading,
    and so on. This version corresponds to the version you add to the Revision History table inside the
    document. It also doesn't hurt to add in the summary field what you updated in the document (again like in
    the Revision History table).

    But we still need to notify others when we're editing the document. So still make a note in the summary
    when you 'check it out' so to speak.

    Let me know if this won't work out for some reason.


SRS Document
2 messages



Jason Daniels <danielsj3@nku.edu>                                                   Mon, Feb 22, 2010 at 10:43 AM

To: bbed04@gmail.com, Ryan Ware <rware88@gmail.com>


  I'm still unable to change my user-name when editing the SRS document, it still says its Ryan committing the
  changes.

  Ben, are you able to have MS Word properly track your changes?

  Jason
Ben Bedinghaus <bbed04@gmail.com>                                                  Tue, Feb 23, 2010 at 1:00 AM

To: Jason Daniels <danielsj3@nku.edu>


  All of my changes were documented but I didnt see any other changes from other people.

  [Quoted text hidden]


  --
  Benjamin Bedinghaus
  bbed04@gmail.com



CSC-440-001M-2010-030: Updated schedule
1 message

haow1@nku.edu <haow1@nku.edu>                                                    Wed, Feb 24, 2010 at 9:58 PM
To: haow1@nku.edu

  Hi all,



  I posted the updated schedule on the blackboard. We will have the midterm exam on 03/16. Also, each team
  needs to demonstrate the prototype system to me on 03/16. The SRS document will be due on 03/21. Project 1
  and presentation slides will be due on 03/30. Project 1 presentation will be on 04/06.



  Thanks!



  Wei

CSC-440-001M-2010-030: Subversion repository
1 message



haow1@nku.edu <haow1@nku.edu>                                                    Thu, Feb 25, 2010 at 11:25 AM

To: haow1@nku.edu


  Hi all,
  Dennis Heher, graduate assistant, has created Subversion repository on kosh (kosh.nku.edu) machine for you.
  The branch name for team x is csc440-teamx-2010s, where 1<=x<=7. Dennis also wrote SVN and Tortoise
  Howto documents. I have already posted the documents on the blackboard. If your team wants to use the
  subversion repository on kosh to do source code version control for your project, please read these two
  Howto documents. If you have any question, please email Dennis at heherd1@mymail.nku.edu and CC your
  email to me.




  Some teams have not emailed me the updated MS project files yet. Please email me your updated MS project
  file ASAP. Each team needs to email me a meeting agenda, a meeting minutes, and an updated MS project file
  every week.




  Thanks!




  Wei



CSC 440 Team6: Meeting Agenda 8
1 message

Ryan Ware <rware88@gmail.com>                                               Mon, Mar 1, 2010 at 9:26 PM
To: haow1@nku.edu
Cc: Jason Daniels <jasonbdaniels@gmail.com>, Ben Bedinghaus <bbed04@gmail.com>

  Attached is team 6 meeting agenda 8 for 3/02.

  Thanks



        3.02 Meeting Agenda.docx                                                                                Formatted: Font: (Default) Times New
        13K                                                                                                     Roman, 12 pt, No underline, Font color: Blue


CSC 440 Team6: Meeting Minutes 8
1 message

Ryan Ware <rware88@gmail.com>                                                Fri, Mar 5, 2010 at 2:18 PM
To: Wei Hao <haow1@nku.edu>
Cc: Jason Daniels <jasonbdaniels@gmail.com>, Ben Bedinghaus <bbed04@gmail.com>

  Forgot to send these out earlier... attached are team 6 meeting minutes from 3/02.

  Thanks,
 Ryan Ware



      3.02 Meeting Minutes.docx                                                                               Formatted: Font: (Default) Times New
      15K                                                                                                     Roman, 12 pt, No underline, Font color: Blue


CSC 440 Team6: Updated Microsoft Project
1 message



Ben Bedinghaus <bbed04@gmail.com>                                              Tue, Mar 16, 2010 at 6:38 PM

To: haow1@nku.edu

Cc: Ryan Ware <rware88@gmail.com>, Jason Daniels <jasonbdaniels@gmail.com>


 Here is the updated Microsoft Project File

 --
 Benjamin Bedinghaus
 bbed04@gmail.com




      mobile_smil.mpp
                                                                                                              Formatted: No underline, Font color: Blue
      185K



Using Java Servlet
2 messages



Benjamin Bedinghaus <bbed04@gmail.com>                                        Wed, Mar 17, 2010 at 1:24 PM

To: rware88@gmail.com, jasonbdaniels@gmail.com


 After looking for a good example of how I want to do things. I have found an example of a java
 servlet that I am going to use to transfer all information between the server and the phone. This
 one has an example of transferring a png file. I will be able to do this kind of thing for both database
 and files. Take a look and let me know what you think.
  http://developerlife.com/tutorials/?p=288




  Ben



Ryan Ware <rware88@gmail.com>                                                          Wed, Mar 17, 2010 at 2:20 PM

To: Benjamin Bedinghaus <bbed04@gmail.com>

Cc: jasonbdaniels@gmail.com


  Looks like this would work for uploading or downloading the files, but you'll also need to handle other
  requests like "return list of all new files for this phone" or whatever. If there is a way of determining what type
  of request is being made then this will work. If not then you might try something like Java RMI where you can
  define remote service methods to invoke from the phone.

  [Quoted text hidden]




Meeting Sunday
4 messages



Jason Daniels <danielsj3@nku.edu>                                                        Fri, Mar 19, 2010 at 1:29 PM

To: bbed04@gmail.com, Ryan Ware <rware88@gmail.com>


  Ben, Ryan and I were talking about meeting on Saturday and Sunday this weekend. Would you be up for this?

  I'm thinking for Saturday meet at normal time, 2:00 PM, let me know what you guys think.

  Jason




Benjamin Bedinghaus <bbed04@gmail.com>                                                   Fri, Mar 19, 2010 at 1:49 PM

To: Jason Daniels <danielsj3@nku.edu>, Ryan Ware <rware88@gmail.com>
  I won't be able to meet until later. I have to work.



  From: Jason Daniels <danielsj3@nku.edu>
  Sent: Friday, March 19, 2010 1:29 PM
  To: bbed04@gmail.com; Ryan Ware <rware88@gmail.com>
  Subject: Meeting Sunday

  Ben, Ryan and I were talking about meeting on Saturday and Sunday this weekend. Would you be up for this?

  I'm thinking for Saturday meet at normal time, 2:00 PM, let me know what you guys think.

  Jason




Ryan Ware <rware88@gmail.com>                                                       Fri, Mar 19, 2010 at 1:53 PM

To: Benjamin Bedinghaus <bbed04@gmail.com>

Cc: Jason Daniels <danielsj3@nku.edu>


  What time could you meet? Our SRS document & review are due on Sunday.. so we're really running low on
  time.

  [Quoted text hidden]




Benjamin Bedinghaus <bbed04@gmail.com>                                              Fri, Mar 19, 2010 at 9:30 PM

To: Ryan Ware <rware88@gmail.com>

Cc: Jason Daniels <danielsj3@nku.edu>


  I can meet around 4-430.




  From: Ryan Ware [mailto:rware88@gmail.com]
  Sent: Friday, March 19, 2010 1:54 PM
  To: Benjamin Bedinghaus
  Cc: Jason Daniels
  Subject: Re: Meeting Sunday

                                                                                                                   Formatted: Left
7.5 Software Configuration Management
 The components of the software configuration management (scm) consisted of Microsofts’s Word to           Formatted: Left
track changes to the SRS document, Google Code to provide a central location for source code and other
electronic files, and also scm consisted of Eclipse coupled with the plugin subclipse to provide SVN
control. The process of the scm primarily consisted of synchronizing local copies of source with the
repository. Additional functionality included subclipse’s ability to compare conflicts between local and
repository source files. Google code also provided functionality to comment on changes commited to
the repository.

In more detail here is an example scenario of updating and commiting source code changes to the
repository.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:10/17/2012
language:Latin
pages:54