Case study in engineering software for reuse
S Ramakrishnan
6 points
* 4 hours per week
* Second semester
* Caulfield
*
Prerequisites: SFT4490
Objectives At the completion of this subject students should understand object-oriented software reuse; know about classification schemes, retrieval and queries to select components from repository; and be able to consider planned reuse in the context of measurements for quality.
Synopsis Explore reuseability issues using a case study approach to systematic software reuse: design with reuse vs design for reuse; reuse granularity; frameworks and reuse tools; reuse models - query and retrieval based on various classification schemes from a repository; reuse process; quality and reuseability of components; design evolution and reuse; pluggable architectures. Identify behaviours that can be reused in another application and design for reuseability by building a library of software modules (software Ics), ie antilogies that define the basic terms and relations of the domain and represent classes based on this ontology; reuse or create components as black-box software components or white-box software components (frameworks); use or develop appropriate software tools to assist in the production of quality object-oriented software systems and construct a reasonably complex object-oriented system in a software engineering context.
Assessment Classroom discussion: 25%
* Practical assignment: 75%
Recommended texts
Gamma E and others Design patterns Addison-Wesley, 1995
Jacobson I Object-oriented software engineering Addison-Wesley, 1992
McGregor J Object-oriented software development: Engineering software for reuse Van Nostrand, 1992
Meyer B Eiffel the language Prentice-Hall, 1992
Meyer B Reusable software Prentice-Hall, 1994
| Published by Monash University, Clayton, Victoria
3168 Copyright © Monash University 1996 - All Rights Reserved - Caution Authorised by the Academic Registrar December 1996 |