Software Requirements Mode Read Note four

First, the data entity demand pattern. is divided into data type, identifier, data structure, calculation formula, data archiving, data life Six kinds of demand mode.

Mode Name,	Live Entities	Transaction	Configuration	Chronicle	Information storage Infrastructure
Related patterns (patterns associated with them)	Data type, structure, configuration	Data structure, datatype	Data types, data structures, live entities	Transaction
Expected frequency (expected frequency of use)	50% of all requirements	Typically less than 10	10% of total demand	Between one and 20 of them.
Applicability	Establish an entity where information needs to be preserved and has a lifespan	Define an event in a live entity or enter the function of a transaction	Define parameter values to control how the system works	Some or some of the events that must be recorded in a system's life.
Content (what nouns are included in the pattern, and what are the basic concepts)	Entity name, explanation of entity, how entity is uniquely determined, details of parent entity	Trade name, interpretation of the transaction, information contained in the transaction, how a transaction is uniquely determined, all entity details, when the transaction is considered to have occurred, the life of the transaction	Configuration value, configuration entity, name and destination, representative value, data type, level, configuration value when you can modify	Record the type of event, information recorded for each thing, severity
Development considerations	Some of the topics discussed in the additional requirements, even if no universal requirements are defined, are worth considering	It's never going to change after a deal happens.	Consider the impact of the system modifying configuration values at run time	Performance considerations, taking into account the possible number of each event
Test considerations	For each live entity check add modify delete and query function	Note the statement of the time when a transaction was identified.	Basically the same as the entity, but to check the effect after changing the entity	Record system activities as much as possible

Software Requirements Mode Read Note four