osera-isp-dev — OSERA Infrastructure Service Platform Listserv at SourceForge

Re: [osera-isp-dev] OISP Task-4, Satisfaction of requirements

[Cory C. <co...@mo...>]

 

 

Rick,

Many of your comments are covered in the "Other Requirements" section
(which comes from the text).   Also, at this point I want to make sure
we are agreeing on the solution, not just the requirement.



Comment R1:

Not sure what you mean, we need a representation of BPMN models.  The
Plan calls for BPDM (which is a representation of BPMN).  You stated a
preference for Intallio.  We are willing to substitute Intallio as the
representation of BPMN but need to resolve this ASAP.  So I think the
resolution is that MDS & GSA Agree to use The Intallio file format as
the representation of BPMN for the project instead of BPDM.

 

Comment R2-1: Satisfied by 4.5.04

Comment R2-2: Satisfied by 4.x.05

Comment R2-3: The KB is maintained in a consistent state. An asset may
be checked in or out from another tool that may or may not be
consistent, in which case consistency would be checked by that tool
(such as topbraid).

 

Comment R3: The caption is directly from the RFQ deliverables list, the
mapping is a different deliverable (4.5.08) - so this is satisfied.

 

Comment R4: Satisfied by 4.x.05

 

Comment R5: There is a user registry, which we can show.

 

From: ose...@li...
[mailto:ose...@li...] On Behalf Of
ric...@gs...
Sent: Thursday, July 03, 2008 9:45 AM
To: Cory Casanave
Cc: ose...@li...
Subject: Re: [osera-isp-dev] OISP Task-4, Satisfaction of requirements

 


Thanks Cory, here are a few annotations to the Task 4 - Satisfaction of
Requirements document derived from the statement of work. 



Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604 




"Cory Casanave" <co...@mo...> 

07/02/2008 01:17 AM 

To

ric...@gs... 

cc

ose...@li... 

Subject

OISP Task-4, Satisfaction of requirements

 

		




Rick, 
As discussed, here is a summary of what we are working on to satisfy
Task-4 requirements.  Note that there is an open item with regard to the
BPMN serialization format used, as you had issues with the planned use
of BPDM.  We can switch to the Intalio-Eclipse format. 
-Cory[attachment "OSIP-Task4-Requirements.doc" deleted by Richard C.
Murphy/IAA/CO/GSA/GOV] 

[osera-isp-dev] great job yesterday at task 3 demonstration

[<ric...@gs...>]

Cory & All:

I wanted to extend a congratulations and thank you to everyone involved 
directly and indirectly in yesterday's demonstration of the Bricks 
Management Application to the ITAPC membership. I especially want to thank 
Cory & Ed for their leadership in getting us through the task management 
process as well as Dean and Irene for their work on a very well received 
application and Willie for his support here at GSA.

I left the meeting with the impression that we scored a big win with the 
ITAPC. Stay tuned !

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

[osera-isp-dev] OSIP Meeting Reminder

[Cory C. <co...@mo...>]

When: Tuesday, July 01, 2008 1:30 PM-2:30 PM (GMT-05:00) Eastern Time (US & Canada).
Where: Cory's office & Phone

*~*~*~*~*~*~*~*~*~*

 https://www2.gotomeeting.com/join/891771730 
Conference Call: (605) 475-8585, access code 891-771-730 
Meeting ID: 891-771-730

[osera-isp-dev] GoToMeeting Invitation - New meeting

[Ed H. <ed...@mo...>]

When: Tuesday, June 24, 2008 1:30 PM-2:30 PM (GMT-05:00) Eastern Time (US & Canada).
Where: MDS Conference Room and Teleconference

*~*~*~*~*~*~*~*~*~*

Please join my meeting at
 https://www1.gotomeeting.com/join/859064074
Conference Call: (309) 946-4505, access code 859-064-074
Meeting ID: 859-064-074

GoToMeeting(TM) 
Online Meetings Made Easy

[osera-isp-dev] GoToMeeting Invitation - Weekly OISP Meeting

[Ed H. <ed...@mo...>]

When: Tuesday, June 17, 2008 1:30 PM-3:00 PM (GMT-05:00) Eastern Time (US & Canada).
Where: Phone and MDS

*~*~*~*~*~*~*~*~*~*

I'll be sitting in for Cory this week...please note phone number...

Please join my meeting at
 https://www1.gotomeeting.com/join/821153904
Conference Call: (712) 580-0610, access code 821-153-904
Meeting ID: 821-153-904

GoToMeeting(TM) 
Online Meetings Made Easy

[osera-isp-dev] OISP Meeting Reminder

[Cory C. <co...@mo...>]

When: Tuesday, June 10, 2008 1:30 PM-2:30 PM (GMT-05:00) Eastern Time (US & Canada).
Where: MDS & Phone

*~*~*~*~*~*~*~*~*~*

 https://www2.gotomeeting.com/join/891771730 
Conference Call: (605) 475-8585, access code 891-771-730 
Meeting ID: 891-771-730

[osera-isp-dev] Fw: REMINDER: Next Federal DAS Meeting 12 June 2008 @ 1pm

[<ric...@gs...>]

<div><font size="2">Cory &amp; All:<br><br>Just a heads up on the next DAS meeting, if you're interested.<br><br></font><div>Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604<br><div><br></div><font color="#990099">-----Forwarded by Richard C. Murphy/IAA/CO/GSA/GOV on 06/08/2008 12:17PM -----<br><br></font><blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: "Loaiza-Lemos,Francisco L" &lt;fl...@id...&gt;, "Haberkamp,Bruce W Mr CIO/G6" &lt;Bru...@US...&gt;, bob...@ss..., ch...@st..., den...@hq..., don...@dh..., dou...@na..., gar...@hh..., hl...@gp..., hol...@ed..., ja...@dn..., jd...@cs..., lui...@va..., mar...@gs..., mcc...@ep..., McC...@ep..., rho...@do..., ric...@fa..., rob...@na..., shu...@hu..., TT...@nr..., a-n...@ng..., ah...@ci..., ala...@ve..., al...@nr..., am...@ew..., as...@mi..., bre...@hq..., bru...@us..., car...@us..., cc...@dh..., che...@kc..., chi...@ba..., cj...@mi..., cm...@re..., co...@CD..., cor...@mi..., cox...@ba..., cra...@os..., ct....@kc..., da...@uc..., dav...@ft..., db...@co..., dc...@es..., deb...@fa..., den...@om..., dou...@sr..., dus...@us..., Dale_G_Guenther%FS...@io..., edw...@st..., eli...@na..., gia...@fm..., glo...@kc..., ham...@ep..., ha...@us..., hm...@ne..., Hai...@ma..., im...@gp..., jam...@os..., jam...@do..., jan...@do..., jar...@dn..., jas...@te..., jfe...@re..., jmc...@mi..., jn...@as..., joa...@na..., joh...@hh..., joh...@kc..., Jim...@no..., kar...@dh..., kc...@cm..., ken...@sa..., kev...@sa..., kir...@ep..., kir...@us..., kk...@cs..., lis...@ed..., lis...@os..., lke...@co..., lo...@kn..., mam...@ci..., man...@ep..., ma...@uc..., mar...@do..., mar...@hu..., mau...@sr..., mc...@de..., mic...@dh..., mik...@vi..., mmg...@wi..., mo...@hu..., mti...@ea..., nan...@as..., ni...@mi..., nie...@sa..., nk...@Pe..., nor...@kc..., pat...@us..., pau...@os..., pau...@kc..., ph...@pp..., phi...@ts..., rca...@fd..., ric...@us..., ric...@gs..., rra...@Ci..., rub...@ir..., rya...@kc..., Ric...@dl..., sco...@be..., sco...@us..., sd...@ci..., shu...@hu..., son...@us..., st...@st..., st...@si..., ste...@ed..., ste...@rm..., stu...@ep..., tai...@us..., ter...@lo..., ter...@kc..., tom...@us..., tra...@va..., tta...@ci..., wa...@mi..., war...@ep..., way...@ts..., wha...@ba..., yen...@sb...<br>From: Suz...@io...<br>Date: 06/07/2008 04:46PM<br>cc: Adr...@no..., suz...@io..., bet...@os..., ama...@os..., th...@ci...<br>Subject: REMINDER:  Next Federal DAS Meeting 12 June 2008 @ 1pm<br><br><font face="Default Sans Serif, Verdana, Arial, Helvetica, sans-serif" size="2"><font size="2">Hi Everyone,<br>Just a friendly reminder from Adrian and me that our next monthly meeting is scheduled for </font><b><font size="2">Thursday, 12 June 2008 at 1-3pm</font></b><font size="2">&nbsp;(eastern time). &nbsp;The location is the DOD (P&amp;R) facility in Ballston, Virginia. Directions with complete address are contained in the attachment for those who are new to DAS. </font><br><font size="2">Meeting room is on the 5th floor (Main Conference Room in suite # 502). </font><b><font size="2"><br><br>Telecon info for those who call-in</font></b><font size="2">: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</font><font size="3">&nbsp;</font><font size="2">&nbsp; &nbsp;<br>Call in number: &nbsp; 866-560-1229<br>Access code: &nbsp;2848270 <br>(This number is not always the same for each meeting.)</font><b><font size="2"><br><br>Agenda</font></b><font size="2">&nbsp; &nbsp;(times are approximates)<br>- Introductions &amp; opening remarks (10 min)<br>- Annual review of DAS mission, and accomplishments.- Suzanne Acar (20 min)<br>- Defining the way ahead for DAS - Adding value to Government - open discussion (60 minutes)</font><br><font size="2">- Updates from Working Groups (20 minutes total)</font><br><font size="2">&nbsp; &nbsp;- Best Practice</font><br><font size="2">&nbsp; &nbsp;- DQ Guide</font><br><font size="2">    &nbsp; &nbsp;- IAC<br>- Wrap-up and close (10 minutes) </font><b><font size="2"><br><br>Read Aheads</font></b><font size="2"><br>Presentations will be posted in the DAS area of collab.core.gov. &nbsp;I'll make every attempt to have them posted prior to the scheduled meeting.</font><b><font size="2"><br>If you need help accessing, please contact Tina Horan at: &nbsp;th...@ci....</font></b><font size="2"><br><br><br>Thanks, <br>Suzanne <br>__________________________________<br>Suzanne Acar<br>Senior Information Architect and <br>Co-chair, Federal Data Architecture Subcommittee<br>Office of the Secretary (OCIO)<br>U.S. Department of the Interior<br>202-208-3216 <br><br>Acta non Verba <br>Classification: &nbsp;UNCLASSIFIED <br>Caveats: NONE</font><font size="3">&nbsp;</font><tt><font size="2"><br></font></tt><font size="3"><br><br></font><img alt="" src="cid:1212871578921" height="2" width="10"> </font>
</blockquote><br><br>[attachment "DAS meeting location (DOD P&amp;R).doc" removed by Richard C. Murphy/IAA/CO/GSA/GOV]<br></div></div>

