This is how you develop high-quality software quick as a flash

When talking about contemporary practices in the area of software developments, there is no getting around the terms Continuous Integration, Continuous Delivery and Continuous Deployment. Core of these methods is the automatization of manual processing steps which leads to a reliable, error-free delivery of new releases and an increase in efficiency within the entire area of software developments.

Last but not least, agility relies on these continuous practices to enable a short time-to-market and therefore the ability to react immediately to demands.

Continuous Integration (CI)

Automatization process for developers: code changes are verified automatically

Continuous Delivery (CD)

Supplements CI by automated, quality-proven provision of production-ready software packages for the integration environment

Continuous Deployment (CD)

Supplements the automated provision in the integration environment by an automated installation of the software packages in the production environment

Automated test guarantee quality

The quality of software is mainly determined by tests, conducted even in case of the tiniest change. Manual tests take up time and are usually not very transparent for employees and customers. A clearly defined, automated procedure however will guarantee quality.

Demands are increasing everywhere and software developers in particular have to provide high-quality software in increasingly shorter intervals. Even though an extreme rhythm like Amazon’s - where updates go live every 20 seconds- only affects a few companies so far: in general, acceleration is a reality for every company, that is located within the fast moving digitalization environment. The answer to this requirement is Continuous Integration, Continuous Delivery and Continuous Deployment. On developer level it has been common practice for a long time to have changes tested automatically (Unit tests). For the remaining software cycle, a change to continuous practices will mean considerable additional effort, since automated tests (integration- and E2E-tests) in the deployment- and production department have to be designed and written first.

Code-Review – each code is verified twice

A further aspect of quality assurance is provided by the four-eyes principle. In order to not just guarantee the function- and operability, but to also keep an eye on the whole picture, it is possible that each code must be reviewed and released by one or more developers.

Frequent team meetings foster transparency amongst all participants, so that relevant information is available for everyone at any time.

A new culture of cooperation is needed

Breathing life into Continuous requires the cooperation of all participants. Here DevOps is gaining ground as an adequate mindset. DevOps is equivalent for developing speed, provision and quality, with an impact far beyond all technical aspects of Continuous practices. DevOps changes mindsets, developing processes are seen holistically and bridges between developing- and operational teams are built.

This creates a communicative, cooperate culture of collaboration featuring values such as end-to-end responsibility, continuous improvements, transparency as well as a constructive error-culture.
We have been applying these developing methods following the principles of the DevOps culture for years and have proven our expertise throughout numerous projects while gathering Best Practice experiences along the way.

The components of the projects are mostly

  • The process definition and creation of a target image
  • Agile procedure, for ad-hoc reaction in case of changes
  • Agile mindset
  • Customer support for the selection of tools
  • Product Owner coaching, provided by the customer

Utilization of Continuous practices

  • accelerated development cycles
  • risk minimization: minimized error rate
  • increase in quality
  • shortened time-to-market of new features
  • tools support and enforce defined processes
  • increased acceptance within special departments
  • long-term cost reduction

A chain of numbers

Ein Beispiel aus unserem Entwicklungsbereich, das aufzeigt wie produktivitätssteigernd Continuous Integration sein kann: 20 Entwickler lassen während eines Monats 2.600 Builds erstellen, 1One example from our developing department, that shows how productivity-enhancing Continuous Integration can be: 20 developers create 2.600 builds during one month, are executing 1.000 automatized installations in the test system and are running 4,5 million automated tests. And while this is done purely automatized, all participants are productively developing new features.

This efficient software development process shortens the time required to implement the desired software or features - from the idea to the deliverable version - enormously.

How we support you

SALT Solutions is your partner to support the introduction of continuous development methods, in regards to prerequisites and requirements, support in the selection of tools, definition of processes, the use of agile methods and, more generally, in the implementation of projects in order to efficiently achieve corporate goals.

We take care of your journey to digitization.

Schedule an appointment
Your contact
Jörg Schübel
Jörg Schübel
Fon: +49 89 589772 7370