Re: [Fwd: [regrep-cc-review] [REVISITED AGAIN][regrep-cc-review] CCTS Spec RIM Mappings Revisited: [S8] to [S18]]

["Chiusano Joseph" <chiusano_joseph@bah.com>]

Please see comments marked with <JMC2>. There is a question in the first
one - the rest are all concurrence.

Joe

Diego Ballvé wrote:
> 
> Minor comments, tagged by <Diego>. Basically I would change some of
> the "N/A".. we might not strictly fulfil the requirement but we're
> using an equivalent way to achieve the desired feature. Besides that,
> agreed.
> 
> Diego
> 
> -------------------
> 
> 7.1.3 Stored Core Component Properties
> 
> [S8]
> Stored Core Component Properties shall be stored as part of the stored
> Aggregate Core Component to which they belong, i.e. they shall never
> exist independently of their owning Aggregate Core Component.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> </JMC>
> 
> <Diego>
> Stored as part of BCC/ASCC + RIM Association.
> </Diego>

<JMC2>
Ah, good point - we should note for this requirement our new proposed
handling of Properties, as slots on BCCs and ASCCs. Can you please
clarify what you mean by "+ RIM Association"? Is this the association
between a BCC and ASCC?
</JMC2>
 
> [S9]
> Stored Core Component Properties shall be defined as one of the two
> recognized types: Basic Core Component Property or Association Core
> Component Property.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> </JMC>
> 
> [S10]
> Stored Core Component Properties shall include the following Attributes:
> - Property Term
> - Cardinality
> 
> <JMC>
> Property Term and Cardinality will be represented as attributes of Basic
> Core Components (BCCs) and Association Core Components (ASCCs), through
> Slots.
> 
> NOTE: For representation of Cardinality, see "Cardinality" thread.
> </JMC>
> 
> p.76:
> 
> 7.1.4 Stored Basic Core Component Properties
> 
> [S11]
> Basic Core Component Properties are a particular category of Core
> Component Properties. As such, stored Basic Core Component Properties
> shall include all Attributes of stored Core Component Properties.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> </JMC>
> 
> <Diego>
> Covered as defined in comments for [S10].
> </Diego>

<JMC2>
I concur - I'll update the Requirements Mapping document to reflect
this.
</JMC2>
 
> [S12]
> Stored Basic Core Component Properties shall be linked to the Data Type
> that describes the possible values of the Basic Core Component Property.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> This linkage will now be directly from a Data Type to a BCC.
> </JMC>
> 
> 7.1.5 Stored Association Core Component Properties
> 
> [S13]
> Association Core Component Properties are a particular category of Core
> Component Properties. As such, stored Association Core Component
> Properties shall include all Attributes of stored Core Component
> Properties.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> </JMC>
> 
> <Diego>
> Stored as part of BCC/ASCC + RIM Association.
> </Diego>

<JMC2>
I concur - I'll update the Requirements Mapping document to reflect
this.
</JMC2>
 
> [S14]
> Stored Association Core Component Properties shall be linked to the
> Aggregate Core Component that describes the structure of the Association
> Core Component Property.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> </JMC>
> 
> 7.1.6 Stored Basic Core Components
> 
> [S15]
> Basic Core Components are a particular category of Core Components. As
> such, stored Basic Core Components shall include all Attributes of
> stored Core Components.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> </JMC>
> 
> <Diego>
> Stored as part of BCC/ASCC + RIM Association.
> </Diego>

<JMC2>
I concur - I'll update the Requirements Mapping document to reflect
this.
</JMC2>
 
> [S16]
> Stored Basic Core Components shall represent a Basic Core Component
> Property of a particular Aggregate Core Component.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> However, we will represent the relationship between ACCs and BCCs
> through Associations.
> </JMC>
> 
> 7.1.7 Stored Association Core Components
> 
> [S17]
> Association Core Components are a particular category of Core
> Components. As such, stored Association Core Components shall include
> all Attributes of stored Core Components.
> 
> <JMC>
> We will simply include all attributes of Core Components with the
> Association Core Component (ASCC) ObjectType.
> </JMC>
> 
> [S18]
> Stored Association Core Components shall represent an Association Core
> Component Property of a particular Aggregate Core Component.
> 
> <JMC>
> N/A, since we are not storing Core Component Properties as entities.
> However, we will represent the relationship between ACCs and ASCCs
> through Associations.
> </JMC>
> 
> <Diego>
> Well, stored ASCC do represent a property from an ACC, even though
> properties are not saved as entities.
> <Diego>

<JMC2>
I concur - I'll update the Requirements Mapping document to reflect
this.
</JMC2>
 
> THE END.
begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard