Тестирование спецификаций

Editor's Notes

• #12: 1. Validate requirements against objectives. Compare the objectives, which describe why the project is being initiated, to the requirements, which describe what is to be delivered. The objectives define the success criteria for the project. If the what does not match the why, then the objectives cannot be met, and the project will not succeed. If any of the requirements do not achieve the objectives, then they do not belong in the project scope.2. Apply scenarios against requirements. Apply scenarios against requirements. A scenario is a task oriented users’ view of the system. The individual requirements, taken together, must be capable of satisfying any scenario; otherwise the requirements are incomplete.3. Perform an initial ambiguity review. An ambiguity review is a technique for identifying and eliminating ambiguous words, phrases, and constructs. It is not a review of the content of the requirements. The ambiguity review produces a higher quality set of requirements for review by the rest of the project team.4. Perform domain expert reviews. The domain experts review the requirements for correctness and completeness.5. Create Cause-Effect Graph. The requirements are translated into a Cause-Effect Graph, which provides the following benefits:o It resolves any problems with aliases (i.e., using different terms for the same cause or effect).o It clarifies the precedence rules among the requirements (i.e., what causes are required to satisfy what effects).o It clarifies implicit information, making it explicit and understandable to all members of the project team.o It begins the process of integration testing. The code modules eventually must integrate with each other. If the requirements that describe these modules cannot integrate, then the code modules cannot be expected to integrate. The cause-effect graph shows the integration of the causes and effects.o Cause-Effect Graphs may look intimidating on the surface. They would appear to need someone with a formal logic background or electricalengineering background to create them. However, all you need to know to build them is the definition of “AND”, “OR”, and “NOT”. If you are in thesoftware profession and unsure of these three terms then it is time for a career change.6. Logical consistency checks performed and test cases designed by BenderRBT tool.The tool identifies any logic errors in the cause-effect graph. The output from the tool is a set of test cases that are 100 percent equivalent to the functionality in the requirements.7. Review of test cases by requirements authors. The designed test cases are reviewed by the requirements authors. If there is a problem with a test case, the requirements associated with the test case can be corrected and the test cases redesigned.8. Validate test cases with the users/domain experts. If there is a problem with the test case, the requirements associated with it can be corrected and the test case redesigned. The users/domain experts obtain a better understanding of what the deliverable system will be like. From a Capability Maturity Model® IntegrationSM (CMMISM) perspective, you are validating that you are building the right system.9. Review of test cases by developers. The test cases are also reviewed by the developers. By doing so, the developers understand what they are going to be tested on, and obtain a better understanding of what they are to deliver so they can deliver for success.10. Use test cases in design review. The test cases restate the requirements as a series of causes and effects. As a result, the test cases can be used to validate that the design is robust enough to satisfy the requirements. If the design cannot meet the requirements, then either the requirements are infeasible or the design needs rework.11. Use test cases in code review. Each code module must deliver a portion of the requirements. The test cases can be used to validate that each code module delivers what is expected.12. Verify code against the test cases derived from requirements. The final step is to build test cases from the logical test cases that have been designed by adding data and navigation to them, and executing them against the code to compare the actual behavior to the expected behavior. Once all of the test cases execute successfully against the code, then it can be said that 100 percent of the functionality has beenverified and the code is ready to be delivered into production. From a CMMI perspective, you have verified that you are building the system right.
• #17: The document conforms to the standard template.The document has been spell-checked.The author has visually examined the document for any layout errors.Any predecessor or reference documents that the inspectors will require to examine the document are available.Line numbers are printed on the document to facilitate referring to specific locations during the inspection meeting.All open issues are marked as TBD (to be determined).The moderator didn't find more than three major defects in a ten-minute examination of a representative sample of the document.___All issues raised during the review have been addressed.Any changes made in the document and related work products were made correctly.The revised document has been spell-checked.All TBDs have been resolved, or each TBD's resolution process, target date, and owner has been documented.The document has been checked into the project's configuration management system
• #23: Intelligent Process Control (IPC) System for the board production technological process, based on the expert system