Wiki Navigation

Luna Team Meeting Notes - 5/29/08

Notes:

Close ALL POSSIBLE tickets by Sunday

ANYTHING required for job, have done by saturday
- check release checklist
  - daily builds
FINAL QA MEETING SUNDAY
- where/when - meet in the csl 2pm

get basis path testing paperwork and inspections paperwork to stephanie/ian by saturday/sunday if coming to QA
RELEASE MONDAY 7pm in lab
microschedule
- thursday
  - have basis path testing done
  - Richard run emma - email results to Steph
  - last minute changes to code
  - fixup user manual
  - write tests which are past due (system test scripts/unit tests)
- friday
  - testing to satisfy coverage requirement
  - defect fixing and testing - follow procedure
  - fixup user manual
  - write tests which are past due (system test scripts/unit tests)
- saturday
  - testing to satisfy coverage requirement
  - defect fixing and testing - follow procedure
  - user manual done
  - write tests which are past due (system test scripts/unit tests)
- sunday
  - close tickets
  - Final QA meeting - CSL 2pm
- monday - release meeting - 7pm

post-integration
- everything went pretty well
- few defects will be fixed asap

change request
- layout for prefrence panel - too new for 1.6
- requirement says 1.5 or higher
  - change to 1.6 or higher
  - mark submit change request/ tracy change
assign defects
- assigned 394 to long
- assigned 395 to istewart

Tasks:

Stephanie

make tickets
- what to bring to qa meeting
- release checklist tickets
Email UM changes to Tracy
- section for text box
fix script system test for stage 2
post meeting minutes and wsr
complete basis path testings
add announcement for release meeting and QA meeting
send email of microschedule
add defect for having to add mypanels to pauls panels for integration

Mark

submit change request for 1.6 version
complete basis path testings
System Test - make a manual test and then script it, add test to the cases page and update the history, then email to richard and create script

Tracy

fix srs for change request
complete basis path testings
user manual fixing

Ian

complete basis path testings

Richard

use emma to test our testsuite... send stephanie results by friday so we can make the requirement for % of tests coverage
complete basis path testings

Paul

update daily builds on wiki
javadocs for added jalopy classes/changestyle classes
complete basis path testings

Luna Team Meeting Notes - 5/22/08

Notes:

TESTING, CODING, TESTING, TESTING
- NEXT TWO WEEKS
  - system tests
    - scripts
  - unit tests
  - basis path tests
    - integration tests
      - not til code and unit tests written
IF YOU CANNOT COMPLETE A TICKET ON TIME; EMAIL STEPHANIE REASONS AND THE DATE YOU WOULD LIKE THE DUE DATE

TO BE EXTENDED

Inspections - due by Friday
- Tracy - Richard - Paul
- Stephanie - Ian - Mark
INTEGRATION

Tasks:

Stephanie

make tickets
Email UM changes to Tracy
- section for text box
script system test for stage 2
UNIT Tests are PASTDUE - complete ASAP
Complete inspections send results to author
email richard about test case change

Mark

approve change request for removal of req.
script system test for stage 2
UNIT Tests are PASTDUE - complete ASAP
Complete inspections send results to author

Tracy

update User Maunal
script system test for stage 2
UNIT Tests are PASTDUE - complete ASAP
Complete inspections send results to author
email richard about test case change
update staged delivery plan
- req 1, will link to jalopy um if there is an existing section
tag html code for header/footer and email to paul

Ian

SYSTEM test case PASTDUE
- post on test cases page and email copy to richard
script system test for stage 2
UNIT Tests are PASTDUE - complete ASAP
Complete inspections send results to author

Richard

SYSTEM test case PASTDUE
- post on test cases page
UNIT Tests are PASTDUE - complete ASAP
Complete inspections send results to author
add column to test case result matrix to specify when the last time the tests were run

Paul

Complete inspections send results to author
System tests need to be automated with scripts - if can't let Richard know ASAP
create integration plan
script system test for stage 2
for footer/header section, link to ChangeStyle UM not Jalopy

Luna Team Meeting Notes - 5/20/08

Notes:

TESTING, CODING, TESTING, TESTING
- NEXT TWO WEEKS
  - system tests
    - scripts
  - unit tests
    - basis path tests - starts thursday
  - coverage tests
    - integration tests
      - not til code and unit tests written
IF YOU CANNOT COMPLETE A TICKET ON TIME; EMAIL STEPHANIE REASONS AND THE DATE YOU WOULD LIKE THE DUE DATE

TO BE EXTENDED

Inspection teams
- Tracy - Richard - Paul
- Stephanie - Ian - Mark
CLOSE TICKETS AS SOON AS COMPLETED
BASIS TESTING MODULES :
- Stephanie - HeaderSettingsPage?
- Ian – your requirement code
- Paul – Format Action.java’s actionPerformed method
- Richard – ChangeStyleMenu?.java’s isUndoable method
- Mark – ChangeStyleMenu?.java’s getClassMenuItem method
- Tracy – ChangeStylePref?.java’s actionPerformed method

Tasks:

Stephanie

make tickets
post wsr
add scripts to schedule and daily build complete
UNIT Tests are PASTDUE - complete ASAP
CODE DUE WED - do not COMMIT
Complete inspections send results to author
System tests need to be automated with scripts - if can't let Richard know ASAP
Basis Path Tests

Mark

approve change request for removal of req.
SYSTEM test case PASTDUE
- post on test cases page and email copy to richard
- need to be automated with scripts - if can't let Richard know ASAP
UNIT Tests are PASTDUE - complete ASAP
CODE DUE WED - do not COMMIT
Complete inspections send results to author
Basis Path Tests

Tracy

remove requirement 3.0.11 from the SRS as per change request
SYSTEM test case PASTDUE
- post on test cases page and email copy to richard
- need to be automated with scripts - if can't let Richard know ASAP
need to be automated with scripts - if can't let Richard know ASAP
UNIT Tests are PASTDUE - complete ASAP
CODE DUE WED - do not COMMIT
Complete inspections send results to author
send html links to paul
change richards req (4)
Basis Path Tests

Ian

SYSTEM test case PASTDUE
- post on test cases page and email copy to richard
- need to be automated with scripts - if can't let Richard know ASAP
UNIT Tests are PASTDUE - complete ASAP
CODE DUE WED - do not COMMIT
Complete inspections send results to author
Basis Path Tests

Richard

add paul's stage 2 test to test matrix
SYSTEM test case PASTDUE
- post on test cases page
  - need to be automated with scripts - if can't let Richard know ASAP
UNIT Tests are PASTDUE - complete ASAP
CODE DUE WED - do not COMMIT
Complete inspections send results to author
Basis Path Tests

Paul

UNIT Tests are PASTDUE - complete ASAP
CODE DUE WED - do not COMMIT
Complete inspections send results to author
System tests need to be automated with scripts - if can't let Richard know ASAP
create integration plan
Basis Path Tests
Fix test case 11 to say a no defects between a certain number of formats (like 30) instead of four hours between defects

Luna Team Meeting Notes - 5/15/08

Notes:

Next Thursday - status update...
- make sure visibility cals are updated and current on the wiki
update risks
release maintenance work Stage 1.1
Update risks
- Tool issues like costello
- lack of sleep will lower quality
- Lack of customer communication (awaiting response for long period of time)
Add new system tests to wiki
- add to system test cases page
- email number, case, etc. to Richard
- richard will link everything else
CLOSE ALL TICKETS THAT ARE POSSIBLE TO CLOS
For Tuesday
- All Unit Tests and System tests for stage 1.1
- release page updated - release notes
- schedule updated and concrete
- make sure wiki is all connected

Tasks:

Stephanie

system giu test for xml naming convention - due Sunday
fix schedule
- add new section for maintenance release - Rename to Stage 1.1
  - auto-daily build LATE
clarity for headers and footers
- put text box in delete area
- we don't want to allow for deletion of headers
UNIT Tests AND SYSTEM TESTS for Stage 2 requirement(s) - Due SATURDAY
Begin coding for Stage 2 requirement(s) - DUE Wed.
update visibility calcs
unit tests need to be updated (LINK)

Mark

Finish up status of change request for req. 5 removal
UNIT Tests AND SYSTEM TESTS for Stage 2 requirement(s) - Due SATURDAY
Begin coding for Stage 2 requirement(s) - DUE Wed.
HOURS REPORT

Tracy

maintanence req. 4 - due 5/20
- Write User Manual Conventions section
write updates to the User Manual for requirement 9 by 5/13
Change request for user manual for stage 1.1
change unit test for old homework into .java from .txt
UNIT Tests AND SYSTEM TESTS for Stage 2 requirement(s) - Due SATURDAY
Begin coding for Stage 2 requirement(s) - DUE Wed.
HOURS REPORT
release notes for 1.1
defect for batch undo in the SRS

Ian

