Re: Failure associated with crosscuts

Marc (or anyone else),

Just on a side note, while the topic is up! You appear to be doing
research into ways to quantify the impact of crosscutting on modularity.
Have you come across work/papers that attempt to quantify or measure the
impact that the composition of concerns have on software?
I'm really interested in seeing some metrics/tools that do this! Parnas
suggests, in his famous paper, that modularisation has an impact on
efficiency due to the "frequent transfer of control between modules". This
has a negative effect on composition and global reasoning because you have
to understand the modular interactions. Could measuring inter-modular
transfer of control be used as a metric to demonstrate the impact
compositional complexity has on software I wonder? Coming back to the
topic, can too much modularity be a problem and also lead to "software
failure"?

Thanks,
Andrew

> Hi Charles,
>
>
>
>                 Many researchers are looking at how crosscutting affects
> software quality.  Alessandro Garcia and his colleagues have done
> excellent
> work in analyzing how crosscutting affects modularity properties such as
> CBO, LCOM, etc.:
>
>
>
> U. Kulesza, C. Sant'Anna, A. Garcia, R. Coelho, A. V. Staa, and C. Lucena,
> "Quantifying the Effects of Aspect-Oriented Programming: A Maintenance
> Study," Intl. Conf. on Software Maintenance (ICMS 2006), 2006.
>
>
>
>                 Marc Bartsch and Rachel Harrison tried correlating
> aspect-based metrics with development effort:
>
>
>
> Marc Bartsch and Rachel Harrison, "Towards an Empirical Validation of
> Aspect-Oriented Coupling Metrics," Workshop on the Assessment of
> Aspect-Oriented Technologies (ASAT) 2007 in Conjunction with AOSD 2007,
> Vancouver, Canada.
>
> http://aosd.net/workshops/asat/2007/papers/Towards%20an%20Empirical%20Valida
> tion%20of%20Aspect-Oriented%20Coupling%20Metrics.pdf
>
>
>
>                 There are dozens of papers on aspect-based and
> concern-based
> metrics.  Our group recently put out a paper arguing that concern-based
> metrics are more informative than traditional metrics (e.g., the CK
> metrics)
> for assessing modularity and change cost:
>
>
>
> M. Eaddy, A. Aho, and G. C. Murphy, "Identifying, Assigning, and
> Quantifying
> Crosscutting Concerns," to appear in the ICSE Workshop on Assessment of
> Contemporary Modularization Techniques (ACoM 2007), Minneapolis, MN, May
> 22,
> 2007.
>
> http://www.cs.columbia.edu/~eaddy/publications/Identifying,%20Assigning,%20a
> nd%20Quantifying%20Crosscutting%20Concerns.pdf
>
>
>
>                 There are also dozens of papers on
> identifying/mining/finding the concerns of a program.
>
>
>
>                 I'd be interested in reading your paper, "Identifying
> Transverse Software Failures."  Please send me a link.
>
>
>
> Cheers,
>
>
>
> Marc Eaddy
>
> PhD Student
>
> Columbia University
>
> http://www.columbia.edu/~me133
>
>
>
> From: Donisthorpe C (AT) [mailto:[email protected]]
> Sent: Thursday, March 29, 2007 5:45 AM
> To: [email protected]
> Subject: [aosd-discuss] Failure associated with crosscuts
>
>
>
> Hi all,
>
>
>
> I am investigating the idea of software failure linked to the effects of
> crosscuts.
>
> As an architecture concern how do early aspects-analysis address this
> possibility?
>
> I have already produced a paper "Identifying Transverse Software Failures"
> that identifies the issue of crosscutting failure influences:
>
>
>
> DONISTHORPE, C. R., 2007. Identifying Transverse Software Failures. In:
> P.
> PLASSMAN, R. WILTSHIRE, et al. eds.  1st Research Student Workshop. 1 ed.
> Glamorgan Business Centre, University of Glamorgan, Wales, United Kingdom:
> The Research Office, University of Glamorgan, Faculty of Advanced
> Technology, Pontypridd Mid Glamorgan, CF37 1DL
>
> ISBN 978-1-84054-156-4
>
>
>
> Can anyone suggest some useful text on this subject as I want to develop
> this theme further?
>
>
>
>
>
> Regards
>
>
>
> Charles
>
>
>
> Tel: 07899 844460
>
> _______________________________________________
> discuss mailing list    -    [email protected]
>
> To unsubscribe and change options, go to:
> http://aosd.net/mailman/listinfo/discuss_aosd.net
>
> Check out the AOSD.net Wiki: http://aosd.net/wiki
>



_______________________________________________
discuss mailing list    -    [email protected]

To unsubscribe and change options, go to:
http://aosd.net/mailman/listinfo/discuss_aosd.net

Check out the AOSD.net Wiki: http://aosd.net/wiki