ArtisTech lives by two principles of technology guidance:
- Technology Experience Creates Flexible Open Architectures: ArtisTech is committed to, and skilled in, the Microsoft .NET platform as well as JAVA (including J2EE, J2ME and JBOSS). ArtisTech’s senior
staff have programmed in all of the industrial strength language/platforms, and ported to J2ME, Palm OS, and WindowsCE platforms. Our senior software experts have developed critical software in a wide array of domains, from
real-time continuous planning in JAVA (DARPA COAA program), to real-time analytic simulation in C/C++ UNIX to derive answers from scenarios. Our software architects have diverse expertise including extensive programmed in
LISP, ADA, openGL.
- Prototype/Apply: On the way to building new, fully operational applications, it is critical to prototype effectively. ArtisTech’s staff is composed of Software Engineering and Software Development
experts. We use UML and other OOD approaches to develop reusable, extensible code to provide reusable software from our research prototypes, for our operational client applications. As a small business, we must develop
efficiently to survive.
We use several effective and important Software Engineering approaches to meet customer software development requirements:
ArtisTech staff pragmatically apply UML, a combination of object oriented analysis and design, object oriented modeling and a “Use Case” oriented approach.
Effective Coding and Documentation Standards
ArtisTech has taken a disciplined approach to software design and coding which ensures that the systems we build are exceptionally extensible.
RAD (Rapid Application Development) is defined as “a software development process that allows usable systems to be built in as little as 60-90 days, often with some compromises.”. This method takes advantage of the “80-20” rule, which says that 80% of the
functionality of a system is usually developed in 20% of the total development time. It is especially useful for prototyping, in that the acceptability of a system can be assessed against the agreed mimimum useful
set of requrements rather than all requirements. The benefits can be huge. The method avoids the long delays which can lead to the software only reaching a sufficient state of development only after the customer’s
problem has changed.