wolfgangfahl / arcon Goto Github PK

Annotations - Requirements, Rhapsody can define requirements that is loaded 
into Arcon. How are they used and defined.

Requirements hold no special code yet.

Stereotypes are linked from the profile with different names depending on the 
type, for example: base_Class, base_Package, etc. How can we support all 
possible types without specific defining all of them in the code (like it is 
now)

Defining a generic return type '@' in arch rules does not work in Papyrus. Need 
to define a standard and translate it. Use <undefined>?

Set Standard: Letting the return have <undefined> type equals defining type '@' 
in Rhapsody.

Special rule for constraint {private} - Is it needed for package as well?

Property, Multiplicity - for generic attributes, use * multiplicity instead of 
% setting it to unlimited number? '%' could define only the matching.

Tagged values are handled differently in Rhapsody an Papyrus. Rhapsody using 
old way while Papyrus using uml2.0 standard where tag definitions are set on 
the stereotypes and tagged values defined for classes realizing the 
stereotypes. What difference does this make for defining and checking rules.

Tagged values are defined in the profile definition within the XMI file. Only 
modified values are shown, default values were left out (false for a boolean).

Property, Multiplicity - How does Arcon want the string to look like?

Seems to be no constraint as long as both arch and system use the same way. 
Current is <lower>..<upper>, (e.g. "1..*")

If the tagged definition use the default value then it won't always be printed 
in the XMI file. How do we read/get the Tagged value if it isn't in the XMI 
file. Also ArCon don't have the same default values which may lead to problems.

Implement reading for links.

InstanceTranslator

Turn off debug (for plugin) printing for release version of ArconPlugin

Asynchronous Operation. How is it defined in xmi and papyrus. How to read it.

Check model stereotypes "System_Model" and "Arch_Rules_Model" in validation 
phase instead of when reading the model.

Package_Composition_Rule::Check - has some special code. Look over if
implementing package visibility.

Can not set stereotype on Association_Ends in Papyrus, can only be done on the 
Association. 

Arcon only checks it when it is on the Association_End. Affected rule: T11
and more

Association does not exist in Arcon. Can not connect stereotypes to an 
Association. Getting reports from XMI_Reader. Decide how to handle it.

Do not create an Association element, but just set the stereotype on the 
Association_Ends.

Constructor

Set Standard: Same name as owner Class and do not have a return type.

Type, how should the type string really look like. Investage when using with 
implementation

Test if there are any case where current implementation does not work.

Links. Rhapsody use links but links can only be set between objects. Papyrus 
does only use class diagram and not Model Object Diagram. Seem to exist a Link 
edge in Papyrus, investigate.

The counterpart for link is InstanceSpecification Link in Papyrus. Also an 
object's counterpart is InstanceSpecification.

Association_End - Classifier - When a class is the classifier the 
association_end becomes a property in the source code (should an external 
property be created or use the Association_End as property)?

Association_End is used as property.

ClassDiagram - No info about this inside the model itself. Extra support added 
for the modelling tool and not the model itself. Decide how to do with this for 
Papyrus.

Defining a return type of class C1 that exist in arch_rules does not seem to 
work correctly. The return type in system model should be of a stereotype 
<<C1>>. Possible cause: Type is not set correctly. Should be set in 
postTranslate when we have all types.

Fixed in rev 106

Both Association_Ends will not receive the stereotype. Only the first one found 
with GetElementByID

First one seem to be the association_end that is navigable (i.e. the property), 
so the one getting the stereotype is the one we want it on.

Operation behavior - How is it used by Arcon. Not read atm by XMI_Reader. Not 
yet supported, T14?

Behavior is the implementation of the operation.

Constructor / Deconstructor - How to define them in Papyrus? Discuss.

Remember that skipping the return value is the same as saying it is 
unconstrained in the arch_model. So just letting constructor have no return 
type without a naming constraint is no good idea.

Find out which association_end that is From_End vs. To_End

The ID of the classifier for the instance is actually the ID of an Association. 
But since ArCon dont have Associations the ID is linked to both 
Association_Ends. The first one found in GetElementByID will be the one we set 
to From_End. Is this always true, or are there situations
were it fails.

Profile definition does not use the notation "profile:class" as a standard. 
"profile" just
happened to be the name of the profile. Found when using a profile named
Arch_Rules_Profile.

What is MC in the Element class of Arcon's Meta_Models?

MC is never used in ArCon and as such it is set to be of no importance. The 
question about what MC really stands for remains unanswered.

Association , with ownedEnd. Meaning End that is not owned by the classifier. 
How should it be handled in ArCon?

Currently creating a Association_End for each that is owned by the package 
containing the Association.

Defining a generic attribute type '@' in arch rules does not work in Papyrus. 
Need to define a standard and translate it. Use <undefined>?

Set Standard: Letting the attribute have <undefined> type equals defining type 
'@' in Rhapsody.

Add more documentation in the Arcon model (currently most is just in VS2010 
project)

Qualifier

(seems to not be supported by Papyrus yet)

Handle different operation method languages. What if several languages are 
defined, which behavior to use?

Visibility on operation parameter seem to not matter. Should it? (Rule T13)

Not important

setItsType(Association_End*) in Links. Seem to refer to a Association_End to 
represent the Association. Does it, or what should this type be set to?

Implementation code can not be defined, and therefore no ArCon rules can be 
applied,i.e. Set() { @ Notify(); }. Implement behavior support for Papyrus

implementation can be defined using the method field for an operation. Then 
using ownedBehavior to define the implementation within the body.

Parameters, defining % as name, with type <undefined> does not allow several 
parameter (getting too many report)

Working now without have done anything in the code. Possibly model was wrong?

Package visibility - Add support in Arcon

Add if time

Set zero an a association end in Papyrus. Seem to automatically reset to one of 
the standards. Is there cases when we want to set zero on a multiplicity? 
Basically, Is the rule "Only explicitly allowed relations are allowed" 
applicable for all Parts?

Or may it be a case when we want to explicitly disallow a connection?

Let the user define the postfix convention (defining the strings, i.e _arch, 
_system)

Added options in preferences page

"Method is defined as the implementation of an operation. It specifies the 
algorithm or procedure associated with an operation." How can we use this to 
support the implementation rules ArCon support for Rhapsody?

This can be used to define the operation's behavior (implementation).

ShowOnlyPublicContent_Constraint / ShowOnlyPublic_Constraint - need to add
something here if we implement package visibility?

Set a stereotype for the model "System_Model" and "Arch_Rules_Model". Check 
that this is set for the model when loading it.

T5 Tagged values rule. Tested in Arcon and it seem to not pickup the meta 
stereotype but just thinking it should match a property like rule T12. Is T5 
really supported in ArCon 1.4?

Set to low priority according to discussion about tagged values below.

What is the different between ownedBehavior and nestedClassifier? when defining 
a method for operation

Clean up messages (debug) from Arcon

Let user define what to use, postfix or prefix

Added option in preferences page

Events/Signals functions (example use in washing machine)

Added options in preferences page

Not all types, are defined in ArCon. For example 'usage'-edge that can be set 
in Papyrus does not have a corresponding meta model in Arcon. Should they be 
translated into another existing class in Arcon so some rules can be checked on 
them.

Missing types have to be implemented before they can be checked. ArCon V3 
should take care of this.

Defining a generic parameter type '@' in arch rules does not work in Papyrus. 
Need to define a standard and translate it. Use <undefined>?

Set Standard: Letting the parameter have <undefined> type equals defining type 
'@' in Rhapsody.

Destructor

Set Standard: Same name as owner Class with ~ at the beginning, and do not have 
a return type.