Welcome
Project Description
Software Development Plan
Gantt Schedule
Specifications Document
Project Proposal
Design Document
Client Email
Teleconference Minutes
Status Reports
Team Meeting Minutes
Client Meeting Minutes
Team Pictures

Status Reports



+++ TEAM LIVERMORE STATUS REPORT 9/12/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

See Meeting Minutes for 9-9-97.

1.2 List of tasks completed

Developed a role for each team member.

Established a set meeting time.

1st. teleconference time established. ***

Contacted Client (see 1.5 for details)

1.3 List of tasks started

Research into X-windows.

1.4 List of delayed tasks

None.

1.5 List of any problem areas or questions that need resolution

An introduction email was sent to the client Friday with a proposed meeting time of Thursday at 10:45. He did not respond to the email, so we called him on the phone Monday and confirmed the meeting time personally. A detailed description has not yet been received, but we intend to request one from the client at the Thursday meeting.

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 2 HRS

azs - 2.5 HRS

nfc - 3 HRS

2.2 Hours spent in team meetings

ajw - .5 HRS

azs - .5 HRS

nfc - .5 HRS

2.3 Tasks completed

ajw - Scheduled Conference room for three weeks in hopes that the Thursday 10:45 meeting will be acceptable for the client on a permanent basis.

azs - Typed meeting minutes and emailed to group

nfc - Contacted client and confirmed Thursday 10:45 meeting time

2.4 Tasks started

ajw - Researched X-windows

azs - Researched X-windows

nfc - Researched X-windows

2.5 Tasks delayed

ajw - None

azs - None

nfc - None

2.6 Areas of concern

ajw - X-windows

azs - Planing meeting that do not conflict with anyone’s schedule

nfc - Contacting client and confirming 10:45 Thursday meeting time

*** Note: Teleconference successfully completed with client.

Meeting minutes will appear in the next status report.

SUBMITTED BY: nfc



+++ TEAM LIVERMORE STATUS REPORT 09/19/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

See Meeting Minutes for 09-11-97.

See Teleconference Minutes for 09-11-97.

See Meeting Minutes for 09-14-97.

1.2 List of tasks completed

Found the manuals for X-windows

Has a successful teleconference with the client Sent additional emails to client with questions to be answered(see 1.5 for details)

Completed Software Development Plan

1.3 List of tasks started

Requirements Capture

Web page

1.4 List of delayed tasks

None.

1.5 List of any problem areas or questions that need resolution

Two additional emails have been sent to the client. The first was the teams proposal to visit Livermore with the intent of allowing the client to direct his attention to his October 1st deadline and we visit after October 1st had passed.

The second email was requesting more information on the C++ "Standard template library" that the client says we will need to perform our work. So far we have not found the library and our system admin. requests more information(eg. exact .h file names to search for) to better search for it.

To date we have not received ANY email from the client, including the initial in depth project description we requested. We have a teleconference with the client tomorrow at 10:45am.

Perhaps he is waiting to answer our questions at that time.

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 5 HRS

azs - 7 HRS

nfc - 9 HRS

2.2 Hours spent in team meetings

ajw - 2.5 HRS

azs - 2.5 HRS

nfc - 2.5 HRS

2.3 Tasks completed

ajw - Gantt Schedule, Coauthor of Development Plan Document

azs - Meeting Minutes, Coauthor of Development Plan Document

nfc - Status Report, Coauthor of Development Plan Document

2.4 Tasks started

ajw - revision of Gantt schedule

azs - None

nfc - web page

2.5 Tasks delayed

ajw - None

azs - None

nfc - None

2.6 Areas of concern

ajw - \ all | Getting requirements for Specification Document by due date