maintenance req.3 - due 5/15
write udates to the User Manual for requirements 2/6 and submit to Tracy by 5/13 (waiting for customer response)
UNIT Tests AND SYSTEM TESTS for Stage 2 requirement(s) - Due SATURDAY
Begin coding for Stage 2 requirement(s) - DUE Wed.
HOURS REPORT
post QA Plan on wiki

Richard

write updates to the User Manual for requirements 3/4 and submit to Tracy by 5/13 LATE
Complete EMMA coverage testing tutorial (in test plan)
runs all Stage 1.0 tests on maintenance - Sunday/Monday
- make sure all tests (system and unit) pass for Stage 1.1
- get ready for 1.1 release
UNIT Tests AND SYSTEM TESTS for Stage 2 requirement(s) - Due SATURDAY
Begin coding for Stage 2 requirement(s) - DUE Wed.
HOURS REPORT

Paul

automated Daily Build LATE
maintenance req. 2 - due 5/15 LATE
write updates to the User Manual for requirement 1 and submit to Tracy by 5/13 LATE
system tests and unit tests for maintenance work - due Sunday
UNIT Tests AND SYSTEM TESTS for Stage 2 requirement(s) - Due SATURDAY
Begin coding for Stage 2 requirement(s) - DUE Wed.
HOURS REPORT

Luna Team Meeting Notes - 5/8/08

Notes:

decide repository
modify schedule
- Unit Tests due Saturday instead of Thrusday
- Coding Sunday thru Wednesday by like 9pm (since inspections on Thursday)

Tasks:

Stephanie

old wsr ant todays notes - post
make tickets
write updates to the User Manual for requirement 7 and submit to Tracy
send Ian what needs to be changed for test case 22
update schedule
system giu test for xml naming convention - due Sunday

Mark

Finish up status of change request for req. 5 removal
write updates to the User Manual for requirement 8 and submit to Tracy by 5/13
Finish repository rework

Tracy

maintanence req. 4 - due 5/15
- Write User Manual Conventions section
write updates to the User Manual for requirement 9 by 5/13
Change request for user manual for stage 1.1
change unit test for old homework into .java from .txt

Ian

procedure rewrite for test case 22
maintenance req.3 - due 5/15
write udates to the User Manual for requirements 2/6 and submit to Tracy by 5/13
write universal BClass stub for unit testing - waiting for repository

Richard

write updates to the User Manual for requirements 3/4 and submit to Tracy by 5/13
Complete EMMA coverage testing tutorial (in test plan)
prototype for undo dialog
work on automating system tests

Paul

automated Daily Build
- Tues - 5/13
maintenance req. 2 - due 5/15
figure out what needed for requirement
write updates to the User Manual for requirement 1 and submit to Tracy by 5/13
system tests and unit tests for maintenance work - due Sunday

Luna Team Meeting Notes - 5/8/08

Notes:

FOLLOW THE DEFECT PROCEDURE
Testing Cycle
- Unit Test (white box)
- Coding
- Integration Testing (white box)
- System Testing (black box)
- Acceptance Testing
System test/unit test case for maintenance work
Schedule Revisions:
- Unit Testing by Thursday 15th
- Coding start Friday 16th done by 21st
- Inspections Tues 22nd
- Integration 23rd - 27th
  - System Tests 23rd - 27th
- Basis Path Testing (next week - release)
- coverage testing (next week - release)
EACH PERSON NEEDS TO WRITE SYSTEM TEST CASES AND SCRIPTS, UNIT TEST CASES FOR THEIR NEW REQUIREMENTS
EVERYONE NEEDS TO REDO THE ASSIGNMENT DUE TUES

Tasks:

Stephanie

rewrite schedule
old wsr
make tickets
maintanence req. 4 - due 5/15
send tracy xml convention summary
figure out what needed for requirement
write updates to the User Manual for requirement 7 and submit to Tracy

Mark

SET COMPONENT FIELDS ON TRAC - due ASAP (LATE)
- can change through wiki under admin page
- change severity fields
change request for removal of req. 5
send tracy xml convention summary
fix branching
figure out what needed for requirement
write updates to the User Manual for requirement 8 and submit to Tracy by 5/13
New section on Release Page for Maintenance work (Stage 1.1)
HW ASSIGNMENT BY SAT

Tracy

add requirements to SRS
switch up staged delivery plan
maintanence req. 4 - due 5/15
- Write User Manual Conventions section
figure out what needed for requirement
write updates to the User Manual for requirement 9 by 5/13
Change request for User Manual

Ian

procedure rewrite for test case 22
maintenance req.3 - due 5/15
figure out what needed for requirement
write udates to the User Manual for requirements 2/6 and submit to Tracy by 5/13
write universal BClass stub for unit testing

Richard

req. 8 feasibility Due THURSDAY
prototype editing
figure out what needed for requirement
write updates to the User Manual for requirements 3/4 and submit to Tracy by 5/13
Complete EMMA coverage testing tutorial (in test plan)
make system test scripts for last releases functional system test cases (cases you did)

Paul

automated Daily Build
- Tues - 5/13
maintenance req. 2 - due 5/15
figure out what needed for requirement
write updates to the User Manual for requirement 1 and submit to Tracy by 5/13
System test case/unit test case for maintenance work (button, is there and clickable)

Luna Team Meeting Notes - 5/6/08

Notes:

FOLLOW THE DEFECT PROCEDURE
New for Stage 2:
- Do Black Box Testing
  - In week 8: complete WHITE box testing
- Write unit tests before code
- Coverage Testing
- Automated functional system tests using Costello
- Automated Daily Build
Every person needs to write udates to the User Manual for their requirement(s) and needs to submit them to Tracy so she can add them to the User Manual
Write Cosetello System Tests, after Thursday's homework, for new requirements

From Release:

* More thorough, product specific javadocs, don't just use @override * Fix some system tests

Case 22
- needs procedure rewrite
Case 16
- edit procedure and put into test data (follow other cases)

* REQ. 10 NOT WHAT USER WANTED

Known Issues from Release:

* OK doesn't save settings without apply * In Preferences Dialog, uses wrapping not misc wrapping for misc wrapping page -- FIXED * Change testcase/UM documentation (Case 16) -- FIXED * Forward slash in undo -- FIXED

Maintenance Work: DUE MAY 15th

1. Fix the drop down menu for conventions (fix little bit hidden)

2. make help link (near label) to the UM predefined conventions section

3. add a predefined conventions section to the User Manual

4. fix name of conventions in files

redo xml files

DELEGATION:
1. IAN
2. PAUL
3. TRACY
4. STEPHANIE

Stage 2 Requirements:

1. Every panel in the settings dialog will have a help link linking to the corresponding section in the Jalopy User Manual.

2. ChangeStyle will allow the user to modify predefined conventions and save them as customized conventions that will appear in the conventions drop down box along with the original predefined conventions.

3. ChangeStyle implement Batch Undo, which presents the user with a dialog with a selectable list of files which can be undone, while displaying files which cannot be undone in grey.

4. Changes made by ChangeStyle’s formatting are visible immediately in the editor window, and when the Undo button is selected in the editor window, the editor window shows the undone code.

5. ChangeStyle's editor window will present a Format button to the user. -- BEING REMOVED!!!

6. The import and export convention functionality for ChangeStyle is working properly and is located in the Preferences Panel and is designed based on the approved UI prototype.

7. ChangeStyle allows the user to replace Headers and Footers containing some user-specified text in the corresponding panels and offers a help link to a new section in the User Manual describing Headers and Footers in more detail.

NEW**8. Every time a class or project is formatted by ChangeStyle, the 'status panel' at the bottom of BlueJ's window displays "Formatting... Done." When the undo feature is selected, the window will display "Undo Formatting... Done" -- ********Needs Feasibility

NEW**9. When the users clicks, the "Edit Style Conventions" button, no matter how many times, the Preferences panel only appears once.

Delegation:

1.Paul Help:Stephanie/Tracy

2.Ian Help:Richard/Mark

3.Richard Help:Paul

4.Richard Help:Tracy

6.Ian Help:Mark

7.Stephanie

8.Mark

9.Tracy

Tasks:

Stephanie

schedule
post notes and wsr
make tickets
- system tests with costello after thurs
maintanence req. 4 - due 5/15
send tracy xml convention summary
figure out what needed for requirement
write updates to the User Manual for requirement 7 and submit to Tracy

Mark

SET COMPONENT FIELDS ON TRAC - due ASAP (LATE)
- can change through wiki under admin page
- Components include: Jalopy, Extension, PreferenceGenerator?, MenuGenerator?, CUSTOM CLASSES?
change request for removal of req. 5
send tracy xml convention summary
fix branching
prototype editing
figure out what needed for requirement
write updates to the User Manual for requirement 8 and submit to Tracy by 5/13

Tracy

make corrections to stage requirements
- get from meeting notes

post maintenance work
add requirements to SRS
maintanence req. 4 - due 5/15
- Write User Manual Conventions section
talk to customer about questions for stage
figure out what needed for requirement
write updates to the User Manual for requirement 9 by 5/13

