Requirements templates and patterns

Templates and patterns for use in service initiatives

Templates for elements at the Application layer of the ArchiMate architectural framework:
Types of non-functional requirements that can be used when completing the Non-functional requirements (NFR) field in the before mentioned templates - depending on the template, different types of NFR will matter.
Types of project issues that can be used when completing the Project Issues (PI) field in the before mentioned templates - depending on the template, different types of PI will matter.
Techno Order (Ens Dictionary): artefacts for use in a Collaborative Planning Methodology (Interaction Dictionary) at different levels of scope.
For guidance on identifying and modelling event complexes, see event.

Role navigator (Actor Atlas): some background for a range of possible stakeholder roles that could be assumed by stakeholders described in a Stakeholder template.
Regulations navigator (Actor Atlas): a page with links to a range of regulations to which business collaborations should comply (ref. non-functional requirement of type 17 (Legal Requirements)).
Federal Enterprise Architecture (FEA), with a summary (Ens Dictionary) of its reference models and levels of scope.
A summary description (Ens Dictionary) of layers, aspects and model elements of ArchiMate® 2.1.

Volere: http://www.volere.co.uk/
EMPRESS (ITEA): Framework for Requirements, Deliv. 3.1 (N. Heumesser, editor), April 5 2004.
COMET_Method_v2-4 COMET (Component and Model-based Development Methodology)

The backlinks below usually do not include the child and sibling items, nor the pages in the breadcrumbs.