[osera-isp-dev] OISP Meeting Reminder

[Cory C. <co...@mo...>]

When: Tuesday, June 03, 2008 1:30 PM-2:30 PM (GMT-05:00) Eastern Time (US & Canada).
Where: MDS & Phone

*~*~*~*~*~*~*~*~*~*

 https://www1.gotomeeting.com/join/891771730 
Conference Call: (605) 475-8585, access code 891-771-730 
Meeting ID: 891-771-730

Re: [osera-isp-dev] dynamic change and configuration managementwhitepaper

[Cory C. <co...@mo...>]

Ok - remember this is just a "course check" version - not intended for
final edit.

 

From: ose...@li...
[mailto:ose...@li...] On Behalf Of
ric...@gs...
Sent: Friday, May 30, 2008 2:37 PM
To: ose...@li...
Cc: phy...@gs...
Subject: [osera-isp-dev] dynamic change and configuration
managementwhitepaper

 


Ed, Cory & All: 

Just to let you know I have uploaded my comments on the dynamic change a
configuration management whitepaper to the portal IV&V section. 

I know Phyllis is still wokring on hers and I believe Didier is working
on his ! 

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

[osera-isp-dev] dynamic change and configuration management whitepaper

[<ric...@gs...>]

Ed, Cory & All:

Just to let you know I have uploaded my comments on the dynamic change a 
configuration management whitepaper to the portal IV&V section.

I know Phyllis is still wokring on hers and I believe Didier is working on 
his !

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

[osera-isp-dev] OISP Meeting Reminder

[Cory C. <co...@mo...>]

When: Tuesday, May 27, 2008 1:30 PM-2:30 PM (GMT-05:00) Eastern Time (US & Canada).

*~*~*~*~*~*~*~*~*~*

Please join my meeting at 
 https://www1.gotomeeting.com/join/891771730 
Conference Call: (605) 475-8585, access code 891-771-730 
Meeting ID: 891-771-730 

[osera-isp-dev] bureaucracy timeout - use cases committed

[<ric...@gs...>]

<div><font size="2"><font size="4">Irene, Jim and other OSERAti:<br><br>Ok, I took a bureaucracy timeout and committed the Bricks PIM to the repository. Although we may, or may not use them in the June 4 presentation, please be able to generate the use case report from the Bricks PIM by that time. <br><br>As I described yesterday, a definition for what we mean by supersedes and a definition for a brick are important. Also, I uploaded a sample of the report I created last week we can use as a prototype of the report. Note: I had to copy and paste section 4 and definitions from the model. <br><br>You might check with Walt on ways to generate that content.<br></font> <br></font><div>Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604<br></div></div>

[osera-isp-dev] rick's notes from the bricks ipr

[<ric...@gs...>]

Hello Irene and other OSERati !

here are my notes from last weeks IPR ...

1. ITAPC members identify directly with Bricks, not the FEA. Seeing as 
people read from top-left to bottom-right. Consider moving the FEA 
scrolling list from the top-left corner. 
2. The product life-cycle had a strong visual placement in the Bricks 
Powerpoint. Consider reinforcing the topics of the product life-cycle in 
the UI. I'm not suggesting a significant redesign here. I'm just saying 
give them the visual queues they need to readily identify the product 
lifecycle.
3. If a column in a search result table is empty, can't it be "hidden" ?
4. Please provide a definition for supersede and brick, so we can document 
them in the use case report.
5. Dean - good stuff, but I'd like to better understand how the FEA and 
FTF are being used in the application
6. As a reminder, IPRs serve the purpose of taking stock on where we are 
in satisfying the requirements for the demonstration. The requirements for 
the demonstration are as follows:

a) Integration of the “One GSA” EA Bricks, the FTF and the FEA TRM as a 
shared concept implementation. 

b) Suitable web user interface, integrated into the enterprise-wide 
knowledgebase, hosted on LifeRay portal in J2EE, for members of the ITAPC 
to populate and maintain the technology architecture enterprise-wide 
knowledge base. Suitability of the user interface is determined by 
interviews ITAPC stakeholders.

c) User queries represented in a query language based on a voluntary 
consensus standard returning consistent results based on terms specified 
in both “The Bricks,” the FTF and the FEA TRM through a shared concept 
implementation at the level of an operational prototype. 

I don't recall these capabilities being shown in the IPR.

Ed and Cory, let's do what we did last time where you indicated how the 
bricks application satisfies the requirements for the demonstration. 
Wednesday, let's decide on the date for the Task 3 demonstration.

BTW - Will we have the user manual QA'd and ready to hand to the users on 
June 4 ?

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

Re: [osera-isp-dev] (no subject)

[Jim L. <ji...@mo...>]

ric...@gs... wrote:
> Cory & All:
>
> Attached is the use case description report generated from MagicDraw. 
> Please provide some QA and comment today as I am presenting this to 
> the ITAPC tomorrow afternoon.
>
> Once Rob and Reddy give me permissions to commit, I'll check the 
> BricksPIM back into subversion and maintenance of the model including 
> the use case descriptions will be off my plate.
>
> Walt, many thanks for the templates you sent yesterday !
>
> Best wishes,
>
> Rick
>
> office: 202-501-9199
> cell: 202-557-1604
Rick,

Figure 10 now has a blank activity that used to have the name of the 
deleted behavior. You might want to name it with what was the name of 
the deleted behavior.

-Jim

Re: [osera-isp-dev] (no subject)

[<ric...@gs...>]

Thanks for the heads up, Jim.
Best Wishes, Rick (202-501-9199)


----- Original Message -----
From: "Jim Logan" [ji...@mo...]
Sent: 05/14/2008 11:55 AM AST
To: Richard Murphy
Cc: ose...@li...; co...@mo...; ir...@to...; ed...@mo...; wa...@mo...; George Thomas; Jer-Ren Yen; re...@lm...
Subject: Re:



ric...@gs... wrote:
> Cory & All:
>
> Attached is the use case description report generated from MagicDraw. 
> Please provide some QA and comment today as I am presenting this to 
> the ITAPC tomorrow afternoon.
>
> Once Rob and Reddy give me permissions to commit, I'll check the 
> BricksPIM back into subversion and maintenance of the model including 
> the use case descriptions will be off my plate.
>
> Walt, many thanks for the templates you sent yesterday !
>
> Best wishes,
>
> Rick
>
> office: 202-501-9199
> cell: 202-557-1604
Rick,

Figure 10 now has a blank activity that used to have the name of the 
deleted behavior. You might want to name it with what was the name of 
the deleted behavior.

-Jim

Re: [osera-isp-dev] bricks use case descriptions

[<ric...@gs...>]

<div>Ok, we'll the word in the use case description I received was "supercedes," so without a clear meaning of supercedes, it would probably be best to modify the use case language to reflect the functions that actually exist in the application.<br><br>Anwyay, let's talk tomorrow. I'm a Ralph wannabe and I need to log a few more hours on Haskell tonight !<br><br><div>Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604<br><div><br></div><font color="#990099">-----"Irene Polikoff" &lt;ir...@to...&gt; wrote: -----<br><br></font><blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: ric...@gs...<br>From: "Irene Polikoff" &lt;ir...@to...&gt;<br>Date: 05/13/2008 11:34PM<br>cc: ose...@li..., ed...@mo..., "'Walt Melo'" &lt;wa...@mo...&gt;, cli...@gs...<br>Subject: RE: [osera-isp-dev] bricks use case descriptions<br><br>



