• strict warning: Non-static method view::load() should not be called statically in /home/universe120/www/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/universe120/www/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/universe120/www/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter_node_status::operator_form() should be compatible with views_handler_filter::operator_form(&$form, &$form_state) in /home/universe120/www/sites/all/modules/views/modules/node/views_handler_filter_node_status.inc on line 14.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/universe120/www/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/universe120/www/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.

New report available! Synthesis of use case requirements, release 2 (Deliverable D4.2)

News date: 
Fri, 2012-04-13

The UniverSelf project is proud to announce the final release of the technical report on use case requirements:

Deliverable D4.2 - Synthesis of use case requirements - release 2.

The report can be accessed under the Dissemination/Technical Reports section, or directly at the following link http://www.univerself-project.eu/technical-reports



This report provides a consolidated synthesis of the requirements related to the use cases defined in WP4 “Deployment and Impact”.

Specifically, the preliminary requirements (initially as reported in the report D4.1 [1]) have been refined, in some cases extended, and prioritized by using the Quality Function Deployment(QFD) methodology.

Deliverable D4.2 is also reporting the lessons learnt in eliciting the future networks management requirements, the internal project use (mainly towards the work of WP2, WP3 and other tasks of WP4) and external exploitation, mainly towards the standardization activities.

In the UniverSelf project, a use case is a descriptor of a (set of) precise problem(s) to be solved, in a given technological context. The role of the use case is to formally identify, clarify, and organize both requirements and modelling of the system to be designed; the implementation and evaluation of the designed solution will then validate the resolution of the problem(s) addressed by the use case.

Use cases definition started from the three reference scenarios identified during the project proposal preparation, i.e. Scenario 1 - Operators’ Service and Data Management, Scenario 2 - SON for Radio Access and Core Networks, and Scenario 3 - Future Internet Services Management and Network Resource Optimization.

The use cases are:

  1. Self-diagnosis and self-healing for IMS VoIP and VPN services
  2. Network Stability and Performance
  3. Dynamic Virtualization and Migration of Contents and Servers
  4. SON and SON Collaboration according to Operator Policies
  5. Network Morphing (use case #5 has been merged with use case #6)
  6. Operator-governed, End-to-end, Autonomic, joint Network and Service Management
  7. Network and Services Governance

Main achievements reported in this deliverable include:

  • The telecommunication industry perspective, based on the views of the project industrial partners, in terms of what are the technical and business problems that the ICT industry is willing to solve thanks to the development and adoption of UMF and Network Empowerment technologies developed in the context of UniverSelf;
  • A detailed list, an analysis and a synthesis of the functional, non-functional and business requirements of the six use cases;
  • Some considerations on how this process of use case requirements expression and analysis have been (and are being continuously) exploited within the project activities (e.g. with particular reference to the work package 2 and work package 3) and towards relevant standardization bodies, are also given.
  • QFD analysis has also attracted the interest of WP4-Task 4.3 (Impact Analysis). Applicability of such methodology to business requirements and standard business (model) choices could be very useful in determining which problems and requirements would be the most essential from a business perspective and on which business aspects the system will have an impact given the current set of problems and requirements. Specifically Task 4.3 linked QFD methodology to a fixed set of business modelling choices for future-internet systems, namely the twelve parameters provided in the business model configuration matrix by [11]. Results of this work will be presented in Deliverable 4.7 (Analysis of the impact of deployment of autonomic networking functionalities).