LUNA Software, Stephanie Long, May 27th, 2008

Team Accomplishments:

We successfully released our maintenance stage work. Paul created an integration plan, which I posted on the wiki. We began integration on Monday and will finish by Wednesday. We finished writing the code we had for Stage 2.0 and exchanged work to complete Inspections on the code. We completed inspections and met with the other team members to discuss our findings. Richard created automated scripts for Stage 1.0 functional requirements. I distributed basis paths tests for the team to complete. Everyone was reminded of past items to still complete, we have been having a lot of late action items.

Unfinished Tasks:

We need to finish Integration and testing the changes.

This next week we need to finish EVERYTHING.

This weekend I plan, with Ian, to QA everything by Sunday so there is no last minute work to do on Monday.

Schedule Revisions:

none

Group Problems:

Members have not been completing work when asked. System tests and junit tests are far past due.

Late Weekly Hours Reports:

Tracy

LUNA Software, Stephanie Long, May 19th, 2008

Team Accomplishments:

We completed the work to release stage 1.1 including changing the user manual (adding a new section), fixing the drop down box to not hide a label, fixed the xml files, and adding a help link. We also completed system tests and unit tests when appropriate. Richard ran through all the tests and made sure if any didn't pass that they were fixed. He updated the System test cases matrix, wiki page, and results wiki page. He also submitted a change request to omit a requirement that isn't testable. Ian finally posted the QA plan on the wiki. I changed the unit tests link to point to the unit tests for stage 1.1. I posted the last weekly status report and meeting minutes for the week on the wiki. Everyone finished up the defect homework assignment which we had all done incorrectly. Everyone was supposed to begin work on Stage 2 unit tests, system tests and then coding. Richard got the batch undo functionality to work and got up a prototype. He also researched EMMA and completed the tutorial. Ian added our universal BClass to use for testing to the repository. We also came up on a final decision for how to organize the repository.

Unfinished Tasks:

Update visibility calculations with last two weeks totals for stage 1.1 release.

I think Paul still needs to finish creating the automated daily build.

Most of the team still needs to complete system tests and unit tests and complete their requirements coding by Wednesday so we can have inspections on Thursday.

I think Tracy still needs to complete the release notes for the stage 1.1 release.

Schedule Revisions:

changed column names and updated coloring

Group Problems:

Members have not been completing work when asked:

The only people to complete the stage 2 system test cases on time was Myself.

Only Paul completed unit tests for stage 2.0 on time.

They all know when Hours Reports are due to me (Sunday evening by 8) and no one turned them in on time. The only person to even submit it to me on Sunday was Richard.

I am weary of the group not giving as much time. Other classes are getting more demanding and so is this class.

Late Weekly Hours Reports :

Ian, Paul, Mark, Tracy

LUNA Software, Stephanie Long, May 12th, 2008

Team Accomplishments:

We finalized the delegation of the maintenance work and the new requirements for this stage. We also removed the requirement 5 for this stage after realizing it isn't feasible. Ian created a UI prototype for how we want our extension to be presented in the preferences panel. It is available on the wiki.

Paul and Ian made tutorials for new tools we are required to use for this release.

Mark rebranched the repository correctly and had to make a few corrections on the rebranch. He also set the severity and component fields on trac (very late).

I announced to the team that each person needs to write system test cases and scripts and unit test cases for their new requirements. I layed out the schedule to follow for the team over the next few weeks so we can incorporate everything that needs to happen in a timely manner.

Ian created a universal test class for us to use in unit testing the new requirements.

Tracy updated the staged delivery plan with the new requirements.

Unfinished Tasks:

Complete the homework due last week which was completed incorrectly.

Update visibility calculations with last weeks totals.

Finish up the maintenance work for release 1.1 and test it.

Paul needs to automated the daily build by Tuesday.

Tracy needs to submit a change request for the changes to the User Manual for stage 1.1

Schedule Revisions:

finalized schedule after figuring out flow/order of work

Group Problems:

Getting members to submit weekly hours reports on-time and responding to management emails. It is week 7 and I only had one team member who remembered to submit their hours report. I don't want to have to send emails out as reminders every week. I did for the first 5 weeks.

