{section}
{column}
h1. Webconsole Functional Specification
This document describe several functional specification parts:
* Each functional aspect of Petals Webconsole features.
* What make the product in each conditions.
* Functional processes that need to be modeled.
{column}
\\
{column:width=350px}
{panel}{toc}\\ {panel}\\
{column}\\
{section}
h1. User connection
At the first glance the Petals Webconsole can have two differents scenarios, when user arrives at the
home page of the Webconsole.
h2. First scenario
+Condition:+ no server are saved in the webconsole.xml.
+State:+ The Webconsole haven't any declared server and is
in unconnected state and wait for a connection to a server.
{gliffy:name=User connection first scenario|align=left|size=L|version=2}
h2. Second scenario
+Condition:+ at least one server is defined in the webconsole.xml.
+State:+ The Webconsole have declared server in configuration file
and is in unconnected state and wait for a connection to a server.
{gliffy:name=User connection second scenario|align=left|size=L|version=1}
h1. Administrative tasks
This part present functionnal process of all administrative tasks such as:
* Start component
* Uninstall shared library
* Shutdown service assembly
* Ect ...
h2. Stop component scenario
+Condition:+ The focused component is in "Start" state
+State:+ The Webconsole have at least one declared server and is
in connected state and wait a "Stop" action on one component in
component list.
{gliffy:name=Stop component scenario|align=left|size=L|version=1}\\
Displayed error messages can be very different depending on the error that occurred.
For example an error can throw because the component isn't in the valid state to perform
the requested action such as: component is in _started_ state and you perform a _shutdown_
action. The previous case may be appear if the component state *isn't correctly synchronized*,
with *the current state* of the component on the node petals.
h2. Start component scenario
+Condition:+ The focused component is in "Stop" or "Shutdown" state
+State:+ The Webconsole have at least one declared server and is
in connected state and wait a "Start" action on one component in
component list.
{gliffy:name=Start_component_scenario|align=left|size=L|version=2}
h2. Shutdown component scenario
+Condition:+ The focused component is in "Stop" state
+State:+ The Webconsole have at least one declared server and is
in connected state and wait a "Shutdown" action on one component in
component list.
{gliffy:name=Shutdown_component_scenario|align=left|size=L|version=1}
h2. Uninstall component scenario
+Condition:+ The focused component is in "Shutdown" state
+State:+ The Webconsole have at least one declared server and is
in connected state and wait a "Uninstall" action on one component in
component list.
{gliffy:name=Uninstall_component_scenario|align=left|size=L|version=1}
{column}
h1. Webconsole Functional Specification
This document describe several functional specification parts:
* Each functional aspect of Petals Webconsole features.
* What make the product in each conditions.
* Functional processes that need to be modeled.
{column}
\\
{column:width=350px}
{panel}{toc}\\ {panel}\\
{column}\\
{section}
h1. User connection
At the first glance the Petals Webconsole can have two differents scenarios, when user arrives at the
home page of the Webconsole.
h2. First scenario
+Condition:+ no server are saved in the webconsole.xml.
+State:+ The Webconsole haven't any declared server and is
in unconnected state and wait for a connection to a server.
{gliffy:name=User connection first scenario|align=left|size=L|version=2}
h2. Second scenario
+Condition:+ at least one server is defined in the webconsole.xml.
+State:+ The Webconsole have declared server in configuration file
and is in unconnected state and wait for a connection to a server.
{gliffy:name=User connection second scenario|align=left|size=L|version=1}
h1. Administrative tasks
This part present functionnal process of all administrative tasks such as:
* Start component
* Uninstall shared library
* Shutdown service assembly
* Ect ...
h2. Stop component scenario
+Condition:+ The focused component is in "Start" state
+State:+ The Webconsole have at least one declared server and is
in connected state and wait a "Stop" action on one component in
component list.
{gliffy:name=Stop component scenario|align=left|size=L|version=1}\\
Displayed error messages can be very different depending on the error that occurred.
For example an error can throw because the component isn't in the valid state to perform
the requested action such as: component is in _started_ state and you perform a _shutdown_
action. The previous case may be appear if the component state *isn't correctly synchronized*,
with *the current state* of the component on the node petals.
h2. Start component scenario
+Condition:+ The focused component is in "Stop" or "Shutdown" state
+State:+ The Webconsole have at least one declared server and is
in connected state and wait a "Start" action on one component in
component list.
{gliffy:name=Start_component_scenario|align=left|size=L|version=2}
h2. Shutdown component scenario
+Condition:+ The focused component is in "Stop" state
+State:+ The Webconsole have at least one declared server and is
in connected state and wait a "Shutdown" action on one component in
component list.
{gliffy:name=Shutdown_component_scenario|align=left|size=L|version=1}
h2. Uninstall component scenario
+Condition:+ The focused component is in "Shutdown" state
+State:+ The Webconsole have at least one declared server and is
in connected state and wait a "Uninstall" action on one component in
component list.
{gliffy:name=Uninstall_component_scenario|align=left|size=L|version=1}