<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">&lt;<font color="#000000" face="Times New Roman" size="3">Would you be able to talk some tomorrow about what we mean when we say 
one policy supersedes another&gt;</font></span></font></div>
<div dir="ltr" align="left"><font color="#000000" face="Times New Roman" size="3"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">I can talk about my understanding of it.&nbsp;I 
understand superseding as&nbsp;an act of&nbsp;a decision about&nbsp;a use of 
technology at GSA becoming outdated. Let's say IE 6.0 was an approved standard, 
then a new decision was made that IE 6.0 is in containment starting this month 
and IE 7.0 is now an approved standard. These are 3 policy decisions.&nbsp; "IE 
6.0 is an approved standard" is being superseded or becomes 
outdated.</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">The notion of one policy superseding another one is not 
as clear to me.</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">For example, we could say that 2 policies (IE 6.0 is in 
containment starting this month and IE 7.0 is an approved standard) now replace 
the original one (IE 6.0 is an approved standard) or we could say that only one 
of them replaces the original one. </span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">Often, there would be a change of status - something 
that was approved becomes in containment, something that was a tactical strategy 
becomes approved, something that was in containment becomes retired, etc. I 
believe the view use case diagrams may have took&nbsp;was that a policy decision 
gets superseded by another decision about the same product, so in this example 
"IE 6.0 is an approved standard" is superseded by " 6.0 is in containment 
starting this month". </span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">On the other hand, it is possible for a policy decision 
to become outdated without&nbsp;us creating&nbsp;another decision about the 
product in question. </span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">For example, product X was listed as a strategic 
direction, then we decided that it was no longer the case. There are no new 
decisions about product X, it just got deleted and is no longer mentioned any 
place. </span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">When we do this, we could, at the same time, add 
another product as a strategic direction. Would this mean that a decision about 
giving another product the same status as the status of product X, supersedes 
the policy about product X? If so, does it mean that potentially one or 2 
policies (or may be even more) could supersede&nbsp;a previously existing 
policy&nbsp;and therefore, "IE 6.0 is in containment starting this month" and 
"IE 7.0 is an approved standard" superseded "IE 6.0 is an approved standard"? 
The only constraint is that a superseding policy has to be either about the same 
product or have to&nbsp;give another product the same 
status.</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">Finally, we could have just removed product X and done 
nothing else, so a decision can be superseded without putting in place a new 
one.</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008"></span></font>&nbsp;</div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span class="703560203-14052008">I do not believe we teased it out to the extent I am 
doing it here and I don't believe there is currently&nbsp;a model supporting the 
concept of superseding, although may be Cory has done something in the shared 
concepts I am not aware of as part of his work on the effectivity. It is also 
possible that Cory have a design in mind&nbsp;where a decision gets superseded 
by a negating statement, so "IE 6.0 is an approved standard" gets superceded by 
"IE 6.0 is NOT an approved standard"</span></font></div>
<div><font color="#0000ff" face="Arial" size="2"></font>&nbsp;</div>
<div align="left"><font face="Arial" size="2">Irene Polikoff</font></div>
<div align="left"><font face="Arial" size="2">Executive Partner, 
TopQuadrant</font></div>
<div align="left"><font face="Arial" size="2">tel: 914-777-0888/ </font><font face="Arial" size="2">cell: 914-329-8576</font></div>
<div align="left"><font face="Arial" size="2"><a href="http://www.topquadrant.com/">www.topquadrant.com</a></font></div>
<div>&nbsp;</div><br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> ric...@gs... 
[mailto:ric...@gs...] <br><b>Sent:</b> Tuesday, May 13, 2008 11:01 
PM<br><b>To:</b> ir...@to...<br><b>Cc:</b> 
ose...@li...; ed...@mo...; 'Walt Melo'; 
cli...@gs...<br><b>Subject:</b> RE: [osera-isp-dev] bricks use case 
descriptions<br></font><br></div>
<div></div>
<div>Sounds good with me, how about you Ed ?<br><br>BTW - Would you be able to 
talk some tomorrow about what we mean when we say one policy supercedes another 
?<br><br>
<div>Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604<br>
<div><br></div><font color="#990099">-----"Irene Polikoff" 
&lt;ir...@to...&gt; wrote: -----<br><br></font>
<blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: 
  ric...@gs..., ose...@li..., 
  ed...@mo...<br>From: "Irene Polikoff" 
  &lt;ir...@to...&gt;<br>Date: 05/13/2008 10:53PM<br>cc: "'Walt Melo'" 
  &lt;wa...@mo...&gt;, cli...@gs...<br>Subject: RE: 
  [osera-isp-dev] bricks use case descriptions<br><br>
  <div dir="ltr" align="left"><span class="843415102-14052008"><font color="#0000ff" face="Arial" size="2">I asked Jim about this in the past. He said he originally 
  wanted to have this use case, but then decided it was not needed (or it was 
  too premature to define one). I think deleting it is the right thing to 
  do.</font></span></div>
  <div>&nbsp;</div>
  <div align="left"><font face="Arial" size="2">Irene Polikoff</font></div>
  <div align="left"><font face="Arial" size="2">Executive Partner, 
  TopQuadrant</font></div>
  <div align="left"><font face="Arial" size="2">tel: 914-777-0888/ </font><font face="Arial" size="2">cell: 914-329-8576</font></div>
  <div align="left"><font face="Arial" size="2"><a href="http://www.topquadrant.com/">www.topquadrant.com</a></font></div>
  <div>&nbsp;</div><br>
  <div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
  <hr tabindex="-1">
  <font face="Tahoma" size="2"><b>From:</b> ric...@gs... 
  [mailto:ric...@gs...] <br><b>Sent:</b> Tuesday, May 13, 2008 10:39 
  PM<br><b>To:</b> ose...@li...; 
  ed...@mo...<br><b>Cc:</b> Walt Melo; 
  cli...@gs...<br><b>Subject:</b> Re: [osera-isp-dev] bricks use case 
  descriptions<br></font><br></div>
  <div></div>
  <div><font size="2"><font size="3">Ed, I think you may not have the right 
  understanding of my request. Someone, I'm guessing Jim, partially defined a 
  use case called ValidateTechnologyPolicy and put it in the model. There's an 
  empty use case and a blank diagram.<br><br>I never asked anyone to put this 
  use case in the model in the first place. But what I don't think anyone wants 
  is a model that creates the impression we're sloppy.<br><br>Maybe the smart 
  thing is to have me take it out for you. I'll do that for free !<br><br>Lemme' 
  know ...<br><br></font></font>
  <div><font size="3">Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604</font><br>
  <div><br></div><font color="#990099">-----"Ed Harrington" 
  &lt;ed...@mo...&gt; wrote: -----<br><br></font>
  <blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: 
    ric...@gs..., ose...@li...<br>From: "Ed 
    Harrington" &lt;ed...@mo...&gt;<br>Date: 05/13/2008 10:22PM<br>cc: 
    "Walt Melo" &lt;wa...@mo...&gt;, 
    cli...@gs...<br>Subject: RE: [osera-isp-dev] bricks use case 
    descriptions<br><br><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
    <div class="Section1">
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">Rick:&nbsp; <O:P></O:P></font></span></p>
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">A very simple reminder: we were only required to develop “Add” 
    and “Update” use case descriptions and use case models.&nbsp; Anything 
    beyond that – and we have delivered a lot more – is gravy.&nbsp; “Validate 
    Technology Policy” IMHO appears to be outside the scope of our capabilities 
    or capacity.&nbsp; I would think that a validated Technical Policy would 
    need to be in place and would be reflected in the choices that were made in 
    the process.<O:P></O:P></font></span></p>
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">Also, I thought that we had discussed, early on in our 
    discussions, that we were NOT to build an application (based on use cases) 
    that would be part of the decision process…our Bricks application, as 
    reflected in our understanding of the SOW and as we submitted our (accepted) 
    proposal, was to only reflect decisions that had been already 
    made.<O:P></O:P></font></span></p>
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">I submit that your request is out of scope for the current 
    requirements.&nbsp; We will be happy to consider it, but it will require 
    additional funding.&nbsp; If appropriate, I’ll submit this to the 
    CO.<O:P></O:P></font></span></p>
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
    <p class="MsoNormal"><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';">Regards,</span></b><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';"><O:P></O:P></span></b></p>
    <p class="MsoNormal"><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';">Ed 
    Harrington</span></b><span style="font-size: 14pt; color: navy;"><O:P></O:P></span></p>
    <p class="MsoNormal"><b><span style="font-size: 9pt; color: teal; font-family: 'Calibri','sans-serif';">Mobile: 
    +1.757.342.4552&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email: 
    </span></b><b><u><span style="font-size: 9pt; color: blue; font-family: 'Calibri','sans-serif';"><a href="mailto:ed...@mo..."><span style="color: blue;">ed...@mo...</span></a><O:P></O:P></span></u></b></p>
    <p class="MsoNormal"><b><u><span style="font-size: 9pt; color: blue; font-family: 'Calibri','sans-serif';"><a href="http://www.modeldriven.com"><span style="color: blue;">www.modeldriven.com</span></a></span></u></b><b><span style="font-size: 9pt; color: navy; font-family: 'Calibri','sans-serif';"> 
    </span></b><b><span style="font-size: 9pt; color: teal; font-family: 'Calibri','sans-serif';"><O:P></O:P></span></b></p>
    <p class="MsoNormal"><span style="font-size: 8pt; color: navy; font-family: 'Calibri','sans-serif';">Disclaimer: 
    Privileged or Confidential information may be contained in this message or 
    with any files transferred with it.&nbsp; If you are not the intended 
    recipient, kindly destroy this message and notify the sender by return 
    mail.&nbsp; Opinions, conclusions and other information included in this 
    message that do not relate to the official business of Model Driven 
    Solutions are neither given nor endorsed by it.</span><span style="color: navy; font-family: 'Calibri','sans-serif';"><O:P></O:P></span></p>
    <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
    <div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
    <p class="MsoNormal"><b><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">From:</span></b><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';"> 
    ose...@li... 
    [mailto:ose...@li...] <b>On Behalf Of 
    </b>ric...@gs...<br><b>Sent:</b> Tuesday, May 13, 2008 9:35 
    PM<br><b>To:</b> ose...@li...<br><b>Cc:</b> Walt 
    Melo<br><b>Subject:</b> [osera-isp-dev] bricks use case 
    descriptions<O:P></O:P></span></p></div>
    <p class="MsoNormal"><O:P></O:P></p>
    <div>
    <p class="MsoNormal" style="margin-bottom: 12pt;">Jim, Irene, Rob or 
    Reddy:<br><br>I have entered the use case descriptions in MagicDraw. Just 
    two things:<br><br>1. The Bricks PIM in subversion is missing the 
    ValidateTechnologyPolicy use case including the model&nbsp; and the diagram. 
    Also, there's no description in the use case document. Jim, would you mind 
    updating the model and diagram ? Irene, I assume you're writing the 
    descriptions.<br><br>Just a heads up, I have checked out the BricksPIM from 
    subversion, so we'll have to synchronize.<br><br>2. Rob: Would you mind 
    setting me ( rmurphy ) up with write permissions so I can 
    commit.<br><br>Jim, I'll let you know when I get my commit permissions. If I 
    get them early tomorrow, I may be able to execute my commit before you make 
    any mods.<br><br>Sorry for the short notice, but I'll be presenting the 
    bricks use cases to the ITAPC Thursday, so we'll come off better if we're 
    done by then.<O:P></O:P></p>
    <div>
    <p class="MsoNormal">Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604<O:P></O:P></p></div></div></div></blockquote><br></div></div></blockquote><br></div></div></blockquote><br></div></div>

