A work product pool approach to methodology specification and enactment
- Publication Type:
- Journal Article
- Citation:
- Journal of Systems and Software, 2008, 81 (8), pp. 1288 - 1305
- Issue Date:
- 2008-08-01
Closed Access
| Filename | Description | Size | |||
|---|---|---|---|---|---|
 | 2007005373OK_Gonzalez.pdf | 734.88 kB |
Copyright Clearance Process
- Recently Added
- In Progress
- Closed Access
This item is closed access and not available.
Software development methodologies advocated and used today, whether traditional and plan-based or contemporary and agile, usually focus on process steps i.e. they start with requirements and iteratively describe what steps are necessary to move to the next stage or phase, until the software application is delivered to the end user. Such a process-oriented view of methodologies, based on the metaphor that human organizations are "machines" that "execute" processes, often results in methodologies that are too rigid and hard to follow, and most often than not end up being ignored or bypassed. Our proposal here is that, since the ultimate aim of software development is to provide a software product, software development methodologies should be described in terms of the intermediate products that are necessary to reach such a final product, plus the needed micro-processes that, as necessary evils, will be required to produce the appropriate work products from other, previously created ones. Using this product-oriented approach, software development methodologies can be specified that are, at least, as flexible as lightweight, agile approaches and, at the same time, as powerful and scalable as plan-oriented ones. © 2007 Elsevier Inc. All rights reserved.
Please use this identifier to cite or link to this item: