⚙    bpm    sdlc    bianl    data    meta    math    ⚙ 👐 🎭 index - references    elucidation    metier 🎭
⚒    Intro     it2it     versioning     SAS-mdl2     SAS-mdl3     What more     ⚒ 👐    top bottom   👐

Devops SDLC - Software Development Life Cycle


Practical cases "versions": testing, releases (versions), deployment

Implementing business Logic, personal experiences.

vmap sdlc Realization is being in some lost environment without much help arround.
Clockwise or counterclockwise there is no direct way to do both at the same time.

Even with clear described to achieve goals the dependicies on others can make it hard.

🔰 Too fast .. previous.

Contents

Reference Topic Squad
Intro Implementing business Logic, personal experiences. 01.01
it2it Automatization of automation engineers. 02.01
👓 JST JST, my own made tool in the 1990´s 02.xx
versioning Versioning tools versus business requirements. 03.01
SAS-mdl2 SAS Proces model-2, ALC 04.01
SAS-mdl3 SAS Proces model-3, ALC 05.01
What more & More 06.01

Progress


 legal

Automatization of automation engineers.

Automatization is common usage doing for business lines. It can be done on ICT. New words getting used is for example IT4IT although the thoughts of that are similar to the old AIM.

JST

JST, my own made tool

The tool JST had the mission of automatization testing verifying validation of software (end 80´s) . It was extended to developpers and acceptance (middle 90´s). (JST 👓 click figure)

Aside the testing also covering the technical routines. There is no technical difference to those. Only the processed information is different.

When covering all of the DTAP, Development, Test, Acceptance, Production, combined with release management.

Special Acceptance environment notes
Accptance testing is usually interpreted as getting users involved. Working on JST, I got a notification that the subject of testing is important.
Within A stage the business data can be different to it´s usage goal, as there are:
Intra #smta
The concept of JST is based on modelling the information used by processing jobs for testing or other activities.
detailed descriptive information at ..
Details (opens new page), to be found at:
👓 VMAP, ISTQB Test management, part of ALC
👓 ALC type2 Application Life Cycle - model2
👓 AIM model Amsterdam Information Management
👓 - Logical Security segregation
👓 Structured Programming
👓 - Performance & tuning


 feel lost

Versioning tools versus business requirements.

💣 Words are often not covering the intentions and meanin in the requires context. One of the abused ones is "versions".

Guidelines eg iec/iso 27002
istqb
12.5.1 Installation of software on operational systems istqb
istqb
Those guidelines, mentioned in regulations, are clear. The intention is to know which software version was used on a moment in time in the ⚠ production ❗ environment.

nvie git lines
Git Generic usage
Nvie is often referred as a scucefull approach using git. The picture at the right is Git nvie.

It shows branching lines features (develop), develop (integration), Release barcnches (acceptance), hotfixes , master (P).
It isn´t showing the release management and archiving.

It doesn´t solve anyting on the requirement for versioning for production environments. It doesn´t solve a complete previous version CMDB information.
The focus: developing software (3gl).

classic modelv2 lines
The classic approach is having clear stages for relases with their versions and archiving.
The development lines are the same.

The software library is the central location having all possible future, current, and previous versions of production software.

 legal

SAS Usage ALC model-2

In the basic approach, analysts are needing data, the code they build should run predictable repeatable.
The support is for interactive and operational batch similar, solving the same issues. Accpetable runtime performance is important considering choices.

The following questions solved and implemented:

Intra #smta
Supporting any tool (middleware application) should follow the generic goals and generic legal requirements.
Configuration for the business processing a part of ICT service being very dedicated to business lines.
detailed descriptive information at ..
Details (opens new page), to be found at:
👓 VMAP, ISTQB Test management, part of ALC
👓 ALC type2 Application Life Cycle - model2 (linked model3)
👓 AIM model Amsterdam Information Management
👓 - Logical Security segregation
👓 Structured Programming
👓 - Performance & tuning


 legal

SAS Usage ALC model-3

What is done for mdl2 being extended to what the Application Life Cycle, Analytics Life Cycle, is needing.
The support is for interactive and operational batch similar, solving the same issues.

The following questions solved and implemented:

rls_sascntr_a.jpg
Big variation SAS artifacts
The variaton in artifacts is surprising big, every type being used to manage in release management. Every artifact type having his own technical solution to implement in achieving release management.

A list (limited) of artifacts:
Artifact description source location config runnable
base code Embedded Eguide export OS: <name>.sas
base code -na- -na- OS: <name>.sas
macro function -na- macro-search OS: <name>.sas
formats OS: <name>.sas format-search OS: <name>.sas7bcat
compiled function OS: <name>.sas fcmp-search OS: <name>.sas7bitm
SCL SAS catalog compile scl OS: <name>.sas7bcat
user-calendar OS: <name>.sas calendar-set OS: <name>.sas7bdat
Data Integration Metadata compile generate OS: <name>.sas7bdat
Data Integration Metadata export-import Metadata
Miner project OS:directories -na- Metadata
Miner metaobject Metadata -na- OS: <name>.sas
LSF jobs (repo) Metadata job deploy OS: <name>.sas
LSF jobs (flows) Metadata export-import Metadata
LSF jobs (flows) Metadata -lsf Manual modify- LSF repository
... ... ... ...

& More

dual feeling
Lost with releases - life Cycles
💣 Words are often not covering the intentions and meaning in the given context. One of the abused ones is "versions".

💣 release management with SAS artifacts is confusing when not knowing how every artifact is behaving. Problematic is that every approach is happening.
Code can be interpreter like, that is there is no source location as the runnable code is the source code.
Code can be generated from a database metadata (5-gl), that implies there is a source database, not source code. Only export/import to containererd objects to promote is doable.

MAchine learning git 💣 Assuming you can put a data mining project into git for versioning, will cause big issues.
A data mining project using real easily grows above many Gb's. Have seen them using 60Gb and more.
The sizing limit with version-tools like git is based on 3-gl languages. Detecting differences is based on a 3-gl, manual source getting compiled, assumption.
Bitbucket from Atlassian repository limit (total of all historical versions) of 1 Gb.

logo git
Release management Git connection
benevolent-dictator.png The git reference. Used with os shell (xcmd) commands.

Using any releasement tool is always requiring an ulitmate approver, git name: "dictator".

sdlc_gitwrk_01.png Git uses a local repository that copies locally all files in an os-directory structure. These are the daily working actvities. A central repository to be connected. All artifacts are verified on incremental changes, blocking when something is out of order.

CA Endevor SCM an example of a complete service doing release management. ca endevor git

Following steps

Missing link

These are practical experiences.

Business Intelligence & Analytics 👓 as next topic to help with bpm and using SDLC (software development life cycle).

What is not there are: 👓 the SDLC concepts & requirements.



⚒    Intro     it2it     versioning     SAS-mdl2     SAS-mdl3     What more     ⚒ 👐    top bottom   👐
⚙    bpm    sdlc    bianl    data    meta    math    ⚙ 👐 🎭 index - references    elucidation    metier 🎭

© 2012,2019 J.A.Karman