From OpenNMS

Scenario 1: Opening the service page

 1.User opens the services page http://127.0.0.1/opennms/services
 2.The following page is displayed.
   File:ServicesUI.pdf
 3.The user has options to start, stop, restart, refresh selected services. 

Scenario 2: Refresh Operation

 1.The user selects a few services and presses the refresh button.
 2.The services selected are ignored and the latest status is retrieved and presented.

Scenario 3: Start, Stop, Restart operations

 1.The use selects a few services and presses a restart button.
 2.The selected services are “acted upon”. If a service that is already started is asked to be started again,
     the request is ignored. Similar behavior is assumed for other actions.
   a.Start operation:
     1.For each selected service that is not started, a “start” message is sent to the service.
     2.For each selected service that is already in start state, the effect would be equivalent to ignoring
       the request.
   b.Stop operation:
     1.For each selected service that is stopped, a “stop” message is sent to the service.
     2.For each selected service that is already in “stop” state, the effect would be equivalent to ignoring 
       the request.
 3.Restart operation:
   a.For each service selected, this would be the equivalent of doing a stop operation followed by a start 
     operation.

Scenario 4: Inspection of properties/laundry list of certain services.

 1.Certain services have certain property lists. For example, “pollerd” has a property called “node list” 
   which lists the nodes to poll. Such services are shown with a hyper link on the services page. On 
   following the link, the properties held by the service are exposed (on a separate page).