Approaches to software development
◄Previous: 3.4 Activities and artefacts in the development process

# Domain modelling

Our starting point will be to document and model the structure and processes of the organisation’s business. Starting from some description of the problem, the initial problem statement, you will learn how to identify elements of the real-world problem and their properties, and build corresponding structural and dynamic models. The emphasis at this stage is on understanding the current domain situation.

The behaviour model provides descriptions of business processes and behavioural aspects of the domain. You will meet modelling techniques such as activity diagrams. Business rules are used to express constraints on the dynamic model. For example, given a behaviour model describing aspects of a library, there might be a business rule determining the limit on the number of books an individual member can borrow. A structural domain model, also called the conceptual model, describes the significant concepts in the domain and how they are related.

A glossary of relevant terms and definitions is also produced. This textual document grows throughout the duration of the project.

Some artefacts involved in domain modelling (as well as some used in other phases) are shown in Figure 11.

Figure 11 Some development artefacts
View long description

## Activity 14 Domain modelling

Allow approximately 15 minutes.

1. What is the purpose of domain modelling?
2. What is the role of each of the artefacts produced during domain modelling?

## Answer

1. Domain modelling is concerned with gaining an understanding of the environment in which any system that is designed must operate.
2. During domain modelling, we produce the following artefacts:
   - initial problem statement – a description of the problem
   - behaviour model – a description of the business processes and behaviour of the domain
   - business rules – constraints on the way the behaviour model operates
   - glossary – definitions of relevant terms
   - structural domain model – an initial structural model representing the concepts relevant to the domain.

◄Contents►Next: Requirements

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.