...............................
Date: Mon, 22 Feb 1999 18:03:07
Who: David Shupe
Subject:  Major database change coming
Original file: /home/tab/jc.t
...............................
From listmaster Mon Feb 22 18:01 PST 1999
Received: from castor.ipac.caltech.edu (castor [134.4.10.10])
	  by chomsky.ipac.caltech.edu (8.8.5/8.6.4)
	  with ESMTP id SAA28170; Mon, 22 Feb 1999 18:01:45 -0800 (PST)
Received: from skycap.ipac.caltech.edu (skycap.ipac.caltech.edu [134.4.50.197])
	  by castor.ipac.caltech.edu (8.8.8/8.6.4)
	  with SMTP id SAA25907; Mon, 22 Feb 1999 18:01:47 -0800 (PST)
Message-Id: <3.0.1.32.19990222180307.00be9b44@chomsky.ipac.caltech.edu>
X-Sender: shupe@chomsky.ipac.caltech.edu
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Mon, 22 Feb 1999 18:03:07 -0800
To: tim@ipac.caltech.edu, cjl@ipac.caltech.edu, perry@ipac.caltech.edu
From: David Shupe <shupe>
Subject: Major database change coming
Cc: wire@ipac.caltech.edu
In-Reply-To: <199902230117.RAA17325@skyhawk.ipac.caltech.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Length: 2795
Status: RO

Everyone please take notice of the major database change that will be
happening this week. See Tim's change request for the description.

Dave

At 05:17 PM 2/22/99 -0800, tim wrote:
>Submitted by: Tim Conrow
>
>Tracking Number: 42
>
>Date: Mon Feb 22 17:17:42 1999
>
>o Software to Modify: Many SO and DA DB access programs
>
>o Description of Requested Change:
>1) Create new databases in DBMS; 'wire_debug', 'wire_dev', and possibly
others
>2a) Rename DB 'wire' to 'wire_test' and create a new DB called 'wire'.
>2b) Re-create all table structures in 'wire_test' in 'wire', but without
data (i.e. empty tables).
>3) Alter DA programs db_soda1, db_soda2, db_warehouse*, plus various state
change codes
>   to allow for user entry of DB name to use. Do not change SO codes
requireed for timeline delivery.
>4) Make same changes as 3 for SO codes needed for timeline delivery.
>5) Change timeline delivery scripts so SEQ mode 1 (debug t/l delivery)
uses table 'observation' in 'wire_debug' DB
>   instead of table 'observation_debug' in 'wire' DB.
>
>
>o Criticality: Requirement
>
>o Classification: Major Change
>
>o How long will it take: 2 Day(s)
>
>o Risk Factor: Medium Risk
>
>o Comments on criticality, risk, etc.:
>- 1-3) must be completed ASAP. Target Wed. (2-24-99), but
>  Thurs. AM is acceptable.
>- 4) can be done post launch but should be done before
>  any changes are required to the SO timeline delivery
>  code. I.e. ASAP after launch.
>- 5) can be done at any time and is of lower priority
>
>o Justification:
>1-2 are required for flight observation data to
>be recorded in a fresh data base, separate from ops
>test data. 3) must be done so DA can test Input changes
>on ops test data before launch. 4) must be done to
>allow SO to test new code post launch. 5) is an
>enahncement that will allow greater flexibility and
>upgradability in the timeline delivery process.
>
>o Impact of change on SOC subsystems:
>Increase in flexibility and seapration of ops test and real data.
>
>o Proposed testing procedure and tester(s):
>1-3) Generate a set of timelines and subject them to
>     the usual validation procedures.
>4)   Regenerate a previous delivery in a new DB and
>     compare the new timelines and obs table to the
>     old one.
>5)   Same as 4.
>
>
CCB Response

Case Type: 1
Approved: approved
Action Item Number(s): Unavailable
Date reviewed by CCB: Mon Feb 22 17:57:06 1999

CCB assessment of criticality:
This is a critical, major change that is required to allow
database tools to be tested with ops test data without
harming the mission database.


CCB assessment of risk:
medium risk.

Procedure for passing to DEV or OPS:
As specified in change request.

Name of tester: Yi, Wen, Tim, Tom
Test results due by: February 26, 1999