You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page contains service description outlining how and where service should be used, targeted users, service delivery model and service elements and topology.

RESPONSIBLE: Information provided in this page is initially populated by the development team (during the transition phase), and revised based on the need or in a yearly service check by service_name Service Manager, with exception of CBA which remains the responsibility of business development team.

Service description

Add brief description of the service, how and where service should be used,  typical or key use cases or scenarios (for various groups/levels of end users) and other relevant overview information

Users

Add definition of who are the targeted users, estimate about possible number of users etc.

Contacts

All operations, business development and stakeholders contacts

 

Service ManagerDeputy Service ManagerL1 supportL2 supportL3 support
     

Service delivery model

Add explanation about organisation of service delivery

Service Elements

Service Elements, with brief description and links to products, resource instances and software stack of the service, indicating the software components types - if they are internally (in-house) developed, OSS or commercial off-the-shelf softwareService elements can be grouped in two following categories:

Technology infrastructure

Add list and description of products and resources used to deliver main functionalities of the service. Add service technical architecture - i.e. its good to have a conceptual architectural diagram and topology diagram.

Supporting infrastructure

Add list and descriptions of products and resources used to deliver supporting services such as specialized monitoring and measuring systems, configuration management system, issue/ticket reporting system, etc.)

Cost Benefit Analysis

Provide URL to last valid CBA

  • No labels