In a company where software quality is paramount and where products evolve,
complexity increases over time.
One way to get consistent and predictable results is to automate
(in a known and expected way)
additional tasks required of employees in addition to product development.
Abc has been renamed to Abcd since v8.08 to better reflect its role and capabilities.
Abcd covers steps A,B,C,D and prepares step E in the ABCDE process.
Accordingly:
Sample configuration for abc Main Config directory. Designed to demonstrate the most important capabilities of abc. Notes: * Projects inherit this configuration, then select specific parts to use. * Projects need only establish what differs from the Main Configuration. * The order in which variables are evaluated within other variables is important.
One of main goals of Abc is to help developers do fewer context switches
and be able to focus on project logic.
One way is to automate (in a known and expected way) the additional maintenance tasks required by the tools to be performed by the user.
# Product Development Cycle # # This is an adjusted example with ABCDE process # applied with Abc on quite a few products. # ( And it works as intended from years. ) # # It may be useful to preview the capabilities of Abc: # * How much Time is saved. # * How much the Quality increases over time.
# Sample hook scripts PATH should contain this directory. Note: Abc version 5 support changing PATH from Jake or Make. The scripts and this directory are added here for reference, in case you want to quickly build for the first time the sample projects. These scripts: - Can be used in Abc configuration files.
Customize Abc main config directory for your coding style and your projects 1. Recommended at start. Read the comments in each Abc main config file. Make changes for all projects in small steps and test each step. 2. Recommended for special projects. Add your changes, what is different from the default,