D. M. Berry K. Daudjee J. Dong I. Fainchtein M. A. Nelson T. Nelson L....  Home/Search
Context
Related
| utdallas.edu/~jdong/pap...userman03.pdf Cached: PS.gz PS PDF This document uses CoBlitz to cache paper downloads. If your firewall is blocking outgoing connections to port 3125, you can use these links to download local copies.
Image Update HelpPS.gz PS PDF From: utdallas.edu/~jdong/research (more) (Enter author homepages) |
Rate this article:      (best)Comment on this article |
Abstract: This paper argues that a user#s manual makes an excellent software requirements specification. It describes several experiences, including one in industry, of writing user#s manuals as requirements specifications. Finally, it discusses several lessons learned from the experiences. (Update)
Similar documents (at the sentence level):
27.2%: User's Manual as a Requirements Specification - Berry, Daudjee, Dong, Nelson.. (2001) (Correct)
Active bibliography (related documents): More All
0.6: The Role of Emotion, Values, and Beliefs in - The Construction Of (Correct)
0.5: Management View on Current Requirements Engineering.. - Nikula, Sajaniemi.. (2000) (Correct)
0.4: From Contract Drafting to Software Specification: Linguistic.. - Berry, al. (2000) (Correct)
Similar documents based on text:
0.0: Unknown - (Correct)
BibTeX entry: (Update)
@misc{ dong-original,
author = "Berry Daudjee Dong",
title = "Original Article",
url = "citeseer.ist.psu.edu/742682.html" }
Citations (may not include all citations):441 Software engineering economics (context) - BW - 1981
237 Software testing techniques (context) - Beizer - 1990
204 Object-oriented software engineering (context) - Jacobson - 1992
200 PostScript language reference manual (context) - Inc - 1992
131 The mythical man-month: essays on software engineering (context) - Jr - 1975
86 A rational design process: how and why to fake it (context) - DL, PC - 1986
49 Advances in software inspections (context) - ME - 1986
42 Software requirements: analysis and specification (context) - AM - 1990
40 Scenarios in system development: current practice (context) - Weidenhaupt, Pohl et al. - 1998
40 The inevitable intertwining of specification and implementat.. (context) - Swartout, Balzer - 1982
30 Requirements engineering: a roadmap - Nuseibeh, Easterbrook - 2000
28 Software engineering concepts (context) - RE - 1985
25 Exploring requirements: quality before design (context) - DC, GM - 1989
23 Weaving together requirements and architecture (context) - BA - 2001
19 PIC---a language for typesetting graphics (context) - BW - 1982
17 Intent specification: an approach to building human-centered.. - NG - 1998
17 Requirements engineering in the year 00: a research perspect.. (context) - van Lamsweerde - 2000
15 A typesetter-independent TROFF (context) - BW - 1982
12 Computer Science Department (context) - What, how et al. - 2001
12 Requirements engineering: the emerging wisdom (context) - Siddiqi - 1996
12 A strategy for conceptual model acquisition (context) - JCSP, APM - 1993
10 Functional program testing (context) - WE - 1980
9 Dorset House (context) - deadline - 1997
8 Problem frames: analysing and structuring software developme.. (context) - MA - 2001
7 Requirements engineering (context) - DM - 1998
7 IEEE Standard portable operating system interface for comput.. (context) - POSIX - 1988
6 flo---A language for typesetting flowcharts - Wolfman - 1989
6 flo---A language for typesetting flowcharts - Wolfman - 1990
6 Surfacing ambiguity in natural language requirements (context) - Kamsties - 2001
6 Requirements engineering in small and medium enterprises (context) - Kamsties, Ho et al. - 1998
6 Requirements development in scenario-based design (context) - Carroll, Rosson et al. - 1998
6 Scenario-based prototyping for requirements identification (context) - JW - 1982
5 A method for extracting and stating software requirements th.. - Ravid - 1999
5 software project management: principles and examples (context) - BW, Theory - 1989
4 Requirements engineering (context) - Sommerville, Sawyer - 1997
4 Introducing requirements engineering: how to make a cultural.. (context) - Kauppinen, Kujala et al. - 2002
3 Can English majors write maintenance documentation (context) - RL - 1993
3 Requirements engineering (context) - Kotonya, Sommerville - 1998
3 NROFFTROFF user#s manual (context) - TROFF, Technical et al. - 1976
1 Elicitation of requirements from user documentation - John, Do - 2003
1 ciency requirements with use cases (context) - rr, Kerkow et al. - 2003
1 Requirements specification for a large-scale telephony-based.. (context) - Fainchtein - 2002
1 WD-pic (context) - Ou - 2002
1 Pontif cia Universidade Cato lica (context) - Evoluc, rios et al. - 2000
1 Scenarios and design cognition (context) - JM - 2002
1 WD-pic (context) - Shpilberg - 1997
Documents on the same site (http://www.utdallas.edu/~jdong/research.html): More
Component Contract Templates - A Rigorous Approach for.. - Dong, Alencar, Cowan (Correct)
Extending UML to Visualize Design Patterns in Class Diagrams - Dong, Yang (Correct)
On Analysis of Design Component Contracts: A Case Study - Dong, Alencar, Cowan (Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC