ISA relies on the Object Oriented paradigm. Let me now join OO with our wishes. Some guidances emerge . The first one is, not surprisingly, “Everything in ISA is an Object”!
Continue reading Object Oriented GuidelinesRelational
Third post on the object state axiom. Here I will speak about the state of the Class object and begin to define what it is. It is also question of immutability and of threaded objects.
Continue reading The State axiom – Part 3In this second post on Object state, we will see what are Fields, Relationships, Properties and Attributes; and why and how to put them all together.
Continue reading The State axiom – Part 2This post answers the question “What’s a State ?”. It also consider object life cycle and the basic Design Patterns. Finally, Eiffel’s advanced features around state are evoked.
Continue reading The State axiom – Part 1What are the Identity axiom consequences ? Here is a list of studied subject by this post: Addressing, Unitarity, Uniqueness, Ubiquity, Versioning.
Continue reading The Identity axiomIn the perspective to give a basement to ISA, here is an exploration of pros and cons of major paradigms (No paradigm, Object Oriented, Sets (Relational) and Functional). To sum up the OO paradigm is retained for ISA. It is this approach that has made me discover the “Atom Oriented” possible paradigm.
Continue reading Available paradigms overviewHave an underlying paradigm to help building ISA is a mean to promote coherence and consistency.
In this way it is easier to follow all the previously expressed wishes. It also gives guidelines for choosing among solutions in particular on reuse of an existing one.
One of firsts motivation of ISA is to unify the architecture and to make it simple in order to eliminate useless “expertise”.
ISA makes a break with the existent. Thus this architecture is free to make its choices. In other words, compatibility with actual IT is not a concern for ISA. This primary option eliminates the niches for geeks and experts.