"$# ! Survey and analysis research on verification and validation of requirements and architecture level specifications. Requirement specification is one of the first and most important stages of the software development. Errors introduced at this stage often turn out to be the costliest and most difficult to find and recover. Additionally, accurate requirement specification also helps increase the efficiency of software product design and verification stages. Hence, verification and validation of requirements and architecture level specifications is essential for prevention of major errors in the product development life cycle. There are several methods and tools for requirement level verification and validation and architecture specification in the existing literature. Requirement level verification and validation include analyzing software requirements to determine if they are consistent with, and within the scope of, system requirements, assuring that the requirements are testable and capable of being satisfied. These methods can be classified based on different criteria such as executable and non-executable methods, formal and informal methods etc. At the same time, a classification of requirement specifications into different categories can also be found in the existing literature. I propose to comprehensively study and analyze the classification of software requirement specifications and various methods used in verifying and validating them. I would try to analyze the relative performance of these methods for each of these requirement specification types. I would then propose a formal verification and validation method for a certain taxonomy of requirement specifications. Some of the methods and tools that I currently plan to analyze include: 1. SCR method 2. Verification and Specification of requirements by 'STATEMATE' 3. N-Fold inspection 4. Measuring consensus etc.I would add more methods and tools to my analysis after further search of the existing literature. I would first analyze the taxonomy of requirement specification methods for several types of requirements such as user requirements, system requirements, software requirements, functional requirements, non-functional requirements, domain requirements etc.After analyzing the classification of the software requirement specification methods, I would then propose a boundary between the software requirement specification and the design specification. After identifying different requirement specification types and and the boundary between the specification and design, I would analyze which verification and validation methods can be applied to each type of the specifications. Finally, I would select a taxonomy of requirement specification and then propose a formal method for verification and validation of that taxonomy of requirement specification. The expected result of the project would be selecting a taxonomy of requirements and defining a formal method of verification and validation for that taxonomy of requirements. The efficiency of the proposed formal method would be measured and verified by a set of software developers who will be using the method in the requirement phase of software development life cycle and measuring how the method has improved the efficiency of their software development. 1) Study and analysis of the taxonomy of software requirements. [1 Weeks] [10/10/08 - 10/16/08] 2) Defining a boundary between requirement phase and design phase. [3 Days] [10/17/08 - 10/19/08] 3) Study and analysis of different verification and validation methods for the for taxonomy of the requirements. + Progress Report [2 Weeks] [10/19/08 - 11/02/08] 4) Selecting a classification of requirements and proposing a formal method for verification and validation of requirements and system level architecture.[2 weeks] [11/02/08 - 11/17/08] 5) Verifying the efficiency of the formal method by developers consensus [1 Week] [11/17/08 - 11/24/08] 6) Final project report preparation, submission & Presentation. [1 Week] [11/24/08 - 12/01/08] 1. A.T. Bahill and S.J. Henderson, Requirements development, verification and validation exhibited in famous failures, Syst Eng 8(1) (2005), 1-14. 2. C. Heitmeyer, M. Archer, R. Bharadwaj, and R. Jeffords. Tools for constructing requirements specifications: The SCR toolset at the age of ten. Computer Systems Science and Engineering, 20(1):19–35, January 2005. 3. C. Heitmeyer, J. Kirby, B. Labaw, M. Archer, and R. Bharadwaj. Using abstraction and model checking to detect safety violations in requirements specifications. IEEE Trans. on Softw. Eng., 24(11), November 1998. 4. W. Yu, Verifying Software Requirements — a Requirement Tracing Methodology and Its Software Tool — RADIX, IEEE J. Selected Areas in Comm., Feb. 1994, pp. 234-240. 5. A. Gargantini and C. Heitmeyer. Automatic generation of tests from requirements specifications. In Proc. ACM 7th Eur. Software Eng. Conf. and 7th ACM SIGSOFT Symp. on the Foundations of Software Eng. (ESEC/FSE99), Toulouse, FR, September 1999. 6. Steve M. Easterbrook, Robyn R. Lutz, Richard Covington, John Kelly, Yoko Ampo, and David Hamilton. Experiences using lightweight formal methods for requirements modeling. IEEE Trans. Software Eng., 24(1):4–14, 1998. 7. Ramesh Bharadwaj and Constance Heitmeyer. Model checking complete requirements specifications using abstraction. Automated Software Engineering, 6(1), January 1999. 8. S. P. Miller, M. P. Heimdahl, and A. Tribble. Proving the shalls. In Proceedings of FM 2003: the 12th International FME Symposium, September 2003. 9. W, M. Wilson, Writing effective requirements, http://satc.gsfc.nasa.gov/support/STC_APR97/write/writert.html 10. C. Heitmeyer, J. Kirby, B. Labaw. Tools for formal
View Full Document
Unlocking...