1 Scope
1.1 Motivation
1.2 Document organization
2 References
3 Definitions
4 Abbreviations and acronyms
5 Scope of URN
5.1 What is URN?
5.2 What is URN-NFR?
5.3 Why goal-oriented requirements engineering?
5.4 What is URN-FR?
5.5 Intended usage
6 Language requirements for URN-NFR
6.1 Expressing tentative, ill-defined and ambiguous requirements
6.2 Clarifying, exploring, and satisficeing goals and requirements
6.3 Expressing and evaluating measurable goals and NFRs
6.4 Argumentation
6.5 Linking high-level business goals to system requirements
6.6 Multiple stakeholders, conflict resolution and negotiation
support
6.7 Requirements prioritization
6.8 Requirements creep and churn and other evolutionary forces
6.9 Integrated treatment of functional and non-functional requirements
6.10 Multiple rounds of commitment
6.11 Life-cycle support
6.12 Traceability
6.13 Ease of use and precision
6.14 Modularity
6.15 Reusable requirements
6.16 Performance indicators
7 Language requirements for URN-FR
7.1 System trigger and termination conditions
7.2 System operations and responses
7.3 Complex and lengthy behaviour
7.4 Relationships among scenarios
7.5 Scenario cancellation and failure handling
7.6 Time-dependent behaviour
7.7 Component definition
7.8 Environment specification
8 Other language requirements for URN
8.1 Requirements traceability
8.2 Requirements test case specification
8.3 Evaluation of goal and NFR satisfaction
8.4 Performance analysis of requirements
8.5 Change management
8.6 Concrete representations
8.7 Usability
8.8 Extensibility
9 Language requirements summary
9.1 Requirements table format
9.2 URN requirements table
Appendix I – Requirements engineering activities
Appendix II – Guidelines for the maintenance of URN
II.1 Maintenance of URN
II.2 Rules for maintenance
II.3 Change request procedure
Bibliography