Apoptotic Objects

This could be done by having AOP code under certain conditions modify the apoptotic object behaviour such that all method invocations have no effect. Alternatively, some apoptotic objects might be more selective in which of its interfaces become unusable. Modified Behaviour such as this could be very useful in mobile environments where collaborating services are likely to exchange code and data. In such environments, apoptosis might offer a mechanism to protect users' privacy or protect them from malicious actions when a trust between entities is broken. there are lots of other scenarios possible which should become obvious once you read the related literature.

Task

There is a site dedicated to this Wikipedia for Apoptosis. Also, read the Special Issue on Aspect-Oriented Programming in the October 2001 issue of "Communications of the ACM". You should also check out Getting started with AspectJ.

The end-result should be a thesis focussed on apoptotic objects outlining your approach, concept of apoptosis in computer behaviour, results, discussion of system and evaluation. You should basically develop other examples along with concrete scenarios where it might be used all of which demonstrate the applicability of apoptotic computing.

Thanks to an unidentified source at the OU for the idea for this topic.