Archives
-
FxCop rules contest.
I won Visual Assist X (1-user license) at Codeproject (article contest) and I really don’t need it. So here is the deal, the one that will send me most of rules for FxCop (Design rules preferred) will get this Visual Assist X (1-user license). All of the rules (including their sender) will be published here.
-
Enterprise Navigation mechanism.
As every average enterprise my domain also contains many systems develop by many development tools and running on several operation systems. We’ve got Natural/Adabas applications running on MF, Java applications running on Sun and Linux machine, COM, .NET, Delphi, Magic systems running on Windows machines and SAP applications. Most of our systems running as web applications, several as client/server applications and few using virtual terminal.
-
What are the main changes in IT world that will occur in the next 10 years?
As part of the interviews, that I go through lately, I was asked to mention 3 main changes that will happen in IT field within the coming 10 years. Well here my humble opinion:
-
The visual age and architecture or who will save me from endless grid views?
Today most of system split into layers with visual layer (UI) that responsible for formatting and displaying data to the user. Beneath UI layers responsible for application logic and data management. This concept pushes many of us to believe that visual layers are just simple formatting of data therefore can be easily recreate in each system against other system layers to show data. Right?
-
While downsizing/rewriting legacy systems to open/newest system don’t follow legacy system design.
Actually there are two aspects that we tend to follow when downsizing legacy system. The first aspect is business logic and the second is system design.
-
Looking for enterprise architect position.
-
Natty test for adaptive OO systems.
This is a simple test that I use to get basic insight whether system is built on solid OO approach, and adaptive to further changes. Using those questions while interviewing system owner gives me indication about OO level of the system and system adaptively level.
-
What about Specification?
How many times you use third party library that implement any given task such as state machine, logging, Concurrency Utilities, etc’? Eventually you manage to find the right package for your needs and integrate it into your system. Every thing looks great until you find out that the chosen package needs to be replaced for some reason. The problem now is that you need to change your system code in order to use the new package because the new package based on other API and interfaces to interact with.
-
Entity architecture.
There are two main architectural pattern regarding application structure. The most common one is Layer patter. Layer suggests that you will organize your code in layers which characterize certain system aspect and responsible to carry out that system character. System is building from those layers one on another while the upper layer responsible to receive incoming request (Usually User Interface - UI layer) and return results. The request is processed by calling other system layers to perform their layer specialty as part of the process. Every layer should call only layers near the calling layer, no direct calls over layers should be made. In the end of the process the upper layer return results back to the caller. The most classic separation is to 3 layers a. Presentation – responsible for receiving client request and displaying process data. B. Domain logic also known as Business logic – holds system logic. C. Data access – Retrieving and update system data.
-
Part of page images download to machine but didn’t display.
-
Pluggable architecture