◄Back

# Long description

The figure shows which artefacts are used in which phase of the development process. The phases shown are Domain modelling, Requirements, Analysis, and Design.

In ‘Domain modelling’ are the following artefacts: ‘Glossary’, represented by a list of textual items; ‘Problem statement’, represented as a small sheet of paper with scribblings on it.; ‘Business processes’ represented by an activity diagram; ‘Business rules’; and, ‘domain structural model’ represented by a class diagram. Under ‘Structural domain model’ it says:

‘- conceptual classes and associations

- conceptual attributes

- no operations or interfaces as yet’.

In Requirements are the following artefacts: ‘Glossary’ and ‘Problem statement’ represented as in domain modelling; plus ‘Use case model’ represented by a use case diagram; ‘Elaborated use cases’ represented by a list a textual use case; and ‘Functional and non-functional software requirements’, represented by a textual description of a requirement.

In ‘Analysis’ are the following artefacts: ‘Glossary’ represented as in domain modelling; ‘System operations’ represented by an abridged version of a formal description of an OCL operation; and ‘analysis structural model’ represented by a class diagram. Under ‘analysis structural model’ it says:

‘-analysis classes

-constraints’.

In ‘Design’ are the following artefacts: ‘Glossary’ represented as in domain modelling; ‘Behaviour model (interaction diagrams)’ represented by a communication diagram; and ‘design structural model’, by a class diagram. Under ‘design structural model’ it says:

‘- navigability

- qualified associations

- class operations’.