|
 |
Architectural details
NethFrame - a new general business approach for a better enterprise productivity
The new technologies are bringing along a strong support for developers and development process. Many IDE provide today a common way of developing some unspecific business structures.
The fundamental paradigm of Object Oriented Thinking by reusing the existing functionalities and structures is applied on a large scale with the use of frameworks and with the purpose of increasing the productivity.
The presence of a framework assures a consistent development context and offers all facilities ready to go. The developers can concentrate on the business logic implementation without worrying about the technical support and context. The technical predefined framework is the .NET framework.
The .NET framework is a generic framework that has a neutral approach of the specific business logic for specific applications.
The .NET framework is a general framework that only gives a general approach of development and provides no specialization in the sense of increasing the enterprise productivity.
Why do we need the NethFrame framework?
Because our NethFrame is a framework that is:
- complete generic as far as business logic dependencies are concerned and
- specialized for enterprise productivity.
By using a framework, the newly created applications benefit from other advantages automatically:
- the scalability of the application
- the portability of the application
- the opening of the application to future development and to future business additions or updates
Framework components
1. The INFRAGISTICS NetAdvantage is in fact "a presentation layer toolset for building commercial class user interfaces for Windows Forms, ASP.NET, Tablet PC and COM". We are using this presentation layer because of the multiple facilities that are integrated in its components. The original .NET presentation layer consists of components that do not support many useful needs.
The INFRAGISTICS NetAdvantage set of presentation layer components is a commercial one and it is not intended to be integrated in our framework in the future. But we need to isolate our framework from the product in the future to avoid the improbable but possible situation of closing the product development and support. For that purpose we will inherit all used classes and we will use only our specific class names in our framework.
2. NethFrame Internal Modules -CSLA Isolation Layer - CSLA .NET
"The Component-based Scalable Logical Architecture (CSLA) is a distributed object-oriented architecture, meaning that it uses object-oriented design and programming concepts to define a logical n-layer architecture.
An application that is built on the basis of this architecture can easily be configured to run in various physical n-tier configurations.
Because this product is not a commercial one, that means it is delivered "as it is", without any official support and because it is an open-source product we have chosen to integrate the principle and main functions of its components in our framework in the future.
To increase the productivity in using "our" CSLA components we are using a specific generator named CodeSmith Studio based on a free engine - Code Smith Tools.
3. NethFrame Internal Modules - .NET Isolation Layer
This module of our architecture is assuring the previous specified principles of isolation in relation with .NET.
4. NethFrame Internal Modules - Base Components Layer
The basic components layer contains all the basic components of the framework, such as:
- The logging system
- The synchronous messaging system
- The asynchronous messaging system
- The search and filter system
- The authorization and authentication system based on technical accounts and business accounts
- The licensing system
- The communication encryption system
- The data paging mechanism
- The caching mechanism
All these functional systems will represent the basis for the next layers. The visibility is of the "up-down" type in the sense of viewing the base layer from the business kernel and business shell layers.
5. NethFrame Internal Modules -KERNEL components Layer
This is the first business layer of our framework. All general business rules and all general business objects are implemented on this layer.
The following are implemented on this layer:
- The licensing mechanism
- The integration with third components ("Microsoft World" components for example).
- The import/export system
- The printing and reprinting system
- The reporting system, including report editing facility
- The logical navigation (based on possible workflows)
- The docking system
6. NethFrame Internal Modules -SHELL components Layer
This is the second business layer of our framework.
On this layer, the following are implemented:
- The business templates for forms and controls
- The reports scheduler
- The tab order customization
- The "to-do list" functionality
- The chat mechanism
- The forum possibility
- The "no touch deployment" facility
- The multi-company support
Last versions of integrated components
- .NET 2.0
- CSLA 2.0
- MS SQL Server 2005
- Infragistics NetAdvantage 2006
|
|
|
|
