The delivery of a robust software product demands a well practiced methodology to drive stakeholders to shape the requirements and encourage collaboration.  Integration and development efforts are becoming more prevalent in organization to solve immediate business problems; however, lack of proper planning and architecture foresight decrease maintainability. A formalized and accepted methodology instituted enhances the productivity of development effort by involving the stakeholders early and often

The Aaxis Group Software Development Process
Leveraging the discipline of the Rational Unified Process (RUP) with the practicality of eXtreme Programming (XP)

The AAXIS development team exercises a proven and professional software development process that has enabled success with all of our customer and internal software projects.

Our process capitalizes on the execution of the "best practices" of software development as identified by the Rational Unified Process (RUP), combined with the rapid, micro-iterative process defined by "Extreme Programming" (XP), an implementation of Agile Software Development. Through years of software development and engineering experience, AAXIS has assembled a winning team well attuned to this process for the entire lifecycle for specifying, designing, building, testing, deploying, and repeating enterprise-scale software solutions.

Macroscopic Development Process - Rational Unified Process
The Rational Unified Process (RUP) is the defacto standard for Software Engineering and Development. AAXIS embraces RUP best practices throughout the four core phases of the process: inception, elaboration, construction and transition.

Microscopic Development Process - Extreme Programming
eXtreme Programming (XP) is a software development practice that focuses primarily on developing test cases first, integrating often, and maximize communication in a rapid iterative and repeatable manner. Within the macroscopic RUP process, the AAXIS Group executes eXtreme Programming through an intensive, rapid iterative build-test-refactor cycle. XP iterations are shorter than the RUP iteration, so that the contained XP iterations are defined as smaller steps to meet the goals of its parent RUP iteration.