Ian

fix prototype
- add help button under EDIT
procedure rewrite for test case 22
maintenance req.3 - due 5/15
figure out what needed for requirement
write udates to the User Manual for requirements 2/6 and submit to Tracy by 5/13
write universal BClass stub for unit testing

Richard

req. 8 feasibility Due THURSDAY
prototype editing
figure out what needed for requirement
write updates to the User Manual for requirements 3/4 and submit to Tracy by 5/13

Paul

automated Daily Build
- Tues - 5/13
maintenance req. 2 - due 5/15
figure out what needed for requirement
write updates to the User Manual for requirement 1 and submit to Tracy by 5/13

Luna Team Meeting Notes - 5/1/08

Notes:

decide requirements – write quantifiably

Proposed Maintenance Work:

1. Fix the drop down menu for conventions (fix little bit hidden) 2. make label for box that links to the UM predefined conventions section 3. add a predefined conventions section to the User Manual 4. fix name of conventions

redo xml files

Proposed Stage 2 Requirements: 1. Make multiple help links (vs. Stage 1.0 universal button)

make label links
use lookup table/tool tips

Official Requirement 1: Every panel in the settings dialog will have a personal help link linking to the corresponding section in the Jalopy User Manual.

2. Dynamic customzed conventions

have a folder where the user can place their own conventions which will be listed in the drop down menu

Official Requirement 2: ChangeStyle will allow the user to modify predefined conventions and save them as customized conventions that will appear in the conventions drop down box along with the original predefined conventions.

3. Batch Undo - UI Prototype

Official Requirement 3: ChangeStyle implement Batch Undo, which presents the user with a dialog with a selectable list of files which can be undone, while displaying files which cannot be undone in grey.

4. Use text replacement vs. file replacement

show immediate change in editor

use undo button in editor
make sure that the editor doesn't blank out using undo(in editor) after formatting

Official Requirement 4: Changes made by ChangeStyle’s formatting are visible immediately in the editor window, and when the Undo button is selected in the editor window, the editor window shows the undone code.

5. Personal editor with format button inside Modify BlueJ editor to present a Format button to the user.

Official Requirement 5: ChangeStyle's editor window will present a Format button to the user.

6. Reorganize settings dialog

remove general/projects/printer label/code inspector
- add those features (and predefined conventions) to new Changestyle dialog
  - on main settings dialog only have button
move predefined conventions to general pane
Fix apply/ok to save naming for conventions correctly
- when hit export - flush conventions first then export
- currently has tempermental functionality
Fix multiple settings dialog pop-up
Move import/export convention functionality from General Tab in SettingsDialog? to ChangeStyle Preferences Panel and redesign the preferences panel based on the approved UI Prototype ...

Official Requirement 6: The import and export convention functionality for ChangeStyle is located in the Preferences Panel and is designed based on the approved UI prototype.

7. Header and footer tabs - change to do single not multiple - omit error message

give text field for header input and one for footer
Delete "Delete Headers/Footers" and replace with "Replace Header/Footer Containing..." in Header and Footer panels. Have help button link to new User Maunal section describing Headers and Footers more in detailed.

Official Requirement 7: ChangeStyle allows the user to replace Headers and Footers containing some user-specified text in the corresponding panels and offers a help link to a new section in the User Manual describing Headers and Footers in more detail.

Tasks:

Stephanie

send reqs to Tracy
defect ticket for "loose"
post notes and wsr
make tickets
review stage 2 requirements list and send Stephanie what top three requirements choices

Mark

SET COMPONENT FIELDS ON TRAC - due SATURDAY by midnight
- can change through wiki under admin page
- Components include: Jalopy, Extension, PreferenceGenerator?, MenuGenerator?, custom classes?

review stage 2 requirements list and send Stephanie what top three requirements choices

Tracy

batch formatting - add requirement to SRS
post new reqs on wiki staged delivery plan
talk to customer about layout and one help links
review stage 2 requirements list and send Stephanie what top three requirements choices

Ian

make jalopy error message more verbose
layout sketches – UI Prototype?
review stage 2 requirements list and send Stephanie what top three requirements choices

Richard

feasibility for editor feature and text replacement vs. file replacement
automatic revision rework
batch undo prototype
* review stage 2 requirements list and send Stephanie what top three requirements choices

Paul

final Stage 1 LOC
estimate for stage 2
review stage 2 requirements list and send Stephanie what top three requirements choices

Luna Team Meeting Notes - 4/29/08

Notes:

WE GOT ACCEPTED!! YEA!
decide requirements
Release 2 : JUNE 3rd!!!!

HEADS UP!!!! : Formal white box tests

From Release:

More thorough, product specific javadocs, don't just use @override Fix some system tests

Proposed Maintenance Work:

redo xml files

Proposed Stage 2 Requirements:

1. Make multiple help links (vs. Stage 1.0 universal button)

make label links
use lookup table/tool tips

2. Dynamic predefined conventions

have a folder where the user can place their own conventions which will be listed in the drop down menu

3. Batch Undo 4. Use text replacement vs. file replacement

show immediate change in editor

use undo button in editor
make sure that the editor doesn't blank out using undo(in editor) after formatting

6. Reorganize settings dialog

remove general/projects/printer label/code inspector
- add those features (and predefined conventions) to new Changestyle dialog
  - on main settings dialog only have button
move predefined conventions to general pane
Fix apply/ok to save naming for conventions correctly
- when hit export - flush conventions first then export
- currently has tempermental functionality

7. Header and footer tabs - change to do single not multiple - error message

give text field for header input and one for footer

Tasks:

Stephanie

send reqs to Tracy
defect ticket for "loose"
post notes and yest. email to dalbey
make tickets

Mark

add link for stage 2 requirements
add stage 2 user manual link

Tracy

batch formatting - add requirement to SRS
post new reqs on wiki staged delivery plan
talk to customer about layout and one link per tab vs. one per thing

Ian

Costello tutorial - due thurs
make jalopy error message more verbose
layout sketches

Richard

feasibility for req. 4
automatic revision rework

Paul

Costello tutorial - due thurs
final Stage 1 LOC
estimate for stage 2

Luna Team Meeting Notes - 4/24/08

Notes:

write JUNIT tests for code that is testable

o if a GUI change then use ABBOT to test (UNIT)

two choices to download --- not same
only zip has costello (Costello for system tests)

o or ask Professor Dalbey for help

2 defects a week

emergency change request...
- add pop to display message that code couldn't be formatted
acceptance test meeting at 7pm on Monday in lab

Tasks:

Stephanie

update/make tickets
make more reports with due date
check version number
JUnit test by Friday to Richard (and Stephanie for binder)
send system test cases to Richard
update project vision
add wiki links for Test Matrix, Test Cases, Test Results
- add test cases to wiki page after compilation
make document of all source code (or equivalent) and send to Stephanie for binder
print inspection log
rewrite email for code proposal

Mark

send Stephanie system test cases
JUnit Tests by Friday to Richard(and Stephanie for binder)
Add whether or not change request proposals are approved/denied
Make folder in repository for JUnit tests
pictures for user manual
make document of all source code (or equivalent) and send to Stephanie for binder
add change proposal for pop-up unsuccessful format

Tracy

JUnit test by Friday to Richard(and Stephanie for binder)
get User Manual Up on wiki
update SRS
release notes
fix requirements page and staged delivery plan for more qunatifiable requirements
make document of all source code (or equivalent) and send to Stephanie for binder
add xp, os 10, linux for system requirements - add to requirements

Ian

JUnit test by Friday to Richard(and Stephanie for binder)
send Jalopy known issues list to professor Dalbey
possibly change UI????
make document of all source code (or equivalent) and send to Stephanie for binder

Richard

JUnit test by Friday to Richard (and Stephanie for binder)
over weekend run system tests and unit tests a few times
post results and matrix on wiki
make document of all source code (or equivalent) and send to Stephanie for binder

Paul

JUnit test by Friday to Richard (and Stephanie for binder)
Update Daily Build Procedure on wiki
continue daily build
make document of all source code (or equivalent) and send to Stephanie for binder
submit change request for batch formatting

Luna Team Meeting Notes - 4/22/08

Notes:

check where everyone is
Paul introduced team to daily build
write JUNIT tests for code that is testable
- if a GUI change then use ABBOT to test
- or ask Professor Dalbey for help
system tests not automated (yea!)

Tasks:

Stephanie

post past two meeting notes
update/make tickets
make more reports with due date
look at mark’s change requests
figure out how to add new fields
- trac.ini is place
check version number
remove jalopy’s history functionality
inspection preparation (Ian/Mark)
update schedule
defect reports for stage 0.1 (my two changes)
JUnit test by Friday to Richard
send system test cases to Richard
print out test cases for OH tomorrow

Mark

