Here I study the Class Object state axiom in the perspective of an incorporation in ISA. What’s about the Class life cycle ? And about the Versioning, the Grouping and the Delivery ?
Continue reading The State axiom – Part 4Instance
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 axiomWhat is an object ? This is the question this post answered by establishing an axiomatic: Encapsulation, Interface, Behavior, Identity and State.
This post also reveals what is there behind these axioms and begins to explore their implications.
Have 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.
Think and design ISA to be durable for several decades. The main design patterns should be incorporated as much as possible. This architecture should not limit itself in changes that it can elaborate to have good performances. And this in both dimensions hardware and software. Remain native : It is the condition to do at best of the possible. Define a solid base and then incorporate an extension mechanism.
Continue reading ISA Wish N°6 – Modern, performant and durableOne 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.
The first benefit to incorporate security in the lowest layers of ISA is that its safety is generalized every where ISA is deployed, and at anytime. This is a very important advantage when comparing to security problems recurrently occuring on all runtime environments (operating systems, browsers, etc.)
Continue reading ISA Wish N°3 – Intrinsic securisation