Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Next steps of cross-cutting requirements work (inc. compatibility and reviews of building block specs)

https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements/5-cross-cutting-requirements

https://datatracker.ietf.org/doc/html/rfc2119

https://datatracker.ietf.org/doc/html/rfc8174

development, deployment, architecture, quality, security, data

REQUIRED, RECOMMENDED, DRAFT, DEPRECATED

required, expected, recommended, draft, deprecated

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="cfr.xsl"?>
<cross-functional-requirements>
	<requirement>
		<category>development</category>
		<en>
			<rule>This is a requirement</rule>
			<additional>
				...
			</additional>
		</en>
		<level>REQUIRED</level>
		<reference>1</reference>
	</requirement>
	<requirement>
		...
	<requirement>
	...
</cross-functional-requirements>

Creation of GovStack overarching terminology

https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/3-terminology

Other issues raised

  • No labels