Soplets are a radically new way of writing code - but why should you do it that way anyway? Why shouldn't object-oriented programming be good enough anymore for you? The short answer is: You will write better code. The long answer takes, well, a bit longer:
Write clear, simple, standardized code. Writing code the Soplet way is an easy to learn, easy to follow programming pattern. There is not much room for error, even for the less experienced programmer. The code structure is very simple and easy to understand, so much so that even a non-programmer could get an idea of the content, if he wanted to.
On the other side, Soplets are formally structured (as opposed to JavaDoc for instance), there is no way of 'not' following the structure as defined by the annotation @interface class. This makes it easy to put in place and enforce project-wide programming guidelines.
In combination with the Soplet Eclipse Plugin, a large part of the required functionality (such as getter and setter methods) are generated automatically as byte code. Secondary features of Soplets (such as the component binding) reduce and streamline your code even further.
There are many reasons for this high level of cost, and many ways to measure (or at least estimate) the grade of maintainability of the software. One important measurement is the grade of Semantic Convergence, meaning: as more semantically related data is spread inside and outside the code, the more expensive it is to maintain the code.
Soplet is a direct answer to this situation, by propagating the spatial and logical unity of a given concept. This approach makes sure that a value is defined only once and not duplicated across the code or elsewhere, and that semantically related values are close together at a single place.
Soplets are well delimited blocks of code, which are easy to read and understand, even for the non-initiated reader. They describe one-to-one concrete, self-containing concepts. They are self-documenting, as the attributes are implementation and documentation at the same time.
Soplets are strong-typed by design, which makes it easy to navigate them in an IDE environment, as most of the Soplets are linked to each other, or to other parts of the code.
And last but not least, given their formally structured nature, Soplets can be used to generate user and system documentation in the form of PDF, HTML, XML or other formats, be it during compile time or during runtime.
What's wrong with MDA? for more details.