Meeting Minutes
CSE 449 Palm Pilot Group 
9/23/99


Team Standards            
I.    Roles 

    a.  Leader - Jason Campbell 
            1. coordinates and runs meetings 
            2. writes up documents 
    b.  Communicator - Josh Colvin 
            1. responsible for all communications with 
                the sponsor 
            2. coordinates meetings with sponsor 
    c.  Recorder - Jason Sherrill 
            1. takes meeting notes 
            2. Email out meeting minutes 
            3. maintains team notebook 
    d.  Facilitator - Ben Tobin 
            1. resolves disputes 
            2. writes up documents with Leader 

II.    Meetings 

    a.  Weekly Time - Thursdays at 4:00 PM 
    b.  Standard Agenda 
            1. discuss progress of each person 
                    problems encountered 
                    solutions found 
            2. present new ideas, brainstorming 
            3. discuss ideas and proposed changes 
            4. determine expected deliverables by next meeting 
    c.  Decision Strategy 
            1. try to come to a unanimous agreement 
            2. if not, Email sponsor to get his input 
    d.  Minutes - sent by Email by day before next meeting 
    e.  Attendance Rule - any missed meeting with out excuse will 
            be discussed and consequences will be determined then 
    f.  Conflict Resolution Strategy - facilitator or somebody else 
            not involved in conflict will mediate 

III.    Document Standards 

    a.  Word Processor Version - Microsoft Word 
    b.  Coordination - Leader and Facilitator will take turns 
    c.  Version Control - RCS 
    d.  Format - Times New Roman, 12 pt. font, 
            bottom center page numbering, structure etc. to be 
            decided on first main document 
    e.  Review Process - Individual components should be done 
            by the team meeting before the document is due 

IV.    Self Evaluation Method 

    a.  At each meeting 
    b.  Informal discussions 

V.    Standards for Behavior / Cooperation 

    a.  Anybody can suggest a design change.  Team consent 
         is always required 
    b.  No side talking, otherwise informal meetings




 
Meeting Minutes
PalmReaders
12/2/99



1.  Discussed the upcoming presentation

2.  Talked about the digital pictures we took

3.  Discussed changes to our web page

4.  Decided to Email our sponsor about our proposal since we haven't recieved a reply yet

5.  Decided to start our presentation on Tuesday




 
Meeting Minutes
PalmReaders
12/7/99



1.  Discussed our web site and changes to be made

2.  Decided to change background color

3.  Talked about what needs to be finished for our proposal
        - address sponsor comments, arch. diagrams, schedule

4.  Discussed our presentation

5.  Divided up presentation material into slides

6.  Made index cards for each slide

7.  Organized cards into the order we'll present them and divided them into 4 groups

8.  Each person picked a group to present

9.  Presentation order: Josh, Jason C., Jason S., Ben

10. Decided to make the slides and to revise the Proposal in parallel groups of 2 on Thursday 12/9

11. After that we'll do architecture diagrams and schedule, then add them to our presentation




 
Meeting Minutes
PalmReaders
12/9/99



1.  Brought all our individual slides together

2.  Broke into 2 groups: One worked on the presentation the other on revising our proposal

3.  Addressed sponsor concerns about our document

4.  Finalized background and slide consistency for presentation

5.  Made a data flow diagram (DFD) in Power Point

6.  Made a logical view diagram in Power Point

7.  Made a tentative development schedule

8.  Finalized our proposal and printed it out




 
Meeting Minutes
PalmReaders
1/22/00



1.  Decided new meeting times to accomodate changed schedules:
        Primary:  Thursday  - 6:30 PM
        Backup:   Wednesday - 6:30 PM
        2nd Bkup: Saturday  - 1:00 PM

2.  Designed preliminary layout of our program's opening screen

3.  Designed menus and buttons for opening screen

4.  Decided to modify parts of Proposal: meeting time change,
        move editing requirement up to must do requirements

5.  Decided to send initial Email to Sponsor telling when to 
        expect finished proposal

6.  Decided what needs to be done over next week to finish proposal:
        Update our schedule based on new information from Dr. Wecker
        Change our logic diagram and complete Architecture
        Make other minor changes to the proposal




 
Meeting Minutes
PalmReaders
1/25/00



1.  Listed all menu options/events for the other doc readers

2.  Worked out a menu system and button layout for our opening screen

3.  Worked out the menu system for our view/edit doc screen

