Blogs about Jazz

Blogs > Jazz Team Blog >

Lessons learned adopting the IBM Systems and Software Engineering Solution

I recently had the opportunity to work on site with customers from all around the world on the Systems and Software Engineering (SSE) Solution Beta. I lead the SSE Jumpstart team, whose responsibility is to understand Systems customers business needs and help them adopt IBM’s new offerings. By working closely with early program customers, we identify where our solution does and does not meet their needs. This allows us to respond more quickly to improve the solution and capture lessons learned before the solution is generally available. Our mission is to make customers and partners successful using the SSE solution and iteratively improve the solution. The SSE Solution helps teams specify, design, implement and validate complex products and the software that powers them. It offers an integrated set of capabilities to enable you to predictably deliver competitive, high-quality products while meeting regulatory and compliance requirements. The Systems and Software Engineering (SSE) Solution includes:

  • IBM Rational DOORS for requirements management
  • IBM Rational Rhapsody and Rhapsody Design Manager for system and software modeling
  • IBM Rational Team Concert(RTC) for project, change, build and source management
  • IBM Rational Quality Manager (RQM) for quality and test management
  • IBM Rational Engineering Lifecycle Manager (RELM) to visualize, analyze and organize engineering data and their relationships
  • IBM Rational Solution Process Assets

The focus of the most recent beta was on IBM Rational Engineering Lifecycle Manager (RELM). This new offering was announced and blogged about by Meg Selfe, Vice President of Complex and Embedded Systems. The purpose of this technical article just published on  is to share some of the lessons learned while working with beta customers as they adopted the SSE Solution. The article answers some of the most common business and technical questions asked by the SSE beta customers. This information will hopefully be useful for solution architects and deployment specialists. The SSE solution adoption lessons learned are categorized into four areas:

  • Business Needs and Capabilities
  • Solution Architecture
  • Planning the Deployment and Installation
  • Using RELM

I hope you find the article useful when adopting the SSE Solution.

Carlos Ferreira
SSE Jumpstart Team