Re: [osera-isp-dev] bricks use case descriptions

[Irene P. <ir...@to...>]

<Would you be able to talk some tomorrow about what we mean when we say one
policy supersedes another>
 
I can talk about my understanding of it. I understand superseding as an act
of a decision about a use of technology at GSA becoming outdated. Let's say
IE 6.0 was an approved standard, then a new decision was made that IE 6.0 is
in containment starting this month and IE 7.0 is now an approved standard.
These are 3 policy decisions.  "IE 6.0 is an approved standard" is being
superseded or becomes outdated.
 
The notion of one policy superseding another one is not as clear to me.
 
For example, we could say that 2 policies (IE 6.0 is in containment starting
this month and IE 7.0 is an approved standard) now replace the original one
(IE 6.0 is an approved standard) or we could say that only one of them
replaces the original one. 
 
Often, there would be a change of status - something that was approved
becomes in containment, something that was a tactical strategy becomes
approved, something that was in containment becomes retired, etc. I believe
the view use case diagrams may have took was that a policy decision gets
superseded by another decision about the same product, so in this example
"IE 6.0 is an approved standard" is superseded by " 6.0 is in containment
starting this month". 
 
On the other hand, it is possible for a policy decision to become outdated
without us creating another decision about the product in question. 
 
For example, product X was listed as a strategic direction, then we decided
that it was no longer the case. There are no new decisions about product X,
it just got deleted and is no longer mentioned any place. 
 
When we do this, we could, at the same time, add another product as a
strategic direction. Would this mean that a decision about giving another
product the same status as the status of product X, supersedes the policy
about product X? If so, does it mean that potentially one or 2 policies (or
may be even more) could supersede a previously existing policy and
therefore, "IE 6.0 is in containment starting this month" and "IE 7.0 is an
approved standard" superseded "IE 6.0 is an approved standard"? The only
constraint is that a superseding policy has to be either about the same
product or have to give another product the same status.
 
Finally, we could have just removed product X and done nothing else, so a
decision can be superseded without putting in place a new one.
 
I do not believe we teased it out to the extent I am doing it here and I
don't believe there is currently a model supporting the concept of
superseding, although may be Cory has done something in the shared concepts
I am not aware of as part of his work on the effectivity. It is also
possible that Cory have a design in mind where a decision gets superseded by
a negating statement, so "IE 6.0 is an approved standard" gets superceded by
"IE 6.0 is NOT an approved standard"
 
Irene Polikoff
Executive Partner, TopQuadrant
tel: 914-777-0888/ cell: 914-329-8576
www.topquadrant.com <http://www.topquadrant.com/> 
 

  _____  

From: ric...@gs... [mailto:ric...@gs...] 
Sent: Tuesday, May 13, 2008 11:01 PM
To: ir...@to...
Cc: ose...@li...; ed...@mo...; 'Walt Melo';
cli...@gs...
Subject: RE: [osera-isp-dev] bricks use case descriptions


Sounds good with me, how about you Ed ?

BTW - Would you be able to talk some tomorrow about what we mean when we say
one policy supercedes another ?


Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604


-----"Irene Polikoff" <ir...@to...> wrote: -----



To: ric...@gs..., ose...@li...,
ed...@mo...
From: "Irene Polikoff" <ir...@to...>
Date: 05/13/2008 10:53PM
cc: "'Walt Melo'" <wa...@mo...>, cli...@gs...
Subject: RE: [osera-isp-dev] bricks use case descriptions


I asked Jim about this in the past. He said he originally wanted to have
this use case, but then decided it was not needed (or it was too premature
to define one). I think deleting it is the right thing to do.
 
Irene Polikoff
Executive Partner, TopQuadrant
tel: 914-777-0888/ cell: 914-329-8576
www.topquadrant.com <http://www.topquadrant.com/> 
 

  _____  

From: ric...@gs... [mailto:ric...@gs...] 
Sent: Tuesday, May 13, 2008 10:39 PM
To: ose...@li...; ed...@mo...
Cc: Walt Melo; cli...@gs...
Subject: Re: [osera-isp-dev] bricks use case descriptions


Ed, I think you may not have the right understanding of my request. Someone,
I'm guessing Jim, partially defined a use case called
ValidateTechnologyPolicy and put it in the model. There's an empty use case
and a blank diagram.

I never asked anyone to put this use case in the model in the first place.
But what I don't think anyone wants is a model that creates the impression
we're sloppy.

Maybe the smart thing is to have me take it out for you. I'll do that for
free !

Lemme' know ...


Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604


-----"Ed Harrington" <ed...@mo...> wrote: -----



To: ric...@gs..., ose...@li...
From: "Ed Harrington" <ed...@mo...>
Date: 05/13/2008 10:22PM
cc: "Walt Melo" <wa...@mo...>, cli...@gs...
Subject: RE: [osera-isp-dev] bricks use case descriptions



Rick:  



A very simple reminder: we were only required to develop "Add" and "Update"
use case descriptions and use case models.  Anything beyond that - and we
have delivered a lot more - is gravy.  "Validate Technology Policy" IMHO
appears to be outside the scope of our capabilities or capacity.  I would
think that a validated Technical Policy would need to be in place and would
be reflected in the choices that were made in the process.



Also, I thought that we had discussed, early on in our discussions, that we
were NOT to build an application (based on use cases) that would be part of
the decision process.our Bricks application, as reflected in our
understanding of the SOW and as we submitted our (accepted) proposal, was to
only reflect decisions that had been already made.



I submit that your request is out of scope for the current requirements.  We
will be happy to consider it, but it will require additional funding.  If
appropriate, I'll submit this to the CO.



Regards,

Ed Harrington

Mobile: +1.757.342.4552        email:  <mailto:ed...@mo...>
ed...@mo...

 <http://www.modeldriven.com> www.modeldriven.com 

Disclaimer: Privileged or Confidential information may be contained in this
message or with any files transferred with it.  If you are not the intended
recipient, kindly destroy this message and notify the sender by return mail.
Opinions, conclusions and other information included in this message that do
not relate to the official business of Model Driven Solutions are neither
given nor endorsed by it.



From: ose...@li...
[mailto:ose...@li...] On Behalf Of
ric...@gs...
Sent: Tuesday, May 13, 2008 9:35 PM
To: ose...@li...
Cc: Walt Melo
Subject: [osera-isp-dev] bricks use case descriptions



Jim, Irene, Rob or Reddy:

I have entered the use case descriptions in MagicDraw. Just two things:

1. The Bricks PIM in subversion is missing the ValidateTechnologyPolicy use
case including the model  and the diagram. Also, there's no description in
the use case document. Jim, would you mind updating the model and diagram ?
Irene, I assume you're writing the descriptions.

Just a heads up, I have checked out the BricksPIM from subversion, so we'll
have to synchronize.

2. Rob: Would you mind setting me ( rmurphy ) up with write permissions so I
can commit.

Jim, I'll let you know when I get my commit permissions. If I get them early
tomorrow, I may be able to execute my commit before you make any mods.

Sorry for the short notice, but I'll be presenting the bricks use cases to
the ITAPC Thursday, so we'll come off better if we're done by then.

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

Re: [osera-isp-dev] bricks use case descriptions

[<ric...@gs...>]

<div><font size="3">Jim, I'm not sure what you mean by "behavior from the activity(ies?)"</font><font size="3"> but, I have deleted the </font><font size="2"><font size="3">ValidateTechnologyPolicy use case and its associated blank diagram with great ceremony and at no cost. <br><br>Rob, or Reddy: Lemme' known when my permissions are setup. I'm ready to commit.<br></font></font><div><div><font size="3"><br>Back to some Haskell !</font><br><br></div><font color="#990099">-----"Jim Logan" &lt;ji...@mo...&gt; wrote: -----<br><br></font><blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: ric...@gs...<br>From: "Jim Logan" &lt;ji...@mo...&gt;<br>Date: 05/13/2008 11:08PM<br>cc: ir...@to..., "'Walt Melo'" &lt;wa...@mo...&gt;, ose...@li..., cli...@gs...<br>Subject: Re: [osera-isp-dev] bricks use case descriptions<br><br>


  

<a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a> wrote:
<blockquote cite="mid:OF3...@gs..." type="cite">
  <div>Sounds good with me, how about you Ed ?<br>
  </div>
</blockquote>
Rick et al,<br><br>
Irene's summary of what happened is accurate. I think deleting this
behavior from the activity(ies?) that call
it would be best.<br><br>
-Jim
<blockquote cite="mid:OF3...@gs..." type="cite">
  <div><br>
  <div><font color="#990099">-----"Irene Polikoff"
<a class="moz-txt-link-rfc2396E" href="mailto:ir...@to...">&lt;ir...@to...&gt;</a> wrote: -----<br>
  <br>
  </font>
  <blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To:
<a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a>, <a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a>,
<a class="moz-txt-link-abbreviated" href="mailto:ed...@mo...">ed...@mo...</a><br>
From: "Irene Polikoff" <a class="moz-txt-link-rfc2396E" href="mailto:ir...@to...">&lt;ir...@to...&gt;</a><br>
Date: 05/13/2008 10:53PM<br>
cc: "'Walt Melo'" <a class="moz-txt-link-rfc2396E" href="mailto:wa...@mo...">&lt;wa...@mo...&gt;</a>,
<a class="moz-txt-link-abbreviated" href="mailto:cli...@gs...">cli...@gs...</a><br>
Subject: RE: [osera-isp-dev] bricks use case descriptions<br>
    <br>
    <div dir="ltr" align="left"><span class="843415102-14052008"><font color="#0000ff" face="Arial" size="2">I asked Jim about this in the
