During design, your goal will be to decide how the expected functionality is to be allocated to each part of the system. You need to make choices about which classes the system operations should be allocated to. These decisions can be explored and documented using further behaviour models. UML uses interaction (sequence and communication) diagrams that show a set of classes and the messages between them.
During design both structural and behaviour models are elaborated. In fact you will see that behaviour models are used for both external and internal behaviour of objects.
Some artefacts involved in design are shown in Figure 11.
Allow approximately 15 minutes.
OpenLearn - Approaches to software development Except for third party materials and otherwise, this content is made available under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 Licence, full copyright detail can be found in the acknowledgements section. Please see full copyright statement for details.