|
|
Index of Activities
|
| Our Programming Methodology |
There are so many software applications and programs that it would be superfluous trying to explain in a paragraph the meaning of each item listed above. In despite of its apparent diversity their distinctive difference is "coding" not the construction methodology. We always start from an architecture that covers not only the details of the applications to be programmed but also globally the whole system to serve. For instance, if we are contracted to make a custom made accounting package we study globally the whole "physiology" of the accounting process and all its interrelations within an organization resembling a Holistic approach in Medicine.
At first sight our potential customers and perhaps our competitors may argue that this methodology is unnecessary expensive but the Systems Thinking experience say just the contrary. We spent, in the average, 20% of our total time doing the architecture but we save a lot of time afterwards being our costs by far much lower than conventional. Actually, programmers spend almost 90% of their time "coding", that is, translating to some programming code a set of specifications not always well defined, most times confectioned in a hurry, with a myriad of weak points. We prefer to start programming once specifications are fully checked and certified. The tasks of coding in our methodology are not as significant as conventional, in fact less than 30% of the total time. We devote enough time to think, to review, to meticulously document what we do step-by-step.
|
|
| Programming Talent vs. Coding Talent |
|
From the systems point of view of our working methodology, there is not much difference between Microprogramming, a Systems Application Programming and the Programming of a set of Intelligent Agents. Main differences rest in coding, not in the analysis and system design tasks. Our philosophy is to hire and to enhance programming talent not mere coding talent. Instead of offering the conventional approach: A Language-Oriented to an Application-For a given Industry, for instance a Java guru specialized in security for the banking industry we prefer to offer an interdisciplinary approach of programming excellence, for instance a Senior Systems Architect, a Senior Programmer Analysts and a Senior Programmer to solve the security problems of a banking institution.
|
|
|
|