Jalopy tests 4.3.5.3 – 4.3.6.1 by Sunday @ midnight
look at mark’s change requests
inspection preparation (Stephanie/Ian)
JUnit test by Friday to Richard

Tracy

look at mark’s change requests
JUnit test by Friday to Richard
inspection preparation (Paul/Richard)

Ian

look at mark’s change requests
- inspection preparation (Stephanie/Mark)
JUnit test by Friday to Richard
send Jalopy known issues list to professor Dalbey

Richard

look at mark’s change requests
- inspection preparation (Tracy/Paul)
JUnit test by Friday to Richard

Paul

look at mark’s change requests
- inspection preparation (Tracy/Richard)
JUnit test by Friday to Richard

Luna Team Meeting Notes - 4/17/08

UPDATED SCHEDULE:

System Tests : Due Friday 18th @ midnight

Jalopy Tests : Due Sunday 20th @ midnight to Tracy

Write Code/comments – Due Wednesday 23rd @ noon

Inspection Meeting (complete inspection at home) : Thursday 24th in LAB

Unit Testing using JUnit: Due Saturday 26th at midnight

All JOB-specific documents and such: Due Saturday the 26th at midnight

Final QA stuff: Due Monday 8pm.

I want EVEREYTHING done by 8PM on MONDAY.

Notes:

Schedule solidify
split up inspections
- next Thursday in lab - meeting
split up system test cases due FRIDAY
- Tracy 3.0.1-3.0.5
- Mark 3.0.6-3.0.9
- Paul 3.0.10-3.0.13
- Ian 3.0.14-3.0.18
- Stephanie 2.1.4,6,7,12,13

for new code - write up test cases

Tasks:

Stephanie

post todays meeting notes
update/make tickets
figure out how to add new fields - trac.ini is place
System Tests
update schedule
Jalopy tests 4.3.5.2 – 4.3.5.2.2 by Sunday @ midnight

Mark

Jalopy tests 4.3.5.3 – 4.3.6.1 by Sunday @ midnight
System tests

Tracy

Jalopy tests 4.3.5.1 (all) by Sunday @ midnight
Change requirements list
System tests

Ian

Jalopy tests 4.3.6.2 – 4.3.7.3 by Sunday @ midnight
System tests

Richard

Jalopy tests 4.3.8 (all) by Sunday @ midnight
System tests

Paul

Jalopy Tests 4.3.4.2.2 – 4.3.4.3 by Sunday @ midnight
System tests

Luna Team Meeting Notes - 4/15/08

Notes:

QA managers meet with us (Luna) and distribute Jalopy tests created by Ian
Don’t submit code to svn prior to inspection – must pass inspection before commit

Team Notes:

System test cases break up moved to Thursday
EMERGENCY!: we need to create a solid list of requirements for stage one
need to estimate time for each potential requirement and then compile average
Jalopy tests due to Tracy by Sunday at Midnight

Tasks:

Stephanie

post todays meeting notes
update/make tickets
learn project plan and edit as needed
figure out how to add new fields - trac.ini is place
- one for defects
review Stage 1 scoresheet/release checklist/criteria list
update schedule
- email Tracy Ian’s Jalopy list
Jalopy tests 4.3.5.2 – 4.3.5.2.2 by Sunday @ midnight
Team Manager 1.0 Release duties complete by 27th @ 5pm
- see schedule

Mark

Jalopy tests 4.3.5.3 – 4.3.6.1 by Sunday @ midnight
Emergency hours estimate for requirements
Change Manager 1.0 Releases duties complete by 27th @ 5pm
- see schedule

Tracy

Jalopy tests 4.3.5.1 (all) by Sunday @ midnight
write stage 1 requirements (update)
update stage delivery plan with stage 1 requirements
Emergency hours estimate for requirements
Analyst 1.0 Release duties complete by 27th @ 5pm
- see schedule

Ian

Jalopy tests 4.3.6.2 – 4.3.7.3 by Sunday @ midnight
learn QA plan and edit as needed
Emergency hours estimate for requirements
QA Manager 1.0 Release duties complete by 27th @ 5pm
- see schedule

Richard

Jalopy tests 4.3.8 (all) by Sunday @ midnight
learn test plan and edit as needed
create system tests cases for 0.1 and 1.0
- email steph
Emergency hours estimate for requirements
Test Manager 1.0 Release duties complete by 27th @ 5pm
- see schedule

Paul

Jalopy Tests 4.3.4.2.2 – 4.3.4.3
Make Daily Build Plan
Emergency hours estimate for requirements
Design/Implementation Manager 1.0 Release duties complete by 27th @ 5pm
- see schedule

Luna Team Meeting Notes - 4/10/08

Notes

- class discuss stage 1 requirements

- group discussed top risks

- check if need to change:

system requirements: add for Mac and Linux users
don't make reqs unnecessarily restrictive
install instructions correct

- make change requests for changes!!!!!

- Prof. Dalbey discussed what needs to happen next:

Analyst
- take changes list and put into 1.0 requirements so we can test feasibility
- update staged delivery plan
- update user manual
Write system test cases for 0.1 and 1.0 features
feasibility for stage 1.0 features
- generate solutions or walk-arounds
Jalopy Tests
- do we have the current version of Jalopy?
- is there a list of known defects
- new release soon?
- will they fix defects we find?
- not automated

Teams Notes:

defect tracking
will need to update user manual and staged delivery plan
richard didn't bring risks list
Stage 1 rough requirements:
1. put format in class and tools menu
  - no feasibility needed - already was in tools menu
2. online help in settings dialog or use tool tips
  - Ian and Mark feasibility by tues.
3. fix undo functionality
4. look at Jalopy known issues
5. default switch formatting option
  - Paul feasibility by Tues

Tasks:

Stephanie

post todays meeting notes
update/make tickets
learn project plan and edit as needed
post LOC when recieve from Paul
figure out how to add new fields - trac.ini is place
- one for defects
review Stage 1 scoresheet/release checklist/criteria list
compile Risks
break up of system test cases if needed
assign jalopy tests when get split up list from Ian
email hour requirements

Mark

make change request proposal for change to requirements
- change will effect user manual and product
make change request for figure 10 change in user manual
create risks list
learn change plan and edit as needed
branch project (familiarize with)
- need comments first
- wait to do til Thursday 4/8
make "release" folder in respository and put correct jar files in corresponding folder
make link to current build
review Stage 1 scoresheet/release checklist/criteria list of your positions duties
Feasibililty for using toolTips - req. 7

Tracy

review Stage 1 scoresheet/release checklist/criteria list of your positions duties
due Ian's jarfile assignment
write stage 1 requirements
update stage delivery plan with stage 1 requirements
email richard old requirements
email paul new requirements

Ian

learn QA plan and edit as needed
review Stage 1 scoresheet/release checklist/criteria list of your positions duties
look up features of jalopy, split up list to test
feasibility for putting online help in settings dialog

Richard

learn test plan and edit as needed
review Stage 1 scoresheet/release checklist/criteria list of your positions duties
due Ian's jarfile assignment
create system tests cases for 0.1 and 1.0
- email steph

Paul

review Stage 1 scoresheet/release checklist/criteria list of your positions duties
due Ian's jarfile assignment
review code to see if need to add comments/psuedocode
- in 0.1 before branch
- delayed to after 4/10/08 due to repository rework
estimate planned lines of code
- after recieve reqs from Tracy
- due by Thursday
redo LOC count to not have comments
default switch feasibility

Luna Team Meeting Notes - 4/8/08

Notes:

- Tracy in customer conference call

- class reviewed/discussed

action item tracking - using trac tickets
- add new field - project plan
  - due date
  - status
change control plan
defect tracking through trac tickets
- retroactively create defect ticket and mark it as fix
  - Stephanie make 1st 3 for changes made
system tests
- ad-hoc: no more
- new approach: systematic
  - read about for HW
Stage 1 delivery plan
- Thursday
each team copy of user manual
- edit UM to reflect stage 1 changes
- edit design documents as needed
  - class diagram
  - psuedocode
look at code
- add comments of psuedocode if not there

Team Notes:

Stephanie now risk manager
team decided how to fix problem of updating jarfile
- have working copy in the repository and then seperate folders contain release of the jarfile

Heads Up: Stage 1 Release Dates

Stage 1 complete due 4/29 Jalopy Tests due 4/22 System Tests due 4/17

Mark wants team make comments for revisions meaningful
- say the java file you edited in the comment
- then say what you did to file
Go over design next meeting

Tasks:

Stephanie

post todays meeting notes
update/make tickets
create risks list
learn project plan and edit as needed
fix jar file to release 119
- today by 5
post LOC when recieve from Paul
figure out how to add new fields - trac.ini is place
- one for defects
  - add defect tickets
review Stage 1 scoresheet/release checklist/criteria list
due Ian's jarfile assignment

Mark

