Re: Aspect Oriented Programming
- From: "Chris Mullins [MVP - C#]" <cmullins@xxxxxxxxx>
- Date: Tue, 15 Jan 2008 09:59:15 -0800
I'm not so sure about that. Although I could be completly be out left field
here, I freely admit...
I think the biggest problem is that few (including me) really know with AOP
is. I have some ideas, I've read some articles and surfed the web a bit, but
a deep computer-science level of understanding? Hrm. Not really.
Certainly, there's not deep support for AOP throughout Visual Studio, but
there are lots of things that seem to fit the bill.
I do alot of work on Frameworks and Infrastructure, and frequently use
Aspects. For me, this is generally done with Metadata (aka: Custom
Attributes) and some static helper classes. The .Net Framework also seems to
have some support for at least commno Aspects.
In much of our code, classes and methods are decorated with aspects like:
[Traceable(TraceLevel=Verbost)], or
[PacketHandler(RequiredAuth = SASL)] or
Many of the App Blocks coming out of the Patters & Practices group fall
under the general (at least to me) category of Aspects.
With the ability now to write Context Bound objects, and the use of custom
attributes, there is quite a bit of AOP that can be done, although I tend
not to see too many people doing it...
--
Chris Mullins
"David Anton" <DavidAnton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C784D614-8650-4618-AC1F-D2D2021116C2@xxxxxxxxxxxxxxxx
I remember reading about AOP in the late 90's, thinking that it would be
interesting to play with it when it was widely available. However, my
chosen
development environment is Visual Studio (for various reasons), and AOP
has
simply not made its way there yet - AOP isn't compelling enough for me to
switch development environments.
--
http://www.tangiblesoftwaresolutions.com
C++ to C#
C++ to VB
C++ to Java
Instant C#: VB to C#
Instant VB: C# to VB
Instant C++ VB Edition: VB to C++/CLI
Instant C++ C# Edition: C# to C++/CLI
"ar3492@xxxxxxxxxxxxxxxxxx" wrote:
Hello, I'm a post-graduate student at the Open University in the
United Kingdom. I'm carrying out research into Aspect Oriented
Programming (AOP) to investigate the reasons why it has not been more
widely adopted by commercial software developers and would be grateful
if you could help by taking a couple of minutes to complete the
questionnaire below. I would very much appreciate a response, even if
you have not previously used AOP.
Thanks a lot for your help,
Andrew Rowe
INTRODUCTION
This survey is being conducted for the Open University in order to
investigate the barriers to the adoption of aspect oriented
programming (AOP) in commercial software development. AOP has been
created to solve the problem of crosscutting concerns in software
development and whilst used in academic research, has yet to make an
impact in commerce. The results of this research will be used to
evaluate AOP and in deciding the direction of future developments.
Please return your completed questionnaire to
ar3492@xxxxxxxxxxxxxxxxxx
SECTION 1 - PARTICIPANT INFORMATION
In this section, please type the letter of the option which most
closely matches your own.
1. Current employment position:
a. Academic
b. Software developer/programmer
c. Tead lead/manager
d. Other (please specify)
Your answer:
2. Have you previously heard of aspect oriented programming (AOP)?
a. Yes
b. No
Your answer:
If you answered Yes to Question 2, please continue to question 3.
If you answered No to Question 2, your questionnaire ends here -
thanks for your time!
3. How many years of practical experience in AOP do you have? __
a. None or < 1 year
b. 1-2
c. 2-4
d. > 4
Your answer:
SECTION 2 - BARRIERS TO THE ADOPTION OF ASPECT ORIENTED PROGRAMMING
1. Strongly agree
2. Agree
3. Neither agree or disagree
4. Disagree
5. Strongly disagree
Using the scale of 1-5 shown above, please select the extent to which
you believe the following are barriers to the adoption of aspect
oriented programming:
1. AOP is an immature technology.
Your answer:
2. Not many interesting aspects outside of logging or tracing.
Your answer:
3. Not many meaningful examples to demonstrate the advantages of AOP.
Your answer:
4. AOP is not an improvement over object oriented programming.
Your answer:
5. Aspect oriented programs are very complicated.
Your answer:
6. Aspect oriented programs are difficult to test.
Your answer:
7. Aspect oriented programs are difficult to maintain.
Your answer:
8. Aspect oriented programs are difficult to debug.
Your answer:
9. Aspect oriented programs perform slowly.
Your answer:
10. The syntax of aspect oriented programs (e.g. join points) is
difficult to understand.
Your answer:
11. It is difficult to understand the execution pattern of an aspect
oriented application.
Your answer:
12. AOP is not supported in my chosen development language.
Your answer:
13. AOP is not supported in my chosen software development environment/
IDE.
Your answer:
14. AOP tools are immature.
Your answer:
15. AOP has a steep learning curve/is difficult to learn.
Your answer:
16. I do not have enough time to learn AOP.
Your answer:
17. High costs of adopting AOP (training/processes etc)
Your answer:
18. No established AOP software development methodology.
Your answer:
19. Application design is more difficult in AOP than in OO or
procedural development.
Your answer:
20. Please list below any other barriers which have not been
identified above.
Your answer:
Thank you for your time!
Please return your completed questionnaire to
ar3492@xxxxxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: Aspect Oriented Programming
- From: Arne Vajhøj
- Re: Aspect Oriented Programming
- References:
- Aspect Oriented Programming
- From: ar3492
- RE: Aspect Oriented Programming
- From: David Anton
- Aspect Oriented Programming
- Prev by Date: Re: My database class
- Next by Date: Question on classes
- Previous by thread: RE: Aspect Oriented Programming
- Next by thread: Re: Aspect Oriented Programming
- Index(es):
Relevant Pages
|
