PL EN


Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników
Tytuł artykułu

Method of non-functional requirements balancing during service development

Identyfikatory
Warianty tytułu
Języki publikacji
EN
Abstrakty
EN
Today, the list of telecom services, their functionality and requirements for Service Execution Environment (SEE) are changing extremely fast. Especially when it concerns requirements for charging as they have a high influence on business. This results in the need for constant adaptation and reconfiguration of Online Charging System (OCS) used in mobile operator networks. Moreover any new functionality requested from a service can have an impact on system behavior (performance, response time, delays) which are in general nonfunctional requirements. Currently, this influence and reconfiguration strategies are poorly formalized and validated. Current state-of-the-art approaches are considered methodologies that can model non-functional or functional requirements but these approaches don’t take into account interaction between functional and nonfunctional requirements and collaboration between services. All these result in time and money consuming service development and testing, and cause delays during service deployment. The balancing method proposed in this paper fills this gap. It employs a well-defined workflow with predefined stages for development and deployment process for OCS. The applicability of this novel approach is described in a separate section which contains an example of GPRS service charging. A tool, based on this method will be developed, providing automation of service functionality influence on non-functional requirements and allowing to provide a target deployment model for a particular customer. The reduction of development time and thus necessary financial input has been proved based on real-world experiments.
Rocznik
Strony
50--57
Opis fizyczny
Bibliogr. 13 poz., rys.
Twórcy
autor
autor
autor
autor
Bibliografia
  • [1] 3GPP TS 32.296 Online Charging System (OCS): Application and interfaces, 88 p.
  • [2] Abdukalykov R., Hussain I., Kassab M., Ormandjieva O.: Quantifying the Impact of Different Non-functional Requirements and Problem Domains on Software Effort Estimation. 9th International Conference on Software Engineering Research, Management and Applications (SERA), 2011
  • [3] National Institute of Standards and Technology: Software Errors Cost U.S. Economy $59.5 Billion Annually (NIST 2002-10). http://www.nist.gov/public_affairs/releases/n02-10.htm (2002).
  • [4] Lindstrom D.R.: Five Ways to Destroy a Development Project. IEEE Software, September 1993, pp. 55-58.
  • [5] Boehm B., In H.: Identifying Quality-Requirement Conflicts. IEEE Software, March 1996, pp. 25-35.
  • [6] Breitman K. K., Leite J.C.S.P., Finkelstein A.: The World's Stage: A Survey on Requirements Engineering Using a Real-Life Case Study. Journal of the Brazilian Computer Society No. 1, Vol. 6, Jul. 1999, pp. 13-37.
  • [7] Chung L.: Representing and Using Non-Functional Requirements: A Process Oriented Approach. Ph.D. Thesis, Dept. of Comp. Science. University of Toronto, June 1993. Also tech. Rep. DKBS-TR-91-1.
  • [8] Chung L., Nixon B. A., Yu E., Mylopoulos J.: Non-Functional Requirements in Software Engineering, Kluwer Academic Publishers, Boston, 2000.
  • [9] http://www.info.ucl.ac.be/research/projects/AVL/ReqEng.html
  • [10] http://www.objectiver.com/
  • [11] Quan Tran: NFR-Assistant: tool support for achieving quality, Application-Specific Systems and Software Engineering and Technology, 1999. ASSET '99. Proceedings. 1999 IEEE Symposium.
  • [12] http://www.softwareag.com/corporate/products/aris_platform/default.asp
  • [13] Page A., Johnston K., Rollison B.: How We Test Software at Microsoft, Microsoft Press – December 10, 2008, 448 p.
Typ dokumentu
Bibliografia
Identyfikator YADDA
bwmeta1.element.baztech-article-BPS3-0025-0127
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.