S.O.S. RUBY : It seems that RUBY today can resolve all my Geek problems ^^


for Rapid Prototyping, Cross-platform libraries and Rich Mature ecosystem , I have to go back to RUBY programming Language (with my mixed philosophy of Scala, Java, PHP, LISP and ADA in mind ^^)

Ruby Conf 12 – Ruby Vs. The World


DA VINCI WAY : The View 5 Show – Introduction

DA VINCI WAY : The View 5 Show

“Simplicity is the ultimate of sophistication” Leornado Da Vinci

“The View 5 show”, first part of my future book “DA VINCI WAY”,  is a new simplified system description framework on which I am working, a concept tool study for helping describing rapidly with five simple views, any technologies, any applications or any mechatronic or robotic systems.

These 5 views will be modelized by 5 kind of diagrams with simplified (not-fully-detailed) structure , fields and relationships. It will look like a Quick start visual manual for helping noobs understanding rapidly a complex system to study it quick in practice with a clear perception of all his main features, structures, data, logics and user interfaces.

Here comes the V5 ! *

1 – For Features/requirements view : Simplified and Agile Use case diagrams

2- For architecture view : Simplified and Agile Block diagrams

3- For Data structure view : Simplified and Agile Data entities diagrams

4 – For Logic processes view : Simplified and Agile Flowchart diagrams

5- For User Interface view : Simplified and Agile Wireframe diagrams

Nota : The 3 last views (data, logic and User Interface) should be assembled into a group called “Methods” or “Design Patterns views” because of the strong interaction between these 3 views, interacton which is corresponding to a kind of convention from the authors of the system described.

Most important thing, The 5 views will help us describing the 3 most important properties to keep in mind from the system :

1 – Features
2 – Architectures
3 – Methods for execution of his tasks ( or design patterns or Model processes)

DA VINCI WAY - The Views 5 : 3 properties of the system


EASY-TO-UNDERSTAND : Rapid and Agile understanding of a system described by only 5 simplified diagrams .


– Too much diagrams and complex details needed today to describe a system but doesn’t help for rapid, easy and clear understanding of a system.

– Diagrams are complex to write and to understand, for both end users and diagram developers.

– Too much people don’t use diagrams in their work and they don’t want to use it in their future work because it takes too much time and resources to develop and too much time and resources to understand.


Easy-to-read and Easy-to-understand narration.

Always add very little helper notations on side zone like title, legends, keywords definitions, list, steps, matrix, external links, etc to help keep in mind the goal and the main/generic/casual features.

Limited diagrams : only 5 simple views to resume the description of a system.

Less details for each diagrams : Simplified structure, fields list and relationships list

Rich media illustrations for Rapid visualization : symbols are replaced by well designed familiar icons, but design have to be minimalist with low and subtle saturation.

Always Simplify Relationships: Relationships are simplified to one line and limited to two titles.

External Deep links for getting more details or more diagrams


Preface : The 7 Rules for Next Technologies


1 – For Features/requirements view : Simplified and Agile Use case diagrams

2- For architecture view : Simplified and Agile Block diagrams

3- For Data structure view : Simplified and Agile Data entities diagrams

4 – For Logic processes view : Simplified and Agile Flowchart diagrams

5- For User Interface view : Simplified and Agile Wireframe diagrams

Conclusion : Technology means Conventions and Design Patterns

– I will explain on next step, one by one the definition (Concept and rules) of each of these diagrams , by following this infrastructure

– Standard definition (Concept and Rules)

– Fields list

– Relationships list

– Limitations

– External links to know more about the standard sources of these diagrams

DA VINCI WAY : a sketch book project for new systems design

I decided to start a sketch book for new systems design called “Da Vinci Way”, a new approach in technology, a Tresor Map for Imagineers 😉

“Simplicity is the ultimate sophistication.” Leonardo da Vinci

Leonardo di ser Piero da Vinci was an Italian Renaissance polymath: painter, sculptor, architect, musician, scientist, mathematician, engineer, inventor, anatomist, geologist, cartographer, botanist, and writer. His genius, perhaps more than that of any other figure, epitomized the Renaissance humanist ideal. Leonardo has often been described as the archetype of the Renaissance Man, a man of “unquenchable curiosity” and “feverishly inventive imagination”.

First part :

DA VINCI WAY : The View 5 Show – Introduction

Sketch drawing : the best tool for projects development ^^

A KEY CONCEPT THAT WE HAVE ALL FORGOTTEN AT WORK ^^ : Go back and buy Real pencil, Real gum and Real papers for SKETCH (Drawing).

Sketch (drawing), is a rapidly executed freehand drawing that is not usually intended as a finished work, but a preliminary exploration.
it might record or develop an idea for later use or it might be used as a quick way of graphically demonstrating an idea or principle.


sketch drawing

My final Weapon of Choice : Scala Programming Language

Astroneo Reloaded : Stop Graphic Design, Come back to Programming XD

Why choosing Scala ? Read this very interesting approach on all programming languages from Babu Srinivasan’s blog :
“It is a very good idea to learn several programming languages. It makes you a better programmer. But if you want to devote all your energies to becoming a proficient and productive programmer and want to learn one powerful, freely available, high level general-purpose language (not domain specific), what would you choose?”
“Scala is a general purpose programming language designed to express common programming patterns in a concise, elegant, and type-safe way. It smoothly integrates features of object-oriented and functional languages, enabling Java and other programmers to be more productive. ” http://www.scala-lang.org/


ADA-JAVA Interfacing Suite by The Adacore-Team : “I love it when a plans come together !”

Ada-Java Interfacing Suite by The Adacore-Team  :  http://www.adacore.com/gnatpro/toolsuite/ada-java/

AdaCore logo

ADA 2012 programming language or GROOVY scripting language ??? Hard choice – Torture lol

ADA 2012 + Microsoft .NET Framework or GROOVY + Java/Spring Framework ?????????

Groovy and his convention-like frameworks Grails, Griffon  and Java/Spring ecosystem is well suited for my agile approach on future control system projects but ADA 2012 is clearely more robust and simple  and .NET framework can complete the  omissions of ADA ecosystem. Two of them  have interesting features , Hard to choose XD

Groovy : http://groovy.codehaus.org/

ADA 2012 : http://www.adacore.com/adaanswers/about/ada-2012/