azs - ------{ Quicker client communication/feedback

nfc - / |

SUBMITTED BY: nfc



+++ TEAM LIVERMORE STATUS REPORT 09/24/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

Our client meeting did not take place on Thursday as planned. However the client did email a response to ALL of our questions that we had emailed to him previously. Monday we threw around the idea of a added teleconference meeting with the client (before our next Thursday meeting), but scheduling of such a meeting between all parties was not possible.(we also realized that once the Disclosure agreement is signed the Teleconference meetings be more useful and informative for all)

See Meeting Minutes 9-18-97

See Meeting Minutes 9-21-97

1.2 List of tasks completed

Revision of Software Development Plan

Posted SDP on web page and informed client of its location

1.3 List of tasks started

Requirements Capture

Creating new Gantt Schedule (we plan to include more detail)

1.4 List of delayed tasks

None.

1.5 List of any problem areas or questions that need resolution

Still need STL, map software and map file

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 4.0 HRS

azs - 2.5 HRS

nfc - 3.0 HRS

2.2 Hours spent in team meetings

ajw - 2.5 HRS

azs - 2.5 HRS

nfc - 2.5 HRS

2.3 Tasks completed

ajw - Gantt Schedule

azs - Meeting Minutes

nfc - Status Report

2.4 Tasks started

ajw - Requirements Capture

azs - Requirements Capture

nfc - Requirements Capture

2.5 Tasks delayed

ajw - None

azs - None

nfc - None

2.6 Areas of concern

ajw - see 1.5

azs – see 1.5

nfc - downloading .mpp file may be a problem

SUBMITTED BY: Nathan



+++ TEAM LIVERMORE STATUS REPORT 10/3/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

See 1.5

See Meeting Minutes for 9-25-97.

See Teleconference Minutes for 9-25-97.

1.2 List of tasks completed

We have completed and handed-in the Specifications Document. It is available for viewing in HTML format or downloading in WORD format at the temporary web site:

http://www.cse.nau.edu/~nfc

1.3 List of tasks started

Project Proposal Document

1.4 List of delayed tasks

analysis of information to formulate accurate algorithm(see 1.5)

1.5 List of any problem areas or questions that need resolution

We were expecting the Disclosure Statements last Thursday so that we could receive the source code and begin analysis of the problem. Our next major paper deadline is 10-9-97 and requires that we propose a solution to the problem, but without the code and the time to absorb and analyze the problem we face requesting a push of the Project Proposal document. The teams hopes are high that things will pick-up since the October 1st deadline our client has been working on is now past.

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 5.5 HRS

azs - 5.5 HRS

nfc - 7.5 HRS

2.2 Hours spent in team meetings

ajw - 2.5 HRS

azs - 2.5 HRS

nfc - 2.5 HRS

2.3 Tasks completed

ajw - creation of a new Gantt Schedule, Spec. Doc.

azs - Meeting Minutes, Spec. Doc.

nfc - Status Report, Spec. Doc.

2.4 Tasks started

ajw - revise Specifications Document

azs - Start Project Proposal Document

nfc - continued updating and improvement of the web page

2.5 Tasks delayed

ajw - accurate analysis of the algorithm(see 1.5)

azs - accurate analysis of the algorithm(see 1.5)

nfc - accurate analysis of the algorithm(see 1.5)

2.6 Areas of concern

ajw - see 1.5, getting the trip

azs - see 1.5, getting into the plant

nfc - see 1.5

SUBMITTED BY: Nathan



+++ TEAM LIVERMORE STATUS REPORT 10/10/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

See M_Minutes_10-2-97, T_Minutes_10-2-97

1.2 List of tasks completed

Determined path to Livermore

Rented Rental Car

Requested and received approval for Project Proposal Document Push Request

Filled out and faxed security clearance to visit Lawrence Livermore

Resubmitted the Spec. Document

1.3 List of tasks started

Started Proposal so we would have initial work to discuss at the meetings

1.4 List of delayed tasks

We submitted a Push request to delay the Proposal Document

1.5 List of any problem areas or questions that need resolution

We decided not to make Hotel reservations and find a place to stay when we got there

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 5 HRS

azs - 6 HRS

nfc - 7.5 HRS

2.2 Hours spent in team meetings

ajw - 6.0 HRS

azs - 6.0 HRS

nfc - 6.0 HRS

2.3 Tasks completed

ajw - Gantt Schedule, Rewrite of Spec. Document

azs - Meeting Minutes, Rewrite of Spec. Document

nfc - Status Report, Rewrite of Spec. Document

2.4 Tasks started

ajw - Proposal Budget

azs - Proposal

nfc - continued updating and improvement of the web page

2.5 Tasks delayed

ajw - None

azs - None

nfc - None

2.6 Areas of concern

ajw - where to stay

azs - quickest route to Lawrence Livermore

nfc - involving Aasif in discussions

SUBMITTED BY: nfc



+++ TEAM LIVERMORE STATUS REPORT 10/17/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

The team departed Wednesday night at 11pm for Lawrence Livermore. We were able to spend both thursday night and the entire day Friday discussing the project. Based on this information we were able to produce a more accurate Proposal Document. we will also be updating the specifications document to reflect new information learned from the visit. Please see Revision 1.2 for the updated version.

See Client_Minutes_10-9-97, M_Minutes_10-9-97

1.2 List of tasks completed

Proposal Document

Trip to Lawrence Livermore

1.3 List of tasks started

"looks like" proposal

1.4 List of delayed tasks

None.

1.5 List of any problem areas or questions that need resolution

we will not receive the Bx editor for creating our X-Windows GUI

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 14

azs - 15

nfc - 35

2.2 Hours spent in team meetings

ajw - 9

azs - 9

nfc - 9

2.3 Tasks completed

ajw - Update Gantt Schedule

azs - Meeting Minutes

nfc - Status Report

2.4 Tasks started

ajw - revise Proposal Document

azs - revise Proposal Document

nfc - continued updating and improvement of the web page, revise Proposal Document, revise/rewrite the Specification Document

2.5 Tasks delayed

ajw - None.

azs - None.

nfc - None.

2.6 Areas of concern

ajw - >

azs - >>> getting oriented with STP

nfc - >

SUBMITTED BY: nfc



+++ TEAM LIVERMORE STATUS REPORT 10/24/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

See m_meeting_10-15-97.doc, m_meeting_10-19-97.doc, t_meeting_10-16-97.doc, t_meeting_10-21-97.doc

1.2 List of tasks completed

NONE

1.3 List of tasks started

"Looks Like" prototype

1.4 List of delayed tasks

NONE

1.5 List of any problem areas or questions that need resolution

Our Client has switched us from using X-windows to Motif.

In doing this our programming language has also changed from C++ to C.

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 3

azs - .75

nfc - 4.5

2.2 Hours spent in team meetings

ajw - 8.5HRS

azs - 8.5HRS

nfc - 8.5HRS

2.3 Tasks completed

ajw - Update Gantt Schedule

azs - Meeting Minutes

nfc - Status Report

2.4 Tasks started

ajw - Create STP project, Understanding Motif

azs - Understanding Motif

nfc - continued updating and improvement of the web page, Revision of Proposal

2.5 Tasks delayed

ajw -

azs - NONE

nfc -

2.6 Areas of concern

ajw -

azs - MOTIF!!!, Also see 1.5

nfc -

SUBMITTED BY: nfc



+++ TEAM LIVERMORE STATUS REPORT 10/31/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

See M_Minutes_10-23-97, M_Minutes_10-25-97, M_Minutes_10-28-97

1.2 List of tasks completed

"Looks like" prototype, Notebook update, initial workout of ALL OMT models

1.3 List of tasks started

all OMT models

1.4 List of delayed tasks

NONE

1.5 List of any problem areas or questions that need resolution

Getting files from TOM to begin analysis.

Getting the Proposal document finished and signed by all parties.

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 17 HRS

azs - 15 HRS

nfc - 15 HRS

kwt - 5 HRS

2.2 Hours spent in team meetings

ajw - 7 HRS

azs - 7 HRS

nfc - 7 HRS

kwt - 4 HRS

2.3 Tasks completed

ajw - Update Gantt Schedule

azs - Meeting Minutes

nfc - Status Report, Notebook update

kwt - catch up on project requirements

2.4 Tasks started

ajw - training team on OMT

azs - High level OMT

nfc - Dynamic OMT

kwt - continued updating and improvement of the web page, functional OMT

2.5 Tasks delayed

ajw - NONE

azs - NONE

nfc - NONE

kwt - NONE

2.6 Areas of concern

ajw - getting files from TOM

azs - switch between C and C++ language

nfc - all of the above!!

kwt - non-disclosure paperwork

SUBMITTED BY: Nathan



+++ TEAM LIVERMORE STATUS REPORT 11/7/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

The client was out sick for the week, so the teleconference was not scheduled.

No group meetings took place for the week, but members of the team did meet throughout the week to work on the OMT, Proposal, and Specifications Documents.

1.2 List of tasks completed

Initial design of the High level OMT was completed on paper

1.3 List of tasks started

Dynamic and Functional models have begun construction

Kevin began training the group on STP

1.4 List of delayed tasks

NONE

1.5 List of any problem areas or questions that need resolution

We were scared that we had miss communicated with the client about

the teleconference meeting time. (day light savings has begun, and

we thought we had screwed up our time tables)

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 14 HRS

azs - 14 HRS

nfc - 14 HRS

kwt - 14 HRS

2.2 Hours spent in team meetings

ajw - 2.5 HRS

azs - 2.5 HRS

nfc - 2.5 HRS

kwt - 2.5 HRS

2.3 Tasks completed

ajw - Update Gantt Schedule

azs - High Level OMT

nfc - Status Report

kwt - High Level OMT

2.4 Tasks started

ajw - Review of requirements for OMT presentation

azs - OMT stuff

nfc - OMT stuff

kwt - continued updating and improvement of the web page, OMT stuff, powerpoint presentation, revision of Specifications Document

2.5 Tasks delayed

ajw - NONE

azs - NONE

nfc - NONE

kwt - NONE

2.6 Areas of concern

ajw - Dynamic model is pretty big

azs - Dynamic model is pretty big

nfc - Dynamic model is pretty big

kwt - Dynamic model is pretty big

SUBMITTED BY: Nathan



+++ TEAM LIVERMORE STATUS REPORT 11/14/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

See M_Minutes_11-6-97, M_Minutes_11-7-97,T_Minutes_11-6-97, OMT_review

Tom provided us with example code

1.2 List of tasks completed

OMT presentation

1.3 List of tasks started

NONE

1.4 List of delayed tasks

Review of Toms example code

1.5 List of any problem areas or questions that need resolution

NONE

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - ?8HRS?

azs - 15HRS

nfc - 15HRS

kwt - ?10HRS?

2.2 Hours spent in team meetings

ajw - ????

azs - 4.5HRS

nfc - 4.5HRS

kwt - 4.5HRS

2.3 Tasks completed

ajw - High level OM

azs - Meeting Minutes

nfc - Status Report

kwt - Functional Document

2.4 Tasks started

ajw - NONE

azs - NONE

nfc - NONE

kwt - continued updating and improvement of the web page, powerpoint presentation, revision of Specifications Document

2.5 Tasks delayed

ajw -

azs -

nfc - revision of the proposal document.

kwt -

2.6 Areas of concern

ajw - NONE

azs - NONE

nfc - NONE

kwt - NONE

SUBMITTED BY: Nathan



+++ TEAM LIVERMORE STATUS REPORT 11/21/97 +++

ATTENTION: STATUS REPORT SHOWS WEDNESDAY TO WEDNESDAY ONLY

1. TEAM REPORT

1.1 General Summary of team meetings and progress made during the week

See M_Minutes_11-19-97, T_Minutes_11-13-97

1.2 List of tasks completed

Revision of Specs. Doc.

1.3 List of tasks started

Revision of OMT

1.4 List of delayed tasks

Revision of Proposal

1.5 List of any problem areas or questions that need resolution

We are still waiting for faxes from Tom.

2. INDIVIDUAL STATUS REPORT

Each team member must include the following

2.1 Hours worked on the project during the week

ajw - 0.0

azs - 1

nfc - 1

kwt - 10

2.2 Hours spent in team meetings

ajw - 2.0

azs - 4.5

nfc - 4.5

kwt - 4

2.3 Tasks completed

ajw - Update Gantt Schedule

azs - Meeting Minutes

nfc - Status Report

kwt - Proposal, Specs, OMT update

2.4 Tasks started

ajw - Works Like

azs - Works Like

nfc - Works Like

kwt - continued updating and improvement of the web page, powerpoint presentation, revision of Specifications Document, Works Like

2.5 Tasks delayed

ajw - NONE

azs - NONE

nfc - NONE

kwt - NONE

2.6 Areas of concern

ajw - executing the code from Tom

azs - NONE

nfc - NONE

kwt - Disclosure agreement

SUBMITTED BY: Nathan