How to use UML! Part 2
Filed under How To
Part 2 of our short brief “How to use UML”. You have missed part 1 of our example? Click here for the related article.
4. Now you can start to construct a domain model (high level business objects), sequence diagrams, collaboration diagrams and user interface models straight from the in- and outputs of the BPM and the details of the use cases. With this describtion you describe the of the interaction and an interface for users to to execute use case scenarios.
5. Create now the Class Model out of the the domain model, the user interface model and the scenario diagrams. In this precise specification you define the objects in the system, their data or attributes and their behaviour or operations. Use inheritance to abstract domain object into class hierarchies. Scenario diagram messages map to class operations. You can also use existing framework or design pattern by importing an existing model element into the new system. Do not forget to define tests for each unique class and all class functions.
6. Beginning with the class model you can brake it into discrete packages and components. Than each component represents a deployable chunk of software collecting its behaviour and the data of the classes. The built component model defines the logical packaging of classes. For each component define integration tests to confirm that the component’s interface meets the specifcation given it in relation to other software elements.
7. Do not forget to capture and document all additional requirements and collect them within the model; try to keep up to date as you do with the model matures.
Keep on reading “how to use UML” here.
