X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C70A05.04FF820B@onstor-exch02.onstor.net>; Thu, 16 Nov 2006 20:58:27 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C70A05.04FF820B"
Content-class: urn:content-classes:message
Subject: RE: Delorean MRD/PRD REV1.2
Date: Thu, 16 Nov 2006 20:58:27 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E013D2456@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Delorean MRD/PRD REV1.2
thread-index: AccJ7pTQ3+up672FSK6omO103gJ4WQABuoJwAAHjfRQAAZGXfg==
References: <BB375AF679D4A34E9CA8DFA650E2B04ECAA51F@onstor-exch02.onstor.net>
From: "Paul Hammer" <paul.hammer@onstor.com>
To: "Narayan Venkat" <narayan.venkat@onstor.com>,
	"Andrew LeFebvre" <andrew.lefebvre@onstor.com>,
	"dl-Delorean" <dl-Delorean@onstor.com>,
	"dl-eng-ops-staff" <dl-eng-ops-staff@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C70A05.04FF820B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20

________________________________

From: Narayan Venkat
Sent: Thu 11/16/2006 8:01 PM
To: Paul Hammer; Andrew LeFebvre; dl-Delorean; dl-eng-ops-staff
Subject: Re: Delorean MRD/PRD REV1.2



Paul,

The limits Andy refers to are the published limits (e.g., max num =
volumes, max connections, etc.,) that we will support.

** Got it, lets start calling this scalability, think it more accurately =
describes what our focus will be. =20
=20
** In the Volume section of the MRD I would change the wording so that =
it does not say create 200 volumes, we can do that today (it has been =
verified), we need to be able to support a 200 volume configuration =
using all advertised features of the product. Think that is closer to =
our intent.


The PRD doc has sections for response to the requirements.  It's =
expected that the response columns will be filled by Dev and QA.

