In this chapter, the following content will be discussed: Relational databases, structured query language (SQL), database systems, database access from programming languages. | Requirements Validation and Management Lecture-24 Recap 2 Validation process Review team membership Review checklist Validating requirements Prototyping Preparing user manual Model checking Preparing tests Today’s lecture 3 Requirements validation Requirements management Hard-to-test requirements System requirements Requirements which apply to the system as a whole. In general, these are the most difficult requirements to validate irrespective of the method used as they may be influenced by any of the functional requirements. Tests, which are not executed, cannot test for non-functional system-wide characteristics such as usability. Exclusive requirements These are requirements which exclude specific behaviour. For example, a requirement may state that system failures must never corrupt the system database. It is not possible to test such a requirement exhaustively. Some non-functional requirements Some non-functional requirements, such as reliability requirements, can only be tested | Requirements Validation and Management Lecture-24 Recap 2 Validation process Review team membership Review checklist Validating requirements Prototyping Preparing user manual Model checking Preparing tests Today’s lecture 3 Requirements validation Requirements management Hard-to-test requirements System requirements Requirements which apply to the system as a whole. In general, these are the most difficult requirements to validate irrespective of the method used as they may be influenced by any of the functional requirements. Tests, which are not executed, cannot test for non-functional system-wide characteristics such as usability. Exclusive requirements These are requirements which exclude specific behaviour. For example, a requirement may state that system failures must never corrupt the system database. It is not possible to test such a requirement exhaustively. Some non-functional requirements Some non-functional requirements, such as reliability requirements, can only be tested with a large test set. Designing this test set does not help with requirements validation. Key points Requirements validation should focus on checking the final draft of the requirements document for conflicts, omissions and deviations from standards. Inputs to the validation process are the requirements document, organisational standards and implicit organisational knowledge. The outputs are a list of requirements problems and agreed actions to address these problems. Reviews involve a group of people making a detailed analysis of the requirements. Review costs can be reduced by checking the requirements before the review for deviations from organisational standards. These may result from more serious requirements problems. Key points Checklists of what to look for may be used to drive a requirements review process. Prototyping is effective for requirements validation Systems models may be validated by paraphrasing them. This means that they are systematically translated into a .
