The Boss of ERP System/Center of an ERP System

Accounting Module is the center of an ERP System, for every other module is directly or indirectly linked with accounts. And most strange of all even Quality Control links to accounting as without Raw Material or Finished Goods passed by Q.C. is not considered to be Purchases or Sales respectively.
Its truly the Boss of an ERP System as every Module links and ultimately reports to the Accounting Module.

System/ERP Analysis

Work of System/ERP Analysis is very much like a game of chess. 

Just like a genius chess player foresees his moves, an analyst too has to foresee the development and implementation moves. If an analyst discovers new things which he failed to foresee during analysis period then its nothing but bad analysis. As those new things discovered during the development or implementation period are the direct cause of the delay in the project by demanding complete re-designing of the System.

Intrinsic Philosophy of RDBMS

The basic idea is that a data becomes meaningful only when 2 dimensions of the data are defined.
This is the Quantum level of Relational Database Management System.

Simple and amazing isn't it?

The Origin of Programming Languages

It all started with invention of P.L.A.D.C. (Programmable Logic Array Digital Circuit) or P.L.D.:

P.L.A.D.C. gave birth to programming concept with Machine Languages.
Before P.L.D. only Digital Logic Circuits existed.

The invention of P.L.D. gave birth to the concept of programming itself. This was a monumental shift in the image of computers. 

Machine Language

The P.L.D. was such a device that could convert itself into any D.L.C. according to the signals sent in electronic impulses which were high and low combinations. The high and low states were named as 0s and 1s respectively and thereby called as machine language.
While machine languages were the first programming languages, it involved a process called debugging. You may know what is debugging (in higher level languages the compiler or the IDE does automatic debugging) but when machine languages were used debugging was manual. This was definitely a tedious work and the higher-level language programmers of today definitely won't do it as they are used to relatively much more sophisticated environment.  

Assembly Language  

In assembly language the 0s and 1s were replace by mnemonics. Example '1010' was replaced with 'A'. Here programming became much easier and understandable until of course there was a shift in the complexities of the functionality demanded. 

Third Generation Languages

When more and more complexities were demanded these mnemonics in the assembly language too became relatively complex for the programmers. This lead to the creation of Third Generation languages such as C, PASCAL, BASIC etc. and later on OOPs based languages like C++, Java, C# etc.
To be continued......

A Thesis on Program and Exceptions

A program is very much like a train which runs on track of instructions.

While an Exception is an end of line in the track of instructions. As Exceptions are events for which no instruction is given to the computer. So on reaching such an event (end) the program crashes.

In the above picture the train (program) is about to crash on reaching the end (exception). 
Exceptions are therefore called events for which no instructions are given to the computer. In other words the program runs out of the track of instructions.
While exception handling is very similar to safe changing of track of the train.
Just ponder upon the following picture.

The try-block is very similar to a radar that detects the exception before hand if it finds any exception it lets the program on a safe track called catch-block.
Isn't it amazing! to think like that.

There are 3 features of OOPs

Following are the 3 features of OOPs:

1) Abstract-o-Encapsulism (Combination of Visible & Invisible data)

2) Polymorphism

3) Inheritance

I just decided to combine the 'Abstraction' and 'Encapsulation' together to form 'Abstract-o-Encapsulism' which is simply ‘Combination of Visible & Invisible data’. As I am convinced that 'Abstraction' and 'Encapsulation' are just 2 aspect of the same thing.

A Grand Linkage:

Likewise, 'Abstraction' is CAUSED by 'Encapsulation'.

So the Equation is,

'Abstraction' + 'Encapsulation' = Whole Truth (Complete Data)

Now,

'Abstraction' = partial Truth (Data) which is visible.

'Encapsulation' = remaining partial Truth (Data) which is invisible.

Therefore,

Partial Truth (Data) which is visible + Remaining partial Truth (Data) which is invisible = Whole Truth (Complete Data) in other words, "Everything around us is Abstract-o-Encapsulism".

- By Suneet K. G. Chaudhary

[E-mail: skgchaudhary@gmail.com]

Abstraction is Magic (in context of OOP)

I have just discovered a synonym for Abstraction and that is 'Magic'. Anything which you feel like Magic is an Abstraction for you. And most importantly Abstraction is all around us.
For Eg: When a Magician brings out a flower from an empty box. You have absolutely no idea, how the flower reached inside the empty box. There is obviously some way but its hidden. The magician Encapsulates the way through which the flower entered the box. Now, thats what I call an Abstraction.
Similarly, when you use 'Facebook' ever wondered how it works. Its a complete Abstraction. Remember there are hard working developers working behind the scenes for your comfort on Facebook.