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

Advertisements

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