make change request proposal for change to requirements
- change will effect user manual and product
make change request for figure 10 change in user manual
create risks list
learn change plan and edit as needed
branch project (familiarize with)
- need comments first
- wait to do til Thursday
make "release" folder in respository and put correct jar files in corresponding folder
make link to current build
review Stage 1 scoresheet/release checklist/criteria list of your positions duties
due Ian's jarfile assignment

Tracy

double check usermanual pic - mess with more
create risks list
add list from google group to page
- wikipage:Stage 1 and Stage 2 Plan - rename page
review Stage 1 scoresheet/release checklist/criteria list of your positions duties
due Ian's jarfile assignment
send Ostrich html of User Manual

Ian

create risks list
learn QA plan and edit as needed
review Stage 1 scoresheet/release checklist/criteria list of your positions duties
due Ian's jarfile assignment

Richard

create risks list
learn test plan and edit as needed
review Stage 1 scoresheet/release checklist/criteria list of your positions duties
due Ian's jarfile assignment

Paul

create risks list
download LOC tool and report project LOC by Thursday meeting
review Stage 1 scoresheet/release checklist/criteria list of your positions duties
due Ian's jarfile assignment
review code to see if need to add comments/psuedocode
- in 0.1 before branch

Luna Team Meeting Notes - 4/3/08

- Requirement changed... if code is not compilied, gray out format button

push back deadline - to 3:30 pm
add to user manual
- how will user know to compile first
- maybe instead of gray out, let them click it and pop up a message saying to compile first
  - disable button
    - display message "not compiled"
      - Richard completed this fix in class - now format is greyed out and next to the format "(not compiled)" shows
  - show "must compile method"
- Richard is handling how to fix
  - disabled with "noty compiled" message next to format option
Change Request!!
- class meeting
- impact; can't get jar file ready intime for release today
- change

Need to update jar file at 3pm

Tasks:

Stephanie

meet paul to in CSL at 3pm to make jar file for 0.1 release
update/make tickets

Mark

make change request proposal for change to requirements
- change will effect user manual and product
make change request for figure 10 change in user manual
add intstructions to download
- DUE by 3:15PM TODAY
change stage 1 to stage 0.1 on wiki
- Fri by MIDNIGHT

Tracy

double check usermanual pic
change release notes
- document in known issues: 1. that our "undo button" requirement is not completed
  1. that the class agreed that the compiled check won't work
- before 3pm TODAY
add user manual to svn

Ian

Richard

please attempt to finish the undo button
- if this cannot be completed before 3pm then email and let me know the status

Paul

Meet Stephanie at 3 in CSL to make final Jar file for 0.1 release

Luna Team Meeting Notes - 4/1/08

Job Changes:

Mark - Change Manager

Stephanie - Team Manager

Tracy - Analyst

Paul - Design/Implementation Manager

Ian - QA Manager

Richard - Test Manager

Notes:

- Team decided we will use version number in style of complete release, followed by stage release, followed by version number of svn (ex: 0.1.88)

- Team decided to change group weekly status report on Monday

- Team decided to have a "time update" for the week due by Sunday at 8PM

- Team decided to no longer have weekly status reports but on the condition we religiously update the status of our tickets. If this doesn't happen we will revert to individual status reports

- Team split up work to get stage one release of ChangeStyle complete

Need to complete:

Code into framework = IAN
Undo formatting = RICHARD
Handle uncompiled code = STEPHANIE
link/description in "about" box = TRACY

More Notes

