Table of Contents
1Scope
1.1Motivation
1.2Documentorganization
2References
3Definitions
4Abbreviationsandacronyms
5ScopeofURN
5.1WhatisURN?
5.2WhatisURN-NFR?
5.3Whygoal-orientedrequirementsengineering?
5.4WhatisURN-FR?
5.5Intendedusage
6LanguagerequirementsforURN-NFR
6.1Expressingtentative,ill-definedandambiguous
requirements
6.2Clarifying,exploring,andsatisfyinggoalsand
requirements
6.3ExpressingandevaluatingmeasurablegoalsandNFRs
6.4Argumentation
6.5Linkinghigh-levelbusinessgoalstosystemrequirements
6.6Multiplestakeholders,conflictresolutionand
negotiationsupport
6.7Requirementsprioritization
6.8Requirementscreepandchurnandotherevolutionaryforces
6.9Integratedtreatmentoffunctionalandnon-functional
requirements
6.10Multipleroundsofcommitment
6.11Life-cyclesupport
6.12Traceability
6.13Easeofuseandprecision
6.14Modularity
6.15Reusablerequirements
7LanguagerequirementsforURN-FR
7.1Systemtriggerandterminationconditions
7.2Systemoperationsandresponses
7.3Complexandlengthybehaviour
7.4Relationshipsamongscenarios
7.5Componentdefinition
7.6Environmentspecification
8OtherlanguagerequirementsforURN
8.1Requirementstraceability
8.2Requirementstestcasespecification
8.3Performanceanalysisofrequirements
8.4Changemanagement
8.5Concreterepresentations
8.6Usability
9Languagerequirementssummary
9.1Requirementstableformat
9.2URNrequirementstable
AnnexA-CompliancetothisRecommendation
AppendixI-Requirementsengineeringactivities
AppendixII-GuidelinesforthemaintenanceofURN
II.1MaintenanceofURN
II.2Rulesformaintenance
II.3Changerequestprocedure
Bibliography Abstract
Defines URN (User Requirements Notation) for describing user requirement as goals and scenarios in a formal way without any reference to implementation mechanisms and with optional dependency on component specification.
