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.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
