37 Things that Don't Work in Object-Oriented Modelling with UML
msra(1998)
摘要
The authors offer a catalogue of problems experienced by developers, using various object modelling techniques brought into prominence by the current widespread adoption of UML standard notations. The problems encountered have different causes, including: ambiguous semantics in the modelling notations, cognitive misdirection during the development process, inadequate capture of salient system properties, lack of appropriate supporting tools and developer inexperience. Some of the problems can be addressed by increased guidance on the consistent interpretation of diagrams and the most helpful sequencing of techniques. Others require a revision of UML and its supporting tools. Most problems can be traced to the awkward transition between analysis and design, where UML's eclectic philosophy (the same notation for everything) comes unstuck. Modelling techniques that were appropriate for informal elicitation are being used to document hard design decisions; the same UML models are subject to different interpretations in analysis and design; developers are encouraged to follow analytical procedures which do not translate straightforwardly into clean designs. UML is itself neutral with respect to good or bad designs; but the consequences of allowing UML to drive the development process are: inadequate object conceptualisation, poor control structures and poorly-coupled subsystems.
更多查看译文
关键词
development process,control structure
AI 理解论文
溯源树
样例
生成溯源树,研究论文发展脉络