I am weary of the group not giving as much time. Other classes are getting more demanding and so is this class.

Being familiar with all the new testing techniques required for this release.

Late Weekly Hours Reports:

Ian, Paul, Mark, Richard

LUNA Software, Stephanie Long, May 5th, 2008

Team Accomplishments:

We finished and finalized all the documents for the release meeting last week. At the release meeting, after a stressful 50min we successfully corrected 3 bugs which would've held us back from acceptance, but we did it! After lots of stress and hard work, it paid off. This is a major accomplishment in my book.

We had a little cookie party, thanks to me... To reward the team and keep morale high.

We decided on what tasks we wanted to include in our maintenance portion of the release and finalized the requirements for Stage 2.0 release. I asked the team to send me their top three choices for requirements, but only two people responded so I will delegate tasks accordingly tomorrow at the meeting.

Members of the team conducted feasibility research and created prototypes for the Stage 2 requirements and will report their findings at the next meeting.

The wiki is completely up to date for the Stage 1 release, including visibility calculations and links.

Unfinished Tasks:

We need to finalize the dispersement of the requirements and discuss Mark's sudden requirement proposal.

We also need to disperse the maintenance work.

We need to review the prototypes create for the new requirements.

Everyone needs to familiarize them-self with what is expected from their role for stage 2.

Need to create schedule to this stage. We need to get started with this stage's requirements... I don't want to be rushed like last time..

Make sure all problems from release are identified and fixed.

Schedule Revisions:

need to create new schedule for stage 2

Group Problems:

Getting members to submit weekly hours reports on-time and responding to management emails.

I am weary of the group not giving as much since we release stage 1 on time... I don't want them getting too comfortable.

Late Weekly Hours Reports :

Tracy, Mark, Richard

LUNA Software, Stephanie Long, April 28th, 2008

Team Accomplishments:

Finished making reports with due dates (defect report as well) and made tickets for meeting action items. I posted the meeting minutes for the weeks meetings and posted the last to weekly progress reports on wiki.

Members completed Unit Testing (some couldn’t due to BClass/BlueJ creation failure), with JUnit and Abbot. Mark finally completed and turned in his system test cases.

I asked each member to estimate the weekly defect count and report back to me so I could finish completing the visibility calculations pages.

Added Change Requests for defects and changes to SRS requirements and approved them as team.

Conduct code inspections and complete prep work then rework code as needed.

Each Team Member completed their particular jobs for release:

Add wiki pages for system test cases, results, matrix, and unit tests. Richard created these pages and posted all current information for Stage 1.0 release. Ian and I met for a final QA session on Sunday and worked on gathering empirical data and figuring out exactly what needed to be done for the release. Ian and I compiled the binder for release; I created the table of contents and all the section headers. I also numbered the pages and separated them with stickies for easy navigation. Tracy updated the SRS, the Stage 1.0 User Manual (which Mark took pictures for), release notes for stage 1 release and created a README.txt file to include with the download. Paul is continuing daily build and finalized the procedure and updated the correspondin g pages for the Stage 1.0 Release. Richard ran our system tests and unit tests and documented the results.

Everyone prepared for the initial release, sending system test cases, their sections of code to be printed out, their inspection documentation, and any unit tests.

Unfinished Tasks:

Currently we (Ian, Richard, and I) will do a final check of all the requirements for the Stage 1 release before 7pm (the meeting time).

Schedule Revisions:

Push back JUnit Test Cases Luna Due Date

Group Problems:

Getting members to submit weekly hours reports on-time.

We had problems with certain members not completing their system test and JUnit tests on time which delayed testing and QA.

Late Weekly Hours Reports :

None

Hours for Week 3:

Stephanie – 18

Paul – 16

Ian – 14.5

Richard – 14

Mark – 9

Tracy – 8.25

LUNA Software, Stephanie Long, April 21th, 2008

Team Accomplishments:

