A project (shown here in dark blue) is a container unit for all work related to a development project. It stores all relevant artifacts across the development lifecycle, starting with enhancement requests and defects, progressing through development, and concluding with release. Projects are associated with all project-relevant objects such as change requests, requirements, and release packages.
Service Management (shown here in violet) is the practice of managing incoming demand to an IT organization, by tracking new Ops Change Requests (such as incident and problem reports), and then managing change over time in response to those requests, incidents, and problems.
Requirements Management (shown here in pink) is the practice of tracking the development and implementation of product requirements, from inception through to delivery. Organize your product requirements according to type, into custom collections, and into documents that you can share with other stakeholders. Key to requirements management is the audibility of work over time, so that you can see how requirements have been implemented by developers and testers, and how final products are delivered. You can associated requirements to the change requests, enhancement requests, and releases via which the requirements are implemented.
With development management (shown here in light blue), you orchestrate and monitor your key software development efforts, tracking source code changes and approvals through a central workflow engine. You coordinate events across systems, integrating application project definition, source code management, quality management, and release approvals. You also track and report on development progress, providing comprehensive decision-making support to managers and directors who need the latest information at all times on key performance indicators (KPIs).
Quality management (shown here in green) is the process of managing product test cases and tracking the success or failure of tests when validating built products. Test cases are related to the development change requests that they are intended to validate.
Release management (shown here in orange) manages the flow of change into production. It is the handoff between development, quality assurance, and production operation teams. The goal of release management is to deploy application changes into production with high quality and without disrupting the business. But this process is often performed manually and is inefficiently connected to the rest of the application lifecycle, leaving a critical gap between application development and operations as well as creating a backlog of changes that must be made.
At a high level, the domains interact as follows:
Demand Management: Incoming requests from users drive new requirements for development and are planned into releases.
Requirements Management: In response to new demand, requirements drive new release plans, new development change requests, and new test case development.
Release Management: New releases are planned in response to incoming demand, requirements, and operational change requests. Furthermore, testable and releasable builds are planned based on Development and QA input.
Service Management: User demand drives requests for new and changed applications and for defect fixes; operational infrastructure changes are coordinated and planned into releases with application changes.
Development Management: Development builds and delivers new code in response to incoming requirements. As QA test builds, Development respond and address issues.
Quality Management: QA exercise test cases against development and release builds, returning rest results back to Development and turning over approved releases to Release Management.