GDPA  
Prescriptive Task Chains  

A-B-C- D-E-F- G-H-I- J-K-L- M-N-O- P-Q-R- S-T-U- V-W-X- Y-Z

Identification

Prescriptive Task Chains

Definitions/Uses

2001
Reference /Scacchi, 2001/ Process Models in Software Engineering
Definition/
Use		 Prescriptive task chains are idealized plans of what actions should be accomplished, and in what order. For example, a task chain for the activity of object-oriented software design might include the following task actions:
  • Develop an informal narrative specification of the system
  • Identify the objects and their attributes
  • Identify the operations on the objects
  • Identify the interfaces between objects, attributes, or operations
  • Implement the operations
Clearly, this sequence of actions could entail multiple iterations and non-procedural primitive action invocations in the course of incrementally progressing toward an object-oriented software design.

Task chains join or split into other task chains resulting in an overall production network or web /Kling, 1982/.

See also

Descriptive Task Chains
Process Model

This page online  •  GDPA Online  •  Last Updated 10.June.2002 by C. Freericks