A software architecture reflects the way a product is organised. The way a software product is organized determines how well, or how poorly, it fits into the software landscape of industry-standard technology as well as existing and evolving technology and business paradigms. It also determines how well it scales from both a transactional and user-count perspective. The foundation of a superior business management architecture is that it is organized into layers: There is a separation of core business logic from interface and database services.
The benefit of a strong architecture and good implementation is that the resulting product will:• Stand the test of time.
• Embrace industry-standard technology quickly and naturally.
• Customise easily to fit the special needs of your business.
• Deploy flexibly to new paradigms.
• Scale to the changing size of your business.
Allow greater independence to make choices such as database or operating system. A superior architecture is not created overnight. Creating a product with a superior architecture takes a huge investment over a number of years. Sage has made that investment. Over the past decade, as software fads have come and gone, the architectural message and object-oriented approach of Sage Accpac has remained unchanged. The Sage 300 ERP (formerly known as Sage ERP Accpac) architecture stands the test of time and is ready to deliver value to your business for years to come.
The Sage 300 ERP (formerly known as Sage ERP Accpac) Architecture Technology
Sage 300 ERP (formerly known as Sage ERP Accpac) has a superior architecture based on separation of core business logic from user interface and database services. The truth is that no other player in the midmarket has anything approaching the strength of this architecture.
The Sage 300 ERP (formerly known as Sage ERP Accpac) architecture separates user interface services, core business logic, and database services, and is implemented in a completely object-oriented fashion. The architecture allows for easy adaptation of new user interfaces and databases, while maintaining a single common code base for business logic.
Separation of Core Business Logic
The Sage 300 ERP (formerly known as Sage ERP Accpac) architecture, is designed to stand the test of time by isolating and minimizing dependencies on workstation and network operating systems, databases and user interface environments. The architecture features a strict separation of interface services, business logic services, and database access services, with interfaces that provide consistent layer-tolayer communication.
Database Services. Sage 300 ERP (formerly known as Sage ERP Accpac) currently supports three database choices: Pervasive.SQL, Microsoft SQL Server, and Oracle. When speaking of different databases, different versions of the same database deserve some notice. Database versions change frequently, and the Sage 300 ERP (formerly known as Sage ERP Accpac) business logic does not depend on the peculiarities of a single database version. Because all database access is abstracted into a Common Database Services Interface (CDSI), adaptation to a new database version can be done quickly in one place (the database driver), with less detailed testing of the whole application required.
If you are looking to benefit from the implementation of a world class ERP Solution, please contact our Strategic Sales Team.