You can create calculated members for dimension and then use them in the query. Example below will create 3 calculated members based on filter condition:

WITH MEMBER [Product].[Category].[Case Result 1] AS ‘ Aggregate(Filter([Product].[Category].[All].children, [Product].[Category].currentmember.Properties(“Key”) < “3″))’
MEMBER [Product].[Category].[Case Result 2] AS ‘ Aggregate(Filter([Product].[Category].[All].children, [Product].[Category].currentmember.Properties(“Key”) = “3″))’
MEMBER [Product].[Category].[Case Result 3] AS ‘ Aggregate(Filter([Product].[Category].[All].children, [Product].[Category].currentmember.Properties(“Key”) > “3″))’
SELECT NON EMPTY {[Measures].[Order Count] } ON COLUMNS
, {[Product].[Category].[Case Result 1],[Product].[Category].[Case Result 2],[Product].[Category].[Case Result 3] } ON ROWS
FROM [Adventure Works]

Result will be

http://ssisctc.codeplex.com

http://evisional.wordpress.com/2011/08/05/sp_viewdata/

Definitions:

PascalCasing (aka Upper Camel Casing) – The first character of each word is capitalised. Example: FirstName

camelCasing – The first character of each word is capitalized except the first one Example: firstName

*UPPERCASE – All characters are uppercase. Use these identifiers only for abbreviations (eg: ADO) and for Transact SQL keywords (eg: SELECT Id FROM Table)

 (reference: http://en.wikipedia.org/wiki/Naming_convention_(programming) )

1. Package Name Convention

As the number of packages will grow during the project life, it is suggested to have naming convention for ETL package names so that the package can be manageable.  The current development culture of defining namespaces for objects. Accordingly, the following package naming convention should be applied to package names:

[ProjectName].[DestinationDatabaseName].[SubjectName].[Action]_[Table Name].dtsx

OR

[ProjectName].[DestinationDatabaseName].[SubjectName].[Package_Description_Purpose].dtsx

eg.

AdventureWork.EDW.Sales.Load_Internet_Sales.dtxs 
AdventureWork.EDW.Sales.Transform_Internet_Sales.dtxs
AdventureWork.EDW.Sales.Load_DimCustomer.dtxs

2. Name Convention for Tasks/Compontents

Use naming conventions for your tasks and components. I suggest using acronymns at the start of the name and there are some suggestions for these acronymns at the end of this article. This approach does not help a great deal at design-time where the tasks and components are easily identifiable but can be invaluable at debug-time and run-time.  e.g. My suggested acronymn for a Data Flow Task is DFT so the name of a data flow task that populates a table called MyTable could be “DFT Load MyTable”.

The acronymns below should be used at the beginning of the names of tasks to identify what type of task it is.

These acronymns should be used at the beginning of the names of components to identify what type of component it is.

3. Variable Names

Name convention for SSIS package should be in Pascal Casing

E.g :

IsOk
IsDateEarlierThanOctober
SourceConnectionString

The following common variable names should be used across packages

SourceConnectionString
TargetConnectionString
LogConnectionString

4. Script

 
SSIS supports both VB.NET & C# Scripts. In HICAR project, the VB.NET Script is used across the SSIS package, particularly Script component. The following table summarizes the capitalisation rules for identifiers and provides examples for the different types of identifiers.

DataStage: Windows, Unix, Other Platforms
Informatica: Windows, Unix
Microsoft SSIS: Windows

2) Parallelism

DataStage:  Have both sequence (DataStage Server) and parallel (DataStage Enterprise Server )process
Informatica: ?
Microsoft SSIS: ?

3) Deployment facility

DataStage: No
Informatica: Yes
Microsoft SSIS: Yes

4) . Numbers of available transformation functions

Informatica:. 58
DataStage: 28 
Microsoft SSIS: 30

5) Slowly Changing Dimension

Informatica:. Supports Full history, recent values, Current & Prev values.
DataStage: Supports only through Custom scripts. Does not have a wizard to do this
Microsoft SSIS: Yes, with a Wizard but difficult to modify

6). Time Dimension generation

Informatica:. Does not support.
DataStage: Does not support
Microsoft SSIS: Does not support, but Time Dimension can be generated by using Microsoft SSAS

7). Rejected Records

Informatica:. Can be captured
DataStage: Cannot be captured in separate file
Microsoft SSIS: Can use conditional split transformation and error redirection to either CSV files or tables.

8). Debugging Facility

Informatica:. Not Supported
DataStage: Supports basic debugging facilities for testing.
Microsoft SSIS:  can use Breakpoint, Data Viewer and error handling

9) Application Integration Functionality, support for real Time Data Exchange

Informatica:. Not Available
DataStage: Not Available.
Microsoft SSIS: Not Available.

10) Metadata: Ability to view & navigate metadata on the web

Informatica:. Does not support
DataStage: Job sessions can be monitored using Informatica Classes
Microsoft SSIS: Does not support

11) Ability to Customize views of metadata for different users (DBA Vs Business user)

Informatica:. Supports.
DataStage: Not Available
Microsoft SSIS: Does not support 

12)  Metadata repository can be stored in RDBMS

Informatica:. Yes
DataStage: No. But the proprietary meta data can be moved to a RDBMS using the DOC Tool
Microsoft SSIS: Does not support 

13) Support And Maintenance, Command line operation

Informatica:. Pmcmd –server interface for command line
DataStage: Not Available
Microsoft SSIS:  Usage of Dtexec.exe

14) Ability to maintain versions of mappings

Informatica:. Yes
DataStage: No
Microsoft SSIS:  No

15) Job Controlling & Scheduling, Alerts like sending mails

Informatica:. Supported.
DataStage: Does not support directly ( no option). But possible to call custom programs after the job get executed)
Microsoft SSIS:  Job Agent, Email Notification

16) Languages

Informatica: ?
DataStage:  Script, C++
Microsoft SSIS:   C# (2005,2008), VB.NET (2005)

 17) ETL Proccess

Informatica: ?
DataStage:   DataStage Job
Microsoft SSIS:   package

18) Support for looping the source row (For While Loop)

Informatica:. Supports for comparing immediate previous record
DataStage: Does not support
Microsoft SSIS: Yes. ForEach Loop

WITH
MEMBER [Measures].[ParameterCaption] AS [Currency].[Currency Code].CURRENTMEMBER.MEMBER_CAPTION
MEMBER [Measures].[ParameterValue] AS [Currency].[Currency Code].CURRENTMEMBER.UNIQUENAME
MEMBER [Measures].[ParameterLevel] AS [Currency].[Currency Code].CURRENTMEMBER.LEVEL.ORDINAL

SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,
FILTER ( [Currency].[Currency Code].CHILDREN,NOT ISEMPTY( [Measures].[Closing Balance] ) ) ON ROWS

FROM ( SELECT ( STRTOSET(@Agency, CONSTRAINED) ) ON COLUMNS FROM [My Cube])

http://www.manoli.net/csharpformat/format.aspx#html