Each member on the team completed System Test Cases that were assigned to them, due by Sunday 20th (deadline extended, Mark LATE). We had issues understanding how to complete the cases but we split up the non-functional requirements between Tracy, Mark, Ian, and Paul while Richard and I completed tests for the functional requirements. In trying to complete this assignment the team realized many changes are needed to be made to SRS so we decided on those changes and began the Change Control process. Mark was alerted to make change requests for the changes. Tracy was notified to make these changes asap.

Each member on the team completed Jalopy Tests that were assigned to them, due by Sunday 20th at midnight to Tracy (Mark LATE).

Each member was asked to create an estimate time schedule for the prospective requirements. After consulting the lists, we decided which requirements to implement and split up the code.

I revised the schedule to reflect the next two weeks and the deliverables for Stage 1.0. Due to having to rewrite requirements, more editing is needed for the System Tests due date.

I created new field on trac tickets and created a query. I plan to make more reports but was waiting until I cleared up the issues I was having with the reports (did that today at office hours).

Unfinished Tasks:

Rewrite the Stage 1.0 requirements to be testable.

Make corrections to SRS Functional and Non-Functional Requirements.

Code assignments for Stage 1.0

Inspections for Stage 1.0

Unit Tests for Stage 1.0

Complete System Tests/ Integration Tests on code

Final QA of Stage 1.0 materials

Create more reports reflecting Luna Due Date

Update the visibility calculations

Schedule Revisions:

Push back Luna Due Date for system test cases (done, but needs to be edited again due to requirements rewrite)

Set final Luna Due Dates for code, inspections, tests

Group Problems:

Getting members to submit weekly hours reports on-time.

We had problems with poorly written SRS requirements for testing.

Even though plenty reminder emails were sent out, the not everyone on the team submitted work ontime.

Late Weekly Hours Reports :

Mark submitted a late weekly hours report.

Hours for Week 3:

Stephanie – 11.5

Paul – 10

Ian – 8.25

Richard – 11

Mark – 0 (did not recieve report)

Tracy – 8.25

LUNA Software, Stephanie Long, April 14th, 2008

Team Accomplishments:

Mark reorganized the repository and branched the project. I posted each meeting's notes and created tickets for all assigned tasks, which is done every week. Ian created a mini jar assignment so that each member of the team would feel comfortable creating a jar file in eclipse. Paul determined the current LOC count for the project (with and without comments). Paul also went through the old code and made sure it followed coding standards (psuedocodes and commenting). Tracy fixed the User Manual picture which was causing issues. Ian reviewed Jalopy's requirements and created a list of tests (300) which need to be preformed. I sent Richard a rough version of the Stage 1 Requirements so he could create system test cases, I also had to change the link to the SRS to point to the new spot in the repository. I compiled the team's risks lists and posted them on the wiki. I fixed the release page to point to the proper version of the changestyle jar file and had to do some manipulations on the repository (when Mark reorganized the repository these changes were trashed). I updated the visibility calculations on the wiki page and also the actual page with the tables, I also created a new table which follows your (Dr. Dalbey) template. Ian and Mark are doing feasibility testing for putting help in the settings dialog vs. tooltips. Paul is testing the feasibility of having a formatting option which inserts a default for a switch statement. Tracy added the customers notes from the analyst meeting to the wiki and created the requirements list for Stage 1.0. Mark created a current build section to the wiki to get the latest build of ChangeStyle. Mark updated the change control plan and created and posted the change requests for the changes already made to the 0.1 version.Mark also created a Defect Weekly Report Log.

Unfinished Tasks:

Split up the Systems Tests and Jalopy Tests. I need to fix the visibility calculations for this past week. I also need to figure out how to report our batting average table calculations. The QA, Test, and Implementation Manager need to tell me what exactly they need to complete their duties for the Stage 1 release. The corrections I made to our initial release need to be identified in the Defect Tracking System. This includes finding out how to add more fields to the tickets through the trac.ini. Tracy and Paul still need to complete Ian's mini jar assignment. After reviewing Paul, Mark, and Ian's feasibility prototypes for the stage 1 requirements, we need to split up and complete the code to meet the requirements.

Schedule Revisions:

None yet. I plan to have you (Dr.Dalbey) look over it in the next lab.

