|
Class Diagrams and Use Cases - Experimental Examination of the Preferred Order of Modeling |
|
Peretz Shoval, Avi Yampolsky, Mark Last
|
|
Monday, 05 June 2006 |
In most UML-based methodologies, the analysis tasks include
mainly modeling the functional requirements using use cases, and modeling the
problem domain using a class diagram. Different methodologies prescribe different orders of carrying out these tasks, and there is no commonly agreed order
for performing them. In order to find out whether the order of these analysis activities makes any difference, and which order leads to better results, we carried
out a comparative experiment. Subjects were asked to create the two analysis
models for a certain system in two opposite orders, and the qualities of the produced models were then compared. The results of the experiment reveal that the
class diagram is of better quality when created as the first modeling task, while
no significant effect of the analysis order was found on the quality of the use
cases. We also found out that analysts prefer starting the analysis with data
modeling.
[PDF]
[Slides in PDF]
[BibteX]
Only registered users can write comments.
Please login or register. |
