Specification of non-functional requirements for contract specification in the NGOSS framework for quality management and product evaluation

12Citations
Citations of this article
31Readers
Mendeley users who have this article in their library.
Get full text

Abstract

The community of Operation Support Systems (OSS) for telecom applications defined a set of fundamental principles, processes, and architectures for developing the Next Generation OSS through the TeleManagement Forum TMF. At the heart of NGOSS lies the notion of a "Contract" which embodies the specification of services offered by an OSS component for quality management and product evaluation. However, TMF does not provide any method (or process) for specification of the non-functional part in the NGOSS contract specification. In this paper, we develop a systematic approach for specifying non-functional requirements of telecom OSS applications for contracts in the NGOSS framework for quality management and evaluation. Specifically, two categories of non-functional specification techniques are explored: qualitative and quantitative. Furthermore, we introduce two quantitative non-functional requirements specification methods: crisp and elastic to expand the capability of the current NGOSS contract specification method since only qualitative non-functional specification is currently available from TMF. © 2007 IEEE.

Cite

CITATION STYLE

APA

Liu, X., Azmoodeh, M., & Georgalas, N. (2007). Specification of non-functional requirements for contract specification in the NGOSS framework for quality management and product evaluation. In Proceedings - ICSE 2007 Workshops: 5th International Workshop on Software Quality, WoSQ 2007 (pp. 7–12). IEEE Computer Society. https://doi.org/10.1109/WOSQ.2007.12

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free