Date of Award
Spring 2011
Access Restriction
Campus Access only Research Projects
Degree Name
Master of Science
Department
Systems Engineering
School or College
Seaver College of Science and Engineering
Abstract
40% of all project failures are the result of inadequate requirement analysis; the end results do not fit the customer's desires. To combat this problem, the Department of Defense has instituted a new acquisition process necessitating that the requirements aspect of the program be examined earlier. It is more imperative than ever that programs deliver the right system. Verification of Use Cases (VUC) is a solid way to increase the odds that the customer wants are met. VUC has four main components: tracking system, requirements attached to respective use case, test cases built from use cases, and the subsystem requirement tested against the system requirement. The tracking system is a way to ensure the requirements, use cases and test cases are all linked. Regardless of the document, or phase of the program, an alphanumeric system is used, as the unique ID, linking the requirements, use cases, and test cases together.
The use case does not usually include the requirement, however with VUC it will. This way, regardless of the phase of the project or the personnel on the project, the use case can never be lost as it in the same document as the requirements. It is this document that is flowed down to the test engineers to use to build the test cases.
Using the scenarios of the use cases, the test cases are built and stored in a matrix. Each scenario will have at least one, if not more, test cases associated with it. This results in thorough test cases for each use case and linked requirement, increasing the likelihood that no part of the requirement is overlooked. The last phase of VUC takes the subsystems requirements and tests them back to their parent system test case, which was built from its respective use cases. This ensures that each subsystem meets the customer's expectations, getting the system closer to fulfilling its expected role and on budget and on schedule.
Recommended Citation
Bouldin, Shannon, "Verification of Use Cases" (2011). LMU/LLS Theses and Dissertations. 384.
https://digitalcommons.lmu.edu/etd/384
Oral Presentation
