Modelling object-oriented software – an introduction

Course learning outcomes

After studying this course, you should be able to:

• list the components that make up a conceptual model of a system domain, and describe briefly the form and purpose of each component
• explain why a conceptual model forms the basis for modelling the structure of the system, i.e. gives an initial structural model of the system
• use various techniques and guidelines to identify an appropriate set of classes and associations from a requirements document, including their attributes and multiplicities
• identify situations where a generalisation relationship between classes exists, and decide on appropriate parent and child classes, and their attributes and associations.
• identify and reason about derived attributes and associations.