past. He said he originally wanted to have this use case, but then
decided it was not needed (or it was too premature to define one). I
think deleting it is the right thing to do.</font></span></div>
    <div>B </div>
    <div align="left"><font face="Arial" size="2">Irene Polikoff</font></div>
    <div align="left"><font face="Arial" size="2">Executive Partner,
TopQuadrant</font></div>
    <div align="left"><font face="Arial" size="2">tel: 914-777-0888/ </font><font face="Arial" size="2">cell: 914-329-8576</font></div>
    <div align="left"><font face="Arial" size="2"><a moz-do-not-send="true" href="http://www.topquadrant.com/">www.topquadrant.com</a></font></div>
    <div>B </div>
    <br>
    <div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
    <hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a> [<a class="moz-txt-link-freetext" href="mailto:ric...@gs...">mailto:ric...@gs...</a>] <br>
    <b>Sent:</b> Tuesday, May 13, 2008 10:39 PM<br>
    <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a>; <a class="moz-txt-link-abbreviated" href="mailto:ed...@mo...">ed...@mo...</a><br>
    <b>Cc:</b> Walt Melo; <a class="moz-txt-link-abbreviated" href="mailto:cli...@gs...">cli...@gs...</a><br>
    <b>Subject:</b> Re: [osera-isp-dev] bricks use case descriptions<br>
    </font><br>
    </div>
    <div><font size="2"><font size="3">Ed, I think you may not have the
right understanding of my request. Someone, I'm guessing Jim, partially
defined a use case called ValidateTechnologyPolicy and put it in the
model. There's an empty use case and a blank diagram.<br>
    <br>
I never asked anyone to put this use case in the model in the first
place. But what I don't think anyone wants is a model that creates the
impression we're sloppy.<br>
    <br>
Maybe the smart thing is to have me take it out for you. I'll do that
for free !<br>
    <br>
Lemme' know ...<br>
    <br>
    </font></font>
    <div><font size="3">BestB wishes,<br>
    <br>
Rick<br>
    <br>
office:B 202-501-9199<br>
cell:B 202-557-1604</font><br>
    <div><br>
    </div>
    <font color="#990099">-----"Ed Harrington"
<a class="moz-txt-link-rfc2396E" href="mailto:ed...@mo...">&lt;ed...@mo...&gt;</a> wrote: -----<br>
    <br>
    </font>
    <blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To:
<a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a>, <a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a><br>
From: "Ed Harrington" <a class="moz-txt-link-rfc2396E" href="mailto:ed...@mo...">&lt;ed...@mo...&gt;</a><br>
Date: 05/13/2008 10:22PM<br>
cc: "Walt Melo" <a class="moz-txt-link-rfc2396E" href="mailto:wa...@mo...">&lt;wa...@mo...&gt;</a>, <a class="moz-txt-link-abbreviated" href="mailto:cli...@gs...">cli...@gs...</a><br>
Subject: RE: [osera-isp-dev] bricks use case descriptions<br>
      <br>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
      <div class="Section1">
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">Rick:B  <O:P></O:P></font></span></p>
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">A very simple reminder: we were only required to
develop bAddb and bUpdateb use case descriptions and use case models.B 
Anything beyond that b and we have delivered a lot more b is gravy.B 
bValidate Technology Policyb IMHO appears to be outside the scope of
our capabilities or capacity.B  I would think that a validated Technical
Policy would need to be in place and would be reflected in the choices
that were made in the process.<O:P></O:P></font></span></p>
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">Also, I thought that we had discussed, early on in our
discussions, that we were NOT to build an application (based on use
cases) that would be part of the decision processb&amp;our Bricks
application, as reflected in our understanding of the SOW and as we
submitted our (accepted) proposal, was to only reflect decisions that
had been already made.<O:P></O:P></font></span></p>
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">I submit that your request is out of scope for the
current requirements.B  We will be happy to consider it, but it will
require additional funding.B  If appropriate, Ibll submit this to the CO.<O:P></O:P></font></span></p>
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
      <p class="MsoNormal"><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';">Regards,</span></b><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';"><O:P></O:P></span></b></p>
      <p class="MsoNormal"><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';">Ed
Harrington</span></b><span style="font-size: 14pt; color: navy;"><O:P></O:P></span></p>
      <p class="MsoNormal"><b><span style="font-size: 9pt; color: teal; font-family: 'Calibri','sans-serif';">Mobile:
+1.757.342.4552B B B B B B B  email: </span></b><b><u><span style="font-size: 9pt; color: blue; font-family: 'Calibri','sans-serif';"><a moz-do-not-send="true" href="mailto:ed...@mo..."><span style="color: blue;">ed...@mo...</span></a><O:P></O:P></span></u></b></p>
      <p class="MsoNormal"><b><u><span style="font-size: 9pt; color: blue; font-family: 'Calibri','sans-serif';"><a moz-do-not-send="true" href="http://www.modeldriven.com"><span style="color: blue;">www.modeldriven.com</span></a></span></u></b><b><span style="font-size: 9pt; color: navy; font-family: 'Calibri','sans-serif';">
      </span></b><b><span style="font-size: 9pt; color: teal; font-family: 'Calibri','sans-serif';"><O:P></O:P></span></b></p>
      <p class="MsoNormal"><span style="font-size: 8pt; color: navy; font-family: 'Calibri','sans-serif';">Disclaimer:
Privileged or Confidential information may be contained in this message
or with any files transferred with it.B  If you are not the intended
recipient, kindly destroy this message and notify the sender by return
mail.B  Opinions, conclusions and other information included in this
message that do not relate to the official business of Model Driven
Solutions are neither given nor endorsed by it.</span><span style="color: navy; font-family: 'Calibri','sans-serif';"><O:P></O:P></span></p>
      <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
      <div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
      <p class="MsoNormal"><b><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">From:</span></b><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">
<a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a>
[<a class="moz-txt-link-freetext" href="mailto:ose...@li...">mailto:ose...@li...</a>] <b>On Behalf Of </b><a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a><br>
      <b>Sent:</b> Tuesday, May 13, 2008 9:35 PM<br>
      <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a><br>
      <b>Cc:</b> Walt Melo<br>
      <b>Subject:</b> [osera-isp-dev] bricks use case descriptions<O:P></O:P></span></p>
      </div>
      <p class="MsoNormal"><O:P></O:P></p>
      <div>
      <p class="MsoNormal" style="margin-bottom: 12pt;">Jim, Irene, Rob
or Reddy:<br>
      <br>
I have entered the use case descriptions in MagicDraw. Just two things:<br>
      <br>
1. The Bricks PIM in subversion is missing the ValidateTechnologyPolicy
use case including the modelB  and the diagram. Also, there's no
description in the use case document. Jim, would you mind updating the
model and diagram ? Irene, I assume you're writing the descriptions.<br>
      <br>
Just a heads up, I have checked out the BricksPIM from subversion, so
we'll have to synchronize.<br>
      <br>
2. Rob: Would you mind setting me ( rmurphy ) up with write permissions
so I can commit.<br>
      <br>
Jim, I'll let you know when I get my commit permissions. If I get them
early tomorrow, I may be able to execute my commit before you make any
mods.<br>
      <br>
Sorry for the short notice, but I'll be presenting the bricks use cases
to the ITAPC Thursday, so we'll come off better if we're done by then.<O:P></O:P></p>
      <div>
      <p class="MsoNormal">BestB wishes,<br>
      <br>
Rick<br>
      <br>
office:B 202-501-9199<br>
cell:B 202-557-1604<O:P></O:P></p>
      </div>
      </div>
      </div>
    </blockquote>
    <br>
    </div>
    </div>
  </blockquote>
  <br>
  </div>
  </div>
  <font face="monospace" size="3"><hr size="4" width="90%"><br>-------------------------------------------------------------------------<br>This SF.net email is sponsored by: Microsoft <br>Defy all challenges. Microsoft(R) Visual Studio 2008. <br><a class="moz-txt-link-freetext" href="http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/">http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</a></font>
  <font face="monospace" size="3"><hr size="4" width="90%"><br>_______________________________________________<br>osera-isp-dev mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a><br><a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/osera-isp-dev">https://lists.sourceforge.net/lists/listinfo/osera-isp-dev</a><br> &nbsp;</font>
</blockquote><br>
</blockquote><br></div></div>

Re: [osera-isp-dev] bricks use case descriptions

