Development Patterns and Best Practices

OnX implements and strongly supports Microsoft’s “Patterns and Best Practices”. They are a set of guidelines that identify key design decisions that are made, during the early phases of development and provide design-level guidance to help choose appropriate design options, where applicable. These guidelines help to develop an overall design by presenting a consistent architecture built of different types of components that will help achieve a good design, taking full advantage of the Microsoft platform. In addition, these guidelines serve as a roadmap of the most important distributed application design issues encountered when using the Microsoft platform. They also simplify application readiness, towards a service-oriented architecture (SOA). This by its very nature forces the solution to be loosely coupled. Thus, allowing the solution to be transferable and portable, from one business premises to another.

These guidelines are becoming an industry standard, allowing for consistent design patterns that are shared across different business verticals’ development teams...

read more ... .NET Best Practices

OnX .NET Reusable Frameworks - Coming Soon!

OnX Development & Implementation Process

Our development methodology is a step-by-step, iterative process that involves a team comprised of subject matter experts, Developers, Solution Architects, User Interface Designers, Quality Assurance Analysts and Project Managers.

For product deployments and systems integration projects, we modify this process slightly to take into account the immediate implementation of the products themselves, and then the customization based on requirements and design concepts determined during the elaboration process. In this manner, a phased approach is often naturally derived from the implementation of customized components, and the subsequent testing and release of each new function.

OnX has a full-time, dedicated Quality Assurance department and a strict QA process that is followed for all projects. Once we move into the future stages of these projects this team will play an active role.

The QA process begins immediately, as soon as the functional specifications and requirements have been documented. A test plan is derived from this document, outlining the basic procedures and types of testing that the project will require. Each project is unique and the requirements and specifications dictate what type of testing is required.