From:	STAR::ST_LAURENT   "Pat - VMS Engineering - DTN: 381-6101" 20-JAN-1997 12:12:45.63
To:	GLENN
CC:	ST_LAURENT
Subj:	Proj. plan

Glenn,

I've only scanned the proj. plan you left last week, so probably will
have some comments later.  I was looking for a schedule update, but
didn't find a schedule outline similar to the one below.  (Although I'm
glad to see the details of how you do estimates!)  

Could you update the schedule below, and include in the proj. plan as
well?  Feel free to include additional milestones as appropriate.

thanks,
Pat

    =======================================================================
    
			Multi-path Switching Project
				  Schedule

	1st draft of design specification for review

	12/31	(I don't expect to take more than 3 or so days vacation
		in December and this stuff's all very clear in my mind.)

		(I'd like to review it, and maybe one other person,
		before you send it to a wide audience.  Plan on 4 working
	        days to get feedback.) 
    
	1st review complete (Holding this with Tom and Lenny and John
	Croll tomorrow 1/21/1997; your comments need to be factored
	in also.
    
	1/25/97

	2nd draft of design specification for review
		(This will be a second 4-day limited review.)
	
	2/1/97

	2nd review complete

	2/15/97
    
	Distribute design specification for group review.
		(I'd suggest sending it to OPENVMS_BASE_IO and
		BASE_OS_CLUSTER, at least.)
	Draft test plan begins here

	3/7/1997 Test plan drafted and reviewed. Coding starts on
		moving existing function level to fully general
		form (n paths)

	3/28/1996
	Existing code & function level coded and minimally
	unit tested (3 weeks est.)

	6/11/1996
	New functionality completed (as outlined in project plan
	and in that order.

	Some unit testing runs concurrently (asking Bill Clogher for
		a trial or three)

	Sub bullets after existing code bullet (with expansion
		factor due to QAR & other interruption load)

	4/4/1997: Command line controls in new server. (Need 
		translation for some of this to C)

	4/21/1997: Lock manager routines coded. Test of these is 
		trickier since a cluster is needed

	4/29/1997: Memory configuration and device scan (doing
		INQUIRY in a loop over local devices) coded

	5/2/1997: New device configuration (adding new devices
		when they need to be autoconfig'd) coded

	5/9/1997: Special HSZ case disabling HSZ ports in a cluster
		coded

	5/16/1997: Watchdog path polling coded

	5/28/1997: Local config file writing coded

	(This is going to be a very strenuous coding effort.)

	6/11/1996: Unit testing, whatever else is needed

	7/11/1997: Code inspection and unit testing complete
	7/18/1997: Finish update of design document to reflect actual
		code

	7/21/1997: Send out final design document for comment and
		possibly schedule review if changes have been
		unexpectedly extensive.
	7/21/1997: Distribute code to other groups for testing also.

	Testing complete	

	8/1/97


Note: This is rather ambitious and does presume no serious glitches will
occur. The "server" bullets noted include relevant code in other modules
which will need to handle "the other end" of the communications which will
go on. The functioning of the testbed code suggests this is not as far
fetched as it may often be, but unknown issues are after all unknown.

The scheme to have partial function implemented early however is intended
to provide assurance that if it becomes necessary to trim functions, that
will still leave at least basic functionality usable.

Glenn Everhart
1/20/1997