[Jim L. <ji...@mo...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a> wrote:
<blockquote
 cite="mid:OF3...@gs..."
 type="cite">
  <div>Sounds good with me, how about you Ed ?<br>
  </div>
</blockquote>
Rick et al,<br>
<br>
Irene's summary of what happened is accurate. I think deleting this
behavior from the activity(ies?) that call
it would be best.<br>
<br>
-Jim
<blockquote
 cite="mid:OF3...@gs..."
 type="cite">
  <div><br>
  <div><font color="#990099">-----"Irene Polikoff"
<a class="moz-txt-link-rfc2396E" href="mailto:ir...@to...">&lt;ir...@to...&gt;</a> wrote: -----<br>
  <br>
  </font>
  <blockquote
 style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To:
<a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a>, <a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a>,
<a class="moz-txt-link-abbreviated" href="mailto:ed...@mo...">ed...@mo...</a><br>
From: "Irene Polikoff" <a class="moz-txt-link-rfc2396E" href="mailto:ir...@to...">&lt;ir...@to...&gt;</a><br>
Date: 05/13/2008 10:53PM<br>
cc: "'Walt Melo'" <a class="moz-txt-link-rfc2396E" href="mailto:wa...@mo...">&lt;wa...@mo...&gt;</a>,
<a class="moz-txt-link-abbreviated" href="mailto:cli...@gs...">cli...@gs...</a><br>
Subject: RE: [osera-isp-dev] bricks use case descriptions<br>
    <br>
    <div dir="ltr" align="left"><span class="843415102-14052008"><font
 color="#0000ff" face="Arial" size="2">I asked Jim about this in the
past. He said he originally wanted to have this use case, but then
decided it was not needed (or it was too premature to define one). I
think deleting it is the right thing to do.</font></span></div>
    <div> </div>
    <div align="left"><font face="Arial" size="2">Irene Polikoff</font></div>
    <div align="left"><font face="Arial" size="2">Executive Partner,
TopQuadrant</font></div>
    <div align="left"><font face="Arial" size="2">tel: 914-777-0888/ </font><font
 face="Arial" size="2">cell: 914-329-8576</font></div>
    <div align="left"><font face="Arial" size="2"><a
 moz-do-not-send="true" href="http://www.topquadrant.com/">www.topquadrant.com</a></font></div>
    <div> </div>
    <br>
    <div class="OutlookMessageHeader" dir="ltr" align="left"
 lang="en-us">
    <hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a> [<a class="moz-txt-link-freetext" href="mailto:ric...@gs...">mailto:ric...@gs...</a>] <br>
    <b>Sent:</b> Tuesday, May 13, 2008 10:39 PM<br>
    <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a>; <a class="moz-txt-link-abbreviated" href="mailto:ed...@mo...">ed...@mo...</a><br>
    <b>Cc:</b> Walt Melo; <a class="moz-txt-link-abbreviated" href="mailto:cli...@gs...">cli...@gs...</a><br>
    <b>Subject:</b> Re: [osera-isp-dev] bricks use case descriptions<br>
    </font><br>
    </div>
    <div><font size="2"><font size="3">Ed, I think you may not have the
right understanding of my request. Someone, I'm guessing Jim, partially
defined a use case called ValidateTechnologyPolicy and put it in the
model. There's an empty use case and a blank diagram.<br>
    <br>
I never asked anyone to put this use case in the model in the first
place. But what I don't think anyone wants is a model that creates the
impression we're sloppy.<br>
    <br>
Maybe the smart thing is to have me take it out for you. I'll do that
for free !<br>
    <br>
Lemme' know ...<br>
    <br>
    </font></font>
    <div><font size="3">Best wishes,<br>
    <br>
Rick<br>
    <br>
office: 202-501-9199<br>
cell: 202-557-1604</font><br>
    <div><br>
    </div>
    <font color="#990099">-----"Ed Harrington"
<a class="moz-txt-link-rfc2396E" href="mailto:ed...@mo...">&lt;ed...@mo...&gt;</a> wrote: -----<br>
    <br>
    </font>
    <blockquote
 style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To:
<a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a>, <a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a><br>
From: "Ed Harrington" <a class="moz-txt-link-rfc2396E" href="mailto:ed...@mo...">&lt;ed...@mo...&gt;</a><br>
Date: 05/13/2008 10:22PM<br>
cc: "Walt Melo" <a class="moz-txt-link-rfc2396E" href="mailto:wa...@mo...">&lt;wa...@mo...&gt;</a>, <a class="moz-txt-link-abbreviated" href="mailto:cli...@gs...">cli...@gs...</a><br>
Subject: RE: [osera-isp-dev] bricks use case descriptions<br>
      <br>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
      <div class="Section1">
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d">Rick:  <O:P></O:P></font></span></p>
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d"><O:P></O:P></font></span></p>
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d">A very simple reminder: we were only required to
develop “Add” and “Update” use case descriptions and use case models. 
Anything beyond that – and we have delivered a lot more – is gravy. 
“Validate Technology Policy” IMHO appears to be outside the scope of
our capabilities or capacity.  I would think that a validated Technical
Policy would need to be in place and would be reflected in the choices
that were made in the process.<O:P></O:P></font></span></p>
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d"><O:P></O:P></font></span></p>
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d">Also, I thought that we had discussed, early on in our
discussions, that we were NOT to build an application (based on use
cases) that would be part of the decision process…our Bricks
application, as reflected in our understanding of the SOW and as we
submitted our (accepted) proposal, was to only reflect decisions that
had been already made.<O:P></O:P></font></span></p>
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d"><O:P></O:P></font></span></p>
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d">I submit that your request is out of scope for the
current requirements.  We will be happy to consider it, but it will
require additional funding.  If appropriate, I’ll submit this to the CO.<O:P></O:P></font></span></p>
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d"><O:P></O:P></font></span></p>
      <p class="MsoNormal"><b><span
 style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';">Regards,</span></b><b><span
 style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';"><O:P></O:P></span></b></p>
      <p class="MsoNormal"><b><span
 style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';">Ed
Harrington</span></b><span style="font-size: 14pt; color: navy;"><O:P></O:P></span></p>
      <p class="MsoNormal"><b><span
 style="font-size: 9pt; color: teal; font-family: 'Calibri','sans-serif';">Mobile:
+1.757.342.4552        email: </span></b><b><u><span
 style="font-size: 9pt; color: blue; font-family: 'Calibri','sans-serif';"><a
 moz-do-not-send="true" href="mailto:ed...@mo..."><span
 style="color: blue;">ed...@mo...</span></a><O:P></O:P></span></u></b></p>
      <p class="MsoNormal"><b><u><span
 style="font-size: 9pt; color: blue; font-family: 'Calibri','sans-serif';"><a
 moz-do-not-send="true" href="http://www.modeldriven.com"><span
 style="color: blue;">www.modeldriven.com</span></a></span></u></b><b><span
 style="font-size: 9pt; color: navy; font-family: 'Calibri','sans-serif';">
      </span></b><b><span
 style="font-size: 9pt; color: teal; font-family: 'Calibri','sans-serif';"><O:P></O:P></span></b></p>
      <p class="MsoNormal"><span
 style="font-size: 8pt; color: navy; font-family: 'Calibri','sans-serif';">Disclaimer:
Privileged or Confidential information may be contained in this message
or with any files transferred with it.  If you are not the intended
recipient, kindly destroy this message and notify the sender by return
mail.  Opinions, conclusions and other information included in this
message that do not relate to the official business of Model Driven
Solutions are neither given nor endorsed by it.</span><span
 style="color: navy; font-family: 'Calibri','sans-serif';"><O:P></O:P></span></p>
      <p class="MsoNormal"><span
 style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font
 color="#1f497d"><O:P></O:P></font></span></p>
      <div
 style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
      <p class="MsoNormal"><b><span
 style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">From:</span></b><span
 style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">
<a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a>
[<a class="moz-txt-link-freetext" href="mailto:ose...@li...">mailto:ose...@li...</a>] <b>On Behalf Of </b><a class="moz-txt-link-abbreviated" href="mailto:ric...@gs...">ric...@gs...</a><br>
      <b>Sent:</b> Tuesday, May 13, 2008 9:35 PM<br>
      <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a><br>
      <b>Cc:</b> Walt Melo<br>
      <b>Subject:</b> [osera-isp-dev] bricks use case descriptions<O:P></O:P></span></p>
      </div>
      <p class="MsoNormal"><O:P></O:P></p>
      <div>
      <p class="MsoNormal" style="margin-bottom: 12pt;">Jim, Irene, Rob
or Reddy:<br>
      <br>
I have entered the use case descriptions in MagicDraw. Just two things:<br>
      <br>
1. The Bricks PIM in subversion is missing the ValidateTechnologyPolicy
use case including the model  and the diagram. Also, there's no
description in the use case document. Jim, would you mind updating the
model and diagram ? Irene, I assume you're writing the descriptions.<br>
      <br>
Just a heads up, I have checked out the BricksPIM from subversion, so
we'll have to synchronize.<br>
      <br>
2. Rob: Would you mind setting me ( rmurphy ) up with write permissions
so I can commit.<br>
      <br>
Jim, I'll let you know when I get my commit permissions. If I get them
early tomorrow, I may be able to execute my commit before you make any
mods.<br>
      <br>
Sorry for the short notice, but I'll be presenting the bricks use cases
to the ITAPC Thursday, so we'll come off better if we're done by then.<O:P></O:P></p>
      <div>
      <p class="MsoNormal">Best wishes,<br>
      <br>
Rick<br>
      <br>
office: 202-501-9199<br>
cell: 202-557-1604<O:P></O:P></p>
      </div>
      </div>
      </div>
    </blockquote>
    <br>
    </div>
    </div>
  </blockquote>
  <br>
  </div>
  </div>
  <pre wrap="">
<hr size="4" width="90%">
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
<a class="moz-txt-link-freetext" href="http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/">http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
osera-isp-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ose...@li...">ose...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/osera-isp-dev">https://lists.sourceforge.net/lists/listinfo/osera-isp-dev</a>
  </pre>
</blockquote>
<br>
</body>
</html>

Re: [osera-isp-dev] bricks use case descriptions

[<ric...@gs...>]

<div>Sounds good with me, how about you Ed ?<br><br>BTW - Would you be able to talk some tomorrow about what we mean when we say one policy supercedes another ?<br><br><div>Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604<br><div><br></div><font color="#990099">-----"Irene Polikoff" &lt;ir...@to...&gt; wrote: -----<br><br></font><blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: ric...@gs..., ose...@li..., ed...@mo...<br>From: "Irene Polikoff" &lt;ir...@to...&gt;<br>Date: 05/13/2008 10:53PM<br>cc: "'Walt Melo'" &lt;wa...@mo...&gt;, cli...@gs...<br>Subject: RE: [osera-isp-dev] bricks use case descriptions<br><br>



<div dir="ltr" align="left"><span class="843415102-14052008"><font color="#0000ff" face="Arial" size="2">I asked Jim about this in the past. He said he originally 
wanted to have this use case, but then decided it was not needed (or it was too 
premature to define one). I think deleting it is the right thing to 
do.</font></span></div>
<div>&nbsp;</div>
<div align="left"><font face="Arial" size="2">Irene Polikoff</font></div>
<div align="left"><font face="Arial" size="2">Executive Partner, 
TopQuadrant</font></div>
<div align="left"><font face="Arial" size="2">tel: 914-777-0888/ </font><font face="Arial" size="2">cell: 914-329-8576</font></div>
<div align="left"><font face="Arial" size="2"><a href="http://www.topquadrant.com/">www.topquadrant.com</a></font></div>
<div>&nbsp;</div><br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> ric...@gs... 
[mailto:ric...@gs...] <br><b>Sent:</b> Tuesday, May 13, 2008 10:39 
PM<br><b>To:</b> ose...@li...; 
ed...@mo...<br><b>Cc:</b> Walt Melo; 
cli...@gs...<br><b>Subject:</b> Re: [osera-isp-dev] bricks use case 
descriptions<br></font><br></div>
<div></div>
<div><font size="2"><font size="3">Ed, I think you may not have the right 
understanding of my request. Someone, I'm guessing Jim, partially defined a use 
case called ValidateTechnologyPolicy and put it in the model. There's an empty 
use case and a blank diagram.<br><br>I never asked anyone to put this use case 
in the model in the first place. But what I don't think anyone wants is a model 
that creates the impression we're sloppy.<br><br>Maybe the smart thing is to 
have me take it out for you. I'll do that for free !<br><br>Lemme' know 
...<br><br></font></font>
<div><font size="3">Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604</font><br>
<div><br></div><font color="#990099">-----"Ed Harrington" 
&lt;ed...@mo...&gt; wrote: -----<br><br></font>
<blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: 
  ric...@gs..., ose...@li...<br>From: "Ed 
  Harrington" &lt;ed...@mo...&gt;<br>Date: 05/13/2008 10:22PM<br>cc: 
  "Walt Melo" &lt;wa...@mo...&gt;, 
  cli...@gs...<br>Subject: RE: [osera-isp-dev] bricks use case 
  descriptions<br><br><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
  <div class="Section1">
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">Rick:&nbsp; <O:P></O:P></font></span></p>
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">A very simple reminder: we were only required to develop “Add” 
  and “Update” use case descriptions and use case models.&nbsp; Anything beyond 
  that – and we have delivered a lot more – is gravy.&nbsp; “Validate Technology 
  Policy” IMHO appears to be outside the scope of our capabilities or 
  capacity.&nbsp; I would think that a validated Technical Policy would need to 
  be in place and would be reflected in the choices that were made in the 
  process.<O:P></O:P></font></span></p>
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">Also, I thought that we had discussed, early on in our 
  discussions, that we were NOT to build an application (based on use cases) 
  that would be part of the decision process…our Bricks application, as 
  reflected in our understanding of the SOW and as we submitted our (accepted) 
  proposal, was to only reflect decisions that had been already 
  made.<O:P></O:P></font></span></p>
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d">I submit that your request is out of scope for the current 
  requirements.&nbsp; We will be happy to consider it, but it will require 
  additional funding.&nbsp; If appropriate, I’ll submit this to the 
  CO.<O:P></O:P></font></span></p>
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
  <p class="MsoNormal"><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';">Regards,</span></b><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';"><O:P></O:P></span></b></p>
  <p class="MsoNormal"><b><span style="font-size: 14pt; color: red; font-family: 'Monotype Corsiva';">Ed 
  Harrington</span></b><span style="font-size: 14pt; color: navy;"><O:P></O:P></span></p>
  <p class="MsoNormal"><b><span style="font-size: 9pt; color: teal; font-family: 'Calibri','sans-serif';">Mobile: 
  +1.757.342.4552&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email: 
  </span></b><b><u><span style="font-size: 9pt; color: blue; font-family: 'Calibri','sans-serif';"><a href="mailto:ed...@mo..."><span style="color: blue;">ed...@mo...</span></a><O:P></O:P></span></u></b></p>
  <p class="MsoNormal"><b><u><span style="font-size: 9pt; color: blue; font-family: 'Calibri','sans-serif';"><a href="http://www.modeldriven.com"><span style="color: blue;">www.modeldriven.com</span></a></span></u></b><b><span style="font-size: 9pt; color: navy; font-family: 'Calibri','sans-serif';"> 
  </span></b><b><span style="font-size: 9pt; color: teal; font-family: 'Calibri','sans-serif';"><O:P></O:P></span></b></p>
  <p class="MsoNormal"><span style="font-size: 8pt; color: navy; font-family: 'Calibri','sans-serif';">Disclaimer: 
  Privileged or Confidential information may be contained in this message or 
  with any files transferred with it.&nbsp; If you are not the intended 
  recipient, kindly destroy this message and notify the sender by return 
  mail.&nbsp; Opinions, conclusions and other information included in this 
  message that do not relate to the official business of Model Driven Solutions 
  are neither given nor endorsed by it.</span><span style="color: navy; font-family: 'Calibri','sans-serif';"><O:P></O:P></span></p>
  <p class="MsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif';"><font color="#1f497d"><O:P></O:P></font></span></p>
  <div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
  <p class="MsoNormal"><b><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">From:</span></b><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';"> 
  ose...@li... 
  [mailto:ose...@li...] <b>On Behalf Of 
  </b>ric...@gs...<br><b>Sent:</b> Tuesday, May 13, 2008 9:35 
  PM<br><b>To:</b> ose...@li...<br><b>Cc:</b> Walt 
  Melo<br><b>Subject:</b> [osera-isp-dev] bricks use case 
  descriptions<O:P></O:P></span></p></div>
  <p class="MsoNormal"><O:P></O:P></p>
  <div>
  <p class="MsoNormal" style="margin-bottom: 12pt;">Jim, Irene, Rob or 
  Reddy:<br><br>I have entered the use case descriptions in MagicDraw. Just two 
  things:<br><br>1. The Bricks PIM in subversion is missing the 
  ValidateTechnologyPolicy use case including the model&nbsp; and the diagram. 
  Also, there's no description in the use case document. Jim, would you mind 
  updating the model and diagram ? Irene, I assume you're writing the 
  descriptions.<br><br>Just a heads up, I have checked out the BricksPIM from 
  subversion, so we'll have to synchronize.<br><br>2. Rob: Would you mind 
  setting me ( rmurphy ) up with write permissions so I can commit.<br><br>Jim, 
  I'll let you know when I get my commit permissions. If I get them early 
  tomorrow, I may be able to execute my commit before you make any 
  mods.<br><br>Sorry for the short notice, but I'll be presenting the bricks use 
  cases to the ITAPC Thursday, so we'll come off better if we're done by 
  then.<O:P></O:P></p>
  <div>
  <p class="MsoNormal">Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604<O:P></O:P></p></div></div></div></blockquote><br></div></div></blockquote><br></div></div>

Re: [osera-isp-dev] bricks use case descriptions

[Irene P. <ir...@to...>]

I asked Jim about this in the past. He said he originally wanted to have
this use case, but then decided it was not needed (or it was too premature
to define one). I think deleting it is the right thing to do.
 
Irene Polikoff
Executive Partner, TopQuadrant
tel: 914-777-0888/ cell: 914-329-8576
www.topquadrant.com <http://www.topquadrant.com/> 
 

  _____  

From: ric...@gs... [mailto:ric...@gs...] 
Sent: Tuesday, May 13, 2008 10:39 PM
To: ose...@li...; ed...@mo...
Cc: Walt Melo; cli...@gs...
Subject: Re: [osera-isp-dev] bricks use case descriptions


Ed, I think you may not have the right understanding of my request. Someone,
I'm guessing Jim, partially defined a use case called
ValidateTechnologyPolicy and put it in the model. There's an empty use case
and a blank diagram.

I never asked anyone to put this use case in the model in the first place.
But what I don't think anyone wants is a model that creates the impression
we're sloppy.

Maybe the smart thing is to have me take it out for you. I'll do that for
free !

Lemme' know ...


Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604


-----"Ed Harrington" <ed...@mo...> wrote: -----



To: ric...@gs..., ose...@li...
From: "Ed Harrington" <ed...@mo...>
Date: 05/13/2008 10:22PM
cc: "Walt Melo" <wa...@mo...>, cli...@gs...
Subject: RE: [osera-isp-dev] bricks use case descriptions



Rick:  



A very simple reminder: we were only required to develop "Add" and "Update"
use case descriptions and use case models.  Anything beyond that - and we
have delivered a lot more - is gravy.  "Validate Technology Policy" IMHO
appears to be outside the scope of our capabilities or capacity.  I would
think that a validated Technical Policy would need to be in place and would
be reflected in the choices that were made in the process.



Also, I thought that we had discussed, early on in our discussions, that we
were NOT to build an application (based on use cases) that would be part of
the decision process.our Bricks application, as reflected in our
understanding of the SOW and as we submitted our (accepted) proposal, was to
only reflect decisions that had been already made.



I submit that your request is out of scope for the current requirements.  We
will be happy to consider it, but it will require additional funding.  If
appropriate, I'll submit this to the CO.



Regards,

Ed Harrington

Mobile: +1.757.342.4552        email:  <mailto:ed...@mo...>
ed...@mo...

 <http://www.modeldriven.com> www.modeldriven.com 

Disclaimer: Privileged or Confidential information may be contained in this
message or with any files transferred with it.  If you are not the intended
recipient, kindly destroy this message and notify the sender by return mail.
Opinions, conclusions and other information included in this message that do
not relate to the official business of Model Driven Solutions are neither
given nor endorsed by it.



From: ose...@li...
[mailto:ose...@li...] On Behalf Of
ric...@gs...
Sent: Tuesday, May 13, 2008 9:35 PM
To: ose...@li...
Cc: Walt Melo
Subject: [osera-isp-dev] bricks use case descriptions



Jim, Irene, Rob or Reddy:

I have entered the use case descriptions in MagicDraw. Just two things:

1. The Bricks PIM in subversion is missing the ValidateTechnologyPolicy use
case including the model  and the diagram. Also, there's no description in
the use case document. Jim, would you mind updating the model and diagram ?
Irene, I assume you're writing the descriptions.

Just a heads up, I have checked out the BricksPIM from subversion, so we'll
have to synchronize.

2. Rob: Would you mind setting me ( rmurphy ) up with write permissions so I
can commit.

Jim, I'll let you know when I get my commit permissions. If I get them early
tomorrow, I may be able to execute my commit before you make any mods.

Sorry for the short notice, but I'll be presenting the bricks use cases to
the ITAPC Thursday, so we'll come off better if we're done by then.

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

Re: [osera-isp-dev] bricks use case descriptions

[<ric...@gs...>]

<div><font size="2"><font size="3">Ed, I think you may not have the right understanding of my request. Someone, I'm guessing Jim, partially defined a use case called ValidateTechnologyPolicy and put it in the model. There's an empty use case and a blank diagram.<br><br>I never asked anyone to put this use case in the model in the first place. But what I don't think anyone wants is a model that creates the impression we're sloppy.<br><br>Maybe the smart thing is to have me take it out for you. I'll do that for free !<br><br>Lemme' know ...<br><br></font></font><div><font size="3">Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604</font><br><div><br></div><font color="#990099">-----"Ed Harrington" &lt;ed...@mo...&gt; wrote: -----<br><br></font><blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: ric...@gs..., ose...@li...<br>From: "Ed Harrington" &lt;ed...@mo...&gt;<br>Date: 05/13/2008 10:22PM<br>cc: "Walt Melo" &lt;wa...@mo...&gt;, cli...@gs...<br>Subject: RE: [osera-isp-dev] bricks use case descriptions<br><br>





<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->


<div class="Section1">

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d">Rick:&nbsp; <o:p></o:p></font></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d"><o:p>&nbsp;</o:p></font></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d">A very simple reminder: we were only required to develop “Add”
and “Update” use case descriptions and use case models.&nbsp; Anything beyond that –
and we have delivered a lot more – is gravy.&nbsp; “Validate Technology Policy” IMHO
appears to be outside the scope of our capabilities or capacity.&nbsp; I would think
that a validated Technical Policy would need to be in place and would be
reflected in the choices that were made in the process.<o:p></o:p></font></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d"><o:p>&nbsp;</o:p></font></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d">Also, I thought that we had discussed, early on in our
discussions, that we were NOT to build an application (based on use cases) that
would be part of the decision process…our Bricks application, as reflected in
our understanding of the SOW and as we submitted our (accepted) proposal, was
to only reflect decisions that had been already made.<o:p></o:p></font></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d"><o:p>&nbsp;</o:p></font></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d">I submit that your request is out of scope for the current requirements.&nbsp;
We will be happy to consider it, but it will require additional funding.&nbsp; If
appropriate, I’ll submit this to the CO.<o:p></o:p></font></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d"><o:p>&nbsp;</o:p></font></span></p>

<p class="MsoNormal"><b><span style="font-size: 14pt; font-family: &quot;Monotype Corsiva&quot;; color: red;">Regards,</span></b><b><span style="font-size: 14pt; font-family: &quot;Monotype Corsiva&quot;; color: red;"><o:p></o:p></span></b></p>

<p class="MsoNormal"><b><span style="font-size: 14pt; font-family: &quot;Monotype Corsiva&quot;; color: red;">Ed Harrington</span></b><span style="font-size: 14pt; color: navy;"><o:p></o:p></span></p>

<p class="MsoNormal"><b><span style="font-size: 9pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: teal;">Mobile: +1.757.342.4552&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
email: </span></b><b><u><span style="font-size: 9pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: blue;"><a href="mailto:ed...@mo..."><span style="color: blue;">ed...@mo...</span></a><o:p></o:p></span></u></b></p>

<p class="MsoNormal"><b><u><span style="font-size: 9pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: blue;"><a href="http://www.modeldriven.com"><span style="color: blue;">www.modeldriven.com</span></a></span></u></b><b><span style="font-size: 9pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: navy;"> </span></b><b><span style="font-size: 9pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: teal;"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size: 8pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: navy;">Disclaimer: Privileged or Confidential information may be contained
in this message or with any files transferred with it.&nbsp; If you are not the
intended recipient, kindly destroy this message and notify the sender by return
mail.&nbsp; Opinions, conclusions and other information included in this
message that do not relate to the official business of Model Driven Solutions
are neither given nor endorsed by it.</span><span style="font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: navy;"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><font color="#1f497d"><o:p>&nbsp;</o:p></font></span></p>

<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">

<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: &quot;Tahoma&quot;,&quot;sans-serif&quot;;">From:</span></b><span style="font-size: 10pt; font-family: &quot;Tahoma&quot;,&quot;sans-serif&quot;;"> ose...@li...
[mailto:ose...@li...] <b>On Behalf Of </b>ric...@gs...<br>
<b>Sent:</b> Tuesday, May 13, 2008 9:35 PM<br>
<b>To:</b> ose...@li...<br>
<b>Cc:</b> Walt Melo<br>
<b>Subject:</b> [osera-isp-dev] bricks use case descriptions<o:p></o:p></span></p>

</div>

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

<div>

<p class="MsoNormal" style="margin-bottom: 12pt;">Jim, Irene, Rob or Reddy:<br><br>
I have entered the use case descriptions in MagicDraw. Just two things:<br><br>
1. The Bricks PIM in subversion is missing the ValidateTechnologyPolicy use
case including the model&nbsp; and the diagram. Also, there's no description in
the use case document. Jim, would you mind updating the model and diagram ?
Irene, I assume you're writing the descriptions.<br><br>
Just a heads up, I have checked out the BricksPIM from subversion, so we'll
have to synchronize.<br><br>
2. Rob: Would you mind setting me ( rmurphy ) up with write permissions so I
can commit.<br><br>
Jim, I'll let you know when I get my commit permissions. If I get them early
tomorrow, I may be able to execute my commit before you make any mods.<br><br>
Sorry for the short notice, but I'll be presenting the bricks use cases to the
ITAPC Thursday, so we'll come off better if we're done by then.<o:p></o:p></p>

<div>

<p class="MsoNormal">Best&nbsp;wishes,<br><br>
Rick<br><br>
office:&nbsp;202-501-9199<br>
cell:&nbsp;202-557-1604<o:p></o:p></p>

</div>

</div>

</div>

</blockquote><br></div></div>

Re: [osera-isp-dev] bricks use case descriptions

[Ed H. <ed...@mo...>]

Rick:  

 

A very simple reminder: we were only required to develop “Add” and “Update” use case descriptions and use case models.  Anything beyond that – and we have delivered a lot more – is gravy.  “Validate Technology Policy” IMHO appears to be outside the scope of our capabilities or capacity.  I would think that a validated Technical Policy would need to be in place and would be reflected in the choices that were made in the process.

 

Also, I thought that we had discussed, early on in our discussions, that we were NOT to build an application (based on use cases) that would be part of the decision process…our Bricks application, as reflected in our understanding of the SOW and as we submitted our (accepted) proposal, was to only reflect decisions that had been already made.

 

I submit that your request is out of scope for the current requirements.  We will be happy to consider it, but it will require additional funding.  If appropriate, I’ll submit this to the CO.

 

Regards,

Ed Harrington

Mobile: +1.757.342.4552        email: ed...@mo... <mailto:ed...@mo...> 

www.modeldriven.com <http://www.modeldriven.com>  

Disclaimer: Privileged or Confidential information may be contained in this message or with any files transferred with it.  If you are not the intended recipient, kindly destroy this message and notify the sender by return mail.  Opinions, conclusions and other information included in this message that do not relate to the official business of Model Driven Solutions are neither given nor endorsed by it.

 

From: ose...@li... [mailto:ose...@li...] On Behalf Of ric...@gs...
Sent: Tuesday, May 13, 2008 9:35 PM
To: ose...@li...
Cc: Walt Melo
Subject: [osera-isp-dev] bricks use case descriptions

 

Jim, Irene, Rob or Reddy:

I have entered the use case descriptions in MagicDraw. Just two things:

1. The Bricks PIM in subversion is missing the ValidateTechnologyPolicy use case including the model  and the diagram. Also, there's no description in the use case document. Jim, would you mind updating the model and diagram ? Irene, I assume you're writing the descriptions.

Just a heads up, I have checked out the BricksPIM from subversion, so we'll have to synchronize.

2. Rob: Would you mind setting me ( rmurphy ) up with write permissions so I can commit.

Jim, I'll let you know when I get my commit permissions. If I get them early tomorrow, I may be able to execute my commit before you make any mods.

Sorry for the short notice, but I'll be presenting the bricks use cases to the ITAPC Thursday, so we'll come off better if we're done by then.

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

[osera-isp-dev] bricks use case descriptions

[<ric...@gs...>]

<div><font size="2"><font size="3">Jim, Irene, Rob or Reddy:<br><br>I have entered the use case descriptions in MagicDraw. Just two things:<br><br>1. The Bricks PIM in subversion is missing the ValidateTechnologyPolicy use case including the model&nbsp; and the diagram. Also, there's no description in the use case document. Jim, would you mind updating the model and diagram ? Irene, I assume you're writing the descriptions.<br><br>Just a heads up, I have checked out the BricksPIM from subversion, so we'll have to synchronize.<br><br>2. Rob: Would you mind setting me ( rmurphy ) up with write permissions so I can commit.<br><br>Jim, I'll let you know when I get my commit permissions. If I get them early tomorrow, I may be able to execute my commit before you make any mods.<br><br>Sorry for the short notice, but I'll be presenting the bricks use cases to the ITAPC Thursday, so we'll come off better if we're done by then.</font><br><br></font><div>Best&nbsp;wishes,<br><br>Rick<br><br>office:&nbsp;202-501-9199<br>cell:&nbsp;202-557-1604<br></div></div>

[osera-isp-dev] OISP Meeting Reminder

[Cory C. <co...@mo...>]

When: Tuesday, May 13, 2008 1:30 PM-2:30 PM (GMT-05:00) Eastern Time (US & Canada).
Where: MDS & Gotomeeting

*~*~*~*~*~*~*~*~*~*

Please join my meeting at 
 https://www1.gotomeeting.com/join/891771730 
Conference Call: (605) 475-8585, access code 891-771-730 
Meeting ID: 891-771-730