IT:AD:System Functional Requirements:Assistance:Self-Help Assistance should be Embeddable [Notes]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

# IT:AD:System Functional Requirements:Assistance:Self-Help Assistance should be Embeddable #

<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}


</callout>


## Requirement ##



<data requirement  #SREQ-cuvw0>
  Guid: bcee0787-b805-411f-9302-5182bb8f0d81
  Id: SREQ-cuvw0
  Title: Self-Help Assistance SHOULD be embeddable.
  Tags: [Assistance] [HelpService]
  Stakeholders: [Users], [Customer Support Services]
  Statement [wiki]: **Requirement:**\\ The Self-Help `AssistanceService` `SHOULD` be able able to be embedded within a dedicated site *and* a corporate branded site.\\ \\ **Rational:**\\ For usability reasons, it's important to improve navigability by keeping branding/chrome consistent.\\ Users should be able to navigate to `http:\\support.app.site.corp.com\` as well as get to the same help via a corporate support url (eg: `http://support.site.corp.com/app/`) \\ \\ **Context**:\\ General.\\ \\ **Impact:**\\ \\ **Comments:**\\ Organisations often already have a designated url from which they deliver help. The management of this system is usually outside the control of the individual application's development teams control. The information quickly become stale and/or too expensive to upkeep, and therefore can become stale. The solution is to allow for the same data to be managed by the app development team, but embeddable and visible within the central help service.\\ \\ Too often, developers create Websites, and Systems rather than Services, limiting choice of delivery over the decade that an average system is required. Keep in flexible. \\ \\
</data>