Group Problems: Tracy's computer developed a problem over the weekend. Her motherboard isn't connecting to the wireless internet card so she can't access the internet. She is having to send it to the manufacturer and it will be gone for at least two weeks. This issue needs to be considered in giving assignments. Tracy kept me posted all weekend and I suggested she rent one from the department but I don't know if she will. (I spoke about this with you already) Getting members to submit weekly hours reports on-time. I had asked all the team members to create a risks list and bring to class, everyone but Richard completed this task.

Late Weekly Hours Reports :

Mark and Richard submitted late weekly hours reports.

HOURS FOR WEEK 2:

Paul - 7 hours

Tracy - 6.75 hours

Richard - 7 hours

Ian - 7.5 hours

Mark - 6 hours

Stephanie - 8.25 hours

LUNA Software, Stephanie Long, April 7th, 2008

Team Accomplishments:

This week our team released it's initial release of ChangeStyle. We had to finish coding the first release so we assigned different requirements to each team member. Paul was responsible for learning how to combine all the libraries and files needed to create the jar file. Tracy was responsible for changing the description and URL in the about box. Richard was responsible for handling the Undo functionality. Ian was responsible for putting the code into the framework and get it working.With some minor issues we completed the first version, but the issues deemed it not ready for release. Mark created the download page for the jar file, following Fish Bowl Games' template. Tracy wrote the first release notes with the known issues and I updated the known issues after becoming aware of a few more. I corrected all the issues brought up after meeting with you (Professor Dalbey), except for the Undo functionality.

Our group switched jobs this week. I am now the Team Manager, Mark is now the Change Manager, Tracy is the Analyst, Paul is the Design/Implementation Manager, Ian is the QA Manager, and Richard is the Test Manager. I changed the wiki permissions for Mark and Tracy so that their access was proper for their position. I also changed the email address from which the tickets come from, so it says my email instead of Tracy's.

Mark and Tracy set up the repository so the Preliminary and Stage 0.1 User Manual is in the repository.

Mark updated the website to reflect the change to name this release 0.1. Tracy double checked to make sure all the updates for last quarter she was responsible for, like the visibiliity calculations, was updated on the wiki.

I posted each meeting's notes and created tickets for all assigned tasks, which is to be done promptly, every week. I also made new nametags for the team as well.

Unfinished Tasks:

The Undo Functionality of the ChangeStyle extension we have created was not finished in time for the initial release of the product. Unfortunately, Richard's computer hasn't been up and working all week so he was not able to complete the code to support the functionality.

Tracy was assigned to post an updated picture to the Stage 0.1 User Manual. She posted the picture but the image isn't showing up on other computers. Tracy recognized this issue in the ticket explanation but I noticed it still hasn't been resolved.

Mark needs to write up two change request proposals. One for the change to the stage 0.1 requirements for the compiled requirement. The second is for the change to the stage 0.1 user manual's picture.

After coming into your office today, I need to revert the ChangeStyle jar file to the one which was released on Thurs. and need to create a new folder in the repository for the release jar files. I also need to . I am now more clear on some of my responsibilities. This coming week, I know I need to know the Project Plan inside and out, and need to put in the few updates for this project. I also need to write up the new schedule and update the visibility calculations page.

I need to delegate the task of Risk Manager. I will take over the task if at the Team Meeting no one wants to.

I need to talk the the implementation manager about their responsibilities and and about counting the lines of code for the project since we now have lines of working code. This week I plan to assign the Test Manager and QA Manager to become complete familiar with their corresponding plans, they need to know these plans inside and out.

The corrections I made to our initial release need to be identified in the Defect Tracking System.

Schedule Revisions:

I have yet to create the schedule for this quarter's project. I plan to create a schedule later this evening to bring to have you (Professor Dalbey) look over.

Group Problems:

When we divided up the coding tasks for the initial release, we gave Richard the Undo Formatting requirement. Due to computer problems he did not complete this code by the midnight deadline on wednesday. He says he updated the files before the three o'clock deadline I made for him (if he did I was going to quickly make a jar file to post before the 3:30 deadline) but I didn't see any evidence of that when I checked the repository at 3:10. After the deadline and when I changed the other issues, I checked if the Undo functionality was working and it still wasn't. A part of me thinks that even though his computer wasn't working, he could have came to school and worked on it in the lab to make sure he made his deadline, I did not communicate this with him though.

