%0 Conference Paper %1 simons99usecase %A Simons, A.J.H. %B Technology of Object-Oriented Languages and Systems, 1999. Proceedings of %D 1999 %K cites.dss cites.pclass research.conceptual.usecases %P 194-203 %R 10.1109/TOOLS.1999.779012 %T Use cases considered harmful %U http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=779012 %X This article traces the unstable semantics of use cases fromJacobson to UML 1.3. The UML 1.1 metamodel formally defined the“uses” and “extend” use case relationships asstereotypes of generalisation, yet both received interpretations thatvaried between inheritance and composition, reflecting a large degree ofconfusion among developers. The recently revised UML 1.3 has quietlydropped these in favour of new “include” and“extend” relationships, which are styled instead as kind ofdependency. Despite this change, the deployment of use case diagramsencourages analysts to correspondence and develop models which concealarbitrary jumps in the flow of control, corresponding to goto and comefrom statements, and in which unpleasant non-local dependencies existacross modules. A discussion of examples reveals how a conscientiousdesigner must disassemble use case models completely to produceproperly-structured code. A radical solution is proposed %@ 0-7695-0275-x

@inproceedings{simons99usecase, abstract = {This article traces the unstable semantics of use cases fromJacobson to UML 1.3. The UML 1.1 metamodel formally defined the“uses” and “extend” use case relationships asstereotypes of generalisation, yet both received interpretations thatvaried between inheritance and composition, reflecting a large degree ofconfusion among developers. The recently revised UML 1.3 has quietlydropped these in favour of new “include” and“extend” relationships, which are styled instead as kind ofdependency. Despite this change, the deployment of use case diagramsencourages analysts to correspondence and develop models which concealarbitrary jumps in the flow of control, corresponding to goto and comefrom statements, and in which unpleasant non-local dependencies existacross modules. A discussion of examples reveals how a conscientiousdesigner must disassemble use case models completely to produceproperly-structured code. A radical solution is proposed}, added-at = {2008-04-04T00:32:10.000+0200}, author = {Simons, A.J.H.}, biburl = {https://www.bibsonomy.org/bibtex/26d352215ff320e16b581da4744b12391/msn}, booktitle = {Technology of Object-Oriented Languages and Systems, 1999. Proceedings of}, doi = {10.1109/TOOLS.1999.779012}, interhash = {d38f9ca6a2a9415476974774f2cd5a2b}, intrahash = {6d352215ff320e16b581da4744b12391}, isbn = {0-7695-0275-x}, keywords = {cites.dss cites.pclass research.conceptual.usecases}, pages = {194-203}, timestamp = {2009-06-25T15:59:14.000+0200}, title = {Use cases considered harmful}, url = {http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=779012}, year = 1999 }