Attributes Of Quality Scenarios/Scenario Sets Used In Software Requirements Elicitation.
Abstract
In order for a quality software product to be developed, quality must exist from the beginning. One of the first stages in software development is requirements gathering. Scenarios help bring together the stakeholders of the future system to discuss and agree upon the requirements of the proposed system. This thesis examines scenarios used in software requirements elicitation. Many different definitions, formats, and ideas exist on scenarios, but no thorough work has been done on what makes a good, quality scenario and scenario set. This thesis will define quality for a scenario and scenario set. Research into the current state of practice of scenarios will reveal any references authors make with respect to quality attributes they want in their scenarios. Since the result of requirements elicitation is the Software Requirements Specification (SRS), research into what makes a quality SRS will inspire ideas for a quality scenario and scenario set. New, previously unmentioned attributes, generated from fresh, new thinking on the subject will round out the quality attribute list for scenarios and scenario sets that this thesis develops. Each attribute will be defined, justified, and examples shown of what a scenario or scenario set would be like if the attribute was missing and how the scenario or scenario set would be improved if the attribute were included. Although this paper does not claim to prove the resulting attribute list is sufficient for a quality scenario and scenario set, it will show the necessity of each attribute. Showing how the software lifecycle or other software development functions will be adversely affected if an attribute is missing will prove necessity.
Document Details
- Document Type
- Technical Report
- Publication Date
- Dec 02, 1997
- Accession Number
- ADA332328
Entities
People
- Kimberly A. Braun
Organizations
- Air Force Institute of Technology