A problem is getting members to remember to submit their weekly hours to me by 8pm on Sundays.

It is going to take work to maintain everyone being on the same page for the project and to complete understand their tasks and responsibilities, but it is my job to make sure this is done. It is a main priority for me.

Late Weekly Hours Reports :

Note: This quarter our team has adopted a policy to heavily update comments on our trac tickets instead of submitting a individual status report. I am requiring the team to send me an email with the hours they contributed over the past week by Sundays at 8pm.

Tracy and Richard submitted late weekly hours reports.

Luna Software – 3/7/08

Team Accomplishments:

- Turned in Extended Prototype (2/29/08)

- Divided ChangeStyle class to individual team members to pseudocode for the detailed design.

- Post Team Philosophy on website.

- Update schedule on website

- All except Ian and Richard need to make a prototype implementing BlueJ with a reference file using Jalopy. (2/26/08)

- Create a tutorial with screenshots on how to use Tortoise.

- Compose a FTR Review Checklist for our FTR Review of High Level Design. (3/04/08)

- Had a FTR Review Meeting and wrote a FTR Summary Report for High Design. (03/06/08)

- FTR Empty Sets SRS (3/6/08)

- Changed everyone’s password on wiki, so that it is easier to login in.

- Added emails to Trac, so we can receive ticket information

- Wrote pseudocode for all classes of ChangeStyle for Detailed Design

- Changed format of SRS on wiki.

- Added Download link to wiki.

Unfinished Tasks:

- All except Ian and Richard need to make a prototype implementing BlueJ with a reference file using Jalopy. (2/26/08) Mark - LATE

- QA checklist for the High Level Design.

- QA Review Checklist of High Level Design (3/11/08).

- QA Review Checklist of our Detailed Design (3/11/08).

- Rework High Level Design with comments from FTR.

- Meet again with TWAIN to shortly review rework of High Level Design

- Summarize the FTR Review with TWAIN

- Check Detailed Level Design for correctness and consistency

- Rewrite pros/cons of features we are not implementing

- Create complete Change Plan Form

- Write Download page information.

Schedule Revisions:

- NONE

Group Problems:

- Receiving all individual status reports on time.

Late Status Reports:

- Mark

- Ian

Luna Software - Weekly Status Report – 2/29/08

Team Accomplishments:

- Completed a rough draft of the High Level Design.

- Created UML diagram for High Level Design

- Turned in complete and finalized User Manual (2/26/08).

- Reviewed SRS Functional requirements to see if Jalopy can match them.

- Turn in complete and UI Prototype. (2/26/08)

- Create a High Level Design of ChangeStyle.

- QA checklist review of User Manual.

- Set up a FTR with TWAIN to review our High Level Design on 3/6.

- Set up FTR to review Empty Set on 3/6.

- Complete final draft of the High Level Design and UML diagram.

- Create Feature lists of Current ChangleStyle? features send to Customer. 2/26

- Email customer about Jalopy’s covering the SRS Requirements.

- Divided ChangeStyle class to individual team members to pseudocode for the detailed design.

- Completed Extended UI Prototype.

Unfinished Tasks:

- Post Team Philosophy on website. LATE

- Update schedule on website

- All except Ian and Richard need to make a prototype implementing BlueJ with a reference file using Jalopy. (2/26/08) - Create a tutorial with screenshots on how to use Tortoise.

- Compose a FTR Review Checklist for our FTR Review of High Level Design. (3/04/08)

- Have a FTR Review Meeting and write a FTR Summary Report for High Design. (03/06/08)

- Create a QA checklist for the High Level Design.

Schedule Revisions:

- NONE

Group Problems:

- Receiving all individual status reports on time. - Getting the Philosophy on wiki, is not a blockage but has been late for 4 weeks.

Late Status Reports:

- Mark

Luna Software - Weekly Status Report – 2/22/08

