ACM Home Page
Please provide us with feedback. Feedback
Playscript for use cases
Full text PdfPdf (212 KB)
Source
ACM SIGSOFT Software Engineering Notes archive
Volume 33 ,  Issue 5  (September 2008) table of contents
SECTION: Article abstracts with full text online table of contents
Article No. 7  
Year of Publication: 2008
ISSN:0163-5948
Author
Richard Riehle  Naval Postgraduate School, Monterey, CA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 68,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1402521.1402525
What is a DOI?

ABSTRACT

The concept of use case has become popular in developing requirements for software systems. It is even recommended as an inherent part of the Unified Modeling Language (UML). An early predecessor of the use case for systems and procedures practice in the 1960's was the Playscript procedure. This article describes how Playscript can contribute to better use cases.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Matthies, Leslie H., The New Playscript Procedure, Management Tool for Action, Office Publications, Inc., Stamford, CT, Second Edition, 1977.
2
 
3
 
4
Larman, Craig, Applying UML and Patterns, Prentice-Hall, Third Edition, 2005, page 80.
 
5
 
6
 
7
Larman, Craig, Applying UML and Patterns, Prentice-Hall, Third Edition, 2005, page 78--79.
8