Ubuntu Wiki

• Launchpad Entry: servercloud-p-orchestra-itsm

• Created:2011-10-20

• Contributors: ChuckShort

• Packages affected:rt, ocsinventory

Summary

ITSM stands for IT service management. ITSM is a discipline for managing information technology (IT) systems, philosophically centered on the customer's perspective of IT's contribution to the business. ITSM stands in deliberate contrast to technology-centered approaches to IT management and business interaction.

In order to differentiate ourselves from other orchestration products we should offer at least an Inventory Management system (ocsinventory) and a Request Tracker (rt).

Release Note

Orchestra can now be used to track hardware and software installed on your network and track support tickets from your users.

User stories

• Joey is a network admin who wants to keep track of how many
  • installs of Precise they have on their network.

• Maurice is a user at BigSoft and needs to request a new wiki to be

  • setup, and sends a request to the IT Dept through the request tracker.

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

• data migration, if any
• redirects from old URLs to new ones, if any
• how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

CategorySpec