Team Accomplishments:

- Add meeting notes 2/14/08, 2/19/08, and 2/21/08 to website.

- Completed individual parts of User Manual.

- Team review of the User Manual.

- Team’s changes and edits were added to the User Manual.

- Compiled parts of User Manual.

- Added User Manual, UI Prototype, High level Design, Detailed Level Design, and Testing Plans to the schedule.

- Completed a rough draft of the High Level Design.

- Created UML diagram for High Level Design

Unfinished Tasks:

- Turn in complete and finalized User Manual (2/26/08).

- Reviewed SRS Functional requirements to see if Jalopy can match them.

- Post Team Philosophy on website. LATE

- Update schedule on website

- Create a High Level Design of ChangeStyle.

- Extend UI Prototype with team design. (2/26/08)

- QA checklist review of User Manual.

- Setting up a FTR with Empty Set to review our High Level Design, waiting for contact from Empty Set.

- All except Ian and Richard need to make a prototype implementing BlueJ with a reference file using Jalopy. (2/26/08)

- Create complete final draft of the High Level Design and UML diagram.

- Create Feature lists of Current ChangleStyle? to send to User. 2/26

- Email customer about Jalopy’s covering the SRS Requirements.

Schedule Revisions:

- NONE

Group Problems:

- Receiving all individual status reports on time.

Late Status Reports:

- Ian

Luna Software – Weekly Status Report – 2/15/08

Team Accomplishments:

- Add team cost/time log to website and configure percent used.

- Add meeting notes 2/7/08, 2/10/08, and 2/12/08 to website.

- Divided User Manual into to individual parts.

- Turn in complete and finalized SRS (2/12/08) at 4:00 pm.

- Team meeting of review of Final SRS Sunday 2-10-08 and Monday 2-11-08.

- Prototype of Jalopy embedded into to BlueJ.

- Prototype of ChangeStyle with Jalopy’s style preferences, formats code into another file.

- Researched Violet as a team UML Diagram Tool and agreed on usage.

- Preliminary QA check of SRS (2/9/08)

- Confirmed QA of SRS for submission (2/11/09)

- Added User Manual, UI Prototype, High level Design, Detailed Level Design, and Testing Plans to the schedule.

Unfinished Tasks:

- Researching notification emails of tickets to only owners.

- Reviewed SRS Functional requirements to see if Jalopy can match them.

- Post Team Philosophy on website.

- Update schedule on website

- Create a High Level Design of ChangeStyle.

- Extend UI Prototype with team design.

- Individual parts of the User Manual. (2/19/08).

- Complete User Manual and UI Prototype (2/21/08)

Schedule Revisions:

- NONE

Group Problems:

- Receiving all individual status reports on time.

Late Status Reports:

- Richard – email sever was down.

- Mark

- Paul

Luna Software – Weekly Status Report - 2/8/08

Team Accomplishments:

- Using Trac Tickets for task/assignments

- Add beginning SRS to trac website

- Add team cost/time log to website and configure percent used

- Add meeting notes 2/1 to website

- First draft of the SRS due 1/31

- Research manual for related code formatting software

- Integrate the individual SRS and team ideas for SRS (2/5/08)

- Update schedule on website

- Looking into over formatters that are open source – Jalopy

- Review combined SRS (2/5/08)

- Determine that Jalopy is possible to integrate into BlueJ

- Updated Team Logo on website

Unfinished Tasks:

- Complete and finalized SRS (2/12/08)

- Research and create a feasible prototype without customer’s specs

- Researching notification emails of tickets to only owners

- Look into SVN to help track tickets and webpage

- Team meeting of review of Final SRS 2-10-08

- Prototype of Jalopy embedded into to BlueJ

- Reviewed SRS Functional requirements to see if Jalopy can match them.

- Researching Violet as a team UML Diagram Tool

- Preliminary QA check of SRS (2/9/08)

- Confirmed QA of SRS for submission (2/11/09)R

- Research if Trac can hide pages from people who are not login

- Post Team Philosophy on website

Schedule Revisions:

- NONE

Group Problems:

- Receiving all individual status reports on time.

