Pitfalls using UML in RUP

This document was uploaded by one of our users. The uploader already confirmed that they had the permission to publish it. If you are author/publisher or own the copyright of this documents, please report to us by using this DMCA report form.

Simply click on the Download Book button.

Yes, Book downloads on Ebookily are 100% Free.

Sometimes the book is free on Amazon As well, so go ahead and hit "Search on Amazon"

14+12 p.
(Выходные данные не указаны).
Did you ever follow the rules of the Rational Unified Process (RUP) in using UML? Well, I tried! is a commonly heard answer to that question. This is the first of two papers written for those that tried or are about to. I’ve tried it myself a number of times and yes, I failed. Following RUP blindly simply doesn’t work, but fortunately, you don’t have to say good-bye to the process altogether. Let me help you by pointing out some of the pitfalls and first of all, by providing an overview of the various models in RUP.
The first paper focuses on business modeling and requirements specification. I will recommend to drop the Business Use Case Model, to use the Domain Model in your use cases and to detail the use cases using activity diagrams.
The second paper describes the use of UML for analysis and design.

Author(s): Admiraal Hans.

Language: English
Commentary: 1371448
Tags: Информатика и вычислительная техника;Объектное моделирование (UML)