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

Design Sense - thoughts


What makes sense to mention but doesn´s fall into one of the main categories

Thinktank, brainstorm

sense or not. Living ICT, can:
  - strictly controlled (I)
  - luxurieus settled friendly (II)
  - feel abandoned, lonely (III)
  - beautiful, full of uncertainty (IV)

🔰 Too fast .. previous.

Progress


Contents

Reference Topic Squad
Intro Thinktank, brainstorm 01.01
innxstbl Conflict of interests, Innovation X Stable operations 02.01
Issues to solve at Analtics life cycle 02.02
frm-cnt Framing the content (site) 03.01
add-emoi Adding emotions into quadrant 04.01
wall-cnfs Communication: request - delivery 🚧 Expectations 05.01
Communication: request - delivery 🚧 Disruptions 05.02
post_vln Evaluating, What others post 06.01

Content Topics, hierarchy

under constrcution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I will limit myself to what I have got involved. That starts here, top down. While working on those, bottom up.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
.

Framing the content (site)

There is a logical sequential order for the chapters. Thats is "e Following Steps". The detailed sections in each chapters are easily bypassed. Not according physical paper:

First Section of each chapter


Connected topics, design line


What more is to say ......:
More links associated - entry/exit
Is used at:
👓 ..
Details to be found at:
👓 ..

Connected topics, devops line


Used references ......:
detailed descriptive information at ..
Details to be found at:
👓 ..

Last paragraph of each chapter


Enterprise Architecture

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

Enterprise Architecture

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

Alignment in Architecture

Missing link
Enterprise architecture is having al lot of detailed concerns. Some like: IT governance, Compliance, Security, Tools, Proces are generic. Also the Software Devlopment Life Cycle is generic.

Being focusses on a single detailed item is easily giving conflicts with other ones.

The generic security with compliance is having my special attention as being one often bypassed and forgotten.


Following steps

Missing link

These are high level considerations

The data is what is all about 👓 there are concepts for those. One is historical included in BI, the dwh.

What is not there are:👓 real life, personal experiences.



👐    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