Chapter 7. Data Entity Requirement Patterns
In this chapter:
7.1 Living Entity Requirement Pattern 129
7.2 Transaction Requirement Pattern 133
7.3 Configuration Requirement Pattern 138
7.4 Chronicle Requirement Pattern 144
7.5 Information Storage Infrastructure 154
Builders of systems tend to take a cavalier and ad hoc attitude to information: we lack rules for when data can be deleted; we’re relaxed about losing data; we permit data to be modified without retaining a record of what it was before; we don’t know who did what; we can’t tell how amounts were calculated. It’s hardly surprising that so many systems handle data in a sloppy and messy manner. This chapter aims to impose some order and consistency, by introducing a scheme for dividing all data ...
Get Software Requirement Patterns now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