In eclipse, under the project tab, follow the pulldown menu and TURN OFF the Build Automatically option; Under the clean project option, TURN OFF the Rebuild After Clean option... (hints from Ian and Richard so the class files of the projects won't be put on the repository)

Tasks:

Stephanie

change permissions for wiki
- switch Mark and Tracy
- under admin part of wiki
make new name tag sheet
create tickets for EVERYTHING
- ticket for Tracy to make sure everything is updated from last quarter
change ticket info via shell
- from address for tickets
change job descriptions link to 309 page on Luna wiki
write up and post team meeting minutes on wiki
edit source code and handle if call format on uncomplied code or not
- by MIDNIGHT 4/2/08
download eclipse

Mark

create download page for stage 1 release
update User Manual image
create seperate folder for the stage 1 user manual in repository

Tracy

add stage 1 User Manual to repository
make image change to stage 1 user manual
edit source code and add a link to our stage 1 user manual and a description of ChangeStyle in the "about" box
- by MIDNIGHT 4/2/08

Ian

get code into framework
- by 9PM 4/1/08
- email team when done

Richard

edit source code and handle undo formatting problem
- by MIDNIGHT 4/2/08

Paul

work on getting all the libraries into a single jar file and put in the repository
- by MIDNIGHT 4/2/08

Meeting Notes - 3/11/08

Reminder

Check Meeting Notes for assigned tasks
Check and update tickets (if complete or not)
High Level Design DUE
Detailed Level Design DUE

Steph

Add meeting notes and Progress Report
Create Download page (Other than Feasibility)
Change User Manual to "User Manual Prelimary"
Add Stage 1 User Manual
Add "Analysis Issues and Trade off" Page

Mark

Go over Pros/Cons of features we are not implementing in Jalopy
Send ChangestyleMenu? to Tracy - NOT DONE
Write wordage for download page. 3/16
Send pictures for edited User Manual to Tracy 3/14.
Email Richard ChangeStyle Menu - NOT DONE

Tracy

Send out meeting notes from 3/6/08 DONE
Action items
Go through User Manual and edit writing.
- Send Dalbey email when is complete
Update ALL WIKI Information!!!!!!

Richard

Create a High level Design for ChangeStyle DONE
Make sure pseucode is correct and constants. By Sat DONE
Email Paul – NOT DONE
Add changes to High Level Design from FTR DONE
Look at Tortoise to see about versions - TBA

Ian

Research feasibility of undo and other features in jalopy
Pros/ Cons for Jalopy 3/17

Paul

QA of High Level design DONE
Compose FTR Checklist for High Level Design DONE
QA Detailed Design aim DONE
Summary of FTR by Tues DONE

Notes

High Level Design was moved to be due Tues, 3/11.
Detailed Design was moved to be due Thurs 3/11
FTR for High Level Design 3/6

Meeting Notes - 3/6/08

Reminder

Check Meeting Notes for assigned tasks
Check and update tickets (if complete or not)
Status Report
EVERYONE add email to settings in wiki!!!
Look at Empty Set's FTR!!

Steph

Add SRS to wiki - not SRS html code
Add meeting notes and Progress Report
Add that our SRS won!
Create Download page By Today

Mark

EMAIL SRS to Steph DONE
Email philosophy DONE/LATE
Email customer about using Jalopy's formatting style. DONE
Go over Pros/Cons of features we are not implementing in Jalopy
Send ChangestyleMenu? to Tracy
Write wordage for download page. Tues

Tracy

Send out meeting notes from 3/6/08
Action items
Pseudocode for ChangeStyleMenu? 3/4 - Took form Mark- gave back
Go through User Manu and make sure it is like extended prototype.

Richard

Create a High level Design for ChangeStyle DONE
Make sure pseudocode is correct and constant. By Sat -email Paul
Add changes to High Level Design from FTR

Ian

Research feasibility of undo and other features in jalopy
Send Pro/Cons for Highlighting to Steph and Mark. DONE

Paul

QA of High Level design
Compose FTR Checklist for High Level Design DONE
QA Detailed Design aim for Mon
Summary of FTR by Tues

Notes

High Level Design was moved to be due Tues, 3/11.
Detailed Design was moved to be due Thurs 3/11
FTR for High Level Design 3/6
FTR is on Thursday
UI Prototype link to feasibility for Setting Changes

Add Credit Page to Detailed Level Design

Update User Manual to go with Extended Prototype
Update SRS to requirements

Edit Bluej's editor
- Make our own editor.

Meeting Notes - 3/4/08

Reminder

Check Meeting Notes for assigned tasks
Check and update tickets (if complete or not)
EVERYONE add email to settings in wiki!!!
Edit psuedocode by tonight
Look at Empty Set's FTR!!

Steph

Add SRS to wiki - not SRS html code
Add meeting notes and Progress Report DONE
Post Philosophy NOT Emailed by Mark
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28 LATE/DONE
Extended Link prototype DONE
Pseudocode for ChangeStyle 3/4

Mark

EMAIL SRS to Steph
Email philosophy NOT DONE
Email customer about using Jalopy's formatting style.
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28 LATE
Emailed UI Prototype and User Manual DONE
Get pictures of Extended Prototype to Ian by 6:00 pm DONE

Tracy

Send out meeting notes from 3/4/08
Action items
Redo schedule in wiki DONE
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28 LATE/DONE
Changes Marks, Ian, Richard and Paul password change DONE
Download Tortoise DONE
Pseudocode for ChangeStylePref? 3/4
Pseudocode for ChangeStyleMenu? 3/4- Took form Mark
Send Dalbey Extended Prototype. DONE
Go through User Manu and make sure it is like extended prototype.

Richard

Create a High level Design for ChangeStyle DONE
Pseudocode for RevertBackupAction? 3/4
Update High Level Design and send to Paul DONE

Ian

Research feasibility of undo and other features in jalopy
Get together with Paul to go over ActionFormat? DONE
Pseudocode for ChangeStylePreview? 3/4
Create links for pictures of Extended Prototype by Tomorrow Morning DONE
- notify Tracy to look over. DONE
Send Pro/Cons for Highlighting to Steph and Mark.

Paul

QA of High Level design
Compose FTR Checklist for High Level Design DONE
Download Tortoise
Email format pseudocode format to all. DONE
meet with Ian to over ActionFormat? DONE
Pseudocode for ActionFormat? 3/4

Notes

High Level Design was moved to be due Tues, 3/11.
Detailed Design was moved to be due Thurs 3/11
FTR for High Level Design 3/6
FTR is on Thursday
UI Prototype link to feasibility for Setting Changes
Add Credit Page to Detailed Level Design
Update User Manual to go with Extended Prototype
Update SRS to requirements

Meeting Notes 2/28/08

Reminder

Check Meeting Notes for assigned tasks

Check and update tickets (if complete or not)

Status Reports due

Steph

Add meeting notes and Progress Report

Post Philosophy NOT Emailed by Mark

Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28

Extended Link prototype

Pseudocode for ChangeStyle 3/4

Mark

Email philosophy NOT DONE

Email customer about using Jalopy's formatting style.

Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28

Emailed UI Prototype and User Manual

Pseudocode for ChangeStyleMenu? 3/ 4

Get pictures of Extended Prototype to Ian by 6:00 pm

Tracy

Send out meeting notes from 2/26/08 and 2/28/08 DONE

Action items

Redo schedule in wiki DONE

Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28

Changes Marks, Ian, Richard and Paul password change

Download Tortoise

Pseudocode for ChangeStylePref? ¾

Send Dalbey Extended Prototype.

Richard

Create a High level Design for ChangeStyle DONE

Pseudocode for RevertBackupAction? 3/4

Update High Level Design and send to Paul

Ian

Research feasibility of undo and other features in jalopy

Get together with Paul to go over ActionFormat?

Pseudocode for ChangeStylePreview? 3/4

Create links for pictures of Extended Prototype by Tomorrow Morning

notify Tracy to look over.

Paul

QA of High Level design

Compose FTR Checklist for High Level Design

Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28 DONE

Download Tortoise

Email format pseudocode format to all.

meet with Ian to over ActionFormat?

Pseudocode for ActionFormat? 3/4

Notes

High Level Design was moved to be due Tues, 3/11.

Detailed Design was moved to be due Thurs 3/11

FTR for High Level Design 3/6

Broke up Detailed Design

Name	Class
Richard	RevertBackupAction?
Ian	ChangeStylePreview?
Tracey	ChangeStylePref?
Mark	ChangeStyleMenu?
Stephanie	ChangeStyle
Paul	FormatAction?

FTR is on Thursday

UI Prototype link to feasibility for Setting Changes

Extended Prototype

Add other checkbox

Undo

Extended Prototype
- Mark - Get pictures by 6:00 pm

Ian Creates links for pictures by Tomorrow Morning

Turn in to Dalbey by 5:00 pm

Go over tortoise

Look over

Meeting Notes - 2/26/08

Reminder

UI Prototype

Check Meeting Notes for assigned tasks

Check and update tickets (if complete or not)

Steph

Add meeting notes and Progress Report DONE

Post Philosophy NOT Emailed by Mark

Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28
Add Class Diagrams to wiki, email form Richard.

Mark

Email philosophy and pic for SRS to Steph (by 2/10) NOT DONE

Email customer about using Jalopys formatting style. DONE
Compile User Manual and turned over to Tracy
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28
Email the customer the User Manual and UI Prototype.

Tracy

Send out meeting notes from 2/26/08

Action items
Redo schedule in wiki change FTR
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28

Richard

Create a High level Design for ChangeStyle Last min
Need to go over
Get together with Ian to go over Design and Prototype. DONE
Email Steph Class Diagrams
Look into detailed design and breaking it up
Add private methods to javadocs

Ian

Research feasibility of undo and other features in jalopy DONE

UI Prototype, cannot be a Power Point (2/26) DONE
Get together with Richard to go over Design and Prototype.
Compile Jalpoy Manual for ChangeStyle (2/20) NVM
Add formatting whole package to prototype.

Paul

QA User Manual DONE
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/28
QA High Level Design

Notes

High Level Design was moved to be due Tues, 2/26.
Detailed Design was moved to be due Thurs 3/7 NEED TO CHAGNE FOR FTR
UI Prototype and User Manual next Tues 2/26 DONE on website.
- Due to QA and changed key functionality. DONE
FTR for Detailed Design 2/5 Needs to be moved.
- FTR for Detailed Level Design

Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/26 All except Ian and Richard
May be able to deliever ChangeStyle like the UI Prototype in 2 weeks
Go over what features that Jalpoy can and cannot do again, confussion so needed to go.
Research Undo and how to do it.

Talk to customer confirm window is planned to not be included in two weeks. Undo is.
High Level Design due dtae is the same
Detailed Design Date is changed to 3/11
Take out Test Plans oof the shcedule
Email Customer with jar file
Email features of the Jalopy now crossrevences SRS
Two Quarters project.

Top Risks

- Time, other classes

- Customer feedback

- Shorting schedule due date of the project

- Coordination scheduling,

- Contacting groups for FTR's

- Familiarity for problem domain

Meeting Notes 2/21/08

Reminder

UI Prototype
Check Meeting Notes for assigned tasks
Check and update tickets (if complete or not)
Status Reports are due tonight at 8:00 pm.

Steph

Add meeting notes and Progress Report
Post Philosophy NOT Emailed by Mark
Edit Overview and Features Sections of User Manual (2/20) sent to Mark by Midnight.
Credits Page User Manual.
Prototype implementing Bluej with a reference file using Jalopy.
- Due Tues 2/26
Add Javadocs to Wiki. 2/26

Mark

Email philosophy and pic for SRS to Steph (by 2/10) NOT DONE
Editing the Preferences Section of the User Manual (2/19) DONE
Email customer about using Jalopy's formatting style. Attahed our ChangeStyle Prototype....rough draft.

Get together Tracy Mark to go over Design for UI Prototype DONE
- Email to Ian before Sunday Night (2/17) DONE
Compile User Manual
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/26 1
Add SRS to WIKI 2/26
Create Feature lists of Current ChangleStyle? to send to User.
- Add to Wiki. 2/26

Tracy

Send out meeting notes from 2/12/08 and 2/14/08 DONE
Send out meeting notes for 2/19/08
Progress Report
Action items
Redo schedule in wiki add RTF and change RTF
Edit Formatting Section of User Manual (2/20) sent to Mark by Midnight. DONE
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/26 2
Recomiple USer Manual add Changes - take over for Mark

Richard

High level Design for ChangeStyle (2/26)
Get together with Ian to go over Design and Prototype. DONE
Start work on Detailed Design

Ian

SICK

UI Prototype, cannot be a Power Point (2/26)
Get together with Richard to go over Design and Prototype.
Compile Jalpoy Manual for ChangeStyle (2/20)

Paul

Edit Requirements and Installation Sections of the User Manual (2/20) sent to Mark by Midnight.
QA User Manual
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/26 3
Contact Empty Set for FTR for THurs 2/28 for High Level Design

Notes

High Level Design was moved to be due Tues, 2/26.
Detailed Design was moved to be due Thurs 3/7
UI Prototype and User Manual next Tues 2/26
- Due to QA and changed key functionality.
FTR for Detailed Design 2/5
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/26 All except Ian and Richard
Went over User Manual - All need to edit with changes and add to wiki. Sent Mark by Midnight
Compile User Manual
RTF will be next THursday on High Level Design

Meeting Notes 2/19/08

Reminder

UI Prototype 2/14
- Check Meeting Notes for assigned tasks
Check and update tickets (if complete or not)

Contact and Contract for User Manual.

Steph

Add meeting notes and Progress Report
- Post Philosophy NOT Emailed by Mark
Edit Overview and Features Sections of User Manual (2/20) sent to Mark by Midnight.
Credits Page User Manual.
Prototype implementing Bluej with a reference file using Jalopy.
- Due Tues 2/26

Mark

Email philosophy and pic for SRS to Steph (by 2/10) NOT DONE

Editing the Preferences Section of the User Manual (2/19) DONE
Email customer about using Jalopy’s formatting style.
Get together Tracy Mark to go over Design for UI Prototype DONE
- Email to Ian before Sunday Night (2/17) DONE
Compile User Manual
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/26

Tracy

Send out meeting notes from 2/12/08 and 2/14/08 DONE

Action items
Redo schedule in wiki DONE
Edit Formatting Section of User Manual (2/20) sent to Mark by Midnight.
Get together with Mark to go over Design for UI Prototype DONE
- Email to Ian before Sunday Night (2/17) DONE
Prototype implementing Bluej with a reference file using Jalopy. Due Tues 2/26

Richard

Create a High level Design for ChangeStyle DONE - Need to go over
Get together with Ian to go over Design and Prototype.

Ian

Try to implement Jalopy with BlueJ Tues 2/12 DONE

UI Prototype xml/configuration file prototype complete (2/14)
- Research feasibility of undo and other features in jalopy
UI Prototype, cannot be a Power Point (2/19)
Get together with Richard to go over Design and Prototype.
Compile Jalpoy Manual for ChangeStyle (2/20)

Paul

Final QA of SRS DONE

Edit Requirements and Installation Sections of the User Manual
- (2/20) sent to Mark by Midnight.

QA User Manual
Prototype implementing Bluej with a reference file using Jalopy.
- Due Tues 2/26

Notes

Individual Sections (2/19) without pictures is okay, need to know

what pictures are needed though

High Level Design was moved to be due Tues, 2/26.
Detailed Design was moved to be due Thurs 3/7
UI Prototype and User Manual next Tues 2/26
- Due to QA and changed key functionality.
FTR for Detailed Design 2/5
UI Prototype - About how to format a whole package.
- "Format Package" is in "Tools".
- "Format Selected file" in "Tools"
- Formatting Double Panel window.
  - Checkbox "Applied to all", if need be.
  - Checkbox "Don’t show this again".
  - "edit" = “Edit Settings"

Change "Preferences" to "Custom Settings"
Where to save the backup files: original files. Only if a full class file. Most recent.

Project Folder/.csbackups/

Jalopy uses "Convention" we use "Style Preferences",
- "Convention File" to change "Style Preference Config File"

Undo...only works immediately right after formatting code.

Prototype implementing Bluej with a reference file using Jalopy.
- Due Tues 2/26 All except Ian and Richard
Went over User Manual - All need to edit with changes and add to wiki. Sent Mark by Midnight
Compile User Manual

Meeting Notes 2/14/08

Reminder

UI Prototype 2/14

Check Meeting Notes for assigned tasks

Check and update tickets (if complete or not)

Steph

Add meeting notes and Progress Report

Post Philosophy NOT Emailed by Mark

Overview and Features Sections of User Manual (2/19)

Mark

Email philosophy and pic for SRS to Steph (by 2/10) NOT DONE

Editing the Preferences Section of the User Manual (2/19)
Email customer about using Jalopy's formatting style.
Get together Tracy Mark to go over Design for UI Prototype
- Email to Ian before Sunday Night (2/17)

Tracy

Send out meeting notes from 2/10/08 and 2/12/08

Action items
Redo schedule in wiki
Formatting Section of User Manual (2/19)
Get together with Mark to go over Design for UI Prototype
- Email to Ian before Sunday Night (2/17)

Richard

Create a High level Design for ChangeStyle
Get together with Ian to go over Design and Prototype.

Ian

Try to implement Jalopy with BlueJ Tues 2/12 DONE

UI Prototype xml/configuration file prototype complete (2/14)

Research feasibility of undo and other features in jalopy

UI Prototype, cannot be a Power Point (2/19)
Get together with Richard to go over Design and Prototype.

Paul

Final QA of SRS DONE

Requirements and Installation Sections of the User Manual (2/19)

Notes

High Level Design (2/21)
Detailed Design (3/4)
UI Prototype (2/21)
User Manual (2/21)
Individual Sections (2/19) without pictures is okay, need to know what pictures are needed though
Test Plan (3/11)
Plan on (3/6)

Meeting Notes 2/12/08

Reminder

SRS DUE!!!!
- Complete SRS handin!!
- Hard Copy due T 4:00pm

Check Meeting Notes for assigned tasks

Check and update tickets (if complete or not)

Steph

Add meeting notes

Research limiting access to pages if not login
- Not possible

Post Philosophy
- NOT Emailed by Mark

Mark

Compile all parts of the SRS with updates and change
Email philosophy and pic for SRS to Steph (by 2/10) NOT DONE

completely finish fine combing SRS by Sat (2/9) and email to Paul NOT DONE
Had SRS for Sunday's meeting

Tracy

Send out meeting notes from 2/10/08 and 2/12/08

Action items
Redo schedule in wiki

Richard

Research Violet UML tool - DONE
Familiarize with Violet - DONE
Only problem is that it sets left most and upper most as the margins.

Ian

Try to implement Jalopy with BlueJ Tues 2/12

UI Prototype xml/configuration file prototype complete (2/14)

Research feasibility of undo and other features in jalopy

UI Prototype, powerpoint 2/14

Paul

Final QA of SRS

Notes

Went over final QA of SRS
User Manual

Meeting Notes 2/10/08

Reminder

Make sure to include time log hours. Go back and look to see if you have any zeros for time hours.
- Check Meeting Notes for assigned tasks
- Check and update tickets (if complete or not)

Steph

Add weekly status report and meeting notes
Fix wiki page Mark wanted
Research limiting access to pages if not login.
Post Philosophy
Credit Page post by Midnight 2/10

Mark

Compile all parts of the SRS with updates and change DONE
Email philosophy and pic for SRS to Steph (by 2/10) NOT DONE
- completely finish fine-combing SRS by Sat (2/9) and email to paul NOT DONE
Send SRS to Paul by Midnight 2/10

Tracy

Write tickets
Send meeting notes

Richard

Research Violet UML tool
Familiarize with Violet

Ian

Try to implement Jalopy with BlueJ Tues 2/12
- xml/configuration file prototype complete
research feasibility of undo and other features in jalopy

Prototype for highlighting?

Paul

Send VIOLET link to Richard DONE
QA of SRS prior to meeting on Sun

Notes

Names for Formatter
- ChangeStyle

What is highlighting? Could do diff?

Meeting

Prioritized SRS features and rules
Discussed Ian's configuration file prototype (xml in eclipse)
Discussed having different phases of prototype
- phase 1 : xml/configuration file
- phase 2 : GUI

Meeting Notes 2/7/08

Reminder

Check Meeting Notes for assigned tasks
Check and update tickets (if complete or not)
JALOPY will work !! :)

