[Better Comments Initiative]: FAMIXBehaviouralEntity

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Better Comments Initiative]: FAMIXBehaviouralEntity

Usman Bhatti
FAMIXBehaviouralEntity is an abstract superclass for any kind of behavior. For example, functions and methods. It has a name because it is a named entity but it also has a signature in the format: methodName(paramType1, paramType2). The signature property is necessary for a behavioral entity. An external parser should provide a few metrics that cannot be derived from the model such as cyclomatic complexity, numberOfStatements and numberOfConditionals. Other metrics can be computed from the model if enough information is provided such as numberOfLinesOfCode (from source anchor) and numberOfComments (from FAMIXComment).

It provides properties to manage:
(i)  parameters
(ii) local variables
(iii) accesses to variables, and
(iv) invocations to and from other behavioural entities.

Optionally, it can also specify a declaredType (e.g. return types for functions). This is useful for modeling behaviours from statically typed languages.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Better Comments Initiative]: FAMIXBehaviouralEntity

abergel
I like your effort guys on commenting

Alexandre


On 24 Nov 2011, at 18:08, Usman Bhatti wrote:

> FAMIXBehaviouralEntity is an abstract superclass for any kind of behavior. For example, functions and methods. It has a name because it is a named entity but it also has a signature in the format: methodName(paramType1, paramType2). The signature property is necessary for a behavioral entity. An external parser should provide a few metrics that cannot be derived from the model such as cyclomatic complexity, numberOfStatements and numberOfConditionals. Other metrics can be computed from the model if enough information is provided such as numberOfLinesOfCode (from source anchor) and numberOfComments (from FAMIXComment).
>
> It provides properties to manage:
> (i)  parameters
> (ii) local variables
> (iii) accesses to variables, and
> (iv) invocations to and from other behavioural entities.
>
> Optionally, it can also specify a declaredType (e.g. return types for functions). This is useful for modeling behaviours from statically typed languages.
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Better Comments Initiative]: FAMIXBehaviouralEntity

Tudor Girba-2
Thanks. It looks good.

Doru


On 25 Nov 2011, at 02:32, Alexandre Bergel wrote:

> I like your effort guys on commenting
>
> Alexandre
>
>
> On 24 Nov 2011, at 18:08, Usman Bhatti wrote:
>
>> FAMIXBehaviouralEntity is an abstract superclass for any kind of behavior. For example, functions and methods. It has a name because it is a named entity but it also has a signature in the format: methodName(paramType1, paramType2). The signature property is necessary for a behavioral entity. An external parser should provide a few metrics that cannot be derived from the model such as cyclomatic complexity, numberOfStatements and numberOfConditionals. Other metrics can be computed from the model if enough information is provided such as numberOfLinesOfCode (from source anchor) and numberOfComments (from FAMIXComment).
>>
>> It provides properties to manage:
>> (i)  parameters
>> (ii) local variables
>> (iii) accesses to variables, and
>> (iv) invocations to and from other behavioural entities.
>>
>> Optionally, it can also specify a declaredType (e.g. return types for functions). This is useful for modeling behaviours from statically typed languages.
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev