[6] in Athena_Backup_System

home help back first fref pref prev next nref lref last post

[tjm@MIT.EDU (Tim McGovern): Re-starting the Athena Backup System Project...]

daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Thu Jun 30 16:43:15 1994

To: athena-backup-mtg@menelaus.MIT.EDU
Date: Thu, 30 Jun 1994 16:43:07 EDT
From: Jonathon Weiss <jweiss@MIT.EDU>


The WBS tim refers to is transaction 5 of this meeting.

------- Forwarded Message

Received: from MIT.MIT.EDU by e40-po.MIT.EDU (5.61/4.7) id AA21118; Thu, 30 Jun 94 16:26:02 EDT
Received: from NEGRIL.MIT.EDU by MIT.EDU with SMTP
	id AA09074; Thu, 30 Jun 94 16:26:01 EDT
Message-Id: <9406302026.AA09074@MIT.EDU>
Date: Thu, 30 Jun 94 16:25:33
From: tjm@MIT.EDU (Tim McGovern)
To: jweiss@MIT.EDU, delgado@MIT.EDU, dkk@MIT.EDU, salemme@MIT.EDU
Subject: Re-starting the Athena Backup System Project...
Cc: kim@MIT.EDU


        [JW: Once the discuss meeting is up, this can go in as well...]

Today, we re-constituted the team for the project that we now call the Athena 
Backup System project.  We assessed where we were, and then mapped out where we 
are going in the short-term.   

Here are the results of our first meeting.

1.  The Team...

                   Project Leader:  Tim McGovern
           Sr. Technical/Designer:  Diane Delgado
                       Programmer:  Jonathon Weiss
         Customer Representatives:  Anne Salemme
                                    David Krikorian (not present)

    For lack of anything better, we agreed to use the Work Breakdown 
    Structure (WBS) that Jonathon had previously developed, and which has been 
    posted to the discuss meeting as transaction [0000].

2.  Where are we...
        
    Using the WBS, we determined that we have 

        - completed the REQUIREMENTS phase
        - written a HIGH LEVEL DESIGN document, but it needs to be
                reviewed again by the team, and then with key DCNS 
                technical experts.

        In the course of coming to this conclusion, we identified a 
        number of the key issues that we need to resolve.  The action
        items that resulted from that discussion are listed below.

3.  Where are we going (short-term)...

    Our goal is to produce a demo-able prototype of the new system as soon
    as possible.  To do that, we first need to finalize a HIGH LEVEL DESIGN
    document.  With that done, we will be able to fine-tune the WBS in the
    area of LOW LEVEL DESIGN and then move quickly to code the prototype.

4.  Action Items

        a1. Anne will provide a demo of the current system to Diane
        a2. Anne will provide information on the Sun backup product Co-Pilot
            to the team...as background for our own work.  We are NOT 
            opposed to a purchased solution, but don't expect there will be 
            a good fit with our requirements.
        a3. Diane will review the existing draft of the HIGH LEVEL DESIGN, and
            produce for the team's review a revised DESIGN before our 
            next meeting.
        a4. Jonathon will establish a mailing list/discuss meeting for this
            project, and populate the the discuss meeting with the documents 
            that have already been created.
        a5. Anne will ask the net about tools that might be more versative
            than dbm, but still not in the Ingres/Oracle class of products,
            for storing the various kinds of dbs that we need for this service. 
        a6. Anne will brief David on the results of the meeting.

5.  Next Meeting

        July 14, 1994  1:30   E40-316.
            

------- End of Forwarded Message


home help back first fref pref prev next nref lref last post