Posted by admin on October 3, 2009 under Software Architect | 
Cognos PowerPlay lets you identify and analyze trends in business and financial performance for better business decisions. IBM Cognos PowerPlay lets you analyze large volumes of dimensionally modeled data with sub-second response times using either a Windows client or Web browser. View data from any angle and in any combination to identify and analyze the driving factors behind your business results. Sophisticated time trending and projection lets users analyze what has changed over previous years, quarters, months, and other critical measures. Scalable, customer-proven architecture maximizes network resources.
Reference - IBM Cognos Powerplay Homepage
Here are some tutorials on IBM Cognos Powerplay.
- Cognos Powerplay Tutorial – Tutorial
- IBM Cognos Powerplay Business Guide – Download the Guide
- COGNOS: Cognos PowerPlay Transformer Tutorial – Cognos PowerPlay Transformer Tutorial
Tags: Cognos Bi Tutorial, Cognos Business Intelligence, Cognos Cubes Tutorial, Cognos Data Warehousing, Cognos Impromptu Tutorial, Cognos Powerplay Cubes, Cognos Powerplay Training, Cognos Powerplay Transformer, Cognos Powerplay Tutorial, Cognos Reportnet Tutorial, Cognos Transformer Tutorial, Ibm Cognos Powerplay
Posted by admin on August 24, 2009 under Software Architect |
Bridge pattern is useful when both the class as well as what it does varies. The class itself can be thought of as the. The bridge pattern can also be thought of as two layers of abstraction. : the implementation can be decoupled even more by deferring the presence of the implementation to the point where the abstraction is utilized.
Bridge pattern is great when used as a base of cross-platform frameworks. You want to localize platform-specific code, thus making your scripts easy to extend and maintain. You want to localize browser/feature/object detection code. To do it; the structure of the bridge pattern.
Bridge pattern is classified as a structural design pattern. This pattern helps to hide the implementation details giving more encapsulation. As the interface implementations and abstractions are decoupled , they can have hierarchies. Changing an implementation needn’t require any compilation of abstractions or its clients. This provides a better layering structure than having the traditional abstract implementation of parent interfaces.
References on Bridge Design Pattern
- The Bridge Design Pattern – A quick look at Bridge pattern
- Bridge Design Pattern in C# and VB.NET. – Bridge Design Pattern C# and VB.NET. Beyond OO Design and Development. Valuable source code and UML
- Bridge Design Pattern – The Bridge pattern decouples an abstraction from its implementation, so that the two can vary independently. Publish interface in an inheritance hierarchy, and bury implementation in its own inheritance hierarchy.
- Bridge Design Pattern in Java – Bridge design pattern Java source code example.
- Design Patterns : Bridge – At The Byte Scrolls Website
Bridge pattern is useful when there is a hierarchy of abstractions anda corresponding hierarchy of implementations. Rather than combining the abstractions and implementations into many distinct classes, the bridge pattern implements the abstractions and implementations as independent classes that can be combined dynamically. The bridge design pattern is a way of organizing the entities identified using the layered architecture pattern into classes. The abstract factory pattern can be used by the bridge pattern to decide which implementation class to instantiate for an abstraction object.
Posted by admin on August 17, 2009 under Software Architect |
Singleton patternis one of the best-known patterns in software engineering. Essentially, a singleton is a class which only allows a single instance of itself to be created, and usually gives simple access to that instance. Most commonly, singletons don’t allow any parameters to be specified when creating the instance – as otherwise a second request for an instance but with a different parameter could be problematic. (if the same instance should be accessed for all requests with the same parameter, the factory pattern is more appropriate. )
- Why Singletons are Evil – While I did not write this, I totally agree with it. Brian Button is probably one of the most talented people I know, and I am sure he would love your feedback.
- We Don’t Need No Stinking Singletons: Why to Avoid the Singleton Pattern – OOP Techniques for Flash and Flex Developers
- Singletons vs. Static Classes – My last post seemed to elicit a good number of interesting responses. Today, I’m musing about Singletons vs. Static Classes — two constructs which appear to accomplish the same task. Or do they?
- Design Patterns – Singleton Pattern – A quick look at Singleton Pattern
- Chill out on the Singleton Fetish – ALT.NET dotnet .NET C# Agile BizTalk ASP.NET
- Know your design tools – The Singleton case – A professional software designer is one whose next paycheck depends on the quality of her software – looks for an ever increasing acquaintance with his design tools. One of the most important design tools in software is the actual computing machine is abstract,
- Exploring the Singleton Design Pattern – Exploring the Singleton Design Pattern
- Singleton – the most overused pattern. – Do you wonder why singleton is overused?
- The Singleton Pattern Revisited – A fresh look at Singleton Design Pattern
- Singletons – we are better off without them – Why we should avaoid it.
- Double-checked locking and the Singleton pattern – All programming languages have their share of idioms. Many are useful to know and use, and programmers spend valuable time creating, learning, and implementing them. The problem is that some idioms are later proven not to be all that they were purported, or to simply not work as described. Double-checked locking is one such idiom in the Java programming language that should never be used. In this article, Peter Haggar examines the roots of the double-checked locking idiom, why it was developed, and why it doesn’t work.
- Singleton pattern – At Wikipedia, the free encyclopedia
- Singleton pattern in MultiThreaded Environment – A Journey Through the Minds of EBW Thought Leaders for dealing with issues caused due to Singleton in Multithreaded implementations
Singleton pattern is: make all the methods as static, if for any reason you cannot make all the methods as static, then go for static instance approach. I feel keeping all methods as static methods is better design and developer friendly.
