Skip Navigation Links
SolutionsExpand Solutions
Contact Us
Why Philosophy?

Our Philosophy

An understanding of the philosophical foundation of the firm you select to deliver your customized software solution is critical. Outlined below is our corporate philosophy regarding a myriad of issues that underpin a successful development project; this discussion provides detail necessary to supplement a high level Mission Statement.

An appreciation of our corporate philosophy regarding these issues will permit you to better understand our project approach and methodology and thus enable you to better evaluate our ability to successfully initiate, develop, and implement your software project.

Software Fit. The tighter your software is integrated into your organization the better you can leverage your investment in technology – a key component in attaining and maintaining your competitive advantage. Your solution should fit like a glove – not like a mitten. Business policies and procedures should never be amended or modified to fit poorly designed custom software or to accommodate an ill fitted off-the-shelf software application package.

Custom Software. Development of Custom Software to meet your organizations needs does not require “reinventing the wheel” nor does it require “starting from scratch”. Off-the-shelf software applications packages can often be used to meet back office (accounting) requirements; many can be modified as required. Additionally, we are often able to modify systems built for other clients to meet your specific and unique needs – thus accelerating development and reducing overall costs. Synergy between components of your system is crucial to software fit.

Rapid Development Prototyping

Methodology. Cost effective systems development is achieved through application of proven project management methodologies. With the advent of fourth generation programming languages, project phases should no longer be performed and completed in series. For example, tasks of Systems Analysis and of Systems Development have evolved into an interdependent iterative process known as Rapid Development Prototyping.

Immediately following the systems analysis (discovery) phase, initial tasks of the Design phase are performed to permit validation of each phase by the development team and stakeholder partners. An initial data model is designed and populated with sample data. Screens and report layouts are designed and quickly prototyped. The resulting “picture worth a thousand words” is an important and critical tool used to validate and, if necessary, to modify results of analysis and design phases.

The handoff between the Design and Development (database development/programming and unit testing) is strengthened through the use of seasoned programmer analysts with knowledge of business processes.

Parallel Beta Testing of legacy systems not only ensures an additional level of quality control but also permits complete training of end users and systems administrators prior to Final Implementation.

Business Process Analysis. Prior to migration of a legacy system or to the design of an entirely new one, it is critical that the efficiency and effectiveness of the underlying business processes in meeting organizational goals be understood and evaluated. This crucial task is performed during the Systems Analysis phase of the development lifecycle. Software should be tailored to organization only after policies and procedures are determined to conform to best practices.

Testing and Quality Control. Unit testing by the programmer/analyst is insufficient to ensure an acceptable level of quality control. Each functional process must be tested at a macro level using sample data to better ensure overall system integrity.


Data Quality and Integrity. Your technology investment can be effectively leveraged only if the underlying data is of the highest integrity – the old adage “garbage in, garbage out” continues to ring true for systems of all sizes and character. Quality information – which will enable you to attain your strategic objectives – can only be gleamed from data of the highest integrity.

Quality control must be an integral aspect of the development process and must be validated through adequate testing. Additionally, design must ensure that errors are trapped and eradicated at each systems interface – at the user interface, and, as importantly, at the interface with each outside data source. Finally, design must ensure that data collected is of sufficient granularity to support the information requirements.

Software Tools. Proper selection of software tools depends on several factors. We develop new systems using Microsoft’s .NET platform an industry standard. .NET will permit construction of enterprise wide client-server systems as well as the most sophisticated web-based systems. The popularity of this platform ensures a breath of experienced personnel resources with be available – as a reasonable cost – to maintain and enhance your system and thus protect your technology investment.
Use of other software platforms is sometimes dictated by the development strategy. For example, Micro Focus tools can be used effectively to facilitate the migration of a cobol-based legacy code from a mainframe to a client-server environment. Modification of off-the-shelf software application modules will also necessitate use of the applications native code.