Steph

Add weekly status report and meeting notes
Fix wiki page Mark wanted
Research limiting access to pages if not login.
Post Philosophy

Mark

Compile all parts of the SRS with updates and change
Email philosophy and pic for SRS to Steph (by 2/10)
- completely finish fine-combing SRS by Sat (2/9) and email to paul

Tracy

SICK

Richard

Research Violet UML tool
Familiarize with Violet

Ian

Try to implement Jalopy with BlueJ Tues 2/12
- xml/configuration file prototype complete
research feasibility of undo and other features in jalopy

Paul

Have Introduction done by midnight and email to Mark
Send VIOLET link to Richard
QA of SRS prior to meeting on Sun

Notes

- Names for Formatter

we like ChangeStyle ; ask Tracy for approval on Sun.

- LabBook? recommendations:

No space between entries; use lines to separate
Don't include Meeting Notes
Date and label every entry
Have thorough explanations (of tasks completed, etc.)
Make sure include individual status report and that it follows template (with good explanations)

- Prioritized SRS features and rules - Discussed Ian's configuration file prototype (xml in eclipse) - Discussed having different phases of prototype

phase 1 : xml/configuration file
phase 2 : GUI

Meeting Notes 2/5/08

Reminder

Team SRS review – Mark
Go over jalopy if time - Ian
Look at Tickets

Steph

Add weekly status report and meeting notes
Look into SVN Tortoise - Can ask Ian/Richard if help
SRS External Interfaces – email to Mark DONE
Add a page for Mark to add Google group information
Research limiting access to pages if not login.
Post Philosophy

Mark

Complete first draft of the SRS due 1/31 - PROBLEM
- Divide work
SRS - Behavior and everything else due 2/5
Compile all parts of the SRS and add to wiki DONE
Email philosophy to Steph

Tracy

Weekly progress report

Create tickets (Look more into custom)
Meeting agenda plan.
If you want to do something during lab after the group meeting email me before 8:00 the night before
SRS Informational Requirements – email to Mark due 2/5 DONE

Richard

Looking at feasible prototype
Feasibility prototype for Jindent to bluej extension - Yes
- Cant because it is a commercial
- Break into different feasibility
Look for new formatting program to use due 2/5
Research UML tool

Ian

Feasibility prototype for Jindent to bluej extension - Yes
- Cant because it is a commercial
- Break into different feasibility
Look for new formatting program to extend due 2/5 – Jalopy DONE
Try to implement Jalopy with BlueJ Thurs 2/7
- Document

Paul

Look at other manual and get general idea
SRS Introduction – email to Mark due 2/5 DONE

Notes

- Monospaced code - Style Formatter not Beautifier

- Names for Formatter

