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.
M. Amoozdeh et al., "Specification of Non-Functional Requirements for Contract Specification in the NGOSS Framework for Quality Management and Product Evaluation," Proceedings of the 5th International Workshop on Software Quality (WoSQ'07), Institute of Electrical and Electronics Engineers (IEEE), Jul 2007.
The definitive version is available at https://doi.org/10.1109/WOSQ.2007.12
5th International Workshop on Software Quality (WoSQ'07)
Keywords and Phrases
contracts; formal specifications; quailty management; software quality; telecommunication computing
Article - Conference proceedings
© 2007 Institute of Electrical and Electronics Engineers (IEEE), All rights reserved.
16 Jul 2007