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 6 Next »

RequirementDesign Constraints
Section3.4
JIRA Tasks
EIR-42 - Getting issue details... STATUS

Introduction

Resolve Before Publication

Section Under Consideration

This should specify design constraints that can be imposed by other standards, hardware limitations, etc. [IEEE830-1998, Section 5.3.5, pg 17]

Target

5.3.5.1 Standards compliance

This subsection should specify the requirements derived from existing standards or regulations. They may
include the following:

	a) Report format;
	b) Data naming;
	c) Accounting procedures;
	d) Audit tracing.

For example, this could specify the requirement for software to trace processing activity. Such traces are
needed for some applications to meet minimum regulatory or financial standards. An audit trace requirement
may, for example, state that all changes to a payroll database must be recorded in a trace file with before and
after values.
  • No labels