Sunday, August 26, 2012

Financial markets

A starting point of my knowledge of capital and money markets, assets movement, valuation, and regulations surrounding it. My focus is to capture the works on a macro level. I acknowledge difficulty in visualizing the time factor on these conceptual models. I am hopeful I will find a way to showcase the effect of time on regulations entities and how they affected these entities and future ones in the same line of thoughts.


Look forward to adding Federal reserve bank and other agencies aligned with the securities & associated industries.

Friday, June 29, 2012

Conceptual Modeling - Why do it?

Why do we involve in conceptual modeling - to interface knowledge between all players involved AND to bring into view ideas - not tables and entities of the business - be that motivation,  process or information.




This gives us a view of overall picture and form a great way to accumulate business knowledge. As this is a collection and position of ideas, this can encapsulate all the components of enterprise - that are of business importance. Ideas might be as simple as Risk and market segmentation. How these play down into the multiple models downward - process & data in layer 3 of Zachman - is a different exercise - typically called logical modeling. This is more to do with knowledge accumulation.

Friday, June 1, 2012

Complexity & Conceptualization

Interesting to see that complexity in IT systems is getting focus - from Main Street! Peter Doolan of Oracle's keynote presentation at the Oracle Location Intelligence conference was an eye opener and hopeful - as it meant we have a focus from the top - on making things easier.

This will be challenging to IT industry - which doesn't reward fixing previous mess so much as  it responds to  the enhancement or additional functionality or offering.

http://www.locationintelligence.net/

Tuesday, April 3, 2012

Much Ado about Hadoop

Much ado about Hadoop - is in the air currently. This is a novel way to do analytics - spread the risk of trying to define everything at once, truly agile. At what cost is the question. Technology innovation makes it possible for mom & pop to afford critical analytics - kudos to innovation on the infrastructure layer - to make clustering of nodes to solve your problem efficiently - at the cost of tailored coding at the MR level.

For the ones in the weeds of it, its new. From a larger perspective, its data management in a new infrastructure layer offering. The concepts of models, knowledge management, change management still apply. Oh - I forgot - the roles still matter. Going forward, data management involving Hadoop MR codes, will evolve into managing the MR Code libraries - as those pose quite a bit of rules for Enterprise to manage. Whats our holistic view into the Map-Reduce Codes... and rules embedded inside?  Limiting the acknowledgement  to the infrastructural gains, with added access to tons of open source statistical excellence is the key.