Agile Development Using Naked Objects
Naked objects are core business objects that are exposed directly to the user, by means of a suitable framework. As well as offering benefits to the finished system, the use of naked objects also facilitates the use of agile development techniques. In particular, it enables the concept of an exploration phase during which users and developers prototype the user interface and the underlying business object model simultaneously. During the subsequent delivery phase, naked objects make it easier to adopt the extreme programming discipline of writing executable user acceptance tests in advance of writing the code to implement a particular story.
KeywordsExploration Phase Business Object User Story Agile Development Planning Game
Unable to display preview. Download preview PDF.
- 1.Ambler, S., Agile Modelling: Effective Practices for Extreme Programming and the Unified Process. 2002: John Wiley & Sons.Google Scholar
- 2.Beck, K., EXtreme Programming EXplained. 1999: Addison-Wesley.Google Scholar
- 3.Jacobson, I., J. Rumbaugh, and G. Booch, The Unified Software Development Process. 1999.Google Scholar
- 4.Palmer, S. and M. Felsing, A Practical Guide to Feature Driven Development. 2002: Prentice Hall.Google Scholar
- 5.Pawson, R. and R. Matthews, Naked objects: a technique for designing more expressive systems. SIGPLAN Notices, 2001. 36(12).Google Scholar
- 6.Pawson, R. and R. Matthews, Naked Objects. 2002: J Wiley.Google Scholar
- 7.Raskin, J., The Humane Interface. 2000, Reading, MA: Addison-Wesley / ACM Press.Google Scholar
- 8.Stapleton, J., Dynamic Systems Development Method. 1997, Reading, MA: Addison-Wesley.Google Scholar