4.  Started a function list for events from the menu system

5.  Reviewed our requirements to see if we covered every feature

6.  Added additional features to our menu system

7.  Decided to meet tomarrow at 6:30 to work on our schedule and diagram




 
Meeting Minutes
PalmReaders
1/26/00



1.  Made a new schedule with Microsoft Project based on our ititial
        schedule and the implementation phases schedule from Dr. Wecker

2.  Created a new Architecture diagram based on our initial diagram
        and our screen layouts/menu systems

3.  Converted diagrams from Word diagrams to JPEG pictures for posting
        on the web site

4.  Finalized our proposal





 
Meeting Minutes
PalmReaders
2/3/00



1.  Discussed testing methods and procedures for our project

2.  Decided to use whitebox testing for modules as they were
        developed, and gremlins debugging program in POSE for
        black box testing

3.  Considered using the handspring development kit for our programs,
        but decided not to use it. We'll use the GNU palmos compiler

4.  Downloaded and installed development software and documentation
        on Ben's computer

5.  Decided to set our web page's background and font to the browsers
        default settings




 
Meeting Minutes
PalmReaders
2/10/00



1.  Found more reference documentation for programming for
        the Palm OS on the internet

2.  Played around with simple programs like Hello World to
        see how to get things like menus, dialog boxes, etc. working

3.  Got a simple GUI program working that has menus and buttons

4.  Decided to get the menu layout program finalized to how we
        want our program to look, and to make screen captures of it
        running in the emulator to post on the web site

5.  Then we made the screen captures of what we have now for the
        Options and Search menus. ftp'ed them to our group web site




 
Meeting Minutes
PalmReaders
2/19/00



1.  Installed a CVS repository into our group directory for
        coding version control

2.  Made some more progress on coding prototypes for our
        User Interface

3.  Made a web page for our coding standards

4.  Made a testing pland and code review web page

5.  Linked our index.html page to the 2 new pages

6.  Changed our index page: deleted duplicate links, cleaned
        it up, etc.

7.  Planned to work on our schedule on Monday




 
Meeting Minutes
PalmReaders
2/26/00



1.  Discussed the upcoming presentation

2.  Planned out what we wanted in our Design presentation

3.  Made index cards for the slides in our presentation

4.  Chose who was going to do which parts

5.  Decided to use POSE to give a demonstration of our
        prototype at the end of the presentation




 
Meeting Minutes
PalmReaders
10/5/99


Risks  -  and ways to Mitigate them 

    1.  Taking on too much for a two semester project 
            a.  Follow the prioritized task list as far down as we can go 
            b.  Be conservative when estimating how much we can do 
                    Add extra features if we have time at the end 

    2.  Additional features being added after the design process has started 
            a.  Keep them in mind for release two 

    3.  Portability:  Later finding out our program works for pilots but not Unix, 
         Having to make several different versions for different platforms 
            a.  Design our program very modularly and for ease of portability 
            b.  Keep graphics and other I/O routines in separate library files 

    4.  Final size of program is too large 
            a.  Reduce the number of features 

    5.  Our doc reader may not be accepted by users 
            a.  Consult with the potential users 
            b.  Keep user interface simple and similar to other pilot programs




 
Meeting Minutes
PalmReaders
2/29/00



1.  Each of us created our slides individually

2.  Brought slides together, put finishing touches on

3.  Chose a background design, added clip art

4.  Practiced our presentation




 
Meeting Minutes
PalmReaders
3/19/00



1.  Installed the compiler, emulator, and Palm references
        Ben's new computer

