On Non-Functional Requirements in Software Engineering
- 1 January 2009
- book chapter
- other
- Published by Springer Science and Business Media LLC in Lecture Notes in Computer Science
Abstract
No abstract availableKeywords
This publication has 31 references indexed in Scilit:
- MOQARE: misuse-oriented quality requirements engineeringRequirements Engineering, 2007
- Guest editorial: 10th anniversary workshop on Requirements Engineering: Foundation for Software Quality (REFSQ’2004)Requirements Engineering, 2005
- Nonfunctional requirements: from elicitation to conceptual modelsIEEE Transactions on Software Engineering, 2004
- Misuse cases help to elicit non-functional requirementsComputing & Control Engineering Journal, 2003
- Towards requirements-driven information systems engineering: the Tropos projectInformation Systems, 2002
- Rationale-Based Use Case SpecificationRequirements Engineering, 2002
- A Scenario Construction ProcessRequirements Engineering, 2000
- A reference model for requirements and specificationsIEEE Software, 2000
- Functional documents for computer systemsScience of Computer Programming, 1995
- Representing and using nonfunctional requirements: a process-oriented approachIEEE Transactions on Software Engineering, 1992