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

THE OBJECTIVE :

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

THE RECCURENT PROBLEM OF MODERN 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.

THE STRATEGY/RULES : THE ICEBERG PERSPECTIVE APPROACH

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

SUMMARY

Preface : The 7 Rules for Next Technologies

Introduction

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

The 7 Rules for Next Technologies : a concise guide to some of the most commonly violated rules in new technologies by companies today.

“Simplicity is the ultimate of sophistication” Leornado Da Vinci

It is intended for all final users of high-tech tools, computers, softwares and devices.
Remember technology is just a science of tools and a tool is just for a task not for spending all your life on it !

The 7 rules for next technologies

The featured contributor is Cheikhna a.k.a astroneo, an imagineer who has studied and worked with several technologies during his long carreer as a project manager, engineer, developer, webmaster and 2D/3D graphic designer. He’s working currently on a new architecture description framework for understanding and using easily any control systems.

Here are Astroneo’s “Seven Rules for next technologies”:

Easy-to-learn, Simple-to-use, Compact, Scalable, Efficient, Reliable and Low-cost.

1- Easy-to-learn, Easy-to-understand : “DUDES, TAKE IT EASY !”

  • A technology which is easy to understand and to learn is the half of the work in using it. but how many times have we met a great tool with awesome features associated with complex non-structured learning curves ? Awesome poor explanations and documentations, no clear diagrams or description views and many manuals and books containing thousand pages of useless comments on details !
  • At the end, you will found that it took you 2 years of learning and practices before you could really appreciate all his power.
    Why not starting with simple tools with quick easy to learn curve including hierarchical structured level steps for the impatients ^^ (basic, advanced, expert)  so we can concentrate only on our tasks and objectives in our project ?
  • 6 months for learning a software tool ??  Remember a computer is just a tool and your life is a shareware, not unlimited !

2- Simple-to-use, Easy-to-use : “KIDS, KEEP IT SIMPLE !”

  • “Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity” Charles Mingus
  • Life is simple, adults make it hard ; Nature is  just a complex combination of simple stuffs so if you have to work on complex projects, you should seriously start by simple things and the first thing to do is to use simple tools that will help you to stay productive in any levels of complexity.

3- Compact : “DAMN, MAKE IT COMPACT !”

  • If i have to describe a complex system to make it easy to understand, I will have to resume it by describing only the surface of the system.But my description will look like an iceberg for noobs when i will decide to describe more deeper in the details and features of the system ;  A short description, a fly on the surface  is the key.
  • It’s the same problem when some companies want to add more stuffs on their products and sell some thousand extensions ; just sell only one tool and name it “THE All-in-One”, “THE Ultimate”, “The Universal prodigious magic awesome kick-ass tool”, your customers will love you for that.
  • A compact tool with main add-on’s included is better than thousand  stuffs  you will have to buy to get things done correctly.
    What we really need is to get the main features of a tool for quick start and use his details/options/extensions/plugins already included when we’ll really need it.

4- Scalable :  “I WANT HIGH OUTRAGEOUS SCALABILITY ! “

  • Flexible means that you have the power to extend his features in the way you need it for your project, task and domain.
    you know life is dynamic, unpredictable and evolutionary so your tool will always have to be adjustable.

5-Efficient : “IT MUST BE EFFICIENT, IT HAVE TO !”

  • Fast and good result that’s the purpose of a tool, That’s all.

6- Reliable and Easy-to-control : “IS IT WORK ? IS IT SURE AND SECURE ? IS IT YOUR PROBLEM ? “

  • Reliable  and robust ? we all know what is the problem with new technologies :
    Why bugs tracks and dreamy wish list on forum support should be the  job of the final users ? ^^

7- Low-Cost not Free or Expensive : ” SOLD OUT ! “

  • A good tool at a low price (not free as a beer if you want something robust) will bring dynamic enthousiast community support and will give better results on time for all than a high perfect product for very important personality or a popular free product efficient for personnal use only !

 

 

– Conclusion : If I have to suggest them a solution I would just always keep in mind 3 keywords , The Easy 3 principle  :

  1. Easy-to-understand for Quick start
  2. Easy-to-use for Rapid Prototyping
  3. Easy-to-control for Monitoring and Debugging
Charles Mingus the Jazzman could be a Genius in Computer Science ^^
“Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity.” C.M.

Related Link :

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

DA VINCI WAY : The View 5 Show – Introduction

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

HELP !
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/

ASTRO-CHOICE : JAVA or ADA 2012 ?

JAVA or ADA 2012 ?

ADA or JAVA ? With JAVA we can find a job ! but with ADA we can change the World ! 😀
ADA 2012 The most Advanced Language for safe and secure Software : http://www.adacore.com/adaanswers/about/ada-2012/

ASTRO-SHADERS for Graphic User Interface

ASTRO-BLUEAt last I have made my own Shaders Library for my GUI projects (Graphic User Interface) and my architecture viewpoints framework 😀

This slideshow requires JavaScript.

Looking for GROOOVVVYYYY

GroovyFor my Teamwork Framework project and Rapid Prototyping Tools project for D.I.Y. Makers ( Do It Yourself) in Robotic and Mechatronic , I am studying a very interesting programming language Groovy and his “Ruby on Rails“-like framework  called Grails . Groovy, the power and rich ressource of java combined with the easy of Ruby, Ruby on Rails, Python and smaltalk.

Groovy is an agile and dynamic language for the Java Virtual Machine. Builds upon the strengths of Java but has additional power features inspired by languages like Python, Ruby and Smalltalk. Makes modern programming features available to Java developers with almost-zero learning curve.

Homepage link : http://groovy.codehaus.org/Groovy logo