📚    BPM    SDLC    BIAanl    Data    Meta    Math    📚 👐 🎭 index - references    elucidation    metier 🎭
⚒    Intro     Pyramid     VMAP     Perspectives     ALC model     What next     ⚒ 👐    top bottom   👐

Design SDLC - Software Development Life Cycle


deep dive layers, VMAP

ICT at an organization by layers.

Vmap layers choices Dimensions by layers Data Proces layers (Meta) The organization is powered by ICT in a ship like constellation.
The engines (data center) out of sight, below visibility.

Serving nultiple customers (multi tenancy) for best performance and best profits.

🔰 Most logical back reference.

Contents

Reference Topic Squad
Intro ICT at an organization by layers. 01.01
Pyramid The full ICT Business Pyramid. 02.01
VMAP The VMAP model, verification of activities. 03.01
Perspectives Different worlds. Perspectives: Business, ICT. 04.01
ALC model Design of development & operational business lines. 05.01
What next Step by step, Travelling the unexplored. 06.00
Combined pages as single topic. 06.02

Combined links
Combined pages as single topic.
🕶 deep dive Data Proces layers (Meta)
🚧 deep dive layers , VMAP
👓 Multiple Dimensions by layers
👓 ALC type2 Business Apllications - 3GL
👓 ALC type3 Low code Analytics, Business


Progress


The full ICT Business Pyramid.

layers - infrastructure bottom - business top.

The VMAP model, verification of activities.

Doing a new engineering job or maintenance is planning activities. There are dependicies. Those dependicies are best shown as a picture of the V-model.
depencies activities infographic.
The activities are:
  1. Requirements can´s be made without knowing business gaps and/or mistakes
  2. Specifications can´t be made without knowing requirements
  3. High level design can´t be made without knowing specifications
  4. Low level design can´t be made without knowing:
    • specifications
    • high level design
  5. Not able Coding, realizing without knowing:
    • specifications
    • high level design
    • low level design
The Agile aspect is that you don´tt ot know everything of all, but something that fits in the most of what fits in what is expected. PATD top-down
The bottom up is the way back DTAP verifications of what is delivered. Preparations of those verifications are able to execute parallel on the realization.

istqb
ISTQB
The capabilities for software testing is standardized with vision. Certifications and an international organization.
ISTQB has the mission: Defining and maintaining a Body of Knowledge which allows testers to be certified based on best practices, connecting the international software testing community, and encouraging research.
 legal

Different worlds. Perspectives: Business, ICT.


Business Experience Pyramid
The business isn´t really interested in technical stuff. They like to have their own dedicated dashboard, doing their own improvemetn PDCA cycles.
three layers building on the previous production version.
Going to their own ICT service delivery desk to get service for some nice tools by ICT with big promises. What is needed for that, ... out of sight.

Infrastructure perspective Pyramid
Hardcore infrastructure like to have the engines up and running. Some tools ("applications") getting installed and activated for what they assume usefull active.
three layers building on the previous production version.
What is needed for cusotmers, the necessities and wishes by customers (organization - business), ... out of sight.

There is a nasty break-up in the middle. In both perspectives it gets broken.

 legal

Design of development & operational business lines.


Guidelines, compliancy.
There are guidelines to do seperations in activity lines (iso/iec 27002): 12.1.4 Separation of development, testing and operational environments Development, testing, and operational environments should be separated to reduce the risks of unauthorized access or changes to the operational environment. three layers building on the previous production version.

Development line - operational line - promoting lines.
Following those guidelines a generic model can be represented in the following picture: three layers building on the previous production version.
Segregations conforming the guideline:
 horse sense

Step by step, Travelling the unexplored.


promoting & evaluations lines.
Promoting artifacts between development and production goes also in several lines.
  1. Visible green vertical: data preparation. Several options like streamed and archived storage
  2. Visible green vertical: data transforming (ABT)
  3. Visible green vertical: applying logic (proces score)
  4. Fully hidden: Delivering results externally
  5. Not by code: Results evaluation, proces decision underpinning.
  6. Partial hidden: Monitoring input data after retrieval
  7. Partial hidden: Monitoring results validation before delivery
The datatransformation and applying logic could be repeated multiple times. Adding two additions steps in the flow. All this is also existing in the traditional software development and deployment. Maybe used words and the technical approach is a little bit different.

Unexplored joureney Enterprise
Visiting all layers (dimensions).
Making a journey to all layers and all stages is exploring where no one has gone before.
The people at the hardcore ICT infrastructure are a different kind of species than the ones servicing the business. Understanding the business and those people is another world.

Combined pages as single topic.
Combined links
🕶 deep dive , Data Proces layers (Meta)
deep dive layers , VMAP
👓 Multiple Dimensions by layers
👓 ALC type2 Business Apllications - 3GL
👓 ALC type3 Low code Analytics, Business


🔰 Most logical back reference.



⚒    Intro     Pyramid     VMAP     Perspectives     ALC model     What next     ⚒ 👐    top bottom   👐
📚    BPM    SDLC    BIAanl    Data    Meta    Math    📚 👐 🎭 index - references    elucidation    metier 🎭

© 2012,2019 J.A.Karman