- Sunday meeting for SRS Final overview noon - Library - UI Prototype is due sometime as feasibility prototype

Meeting

Team SRS review
Mark took over
- Individually looked at Part so SRS

- Jalopy – version 1.5

take core and put a User interface on it
Setting on xml file
External interface when open in eclipse
Side by side original and new

Meeting Notes 1/31/08

Reminder

Look at Tickets
Individual Status Report
If you want to do something during lab after the group meeting email me before 8:00 the night before

Steph

Add weekly status report and meeting notes
Edit already existing changed manage plan with what was discussed in class
- Will add as changes come about
Add open sources code for checkstyle link to web DONE
Look into SVN Tortoise - Can ask Ian/Richard if help
SRS External Interfaces – email to Mark

Mark

Complete first draft of the SRS due 1/31 - PROBLEM
- Divide work
SRS - Behavior and everything else due 2/5
Compile all parts of the SRS and add to wiki

Tracy

Weekly progress report

Create tickets (Look more into custom)
Create template for individual status DONE
Add status "ongoing" DONE
Change percent of code to lines of code DONE
Add task item complete over task items DONE
Meeting agenda plan.
SRS Informational Requirements – email to Mark due 2/5

Richard

Looking at feasible prototype
Feasibility prototype for Jindent to bluej extension - Yes
- Cant because it is a commercial
- Break into different feasibility
Look for new formatting program to use due 2/5

Ian

Check/find source code for CheckStyle? DONE
- Open source - Send link to DONE

Feasibility prototype for Jindent to bluej extension - Yes
- Cant because it is a commercial
- Break into different feasibility
Look for new formatting program to exten due 2/5

Paul

Look at other manual and get general idea
looked at extensions in blueJ DONE
Look into manual layouts to get ideas for format (Sun)
Check to see if wiki format can be converter to doc/pdf DONE
SRS Introduction – email to Mark due 2/5

Notes

Can use JIndent for BlueJ
- Can be run in Java
- Add formatting to Jindent
- If they want to change
- Where the out file goes
Tear into eclipse if need be

Next meeting -

Team SRS review

Meeting Notes 1/29/08

Reminder

WE HAVE A CUSTOMER!!!
Look at Tickets
Read through lab notebook template

All

Read wiki format page
Check tickets once a day

Steph

Add weekly status report DONE
Edit already existing changed manage plan with what was discussed in class
Add open sources code for checkstyle link to web
Look into SVN Tortoise - Can ask Ian if need help

Mark

Complete first draft of the SRS due 1/31
Wiki/Send out to all one day turn over
Email Paul for check - DID NOT DO

Tracy

Weekly progress report DONE
Add/create time logs DONE
Type and look over general schedule Add to web DONE
Change user abilities in Trac DONE
Create tickets and learn for next meeting (Look more into custom)
Personal tickets DONE
Task to action items DONE
Create template for individual status
Add status "ongoing"
Change percent of code to lines of code
Add task item complete over task items

Richard

Looking at feasible prototype - After draft SRS
waiting for feedback

Ian

Check/find source code for CheckStyle? DONE
Open source - Send link to

Paul

Look at other manual and get general idea
Looked at extensions in blueJ
Look into manual layouts to get ideas for format (Sun)
Check to see if wiki format can be converter to doc/pdf DONE

Notes

Went over change control plan
Discussed change submit request ? will be added to website
Looked at SVN Tortoise
Tried changing notice values to true
- Did not send email
Looked into adding email notification to tickets

Meeting Minutes 1/24/08

Reminder

Bring ideas for user interface from assigned formatters; look at Feasibility and Difficulty
Individual Status Report DUE - put in lab note book
Look at Tickets
Read through lab notebook template
SVN Training

All

Read wiki format page --- help- guide

Steph

Add weekly status report
Will check if Trac can send out update on email (only for tickets)-DONE-not possible
Write/add to wiki change manager plan. 1/29

Mark

Contact Ian about JIndent and JIndentCustom for ideas (in class)
Integrate the SRS due 1/29
Will put SRS on Wiki on SAT
All can look at it - 1 day turn over
- Email Paul for check

Tracy

Weekly progress report

Add/create time logs
- Add schedule to web
- Create tickets and learn for next meeting (Look more into custom)
  - Personal tickets
  - Task to action items
  - Look at ownership

Richard

Looking at feasible prototype (After SRS draft)

Ian

Check/find source code for CheckStyle?

Work with Rickard to make a general prototype (Prolonged)
- tried basic bracket prototype

Paul

Look at other manual and get general idea
- looked at extensions in blueJ
Look into manual layouts to get ideas for format (Sun)
Check to see if wiki format can be converter to doc/pdf (DONE)

Notes

- SRS Common Features -- IDEAS --

MUST ASK for formatting - menu button
- After/when user wants
Temp copy of original and changed
Setting file
Custom Rules?
- Provide frame work
- Tags
Don't have to go through users interface
Side by side comparison
- One side rule using/ possible rules
Approve change
Different types of style options
Different indent - spaces/tabs
Formatting for brackets / blocks
NOT option -- HAS TO COMPILE!!!!
Pop up window "Warming: file does not Compiles!" Do you want to continue?
Format all
Keep backups - ask user if you want to save over/ keep backup
Change color of changed formatting
Changed comments
MAYBE in BlueJ- Option for different new line character for browser--Keep BlueJ's--
May want warnings
- ex/ import java.*
Same thing as checkstyle
Run checkstyle at same time -
How in detailed for brackets and indenting
- ex/ empty lines at end of file/method
try/catch different specs
Method sorting - only main
Javadocs
- Tags
- Template
Do all files at the same time ??
Error checking
- File not found
Enforce explicit define variables
Line Max

- SRS Quality

Possible 3 clicks to start
Change should but able to turn off/on
Easy to install - jar file
run on BlueJ
Mass process (mult file)
Support different type of class/interfaces

- Prototype

Reusing checkstyle
- Adding changes
Source code for checkstyle

Meeting Notes 1/22/08

Reminder

* Bring ideas for user interface - Feasibility and Difficulty

All

Fiddle around with eclipse and other ide's for formatting coding
Read wiki format page --- help- guide

Steph

Add weekly status report to website
Will check if Trac can send out update with email
Figure change manager plan
investigate AStyle and create its SRS with Feasibility and Difficulty (1/24)
12 hours a week

Mark

investigate Hammurapi and create its SRS with Feasibility and Difficulty (1/24)
Will Integrate the SRS from the individual (1/26)
- email Paul for check
10 hours a week

Tracy

Add weekly progress report
Add/create time logs
- General schedule due Thurs (1/24)
investigate JMetric and create its SRS with Feasibility and Difficulty (1/24)
- Create tickets and learn for next meeting (1/24)

Richard

Eclipse and create its SRS with Feasibility and Difficulty (1/24)
Looking at feasible prototype - After drafted SRS
10 hours include lab

Ian

Not here
- will email and ask why
And create its SRS with Feasibility and Difficulty (1/24)

Paul

investigate CheckStyle? and create its SRS with Feasibility and Difficulty (1/24)
10 hours include lab
Look at other manual and get general idea - looked at extensions
Look into manual layouts to get ideas for format (Sun)
Check to see if wiki format can be converter to doc/pdf

Notes

BlueJ and CheckStyle? conflict with errors - more in BLueJ
Manual will be on wiki and then transfer to pdf
Manual Format Tuesday 1/29
In BlueJ Manual
- Came with docs
  - Overview
  - Features
  - Download
  - Pictures in how to install
  - Requirements
  - Installation
  - Usage
  - Settings
    - user preference
    - shared lab
  - Contract
- Maybe
  - Examples
  - Tips and trick
  - Update
  - Include pictures
  - Updated extension
  - Contact

Meeting Notes 1/17/08

Reminder

* Individual review due tonight at 8 pm

* Include average Hours a week

* Steph – name tags

* Make sure can access Trac account

* Fiddle around with eclipse other ide's for format

All

Individual review due tonight at 8 pm
Make sure can access Trac account
Fiddle around with eclipse and other ide's for formatting coding
Ideal Top Ten Risk - Tues

Steph

Name Tags - Tues
Will look into website - start/learn/update
Add vision and Team expectations to web

Mark

Create graphical Logo - Tues
- Will email to Steph asap

Tracy

Talk to prof about emailing progress reports – due Fri at 5:00 pm
Add/create time logs
Type and look over general schedule
Change user abilities in Trac

Richard

Work with Ian to make a general protoype for Tues

Ian

Work with Rickard to make a general protoype for Tues

Paul

Look at other manual and get general idea

Notes

Ideas for Prototype
- Need something that will take code and format
  - look at eclipse style coding
  - need tab size
- Idea change Checkstyle to change at end
  - add methods instead of printing error comment
Went over general schedule
Came up with Team expectations and vision – on website -Steph
Will go over feasible prototype on Tues 1/22
Web general/basic training on Thurs 1/24

Download in other formats:

Plain Text