Summary
In this chapter, we examined how ICONIX Process and TDD can be combined to great effect. To combine these two disciplines, we have had to rewrite the rules slightly for TDD, but the basics are pretty much the same.
Using TDD on its own without any up-front design modeling is actually very rare. Even in XP a certain amount of up-front design modeling is generally used—this is normally a collaborative design workshop held just before the coding session, also known as Just-in Time (JIT) Design.4 In such environments, consider using ICONIX Process as described here to improve the collaborative design process.
Finally, at the end of the chapter, we described an automated, model-driven testing process that you can use to drive a testing effort from your use case-driven models.
Named after “Just-in-Time” compilers used in runtime environments such as Java HotSpot, and also used in quality management.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
David Astels, Test-Driven Development: A Practical Guide (Upper Saddle River, NJ: Prentice-Hall, 2003), p. 203.
Doug Rosenberg and Kendall Scott, Use Case Driven Object Modeling with UML: A Practical Approach (New York: Addison-Wesley, 1999), p. 69.
Rights and permissions
Copyright information
© 2005 Doug Rosenberg, Matt Stephens, and Mark Collins-Cope
About this chapter
Cite this chapter
(2005). Test-Driven Development with ICONIX Process. In: Agile Development with ICONIX Process. A-Press. https://doi.org/10.1007/978-1-4302-0009-3_12
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0009-3_12
Publisher Name: A-Press
Print ISBN: 978-1-59059-464-3
Online ISBN: 978-1-4302-0009-3
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)