An analytic framework for specifying and analyzing imprecise requirements
Proceedings of the 18th international conference on Software engineering
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Nonfunctional Requirements: From Elicitation to Conceptual Models
IEEE Transactions on Software Engineering
A runtime-adaptable service bus design for telecom operations support systems
IBM Systems Journal
An introduction to network stack design using software design patterns
MACE'10 Proceedings of the 5th IEEE international conference on Modelling autonomic communication environments
| Hi-index | 0.00 |
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.