Author(s)

C.H.K. Tsang, N.V. Balasubramanian, C. Bloor & C.K. Lam

Abstract

Different software organisations may, depending on their product domains and their prime contractor requirements, use different methodologies for software development or different customisation of the same methodology. It is therefore desirable that a CASE tool should effectively support not only one design methodology but a number of methodologies and their adaptations/customisations. It would also be desirable for the CASE tool to support integration of these methodologies, allowing designers to use them in a complementary way. As the methodology evolves, software organisations may need to adopt newer methodologies; the CASE tool should also support the newer de

Keywords