Capability (C043):— representing_environment_typical Date: 2007/07/11 16:32:00
Revision: 1.24
CoverContentsIntro.Overview Info. modelCapabilities.Ref. dataIssues

Issue raised against: representing_environment_typical

OTHER issues

Open issue Issue: GYL-7 by Leif Gyllstrom (2005-11-09) minor_technical issue
Resolution: Accept. Status: open

In the examples given the State_definition representing the state is classified as State_of_environment. This is missleading since the State_definition is not defining the state of the environment but the environment itself. If Environment_typical would have been a subclass od State_definition in the ARM it would probably have been namned Environment_typical. Therefore I would suggest to create a subclass to State_definition in the RDL named "Environment_typical"

GENERAL issues

Closed issue Issue: GYL-1 by Leif Gyllstrom (2004-03-06) editorial issue
Resolution: Accept. Status: closed

Issue against the introduction if both the Indroduction and Content sections. The capability should not be restricted to be used only to describe a typical environment in which a product_as_realized operates. This is just an example of usage of this module. The Capability "Referencing_product_as_realized" should not be included in the dependent capability list. Requires changes to the text, e.g. last sentences under section "Representing environment typical" and a to couple other places where product_as_realized is refered to.
Comment: (Rob Bodington 04-05-07)
Corrected

Closed issue Issue: GYL-2 by Leif Gyllstrom (2004-03-06) minor_technical issue
Resolution: Accept. Status: closed

The "Representing_environment_actual" should not be incuded as a dependent capability.
Comment: (Rob Bodington 04-05-07)
Corrected

Closed issue Issue: GYL-3 by Leif Gyllstrom (2004-03-06) editorial issue
Resolution: Accept. Status: closed

Figure 2. Both State_definition and Applied_state_definition_assignment should not classified as "Environment". Suggestion, change the classification of the assignment entity to e.g. "valid_environment" (also see example within the "representing_analysis_result" capability).
Comment: (Rob Bodington 04-05-07)
Corrected classifications. State_definition classified as "State_of_environment" Applied_state_definition_assignment classified as "Operating_environment"

Closed issue Issue: GYL-4 by Leif Gyllstrom (2004-03-06) minor_technical issue
Resolution: Accept. Status: closed

Change the usage of the "Representing_person_organization" capability to "Referencing_person_organization".
Comment: (Rob Bodington 04-05-07)
Corrected

Closed issue Issue: GYL-5 by Leif Gyllstrom (2004-03-06) minor_technical issue
Resolution: Accept. Status: closed

Add the usage of the "Assigning_product_properties" capability.
Comment: (Rob Bodington 04-05-07)
Corrected

Closed issue Issue: GYL-6 by Leif Gyllstrom (2004-03-06) minor_technical issue
Resolution: Accept. Status: closed

Should the state_definition module really be part of the usage section since it's being brought in by the representing_state_type capability ?
Comment: (Rob Bodington 04-05-07)
The capability is no longer dependent on representing_state_type capability As all that is required from the state_definition module is state_definition. It makes no sense to typical environments. Any environment can follow on from any other environment.

Closed issue Issue: RBN-1 by Rob Bodington (04-09-02) minor_technical issue
Resolution: Accept. Status: closed

The class "created" has been changed to "Date_created". The diagram needs to change
Comment: (Rob Bodington 04-09-29)
Changed