Scenario-based prototyping for requirements identification
Authors: 
James W. Hooper, Pei HsiaAuthors Info & Claims
Pages 88 - 93
Abstract
The three major facets of software requirements engineering are: (1) requirements identification, (2) requirements analysis, and (3) requirements communication. Much research addresses the latter two aspects, but few practical approaches exist for addressing the first one. Hence, system requirements remains the most critical and problemprone area of system development. There is thus an urgent need for a methodology which helps a user identify requirements and realize potential impacts, in a timely manner.The objectives of this research are: (1) develop a methodology (and accompanying tools) to aid users in identifying requirements before building a system, and (2) evaluate the effectiveness of the methodology (and tools) in actual use.The novel approach of this research is an attempt to capture the conceptual system as visualized by the user, by use of operational examples ("scenarios"). By means of simulation and man-machine interface techniques, the scenarios may serve as a "quick and dirty" prototype of the intended system, providing the means for requirements analysis and validation, and for communicating the real intent of the requirements. It is anticipated that the methodology can be extended to fully support the concept of step-wise refinement and continuing system validation.
References
[1]
Ramamoorthy, C. V. and L. H. So, "Software Requirements and Specifications: Status and Perspectives." Tutorial: Software Methodology, IEEE Computer Society Catalog No. EH0142--0, November 1978.
[2]
Myers, G. J., Software Reliability: Principles and Practices. New York: Wiley-Interscience, 1976.
[3]
Scharer, L., "Pinpointing Requirements," Datamation, Vol. 27, No. 4, April 1981, 139--151.
[4]
Devorkin, D. B., and R. T. Oberndorf, A Survey of State-of-the-Field of Requirements Methodology, AD-A075227 DTIC Technical Report, May 1979, For U. S. Army Institute for Research in Management Information and Computer Science (AIRMICS), Atlanta, Ga.
[5]
FY 79-83 Research and Development Technology Plan, September 1977. R&D Technology Panel to the Mgt. Steering Committee for Embedded Computer Resources. Office of the Director of Defense Research and Engineering.
[6]
Alford, Mack W., "A requirements Engineering Methodology for Real-Time Processing Requirements,"IEEE Transactions on Software Engineering, Volume SE-3, No. 1, January 1977.
[7]
Alford, M. W., "Software Requirements Engineering Methodology (SREM) at the Age of Two," Proceedings of COMPSAC 78, IEEE Catalog No. 78CH1338--30, November 1978.
[8]
H6180/Multics/URL User's Manual, Volume 1, ISDOS Project, University of Michigan, Ann Arbor, MI, March 1977.
[9]
Belford, P. C., A. F. Bond, D. G. Henderson and L. S. Sellers, "Specifications: A Key to Effective Software Development," Proceedings of Second International Conference on Software Engineering, October 1976.
[10]
Nashman, A. E. and P. D. Cross, A Digital Systems Development Methodology. Computer Science Corporation, Falls Church, VA, 1978.
[11]
Willis, M. R., "DAS - An automated System to Support Design Analysis," Proceedings of Third International Conference on Software Engineering, May 1978.
[12]
Hamilton, M. and S. Zeldin, The Foundations for AXES: A Specification Language Based on Completeness of Control. Charles Stark Draper Laboratory, Inc., Cambridge, Mass. Rev. October 31, 1975.
[13]
ICAM Program Prospectus, Air Force Materials Laboratory, Wright-Patterson AFB, Ohio; June 1, 1978.
[14]
Problem Statement Language (PSL), Introduction and User's Manual. PSA Version 4.2, ISDOS Project, University of Michigan, Ann Arbor, MI, May 1977.
[15]
Devorkin, Donald B., Echo Range Software Methodology Report. Computer Sciences Corporation, San Diego, California, July 17, 1978.
[16]
Ross, Douglas T. "Structured Analysis (SA): A Language for Communicating Ideas," IEEE Transactions on Software Engineering, Volume SE-3, No. 1, January 1977.
[17]
Ross, Douglas T. and Kenneth E. J. Schoman, "Structured Analysis for Requirements Definition," IEEE Transactions on Software Engineering, Volume SE-3, No. 1, January 1977.
[18]
RDL/RDP User's Manual, Document No. RSS-060, Update D-4, Sperry-Univac, July 15, 1978.
[19]
Taggart, N. M., Jr., and M. O. Tharp, "A Survey of Information Requirements Analysis Techniques," ACM Computing Surveys, Volume 9, No. 4, December 1977.
[20]
Everhart, C. R., "User Experience With A Formally Defined Requirements Language IORL," in Proceedings of Second U. S. Army Software Symposium, October 1978, 210--219.
[21]
IORL Analyst User's Manual. Teledyne Brown Engineering, Huntsville, Alabama, 1977.
[22]
Xerox Systems Methodology. Xerox Corporation, Rochester, New York, 1978.
[23]
Teichroew, D. and E. Hershey, III, "PSL/PSA: A Computer-Aided Technique for Structured Documentation and Analysis of Information Processing Systems," in Proceedings of Second International Conference Software Engineering, October 1976.
[24]
Davis, C. G. and C. R. Vick, "The Software Development System," IEEE Transactions on Software Engineering, Vol. 3, No. 1, Jan. 1977, 69--84.
[25]
Stephens, S. A. and L. L. Tripp, "Requirements Expression and Verification Atd," in Tutorial: Automated Tools for Software Engineering, IEEE Catalog No. EH0150--3, 1979, 60--67.
[26]
Zave, P. and R. T. Yeh, "Executable Requirements for Embedded Systems," in Proceedings of Fifth International Software Engineering Conference, March 1981, 295--304.
[27]
Hancock, J., "Chipping Away at Productivity," Computerworld, Vol. 13, No. 42, October 15, 1979.
[28]
Gomaa, H. and D. B. H. Scott, "Prototyping as a Tool in the Specification of User Requirements," In Proceedings of Fifth International Software Engineering Conference, March 1981, 333--342.
[29]
Jensen, R. W. and C. C. Tonies, Software Engineering, Englewood Cliffs, N.J.: Prentice-Hall, 1979.
[30]
Foley, J. D., "Tools For the Designers of User Interfaces," Report No. GWU-IIST-81-07, George Washington University, Washington, D. C., 1981.
[31]
Negus, B., M. J. Hunt and J. A. Prentice, "Dialog," Software-Practice and Experience, Vol. 11, 1981, 205--224.
[32]
Janning, M., S. Nachmens and S. Berild, CS4: An Introduction to Associative Data Bases and The CS4 System. Bromley, Kent, Great Britaian: Chartwell-Bratt Ltd., 1981.
[33]
Hsia, P., W. J. Chen, "Experimental Software Engineering," Int'l Computer Symposium, Taipei, Taiwan, 1980.
[34]
Chen, W. J. Experimental Software Engineering, Master's Degree Thesis, July 1981, University of Alabama in Huntsville.
[35]
Hsia, P. and F. Petry, "A Framework for Discipline in Programming," IEEE Trans. Software Engineering, Vol. SE-6, No. 2, March 1980, 226--332.
[36]
Green, T. R. G., M. E. Sime and M. Fitter, Behavioral Experiments on Programming Language, Some Methodological Considerations, (MRC MEMO No. 66), Sheffield, England, Sheffield University Dept. of Psychology, 1975.
[37]
Woodfield, S. N., "An Experiment On Unit Increase in Problem Complexity," IEEE Trans. Software Engineering, March, 1979.
[38]
Shneiderman, B., R. Mayer, D. McKay and P. Heller, "Experimental Investigation of the Utility of Detailed Flowcharts in Programming," CACM Vol. 20, No. 6, June 1977, 353--381.
[39]
Green, T. R. G., "Conditional Program Statements and Their Comprehensibility to Professional Programmer," J. Of Occupational Psychol. 50 (1977), 93--109.
[40]
Sheppard, S. B., P. Milliman, and B. Curtis, "Factors Affecting Programmer Performance in the Debugging Task," G. E. ISP, Feb. 1979.
[41]
Sayware, F. G., "Design of Software Experiment," Meeting On Software Metrics, June 1980.
[42]
Curtis, B., "Experimental Evaluation of Software Characteristics and Programmer Performance," Meeting on Software Metrics, June 1980.
[43]
Brooks, R. E., "Studying Programmer Behavior Experimentally: The Problems of Proper Methodology," CACM, 23, No. 4, April 1980.
[44]
Basili, V. R. and R. W. Reiter, Jr., "A Controlled Experiment Quantitatively Comparing Software Development Approaches," IEEE Transactions On Software Engineering, Vol. SE-7, No. 3, March 1981, 299--320.
Recommendations
Scenario-based prototyping for requirements identification
Special issue on rapid prototypingThe three major facets of software requirements engineering are: (1) requirements identification, (2) requirements analysis, and (3) requirements communication. Much research addresses the latter two aspects, but few practical approaches exist for ...
A scenario-based methodology for conducting requirements elicitation
Requirements analysis is the process of identifying a user's needs and determining what to build in an a system. Within requirements analysis is the process of requirements elicitation in which tacit information about "what to build" is obtained from ...
Interactive Visualization for Elicitation and Validationn of Requirements with Scenario-Based Prototyping
REV '09: Proceedings of the 2009 Fourth International Workshop on Requirements Engineering VisualizationThe different perspectives stakeholders and requirements engineers have on a problem are a major hindrance to de- rive useful requirements. While formal requirements mod- els are well suited for excluding inconsistent requirements, prototypes presented ...
Comments
Please enable JavaScript to view thecomments powered by Disqus.Information & Contributors
Information
Published In
April 1982
190 pages
ISBN:089791094X
DOI:10.1145/1006259
- General Chairs:
- Martha Branstad,
- Marvin Zelkowitz,
- Program Chair:
- Stephen L. Squires
Copyright © 1982 ACM.
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]
Sponsors
Publisher
Association for Computing Machinery
New York, NY, United States
Publication History
Published: 19 April 1982
Check for updates
Qualifiers
- Article
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- View Citations28Total Citations
- 756Total Downloads
- Downloads (Last 12 months)269
- Downloads (Last 6 weeks)36
Reflects downloads up to 19 Dec 2024
Other Metrics
Citations
View Options
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in