Write The User Manual First Is Waterfall

Some contributors to WriteTheUserManualFirst suggest this is a WaterFall.

There are at some different sub-topics here

1 What is WaterFall, really? That question has other pages devoted to it.

2 Does the use of the word First in WriteTheUserManualFirst necessarily imply WaterFall? Does insistence on sequence imply WaterFall?

3 Are there artifacts generated in a software project (e.g. a UserManual) that should not change rapidly?

4 How does a the user manual differ from a user story?
1 What is WaterFall, really? That question has other pages devoted to it.

2 Does the use of the word First in WriteTheUserManualFirst necessarily imply WaterFall? Does insistence on sequence imply WaterFall?

3 Are there artifacts generated in a software project (e.g. a UserManual) that should not change rapidly?


4 How does a the user manual differ from a user story?

See UserManualIsNotUserStory
[Parnas1986] Dave L. Parnas and Paul C. Clements, A RATIONAL DESIGN PROCESS: HOW AND WHY TO FAKE IT for IEEE Transactions on Software Engineering Vol. SE-12, No. 2, February, 1986 pp. 251-257, reprinted as Ch. 18 of "Software Fundamentals: Collected Papers by David L. Parnas, ed D. M. Hoffman and D. M. Weiss, Addison-Wesley, 2001, ISBN 0-201-70369-6 also at http://cobolreport.com/columnists/parnas&clements/09152003.asp
See: WaterfallMethodology, WaterFall, WaterfallMethod, WaterfallModel, WaterfallSyndrome, TestDrivenDevelopment

EditText of this page (last edited May 26, 2004) or FindPage with title or text search