** Got it, are you looking for QA to say the requirement is  understood, =
testable and non-ambiguous (for QA's purposes), makes sense, just not =
use to putting in the MRD, fine with it. Since the core team will have =
other member do we need for those team members to agree too (i.e. =
supportability focus, sales focus)?=20

**Thanks for the clarifications.

-Paul


Narayan Venkat
Tel: (408) 963-2404
Cell: (408) 221-4297
--------------------------
Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: Paul Hammer
To: Andrew LeFebvre; dl-Delorean; dl-eng-ops-staff; dl-se
Sent: Thu Nov 16 19:24:10 2006
Subject: RE: Delorean MRD/PRD REV1.2

Comments in-line.

_____________________________________________
From: Andrew LeFebvre
Sent: Thursday, November 16, 2006 6:18 PM
To: dl-Delorean; dl-eng-ops-staff; dl-se
Subject: Delorean MRD/PRD REV1.2

All,

I helped Narayan combine the initial Delorean PRD and the GNS PRD into a =
single spreadsheet.

Good, thanks,


 I attempted to simplify the document so it isn't as overwhelming, but =
in doing so I've lost some of the "big picture" features and =
requirements of future releases beyond this project.

 << File: Delorean MRD-PRD-REV1-2.xls >>
Narayan will be presenting a summary of this spreadsheet in tomorrow's =
team meeting.

By no means is this document complete.

So is this one just a preview and then we will do another MRD review =
later?

 Here is a list of some of the items which still need to occur:
1.      Customer Service and SE to indicate which RFE and MF bugs they =
desire in the Delorean release

** Hmmm, marketing makes the call on the RFE's, triage team on MF's.

2.      Need to agree on what will be the published spec limits for the =
Delorean release

** Is this a request to run SpecFS? If so that is part of the standard =
test plan for all projects.

3.      Agree on which major and minor features are going into the =
Delorean release
4.      Product Management to update MRD/PRD accordingly
5.      Need DEV and QA to complete their portion of the MRD/PRD


Not sure why QA would update the MRD, the QA part goes in the test plan, =
maybe I am missing the intent?=20

Regards,

Andy



------_=_NextPart_001_01C70A05.04FF820B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: Delorean MRD/PRD REV1.2</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText10233 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2></FONT>&nbsp;</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Narayan Venkat<BR><B>Sent:</B> =
Thu 11/16/2006 8:01 PM<BR><B>To:</B> Paul Hammer; Andrew LeFebvre; =
dl-Delorean; dl-eng-ops-staff<BR><B>Subject:</B> Re: Delorean MRD/PRD =
REV1.2<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Paul,<BR><BR>The limits Andy refers to are the =
published limits (e.g., max num volumes, max connections, etc.,) that we =
will support.</FONT></P><FONT size=3D2></FONT></DIV>=0A=
<DIV><FONT size=3D2>** Got it, lets start calling this scalability, =
think it more accurately describes what our focus will be.&nbsp; =
</FONT></DIV>=0A=
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV><FONT size=3D2>** In the Volume section of the MRD I would change =
the wording so that it does not say create 200 volumes, we can do that =
today (it has been verified), we need to be able to support a 200 volume =
configuration using all advertised features of the product. Think that =
is closer to our intent.</DIV>=0A=
<P><BR>The PRD doc has sections for response to the requirements.&nbsp; =
It's expected that the response columns will be filled by Dev and QA.</P>=0A=
<P>** Got it, are you looking for QA to say the requirement is&nbsp; =
understood, testable and non-ambiguous (for QA's purposes), makes sense, =
just not use to putting in the MRD, fine with it. Since the core team =
will have other member do we need for those team members to agree too =
(i.e. supportability focus, sales focus)? </P>=0A=
<P>**Thanks for the clarifications.</P>=0A=
<P>-Paul<BR><BR><BR>Narayan Venkat<BR>Tel: (408) 963-2404<BR>Cell: (408) =
221-4297<BR>--------------------------<BR>Sent from my BlackBerry =
Wireless Handheld<BR><BR><BR>-----Original Message-----<BR>From: Paul =
Hammer<BR>To: Andrew LeFebvre; dl-Delorean; dl-eng-ops-staff; =
dl-se<BR>Sent: Thu Nov 16 19:24:10 2006<BR>Subject: RE: Delorean MRD/PRD =
REV1.2<BR><BR>Comments =
in-line.<BR><BR>_____________________________________________<BR>From: =
Andrew LeFebvre<BR>Sent: Thursday, November 16, 2006 6:18 PM<BR>To: =
dl-Delorean; dl-eng-ops-staff; dl-se<BR>Subject: Delorean MRD/PRD =
REV1.2<BR><BR>All,<BR><BR>I helped Narayan combine the initial Delorean =
PRD and the GNS PRD into a single spreadsheet.<BR><BR>Good, =
thanks,<BR><BR><BR>&nbsp;I attempted to simplify the document so it =
isn&#8217;t as overwhelming, but in doing so I&#8217;ve lost some of the =
&#8220;big picture&#8221; features and requirements of future releases =
beyond this project.<BR><BR>&nbsp;&lt;&lt; File: Delorean =
MRD-PRD-REV1-2.xls &gt;&gt;<BR>Narayan will be presenting a summary of =
this spreadsheet in tomorrow&#8217;s team meeting.<BR><BR>By no means is =
this document complete.<BR><BR>So is this one just a preview and then we =
will do another MRD review later?<BR><BR>&nbsp;Here is a list of some of =
the items which still need to occur:<BR>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Customer Service and SE to indicate which RFE and MF bugs they desire in =
the Delorean release<BR><BR>** Hmmm, marketing makes the call on the =
RFE&#8217;s, triage team on =
MF&#8217;s.<BR><BR>2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Need to agree on =
what will be the published spec limits for the Delorean =
release<BR><BR>** Is this a request to run SpecFS? If so that is part of =
the standard test plan for all =
projects.<BR><BR>3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Agree on which major =
and minor features are going into the Delorean =
release<BR>4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Product Management to update =
MRD/PRD accordingly<BR>5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Need DEV and QA =
to complete their portion of the MRD/PRD<BR><BR><BR>Not sure why QA =
would update the MRD, the QA part goes in the test plan, maybe I am =
missing the =
intent?&nbsp;<BR><BR>Regards,<BR><BR>Andy<BR></P></FONT></BODY></HTML>
------_=_NextPart_001_01C70A05.04FF820B--
