Skip to main content

Component Types

Intro​

In RocketSLO, every component has a type that reflects its role within your organization and architecture. This allows you to create a clear representation of how your teams and systems are structured.

Common component types include:

  • Product
  • Feature
  • Service
  • Package
  • etc.

Choosing the right types​

The decision of which types to use depends on your specific needs and how you want to model your organization and architecture.

Example:

Consider a team structure with a Product Manager, a Designer, and a Dev Team. Each role has distinct responsibilities:

  • Product Manager: Oversees the overall product.
  • Designer: Defines product capabilities from a user-centered perspective.
  • Dev Team: Implements the services that power those capabilities.

In this scenario, a suitable set of component types might be:

  • Product
  • Capability
  • Service

Using these types would accurately model the team structure, the relationships between roles, and the system's architecture. This aligns the quality management model with the actual ways of working within the organization.

Starting Simple​

You can begin with a single component type, such as "service," which often maps directly to physical components. As your understanding of your system and quality needs evolves, you can expand to include higher-level abstractions like "capabilities" or "features.”