40
Views
5
CrossRef citations to date
0
Altmetric
Original Articles

Experience with Work-Product Oriented Software Development Projects

Pages 111-133 | Published online: 09 Aug 2010
 

Abstract

In this paper, we describe our experiences with student team projects in object-oriented software development. Object-oriented development processes are not as straightforward as, for example, traditional waterfall-like models. In object-oriented development, there is no clear border between analysis, design, and implementation. Students therefore have difficulties deciding on what to do next, how to do it, and why to do it. A work-product oriented development process provides a framework for structuring and managing object-oriented development. Development can be defined in terms of interrelated work products. Each work product is defined by its purpose and contents, the inputs needed, and the techniques used to produce it. The definition of a development process and the production of a single work product are therefore more straightforward. Our experiences show that such an approach is very suitable for student team projects.

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.