|
Data Architecture Guiding Principles |
|
Jan 20, 2009 at 03:41 PM |
|
These guiding principles provide direction but also serve as criteria for evaluating proposed solutions and opportunities: •One version of the truth –Create a single set of data used for analytic reporting which is correct and consistent across the enterprise. Look at MDM emphasize on your critical data
•Work from a single logical vision –Build a single logical BI model/architecture that is agreed upon and provides a common goal for building or modifying physical systems
•Standardize on a set of BI tools –Minimize costs by avoiding duplicate licensing and environments –Create a consistent experience at all levels (tool is not important SAP, Cognos, Oracle, BO,STANDARDIZE)
•Maximize flexibility with modular architecture –Minimize specific tool dependency issues –Reduce future development and maintenance costs significantly
•Build, Deploy and Refine in iterations –Achieve incremental benefits –Accelerate business adoption through reduced development time
•Base data transfer and storage on reporting needs –Avoid the transfer and storage of data that does not meet a current or planned analytic reporting need –Meet business needs for data timeliness
|
|
|
An economy is based on trust |
|
Jan 16, 2009 at 11:14 AM |
|
An economy in our type of society is based on trust and faith. In the last couple of months we have seen different types of human nature. Welcome into the world of economic philosophy that has been unchanged since the 18th century! Did it really take a momentous crisis for us to realize that people are not rational? For example, we don’t perceive circumstances objectively. We pick out those bits of data that make us feel good because they confirm our prejudices. As Andrew Lo of M.I.T. has demonstrated, if stock traders make a series of apparently good picks, the dopamine released into their brains creates a stupor that causes them to under perceive danger ahead. I do take more comfort in the belief that this changing of the guard will generate optimism, if continued, will see economic fruit. The faith that we lack today is not merely in banks, the stock market or real estate investments: it is in each other. The confidence will come back but it may take some time mostly because of the global nature of our institutions and they will regain the power to restore the common sense of trust that makes every economy work. For know we have fear which leads to people not wanting to spend, and not wanting to make investments. And that leads to more fear. |
|
|
SOA Architecture Strategy |
|
Jan 15, 2009 at 11:48 AM |
|
Use industry best practices any new integration solution should be designed using SOA and principles. – –Provide visibility to web services through a published web service catalog. –Modularize services by functionality, maintaining independence and therefore flexibility. –Use schema standards such as Open Applications Group (OAG) and design patterns to ensure technology agnosticism. –Divide processes into atomic single purpose independent services. –Ensure loose-coupling of systems by separating system specific translations and functions from generic business process services. –Utilize tools that readily enable SOA: WebLogic Integration (WLI) in conjunction with an Enterprise Service Bus (ESB).
|
|
|
Tackling a System Selection Process in 4 steps |
|
Jan 15, 2009 at 11:14 AM |
|
Software selection is a tricky and strategic process for any corporation. Here is how I would tackle a system selection process: • The system selection process follows a fact based approach. Application or functional requirements are gathered via interviews and workshops with representatives from the Operations,Finance, Marketing, and IT. These requirements provided the basis for the RFP. • Vendors in various functional areas, including Business Vertical, CRM and ERP, should be reviewed to determine which would be included in the selection process. Through primary and secondary research (e.g. analyst reviews, vendor calls, subject matter expert reviews, vendor websites, etc.), three to five vendors should be issued for an RFP and invited to demonstrate their offerings. • To provide a consistent approach for vendor selection analysis, a scoring schedule with weightings should be developed and validated with the client. Further, scoring criteria should be established to evaluate the vendors’ RFP response. • Based on the scoring results and qualitative assessment of the vendors’ RFP response and product demonstrations, two vendors should be short-listed for detailed cost analysis and high level implementation planning.
Any questions or feedback email me or call me |
|
|
|
<< Start < Previous 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
