Afdrukken

EDITORIAL by Philippe MAGNE, CEO.


The essence of ARCAD Software’s business has always been to educate our customers on software versioning techniques. Without a strong software versioning methodology, it is impossible to establish good control and organization when making application changes.

The concept of a version plays a crucial role in bringing together all the parties involved in a change. A version, by definition, is a vector of communication between the teams involved in the change process, whether they are developers, QA, technical support, or end users. For a software company, this tight communication can even benefit marketing and administration. It ties together marketing and development so marketing delivers the right message, and it helps administration manage costs and control investments.

Lees meer...

Afdrukken

"DEVELOPMENT VERSIONING VS PRODUCTION VERSIONING" By Philippe MAGNE, CEO

There are really two different ways of looking at versioning. It depends on your point of view. Are you concerned with development, or are you concerned with updating production? Depending on what phase you are involved in, a version can have a very different use and meaning.

At the development stage, the purpose of versioning is to coordinate teams and projects. It is very common for day-to-day maintenance to collide with long-term projects that are in progress. It is not uncommon that the same components must be changed simultaneously but for different reasons. Duplication is inevitable, and source management becomes essential, especially with functions that help with the merge. You see, the main objective here is to ensure non-regression of the source code in parallel maintenance situations.

At the production stage, the logic is different. The purpose of versioning at this level is to secure and automate changes to an application and transfers to production to the greatest extent possible.

Lees meer...

Afdrukken

THE VALUE OF AN OPEN “CMDB” REPOSITORY FOR ALL LEVELS OF SOFTWARE CONFIGURATION MANAGEMENT By Michel MOUCHON, Technical Director

Source code managers such as CVS or Subversion are based on a source code repository with two major goals:

  • Ensure management of development conflicts when working in teams
  • Ensure traceability of changes over time.


They allow you to group application changes in batches and to provide the appropriate source code to other tools such as "build" or continuous integration software.

The ARCAD repository is a repository of metadata with its own comprehensive overview of the information system.

Lees meer...

Afdrukken

HOW TO INTERFACE SVN DEVELOPMENT VERSIONING WITH ARCAD TOOLS AND WHY THIS DOES NOT AFFECT THE ENTIRE INTEGRATED APPROACH By Marc DALLAS, R&D Director
 

ARCAD has placed the automation of software development at the heart of its strategy, and this orientation is reflected in providing a collaborative work platform that ensures better management of costs, higher quality, and better productivity.

The success of such a strategy requires, among other things, increasing our capacity for integration. To make a commitment to control costs, without providing the necessary functions to safeguard the existing investments (selected solutions, existing procedures, skill levels ...) is not advisable.

In the open systems world, it is clear that application lifecycle management (ALM) is often reduced to simply managing versions of source code (SCM). Market analysis tends to show that support for this basic (but very necessary) function relies mainly on the Subversion (SVN) solution. This is the standard of the Open Source world and is perfectly suited to this problem.

Taking into account of the use of SVN in our solution represents our commitment to integration and the synergies that then arise.

Lees meer...

Afdrukken

NEW TIPS AND TRICKS FOR USING ARCAD PRODUCTS By Eric LOMBREZ, Technical Support Manager
 

Did you know about the LGLTOPHY parameter of the CHKOBJOUT command?
When you work on files, including logicals, if you do not declare a database library in the development environment, the logicals will be linked to the physical files of the reference environment. This may cause problems when working in the version. This parameter allows you to automatically save the underlying physical in the version library and avoid these issues. Give it a try!

Lees meer...