In 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 2Requirement
What are the requirements ISA should implements.
This 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.
In 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.
Doing nothing is always the best option when acceptable. So optionally if an existing technology is a good candidate to be an ISA part and that it meets all the requirements above, then it should be retained.
This post is also the opportunity to initiate the building process of ISA.
ISA should offer a basic common management for specification, design, test, delivery and the like.
The purpose of ISA is to provide a common set of blocks on which any people involved in software can rely at anytime and anywhere.
Another aspect ISA should address is the continuity in the problem/solution chain thru specification/realisation and the abstraction levels.
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.