2.  Installed them onto Jason C's new computer, wish I had
        a new computer :(

3.  Decided to handle categories by creating a table with
        category names and corresponding number, and to store
        the category of each Doc in the AppInfo block of the db

4.  Planned to start working on implementing categories




 
Meeting Minutes
PalmReaders
3/23/00



1.  Made a more complete list of tasks that still
        need to be completed:
                Decode
                Encode
                Categories
                Change categories
                Bookmarks
                Rename
                Delete
                Beam
                Display Text
                Write Protect files
                Tap screen scrolling
                Find in file
                Global find
                Copy, cut, paste

2.  Decided to try to get decoding and displaying the
        Doc to a working point by next weekend




 
Meeting Minutes
PalmReaders
3/30/00



1.  Happily coding away:

        Josh - converted Doc list to table, set up custom
                draw function database for categories

        Ben - working on implementing categories

        Jason C. - working on bookmarks

        Jason S. - created decompress algorithm, working
                on compress




 
Meeting Minutes
PalmReaders
4/6/00



1.  Still coding away, not so happily though:

        Josh - took out custom draw function, made into
                a custom load

        Ben - working on implementing categories

        Jason C. - working on categories and bookmarks

        Jason S. - working on compress and displaying




 
Meeting Minutes
PalmReaders
4/13/00



1.  Discussed the As Built presentation coming up

2.  Planned out the presentation
        a. made index cards for each slide
        b. put them in the order we want to present
        c. decided who's doing what

3.  Planned to meet on Tuesday to put together slides

4.  Coding, testing:

        Josh - improving GUI, working on code behind buttons

        Ben - working on implementing categories

        Jason C. - working on editing features

        Jason S. - working on decompress on demand




 
Meeting Minutes
PalmReaders
4/18/00



1.  Put together As Built presentation slides

2.  Chose a background, put finishing touches on

3.  Practiced presentation

4.  Coding, testing:

        Josh - working on beaming, improving GUI

        Ben - working on AsBuilt document and poster board

        Jason C. - working on editing features and searching

        Jason S. - getting scrolling through a Doc working




 
Meeting Minutes
PalmReaders
4/24/00



1.  Brought together individual parts of the As Built
        Document

2.  Fixed all the formatting, added more to parts that
        were incomplete

3.  Finished up the As Built

4.  Made our poster board for the Capstone presentation

5.  Brought together all the parts for the Power Point
        part of our presentation

6.  Practiced the final presentation

7.  Decided to burn a CD-R with our presentation, the
        latest code, documentation, and anything else we'll
        need for the Capstone Conference

8.  Finished up debugging parts of our program.




 
Meeting Minutes
PalmReaders
10/12/99



1.  Talked about the prioritized feature list we received from our sponsor

2.  Discussed our draft of the reply to the sponsor

3.  Decided meeting time with our sponsor:  2:00 PM  Thursday
            Later changed by sponsor to 3:30

4.  Discussed what questions to ask the sponsor at the meeting

5.  Revised Email reply to sponsor

6.  Discussed agenda  for the meeting with the sponsor




 
Meeting Minutes
PalmReaders
10/21/99



1.  Discussed what we were going to do for each proposal section

2.  Decided what sections to do first and what to do later as a group

3.  Divided up sections between team members

4.  Decided when and how we would compile the document

5.  Set next meeting time to 4:00 PM on Tuesday 10/26/99




 
Meeting Minutes
PalmReaders
10/26/99



1.  Brought all our separate pieces of the proposal together

2.  Decided the format and structure for our proposal

3.  Edited what we have for the document

4.  Reviewed document for formatting consistency

5.  Made sure we have each section and "to be added" for incomplete sections

6.  Came up with questions for Dr. Wecker that we need to ask before we can complete the proposal





 
Meeting Minutes
PalmReaders
11/9/99



1.  Discussed where we are on our proposal

2.  Made a list of what needs to be done to complete the proposal

3.  Expanded the Cost/Benefits section

4.  Worked on Requirements, combined with Specs into one section

5.  Did some editing for grammar, spelling, and format

6.  Divided up remaining tasks between team members

7.  Dedided how far we might be able to get




 
Meeting Minutes
PalmReaders
11/13/99



1.  Brought all our individual proposal parts together via disk and ftp

2.  Compiled parts into current proposal

3.  Fixed formatting, spelling, and grammar

4.  Made all occurances of Palm Computing and Doc consistent

5.  Put Risks into table

6.  Worked on Architecture

7.  Updated table of contents and cover page

8.  Decided what to leave - to be completed - and what to finish by Monday




 
Meeting Minutes
PalmReaders
11/18/99



1.  Discussed remaining deliverables

2.  Talked about the Architecture

3.  Decided to start working on Arch. on Tuesday at 4:00 PM

4.  Planned to design a menu structure layout




 
Meeting Minutes
PalmReaders
11/23/99


1.  Talked about what will be on our web page

2.  Decided to meet next Monday to get a digital photos taken for our web site

3.  Talked about where well put our web page and our final program

4.  Worked on our Architecture

        a.  Made a Data Flow Diagram

        b.  Made a Logical View Diagram

        c.  Changed our Data View section

        d.  Changed our Structural View section