Use Case Driven Iterative Development: Hurdles and Solutions
Theory says that typical construction iterations in an iterative software development project consist of taking some use cases previously identified and then developing and testing them. However, reality says that use cases are revisited in several iterations, creating a challenging problem in terms of how to specify these “deltas” of functionality in a practical manner, and manage these deltas as their number increase and “deltas of deltas” spawn. The longer the project, the more probable is that this will happen. This paper elaborates on the experience of a use case driven software development project and explains how to deal with this issue.
KeywordsCase Document Iterative Development Requirement Management Tool Case Functionality Project Milestone
Unable to display preview. Download preview PDF.
- 1.Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Sotware Development Process. Addison Wesley, Reading (1998)Google Scholar
- 2.Gottesdiener, E.: Use Cases: Best Practices. IBM Technical Paper (2003) Google Scholar
- 3.Bittner, K., Spence, I.: Use Case Modeling. Addison-Wesley, Reading (2003)Google Scholar
- 4.Evans, G.: Getting from use cases to code Part 1: Use-Case Analysis. IBM Technical Paper (2004)Google Scholar
- 5.Cockburn, A.: Writing effective use cases. Addison Wesley, Reading (2001)Google Scholar