Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
IEEE Software
Metrics for requirements engineering
Selected papers of the sixth annual Oregon workshop on Software metrics
Standards, Guidelines and Examples: System and Software Requirements Engineering
Standards, Guidelines and Examples: System and Software Requirements Engineering
Exploring Requirements: Quality Before Design
Exploring Requirements: Quality Before Design
IEEE Software
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment
IEEE Transactions on Software Engineering
Survivability—a new technical and business perspective on security
Proceedings of the 1999 workshop on New security paradigms
Managing Software Development for Survivable Systems
Annals of Software Engineering
Requirements Definition for Survivable Network Systems
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Managing quality requirements using activity-based quality models
Proceedings of the 6th international workshop on Software quality
Designing for privacy in a multi-agent world
AAMAS'02 Proceedings of the 2002 international conference on Trust, reputation, and security: theories and practice
Reusing security requirements using an extended quality model
Proceedings of the 2010 ICSE Workshop on Software Engineering for Secure Systems
Editorial: Using ontologies with UML class-based modeling: The TwoUse approach
Data & Knowledge Engineering
Measuring software reliability: a fuzzy model
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
Quality improvement such as increased reliability and maintainability are of utmost importance in software development. In this field, which was previously ad hoc and unpredictable rather than customer‐oriented, increasing competition and focus on customer satisfaction have motivated management to put more emphasis on quality issues. This paper provides insight in techniques for dealing with what customers call generic quality attributes and what software engineers call nonfunctional requirements. Since requirements management more than many other disciplines in software engineering need practical insight, examples are provided for dealing with four nonfunctional requirements in large telecommunication systems, namely performance, usability, reliability, and maintainability. Guidelines are presented for specifying, constructing, analyzing, measuring and tracing nonfunctional requirements. Many examples from telecommunication system development show how to specifically and pragmatically deal with nonfunctional requirements. Extracts from three common standards (SEI CMM, ISO 9000–3, BELLCORE suite) are added in the form of a checklist for underlining the importance of proper requirements management from a customer viewpoint.