How to use UML! Part 1
Filed under How To
If you need a suitable Case tool, to define requirements, interaction and elements of the proposed software system, than UML is the right development methodology for your use. There is no exact nature of a process, because this depends on your requirements, but fo example it could look like this:
1. You need a Business Process Model. In this BPM you define the high level business activities and processes to provide a foundation for the Use Case model.
2. Now you map a Use Case Model to your Business Process Model. This UCM defines exactly the functionality of the business requirements and what functionality you are intending to provide from the business user. Done by a traceable link from the appropriate business processes to the Use Case which outlines the business requirements in the process model.
Note: A Use Case Model ensures that an Use Case never exist without a purpose.
3. The next step is to describe what the Use Case has to do, including all necessary requirements, constraints, complexity rating, notes and scenarios. But make sure that the Use Case always meets the business process requirements. An included user acceptance test script will define how the user will test this functionality and what the acceptance criteria are.
Read more of “How to use UML” in the following article “How to use UML! Part 2″
