📚    BPM    SDLC    BIAanl    Data    Meta    Math    📚 👐 🎭 index - references    elucidation    metier 🎭
⚒    Intro     ICT env     new or maintain     layer stages     access segregate     What next    ⚒ 👐    top bottom   👐

Design SDLC - Software Development Life Cycle


Multiple dimensions layers *stages

Release management, versions.

Vmap layers choices ALC type2 Data Administration Building up an organisztizion is growing. Transporting something being improved by tools you are using. Varying from small to big.

Research at small scale still required on what you do at big scale.

🔰 Most logical back reference.

Contents

Reference Topic Squad
Intro Release management, versions. 01.01
ICT env Setting of an ICT environment. 02.01
new or maintain New business application or maintaining one. 03.01
layer stages Details multiple layers 04.01
access segregate Adding who has accessrights, segregation by stages 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 layers , VMAP
🚧 Multiple Dimensions by layers
👓 ALC type2 Business Apllications - 3GL
👓 ALC type3 Low code Analytics, Business


Progress Conversion


PDCS cycle sdcl releases.

Setting of an ICT environment.


An ICT environment is having several lines, development & operational.
The development line (top ltr) is using development tools. Those tools and the used infrastructure (machines, os) should be tested and verified with "user acceptance". The user acceptance is done by development staf, as they are the users of development tools & infrastructure.

The operational line (bottom ltr) should have easlily adopted the deliveries of development. The is requiring the same tools. Most of the development at the operational is minimized or even eliminated when copying developmetn line artifacts is possible. The compelete figure is:
three layers building on the previous production version.
A good collaboration between server (operations) and sas mining (development) is a prerequisite to achieve the wanted situation of easy, simple, quick, reliable trustworhty deployments (agile).

Using existing infrastructure has the requirement: verification that it is sufficiënt for what is going to get build.
It can save a lot of time and hard word. The disadvantage being felt is sharing infrastructure. The containerization is proving it is not a disadvantage but an advantage when done correctly. That is at the business customer delivery line.

 feel lost

New business application or maintaining one.

Delivering releases over all layers has two possible starting points. The difference: creating a new application or changing an existing.

ICT new project - rZ
Needing a own new infrastructure starts at building up that. (top green)
Having infrastructure, building the business application can start (blue diagonal).
After the first delivery the improvement (orange bottom) proces can start.
three layers building on the previous production version.

ICT maintenance project - revZ
At an existing situation several starting points are possible: three layers building on the previous production version.
 feel lost

Details multiple layers

Every layer has his own release managment. Servicing the delivery (prodcution version) is by acceptance that release of the receiving party.

Infrastructure, business, analytics (improvements)
  1. Infrastructure delivering production (P) versions to business development line.
  2. Business development line delivering (P) as business logic and data.
  3. Business (P) data being used as source determining improvements.
three layers building on the previous production version.

Infrastructure hardcore, infrastructure middleware ,business, analytics
The business line is not interested in datacenter services but in the delivery of tools middleware. Modelling of release components is changing because of that.
  1. Hardcore infra delivering production (P) versions to tools - middleware.
  2. Tools - middleware line delivering (P) to business line.
  3. ..(as before).. Totals: four layers instead of three
three layers building on the previous production version.

 feel lost

Adding who has accessrights, segregation by stages


Difference life cycle business artifacts.
Note difference in promotions within business:
❗ At the analytics line: copying business data.
Goal: to explore analyse and derive new insights, define new logic.
❗ At the application line: promoting copying logic.
Blocking, isolating the business data from getting copied.

The reason is for example sensitivity bye Personal Indentificable Information or other classified artifacts not getting distributed outside defined groups.

Access management.
All those artifacts at layers and stages are to be defined on who has access and / or rights for resource - activity.

A technical security access control is becoming visisble.
The network segregation should support segregations in business application domains at the P-stage level.
When the business logic is sensitive the avaiablity to review by developers should be very restrictive. (Silo´s)

Is there a request to explain results of the business process, the versions of production versions should be documented and archived (CMDB).
three layers building on the previous production version.

Step by step, Travelling the unexplored.

 horse sense
Challenge: access management.
Accessmanagement, security, is in scope before going operational. It is better doing a well design before going into building and deliveries. It is a decription properties on information of any type in all layers. I have put securiyt as a metadata subject.

Challenge: releasemanagement Tools, Middleware
The stressed situation in the layers around tools - middleware is propagating into release management. The hardcore infrastructure is seen as commodity tat can be outsourced. That is bringing a new issue for tools middelware setting up their services for the business.

Unexplored joureney Enterprise
Visiting all stages (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 layers , VMAP
Multiple Dimensions by layers
👓 ALC type2 Business Apllications - 3GL
👓 ALC type3 Low code Analytics, Business


🔰 Most logical back reference.



⚒    Intro     ICT env     new or maintain     layer stages     access segregate     What next    ⚒ 👐    top bottom   👐
📚    BPM    SDLC    BIAanl    Data    Meta    Math    📚 👐 🎭 index - references    elucidation    metier 🎭

© 2012,2019 J.A.Karman