👐    metier   👐    design: bpm    sdlc    bianl    sense    data    meta    math    👐    devops: bpm    sdlc    bianl    sense    data    meta    math 👐
👐    Refer    👐    top bottom   👐

Design - Math technical details


Data representation, presentation, performance &tuning

Technical realisations

Technical building This mindmap has two timelines from left to right, at the top concepts ideas and at the bottom the practice of that.
At every moment it possible to cross to another topic a they have all relationships.
The most logical croos over is in a Z approach. When arrived here, looping back in reverse Z when time has not come to an end.


Math in ICT

Slider There are most basic issues in ICT with math. One of those is the inaccuracy with calculations.
Using a slider you had to think about that and by that knowing the possible impact. Using a computer everybody trust the results until the surprising wrong results getting complaints by feed back respsonses.

🔰 Too fast .. previous.

Data Exchange

cloud link There are many ways to exchange data between processes. A clear decoupling plan is helpful with creating normalized systems. Normalized systems have the intention in an easy transition by some "application" in another.

Some well known ways to exchange data are:

Unicode character representation

unicode All data has to be represented in a technical realisation. There are many solutions needing transcoding when going from one to another system using different ones.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
.

Standards IEC/ISO, Enisa, NIST

under constrcution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
.

Performance & Tuning

under constrcution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
.

The yellow brick road

Data monetizing journey
Monetizing Data: Follow the Yellow Brick Road
While the tools have vastly improved, and the power of BI buttressed by AI and Machine Learning has helped greatly with incorporating challenges like unstructured and disparate data (internal and external), that Yellow Brick Road journey still requires cultural and operational steps including empowerment of associated teams. There is not a lot of room for autocracy in achieving the best results. Foundational elements work best, and collaboration is a must.

Following steps

Missing link

These are high level considerations.

Switching context to more practice (devops) 👓 Process Management.

What is not here: 👓 math in practice.



👐    Links    👐    top bottom   👐
👐    metier   👐    design: bpm    sdlc    bianl    sense    data    meta    math    👐    devops: bpm    sdlc    bianl    sense    data    meta    math 👐

© 2012,2019 J.A.Karman