- Time management issues with other classes and members saying they can do the work, but not getting it done.

Late Status Reports:

- Mark

- Richard

Luna Software - Weekly Status Report – 2/1/08

Team Accomplishments:

- More complete and detailed schedule implemented

- Added and gave abilities to all group members for Trac website

- Using Trac Tickets for task/assignments

- Researched other code formatter: JMetric, JIndent, Hammurapi, Astyle, CheckStyle? and Eclipse

- Add beginning SRS to trac website

- Introduce and execute Change Management Plan (1/29/08)

- Researching CheckStyle? source code

- Add team cost/time log to website and configure percent used

- Add meeting notes 1/24, 1/29 and 1/31 to website

- Trac can email tickets to all users

- Changed users abilities to add ticket for task management

- Created Change Plan

- Add open sources code for checkstyle link to website

- Create template for individual status Report

- Feasibility prototype for Jindent to bluej extension cannot use because it is commercial

Unfinished Tasks:

- Write SRS

- First draft of the SRS due 1/31

- Research and create a feasible prototype without customer’s specs

- Research manual for related code formatting software - Researching notification emails of tickets to only owners

- Integrate the individual SRS and team ideas for SRS (2/5/08)

- Review Lab notebook example

- Look into SVN to help track tickets and webpage

- Looking into over formatters that are open source

- Review combined SRS (2/5/08)

- Update schedule on website

Schedule Revisions:

- Changed the SRS, User Manual, and Feasibility Prototype due date were all changed to a week later

- Schedule was checked by professor

Group Problems:

- Completing SRS on time - due date was moved back a week, problem solved

- Receiving all individual status reports on time

Late Status Reports:

- Ian

- Richard

Luna Software - Weekly Status Report – 1/25/08

Team Accomplishments:

- Generate and pass out name tags for all members of team.

- Graphically design the logo and add to website.

- Check user login for Trac website.

- More complete and detailed schedule implemented.

- Added and gave abilities to all group members for Trac website.

- Using Trac Tickets for task/assignments.

- Researched other code formatter: JMetric, JIndent, Hammurapi, Astyle, CheckStyle? and Eclipse.

- Add beginning SRS to trac website.

Unfinished Tasks:

- Add team cost/time log to website and configure percent used.

- Add meeting notes 1/24 to website.

- Write SRS Introduction and

- Research and create a feasible prototype without customer’s specs.

- Research manual for related code formatting software.

- Researching notification emails of tickets (1/29/08)

- Changing users abilities to add ticket for task management

- Integrate the individual SRS and team ideas for SRS - Review Lab notebook example.

- Introduce and execute Change Manager Plan (1/29/08)

- Researching CheckStyle? source code

Schedule Revisions:

- None.

- Schedule was checked by professor.

Group Problems:

- Receiving all individual status reports on time.

Late Status Reports:

- Mark

- Ian

- Paul

Luna Software - Weekly Status Report – 1/18/08

Team Accomplishments:

- We attained our group position, Project Manager: Tracy, Analyst: Mark, Designer: Richard, Implementation: Ian, QA: Paul - We established our team name, pizza, logo, expectations and vision.

- Planned a very broad schedule (will be reviewed and broken down).

- Added and gave abilities to all group members for Trac website.

- Added contacts, expectation, vision, and job description to Trac website.

Unfinished Tasks:

- Generate and pass out name tags for all members of team. (1/22/08)

- Graphically design the logo and add to website.

- Check user login for Trac website.

- Plan and change the broad schedule from meeting 1/17 into a more complete and detailed schedule. (1/22/08)

- Figure out and add to website cost/time log for the team. (1/22/08)

- Research eclipse and other ide’s that are coding formatting to get ideas. (1/22/08)

- Add meeting notes 1/17 to website.

- Research and create a feasible prototype without customer’s specs.

- Research manual for related code formatting software.

Schedule Revisions:

- None.

- Original schedule is in rough draft form.

Group Problems:

- Do not have any problems right now.

- Possible future problems: Certain members not wanting to put much time into this project. Will figure out what to do when/if it comes up.

Late Status Reports:

- Mark