| |
| 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.
Read>>
|
| |
| 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.
Let's discover these two complementary visions
Read>>
|
| |
| 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 and |
|
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.
In this article you will see how the ARCAD repository is a repository of metadata with its own comprehensive overview of the information system.
Read>> |
| |
|
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.
Taking into account of the use of SVN in our solution represents our commitment to integration and the synergies that then arise.
Learn more...
Read>>
|
| |
|
NEW TIPS AND TRICKS FOR USING ARCAD PRODUCTS By Eric LOMBREZ, Technical Support Manager |
|
This topic is dedicated to the users of ARCAD products, to give you little tips and tricks to make your life easier in your daily tasks. In this issue, we tell you everything you need to know about the LGLTOPHY parameter of the CHKOBJOUT command.
Read>> |
| |
|
WHERE TO FIND US IN 2009 ... by Mary LANGEN, Marketing
Manager, North America |
|
Because it is always a great pleasure, we hope to meet many of you during the year 2009.
Here is the plan for the first 6 months:
|
4 March: Scandinavian Developer Conference, Sweden |
|
24 - 26 March: Toronto User Group, Canada |
|
30 March: ORACLE Users Day, Paris |
|
1 - 2 April: WMCPA, Delavan, WI (USA) |
|
6 - 8 April: Northeast User Groups Conference, Framingham, MA (USA) |
|
7 April: Seminar on Multi-platform Deployment (components and data) and Help-desk, |
| Luxembourg |
|
26 - 30 April: COMMON, Reno, NV (USA) |
|
14 May: Seminar on ITIL and Technical Support Management, IBM Forum, Tours Descartes, Paris |
|
6 - 9 June: COMMON EUROPE, Krakow, Poland |
|
