"Software requirement Mode" Reading notes 04

In the process of system development, developers often treat information with contempt and random attitude, in order to solve the problem that many systems deal with the data in a so-so way, we need a solution-data entity requirement pattern. The scheme divides all entities into several fixed categories, sharing many important features, with the aim of imposing some order and consistency. The requirements patterns in the data entity domain include: Data entities (live entities, transactions, configurations, chronicles), and information storage. The live entity demand pattern is used to define an entity whose information needs to be saved and has a life expectancy (that is, it can be built, can be modified several times, and eventually terminated). Its content must include at least: the entity name, the entity's interpretation, the entity contains the information, the entity is uniquely determined by the way, the parent entity's details; Additional requirements are: Edit function, query function, modify history, public data, just tombstone. A trading requirement pattern is a function that defines an event in the life of a living entity, and/or enters such a transaction. Its contents include: The name of the transaction, the interpretation of the transaction, the information contained in the transaction, how a transaction is uniquely determined, the owner's live entity details, when the transaction is considered to have occurred, and the life of the transaction. In the process of development, we should pay attention to, that is, once the transaction occurs, its data will never be modified. The configuration requirements pattern is used to define parameter values and control how the system operates. There are two ways to organize your configuration needs: 1. Define a configuration value (name and purpose, Representative value, data type, level, when the configuration value can be modified), and then describe the level at which it is located; 2. Define the configuration entity (entity name, the purpose of the entity, entity content, how the entity is uniquely determined, when the entity can It forms part of the configuration. Chronicle requirement patterns are used to define some or some of the events that must be recorded in the system's life. A chronicle requirement should include: The type of thing recorded, the information it records, the severity; Additional requirements are: Access control, public Chronicle feature, Chronicle view function, severity level, purge Chronicle, Archive Chronicle, trigger other action, turn chronicle record on or off. The information storage infrastructure is used for the permanent preservation of information.

The functionality of          users is colorful, so it is difficult to find common ground to classify them, and it is worthwhile to write demand patterns for it. In the book "Software Requirements Model", we understand some of them: Query mode and report mode. The query demand mode is used to define the screen display function that is displayed to the user for the specified information. Define a query requirement you should specify the following information: query name, business intent of the query, displayed information, sort order, selection criteria, browsing, interaction, automatic refresh Additional requirements are: 1. Comprehensive queries, in order to prevent having to define a query for every trivial information, define some broad-covering needs, and deal with things that may be forgotten; 2. Public query characteristics, if there are rules that apply to all queries, are defined once, and can be applied to the entire system. At development time, we should be careful to check whether information is available, consider whether there are potential performance issues and whether automatic self-refresh is easy to implement in the expected user interface environment. The report requirement mode is used to define a report that displays the specified information to the user, and the displayed information is not modified by the report. When you need to decide whether to display in a query or in the form of a report, The factors we need to consider are: 1. How much information to display, the display of multi-column information report may be better; 2. How to interact, the report is passive; 3. How often do you need a hard copy, a report should be used frequently; 4. How many people want to see, run a report to others more reliable; 5. If you need to save the results, the report is easier Where the information comes from, if the information is not from the database report the product may not be readable; 7. The degree of information instability, if the data frequently changes the copy of the report will quickly become obsolete; 8. It is cheaper to query or report. The reporting requirements pattern should specify the name of the report, the business intent of the report, the information displayed, the sort order, selection criteria, autorun details, the total level, and the page break level. The ease-of-use requirements model is used to define the ease with which a person with a disability or someone with a particular need is using the system, that is, how easy it is to use; Additional requirements include: general usability, specific needs steps, tailoring to fit one user, documentation and support, proof of consistency, availability. In order to develop the usability function, the software engineer should have the basic application knowledge in 3 fields: (1) The user's specific need range (2) is built into the operating system and other products and technologies in use (3) the types of some of the most important assistive technologies and the general concept of how they work. The user interface infrastructure is a set of related components that work together to interact with the system, and the reporting infrastructure is the one that generates reports for us and can often design new reports, important aspects to consider when implementing: report design tools, delivery mechanisms, chronicleInformation, access control, how recipients are notified, report content and format, report scheduling, reporting, backup, and maintenance of report infrastructure usage.

Software Requirements Mode reading notes