Publishing integration scenarios on Service Management Connect

Body

One of the guiding principles of OSLC is that everything is scenario driven. OSLC workgroups focus on satisfying real-world interoperability
scenarios and use these to agree of what is to be defined in an OSLC specification.

IBM teams follow the same principle when trying to define integration between products. A scenario allows us to define the who,what,why and how of an integration and to do it in a way that allows for disparate groups to focus on the task at hand.

We're publishing on the Jazz for Service Management wiki the scenarios that we've used ( and are using ) to define functionality that went
into newly released ( and soon to be released ) IBM products.
 

• Service and Application Problem Diagnosis
• Service Asset and Configuration Management - View Asset and CI details via UI Preview
• Faster Incident Ticket Routing to reduce Mean Time To Resolution by leveraging real-time monitoring information.
• Perform cross-product configuration for a Business Service Management solution
• Schedule and Orchestrate any vendor's Automation Plan
• Deployment of VM, System, and Application Patterns in cloud

In future blog posts, I'll link these scenarios to their various implementing products. And I'll add other scenarios as they are created
by the development teams.

We welcome your comments and your participation as we define new integration scenarios. If you want to propose a scenario, contact me or
create a page in the wiki ( see here for help. )